0s autopkgtest [16:45:17]: starting date: 2024-03-09 0s autopkgtest [16:45:17]: git checkout: d9c0295 adt_testbed.py: supress warnings from apt using a shell pipeline 0s autopkgtest [16:45:17]: host juju-7f2275-prod-proposed-migration-environment-2; command line: /home/ubuntu/autopkgtest/runner/autopkgtest --output-dir /tmp/autopkgtest-work.mo1s5hw6/out --timeout-copy=6000 --setup-commands /home/ubuntu/autopkgtest-cloud/worker-config-production/setup-canonical.sh --setup-commands /home/ubuntu/autopkgtest/setup-commands/setup-testbed --apt-pocket=proposed=src:gnome-desktop-testing,src:glib2.0 --apt-upgrade libfprint --timeout-short=300 --timeout-copy=20000 --timeout-build=20000 '--env=ADT_TEST_TRIGGERS=gnome-desktop-testing/2021.1-3build1 glib2.0/2.79.3-3ubuntu3' -- ssh -s /home/ubuntu/autopkgtest/ssh-setup/nova -- --flavor autopkgtest --security-groups autopkgtest-juju-7f2275-prod-proposed-migration-environment-2@bos03-arm64-16.secgroup --name adt-noble-arm64-libfprint-20240309-164517-juju-7f2275-prod-proposed-migration-environment-2 --image adt/ubuntu-noble-arm64-server --keyname testbed-juju-7f2275-prod-proposed-migration-environment-2 --net-id=net_prod-proposed-migration -e TERM=linux -e ''"'"'http_proxy=http://squid.internal:3128'"'"'' -e ''"'"'https_proxy=http://squid.internal:3128'"'"'' -e ''"'"'no_proxy=127.0.0.1,127.0.1.1,login.ubuntu.com,localhost,localdomain,novalocal,internal,archive.ubuntu.com,ports.ubuntu.com,security.ubuntu.com,ddebs.ubuntu.com,changelogs.ubuntu.com,launchpadlibrarian.net,launchpadcontent.net,launchpad.net,10.24.0.0/24,keystone.ps5.canonical.com,objectstorage.prodstack5.canonical.com'"'"'' --mirror=http://ftpmaster.internal/ubuntu/ 63s autopkgtest [16:46:20]: @@@@@@@@@@@@@@@@@@@@ test bed setup 64s Get:1 http://ftpmaster.internal/ubuntu noble-proposed InRelease [117 kB] 64s Get:2 http://ftpmaster.internal/ubuntu noble-proposed/multiverse Sources [37.3 kB] 65s Get:3 http://ftpmaster.internal/ubuntu noble-proposed/main Sources [429 kB] 65s Get:4 http://ftpmaster.internal/ubuntu noble-proposed/restricted Sources [3976 B] 65s Get:5 http://ftpmaster.internal/ubuntu noble-proposed/universe Sources [2635 kB] 65s Get:6 http://ftpmaster.internal/ubuntu noble-proposed/main arm64 Packages [577 kB] 65s Get:7 http://ftpmaster.internal/ubuntu noble-proposed/main arm64 c-n-f Metadata [3144 B] 65s Get:8 http://ftpmaster.internal/ubuntu noble-proposed/restricted arm64 Packages [20.3 kB] 65s Get:9 http://ftpmaster.internal/ubuntu noble-proposed/restricted arm64 c-n-f Metadata [116 B] 65s Get:10 http://ftpmaster.internal/ubuntu noble-proposed/universe arm64 Packages [2881 kB] 65s Get:11 http://ftpmaster.internal/ubuntu noble-proposed/universe arm64 c-n-f Metadata [8528 B] 65s Get:12 http://ftpmaster.internal/ubuntu noble-proposed/multiverse arm64 Packages [39.2 kB] 65s Get:13 http://ftpmaster.internal/ubuntu noble-proposed/multiverse arm64 c-n-f Metadata [116 B] 66s Fetched 6752 kB in 2s (3285 kB/s) 67s Reading package lists... 70s Reading package lists... 70s Building dependency tree... 70s Reading state information... 70s Calculating upgrade... 70s The following package was automatically installed and is no longer required: 70s ubuntu-advantage-tools 70s Use 'sudo apt autoremove' to remove it. 71s The following packages will be REMOVED: 71s libglib2.0-0 71s The following NEW packages will be installed: 71s libglib2.0-0t64 libnuma1 libsensors-config libsensors5 numactl sysstat 71s xdg-user-dirs 71s The following packages will be upgraded: 71s efibootmgr gir1.2-glib-2.0 libglib2.0-data ubuntu-minimal ubuntu-standard 71s 5 upgraded, 7 newly installed, 1 to remove and 0 not upgraded. 71s Need to get 2402 kB of archives. 71s After this operation, 2353 kB of additional disk space will be used. 71s Get:1 http://ftpmaster.internal/ubuntu noble-proposed/main arm64 gir1.2-glib-2.0 arm64 2.79.3-3ubuntu3 [182 kB] 71s Get:2 http://ftpmaster.internal/ubuntu noble-proposed/main arm64 libglib2.0-0t64 arm64 2.79.3-3ubuntu3 [1527 kB] 71s Get:3 http://ftpmaster.internal/ubuntu noble-proposed/main arm64 libglib2.0-data all 2.79.3-3ubuntu3 [46.6 kB] 71s Get:4 http://ftpmaster.internal/ubuntu noble/main arm64 ubuntu-minimal arm64 1.535 [10.5 kB] 71s Get:5 http://ftpmaster.internal/ubuntu noble/main arm64 xdg-user-dirs arm64 0.18-1 [18.1 kB] 71s Get:6 http://ftpmaster.internal/ubuntu noble/main arm64 libnuma1 arm64 2.0.18-1 [23.5 kB] 71s Get:7 http://ftpmaster.internal/ubuntu noble/main arm64 ubuntu-standard arm64 1.535 [10.5 kB] 71s Get:8 http://ftpmaster.internal/ubuntu noble/main arm64 efibootmgr arm64 18-1build1 [31.5 kB] 71s Get:9 http://ftpmaster.internal/ubuntu noble/main arm64 libsensors-config all 1:3.6.0-9 [5458 B] 71s Get:10 http://ftpmaster.internal/ubuntu noble/main arm64 libsensors5 arm64 1:3.6.0-9 [26.9 kB] 71s Get:11 http://ftpmaster.internal/ubuntu noble/main arm64 numactl arm64 2.0.18-1 [39.5 kB] 71s Get:12 http://ftpmaster.internal/ubuntu noble/main arm64 sysstat arm64 12.6.1-1ubuntu1 [480 kB] 72s Preconfiguring packages ... 72s Fetched 2402 kB in 1s (3161 kB/s) 73s (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 ... 74662 files and directories currently installed.) 73s Preparing to unpack .../gir1.2-glib-2.0_2.79.3-3ubuntu3_arm64.deb ... 73s Unpacking gir1.2-glib-2.0:arm64 (2.79.3-3ubuntu3) over (2.79.2-1~ubuntu1) ... 74s dpkg: libglib2.0-0:arm64: dependency problems, but removing anyway as you requested: 74s udisks2 depends on libglib2.0-0 (>= 2.77.0). 74s shared-mime-info depends on libglib2.0-0 (>= 2.75.3). 74s python3-gi depends on libglib2.0-0 (>= 2.77.0). 74s python3-dbus depends on libglib2.0-0 (>= 2.16.0). 74s netplan.io depends on libglib2.0-0 (>= 2.70.0). 74s netplan-generator depends on libglib2.0-0 (>= 2.70.0). 74s libxmlb2:arm64 depends on libglib2.0-0 (>= 2.54.0). 74s libvolume-key1:arm64 depends on libglib2.0-0 (>= 2.18.0). 74s libudisks2-0:arm64 depends on libglib2.0-0 (>= 2.75.3). 74s libqrtr-glib0:arm64 depends on libglib2.0-0 (>= 2.56). 74s libqmi-proxy depends on libglib2.0-0 (>= 2.30.0). 74s libqmi-glib5:arm64 depends on libglib2.0-0 (>= 2.54.0). 74s libpolkit-gobject-1-0:arm64 depends on libglib2.0-0 (>= 2.38.0). 74s libpolkit-agent-1-0:arm64 depends on libglib2.0-0 (>= 2.38.0). 74s libnetplan0:arm64 depends on libglib2.0-0 (>= 2.75.3). 74s libmm-glib0:arm64 depends on libglib2.0-0 (>= 2.62.0). 74s libmbim-proxy depends on libglib2.0-0 (>= 2.56). 74s libmbim-glib4:arm64 depends on libglib2.0-0 (>= 2.56). 74s libjson-glib-1.0-0:arm64 depends on libglib2.0-0 (>= 2.75.3). 74s libjcat1:arm64 depends on libglib2.0-0 (>= 2.75.3). 74s libgusb2:arm64 depends on libglib2.0-0 (>= 2.75.3). 74s libgudev-1.0-0:arm64 depends on libglib2.0-0 (>= 2.38.0). 74s libgirepository-1.0-1:arm64 depends on libglib2.0-0 (>= 2.79.0). 74s libfwupd2:arm64 depends on libglib2.0-0 (>= 2.79.0). 74s libblockdev3:arm64 depends on libglib2.0-0 (>= 2.42.2). 74s libblockdev-utils3:arm64 depends on libglib2.0-0 (>= 2.75.3). 74s libblockdev-swap3:arm64 depends on libglib2.0-0 (>= 2.42.2). 74s libblockdev-part3:arm64 depends on libglib2.0-0 (>= 2.42.2). 74s libblockdev-nvme3:arm64 depends on libglib2.0-0 (>= 2.42.2). 74s libblockdev-mdraid3:arm64 depends on libglib2.0-0 (>= 2.42.2). 74s libblockdev-loop3:arm64 depends on libglib2.0-0 (>= 2.42.2). 74s libblockdev-fs3:arm64 depends on libglib2.0-0 (>= 2.42.2). 74s libblockdev-crypto3:arm64 depends on libglib2.0-0 (>= 2.42.2). 74s fwupd depends on libglib2.0-0 (>= 2.79.0). 74s bolt depends on libglib2.0-0 (>= 2.56.0). 74s 74s (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 ... 74662 files and directories currently installed.) 74s Removing libglib2.0-0:arm64 (2.79.2-1~ubuntu1) ... 74s Selecting previously unselected package libglib2.0-0t64:arm64. 74s (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 ... 74637 files and directories currently installed.) 74s Preparing to unpack .../00-libglib2.0-0t64_2.79.3-3ubuntu3_arm64.deb ... 74s libglib2.0-0t64.preinst: Removing /var/lib/dpkg/info/libglib2.0-0:arm64.postrm to avoid loss of /usr/share/glib-2.0/schemas/gschemas.compiled... 74s removed '/var/lib/dpkg/info/libglib2.0-0:arm64.postrm' 74s Unpacking libglib2.0-0t64:arm64 (2.79.3-3ubuntu3) ... 74s Preparing to unpack .../01-libglib2.0-data_2.79.3-3ubuntu3_all.deb ... 74s Unpacking libglib2.0-data (2.79.3-3ubuntu3) over (2.79.2-1~ubuntu1) ... 74s Preparing to unpack .../02-ubuntu-minimal_1.535_arm64.deb ... 74s Unpacking ubuntu-minimal (1.535) over (1.534) ... 74s Selecting previously unselected package xdg-user-dirs. 74s Preparing to unpack .../03-xdg-user-dirs_0.18-1_arm64.deb ... 74s Unpacking xdg-user-dirs (0.18-1) ... 74s Selecting previously unselected package libnuma1:arm64. 75s Preparing to unpack .../04-libnuma1_2.0.18-1_arm64.deb ... 75s Unpacking libnuma1:arm64 (2.0.18-1) ... 75s Preparing to unpack .../05-ubuntu-standard_1.535_arm64.deb ... 75s Unpacking ubuntu-standard (1.535) over (1.534) ... 75s Preparing to unpack .../06-efibootmgr_18-1build1_arm64.deb ... 75s Unpacking efibootmgr (18-1build1) over (18-1) ... 75s Selecting previously unselected package libsensors-config. 75s Preparing to unpack .../07-libsensors-config_1%3a3.6.0-9_all.deb ... 75s Unpacking libsensors-config (1:3.6.0-9) ... 75s Selecting previously unselected package libsensors5:arm64. 75s Preparing to unpack .../08-libsensors5_1%3a3.6.0-9_arm64.deb ... 75s Unpacking libsensors5:arm64 (1:3.6.0-9) ... 75s Selecting previously unselected package numactl. 75s Preparing to unpack .../09-numactl_2.0.18-1_arm64.deb ... 75s Unpacking numactl (2.0.18-1) ... 75s Selecting previously unselected package sysstat. 75s Preparing to unpack .../10-sysstat_12.6.1-1ubuntu1_arm64.deb ... 75s Unpacking sysstat (12.6.1-1ubuntu1) ... 75s Setting up efibootmgr (18-1build1) ... 75s Setting up ubuntu-minimal (1.535) ... 75s Setting up xdg-user-dirs (0.18-1) ... 75s Setting up libsensors-config (1:3.6.0-9) ... 75s Setting up ubuntu-standard (1.535) ... 75s Setting up libglib2.0-0t64:arm64 (2.79.3-3ubuntu3) ... 75s No schema files found: doing nothing. 75s Setting up libglib2.0-data (2.79.3-3ubuntu3) ... 75s Setting up gir1.2-glib-2.0:arm64 (2.79.3-3ubuntu3) ... 75s Setting up libsensors5:arm64 (1:3.6.0-9) ... 75s Setting up libnuma1:arm64 (2.0.18-1) ... 75s Setting up sysstat (12.6.1-1ubuntu1) ... 75s 75s Creating config file /etc/default/sysstat with new version 75s update-alternatives: using /usr/bin/sar.sysstat to provide /usr/bin/sar (sar) in auto mode 76s Created symlink /etc/systemd/system/sysstat.service.wants/sysstat-collect.timer → /usr/lib/systemd/system/sysstat-collect.timer. 76s Created symlink /etc/systemd/system/sysstat.service.wants/sysstat-summary.timer → /usr/lib/systemd/system/sysstat-summary.timer. 77s Created symlink /etc/systemd/system/multi-user.target.wants/sysstat.service → /usr/lib/systemd/system/sysstat.service. 78s Setting up numactl (2.0.18-1) ... 78s Processing triggers for man-db (2.12.0-3) ... 79s Processing triggers for libc-bin (2.39-0ubuntu2) ... 80s Reading package lists... 80s Building dependency tree... 80s Reading state information... 80s The following packages will be REMOVED: 80s ubuntu-advantage-tools* 81s 0 upgraded, 0 newly installed, 1 to remove and 0 not upgraded. 81s After this operation, 71.7 kB disk space will be freed. 81s (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 ... 74769 files and directories currently installed.) 81s Removing ubuntu-advantage-tools (31.1) ... 81s (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 ... 74763 files and directories currently installed.) 81s Purging configuration files for ubuntu-advantage-tools (31.1) ... 83s sh: Attempting to set up Debian/Ubuntu apt sources automatically 83s sh: Distribution appears to be Ubuntu 84s Reading package lists... 85s Building dependency tree... 85s Reading state information... 85s eatmydata is already the newest version (131-1). 85s dbus is already the newest version (1.14.10-4ubuntu1). 85s 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 85s Reading package lists... 86s Building dependency tree... 86s Reading state information... 86s rng-tools-debian is already the newest version (2.4). 86s 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 86s Reading package lists... 86s Building dependency tree... 86s Reading state information... 87s haveged is already the newest version (1.9.14-1ubuntu1). 87s 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 87s Reading package lists... 87s Building dependency tree... 87s Reading state information... 88s The following packages will be REMOVED: 88s cloud-init* python3-configobj* python3-debconf* 88s 0 upgraded, 0 newly installed, 3 to remove and 0 not upgraded. 88s After this operation, 3248 kB disk space will be freed. 88s (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 ... 74762 files and directories currently installed.) 88s Removing cloud-init (24.1-0ubuntu1) ... 89s Removing python3-configobj (5.0.8-3) ... 89s Removing python3-debconf (1.5.86) ... 89s Processing triggers for man-db (2.12.0-3) ... 90s (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 ... 74373 files and directories currently installed.) 90s Purging configuration files for cloud-init (24.1-0ubuntu1) ... 90s dpkg: warning: while removing cloud-init, directory '/etc/cloud/cloud.cfg.d' not empty so not removed 90s Processing triggers for rsyslog (8.2312.0-3ubuntu3) ... 91s Reading package lists... 91s Building dependency tree... 91s Reading state information... 92s linux-generic is already the newest version (6.8.0-11.11+1). 92s 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 92s Hit:1 http://ftpmaster.internal/ubuntu noble InRelease 92s Hit:2 http://ftpmaster.internal/ubuntu noble-updates InRelease 92s Hit:3 http://ftpmaster.internal/ubuntu noble-security InRelease 92s Hit:4 http://ftpmaster.internal/ubuntu noble-proposed InRelease 93s Reading package lists... 93s Reading package lists... 94s Building dependency tree... 94s Reading state information... 94s Calculating upgrade... 94s 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 94s Reading package lists... 95s Building dependency tree... 95s Reading state information... 95s 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 95s autopkgtest [16:46:52]: rebooting testbed after setup commands that affected boot 121s autopkgtest [16:47:18]: testbed running kernel: Linux 6.8.0-11-generic #11-Ubuntu SMP PREEMPT_DYNAMIC Wed Feb 14 02:53:31 UTC 2024 122s autopkgtest [16:47:19]: testbed dpkg architecture: arm64 123s autopkgtest [16:47:20]: @@@@@@@@@@@@@@@@@@@@ apt-source libfprint 128s Get:1 http://ftpmaster.internal/ubuntu noble/main libfprint 1:1.94.7+tod1-0ubuntu1 (dsc) [2996 B] 128s Get:2 http://ftpmaster.internal/ubuntu noble/main libfprint 1:1.94.7+tod1-0ubuntu1 (tar) [9280 kB] 128s Get:3 http://ftpmaster.internal/ubuntu noble/main libfprint 1:1.94.7+tod1-0ubuntu1 (diff) [17.2 kB] 128s gpgv: Signature made Tue Feb 20 08:27:36 2024 UTC 128s gpgv: using RSA key D4C501DA48EB797A081750939449C2F50996635F 128s gpgv: Can't check signature: No public key 128s dpkg-source: warning: cannot verify inline signature for ./libfprint_1.94.7+tod1-0ubuntu1.dsc: no acceptable signature found 130s autopkgtest [16:47:27]: testing package libfprint version 1:1.94.7+tod1-0ubuntu1 130s autopkgtest [16:47:27]: build not needed 131s autopkgtest [16:47:28]: test installed-tests: preparing testbed 135s Reading package lists... 136s Building dependency tree... 136s Reading state information... 136s Correcting dependencies...Starting pkgProblemResolver with broken count: 0 136s Starting 2 pkgProblemResolver with broken count: 0 136s Done 136s Done 136s Starting pkgProblemResolver with broken count: 0 137s Starting 2 pkgProblemResolver with broken count: 0 137s Done 137s The following additional packages will be installed: 137s fontconfig-config fonts-dejavu-core fonts-dejavu-mono gir1.2-fprint-2.0 137s gir1.2-gusb-1.0 gir1.2-json-1.0 gnome-desktop-testing libcairo2 137s libfontconfig1 libfprint-2-2 libfprint-2-tests libfprint-2-tod1 137s libpixman-1-0 libumockdev0 libxcb-render0 libxcb-shm0 libxrender1 137s python3-cairo umockdev 137s The following NEW packages will be installed: 137s fontconfig-config fonts-dejavu-core fonts-dejavu-mono gir1.2-fprint-2.0 137s gir1.2-gusb-1.0 gir1.2-json-1.0 gnome-desktop-testing libcairo2 137s libfontconfig1 libfprint-2-2 libfprint-2-tests libfprint-2-tod1 137s libpixman-1-0 libumockdev0 libxcb-render0 libxcb-shm0 libxrender1 137s python3-cairo umockdev 137s 0 upgraded, 19 newly installed, 0 to remove and 0 not upgraded. 137s 1 not fully installed or removed. 137s Need to get 9522 kB of archives. 137s After this operation, 33.8 MB of additional disk space will be used. 137s Get:1 http://ftpmaster.internal/ubuntu noble-proposed/universe arm64 gnome-desktop-testing arm64 2021.1-3build1 [16.0 kB] 137s Get:2 http://ftpmaster.internal/ubuntu noble/main arm64 gir1.2-json-1.0 arm64 1.8.0-2 [8816 B] 137s Get:3 http://ftpmaster.internal/ubuntu noble/main arm64 gir1.2-gusb-1.0 arm64 0.4.8-1 [7454 B] 137s Get:4 http://ftpmaster.internal/ubuntu noble/main arm64 libpixman-1-0 arm64 0.42.2-1 [193 kB] 138s Get:5 http://ftpmaster.internal/ubuntu noble/main arm64 libfprint-2-tod1 arm64 1:1.94.7+tod1-0ubuntu1 [62.3 kB] 138s Get:6 http://ftpmaster.internal/ubuntu noble/main arm64 libfprint-2-2 arm64 1:1.94.7+tod1-0ubuntu1 [262 kB] 138s Get:7 http://ftpmaster.internal/ubuntu noble/main arm64 gir1.2-fprint-2.0 arm64 1:1.94.7+tod1-0ubuntu1 [7220 B] 138s Get:8 http://ftpmaster.internal/ubuntu noble/main arm64 fonts-dejavu-mono all 2.37-8 [502 kB] 138s Get:9 http://ftpmaster.internal/ubuntu noble/main arm64 fonts-dejavu-core all 2.37-8 [835 kB] 138s Get:10 http://ftpmaster.internal/ubuntu noble/main arm64 fontconfig-config arm64 2.15.0-1ubuntu1 [37.0 kB] 138s Get:11 http://ftpmaster.internal/ubuntu noble/main arm64 libfontconfig1 arm64 2.15.0-1ubuntu1 [142 kB] 138s Get:12 http://ftpmaster.internal/ubuntu noble/main arm64 libxcb-render0 arm64 1.15-1 [16.1 kB] 138s Get:13 http://ftpmaster.internal/ubuntu noble/main arm64 libxcb-shm0 arm64 1.15-1 [5780 B] 138s Get:14 http://ftpmaster.internal/ubuntu noble/main arm64 libxrender1 arm64 1:0.9.10-1.1 [19.1 kB] 138s Get:15 http://ftpmaster.internal/ubuntu noble/main arm64 libcairo2 arm64 1.18.0-1 [550 kB] 138s Get:16 http://ftpmaster.internal/ubuntu noble/main arm64 python3-cairo arm64 1.25.1-2 [153 kB] 138s Get:17 http://ftpmaster.internal/ubuntu noble/universe arm64 libumockdev0 arm64 0.17.18-1 [70.4 kB] 138s Get:18 http://ftpmaster.internal/ubuntu noble/universe arm64 umockdev arm64 0.17.18-1 [71.8 kB] 138s Get:19 http://ftpmaster.internal/ubuntu noble/universe arm64 libfprint-2-tests arm64 1:1.94.7+tod1-0ubuntu1 [6563 kB] 139s Fetched 9522 kB in 1s (9260 kB/s) 139s Selecting previously unselected package gnome-desktop-testing. 139s (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 ... 74318 files and directories currently installed.) 139s Preparing to unpack .../00-gnome-desktop-testing_2021.1-3build1_arm64.deb ... 139s Unpacking gnome-desktop-testing (2021.1-3build1) ... 139s Selecting previously unselected package gir1.2-json-1.0:arm64. 139s Preparing to unpack .../01-gir1.2-json-1.0_1.8.0-2_arm64.deb ... 139s Unpacking gir1.2-json-1.0:arm64 (1.8.0-2) ... 139s Selecting previously unselected package gir1.2-gusb-1.0:arm64. 139s Preparing to unpack .../02-gir1.2-gusb-1.0_0.4.8-1_arm64.deb ... 139s Unpacking gir1.2-gusb-1.0:arm64 (0.4.8-1) ... 139s Selecting previously unselected package libpixman-1-0:arm64. 140s Preparing to unpack .../03-libpixman-1-0_0.42.2-1_arm64.deb ... 140s Unpacking libpixman-1-0:arm64 (0.42.2-1) ... 140s Selecting previously unselected package libfprint-2-tod1:arm64. 140s Preparing to unpack .../04-libfprint-2-tod1_1%3a1.94.7+tod1-0ubuntu1_arm64.deb ... 140s Unpacking libfprint-2-tod1:arm64 (1:1.94.7+tod1-0ubuntu1) ... 140s Selecting previously unselected package libfprint-2-2. 140s Preparing to unpack .../05-libfprint-2-2_1%3a1.94.7+tod1-0ubuntu1_arm64.deb ... 140s Unpacking libfprint-2-2 (1:1.94.7+tod1-0ubuntu1) ... 140s Selecting previously unselected package gir1.2-fprint-2.0:arm64. 140s Preparing to unpack .../06-gir1.2-fprint-2.0_1%3a1.94.7+tod1-0ubuntu1_arm64.deb ... 140s Unpacking gir1.2-fprint-2.0:arm64 (1:1.94.7+tod1-0ubuntu1) ... 141s Selecting previously unselected package fonts-dejavu-mono. 141s Preparing to unpack .../07-fonts-dejavu-mono_2.37-8_all.deb ... 141s Unpacking fonts-dejavu-mono (2.37-8) ... 141s Selecting previously unselected package fonts-dejavu-core. 141s Preparing to unpack .../08-fonts-dejavu-core_2.37-8_all.deb ... 141s Unpacking fonts-dejavu-core (2.37-8) ... 141s Selecting previously unselected package fontconfig-config. 141s Preparing to unpack .../09-fontconfig-config_2.15.0-1ubuntu1_arm64.deb ... 141s Unpacking fontconfig-config (2.15.0-1ubuntu1) ... 141s Selecting previously unselected package libfontconfig1:arm64. 141s Preparing to unpack .../10-libfontconfig1_2.15.0-1ubuntu1_arm64.deb ... 141s Unpacking libfontconfig1:arm64 (2.15.0-1ubuntu1) ... 141s Selecting previously unselected package libxcb-render0:arm64. 141s Preparing to unpack .../11-libxcb-render0_1.15-1_arm64.deb ... 141s Unpacking libxcb-render0:arm64 (1.15-1) ... 141s Selecting previously unselected package libxcb-shm0:arm64. 141s Preparing to unpack .../12-libxcb-shm0_1.15-1_arm64.deb ... 141s Unpacking libxcb-shm0:arm64 (1.15-1) ... 141s Selecting previously unselected package libxrender1:arm64. 141s Preparing to unpack .../13-libxrender1_1%3a0.9.10-1.1_arm64.deb ... 141s Unpacking libxrender1:arm64 (1:0.9.10-1.1) ... 141s Selecting previously unselected package libcairo2:arm64. 141s Preparing to unpack .../14-libcairo2_1.18.0-1_arm64.deb ... 141s Unpacking libcairo2:arm64 (1.18.0-1) ... 141s Selecting previously unselected package python3-cairo. 141s Preparing to unpack .../15-python3-cairo_1.25.1-2_arm64.deb ... 141s Unpacking python3-cairo (1.25.1-2) ... 141s Selecting previously unselected package libumockdev0:arm64. 142s Preparing to unpack .../16-libumockdev0_0.17.18-1_arm64.deb ... 142s Unpacking libumockdev0:arm64 (0.17.18-1) ... 142s Selecting previously unselected package umockdev. 142s Preparing to unpack .../17-umockdev_0.17.18-1_arm64.deb ... 142s Unpacking umockdev (0.17.18-1) ... 142s Selecting previously unselected package libfprint-2-tests. 142s Preparing to unpack .../18-libfprint-2-tests_1%3a1.94.7+tod1-0ubuntu1_arm64.deb ... 142s Unpacking libfprint-2-tests (1:1.94.7+tod1-0ubuntu1) ... 142s Setting up gnome-desktop-testing (2021.1-3build1) ... 142s Setting up libpixman-1-0:arm64 (0.42.2-1) ... 142s Setting up libxrender1:arm64 (1:0.9.10-1.1) ... 142s Setting up libxcb-render0:arm64 (1.15-1) ... 142s Setting up libfprint-2-tod1:arm64 (1:1.94.7+tod1-0ubuntu1) ... 142s Setting up libxcb-shm0:arm64 (1.15-1) ... 142s Setting up fonts-dejavu-mono (2.37-8) ... 142s Setting up fonts-dejavu-core (2.37-8) ... 142s Setting up libumockdev0:arm64 (0.17.18-1) ... 142s Setting up gir1.2-json-1.0:arm64 (1.8.0-2) ... 142s Setting up libfprint-2-2 (1:1.94.7+tod1-0ubuntu1) ... 150s Setting up umockdev (0.17.18-1) ... 150s Setting up fontconfig-config (2.15.0-1ubuntu1) ... 150s Setting up gir1.2-gusb-1.0:arm64 (0.4.8-1) ... 150s Setting up libfontconfig1:arm64 (2.15.0-1ubuntu1) ... 150s Setting up gir1.2-fprint-2.0:arm64 (1:1.94.7+tod1-0ubuntu1) ... 150s Setting up libcairo2:arm64 (1.18.0-1) ... 150s Setting up python3-cairo (1.25.1-2) ... 150s Setting up libfprint-2-tests (1:1.94.7+tod1-0ubuntu1) ... 150s Setting up autopkgtest-satdep (0) ... 150s Processing triggers for man-db (2.12.0-3) ... 151s Processing triggers for udev (255.2-3ubuntu2) ... 151s Processing triggers for libc-bin (2.39-0ubuntu2) ... 155s (Reading database ... 74705 files and directories currently installed.) 155s Removing autopkgtest-satdep (0) ... 156s autopkgtest [16:47:53]: test installed-tests: gnome-desktop-testing-runner libfprint-2 156s autopkgtest [16:47:53]: test installed-tests: [----------------------- 156s Running test: libfprint-2/driver-upektc_img-tcs1s.test 156s ** (umockdev-run:2020): DEBUG: 16:47:53.952: umockdev.vala:123: Created udev test bed /tmp/umockdev.EIHZJ2 156s ** (umockdev-run:2020): DEBUG: 16:47:53.991: umockdev.vala:1297: parsing device description for /devices/pci0000:00/0000:00:08.1/0000:05:00.4/usb3/3-2 156s ** (umockdev-run:2020): DEBUG: 16:47:53.994: umockdev.vala:1366: creating device /devices/pci0000:00/0000:00:08.1/0000:05:00.4/usb3/3-2 (subsystem usb) 156s ** (umockdev-run:2020): DEBUG: 16:47:53.997: umockdev.vala:1411: create_node_for_device: creating file device /tmp/umockdev.EIHZJ2/dev/bus/usb/003/004 156s ** (umockdev-run:2020): DEBUG: 16:47:53.997: umockdev.vala:1297: parsing device description for /devices/pci0000:00/0000:00:08.1/0000:05:00.4/usb3 156s ** (umockdev-run:2020): DEBUG: 16:47:54.000: umockdev.vala:1366: creating device /devices/pci0000:00/0000:00:08.1/0000:05:00.4/usb3 (subsystem usb) 156s ** (umockdev-run:2020): DEBUG: 16:47:54.002: umockdev.vala:1411: create_node_for_device: creating file device /tmp/umockdev.EIHZJ2/dev/bus/usb/003/001 156s ** (umockdev-run:2020): DEBUG: 16:47:54.002: umockdev.vala:1297: parsing device description for /devices/pci0000:00/0000:00:08.1/0000:05:00.4 156s ** (umockdev-run:2020): DEBUG: 16:47:54.004: umockdev.vala:1366: creating device /devices/pci0000:00/0000:00:08.1/0000:05:00.4 (subsystem pci) 156s ** (umockdev-run:2020): DEBUG: 16:47:54.006: umockdev.vala:1297: parsing device description for /devices/pci0000:00/0000:00:08.1 156s ** (umockdev-run:2020): DEBUG: 16:47:54.006: umockdev.vala:1366: creating device /devices/pci0000:00/0000:00:08.1 (subsystem pci) 157s (process:2024): libfprint-context-DEBUG: 16:47:54.213: Initializing FpContext (libfprint version 1.94.7+tod1) 157s (process:2024): libfprint-tod-DEBUG: 16:47:54.233: Impossible to load the shared drivers dir Error opening directory “/usr/lib/aarch64-linux-gnu/libfprint-2/tod-1”: No such file or directory 157s (process:2024): libfprint-context-DEBUG: 16:47:54.239: No driver found for USB device 1D6B:0002 157s (process:2024): libfprint-device-DEBUG: 16:47:54.239: Device reported probe completion 157s (process:2024): libfprint-device-DEBUG: 16:47:54.239: Completing action FPI_DEVICE_ACTION_PROBE in idle! 157s (process:2024): libfprint-device-DEBUG: 16:47:54.239: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 157s (process:2024): libfprint-image_device-DEBUG: 16:47:54.243: Image device open completed 157s (process:2024): libfprint-device-DEBUG: 16:47:54.243: Device reported open completion 157s (process:2024): libfprint-device-DEBUG: 16:47:54.243: Completing action FPI_DEVICE_ACTION_OPEN in idle! 157s (process:2024): libfprint-device-DEBUG: 16:47:54.243: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 157s (process:2024): libfprint-device-DEBUG: 16:47:54.243: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 157s (process:2024): libfprint-image_device-DEBUG: 16:47:54.243: Activating image device 157s (process:2024): libfprint-image_device-DEBUG: 16:47:54.243: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING 157s (process:2024): libfprint-SSM-DEBUG: 16:47:54.243: [upektc_img] ACTIVATE_NUM_STATES entering state 0 157s (process:2024): libfprint-SSM-DEBUG: 16:47:54.244: [upektc_img] ACTIVATE_NUM_STATES entering state 1 157s (process:2024): libfprint-SSM-DEBUG: 16:47:54.244: [upektc_img] ACTIVATE_NUM_STATES entering state 2 157s (process:2024): libfprint-SSM-DEBUG: 16:47:54.245: [upektc_img] ACTIVATE_NUM_STATES entering state 3 157s (process:2024): libfprint-SSM-DEBUG: 16:47:54.245: [upektc_img] ACTIVATE_NUM_STATES entering state 4 157s (process:2024): libfprint-SSM-DEBUG: 16:47:54.246: [upektc_img] ACTIVATE_NUM_STATES entering state 5 157s (process:2024): libfprint-SSM-DEBUG: 16:47:54.246: [upektc_img] ACTIVATE_NUM_STATES entering state 6 157s (process:2024): libfprint-SSM-DEBUG: 16:47:54.247: [upektc_img] ACTIVATE_NUM_STATES entering state 7 157s (process:2024): libfprint-SSM-DEBUG: 16:47:54.247: [upektc_img] ACTIVATE_NUM_STATES entering state 8 157s (process:2024): libfprint-SSM-DEBUG: 16:47:54.248: [upektc_img] ACTIVATE_NUM_STATES entering state 9 157s (process:2024): libfprint-SSM-DEBUG: 16:47:54.248: [upektc_img] ACTIVATE_NUM_STATES entering state 10 157s (process:2024): libfprint-SSM-DEBUG: 16:47:54.249: [upektc_img] ACTIVATE_NUM_STATES entering state 11 157s (process:2024): libfprint-upektc_img-DEBUG: 16:47:54.249: Sensor type : TCS1x, width x height: 256 x 360 157s (process:2024): libfprint-SSM-DEBUG: 16:47:54.249: [upektc_img] ACTIVATE_NUM_STATES completed successfully 157s (process:2024): libfprint-image_device-DEBUG: 16:47:54.249: Image device activation completed 157s (process:2024): libfprint-image_device-DEBUG: 16:47:54.249: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE 157s (process:2024): libfprint-image_device-DEBUG: 16:47:54.249: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 157s (process:2024): libfprint-device-DEBUG: 16:47:54.249: Device reported finger status change: FP_FINGER_STATUS_NEEDED 157s (process:2024): libfprint-SSM-DEBUG: 16:47:54.249: [upektc_img] CAPTURE_NUM_STATES entering state 0 157s (process:2024): libfprint-SSM-DEBUG: 16:47:54.250: [upektc_img] CAPTURE_NUM_STATES entering state 1 157s (process:2024): libfprint-upektc_img-DEBUG: 16:47:54.250: request completed, len: 0000 157s (process:2024): libfprint-SSM-DEBUG: 16:47:54.250: [upektc_img] CAPTURE_NUM_STATES entering state 1 157s (process:2024): libfprint-upektc_img-DEBUG: 16:47:54.251: request completed, len: 0040 157s (process:2024): libfprint-upektc_img-DEBUG: 16:47:54.251: 18th byte is 0c 157s (process:2024): libfprint-SSM-DEBUG: 16:47:54.251: [upektc_img] CAPTURE_NUM_STATES entering state 3 157s (process:2024): libfprint-SSM-DEBUG: 16:47:54.251: [upektc_img] CAPTURE_NUM_STATES entering state 1 157s (process:2024): libfprint-upektc_img-DEBUG: 16:47:54.251: request completed, len: 0000 157s (process:2024): libfprint-SSM-DEBUG: 16:47:54.251: [upektc_img] CAPTURE_NUM_STATES entering state 1 157s (process:2024): libfprint-upektc_img-DEBUG: 16:47:54.252: request completed, len: 0040 157s (process:2024): libfprint-upektc_img-DEBUG: 16:47:54.252: 18th byte is 13 157s (process:2024): libfprint-SSM-DEBUG: 16:47:54.252: [upektc_img] CAPTURE_NUM_STATES entering state 3 157s (process:2024): libfprint-SSM-DEBUG: 16:47:54.252: [upektc_img] CAPTURE_NUM_STATES entering state 1 157s (process:2024): libfprint-upektc_img-DEBUG: 16:47:54.253: request completed, len: 0000 157s (process:2024): libfprint-SSM-DEBUG: 16:47:54.253: [upektc_img] CAPTURE_NUM_STATES entering state 1 157s (process:2024): libfprint-upektc_img-DEBUG: 16:47:54.253: request completed, len: 0040 157s (process:2024): libfprint-upektc_img-DEBUG: 16:47:54.253: 18th byte is 00 157s (process:2024): libfprint-device-DEBUG: 16:47:54.253: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 157s (process:2024): libfprint-SSM-DEBUG: 16:47:54.253: [upektc_img] CAPTURE_NUM_STATES entering state 3 157s (process:2024): libfprint-SSM-DEBUG: 16:47:54.254: [upektc_img] CAPTURE_NUM_STATES entering state 1 157s (process:2024): libfprint-upektc_img-DEBUG: 16:47:54.254: request completed, len: 0000 157s (process:2024): libfprint-SSM-DEBUG: 16:47:54.254: [upektc_img] CAPTURE_NUM_STATES entering state 1 157s (process:2024): libfprint-upektc_img-DEBUG: 16:47:54.254: request completed, len: 0040 157s (process:2024): libfprint-upektc_img-DEBUG: 16:47:54.254: response_size is 2052, actual_length is 64 157s (process:2024): libfprint-upektc_img-DEBUG: 16:47:54.254: Waiting for rest of transfer 157s (process:2024): libfprint-SSM-DEBUG: 16:47:54.254: [upektc_img] CAPTURE_NUM_STATES entering state 1 157s (process:2024): libfprint-upektc_img-DEBUG: 16:47:54.255: request completed, len: 07c4 157s (process:2024): libfprint-image_device-DEBUG: 16:47:54.255: Image device reported finger status: on 157s (process:2024): libfprint-image_device-DEBUG: 16:47:54.255: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 157s (process:2024): libfprint-SSM-DEBUG: 16:47:54.255: [upektc_img] CAPTURE_NUM_STATES entering state 5 157s (process:2024): libfprint-SSM-DEBUG: 16:47:54.256: [upektc_img] CAPTURE_NUM_STATES entering state 1 157s (process:2024): libfprint-upektc_img-DEBUG: 16:47:54.256: request completed, len: 0040 157s (process:2024): libfprint-upektc_img-DEBUG: 16:47:54.256: response_size is 2052, actual_length is 64 157s (process:2024): libfprint-upektc_img-DEBUG: 16:47:54.256: Waiting for rest of transfer 157s (process:2024): libfprint-SSM-DEBUG: 16:47:54.256: [upektc_img] CAPTURE_NUM_STATES entering state 1 157s (process:2024): libfprint-upektc_img-DEBUG: 16:47:54.256: request completed, len: 07c4 157s (process:2024): libfprint-SSM-DEBUG: 16:47:54.256: [upektc_img] CAPTURE_NUM_STATES entering state 5 157s (process:2024): libfprint-SSM-DEBUG: 16:47:54.257: [upektc_img] CAPTURE_NUM_STATES entering state 1 157s (process:2024): libfprint-upektc_img-DEBUG: 16:47:54.257: request completed, len: 0040 157s (process:2024): libfprint-upektc_img-DEBUG: 16:47:54.257: response_size is 2052, actual_length is 64 157s (process:2024): libfprint-upektc_img-DEBUG: 16:47:54.257: Waiting for rest of transfer 157s (process:2024): libfprint-SSM-DEBUG: 16:47:54.257: [upektc_img] CAPTURE_NUM_STATES entering state 1 157s (process:2024): libfprint-upektc_img-DEBUG: 16:47:54.258: request completed, len: 07c4 157s (process:2024): libfprint-SSM-DEBUG: 16:47:54.258: [upektc_img] CAPTURE_NUM_STATES entering state 5 157s (process:2024): libfprint-SSM-DEBUG: 16:47:54.258: [upektc_img] CAPTURE_NUM_STATES entering state 1 157s (process:2024): libfprint-upektc_img-DEBUG: 16:47:54.259: request completed, len: 0040 157s (process:2024): libfprint-upektc_img-DEBUG: 16:47:54.259: response_size is 2052, actual_length is 64 157s (process:2024): libfprint-upektc_img-DEBUG: 16:47:54.259: Waiting for rest of transfer 157s (process:2024): libfprint-SSM-DEBUG: 16:47:54.259: [upektc_img] CAPTURE_NUM_STATES entering state 1 157s (process:2024): libfprint-upektc_img-DEBUG: 16:47:54.259: request completed, len: 07c4 157s (process:2024): libfprint-SSM-DEBUG: 16:47:54.259: [upektc_img] CAPTURE_NUM_STATES entering state 5 157s (process:2024): libfprint-SSM-DEBUG: 16:47:54.259: [upektc_img] CAPTURE_NUM_STATES entering state 1 157s (process:2024): libfprint-upektc_img-DEBUG: 16:47:54.260: request completed, len: 0040 157s (process:2024): libfprint-upektc_img-DEBUG: 16:47:54.260: response_size is 2052, actual_length is 64 157s (process:2024): libfprint-upektc_img-DEBUG: 16:47:54.260: Waiting for rest of transfer 157s (process:2024): libfprint-SSM-DEBUG: 16:47:54.260: [upektc_img] CAPTURE_NUM_STATES entering state 1 157s (process:2024): libfprint-upektc_img-DEBUG: 16:47:54.260: request completed, len: 07c4 157s (process:2024): libfprint-SSM-DEBUG: 16:47:54.260: [upektc_img] CAPTURE_NUM_STATES entering state 5 157s (process:2024): libfprint-SSM-DEBUG: 16:47:54.261: [upektc_img] CAPTURE_NUM_STATES entering state 1 157s (process:2024): libfprint-upektc_img-DEBUG: 16:47:54.261: request completed, len: 0040 157s (process:2024): libfprint-upektc_img-DEBUG: 16:47:54.261: response_size is 2052, actual_length is 64 157s (process:2024): libfprint-upektc_img-DEBUG: 16:47:54.261: Waiting for rest of transfer 157s (process:2024): libfprint-SSM-DEBUG: 16:47:54.261: [upektc_img] CAPTURE_NUM_STATES entering state 1 157s (process:2024): libfprint-upektc_img-DEBUG: 16:47:54.261: request completed, len: 07c4 157s (process:2024): libfprint-SSM-DEBUG: 16:47:54.262: [upektc_img] CAPTURE_NUM_STATES entering state 5 157s (process:2024): libfprint-SSM-DEBUG: 16:47:54.262: [upektc_img] CAPTURE_NUM_STATES entering state 1 157s (process:2024): libfprint-upektc_img-DEBUG: 16:47:54.262: request completed, len: 0040 157s (process:2024): libfprint-upektc_img-DEBUG: 16:47:54.262: response_size is 2052, actual_length is 64 157s (process:2024): libfprint-upektc_img-DEBUG: 16:47:54.262: Waiting for rest of transfer 157s (process:2024): libfprint-SSM-DEBUG: 16:47:54.262: [upektc_img] CAPTURE_NUM_STATES entering state 1 157s (process:2024): libfprint-upektc_img-DEBUG: 16:47:54.263: request completed, len: 07c4 157s (process:2024): libfprint-SSM-DEBUG: 16:47:54.263: [upektc_img] CAPTURE_NUM_STATES entering state 5 157s (process:2024): libfprint-SSM-DEBUG: 16:47:54.263: [upektc_img] CAPTURE_NUM_STATES entering state 1 157s (process:2024): libfprint-upektc_img-DEBUG: 16:47:54.264: request completed, len: 0040 157s (process:2024): libfprint-upektc_img-DEBUG: 16:47:54.264: response_size is 2052, actual_length is 64 157s (process:2024): libfprint-upektc_img-DEBUG: 16:47:54.264: Waiting for rest of transfer 157s (process:2024): libfprint-SSM-DEBUG: 16:47:54.264: [upektc_img] CAPTURE_NUM_STATES entering state 1 157s (process:2024): libfprint-upektc_img-DEBUG: 16:47:54.264: request completed, len: 07c4 157s (process:2024): libfprint-SSM-DEBUG: 16:47:54.264: [upektc_img] CAPTURE_NUM_STATES entering state 5 157s (process:2024): libfprint-SSM-DEBUG: 16:47:54.265: [upektc_img] CAPTURE_NUM_STATES entering state 1 157s (process:2024): libfprint-upektc_img-DEBUG: 16:47:54.265: request completed, len: 0040 157s (process:2024): libfprint-upektc_img-DEBUG: 16:47:54.265: response_size is 2052, actual_length is 64 157s (process:2024): libfprint-upektc_img-DEBUG: 16:47:54.265: Waiting for rest of transfer 157s (process:2024): libfprint-SSM-DEBUG: 16:47:54.265: [upektc_img] CAPTURE_NUM_STATES entering state 1 157s (process:2024): libfprint-upektc_img-DEBUG: 16:47:54.265: request completed, len: 07c4 157s (process:2024): libfprint-SSM-DEBUG: 16:47:54.265: [upektc_img] CAPTURE_NUM_STATES entering state 5 157s (process:2024): libfprint-SSM-DEBUG: 16:47:54.266: [upektc_img] CAPTURE_NUM_STATES entering state 1 157s (process:2024): libfprint-upektc_img-DEBUG: 16:47:54.266: request completed, len: 0040 157s (process:2024): libfprint-upektc_img-DEBUG: 16:47:54.266: response_size is 2052, actual_length is 64 157s (process:2024): libfprint-upektc_img-DEBUG: 16:47:54.266: Waiting for rest of transfer 157s (process:2024): libfprint-SSM-DEBUG: 16:47:54.266: [upektc_img] CAPTURE_NUM_STATES entering state 1 157s (process:2024): libfprint-upektc_img-DEBUG: 16:47:54.267: request completed, len: 07c4 157s (process:2024): libfprint-SSM-DEBUG: 16:47:54.267: [upektc_img] CAPTURE_NUM_STATES entering state 5 157s (process:2024): libfprint-SSM-DEBUG: 16:47:54.267: [upektc_img] CAPTURE_NUM_STATES entering state 1 157s (process:2024): libfprint-upektc_img-DEBUG: 16:47:54.268: request completed, len: 0040 157s (process:2024): libfprint-upektc_img-DEBUG: 16:47:54.268: response_size is 2052, actual_length is 64 157s (process:2024): libfprint-upektc_img-DEBUG: 16:47:54.268: Waiting for rest of transfer 157s (process:2024): libfprint-SSM-DEBUG: 16:47:54.268: [upektc_img] CAPTURE_NUM_STATES entering state 1 157s (process:2024): libfprint-upektc_img-DEBUG: 16:47:54.268: request completed, len: 07c4 157s (process:2024): libfprint-SSM-DEBUG: 16:47:54.268: [upektc_img] CAPTURE_NUM_STATES entering state 5 157s (process:2024): libfprint-SSM-DEBUG: 16:47:54.268: [upektc_img] CAPTURE_NUM_STATES entering state 1 157s (process:2024): libfprint-upektc_img-DEBUG: 16:47:54.269: request completed, len: 0040 157s (process:2024): libfprint-upektc_img-DEBUG: 16:47:54.269: response_size is 2052, actual_length is 64 157s (process:2024): libfprint-upektc_img-DEBUG: 16:47:54.269: Waiting for rest of transfer 157s (process:2024): libfprint-SSM-DEBUG: 16:47:54.269: [upektc_img] CAPTURE_NUM_STATES entering state 1 157s (process:2024): libfprint-upektc_img-DEBUG: 16:47:54.269: request completed, len: 07c4 157s (process:2024): libfprint-SSM-DEBUG: 16:47:54.269: [upektc_img] CAPTURE_NUM_STATES entering state 5 157s (process:2024): libfprint-SSM-DEBUG: 16:47:54.270: [upektc_img] CAPTURE_NUM_STATES entering state 1 157s (process:2024): libfprint-upektc_img-DEBUG: 16:47:54.270: request completed, len: 0040 157s (process:2024): libfprint-upektc_img-DEBUG: 16:47:54.270: response_size is 2052, actual_length is 64 157s (process:2024): libfprint-upektc_img-DEBUG: 16:47:54.270: Waiting for rest of transfer 157s (process:2024): libfprint-SSM-DEBUG: 16:47:54.270: [upektc_img] CAPTURE_NUM_STATES entering state 1 157s (process:2024): libfprint-upektc_img-DEBUG: 16:47:54.271: request completed, len: 07c4 157s (process:2024): libfprint-SSM-DEBUG: 16:47:54.271: [upektc_img] CAPTURE_NUM_STATES entering state 5 157s (process:2024): libfprint-SSM-DEBUG: 16:47:54.271: [upektc_img] CAPTURE_NUM_STATES entering state 1 157s (process:2024): libfprint-upektc_img-DEBUG: 16:47:54.271: request completed, len: 0040 157s (process:2024): libfprint-upektc_img-DEBUG: 16:47:54.271: response_size is 2052, actual_length is 64 157s (process:2024): libfprint-upektc_img-DEBUG: 16:47:54.271: Waiting for rest of transfer 157s (process:2024): libfprint-SSM-DEBUG: 16:47:54.271: [upektc_img] CAPTURE_NUM_STATES entering state 1 157s (process:2024): libfprint-upektc_img-DEBUG: 16:47:54.272: request completed, len: 07c4 157s (process:2024): libfprint-SSM-DEBUG: 16:47:54.272: [upektc_img] CAPTURE_NUM_STATES entering state 5 157s (process:2024): libfprint-SSM-DEBUG: 16:47:54.272: [upektc_img] CAPTURE_NUM_STATES entering state 1 157s (process:2024): libfprint-upektc_img-DEBUG: 16:47:54.273: request completed, len: 0040 157s (process:2024): libfprint-upektc_img-DEBUG: 16:47:54.273: response_size is 2052, actual_length is 64 157s (process:2024): libfprint-upektc_img-DEBUG: 16:47:54.273: Waiting for rest of transfer 157s (process:2024): libfprint-SSM-DEBUG: 16:47:54.273: [upektc_img] CAPTURE_NUM_STATES entering state 1 157s (process:2024): libfprint-upektc_img-DEBUG: 16:47:54.273: request completed, len: 07c4 157s (process:2024): libfprint-SSM-DEBUG: 16:47:54.273: [upektc_img] CAPTURE_NUM_STATES entering state 5 157s (process:2024): libfprint-SSM-DEBUG: 16:47:54.274: [upektc_img] CAPTURE_NUM_STATES entering state 1 157s (process:2024): libfprint-upektc_img-DEBUG: 16:47:54.274: request completed, len: 0040 157s (process:2024): libfprint-upektc_img-DEBUG: 16:47:54.274: response_size is 2052, actual_length is 64 157s (process:2024): libfprint-upektc_img-DEBUG: 16:47:54.274: Waiting for rest of transfer 157s (process:2024): libfprint-SSM-DEBUG: 16:47:54.274: [upektc_img] CAPTURE_NUM_STATES entering state 1 157s (process:2024): libfprint-upektc_img-DEBUG: 16:47:54.274: request completed, len: 07c4 157s (process:2024): libfprint-SSM-DEBUG: 16:47:54.275: [upektc_img] CAPTURE_NUM_STATES entering state 5 157s (process:2024): libfprint-SSM-DEBUG: 16:47:54.275: [upektc_img] CAPTURE_NUM_STATES entering state 1 157s (process:2024): libfprint-upektc_img-DEBUG: 16:47:54.275: request completed, len: 0040 157s (process:2024): libfprint-upektc_img-DEBUG: 16:47:54.275: response_size is 2052, actual_length is 64 157s (process:2024): libfprint-upektc_img-DEBUG: 16:47:54.275: Waiting for rest of transfer 157s (process:2024): libfprint-SSM-DEBUG: 16:47:54.275: [upektc_img] CAPTURE_NUM_STATES entering state 1 157s (process:2024): libfprint-upektc_img-DEBUG: 16:47:54.276: request completed, len: 07c4 157s (process:2024): libfprint-SSM-DEBUG: 16:47:54.276: [upektc_img] CAPTURE_NUM_STATES entering state 5 157s (process:2024): libfprint-SSM-DEBUG: 16:47:54.276: [upektc_img] CAPTURE_NUM_STATES entering state 1 157s (process:2024): libfprint-upektc_img-DEBUG: 16:47:54.277: request completed, len: 0040 157s (process:2024): libfprint-upektc_img-DEBUG: 16:47:54.277: response_size is 2052, actual_length is 64 157s (process:2024): libfprint-upektc_img-DEBUG: 16:47:54.277: Waiting for rest of transfer 157s (process:2024): libfprint-SSM-DEBUG: 16:47:54.277: [upektc_img] CAPTURE_NUM_STATES entering state 1 157s (process:2024): libfprint-upektc_img-DEBUG: 16:47:54.277: request completed, len: 07c4 157s (process:2024): libfprint-SSM-DEBUG: 16:47:54.277: [upektc_img] CAPTURE_NUM_STATES entering state 5 157s (process:2024): libfprint-SSM-DEBUG: 16:47:54.278: [upektc_img] CAPTURE_NUM_STATES entering state 1 157s (process:2024): libfprint-upektc_img-DEBUG: 16:47:54.278: request completed, len: 0040 157s (process:2024): libfprint-upektc_img-DEBUG: 16:47:54.278: response_size is 2052, actual_length is 64 157s (process:2024): libfprint-upektc_img-DEBUG: 16:47:54.278: Waiting for rest of transfer 157s (process:2024): libfprint-SSM-DEBUG: 16:47:54.278: [upektc_img] CAPTURE_NUM_STATES entering state 1 157s (process:2024): libfprint-upektc_img-DEBUG: 16:47:54.279: request completed, len: 07c4 157s (process:2024): libfprint-SSM-DEBUG: 16:47:54.279: [upektc_img] CAPTURE_NUM_STATES entering state 5 157s (process:2024): libfprint-SSM-DEBUG: 16:47:54.279: [upektc_img] CAPTURE_NUM_STATES entering state 1 157s (process:2024): libfprint-upektc_img-DEBUG: 16:47:54.279: request completed, len: 0040 157s (process:2024): libfprint-upektc_img-DEBUG: 16:47:54.279: response_size is 2052, actual_length is 64 157s (process:2024): libfprint-upektc_img-DEBUG: 16:47:54.279: Waiting for rest of transfer 157s (process:2024): libfprint-SSM-DEBUG: 16:47:54.279: [upektc_img] CAPTURE_NUM_STATES entering state 1 157s (process:2024): libfprint-upektc_img-DEBUG: 16:47:54.280: request completed, len: 07c4 157s (process:2024): libfprint-SSM-DEBUG: 16:47:54.280: [upektc_img] CAPTURE_NUM_STATES entering state 5 157s (process:2024): libfprint-SSM-DEBUG: 16:47:54.280: [upektc_img] CAPTURE_NUM_STATES entering state 1 157s (process:2024): libfprint-upektc_img-DEBUG: 16:47:54.281: request completed, len: 0040 157s (process:2024): libfprint-upektc_img-DEBUG: 16:47:54.281: response_size is 2052, actual_length is 64 157s (process:2024): libfprint-upektc_img-DEBUG: 16:47:54.281: Waiting for rest of transfer 157s (process:2024): libfprint-SSM-DEBUG: 16:47:54.281: [upektc_img] CAPTURE_NUM_STATES entering state 1 157s (process:2024): libfprint-upektc_img-DEBUG: 16:47:54.281: request completed, len: 07c4 157s (process:2024): libfprint-SSM-DEBUG: 16:47:54.281: [upektc_img] CAPTURE_NUM_STATES entering state 5 157s (process:2024): libfprint-SSM-DEBUG: 16:47:54.282: [upektc_img] CAPTURE_NUM_STATES entering state 1 157s (process:2024): libfprint-upektc_img-DEBUG: 16:47:54.282: request completed, len: 0040 157s (process:2024): libfprint-upektc_img-DEBUG: 16:47:54.282: response_size is 2052, actual_length is 64 157s (process:2024): libfprint-upektc_img-DEBUG: 16:47:54.282: Waiting for rest of transfer 157s (process:2024): libfprint-SSM-DEBUG: 16:47:54.282: [upektc_img] CAPTURE_NUM_STATES entering state 1 157s (process:2024): libfprint-upektc_img-DEBUG: 16:47:54.282: request completed, len: 07c4 157s (process:2024): libfprint-SSM-DEBUG: 16:47:54.282: [upektc_img] CAPTURE_NUM_STATES entering state 5 157s (process:2024): libfprint-SSM-DEBUG: 16:47:54.283: [upektc_img] CAPTURE_NUM_STATES entering state 1 157s (process:2024): libfprint-upektc_img-DEBUG: 16:47:54.283: request completed, len: 0040 157s (process:2024): libfprint-upektc_img-DEBUG: 16:47:54.283: response_size is 2052, actual_length is 64 157s (process:2024): libfprint-upektc_img-DEBUG: 16:47:54.283: Waiting for rest of transfer 157s (process:2024): libfprint-SSM-DEBUG: 16:47:54.283: [upektc_img] CAPTURE_NUM_STATES entering state 1 157s (process:2024): libfprint-upektc_img-DEBUG: 16:47:54.284: request completed, len: 07c4 157s (process:2024): libfprint-SSM-DEBUG: 16:47:54.284: [upektc_img] CAPTURE_NUM_STATES entering state 5 157s (process:2024): libfprint-SSM-DEBUG: 16:47:54.284: [upektc_img] CAPTURE_NUM_STATES entering state 1 157s (process:2024): libfprint-upektc_img-DEBUG: 16:47:54.285: request completed, len: 0040 157s (process:2024): libfprint-upektc_img-DEBUG: 16:47:54.285: response_size is 2052, actual_length is 64 157s (process:2024): libfprint-upektc_img-DEBUG: 16:47:54.285: Waiting for rest of transfer 157s (process:2024): libfprint-SSM-DEBUG: 16:47:54.285: [upektc_img] CAPTURE_NUM_STATES entering state 1 157s (process:2024): libfprint-upektc_img-DEBUG: 16:47:54.285: request completed, len: 07c4 157s (process:2024): libfprint-SSM-DEBUG: 16:47:54.285: [upektc_img] CAPTURE_NUM_STATES entering state 5 157s (process:2024): libfprint-SSM-DEBUG: 16:47:54.285: [upektc_img] CAPTURE_NUM_STATES entering state 1 157s (process:2024): libfprint-upektc_img-DEBUG: 16:47:54.286: request completed, len: 0040 157s (process:2024): libfprint-upektc_img-DEBUG: 16:47:54.286: response_size is 2052, actual_length is 64 157s (process:2024): libfprint-upektc_img-DEBUG: 16:47:54.286: Waiting for rest of transfer 157s (process:2024): libfprint-SSM-DEBUG: 16:47:54.286: [upektc_img] CAPTURE_NUM_STATES entering state 1 157s (process:2024): libfprint-upektc_img-DEBUG: 16:47:54.286: request completed, len: 07c4 157s (process:2024): libfprint-SSM-DEBUG: 16:47:54.286: [upektc_img] CAPTURE_NUM_STATES entering state 5 157s (process:2024): libfprint-SSM-DEBUG: 16:47:54.287: [upektc_img] CAPTURE_NUM_STATES entering state 1 157s (process:2024): libfprint-upektc_img-DEBUG: 16:47:54.287: request completed, len: 0040 157s (process:2024): libfprint-upektc_img-DEBUG: 16:47:54.287: response_size is 814, actual_length is 64 157s (process:2024): libfprint-upektc_img-DEBUG: 16:47:54.287: Waiting for rest of transfer 157s (process:2024): libfprint-SSM-DEBUG: 16:47:54.287: [upektc_img] CAPTURE_NUM_STATES entering state 1 157s (process:2024): libfprint-upektc_img-DEBUG: 16:47:54.288: request completed, len: 02ee 157s (process:2024): libfprint-upektc_img-DEBUG: 16:47:54.288: Image size is 51840 157s (process:2024): libfprint-image_device-DEBUG: 16:47:54.288: Image device captured an image 157s (process:2024): libfprint-image_device-DEBUG: 16:47:54.291: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 157s (process:2024): libfprint-device-DEBUG: 16:47:54.291: Device reported finger status change: FP_FINGER_STATUS_PRESENT 157s (process:2024): libfprint-device-DEBUG: 16:47:54.291: Device reported finger status change: FP_FINGER_STATUS_NONE 157s (process:2024): libfprint-image_device-DEBUG: 16:47:54.291: Image device reported finger status: off 157s (process:2024): libfprint-image_device-DEBUG: 16:47:54.291: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 157s (process:2024): libfprint-image_device-DEBUG: 16:47:54.291: Deactivating image device 157s (process:2024): libfprint-image_device-DEBUG: 16:47:54.291: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_DEACTIVATING 157s (process:2024): libfprint-SSM-DEBUG: 16:47:54.291: [upektc_img] CAPTURE_NUM_STATES completed successfully 157s (process:2024): libfprint-SSM-DEBUG: 16:47:54.291: [upektc_img] DEACTIVATE_NUM_STATES entering state 0 157s (process:2024): libfprint-SSM-DEBUG: 16:47:54.291: [upektc_img] DEACTIVATE_NUM_STATES entering state 1 157s (process:2024): libfprint-SSM-DEBUG: 16:47:54.292: [upektc_img] DEACTIVATE_NUM_STATES completed successfully 157s (process:2024): libfprint-upektc_img-DEBUG: 16:47:54.292: Deactivate completed 157s (process:2024): libfprint-image_device-DEBUG: 16:47:54.292: Image device deactivation completed 157s (process:2024): libfprint-image_device-DEBUG: 16:47:54.292: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE 157s (process:2024): libfprint-image-DEBUG: 16:47:54.308: Minutiae scan completed in 0.019992 secs 157s (process:2024): libfprint-device-DEBUG: 16:47:54.308: Device reported capture completion 157s (process:2024): libfprint-device-DEBUG: 16:47:54.308: Completing action FPI_DEVICE_ACTION_CAPTURE in idle! 157s (process:2024): libfprint-device-DEBUG: 16:47:54.308: Updated temperature model after 0.07 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 157s (process:2024): libfprint-image_device-DEBUG: 16:47:54.309: Image device close completed 157s (process:2024): libfprint-device-DEBUG: 16:47:54.309: Device reported close completion 157s (process:2024): libfprint-device-DEBUG: 16:47:54.309: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 157s (process:2024): libfprint-device-DEBUG: 16:47:54.309: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 157s ** (umockdev-run:2020): DEBUG: 16:47:54.532: umockdev.vala:150: Removing test bed /tmp/umockdev.EIHZJ2 157s (umockdev-run:2020): GLib-DEBUG: 16:47:54.536: unsetenv() is not thread-safe and should not be used after threads are created 157s Comparing PNGs /tmp/libfprint-umockdev-test-61l1z10d/capture.png and /usr/share/installed-tests/libfprint-2/upektc_img-tcs1s/capture.png 157s PASS: libfprint-2/driver-upektc_img-tcs1s.test 157s Running test: libfprint-2/driver-vfs301.test 157s ** (umockdev-run:2033): DEBUG: 16:47:54.617: umockdev.vala:123: Created udev test bed /tmp/umockdev.MAB4J2 157s ** (umockdev-run:2033): DEBUG: 16:47:54.617: umockdev.vala:1297: parsing device description for /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.3 157s ** (umockdev-run:2033): DEBUG: 16:47:54.619: umockdev.vala:1366: creating device /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.3 (subsystem usb) 157s ** (umockdev-run:2033): DEBUG: 16:47:54.621: umockdev.vala:1411: create_node_for_device: creating file device /tmp/umockdev.MAB4J2/dev/bus/usb/002/005 157s ** (umockdev-run:2033): DEBUG: 16:47:54.621: umockdev.vala:1297: parsing device description for /devices/pci0000:00/0000:00:1d.0/usb2/2-1 157s ** (umockdev-run:2033): DEBUG: 16:47:54.622: umockdev.vala:1366: creating device /devices/pci0000:00/0000:00:1d.0/usb2/2-1 (subsystem usb) 157s ** (umockdev-run:2033): DEBUG: 16:47:54.624: umockdev.vala:1411: create_node_for_device: creating file device /tmp/umockdev.MAB4J2/dev/bus/usb/002/002 157s ** (umockdev-run:2033): DEBUG: 16:47:54.624: umockdev.vala:1297: parsing device description for /devices/pci0000:00/0000:00:1d.0/usb2 157s ** (umockdev-run:2033): DEBUG: 16:47:54.625: umockdev.vala:1366: creating device /devices/pci0000:00/0000:00:1d.0/usb2 (subsystem usb) 157s ** (umockdev-run:2033): DEBUG: 16:47:54.626: umockdev.vala:1411: create_node_for_device: creating file device /tmp/umockdev.MAB4J2/dev/bus/usb/002/001 157s ** (umockdev-run:2033): DEBUG: 16:47:54.626: umockdev.vala:1297: parsing device description for /devices/pci0000:00/0000:00:1d.0 157s ** (umockdev-run:2033): DEBUG: 16:47:54.627: umockdev.vala:1366: creating device /devices/pci0000:00/0000:00:1d.0 (subsystem pci) 157s (umockdev-run:2033): GLib-GIO-DEBUG: 16:47:54.629: _g_io_module_get_default: Found default implementation local (GLocalVfs) for ?gio-vfs? 157s (process:2037): libfprint-context-DEBUG: 16:47:54.718: Initializing FpContext (libfprint version 1.94.7+tod1) 157s (process:2037): libfprint-tod-DEBUG: 16:47:54.718: Impossible to load the shared drivers dir Error opening directory “/usr/lib/aarch64-linux-gnu/libfprint-2/tod-1”: No such file or directory 157s (process:2037): libfprint-context-DEBUG: 16:47:54.721: No driver found for USB device 8087:0020 157s (process:2037): libfprint-context-DEBUG: 16:47:54.721: No driver found for USB device 1D6B:0002 157s (process:2037): libfprint-device-DEBUG: 16:47:54.721: Device reported probe completion 157s (process:2037): libfprint-device-DEBUG: 16:47:54.721: Completing action FPI_DEVICE_ACTION_PROBE in idle! 157s (process:2037): libfprint-device-DEBUG: 16:47:54.721: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 157s (process:2037): libfprint-image_device-DEBUG: 16:47:54.725: Image device open completed 157s (process:2037): libfprint-device-DEBUG: 16:47:54.725: Device reported open completion 157s (process:2037): libfprint-device-DEBUG: 16:47:54.725: Completing action FPI_DEVICE_ACTION_OPEN in idle! 157s (process:2037): libfprint-device-DEBUG: 16:47:54.725: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 157s (process:2037): libfprint-device-DEBUG: 16:47:54.726: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 157s (process:2037): libfprint-image_device-DEBUG: 16:47:54.726: Activating image device 157s (process:2037): libfprint-image_device-DEBUG: 16:47:54.726: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING 157s (process:2037): libfprint-SSM-DEBUG: 16:47:54.726: [vfs301] 1 entering state 0 157s (process:2037): libfprint-SSM-DEBUG: 16:47:54.762: [vfs301] 1 completed successfully 157s (process:2037): libfprint-image_device-DEBUG: 16:47:54.763: Image device activation completed 157s (process:2037): libfprint-image_device-DEBUG: 16:47:54.763: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE 157s (process:2037): libfprint-image_device-DEBUG: 16:47:54.763: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 157s (process:2037): libfprint-SSM-DEBUG: 16:47:54.763: [vfs301] M_LOOP_NUM_STATES entering state 0 157s (process:2037): libfprint-SSM-DEBUG: 16:47:54.764: [vfs301] M_LOOP_NUM_STATES entering state 1 157s (process:2037): libfprint-device-DEBUG: 16:47:54.764: Device reported finger status change: FP_FINGER_STATUS_NEEDED 157s (process:2037): libfprint-device-DEBUG: 16:47:54.826: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 157s (process:2037): libfprint-SSM-DEBUG: 16:47:54.964: [vfs301] M_LOOP_NUM_STATES entering state 2 157s (process:2037): libfprint-SSM-DEBUG: 16:47:54.965: [vfs301] M_LOOP_NUM_STATES entering state 1 158s (process:2037): libfprint-SSM-DEBUG: 16:47:55.166: [vfs301] M_LOOP_NUM_STATES entering state 2 158s (process:2037): libfprint-SSM-DEBUG: 16:47:55.166: [vfs301] M_LOOP_NUM_STATES entering state 3 158s (process:2037): libfprint-device-DEBUG: 16:47:55.166: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 158s (process:2037): libfprint-image_device-DEBUG: 16:47:55.167: Image device reported finger status: on 158s (process:2037): libfprint-image_device-DEBUG: 16:47:55.167: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 158s (process:2037): libfprint-SSM-DEBUG: 16:47:55.168: [vfs301] M_LOOP_NUM_STATES entering state 4 158s (process:2037): libfprint-SSM-DEBUG: 16:47:55.368: [vfs301] M_LOOP_NUM_STATES entering state 5 158s (process:2037): libfprint-SSM-DEBUG: 16:47:55.371: [vfs301] M_LOOP_NUM_STATES entering state 6 158s (process:2037): libfprint-image_device-DEBUG: 16:47:55.371: Image device captured an image 158s (process:2037): libfprint-image_device-DEBUG: 16:47:55.375: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 158s (process:2037): libfprint-device-DEBUG: 16:47:55.375: Device reported finger status change: FP_FINGER_STATUS_PRESENT 158s (process:2037): libfprint-SSM-DEBUG: 16:47:55.375: [vfs301] M_LOOP_NUM_STATES completed successfully 158s (process:2037): libfprint-device-DEBUG: 16:47:55.375: Device reported finger status change: FP_FINGER_STATUS_NONE 158s (process:2037): libfprint-image_device-DEBUG: 16:47:55.375: Image device reported finger status: off 158s (process:2037): libfprint-image_device-DEBUG: 16:47:55.375: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 158s (process:2037): libfprint-image_device-DEBUG: 16:47:55.375: Deactivating image device 158s (process:2037): libfprint-image_device-DEBUG: 16:47:55.375: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_DEACTIVATING 158s (process:2037): libfprint-image_device-DEBUG: 16:47:55.375: Image device deactivation completed 158s (process:2037): libfprint-image_device-DEBUG: 16:47:55.375: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE 158s (process:2037): libfprint-image-DEBUG: 16:47:55.395: Minutiae scan completed in 0.023864 secs 158s (process:2037): libfprint-device-DEBUG: 16:47:55.395: Device reported capture completion 158s (process:2037): libfprint-device-DEBUG: 16:47:55.395: Completing action FPI_DEVICE_ACTION_CAPTURE in idle! 158s (process:2037): libfprint-device-DEBUG: 16:47:55.395: Updated temperature model after 0.57 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 158s (process:2037): libfprint-image_device-DEBUG: 16:47:55.396: Image device close completed 158s (process:2037): libfprint-device-DEBUG: 16:47:55.396: Device reported close completion 158s (process:2037): libfprint-device-DEBUG: 16:47:55.396: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 158s (process:2037): libfprint-device-DEBUG: 16:47:55.396: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 158s ** (umockdev-run:2033): DEBUG: 16:47:55.460: umockdev.vala:150: Removing test bed /tmp/umockdev.MAB4J2 158s (umockdev-run:2033): GLib-DEBUG: 16:47:55.465: unsetenv() is not thread-safe and should not be used after threads are created 158s Comparing PNGs /tmp/libfprint-umockdev-test-gz64snzb/capture.png and /usr/share/installed-tests/libfprint-2/vfs301/capture.png 158s PASS: libfprint-2/driver-vfs301.test 158s Running test: libfprint-2/fp-device.test 158s TAP version 13 158s # random seed: R02S8527b62dcc8bf1e7a5e83e32f7f3ecee 158s 1..17 158s # Start of device tests 158s # Start of async tests 158s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.7+tod1) 158s # libfprint-tod-DEBUG: Impossible to load the shared drivers dir Error opening directory ?/usr/lib/aarch64-linux-gnu/libfprint-2/tod-1?: No such file or directory 158s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0003 158s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 158s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0002 158s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_IMAGE, /tmp/libfprint-BIVBK2/virtual_image.socket 158s # libfprint-context-DEBUG: created 158s # libfprint-device-DEBUG: Device reported probe completion 158s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 158s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 158s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:2044): libfprint-virtual_image-DEBUG: 16:47:55.513: 46514112: ../libfprint/drivers/virtual-image.c:216 158s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:2044): libfprint-virtual_device_connection-DEBUG: 16:47:55.513: 46514190: ../libfprint/drivers/virtual-device-listener.c:153 158s # libfprint-image_device-DEBUG: Image device open completed 158s # libfprint-device-DEBUG: Device reported open completion 158s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 158s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 158s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:2044): libfprint-virtual_image-DEBUG: 16:47:55.613: 46614565: ../libfprint/drivers/virtual-image.c:244 158s # libfprint-image_device-DEBUG: Image device close completed 158s # libfprint-device-DEBUG: Device reported close completion 158s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 158s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 158s # GLib-DEBUG: unsetenv() is not thread-safe and should not be used after threads are created 158s ok 1 /device/async/open 158s # GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used after threads are created 158s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.7+tod1) 158s # libfprint-tod-DEBUG: Impossible to load the shared drivers dir Error opening directory ?/usr/lib/aarch64-linux-gnu/libfprint-2/tod-1?: No such file or directory 158s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0003 158s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 158s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0002 158s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_IMAGE, /tmp/libfprint-UPZ4J2/virtual_image.socket 158s # libfprint-context-DEBUG: created 158s # libfprint-device-DEBUG: Device reported probe completion 158s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 158s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 158s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:2044): libfprint-virtual_image-DEBUG: 16:47:55.717: 46717820: ../libfprint/drivers/virtual-image.c:216 158s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:2044): libfprint-virtual_device_connection-DEBUG: 16:47:55.717: 46717840: ../libfprint/drivers/virtual-device-listener.c:153 158s # libfprint-image_device-DEBUG: Image device open completed 158s # libfprint-device-DEBUG: Device reported open completion 158s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 158s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 158s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:2044): libfprint-virtual_image-DEBUG: 16:47:55.817: 46818235: ../libfprint/drivers/virtual-image.c:244 158s # libfprint-image_device-DEBUG: Image device close completed 158s # libfprint-device-DEBUG: Device reported close completion 158s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 158s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 158s # GLib-DEBUG: unsetenv() is not thread-safe and should not be used after threads are created 158s ok 2 /device/async/close 158s # End of async tests 158s # Start of sync tests 158s # GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used after threads are created 158s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.7+tod1) 158s # libfprint-tod-DEBUG: Impossible to load the shared drivers dir Error opening directory ?/usr/lib/aarch64-linux-gnu/libfprint-2/tod-1?: No such file or directory 158s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0003 158s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 158s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0002 158s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_IMAGE, /tmp/libfprint-DRIZJ2/virtual_image.socket 158s # libfprint-context-DEBUG: created 158s # libfprint-device-DEBUG: Device reported probe completion 158s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 158s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 158s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:2044): libfprint-virtual_image-DEBUG: 16:47:55.920: 46921447: ../libfprint/drivers/virtual-image.c:216 158s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:2044): libfprint-virtual_device_connection-DEBUG: 16:47:55.920: 46921469: ../libfprint/drivers/virtual-device-listener.c:153 158s # libfprint-image_device-DEBUG: Image device open completed 158s # libfprint-device-DEBUG: Device reported open completion 158s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 158s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 158s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:2044): libfprint-virtual_image-DEBUG: 16:47:56.021: 47021770: ../libfprint/drivers/virtual-image.c:244 159s # libfprint-image_device-DEBUG: Image device close completed 159s # libfprint-device-DEBUG: Device reported close completion 159s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 159s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 159s # GLib-DEBUG: unsetenv() is not thread-safe and should not be used after threads are created 159s ok 3 /device/sync/open 159s # GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used after threads are created 159s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.7+tod1) 159s # libfprint-tod-DEBUG: Impossible to load the shared drivers dir Error opening directory ?/usr/lib/aarch64-linux-gnu/libfprint-2/tod-1?: No such file or directory 159s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0003 159s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 159s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0002 159s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_IMAGE, /tmp/libfprint-B2LEK2/virtual_image.socket 159s # libfprint-context-DEBUG: created 159s # libfprint-device-DEBUG: Device reported probe completion 159s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 159s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 159s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:2044): libfprint-virtual_image-DEBUG: 16:47:56.124: 47125418: ../libfprint/drivers/virtual-image.c:216 159s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:2044): libfprint-virtual_device_connection-DEBUG: 16:47:56.124: 47125439: ../libfprint/drivers/virtual-device-listener.c:153 159s # libfprint-image_device-DEBUG: Image device open completed 159s # libfprint-device-DEBUG: Device reported open completion 159s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 159s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 159s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:2044): libfprint-virtual_image-DEBUG: 16:47:56.225: 47225819: ../libfprint/drivers/virtual-image.c:244 159s # libfprint-image_device-DEBUG: Image device close completed 159s # libfprint-device-DEBUG: Device reported close completion 159s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 159s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 159s # GLib-DEBUG: unsetenv() is not thread-safe and should not be used after threads are created 159s ok 4 /device/sync/close 159s # GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used after threads are created 159s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.7+tod1) 159s # libfprint-tod-DEBUG: Impossible to load the shared drivers dir Error opening directory ?/usr/lib/aarch64-linux-gnu/libfprint-2/tod-1?: No such file or directory 159s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0003 159s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 159s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0002 159s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_IMAGE, /tmp/libfprint-MNQ7J2/virtual_image.socket 159s # libfprint-context-DEBUG: created 159s # libfprint-device-DEBUG: Device reported probe completion 159s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 159s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 159s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:2044): libfprint-virtual_image-DEBUG: 16:47:56.328: 47328921: ../libfprint/drivers/virtual-image.c:216 159s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:2044): libfprint-virtual_device_connection-DEBUG: 16:47:56.328: 47328940: ../libfprint/drivers/virtual-device-listener.c:153 159s # libfprint-image_device-DEBUG: Image device open completed 159s # libfprint-device-DEBUG: Device reported open completion 159s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 159s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 159s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:2044): libfprint-virtual_image-DEBUG: 16:47:56.428: 47429331: ../libfprint/drivers/virtual-image.c:244 159s # libfprint-image_device-DEBUG: Image device close completed 159s # libfprint-device-DEBUG: Device reported close completion 159s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 159s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 159s # GLib-DEBUG: unsetenv() is not thread-safe and should not be used after threads are created 159s ok 5 /device/sync/get_driver 159s # GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used after threads are created 159s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.7+tod1) 159s # libfprint-tod-DEBUG: Impossible to load the shared drivers dir Error opening directory ?/usr/lib/aarch64-linux-gnu/libfprint-2/tod-1?: No such file or directory 159s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0003 159s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 159s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0002 159s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_IMAGE, /tmp/libfprint-3X81J2/virtual_image.socket 159s # libfprint-context-DEBUG: created 159s # libfprint-device-DEBUG: Device reported probe completion 159s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 159s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 159s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:2044): libfprint-virtual_image-DEBUG: 16:47:56.532: 47533535: ../libfprint/drivers/virtual-image.c:216 159s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:2044): libfprint-virtual_device_connection-DEBUG: 16:47:56.532: 47533555: ../libfprint/drivers/virtual-device-listener.c:153 159s # libfprint-image_device-DEBUG: Image device open completed 159s # libfprint-device-DEBUG: Device reported open completion 159s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 159s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 159s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:2044): libfprint-virtual_image-DEBUG: 16:47:56.633: 47633843: ../libfprint/drivers/virtual-image.c:244 159s # libfprint-image_device-DEBUG: Image device close completed 159s # libfprint-device-DEBUG: Device reported close completion 159s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 159s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 159s # GLib-DEBUG: unsetenv() is not thread-safe and should not be used after threads are created 159s ok 6 /device/sync/get_device_id 159s # GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used after threads are created 159s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.7+tod1) 159s # libfprint-tod-DEBUG: Impossible to load the shared drivers dir Error opening directory ?/usr/lib/aarch64-linux-gnu/libfprint-2/tod-1?: No such file or directory 159s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0003 159s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 159s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0002 159s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_IMAGE, /tmp/libfprint-5QM6J2/virtual_image.socket 159s # libfprint-context-DEBUG: created 159s # libfprint-device-DEBUG: Device reported probe completion 159s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 159s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 159s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:2044): libfprint-virtual_image-DEBUG: 16:47:56.736: 47737321: ../libfprint/drivers/virtual-image.c:216 159s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:2044): libfprint-virtual_device_connection-DEBUG: 16:47:56.736: 47737342: ../libfprint/drivers/virtual-device-listener.c:153 159s # libfprint-image_device-DEBUG: Image device open completed 159s # libfprint-device-DEBUG: Device reported open completion 159s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 159s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 159s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:2044): libfprint-virtual_image-DEBUG: 16:47:56.836: 47837655: ../libfprint/drivers/virtual-image.c:244 159s # libfprint-image_device-DEBUG: Image device close completed 159s # libfprint-device-DEBUG: Device reported close completion 159s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 159s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 159s # GLib-DEBUG: unsetenv() is not thread-safe and should not be used after threads are created 159s ok 7 /device/sync/get_name 159s # GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used after threads are created 159s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.7+tod1) 159s # libfprint-tod-DEBUG: Impossible to load the shared drivers dir Error opening directory ?/usr/lib/aarch64-linux-gnu/libfprint-2/tod-1?: No such file or directory 159s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0003 159s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 159s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0002 159s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_IMAGE, /tmp/libfprint-DSXZJ2/virtual_image.socket 159s # libfprint-context-DEBUG: created 159s # libfprint-device-DEBUG: Device reported probe completion 159s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 159s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 159s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:2044): libfprint-virtual_image-DEBUG: 16:47:56.940: 47940835: ../libfprint/drivers/virtual-image.c:216 159s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:2044): libfprint-virtual_device_connection-DEBUG: 16:47:56.940: 47940851: ../libfprint/drivers/virtual-device-listener.c:153 160s # libfprint-image_device-DEBUG: Image device open completed 160s # libfprint-device-DEBUG: Device reported open completion 160s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 160s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 160s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:2044): libfprint-virtual_image-DEBUG: 16:47:57.040: 48041165: ../libfprint/drivers/virtual-image.c:244 160s # libfprint-image_device-DEBUG: Image device close completed 160s # libfprint-device-DEBUG: Device reported close completion 160s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 160s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 160s # GLib-DEBUG: unsetenv() is not thread-safe and should not be used after threads are created 160s ok 8 /device/sync/get_scan_type 160s # GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used after threads are created 160s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.7+tod1) 160s # libfprint-tod-DEBUG: Impossible to load the shared drivers dir Error opening directory ?/usr/lib/aarch64-linux-gnu/libfprint-2/tod-1?: No such file or directory 160s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0003 160s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 160s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0002 160s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_IMAGE, /tmp/libfprint-IWKGK2/virtual_image.socket 160s # libfprint-context-DEBUG: created 160s # libfprint-device-DEBUG: Device reported probe completion 160s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 160s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 160s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:2044): libfprint-virtual_image-DEBUG: 16:47:57.144: 48145120: ../libfprint/drivers/virtual-image.c:216 160s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:2044): libfprint-virtual_device_connection-DEBUG: 16:47:57.144: 48145141: ../libfprint/drivers/virtual-device-listener.c:153 160s # libfprint-image_device-DEBUG: Image device open completed 160s # libfprint-device-DEBUG: Device reported open completion 160s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 160s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 160s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:2044): libfprint-virtual_image-DEBUG: 16:47:57.244: 48245441: ../libfprint/drivers/virtual-image.c:244 160s # libfprint-image_device-DEBUG: Image device close completed 160s # libfprint-device-DEBUG: Device reported close completion 160s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 160s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 160s # GLib-DEBUG: unsetenv() is not thread-safe and should not be used after threads are created 160s ok 9 /device/sync/get_finger_status 160s # GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used after threads are created 160s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.7+tod1) 160s # libfprint-tod-DEBUG: Impossible to load the shared drivers dir Error opening directory ?/usr/lib/aarch64-linux-gnu/libfprint-2/tod-1?: No such file or directory 160s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0003 160s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 160s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0002 160s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_IMAGE, /tmp/libfprint-WWQ9J2/virtual_image.socket 160s # libfprint-context-DEBUG: created 160s # libfprint-device-DEBUG: Device reported probe completion 160s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 160s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 160s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:2044): libfprint-virtual_image-DEBUG: 16:47:57.348: 48349655: ../libfprint/drivers/virtual-image.c:216 160s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:2044): libfprint-virtual_device_connection-DEBUG: 16:47:57.348: 48349676: ../libfprint/drivers/virtual-device-listener.c:153 160s # libfprint-image_device-DEBUG: Image device open completed 160s # libfprint-device-DEBUG: Device reported open completion 160s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 160s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 160s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:2044): libfprint-virtual_image-DEBUG: 16:47:57.449: 48450049: ../libfprint/drivers/virtual-image.c:244 160s # libfprint-image_device-DEBUG: Image device close completed 160s # libfprint-device-DEBUG: Device reported close completion 160s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 160s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 160s # GLib-DEBUG: unsetenv() is not thread-safe and should not be used after threads are created 160s ok 10 /device/sync/get_nr_enroll_stages 160s # GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used after threads are created 160s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.7+tod1) 160s # libfprint-tod-DEBUG: Impossible to load the shared drivers dir Error opening directory ?/usr/lib/aarch64-linux-gnu/libfprint-2/tod-1?: No such file or directory 160s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0003 160s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 160s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0002 160s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_IMAGE, /tmp/libfprint-T2V2J2/virtual_image.socket 160s # libfprint-context-DEBUG: created 160s # libfprint-device-DEBUG: Device reported probe completion 160s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 160s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 160s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:2044): libfprint-virtual_image-DEBUG: 16:47:57.553: 48554152: ../libfprint/drivers/virtual-image.c:216 160s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:2044): libfprint-virtual_device_connection-DEBUG: 16:47:57.553: 48554173: ../libfprint/drivers/virtual-device-listener.c:153 160s # libfprint-image_device-DEBUG: Image device open completed 160s # libfprint-device-DEBUG: Device reported open completion 160s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 160s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 160s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:2044): libfprint-virtual_image-DEBUG: 16:47:57.653: 48654475: ../libfprint/drivers/virtual-image.c:244 160s # libfprint-image_device-DEBUG: Image device close completed 160s # libfprint-device-DEBUG: Device reported close completion 160s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 160s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 160s # GLib-DEBUG: unsetenv() is not thread-safe and should not be used after threads are created 160s ok 11 /device/sync/supports_identify 160s # GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used after threads are created 160s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.7+tod1) 160s # libfprint-tod-DEBUG: Impossible to load the shared drivers dir Error opening directory ?/usr/lib/aarch64-linux-gnu/libfprint-2/tod-1?: No such file or directory 160s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0003 160s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 160s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0002 160s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_IMAGE, /tmp/libfprint-HMU5J2/virtual_image.socket 160s # libfprint-context-DEBUG: created 160s # libfprint-device-DEBUG: Device reported probe completion 160s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 160s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 160s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:2044): libfprint-virtual_image-DEBUG: 16:47:57.757: 48757909: ../libfprint/drivers/virtual-image.c:216 160s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:2044): libfprint-virtual_device_connection-DEBUG: 16:47:57.757: 48757929: ../libfprint/drivers/virtual-device-listener.c:153 160s # libfprint-image_device-DEBUG: Image device open completed 160s # libfprint-device-DEBUG: Device reported open completion 160s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 160s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 160s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:2044): libfprint-virtual_image-DEBUG: 16:47:57.857: 48858395: ../libfprint/drivers/virtual-image.c:244 160s # libfprint-image_device-DEBUG: Image device close completed 160s # libfprint-device-DEBUG: Device reported close completion 160s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 160s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 160s # GLib-DEBUG: unsetenv() is not thread-safe and should not be used after threads are created 160s ok 12 /device/sync/supports_capture 160s # GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used after threads are created 160s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.7+tod1) 160s # libfprint-tod-DEBUG: Impossible to load the shared drivers dir Error opening directory ?/usr/lib/aarch64-linux-gnu/libfprint-2/tod-1?: No such file or directory 160s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0003 160s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 160s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0002 160s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_IMAGE, /tmp/libfprint-KYSYJ2/virtual_image.socket 160s # libfprint-context-DEBUG: created 160s # libfprint-device-DEBUG: Device reported probe completion 160s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 160s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 160s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:2044): libfprint-virtual_image-DEBUG: 16:47:57.961: 48961925: ../libfprint/drivers/virtual-image.c:216 160s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:2044): libfprint-virtual_device_connection-DEBUG: 16:47:57.961: 48961940: ../libfprint/drivers/virtual-device-listener.c:153 161s # libfprint-image_device-DEBUG: Image device open completed 161s # libfprint-device-DEBUG: Device reported open completion 161s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 161s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 161s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:2044): libfprint-virtual_image-DEBUG: 16:47:58.061: 49062380: ../libfprint/drivers/virtual-image.c:244 161s # libfprint-image_device-DEBUG: Image device close completed 161s # libfprint-device-DEBUG: Device reported close completion 161s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 161s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 161s # GLib-DEBUG: unsetenv() is not thread-safe and should not be used after threads are created 161s ok 13 /device/sync/has_storage 161s # Start of open tests 161s # GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used after threads are created 161s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.7+tod1) 161s # libfprint-tod-DEBUG: Impossible to load the shared drivers dir Error opening directory ?/usr/lib/aarch64-linux-gnu/libfprint-2/tod-1?: No such file or directory 161s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0003 161s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 161s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0002 161s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_IMAGE, /tmp/libfprint-95UGK2/virtual_image.socket 161s # libfprint-context-DEBUG: created 161s # libfprint-device-DEBUG: Device reported probe completion 161s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 161s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 161s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:2044): libfprint-virtual_image-DEBUG: 16:47:58.165: 49165849: ../libfprint/drivers/virtual-image.c:216 161s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:2044): libfprint-virtual_device_connection-DEBUG: 16:47:58.165: 49165865: ../libfprint/drivers/virtual-device-listener.c:153 161s # libfprint-image_device-DEBUG: Image device open completed 161s # libfprint-device-DEBUG: Device reported open completion 161s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 161s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 161s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:2044): libfprint-virtual_image-DEBUG: 16:47:58.265: 49266219: ../libfprint/drivers/virtual-image.c:244 161s # libfprint-image_device-DEBUG: Image device close completed 161s # libfprint-device-DEBUG: Device reported close completion 161s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 161s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 161s # GLib-DEBUG: unsetenv() is not thread-safe and should not be used after threads are created 161s ok 14 /device/sync/open/notify 161s # End of open tests 161s # Start of close tests 161s # GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used after threads are created 161s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.7+tod1) 161s # libfprint-tod-DEBUG: Impossible to load the shared drivers dir Error opening directory ?/usr/lib/aarch64-linux-gnu/libfprint-2/tod-1?: No such file or directory 161s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0003 161s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 161s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0002 161s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_IMAGE, /tmp/libfprint-Y7K8J2/virtual_image.socket 161s # libfprint-context-DEBUG: created 161s # libfprint-device-DEBUG: Device reported probe completion 161s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 161s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 161s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:2044): libfprint-virtual_image-DEBUG: 16:47:58.368: 49369632: ../libfprint/drivers/virtual-image.c:216 161s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:2044): libfprint-virtual_device_connection-DEBUG: 16:47:58.368: 49369647: ../libfprint/drivers/virtual-device-listener.c:153 161s # libfprint-image_device-DEBUG: Image device open completed 161s # libfprint-device-DEBUG: Device reported open completion 161s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 161s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 161s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:2044): libfprint-virtual_image-DEBUG: 16:47:58.469: 49470001: ../libfprint/drivers/virtual-image.c:244 161s # libfprint-image_device-DEBUG: Image device close completed 161s # libfprint-device-DEBUG: Device reported close completion 161s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 161s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 161s # GLib-DEBUG: unsetenv() is not thread-safe and should not be used after threads are created 161s ok 15 /device/sync/close/notify 161s # End of close tests 161s # Start of identify tests 161s # GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used after threads are created 161s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.7+tod1) 161s # libfprint-tod-DEBUG: Impossible to load the shared drivers dir Error opening directory ?/usr/lib/aarch64-linux-gnu/libfprint-2/tod-1?: No such file or directory 161s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0003 161s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 161s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0002 161s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_IMAGE, /tmp/libfprint-R2P1J2/virtual_image.socket 161s # libfprint-context-DEBUG: created 161s # libfprint-device-DEBUG: Device reported probe completion 161s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 161s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 161s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:2044): libfprint-virtual_image-DEBUG: 16:47:58.572: 49573487: ../libfprint/drivers/virtual-image.c:216 161s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:2044): libfprint-virtual_device_connection-DEBUG: 16:47:58.572: 49573502: ../libfprint/drivers/virtual-device-listener.c:153 161s # libfprint-image_device-DEBUG: Image device open completed 161s # libfprint-device-DEBUG: Device reported open completion 161s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 161s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 161s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:2044): libfprint-virtual_image-DEBUG: 16:47:58.673: 49673812: ../libfprint/drivers/virtual-image.c:244 161s # libfprint-image_device-DEBUG: Image device close completed 161s # libfprint-device-DEBUG: Device reported close completion 161s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 161s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 161s # GLib-DEBUG: unsetenv() is not thread-safe and should not be used after threads are created 161s ok 16 /device/sync/identify/cancelled 161s # GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used after threads are created 161s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.7+tod1) 161s # libfprint-tod-DEBUG: Impossible to load the shared drivers dir Error opening directory ?/usr/lib/aarch64-linux-gnu/libfprint-2/tod-1?: No such file or directory 161s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0003 161s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 161s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0002 161s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_IMAGE, /tmp/libfprint-JD95J2/virtual_image.socket 161s # libfprint-context-DEBUG: created 161s # libfprint-device-DEBUG: Device reported probe completion 161s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 161s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 161s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:2044): libfprint-virtual_image-DEBUG: 16:47:58.776: 49777461: ../libfprint/drivers/virtual-image.c:216 161s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:2044): libfprint-virtual_device_connection-DEBUG: 16:47:58.776: 49777475: ../libfprint/drivers/virtual-device-listener.c:153 161s # libfprint-image_device-DEBUG: Image device open completed 161s # libfprint-device-DEBUG: Device reported open completion 161s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 161s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 161s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:2044): libfprint-virtual_image-DEBUG: 16:47:58.877: 49877787: ../libfprint/drivers/virtual-image.c:244 161s # libfprint-image_device-DEBUG: Image device close completed 161s # libfprint-device-DEBUG: Device reported close completion 161s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 161s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 161s # GLib-DEBUG: unsetenv() is not thread-safe and should not be used after threads are created 161s ok 17 /device/sync/identify/null-prints 161s # End of identify tests 161s # End of sync tests 161s # End of device tests 161s PASS: libfprint-2/fp-device.test 161s Running test: libfprint-2/tod-fp-context-tod-fake_test_dev_tod_current.test 161s Executing: libfprint-2/tod-fp-context-tod-fake_test_dev_tod_current.test 161s TAP version 13 161s # random seed: R02S68b7f1f40c5626c6a39027e0501d342d 161s 1..4 161s # Start of context tests 161s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.7+tod1) 161s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/current/libdevice-fake-tod-driver.so 161s # libfprint-tod-DEBUG: Found TOD entry point symbol 0xfd1a937c2580, GType is 196995567021792 161s # libfprint-tod-DEBUG: Loading driver fake_test_dev_tod_current (Virtual device for debugging) 161s ok 1 /context/new 161s # GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used after threads are created 161s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.7+tod1) 161s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0003 161s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 161s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0002 161s # GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used after threads are created 161s ok 2 /context/no-devices 161s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.7+tod1) 161s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/current/libdevice-fake-tod-driver.so 161s # libfprint-tod-DEBUG: Found TOD entry point symbol 0xfd1a937c2580, GType is 196995567021792 161s # libfprint-tod-DEBUG: Loading driver fake_test_dev_tod_current (Virtual device for debugging) 161s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0003 161s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 161s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0002 161s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_FAKE_DEVICE, yes 161s # libfprint-context-DEBUG: created 161s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_probe: Device Virtual device for debugging in action FPI_DEVICE_ACTION_PROBE 161s # 161s # libfprint-device-DEBUG: Device reported probe completion 161s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 161s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 161s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 161s # 161s # libfprint-device-DEBUG: Device reported open completion 161s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 161s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 161s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 161s # 161s # libfprint-device-DEBUG: Device reported close completion 161s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 161s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 162s ok 3 /context/has-virtual-device 162s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.7+tod1) 162s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/current/libdevice-fake-tod-driver.so 162s # libfprint-tod-DEBUG: Found TOD entry point symbol 0xfd1a937c2580, GType is 196995567021792 162s # libfprint-tod-DEBUG: Loading driver fake_test_dev_tod_current (Virtual device for debugging) 162s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0003 162s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 162s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0002 162s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_FAKE_DEVICE, yes 162s # libfprint-context-DEBUG: created 162s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_probe: Device Virtual device for debugging in action FPI_DEVICE_ACTION_PROBE 162s # 162s # libfprint-device-DEBUG: Device reported probe completion 162s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 162s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 162s ok 4 /context/enumerates-new-devices 162s # End of context tests 162s PASS: libfprint-2/tod-fp-context-tod-fake_test_dev_tod_current.test 162s Running test: libfprint-2/driver-elanmoc.test 162s ** (umockdev-run:2096): DEBUG: 16:47:59.150: umockdev.vala:123: Created udev test bed /tmp/umockdev.3TRGK2 162s ** (umockdev-run:2096): DEBUG: 16:47:59.151: umockdev.vala:1297: parsing device description for /devices/pci0000:00/0000:00:14.0/usb1/1-9 162s ** (umockdev-run:2096): DEBUG: 16:47:59.152: umockdev.vala:1366: creating device /devices/pci0000:00/0000:00:14.0/usb1/1-9 (subsystem usb) 162s ** (umockdev-run:2096): DEBUG: 16:47:59.154: umockdev.vala:1411: create_node_for_device: creating file device /tmp/umockdev.3TRGK2/dev/bus/usb/001/003 162s ** (umockdev-run:2096): DEBUG: 16:47:59.154: umockdev.vala:1297: parsing device description for /devices/pci0000:00/0000:00:14.0/usb1 162s ** (umockdev-run:2096): DEBUG: 16:47:59.155: umockdev.vala:1366: creating device /devices/pci0000:00/0000:00:14.0/usb1 (subsystem usb) 162s ** (umockdev-run:2096): DEBUG: 16:47:59.157: umockdev.vala:1411: create_node_for_device: creating file device /tmp/umockdev.3TRGK2/dev/bus/usb/001/001 162s ** (umockdev-run:2096): DEBUG: 16:47:59.157: umockdev.vala:1297: parsing device description for /devices/pci0000:00/0000:00:14.0 162s ** (umockdev-run:2096): DEBUG: 16:47:59.158: umockdev.vala:1366: creating device /devices/pci0000:00/0000:00:14.0 (subsystem pci) 162s (process:2100): libfprint-context-DEBUG: 16:47:59.242: Initializing FpContext (libfprint version 1.94.7+tod1) 162s (process:2100): libfprint-tod-DEBUG: 16:47:59.242: Impossible to load the shared drivers dir Error opening directory “/usr/lib/aarch64-linux-gnu/libfprint-2/tod-1”: No such file or directory 162s (process:2100): libfprint-elanmoc-DEBUG: 16:47:59.244: 50245399: ../libfprint/drivers/elanmoc/elanmoc.c:1150 162s (process:2100): libfprint-context-DEBUG: 16:47:59.244: No driver found for USB device 1D6B:0002 162s (process:2100): libfprint-device-DEBUG: 16:47:59.245: Device reported probe completion 162s (process:2100): libfprint-device-DEBUG: 16:47:59.245: Completing action FPI_DEVICE_ACTION_PROBE in idle! 162s (process:2100): libfprint-device-DEBUG: 16:47:59.245: Not updating temperature model, device can run continuously! 162s (process:2100): libfprint-SSM-DEBUG: 16:47:59.250: [elanmoc] DEV_INIT_STATES entering state 0 162s (process:2100): libfprint-SSM-DEBUG: 16:47:59.250: [elanmoc] FP_CMD_NUM_STATES entering state 0 162s (process:2100): libfprint-SSM-DEBUG: 16:47:59.250: [elanmoc] FP_CMD_NUM_STATES entering state 1 162s (process:2100): libfprint-SSM-DEBUG: 16:47:59.251: [elanmoc] DEV_INIT_STATES entering state 1 162s (process:2100): libfprint-SSM-DEBUG: 16:47:59.251: [elanmoc] FP_CMD_NUM_STATES entering state 0 162s (process:2100): libfprint-SSM-DEBUG: 16:47:59.251: [elanmoc] FP_CMD_NUM_STATES completed successfully 162s (process:2100): libfprint-SSM-DEBUG: 16:47:59.251: [elanmoc] FP_CMD_NUM_STATES entering state 1 162s (process:2100): libfprint-SSM-DEBUG: 16:47:59.252: [elanmoc] DEV_INIT_STATES entering state 2 162s (process:2100): libfprint-SSM-DEBUG: 16:47:59.252: [elanmoc] FP_CMD_NUM_STATES entering state 0 162s (process:2100): libfprint-SSM-DEBUG: 16:47:59.252: [elanmoc] FP_CMD_NUM_STATES completed successfully 162s (process:2100): libfprint-SSM-DEBUG: 16:47:59.253: [elanmoc] FP_CMD_NUM_STATES entering state 1 162s (process:2100): libfprint-elanmoc-DEBUG: 16:47:59.253: elanmoc FW Version 8004 162s (process:2100): libfprint-SSM-DEBUG: 16:47:59.253: [elanmoc] DEV_INIT_STATES entering state 3 162s (process:2100): libfprint-SSM-DEBUG: 16:47:59.253: [elanmoc] FP_CMD_NUM_STATES entering state 0 162s (process:2100): libfprint-SSM-DEBUG: 16:47:59.253: [elanmoc] FP_CMD_NUM_STATES completed successfully 162s (process:2100): libfprint-SSM-DEBUG: 16:47:59.254: [elanmoc] FP_CMD_NUM_STATES entering state 1 162s (process:2100): libfprint-elanmoc-DEBUG: 16:47:59.254: elanmoc last_read DIM 0x57(87) 0x6B(107) 162s (process:2100): libfprint-SSM-DEBUG: 16:47:59.254: [elanmoc] DEV_INIT_STATES entering state 4 162s (process:2100): libfprint-SSM-DEBUG: 16:47:59.254: [elanmoc] FP_CMD_NUM_STATES entering state 0 162s (process:2100): libfprint-SSM-DEBUG: 16:47:59.254: [elanmoc] FP_CMD_NUM_STATES completed successfully 162s (process:2100): libfprint-SSM-DEBUG: 16:47:59.255: [elanmoc] FP_CMD_NUM_STATES entering state 1 162s (process:2100): libfprint-elanmoc-DEBUG: 16:47:59.255: elanmoc Current enrolled fingers in the Chipset: 1 (0x40 0x01) 162s (process:2100): libfprint-SSM-DEBUG: 16:47:59.255: [elanmoc] DEV_INIT_STATES completed successfully 162s (process:2100): libfprint-device-DEBUG: 16:47:59.255: Device reported open completion 162s (process:2100): libfprint-SSM-DEBUG: 16:47:59.255: [elanmoc] FP_CMD_NUM_STATES completed successfully 162s (process:2100): libfprint-device-DEBUG: 16:47:59.255: Completing action FPI_DEVICE_ACTION_OPEN in idle! 162s (process:2100): libfprint-device-DEBUG: 16:47:59.255: Not updating temperature model, device can run continuously! 162s (process:2100): libfprint-device-DEBUG: 16:47:59.257: Not updating temperature model, device can run continuously! 162s (process:2100): libfprint-SSM-DEBUG: 16:47:59.257: [elanmoc] MOC_ENROLL_NUM_STATES entering state 0 162s (process:2100): libfprint-SSM-DEBUG: 16:47:59.257: [elanmoc] FP_CMD_NUM_STATES entering state 0 162s (process:2100): libfprint-SSM-DEBUG: 16:47:59.257: [elanmoc] FP_CMD_NUM_STATES entering state 1 162s (process:2100): libfprint-elanmoc-DEBUG: 16:47:59.258: elanmoc Current enrolled fingers in the Chipset: 1 (0x40 0x01) 162s (process:2100): libfprint-SSM-DEBUG: 16:47:59.258: [elanmoc] MOC_ENROLL_NUM_STATES entering state 1 162s (process:2100): libfprint-SSM-DEBUG: 16:47:59.258: [elanmoc] FP_CMD_NUM_STATES entering state 0 162s (process:2100): libfprint-SSM-DEBUG: 16:47:59.258: [elanmoc] FP_CMD_NUM_STATES completed successfully 162s (process:2100): libfprint-SSM-DEBUG: 16:47:59.258: [elanmoc] FP_CMD_NUM_STATES entering state 1 162s (process:2100): libfprint-elanmoc-DEBUG: 16:47:59.259: ##### Re-Enrollment Case! ##### 162s (process:2100): libfprint-SSM-DEBUG: 16:47:59.259: [elanmoc] MOC_ENROLL_NUM_STATES entering state 2 162s (process:2100): libfprint-SSM-DEBUG: 16:47:59.259: [elanmoc] FP_CMD_NUM_STATES entering state 0 162s (process:2100): libfprint-SSM-DEBUG: 16:47:59.259: [elanmoc] FP_CMD_NUM_STATES completed successfully 162s (process:2100): libfprint-SSM-DEBUG: 16:47:59.260: [elanmoc] FP_CMD_NUM_STATES entering state 1 162s (process:2100): libfprint-device-DEBUG: 16:47:59.260: Device reported enroll progress, reported 1 of 9 have been completed 162s (process:2100): libfprint-SSM-DEBUG: 16:47:59.260: [elanmoc] MOC_ENROLL_NUM_STATES entering state 2 162s (process:2100): libfprint-SSM-DEBUG: 16:47:59.260: [elanmoc] FP_CMD_NUM_STATES entering state 0 162s (process:2100): libfprint-SSM-DEBUG: 16:47:59.260: [elanmoc] FP_CMD_NUM_STATES completed successfully 162s (process:2100): libfprint-SSM-DEBUG: 16:47:59.261: [elanmoc] FP_CMD_NUM_STATES entering state 1 162s (process:2100): libfprint-device-DEBUG: 16:47:59.261: Device reported enroll progress, reported 2 of 9 have been completed 162s (process:2100): libfprint-SSM-DEBUG: 16:47:59.261: [elanmoc] MOC_ENROLL_NUM_STATES entering state 2 162s (process:2100): libfprint-SSM-DEBUG: 16:47:59.261: [elanmoc] FP_CMD_NUM_STATES entering state 0 162s (process:2100): libfprint-SSM-DEBUG: 16:47:59.261: [elanmoc] FP_CMD_NUM_STATES completed successfully 162s (process:2100): libfprint-SSM-DEBUG: 16:47:59.261: [elanmoc] FP_CMD_NUM_STATES entering state 1 162s (process:2100): libfprint-device-DEBUG: 16:47:59.262: Device reported enroll progress, reported 3 of 9 have been completed 162s (process:2100): libfprint-SSM-DEBUG: 16:47:59.262: [elanmoc] MOC_ENROLL_NUM_STATES entering state 2 162s (process:2100): libfprint-SSM-DEBUG: 16:47:59.262: [elanmoc] FP_CMD_NUM_STATES entering state 0 162s (process:2100): libfprint-SSM-DEBUG: 16:47:59.262: [elanmoc] FP_CMD_NUM_STATES completed successfully 162s (process:2100): libfprint-SSM-DEBUG: 16:47:59.262: [elanmoc] FP_CMD_NUM_STATES entering state 1 162s (process:2100): libfprint-device-DEBUG: 16:47:59.263: Device reported enroll progress, reported 4 of 9 have been completed 162s (process:2100): libfprint-SSM-DEBUG: 16:47:59.263: [elanmoc] MOC_ENROLL_NUM_STATES entering state 2 162s (process:2100): libfprint-SSM-DEBUG: 16:47:59.263: [elanmoc] FP_CMD_NUM_STATES entering state 0 162s (process:2100): libfprint-SSM-DEBUG: 16:47:59.263: [elanmoc] FP_CMD_NUM_STATES completed successfully 162s (process:2100): libfprint-SSM-DEBUG: 16:47:59.263: [elanmoc] FP_CMD_NUM_STATES entering state 1 162s (process:2100): libfprint-device-DEBUG: 16:47:59.264: Device reported enroll progress, reported 5 of 9 have been completed 162s (process:2100): libfprint-SSM-DEBUG: 16:47:59.264: [elanmoc] MOC_ENROLL_NUM_STATES entering state 2 162s (process:2100): libfprint-SSM-DEBUG: 16:47:59.264: [elanmoc] FP_CMD_NUM_STATES entering state 0 162s (process:2100): libfprint-SSM-DEBUG: 16:47:59.264: [elanmoc] FP_CMD_NUM_STATES completed successfully 162s (process:2100): libfprint-SSM-DEBUG: 16:47:59.264: [elanmoc] FP_CMD_NUM_STATES entering state 1 162s (process:2100): libfprint-device-DEBUG: 16:47:59.265: Device reported enroll progress, reported 6 of 9 have been completed 162s (process:2100): libfprint-SSM-DEBUG: 16:47:59.265: [elanmoc] MOC_ENROLL_NUM_STATES entering state 2 162s (process:2100): libfprint-SSM-DEBUG: 16:47:59.265: [elanmoc] FP_CMD_NUM_STATES entering state 0 162s (process:2100): libfprint-SSM-DEBUG: 16:47:59.265: [elanmoc] FP_CMD_NUM_STATES completed successfully 162s (process:2100): libfprint-SSM-DEBUG: 16:47:59.265: [elanmoc] FP_CMD_NUM_STATES entering state 1 162s (process:2100): libfprint-device-DEBUG: 16:47:59.266: Device reported enroll progress, reported 7 of 9 have been completed 162s (process:2100): libfprint-SSM-DEBUG: 16:47:59.266: [elanmoc] MOC_ENROLL_NUM_STATES entering state 2 162s (process:2100): libfprint-SSM-DEBUG: 16:47:59.266: [elanmoc] FP_CMD_NUM_STATES entering state 0 162s (process:2100): libfprint-SSM-DEBUG: 16:47:59.266: [elanmoc] FP_CMD_NUM_STATES completed successfully 162s (process:2100): libfprint-SSM-DEBUG: 16:47:59.266: [elanmoc] FP_CMD_NUM_STATES entering state 1 162s (process:2100): libfprint-device-DEBUG: 16:47:59.267: Device reported enroll progress, reported 7 of 9 have been completed 162s (process:2100): libfprint-SSM-DEBUG: 16:47:59.267: [elanmoc] MOC_ENROLL_NUM_STATES entering state 2 162s (process:2100): libfprint-SSM-DEBUG: 16:47:59.267: [elanmoc] FP_CMD_NUM_STATES entering state 0 162s (process:2100): libfprint-SSM-DEBUG: 16:47:59.267: [elanmoc] FP_CMD_NUM_STATES completed successfully 162s (process:2100): libfprint-SSM-DEBUG: 16:47:59.267: [elanmoc] FP_CMD_NUM_STATES entering state 1 162s (process:2100): libfprint-device-DEBUG: 16:47:59.268: Device reported enroll progress, reported 8 of 9 have been completed 162s (process:2100): libfprint-SSM-DEBUG: 16:47:59.268: [elanmoc] MOC_ENROLL_NUM_STATES entering state 2 162s (process:2100): libfprint-SSM-DEBUG: 16:47:59.268: [elanmoc] FP_CMD_NUM_STATES entering state 0 162s (process:2100): libfprint-SSM-DEBUG: 16:47:59.268: [elanmoc] FP_CMD_NUM_STATES completed successfully 162s (process:2100): libfprint-SSM-DEBUG: 16:47:59.268: [elanmoc] FP_CMD_NUM_STATES entering state 1 162s (process:2100): libfprint-device-DEBUG: 16:47:59.269: Device reported enroll progress, reported 8 of 9 have been completed 162s (process:2100): libfprint-SSM-DEBUG: 16:47:59.269: [elanmoc] MOC_ENROLL_NUM_STATES entering state 2 162s (process:2100): libfprint-SSM-DEBUG: 16:47:59.269: [elanmoc] FP_CMD_NUM_STATES entering state 0 162s (process:2100): libfprint-SSM-DEBUG: 16:47:59.269: [elanmoc] FP_CMD_NUM_STATES completed successfully 162s (process:2100): libfprint-SSM-DEBUG: 16:47:59.269: [elanmoc] FP_CMD_NUM_STATES entering state 1 162s (process:2100): libfprint-device-DEBUG: 16:47:59.269: Device reported enroll progress, reported 9 of 9 have been completed 162s (process:2100): libfprint-SSM-DEBUG: 16:47:59.270: [elanmoc] MOC_ENROLL_NUM_STATES entering state 3 162s (process:2100): libfprint-SSM-DEBUG: 16:47:59.270: [elanmoc] FP_CMD_NUM_STATES entering state 0 162s (process:2100): libfprint-SSM-DEBUG: 16:47:59.270: [elanmoc] FP_CMD_NUM_STATES completed successfully 162s (process:2100): libfprint-SSM-DEBUG: 16:47:59.270: [elanmoc] FP_CMD_NUM_STATES entering state 1 162s (process:2100): libfprint-elanmoc-DEBUG: 16:47:59.270: elanmoc_commit_cb success 162s (process:2100): libfprint-elanmoc-DEBUG: 16:47:59.270: Enrollment was successful! 162s (process:2100): libfprint-device-DEBUG: 16:47:59.270: Device reported enroll completion 162s (process:2100): libfprint-device-DEBUG: 16:47:59.270: Print for finger FP_FINGER_UNKNOWN enrolled 162s (process:2100): libfprint-SSM-DEBUG: 16:47:59.271: [elanmoc] MOC_ENROLL_NUM_STATES completed successfully 162s (process:2100): libfprint-SSM-DEBUG: 16:47:59.271: [elanmoc] FP_CMD_NUM_STATES completed successfully 162s (process:2100): libfprint-device-DEBUG: 16:47:59.271: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 162s (process:2100): libfprint-device-DEBUG: 16:47:59.271: Not updating temperature model, device can run continuously! 162s (process:2100): libfprint-SSM-DEBUG: 16:47:59.271: [elanmoc] MOC_LIST_NUM_STATES entering state 0 162s (process:2100): libfprint-SSM-DEBUG: 16:47:59.271: [elanmoc] FP_CMD_NUM_STATES entering state 0 162s (process:2100): libfprint-SSM-DEBUG: 16:47:59.271: [elanmoc] FP_CMD_NUM_STATES entering state 1 162s (process:2100): libfprint-elanmoc-DEBUG: 16:47:59.272: elanmoc Current enrolled fingers in the Chipset: 1 (0x40 0x01) 162s (process:2100): libfprint-SSM-DEBUG: 16:47:59.272: [elanmoc] MOC_LIST_NUM_STATES entering state 1 162s (process:2100): libfprint-SSM-DEBUG: 16:47:59.272: [elanmoc] FP_CMD_NUM_STATES entering state 0 162s (process:2100): libfprint-SSM-DEBUG: 16:47:59.272: [elanmoc] FP_CMD_NUM_STATES completed successfully 162s (process:2100): libfprint-SSM-DEBUG: 16:47:59.272: [elanmoc] FP_CMD_NUM_STATES entering state 1 162s (process:2100): libfprint-SSM-DEBUG: 16:47:59.273: [elanmoc] MOC_LIST_NUM_STATES entering state 1 162s (process:2100): libfprint-SSM-DEBUG: 16:47:59.273: [elanmoc] FP_CMD_NUM_STATES entering state 0 162s (process:2100): libfprint-SSM-DEBUG: 16:47:59.273: [elanmoc] FP_CMD_NUM_STATES completed successfully 162s (process:2100): libfprint-SSM-DEBUG: 16:47:59.273: [elanmoc] FP_CMD_NUM_STATES entering state 1 162s (process:2100): libfprint-SSM-DEBUG: 16:47:59.273: [elanmoc] MOC_LIST_NUM_STATES entering state 1 162s (process:2100): libfprint-SSM-DEBUG: 16:47:59.273: [elanmoc] FP_CMD_NUM_STATES entering state 0 162s (process:2100): libfprint-SSM-DEBUG: 16:47:59.274: [elanmoc] FP_CMD_NUM_STATES completed successfully 162s (process:2100): libfprint-SSM-DEBUG: 16:47:59.274: [elanmoc] FP_CMD_NUM_STATES entering state 1 162s (process:2100): libfprint-SSM-DEBUG: 16:47:59.274: [elanmoc] MOC_LIST_NUM_STATES entering state 1 162s (process:2100): libfprint-SSM-DEBUG: 16:47:59.274: [elanmoc] FP_CMD_NUM_STATES entering state 0 162s (process:2100): libfprint-SSM-DEBUG: 16:47:59.274: [elanmoc] FP_CMD_NUM_STATES completed successfully 162s (process:2100): libfprint-SSM-DEBUG: 16:47:59.275: [elanmoc] FP_CMD_NUM_STATES entering state 1 162s (process:2100): libfprint-SSM-DEBUG: 16:47:59.275: [elanmoc] MOC_LIST_NUM_STATES entering state 1 162s (process:2100): libfprint-SSM-DEBUG: 16:47:59.275: [elanmoc] FP_CMD_NUM_STATES entering state 0 162s (process:2100): libfprint-SSM-DEBUG: 16:47:59.275: [elanmoc] FP_CMD_NUM_STATES completed successfully 162s (process:2100): libfprint-SSM-DEBUG: 16:47:59.276: [elanmoc] FP_CMD_NUM_STATES entering state 1 162s (process:2100): libfprint-SSM-DEBUG: 16:47:59.276: [elanmoc] MOC_LIST_NUM_STATES entering state 1 162s (process:2100): libfprint-SSM-DEBUG: 16:47:59.276: [elanmoc] FP_CMD_NUM_STATES entering state 0 162s (process:2100): libfprint-SSM-DEBUG: 16:47:59.276: [elanmoc] FP_CMD_NUM_STATES completed successfully 162s (process:2100): libfprint-SSM-DEBUG: 16:47:59.276: [elanmoc] FP_CMD_NUM_STATES entering state 1 162s (process:2100): libfprint-SSM-DEBUG: 16:47:59.277: [elanmoc] MOC_LIST_NUM_STATES entering state 1 162s (process:2100): libfprint-SSM-DEBUG: 16:47:59.277: [elanmoc] FP_CMD_NUM_STATES entering state 0 162s (process:2100): libfprint-SSM-DEBUG: 16:47:59.277: [elanmoc] FP_CMD_NUM_STATES completed successfully 162s (process:2100): libfprint-SSM-DEBUG: 16:47:59.277: [elanmoc] FP_CMD_NUM_STATES entering state 1 162s (process:2100): libfprint-SSM-DEBUG: 16:47:59.278: [elanmoc] MOC_LIST_NUM_STATES entering state 1 162s (process:2100): libfprint-SSM-DEBUG: 16:47:59.278: [elanmoc] FP_CMD_NUM_STATES entering state 0 162s (process:2100): libfprint-SSM-DEBUG: 16:47:59.278: [elanmoc] FP_CMD_NUM_STATES completed successfully 162s (process:2100): libfprint-SSM-DEBUG: 16:47:59.278: [elanmoc] FP_CMD_NUM_STATES entering state 1 162s (process:2100): libfprint-SSM-DEBUG: 16:47:59.279: [elanmoc] MOC_LIST_NUM_STATES entering state 1 162s (process:2100): libfprint-SSM-DEBUG: 16:47:59.279: [elanmoc] FP_CMD_NUM_STATES entering state 0 162s (process:2100): libfprint-SSM-DEBUG: 16:47:59.279: [elanmoc] FP_CMD_NUM_STATES completed successfully 162s (process:2100): libfprint-SSM-DEBUG: 16:47:59.279: [elanmoc] FP_CMD_NUM_STATES entering state 1 162s (process:2100): libfprint-SSM-DEBUG: 16:47:59.279: [elanmoc] MOC_LIST_NUM_STATES entering state 1 162s (process:2100): libfprint-SSM-DEBUG: 16:47:59.279: [elanmoc] FP_CMD_NUM_STATES entering state 0 162s (process:2100): libfprint-SSM-DEBUG: 16:47:59.280: [elanmoc] FP_CMD_NUM_STATES completed successfully 162s (process:2100): libfprint-SSM-DEBUG: 16:47:59.280: [elanmoc] FP_CMD_NUM_STATES entering state 1 162s (process:2100): libfprint-device-DEBUG: 16:47:59.280: Device reported listing completion 162s (process:2100): libfprint-SSM-DEBUG: 16:47:59.280: [elanmoc] MOC_LIST_NUM_STATES completed successfully 162s (process:2100): libfprint-SSM-DEBUG: 16:47:59.280: [elanmoc] FP_CMD_NUM_STATES completed successfully 162s (process:2100): libfprint-device-DEBUG: 16:47:59.280: Completing action FPI_DEVICE_ACTION_LIST in idle! 162s (process:2100): libfprint-device-DEBUG: 16:47:59.280: Not updating temperature model, device can run continuously! 162s (process:2100): libfprint-device-DEBUG: 16:47:59.280: Not updating temperature model, device can run continuously! 162s (process:2100): libfprint-SSM-DEBUG: 16:47:59.281: [elanmoc] IDENTIFY_NUM_STATES entering state 0 162s (process:2100): libfprint-elanmoc-DEBUG: 16:47:59.281: elanmoc elan_identify_run_state 162s (process:2100): libfprint-elanmoc-DEBUG: 16:47:59.281: elanmoc elan_identify_run_state IDENTIFY_SET_MODE 162s (process:2100): libfprint-SSM-DEBUG: 16:47:59.281: [elanmoc] FP_CMD_NUM_STATES entering state 0 162s (process:2100): libfprint-SSM-DEBUG: 16:47:59.281: [elanmoc] FP_CMD_NUM_STATES entering state 1 162s (process:2100): libfprint-SSM-DEBUG: 16:47:59.281: [elanmoc] IDENTIFY_NUM_STATES entering state 1 162s (process:2100): libfprint-elanmoc-DEBUG: 16:47:59.281: elanmoc elan_identify_run_state 162s (process:2100): libfprint-elanmoc-DEBUG: 16:47:59.281: elanmoc elan_identify_run_state VERIFY_WAIT_FINGER 162s (process:2100): libfprint-SSM-DEBUG: 16:47:59.281: [elanmoc] FP_CMD_NUM_STATES entering state 0 162s (process:2100): libfprint-SSM-DEBUG: 16:47:59.282: [elanmoc] FP_CMD_NUM_STATES completed successfully 162s (process:2100): libfprint-SSM-DEBUG: 16:47:59.282: [elanmoc] FP_CMD_NUM_STATES entering state 1 162s (process:2100): libfprint-elanmoc-DEBUG: 16:47:59.282: Verify was successful! for user: 0 mesg_code: 1 162s (process:2100): libfprint-SSM-DEBUG: 16:47:59.282: [elanmoc] FP_CMD_NUM_STATES entering state 0 162s (process:2100): libfprint-SSM-DEBUG: 16:47:59.283: [elanmoc] IDENTIFY_NUM_STATES completed successfully 162s (process:2100): libfprint-SSM-DEBUG: 16:47:59.283: [elanmoc] FP_CMD_NUM_STATES completed successfully 162s (process:2100): libfprint-SSM-DEBUG: 16:47:59.283: [elanmoc] FP_CMD_NUM_STATES entering state 1 162s (process:2100): libfprint-elanmoc-DEBUG: 16:47:59.283: Verify/Identify successful for: FP1-00000000-0-00000000-nobody 162s (process:2100): libfprint-device-DEBUG: 16:47:59.283: Device reported verify result 162s (process:2100): libfprint-device-DEBUG: 16:47:59.283: Device reported verify completion 162s (process:2100): libfprint-SSM-DEBUG: 16:47:59.283: [elanmoc] FP_CMD_NUM_STATES completed successfully 162s (process:2100): libfprint-device-DEBUG: 16:47:59.283: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 162s (process:2100): libfprint-device-DEBUG: 16:47:59.283: Not updating temperature model, device can run continuously! 162s (process:2100): libfprint-device-DEBUG: 16:47:59.284: Not updating temperature model, device can run continuously! 162s (process:2100): libfprint-SSM-DEBUG: 16:47:59.284: [elanmoc] IDENTIFY_NUM_STATES entering state 0 162s (process:2100): libfprint-elanmoc-DEBUG: 16:47:59.284: elanmoc elan_identify_run_state 162s (process:2100): libfprint-elanmoc-DEBUG: 16:47:59.284: elanmoc elan_identify_run_state IDENTIFY_SET_MODE 162s (process:2100): libfprint-SSM-DEBUG: 16:47:59.284: [elanmoc] FP_CMD_NUM_STATES entering state 0 162s (process:2100): libfprint-SSM-DEBUG: 16:47:59.284: [elanmoc] FP_CMD_NUM_STATES entering state 1 162s (process:2100): libfprint-SSM-DEBUG: 16:47:59.285: [elanmoc] IDENTIFY_NUM_STATES entering state 1 162s (process:2100): libfprint-elanmoc-DEBUG: 16:47:59.285: elanmoc elan_identify_run_state 162s (process:2100): libfprint-elanmoc-DEBUG: 16:47:59.285: elanmoc elan_identify_run_state VERIFY_WAIT_FINGER 162s (process:2100): libfprint-SSM-DEBUG: 16:47:59.285: [elanmoc] FP_CMD_NUM_STATES entering state 0 162s (process:2100): libfprint-SSM-DEBUG: 16:47:59.285: [elanmoc] FP_CMD_NUM_STATES completed successfully 162s (process:2100): libfprint-SSM-DEBUG: 16:47:59.285: [elanmoc] FP_CMD_NUM_STATES entering state 1 162s (process:2100): libfprint-elanmoc-DEBUG: 16:47:59.286: Verify was successful! for user: 0 mesg_code: 1 162s (process:2100): libfprint-SSM-DEBUG: 16:47:59.286: [elanmoc] FP_CMD_NUM_STATES entering state 0 162s (process:2100): libfprint-SSM-DEBUG: 16:47:59.286: [elanmoc] IDENTIFY_NUM_STATES completed successfully 162s (process:2100): libfprint-SSM-DEBUG: 16:47:59.286: [elanmoc] FP_CMD_NUM_STATES completed successfully 162s (process:2100): libfprint-SSM-DEBUG: 16:47:59.286: [elanmoc] FP_CMD_NUM_STATES entering state 1 162s (process:2100): libfprint-elanmoc-DEBUG: 16:47:59.287: Verify/Identify successful for: FP1-00000000-0-00000000-nobody 162s (process:2100): libfprint-device-DEBUG: 16:47:59.287: Device reported identify result 162s (process:2100): libfprint-device-DEBUG: 16:47:59.287: Device reported identify completion 162s (process:2100): libfprint-SSM-DEBUG: 16:47:59.287: [elanmoc] FP_CMD_NUM_STATES completed successfully 162s (process:2100): libfprint-device-DEBUG: 16:47:59.287: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 162s (process:2100): libfprint-device-DEBUG: 16:47:59.287: Not updating temperature model, device can run continuously! 162s (process:2100): libfprint-elanmoc-DEBUG: 16:47:59.287: Delete Finger, user_id = FP1-00000000-0-00000000-nobody! 162s (process:2100): libfprint-SSM-DEBUG: 16:47:59.287: [elanmoc] DELETE_NUM_STATES entering state 0 162s (process:2100): libfprint-SSM-DEBUG: 16:47:59.287: [elanmoc] FP_CMD_NUM_STATES entering state 0 162s (process:2100): libfprint-SSM-DEBUG: 16:47:59.288: [elanmoc] FP_CMD_NUM_STATES entering state 1 162s (process:2100): libfprint-device-DEBUG: 16:47:59.288: Device reported deletion completion 162s (process:2100): libfprint-SSM-DEBUG: 16:47:59.288: [elanmoc] DELETE_NUM_STATES completed successfully 162s (process:2100): libfprint-SSM-DEBUG: 16:47:59.288: [elanmoc] FP_CMD_NUM_STATES completed successfully 162s (process:2100): libfprint-device-DEBUG: 16:47:59.288: Completing action FPI_DEVICE_ACTION_DELETE in idle! 162s (process:2100): libfprint-device-DEBUG: 16:47:59.288: Not updating temperature model, device can run continuously! 162s (process:2100): libfprint-elanmoc-DEBUG: 16:47:59.288: Elanmoc dev_exit 162s (process:2100): libfprint-SSM-DEBUG: 16:47:59.288: [elanmoc] DEV_EXIT_STATES entering state 0 162s (process:2100): libfprint-SSM-DEBUG: 16:47:59.288: [elanmoc] FP_CMD_NUM_STATES entering state 0 162s (process:2100): libfprint-SSM-DEBUG: 16:47:59.289: [elanmoc] FP_CMD_NUM_STATES entering state 1 162s (process:2100): libfprint-SSM-DEBUG: 16:47:59.289: [elanmoc] DEV_EXIT_STATES completed successfully 162s (process:2100): libfprint-device-DEBUG: 16:47:59.289: Device reported close completion 162s (process:2100): libfprint-SSM-DEBUG: 16:47:59.289: [elanmoc] FP_CMD_NUM_STATES completed successfully 162s (process:2100): libfprint-device-DEBUG: 16:47:59.289: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 162s (process:2100): libfprint-device-DEBUG: 16:47:59.289: Not updating temperature model, device can run continuously! 162s enrolling 162s finger status: 162s enroll progress: (<__gi__.FpiDeviceElanmoc object at 0xff53f9adf9c0 (FpiDeviceElanmoc at 0x3b21f200)>, 1, None, None, None) 162s finger status: 162s enroll progress: (<__gi__.FpiDeviceElanmoc object at 0xff53f9adf9c0 (FpiDeviceElanmoc at 0x3b21f200)>, 2, None, None, None) 162s finger status: 162s enroll progress: (<__gi__.FpiDeviceElanmoc object at 0xff53f9adf9c0 (FpiDeviceElanmoc at 0x3b21f200)>, 3, None, None, None) 162s finger status: 162s enroll progress: (<__gi__.FpiDeviceElanmoc object at 0xff53f9adf9c0 (FpiDeviceElanmoc at 0x3b21f200)>, 4, None, None, None) 162s finger status: 162s enroll progress: (<__gi__.FpiDeviceElanmoc object at 0xff53f9adf9c0 (FpiDeviceElanmoc at 0x3b21f200)>, 5, None, None, None) 162s finger status: 162s enroll progress: (<__gi__.FpiDeviceElanmoc object at 0xff53f9adf9c0 (FpiDeviceElanmoc at 0x3b21f200)>, 6, None, None, None) 162s finger status: 162s enroll progress: (<__gi__.FpiDeviceElanmoc object at 0xff53f9adf9c0 (FpiDeviceElanmoc at 0x3b21f200)>, 7, None, None, None) 162s finger status: 162s enroll progress: (<__gi__.FpiDeviceElanmoc object at 0xff53f9adf9c0 (FpiDeviceElanmoc at 0x3b21f200)>, 7, None, None, GLib.Error('The finger was not centered properly, please try again.', 'fp - device - retry - quark', 2)) 162s finger status: 162s enroll progress: (<__gi__.FpiDeviceElanmoc object at 0xff53f9adf9c0 (FpiDeviceElanmoc at 0x3b21f200)>, 8, None, None, None) 162s finger status: 162s enroll progress: (<__gi__.FpiDeviceElanmoc object at 0xff53f9adf9c0 (FpiDeviceElanmoc at 0x3b21f200)>, 8, None, None, GLib.Error('The finger was not centered properly, please try again.', 'fp - device - retry - quark', 2)) 162s finger status: 162s enroll progress: (<__gi__.FpiDeviceElanmoc object at 0xff53f9adf9c0 (FpiDeviceElanmoc at 0x3b21f200)>, 9, 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:2096): DEBUG: 16:47:59.301: umockdev.vala:150: Removing test bed /tmp/umockdev.3TRGK2 162s (umockdev-run:2096): GLib-DEBUG: 16:47:59.306: unsetenv() is not thread-safe and should not be used after threads are created 162s PASS: libfprint-2/driver-elanmoc.test 162s Running test: libfprint-2/driver-uru4000-msv2.test 162s ** (umockdev-run:2108): DEBUG: 16:47:59.445: umockdev.vala:123: Created udev test bed /tmp/umockdev.0XGAK2 162s ** (umockdev-run:2108): DEBUG: 16:47:59.445: umockdev.vala:1297: parsing device description for /devices/pci0000:00/0000:00:14.0/usb1/1-10 162s ** (umockdev-run:2108): DEBUG: 16:47:59.446: umockdev.vala:1366: creating device /devices/pci0000:00/0000:00:14.0/usb1/1-10 (subsystem usb) 162s ** (umockdev-run:2108): DEBUG: 16:47:59.448: umockdev.vala:1411: create_node_for_device: creating file device /tmp/umockdev.0XGAK2/dev/bus/usb/001/047 162s ** (umockdev-run:2108): DEBUG: 16:47:59.448: umockdev.vala:1297: parsing device description for /devices/pci0000:00/0000:00:14.0/usb1 162s ** (umockdev-run:2108): DEBUG: 16:47:59.449: umockdev.vala:1366: creating device /devices/pci0000:00/0000:00:14.0/usb1 (subsystem usb) 162s ** (umockdev-run:2108): DEBUG: 16:47:59.451: umockdev.vala:1411: create_node_for_device: creating file device /tmp/umockdev.0XGAK2/dev/bus/usb/001/001 162s ** (umockdev-run:2108): DEBUG: 16:47:59.451: umockdev.vala:1297: parsing device description for /devices/pci0000:00/0000:00:14.0 162s ** (umockdev-run:2108): DEBUG: 16:47:59.452: umockdev.vala:1366: creating device /devices/pci0000:00/0000:00:14.0 (subsystem pci) 162s (process:2112): libfprint-context-DEBUG: 16:47:59.554: Initializing FpContext (libfprint version 1.94.7+tod1) 162s (process:2112): libfprint-tod-DEBUG: 16:47:59.554: Impossible to load the shared drivers dir Error opening directory “/usr/lib/aarch64-linux-gnu/libfprint-2/tod-1”: No such file or directory 162s (process:2112): libfprint-context-DEBUG: 16:47:59.556: No driver found for USB device 1D6B:0002 162s (process:2112): libfprint-device-DEBUG: 16:47:59.557: Device reported probe completion 162s (process:2112): libfprint-device-DEBUG: 16:47:59.557: Completing action FPI_DEVICE_ACTION_PROBE in idle! 162s (process:2112): libfprint-device-DEBUG: 16:47:59.557: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 162s (process:2112): GLib-DEBUG: 16:47:59.560: setenv()/putenv() are not thread-safe and should not be used after threads are created 162s (process:2112): libfprint-image_device-DEBUG: 16:47:59.692: Image device open completed 162s (process:2112): libfprint-device-DEBUG: 16:47:59.692: Device reported open completion 162s (process:2112): libfprint-device-DEBUG: 16:47:59.692: Completing action FPI_DEVICE_ACTION_OPEN in idle! 162s (process:2112): libfprint-device-DEBUG: 16:47:59.692: Updated temperature model after 0.14 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 162s (process:2112): libfprint-device-DEBUG: 16:47:59.692: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 162s (process:2112): libfprint-image_device-DEBUG: 16:47:59.692: Activating image device 162s (process:2112): libfprint-image_device-DEBUG: 16:47:59.692: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING 162s (process:2112): libfprint-SSM-DEBUG: 16:47:59.693: [uru4000] INIT_NUM_STATES entering state 0 162s (process:2112): libfprint-uru4000-DEBUG: 16:47:59.693: read 1 regs at 7 162s (process:2112): libfprint-uru4000-DEBUG: 16:47:59.693: reg value 3 162s (process:2112): libfprint-SSM-DEBUG: 16:47:59.693: [uru4000] INIT_NUM_STATES entering state 1 162s (process:2112): libfprint-SSM-DEBUG: 16:47:59.693: [uru4000] INIT_NUM_STATES entering state 3 162s (process:2112): libfprint-uru4000-DEBUG: 16:47:59.693: set 83 162s (process:2112): libfprint-SSM-DEBUG: 16:47:59.694: [uru4000] INIT_NUM_STATES entering state 4 162s (process:2112): libfprint-SSM-DEBUG: 16:47:59.694: [uru4000] POWERUP_NUM_STATES entering state 0 162s (process:2112): libfprint-SSM-DEBUG: 16:47:59.694: [uru4000] POWERUP_NUM_STATES entering state 1 162s (process:2112): libfprint-uru4000-DEBUG: 16:47:59.694: set 03 162s (process:2112): libfprint-SSM-DEBUG: 16:47:59.694: [uru4000] POWERUP_NUM_STATES entering state 2 162s (process:2112): libfprint-uru4000-DEBUG: 16:47:59.694: read 1 regs at 7 162s (process:2112): libfprint-uru4000-DEBUG: 16:47:59.695: reg value 83 162s (process:2112): libfprint-SSM-DEBUG: 16:47:59.695: [uru4000] POWERUP_NUM_STATES entering state 3 162s (process:2112): libfprint-SSM-DEBUG: 16:47:59.695: [uru4000] POWERUP_NUM_STATES entering state 4 162s (process:2112): libfprint-SSM-DEBUG: 16:47:59.705: [uru4000] POWERUP_NUM_STATES entering state 5 162s (process:2112): libfprint-uru4000-DEBUG: 16:47:59.705: 50706174: ../libfprint/drivers/uru4000.c:291 162s (process:2112): libfprint-SSM-DEBUG: 16:47:59.729: [uru4000] POWERUP_NUM_STATES entering state 6 162s (process:2112): libfprint-SSM-DEBUG: 16:47:59.729: [uru4000] POWERUP_NUM_STATES entering state 1 162s (process:2112): libfprint-uru4000-DEBUG: 16:47:59.729: set 03 162s (process:2112): libfprint-SSM-DEBUG: 16:47:59.729: [uru4000] POWERUP_NUM_STATES entering state 2 162s (process:2112): libfprint-uru4000-DEBUG: 16:47:59.729: read 1 regs at 7 162s (process:2112): libfprint-uru4000-DEBUG: 16:47:59.730: reg value 3 162s (process:2112): libfprint-SSM-DEBUG: 16:47:59.730: [uru4000] POWERUP_NUM_STATES entering state 3 162s (process:2112): libfprint-SSM-DEBUG: 16:47:59.730: [uru4000] POWERUP_NUM_STATES completed successfully 162s (process:2112): libfprint-SSM-DEBUG: 16:47:59.730: [uru4000] INIT_NUM_STATES entering state 5 162s (process:2112): libfprint-uru4000-DEBUG: 16:47:59.731: recv irq type 56aa 162s (process:2112): libfprint-uru4000-DEBUG: 16:47:59.731: late scanpwr interrupt 162s (process:2112): libfprint-SSM-DEBUG: 16:47:59.731: [uru4000] INIT_NUM_STATES entering state 6 162s (process:2112): libfprint-SSM-DEBUG: 16:47:59.731: [uru4000] INIT_NUM_STATES entering state 7 162s (process:2112): libfprint-uru4000-DEBUG: 16:47:59.731: read 16 regs at f0 162s (process:2112): libfprint-uru4000-DEBUG: 16:47:59.731: reg value 50 162s (process:2112): libfprint-SSM-DEBUG: 16:47:59.731: [uru4000] INIT_NUM_STATES entering state 8 162s (process:2112): libfprint-uru4000-DEBUG: 16:47:59.731: Versions 0059 and 0034 162s (process:2112): libfprint-SSM-DEBUG: 16:47:59.731: [uru4000] INIT_NUM_STATES completed successfully 162s (process:2112): libfprint-image_device-DEBUG: 16:47:59.731: Image device activation completed 162s (process:2112): libfprint-image_device-DEBUG: 16:47:59.732: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE 162s (process:2112): libfprint-image_device-DEBUG: 16:47:59.732: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 162s (process:2112): libfprint-uru4000-DEBUG: 16:47:59.732: wait finger on 162s (process:2112): libfprint-device-DEBUG: 16:47:59.732: Device reported finger status change: FP_FINGER_STATUS_NEEDED 162s (process:2112): libfprint-uru4000-DEBUG: 16:47:59.733: recv irq type 0101 162s (process:2112): libfprint-device-DEBUG: 16:47:59.733: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 162s (process:2112): libfprint-image_device-DEBUG: 16:47:59.733: Image device reported finger status: on 162s (process:2112): libfprint-image_device-DEBUG: 16:47:59.733: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 162s (process:2112): libfprint-uru4000-DEBUG: 16:47:59.733: starting capture 162s (process:2112): libfprint-uru4000-DEBUG: 16:47:59.733: Image encryption seed: 1374298404 162s (process:2112): libfprint-SSM-DEBUG: 16:47:59.733: [uru4000] IMAGING_NUM_STATES entering state 0 162s (process:2112): libfprint-SSM-DEBUG: 16:47:59.736: [uru4000] IMAGING_NUM_STATES entering state 1 162s (process:2112): libfprint-uru4000-DEBUG: 16:47:59.736: hw header lines 289 162s (process:2112): libfprint-uru4000-DEBUG: 16:47:59.736: dev2: 10849 162s (process:2112): libfprint-uru4000-DEBUG: 16:47:59.736: image seems to be encrypted 162s (process:2112): libfprint-SSM-DEBUG: 16:47:59.737: [uru4000] IMAGING_NUM_STATES entering state 2 162s (process:2112): libfprint-uru4000-DEBUG: 16:47:59.737: read 4 regs at 34 162s (process:2112): libfprint-uru4000-DEBUG: 16:47:59.737: reg value 7b 162s (process:2112): libfprint-SSM-DEBUG: 16:47:59.737: [uru4000] IMAGING_NUM_STATES entering state 3 162s (process:2112): libfprint-uru4000-DEBUG: 16:47:59.737: encryption id 05 -> key db896f5f 162s (process:2112): libfprint-uru4000-DEBUG: 16:47:59.737: 0 02 67 162s (process:2112): libfprint-uru4000-DEBUG: 16:47:59.737: decoding 67 lines 162s (process:2112): libfprint-uru4000-DEBUG: 16:47:59.737: 1 00 1 162s (process:2112): libfprint-uru4000-DEBUG: 16:47:59.737: skipping 1 lines 162s (process:2112): libfprint-uru4000-DEBUG: 16:47:59.737: 2 02 49 162s (process:2112): libfprint-uru4000-DEBUG: 16:47:59.737: decoding 49 lines 162s (process:2112): libfprint-uru4000-DEBUG: 16:47:59.737: 3 01 1 162s (process:2112): libfprint-uru4000-DEBUG: 16:47:59.737: skipping 1 lines 162s (process:2112): libfprint-uru4000-DEBUG: 16:47:59.737: 4 00 1 162s (process:2112): libfprint-uru4000-DEBUG: 16:47:59.737: skipping 1 lines 162s (process:2112): libfprint-uru4000-DEBUG: 16:47:59.737: 5 02 49 162s (process:2112): libfprint-uru4000-DEBUG: 16:47:59.737: decoding 49 lines 162s (process:2112): libfprint-uru4000-DEBUG: 16:47:59.737: 6 00 1 162s (process:2112): libfprint-uru4000-DEBUG: 16:47:59.737: skipping 1 lines 162s (process:2112): libfprint-uru4000-DEBUG: 16:47:59.738: 7 02 121 162s (process:2112): libfprint-uru4000-DEBUG: 16:47:59.738: decoding 121 lines 162s (process:2112): libfprint-SSM-DEBUG: 16:47:59.738: [uru4000] IMAGING_NUM_STATES entering state 4 162s (process:2112): libfprint-image_device-DEBUG: 16:47:59.738: Image device captured an image 162s (process:2112): libfprint-image_device-DEBUG: 16:47:59.739: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 162s (process:2112): libfprint-device-DEBUG: 16:47:59.739: Device reported finger status change: FP_FINGER_STATUS_PRESENT 162s (process:2112): libfprint-SSM-DEBUG: 16:47:59.739: [uru4000] IMAGING_NUM_STATES completed successfully 162s (process:2112): libfprint-uru4000-DEBUG: 16:47:59.739: await finger off 162s (process:2112): libfprint-uru4000-DEBUG: 16:47:59.740: recv irq type 0200 162s (process:2112): libfprint-device-DEBUG: 16:47:59.740: Device reported finger status change: FP_FINGER_STATUS_NONE 162s (process:2112): libfprint-image_device-DEBUG: 16:47:59.740: Image device reported finger status: off 162s (process:2112): libfprint-image_device-DEBUG: 16:47:59.740: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 162s (process:2112): libfprint-image_device-DEBUG: 16:47:59.740: Deactivating image device 162s (process:2112): libfprint-image_device-DEBUG: 16:47:59.740: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_DEACTIVATING 162s (process:2112): libfprint-uru4000-DEBUG: 16:47:59.740: deactivating 162s (process:2112): libfprint-uru4000-DEBUG: 16:47:59.743: cancelled 162s (process:2112): libfprint-image_device-DEBUG: 16:47:59.743: Image device deactivation completed 162s (process:2112): libfprint-image_device-DEBUG: 16:47:59.743: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE 162s (process:2112): libfprint-image-DEBUG: 16:47:59.777: Minutiae scan completed in 0.038345 secs 162s (process:2112): libfprint-device-DEBUG: 16:47:59.777: Device reported capture completion 162s (process:2112): libfprint-device-DEBUG: 16:47:59.777: Completing action FPI_DEVICE_ACTION_CAPTURE in idle! 162s (process:2112): libfprint-device-DEBUG: 16:47:59.777: Updated temperature model after 0.08 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 162s (process:2112): libfprint-image_device-DEBUG: 16:47:59.801: Image device close completed 162s (process:2112): libfprint-device-DEBUG: 16:47:59.801: Device reported close completion 162s (process:2112): libfprint-device-DEBUG: 16:47:59.801: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 162s (process:2112): libfprint-device-DEBUG: 16:47:59.802: Updated temperature model after 0.02 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 162s ** (umockdev-run:2108): DEBUG: 16:47:59.948: umockdev.vala:150: Removing test bed /tmp/umockdev.0XGAK2 162s (umockdev-run:2108): GLib-DEBUG: 16:47:59.951: unsetenv() is not thread-safe and should not be used after threads are created 162s Comparing PNGs /tmp/libfprint-umockdev-test-fzudcxt1/capture.png and /usr/share/installed-tests/libfprint-2/uru4000-msv2/capture.png 162s PASS: libfprint-2/driver-uru4000-msv2.test 162s Running test: libfprint-2/driver-goodixmoc.test 163s ** (umockdev-run:2121): DEBUG: 16:48:00.063: umockdev.vala:123: Created udev test bed /tmp/umockdev.72BDK2 163s ** (umockdev-run:2121): DEBUG: 16:48:00.064: umockdev.vala:1297: parsing device description for /devices/pci0000:00/0000:00:14.0/usb3/3-9 163s ** (umockdev-run:2121): DEBUG: 16:48:00.065: umockdev.vala:1366: creating device /devices/pci0000:00/0000:00:14.0/usb3/3-9 (subsystem usb) 163s ** (umockdev-run:2121): DEBUG: 16:48:00.067: umockdev.vala:1411: create_node_for_device: creating file device /tmp/umockdev.72BDK2/dev/bus/usb/003/004 163s ** (umockdev-run:2121): DEBUG: 16:48:00.068: umockdev.vala:1297: parsing device description for /devices/pci0000:00/0000:00:14.0/usb3 163s ** (umockdev-run:2121): DEBUG: 16:48:00.069: umockdev.vala:1366: creating device /devices/pci0000:00/0000:00:14.0/usb3 (subsystem usb) 163s ** (umockdev-run:2121): DEBUG: 16:48:00.071: umockdev.vala:1411: create_node_for_device: creating file device /tmp/umockdev.72BDK2/dev/bus/usb/003/001 163s ** (umockdev-run:2121): DEBUG: 16:48:00.071: umockdev.vala:1297: parsing device description for /devices/pci0000:00/0000:00:14.0 163s ** (umockdev-run:2121): DEBUG: 16:48:00.071: umockdev.vala:1366: creating device /devices/pci0000:00/0000:00:14.0 (subsystem pci) 163s (process:2125): libfprint-context-DEBUG: 16:48:00.136: Initializing FpContext (libfprint version 1.94.7+tod1) 163s (process:2125): libfprint-tod-DEBUG: 16:48:00.136: Impossible to load the shared drivers dir Error opening directory “/usr/lib/aarch64-linux-gnu/libfprint-2/tod-1”: No such file or directory 163s (process:2125): libfprint-context-DEBUG: 16:48:00.138: No driver found for USB device 1D6B:0002 163s (process:2125): libfprint-device-DEBUG: 16:48:00.140: Device reported probe completion 163s (process:2125): libfprint-device-DEBUG: 16:48:00.140: Completing action FPI_DEVICE_ACTION_PROBE in idle! 163s (process:2125): libfprint-device-DEBUG: 16:48:00.140: Not updating temperature model, device can run continuously! 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.142: [goodixmoc] FP_INIT_NUM_STATES entering state 0 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.142: [goodixmoc] FP_CMD_NUM_STATES entering state 0 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.142: [goodixmoc] FP_CMD_NUM_STATES entering state 1 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.143: [goodixmoc] FP_CMD_NUM_STATES entering state 1 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.143: [goodixmoc] FP_CMD_NUM_STATES entering state 2 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.144: [goodixmoc] FP_CMD_NUM_STATES entering state 2 163s (process:2125): libfprint-goodixmoc-DEBUG: 16:48:00.144: Firmware type: APP 163s (process:2125): libfprint-goodixmoc-DEBUG: 16:48:00.144: Firmware version: 01000274 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.144: [goodixmoc] FP_INIT_NUM_STATES entering state 1 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.144: [goodixmoc] FP_CMD_NUM_STATES entering state 0 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.145: [goodixmoc] FP_CMD_NUM_STATES completed successfully 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.145: [goodixmoc] FP_CMD_NUM_STATES entering state 1 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.145: [goodixmoc] FP_CMD_NUM_STATES entering state 1 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.146: [goodixmoc] FP_CMD_NUM_STATES entering state 2 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.146: [goodixmoc] FP_CMD_NUM_STATES entering state 2 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.146: [goodixmoc] FP_INIT_NUM_STATES entering state 2 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.146: [goodixmoc] FP_CMD_NUM_STATES entering state 0 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.147: [goodixmoc] FP_CMD_NUM_STATES completed successfully 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.147: [goodixmoc] FP_CMD_NUM_STATES entering state 1 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.147: [goodixmoc] FP_CMD_NUM_STATES entering state 1 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.148: [goodixmoc] FP_CMD_NUM_STATES entering state 2 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.148: [goodixmoc] FP_CMD_NUM_STATES entering state 2 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.149: [goodixmoc] FP_INIT_NUM_STATES completed successfully 163s (process:2125): libfprint-device-DEBUG: 16:48:00.149: Device reported open completion 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.149: [goodixmoc] FP_CMD_NUM_STATES completed successfully 163s (process:2125): libfprint-device-DEBUG: 16:48:00.149: Completing action FPI_DEVICE_ACTION_OPEN in idle! 163s (process:2125): libfprint-device-DEBUG: 16:48:00.149: Not updating temperature model, device can run continuously! 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.149: [goodixmoc] FP_CMD_NUM_STATES entering state 0 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.149: [goodixmoc] FP_CMD_NUM_STATES entering state 1 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.150: [goodixmoc] FP_CMD_NUM_STATES entering state 1 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.150: [goodixmoc] FP_CMD_NUM_STATES entering state 2 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.150: [goodixmoc] FP_CMD_NUM_STATES entering state 2 163s (process:2125): libfprint-goodixmoc-DEBUG: 16:48:00.151: Successfully cleared storage 163s (process:2125): libfprint-device-DEBUG: 16:48:00.151: Device reported deletion completion 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.151: [goodixmoc] FP_CMD_NUM_STATES completed successfully 163s (process:2125): libfprint-device-DEBUG: 16:48:00.151: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 163s (process:2125): libfprint-device-DEBUG: 16:48:00.151: Not updating temperature model, device can run continuously! 163s (process:2125): libfprint-device-DEBUG: 16:48:00.152: Not updating temperature model, device can run continuously! 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.152: [goodixmoc] enroll entering state 0 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.152: [goodixmoc] FP_CMD_NUM_STATES entering state 0 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.152: [goodixmoc] FP_CMD_NUM_STATES entering state 1 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.153: [goodixmoc] FP_CMD_NUM_STATES entering state 1 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.153: [goodixmoc] FP_CMD_NUM_STATES entering state 2 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.154: [goodixmoc] FP_CMD_NUM_STATES entering state 2 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.154: [goodixmoc] enroll entering state 1 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.154: [goodixmoc] FP_CMD_NUM_STATES entering state 0 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.154: [goodixmoc] FP_CMD_NUM_STATES completed successfully 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.155: [goodixmoc] FP_CMD_NUM_STATES entering state 1 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.155: [goodixmoc] FP_CMD_NUM_STATES entering state 1 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.155: [goodixmoc] FP_CMD_NUM_STATES entering state 2 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.156: [goodixmoc] FP_CMD_NUM_STATES entering state 2 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.156: [goodixmoc] enroll entering state 2 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.156: [goodixmoc] FP_CMD_NUM_STATES entering state 0 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.156: [goodixmoc] FP_CMD_NUM_STATES completed successfully 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.157: [goodixmoc] FP_CMD_NUM_STATES entering state 1 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.157: [goodixmoc] FP_CMD_NUM_STATES entering state 1 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.157: [goodixmoc] FP_CMD_NUM_STATES entering state 2 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.158: [goodixmoc] FP_CMD_NUM_STATES entering state 2 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.158: [goodixmoc] enroll entering state 3 163s (process:2125): libfprint-device-DEBUG: 16:48:00.158: Device reported finger status change: FP_FINGER_STATUS_NEEDED 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.158: [goodixmoc] FP_CMD_NUM_STATES entering state 0 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.159: [goodixmoc] FP_CMD_NUM_STATES completed successfully 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.159: [goodixmoc] FP_CMD_NUM_STATES entering state 1 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.159: [goodixmoc] FP_CMD_NUM_STATES entering state 1 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.160: [goodixmoc] FP_CMD_NUM_STATES entering state 2 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.160: [goodixmoc] FP_CMD_NUM_STATES entering state 2 163s (process:2125): libfprint-device-DEBUG: 16:48:00.160: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.161: [goodixmoc] enroll entering state 4 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.161: [goodixmoc] FP_CMD_NUM_STATES entering state 0 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.161: [goodixmoc] FP_CMD_NUM_STATES completed successfully 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.161: [goodixmoc] FP_CMD_NUM_STATES entering state 1 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.161: [goodixmoc] FP_CMD_NUM_STATES entering state 1 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.162: [goodixmoc] FP_CMD_NUM_STATES entering state 2 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.162: [goodixmoc] FP_CMD_NUM_STATES entering state 2 163s (process:2125): libfprint-device-DEBUG: 16:48:00.163: Device reported enroll progress, reported 1 of 12 have been completed 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.163: [goodixmoc] enroll entering state 5 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.163: [goodixmoc] FP_CMD_NUM_STATES entering state 0 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.163: [goodixmoc] FP_CMD_NUM_STATES completed successfully 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.163: [goodixmoc] FP_CMD_NUM_STATES entering state 1 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.163: [goodixmoc] FP_CMD_NUM_STATES entering state 1 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.164: [goodixmoc] FP_CMD_NUM_STATES entering state 2 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.164: [goodixmoc] FP_CMD_NUM_STATES entering state 2 163s (process:2125): libfprint-device-DEBUG: 16:48:00.165: Device reported finger status change: FP_FINGER_STATUS_NEEDED 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.165: [goodixmoc] enroll entering state 3 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.165: [goodixmoc] FP_CMD_NUM_STATES entering state 0 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.165: [goodixmoc] FP_CMD_NUM_STATES completed successfully 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.165: [goodixmoc] FP_CMD_NUM_STATES entering state 1 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.166: [goodixmoc] FP_CMD_NUM_STATES entering state 1 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.166: [goodixmoc] FP_CMD_NUM_STATES entering state 2 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.166: [goodixmoc] FP_CMD_NUM_STATES entering state 2 163s (process:2125): libfprint-device-DEBUG: 16:48:00.167: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.167: [goodixmoc] enroll entering state 4 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.167: [goodixmoc] FP_CMD_NUM_STATES entering state 0 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.167: [goodixmoc] FP_CMD_NUM_STATES completed successfully 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.167: [goodixmoc] FP_CMD_NUM_STATES entering state 1 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.168: [goodixmoc] FP_CMD_NUM_STATES entering state 1 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.168: [goodixmoc] FP_CMD_NUM_STATES entering state 2 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.169: [goodixmoc] FP_CMD_NUM_STATES entering state 2 163s (process:2125): libfprint-device-DEBUG: 16:48:00.169: Device reported enroll progress, reported 2 of 12 have been completed 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.169: [goodixmoc] enroll entering state 5 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.169: [goodixmoc] FP_CMD_NUM_STATES entering state 0 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.169: [goodixmoc] FP_CMD_NUM_STATES completed successfully 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.170: [goodixmoc] FP_CMD_NUM_STATES entering state 1 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.170: [goodixmoc] FP_CMD_NUM_STATES entering state 1 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.170: [goodixmoc] FP_CMD_NUM_STATES entering state 2 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.171: [goodixmoc] FP_CMD_NUM_STATES entering state 2 163s (process:2125): libfprint-device-DEBUG: 16:48:00.171: Device reported finger status change: FP_FINGER_STATUS_NEEDED 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.171: [goodixmoc] enroll entering state 3 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.171: [goodixmoc] FP_CMD_NUM_STATES entering state 0 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.172: [goodixmoc] FP_CMD_NUM_STATES completed successfully 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.172: [goodixmoc] FP_CMD_NUM_STATES entering state 1 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.172: [goodixmoc] FP_CMD_NUM_STATES entering state 1 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.172: [goodixmoc] FP_CMD_NUM_STATES entering state 2 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.173: [goodixmoc] FP_CMD_NUM_STATES entering state 2 163s (process:2125): libfprint-device-DEBUG: 16:48:00.173: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.173: [goodixmoc] enroll entering state 4 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.173: [goodixmoc] FP_CMD_NUM_STATES entering state 0 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.174: [goodixmoc] FP_CMD_NUM_STATES completed successfully 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.174: [goodixmoc] FP_CMD_NUM_STATES entering state 1 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.174: [goodixmoc] FP_CMD_NUM_STATES entering state 1 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.175: [goodixmoc] FP_CMD_NUM_STATES entering state 2 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.175: [goodixmoc] FP_CMD_NUM_STATES entering state 2 163s (process:2125): libfprint-device-DEBUG: 16:48:00.176: Device reported enroll progress, reported 3 of 12 have been completed 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.176: [goodixmoc] enroll entering state 5 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.176: [goodixmoc] FP_CMD_NUM_STATES entering state 0 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.176: [goodixmoc] FP_CMD_NUM_STATES completed successfully 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.176: [goodixmoc] FP_CMD_NUM_STATES entering state 1 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.176: [goodixmoc] FP_CMD_NUM_STATES entering state 1 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.177: [goodixmoc] FP_CMD_NUM_STATES entering state 2 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.177: [goodixmoc] FP_CMD_NUM_STATES entering state 2 163s (process:2125): libfprint-device-DEBUG: 16:48:00.178: Device reported finger status change: FP_FINGER_STATUS_NEEDED 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.178: [goodixmoc] enroll entering state 3 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.178: [goodixmoc] FP_CMD_NUM_STATES entering state 0 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.178: [goodixmoc] FP_CMD_NUM_STATES completed successfully 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.178: [goodixmoc] FP_CMD_NUM_STATES entering state 1 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.179: [goodixmoc] FP_CMD_NUM_STATES entering state 1 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.179: [goodixmoc] FP_CMD_NUM_STATES entering state 2 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.180: [goodixmoc] FP_CMD_NUM_STATES entering state 2 163s (process:2125): libfprint-device-DEBUG: 16:48:00.180: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.180: [goodixmoc] enroll entering state 4 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.180: [goodixmoc] FP_CMD_NUM_STATES entering state 0 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.180: [goodixmoc] FP_CMD_NUM_STATES completed successfully 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.180: [goodixmoc] FP_CMD_NUM_STATES entering state 1 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.181: [goodixmoc] FP_CMD_NUM_STATES entering state 1 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.181: [goodixmoc] FP_CMD_NUM_STATES entering state 2 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.182: [goodixmoc] FP_CMD_NUM_STATES entering state 2 163s (process:2125): libfprint-device-DEBUG: 16:48:00.182: Device reported enroll progress, reported 4 of 12 have been completed 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.182: [goodixmoc] enroll entering state 5 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.182: [goodixmoc] FP_CMD_NUM_STATES entering state 0 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.182: [goodixmoc] FP_CMD_NUM_STATES completed successfully 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.183: [goodixmoc] FP_CMD_NUM_STATES entering state 1 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.183: [goodixmoc] FP_CMD_NUM_STATES entering state 1 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.183: [goodixmoc] FP_CMD_NUM_STATES entering state 2 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.184: [goodixmoc] FP_CMD_NUM_STATES entering state 2 163s (process:2125): libfprint-device-DEBUG: 16:48:00.184: Device reported finger status change: FP_FINGER_STATUS_NEEDED 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.184: [goodixmoc] enroll entering state 3 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.184: [goodixmoc] FP_CMD_NUM_STATES entering state 0 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.185: [goodixmoc] FP_CMD_NUM_STATES completed successfully 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.185: [goodixmoc] FP_CMD_NUM_STATES entering state 1 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.185: [goodixmoc] FP_CMD_NUM_STATES entering state 1 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.186: [goodixmoc] FP_CMD_NUM_STATES entering state 2 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.186: [goodixmoc] FP_CMD_NUM_STATES entering state 2 163s (process:2125): libfprint-device-DEBUG: 16:48:00.186: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.187: [goodixmoc] enroll entering state 4 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.187: [goodixmoc] FP_CMD_NUM_STATES entering state 0 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.187: [goodixmoc] FP_CMD_NUM_STATES completed successfully 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.187: [goodixmoc] FP_CMD_NUM_STATES entering state 1 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.187: [goodixmoc] FP_CMD_NUM_STATES entering state 1 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.188: [goodixmoc] FP_CMD_NUM_STATES entering state 2 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.188: [goodixmoc] FP_CMD_NUM_STATES entering state 2 163s (process:2125): libfprint-device-DEBUG: 16:48:00.189: Device reported enroll progress, reported 5 of 12 have been completed 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.189: [goodixmoc] enroll entering state 5 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.189: [goodixmoc] FP_CMD_NUM_STATES entering state 0 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.189: [goodixmoc] FP_CMD_NUM_STATES completed successfully 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.189: [goodixmoc] FP_CMD_NUM_STATES entering state 1 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.190: [goodixmoc] FP_CMD_NUM_STATES entering state 1 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.190: [goodixmoc] FP_CMD_NUM_STATES entering state 2 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.190: [goodixmoc] FP_CMD_NUM_STATES entering state 2 163s (process:2125): libfprint-device-DEBUG: 16:48:00.191: Device reported finger status change: FP_FINGER_STATUS_NEEDED 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.191: [goodixmoc] enroll entering state 3 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.191: [goodixmoc] FP_CMD_NUM_STATES entering state 0 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.191: [goodixmoc] FP_CMD_NUM_STATES completed successfully 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.191: [goodixmoc] FP_CMD_NUM_STATES entering state 1 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.192: [goodixmoc] FP_CMD_NUM_STATES entering state 1 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.192: [goodixmoc] FP_CMD_NUM_STATES entering state 2 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.192: [goodixmoc] FP_CMD_NUM_STATES entering state 2 163s (process:2125): libfprint-device-DEBUG: 16:48:00.193: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.193: [goodixmoc] enroll entering state 4 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.193: [goodixmoc] FP_CMD_NUM_STATES entering state 0 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.193: [goodixmoc] FP_CMD_NUM_STATES completed successfully 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.193: [goodixmoc] FP_CMD_NUM_STATES entering state 1 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.194: [goodixmoc] FP_CMD_NUM_STATES entering state 1 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.194: [goodixmoc] FP_CMD_NUM_STATES entering state 2 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.195: [goodixmoc] FP_CMD_NUM_STATES entering state 2 163s (process:2125): libfprint-device-DEBUG: 16:48:00.195: Device reported enroll progress, reported 6 of 12 have been completed 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.195: [goodixmoc] enroll entering state 5 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.195: [goodixmoc] FP_CMD_NUM_STATES entering state 0 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.195: [goodixmoc] FP_CMD_NUM_STATES completed successfully 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.196: [goodixmoc] FP_CMD_NUM_STATES entering state 1 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.196: [goodixmoc] FP_CMD_NUM_STATES entering state 1 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.196: [goodixmoc] FP_CMD_NUM_STATES entering state 2 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.197: [goodixmoc] FP_CMD_NUM_STATES entering state 2 163s (process:2125): libfprint-device-DEBUG: 16:48:00.197: Device reported finger status change: FP_FINGER_STATUS_NEEDED 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.197: [goodixmoc] enroll entering state 3 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.197: [goodixmoc] FP_CMD_NUM_STATES entering state 0 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.198: [goodixmoc] FP_CMD_NUM_STATES completed successfully 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.198: [goodixmoc] FP_CMD_NUM_STATES entering state 1 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.198: [goodixmoc] FP_CMD_NUM_STATES entering state 1 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.199: [goodixmoc] FP_CMD_NUM_STATES entering state 2 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.199: [goodixmoc] FP_CMD_NUM_STATES entering state 2 163s (process:2125): libfprint-device-DEBUG: 16:48:00.199: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.199: [goodixmoc] enroll entering state 4 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.199: [goodixmoc] FP_CMD_NUM_STATES entering state 0 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.200: [goodixmoc] FP_CMD_NUM_STATES completed successfully 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.200: [goodixmoc] FP_CMD_NUM_STATES entering state 1 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.200: [goodixmoc] FP_CMD_NUM_STATES entering state 1 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.201: [goodixmoc] FP_CMD_NUM_STATES entering state 2 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.201: [goodixmoc] FP_CMD_NUM_STATES entering state 2 163s (process:2125): libfprint-device-DEBUG: 16:48:00.202: Device reported enroll progress, reported 7 of 12 have been completed 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.202: [goodixmoc] enroll entering state 5 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.202: [goodixmoc] FP_CMD_NUM_STATES entering state 0 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.202: [goodixmoc] FP_CMD_NUM_STATES completed successfully 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.202: [goodixmoc] FP_CMD_NUM_STATES entering state 1 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.202: [goodixmoc] FP_CMD_NUM_STATES entering state 1 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.203: [goodixmoc] FP_CMD_NUM_STATES entering state 2 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.203: [goodixmoc] FP_CMD_NUM_STATES entering state 2 163s (process:2125): libfprint-device-DEBUG: 16:48:00.204: Device reported finger status change: FP_FINGER_STATUS_NEEDED 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.204: [goodixmoc] enroll entering state 3 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.204: [goodixmoc] FP_CMD_NUM_STATES entering state 0 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.204: [goodixmoc] FP_CMD_NUM_STATES completed successfully 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.204: [goodixmoc] FP_CMD_NUM_STATES entering state 1 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.205: [goodixmoc] FP_CMD_NUM_STATES entering state 1 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.205: [goodixmoc] FP_CMD_NUM_STATES entering state 2 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.206: [goodixmoc] FP_CMD_NUM_STATES entering state 2 163s (process:2125): libfprint-device-DEBUG: 16:48:00.206: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.206: [goodixmoc] enroll entering state 4 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.206: [goodixmoc] FP_CMD_NUM_STATES entering state 0 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.206: [goodixmoc] FP_CMD_NUM_STATES completed successfully 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.206: [goodixmoc] FP_CMD_NUM_STATES entering state 1 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.207: [goodixmoc] FP_CMD_NUM_STATES entering state 1 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.207: [goodixmoc] FP_CMD_NUM_STATES entering state 2 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.208: [goodixmoc] FP_CMD_NUM_STATES entering state 2 163s (process:2125): libfprint-device-DEBUG: 16:48:00.208: Device reported enroll progress, reported 8 of 12 have been completed 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.208: [goodixmoc] enroll entering state 5 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.208: [goodixmoc] FP_CMD_NUM_STATES entering state 0 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.208: [goodixmoc] FP_CMD_NUM_STATES completed successfully 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.209: [goodixmoc] FP_CMD_NUM_STATES entering state 1 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.209: [goodixmoc] FP_CMD_NUM_STATES entering state 1 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.210: [goodixmoc] FP_CMD_NUM_STATES entering state 2 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.210: [goodixmoc] FP_CMD_NUM_STATES entering state 2 163s (process:2125): libfprint-device-DEBUG: 16:48:00.210: Device reported finger status change: FP_FINGER_STATUS_NEEDED 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.210: [goodixmoc] enroll entering state 3 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.210: [goodixmoc] FP_CMD_NUM_STATES entering state 0 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.211: [goodixmoc] FP_CMD_NUM_STATES completed successfully 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.211: [goodixmoc] FP_CMD_NUM_STATES entering state 1 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.211: [goodixmoc] FP_CMD_NUM_STATES entering state 1 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.212: [goodixmoc] FP_CMD_NUM_STATES entering state 2 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.212: [goodixmoc] FP_CMD_NUM_STATES entering state 2 163s (process:2125): libfprint-device-DEBUG: 16:48:00.213: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.213: [goodixmoc] enroll entering state 4 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.213: [goodixmoc] FP_CMD_NUM_STATES entering state 0 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.213: [goodixmoc] FP_CMD_NUM_STATES completed successfully 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.213: [goodixmoc] FP_CMD_NUM_STATES entering state 1 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.213: [goodixmoc] FP_CMD_NUM_STATES entering state 1 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.214: [goodixmoc] FP_CMD_NUM_STATES entering state 2 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.214: [goodixmoc] FP_CMD_NUM_STATES entering state 2 163s (process:2125): libfprint-device-DEBUG: 16:48:00.215: Device reported enroll progress, reported 9 of 12 have been completed 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.215: [goodixmoc] enroll entering state 5 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.215: [goodixmoc] FP_CMD_NUM_STATES entering state 0 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.215: [goodixmoc] FP_CMD_NUM_STATES completed successfully 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.215: [goodixmoc] FP_CMD_NUM_STATES entering state 1 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.216: [goodixmoc] FP_CMD_NUM_STATES entering state 1 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.216: [goodixmoc] FP_CMD_NUM_STATES entering state 2 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.217: [goodixmoc] FP_CMD_NUM_STATES entering state 2 163s (process:2125): libfprint-device-DEBUG: 16:48:00.217: Device reported finger status change: FP_FINGER_STATUS_NEEDED 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.217: [goodixmoc] enroll entering state 3 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.217: [goodixmoc] FP_CMD_NUM_STATES entering state 0 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.217: [goodixmoc] FP_CMD_NUM_STATES completed successfully 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.218: [goodixmoc] FP_CMD_NUM_STATES entering state 1 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.218: [goodixmoc] FP_CMD_NUM_STATES entering state 1 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.218: [goodixmoc] FP_CMD_NUM_STATES entering state 2 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.219: [goodixmoc] FP_CMD_NUM_STATES entering state 2 163s (process:2125): libfprint-device-DEBUG: 16:48:00.219: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.219: [goodixmoc] enroll entering state 4 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.219: [goodixmoc] FP_CMD_NUM_STATES entering state 0 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.220: [goodixmoc] FP_CMD_NUM_STATES completed successfully 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.220: [goodixmoc] FP_CMD_NUM_STATES entering state 1 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.220: [goodixmoc] FP_CMD_NUM_STATES entering state 1 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.221: [goodixmoc] FP_CMD_NUM_STATES entering state 2 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.221: [goodixmoc] FP_CMD_NUM_STATES entering state 2 163s (process:2125): libfprint-device-DEBUG: 16:48:00.221: Device reported enroll progress, reported 10 of 12 have been completed 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.222: [goodixmoc] enroll entering state 5 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.222: [goodixmoc] FP_CMD_NUM_STATES entering state 0 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.222: [goodixmoc] FP_CMD_NUM_STATES completed successfully 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.222: [goodixmoc] FP_CMD_NUM_STATES entering state 1 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.222: [goodixmoc] FP_CMD_NUM_STATES entering state 1 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.223: [goodixmoc] FP_CMD_NUM_STATES entering state 2 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.223: [goodixmoc] FP_CMD_NUM_STATES entering state 2 163s (process:2125): libfprint-device-DEBUG: 16:48:00.224: Device reported finger status change: FP_FINGER_STATUS_NEEDED 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.224: [goodixmoc] enroll entering state 3 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.224: [goodixmoc] FP_CMD_NUM_STATES entering state 0 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.224: [goodixmoc] FP_CMD_NUM_STATES completed successfully 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.224: [goodixmoc] FP_CMD_NUM_STATES entering state 1 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.225: [goodixmoc] FP_CMD_NUM_STATES entering state 1 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.225: [goodixmoc] FP_CMD_NUM_STATES entering state 2 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.225: [goodixmoc] FP_CMD_NUM_STATES entering state 2 163s (process:2125): libfprint-device-DEBUG: 16:48:00.226: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.226: [goodixmoc] enroll entering state 4 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.226: [goodixmoc] FP_CMD_NUM_STATES entering state 0 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.226: [goodixmoc] FP_CMD_NUM_STATES completed successfully 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.226: [goodixmoc] FP_CMD_NUM_STATES entering state 1 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.227: [goodixmoc] FP_CMD_NUM_STATES entering state 1 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.227: [goodixmoc] FP_CMD_NUM_STATES entering state 2 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.228: [goodixmoc] FP_CMD_NUM_STATES entering state 2 163s (process:2125): libfprint-device-DEBUG: 16:48:00.228: Device reported enroll progress, reported 11 of 12 have been completed 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.228: [goodixmoc] enroll entering state 5 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.228: [goodixmoc] FP_CMD_NUM_STATES entering state 0 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.229: [goodixmoc] FP_CMD_NUM_STATES completed successfully 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.229: [goodixmoc] FP_CMD_NUM_STATES entering state 1 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.229: [goodixmoc] FP_CMD_NUM_STATES entering state 1 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.230: [goodixmoc] FP_CMD_NUM_STATES entering state 2 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.230: [goodixmoc] FP_CMD_NUM_STATES entering state 2 163s (process:2125): libfprint-device-DEBUG: 16:48:00.230: Device reported finger status change: FP_FINGER_STATUS_NEEDED 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.230: [goodixmoc] enroll entering state 3 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.230: [goodixmoc] FP_CMD_NUM_STATES entering state 0 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.231: [goodixmoc] FP_CMD_NUM_STATES completed successfully 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.231: [goodixmoc] FP_CMD_NUM_STATES entering state 1 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.231: [goodixmoc] FP_CMD_NUM_STATES entering state 1 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.232: [goodixmoc] FP_CMD_NUM_STATES entering state 2 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.232: [goodixmoc] FP_CMD_NUM_STATES entering state 2 163s (process:2125): libfprint-device-DEBUG: 16:48:00.233: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.233: [goodixmoc] enroll entering state 4 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.233: [goodixmoc] FP_CMD_NUM_STATES entering state 0 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.233: [goodixmoc] FP_CMD_NUM_STATES completed successfully 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.233: [goodixmoc] FP_CMD_NUM_STATES entering state 1 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.233: [goodixmoc] FP_CMD_NUM_STATES entering state 1 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.234: [goodixmoc] FP_CMD_NUM_STATES entering state 2 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.234: [goodixmoc] FP_CMD_NUM_STATES entering state 2 163s (process:2125): libfprint-device-DEBUG: 16:48:00.235: Device reported enroll progress, reported 12 of 12 have been completed 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.235: [goodixmoc] enroll entering state 6 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.235: [goodixmoc] FP_CMD_NUM_STATES entering state 0 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.235: [goodixmoc] FP_CMD_NUM_STATES completed successfully 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.235: [goodixmoc] FP_CMD_NUM_STATES entering state 1 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.236: [goodixmoc] FP_CMD_NUM_STATES entering state 1 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.236: [goodixmoc] FP_CMD_NUM_STATES entering state 2 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.237: [goodixmoc] FP_CMD_NUM_STATES entering state 2 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.237: [goodixmoc] enroll entering state 7 163s (process:2125): libfprint-goodixmoc-DEBUG: 16:48:00.237: user_id: FP1-00000000-0-00000000-nobody, user_id_len: 30, finger: 1 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.237: [goodixmoc] FP_CMD_NUM_STATES entering state 0 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.238: [goodixmoc] FP_CMD_NUM_STATES completed successfully 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.238: [goodixmoc] FP_CMD_NUM_STATES entering state 1 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.239: [goodixmoc] FP_CMD_NUM_STATES entering state 1 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.240: [goodixmoc] FP_CMD_NUM_STATES entering state 2 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.240: [goodixmoc] FP_CMD_NUM_STATES entering state 2 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.240: [goodixmoc] enroll entering state 8 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.240: [goodixmoc] FP_CMD_NUM_STATES entering state 0 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.241: [goodixmoc] FP_CMD_NUM_STATES completed successfully 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.241: [goodixmoc] FP_CMD_NUM_STATES entering state 1 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.241: [goodixmoc] FP_CMD_NUM_STATES entering state 1 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.242: [goodixmoc] FP_CMD_NUM_STATES entering state 2 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.242: [goodixmoc] FP_CMD_NUM_STATES entering state 2 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.243: [goodixmoc] enroll completed successfully 163s (process:2125): libfprint-goodixmoc-DEBUG: 16:48:00.243: Enrollment complete! 163s (process:2125): libfprint-device-DEBUG: 16:48:00.243: Device reported enroll completion 163s (process:2125): libfprint-device-DEBUG: 16:48:00.243: Device reported finger status change: FP_FINGER_STATUS_NONE 163s (process:2125): libfprint-device-DEBUG: 16:48:00.243: Print for finger FP_FINGER_UNKNOWN enrolled 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.243: [goodixmoc] FP_CMD_NUM_STATES completed successfully 163s (process:2125): libfprint-device-DEBUG: 16:48:00.243: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 163s (process:2125): libfprint-device-DEBUG: 16:48:00.243: Not updating temperature model, device can run continuously! 163s (process:2125): libfprint-goodixmoc-DEBUG: 16:48:00.243: 51244130: ../libfprint/drivers/goodixmoc/goodix.c:1536 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.243: [goodixmoc] FP_CMD_NUM_STATES entering state 0 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.243: [goodixmoc] FP_CMD_NUM_STATES entering state 1 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.244: [goodixmoc] FP_CMD_NUM_STATES entering state 1 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.244: [goodixmoc] FP_CMD_NUM_STATES entering state 2 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.245: [goodixmoc] FP_CMD_NUM_STATES entering state 2 163s (process:2125): libfprint-goodixmoc-DEBUG: 16:48:00.245: Query complete! 163s (process:2125): libfprint-device-DEBUG: 16:48:00.245: Device reported listing completion 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.245: [goodixmoc] FP_CMD_NUM_STATES completed successfully 163s (process:2125): libfprint-device-DEBUG: 16:48:00.245: Completing action FPI_DEVICE_ACTION_LIST in idle! 163s (process:2125): libfprint-device-DEBUG: 16:48:00.245: Not updating temperature model, device can run continuously! 163s (process:2125): libfprint-device-DEBUG: 16:48:00.245: Not updating temperature model, device can run continuously! 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.245: [goodixmoc] verify entering state 0 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.245: [goodixmoc] FP_CMD_NUM_STATES entering state 0 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.246: [goodixmoc] FP_CMD_NUM_STATES entering state 1 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.246: [goodixmoc] FP_CMD_NUM_STATES entering state 1 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.247: [goodixmoc] FP_CMD_NUM_STATES entering state 2 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.248: [goodixmoc] FP_CMD_NUM_STATES entering state 2 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.248: [goodixmoc] verify entering state 1 163s (process:2125): libfprint-device-DEBUG: 16:48:00.248: Device reported finger status change: FP_FINGER_STATUS_NEEDED 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.248: [goodixmoc] FP_CMD_NUM_STATES entering state 0 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.248: [goodixmoc] FP_CMD_NUM_STATES completed successfully 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.248: [goodixmoc] FP_CMD_NUM_STATES entering state 1 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.249: [goodixmoc] FP_CMD_NUM_STATES entering state 1 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.249: [goodixmoc] FP_CMD_NUM_STATES entering state 2 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.250: [goodixmoc] FP_CMD_NUM_STATES entering state 2 163s (process:2125): libfprint-device-DEBUG: 16:48:00.250: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.250: [goodixmoc] verify entering state 2 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.250: [goodixmoc] FP_CMD_NUM_STATES entering state 0 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.250: [goodixmoc] FP_CMD_NUM_STATES completed successfully 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.251: [goodixmoc] FP_CMD_NUM_STATES entering state 1 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.251: [goodixmoc] FP_CMD_NUM_STATES entering state 1 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.252: [goodixmoc] FP_CMD_NUM_STATES entering state 2 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.252: [goodixmoc] FP_CMD_NUM_STATES entering state 2 163s (process:2125): libfprint-DEBUG: 16:48:00.252: match, score: 28, study: 0 163s (process:2125): libfprint-device-DEBUG: 16:48:00.252: Device reported verify result 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.252: [goodixmoc] verify entering state 3 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.252: [goodixmoc] FP_CMD_NUM_STATES entering state 0 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.253: [goodixmoc] FP_CMD_NUM_STATES completed successfully 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.253: [goodixmoc] FP_CMD_NUM_STATES entering state 1 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.253: [goodixmoc] FP_CMD_NUM_STATES entering state 1 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.254: [goodixmoc] FP_CMD_NUM_STATES entering state 2 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.254: [goodixmoc] FP_CMD_NUM_STATES entering state 2 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.254: [goodixmoc] verify completed successfully 163s (process:2125): libfprint-goodixmoc-DEBUG: 16:48:00.255: Verify complete! 163s (process:2125): libfprint-device-DEBUG: 16:48:00.255: Device reported verify completion 163s (process:2125): libfprint-device-DEBUG: 16:48:00.255: Device reported finger status change: FP_FINGER_STATUS_NONE 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.255: [goodixmoc] FP_CMD_NUM_STATES completed successfully 163s (process:2125): libfprint-device-DEBUG: 16:48:00.255: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 163s (process:2125): libfprint-device-DEBUG: 16:48:00.255: Not updating temperature model, device can run continuously! 163s (process:2125): libfprint-device-DEBUG: 16:48:00.255: Not updating temperature model, device can run continuously! 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.255: [goodixmoc] verify entering state 0 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.255: [goodixmoc] FP_CMD_NUM_STATES entering state 0 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.256: [goodixmoc] FP_CMD_NUM_STATES entering state 1 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.256: [goodixmoc] FP_CMD_NUM_STATES entering state 1 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.257: [goodixmoc] FP_CMD_NUM_STATES entering state 2 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.257: [goodixmoc] FP_CMD_NUM_STATES entering state 2 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.257: [goodixmoc] verify entering state 1 163s (process:2125): libfprint-device-DEBUG: 16:48:00.258: Device reported finger status change: FP_FINGER_STATUS_NEEDED 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.258: [goodixmoc] FP_CMD_NUM_STATES entering state 0 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.258: [goodixmoc] FP_CMD_NUM_STATES completed successfully 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.258: [goodixmoc] FP_CMD_NUM_STATES entering state 1 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.258: [goodixmoc] FP_CMD_NUM_STATES entering state 1 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.259: [goodixmoc] FP_CMD_NUM_STATES entering state 2 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.259: [goodixmoc] FP_CMD_NUM_STATES entering state 2 163s (process:2125): libfprint-device-DEBUG: 16:48:00.260: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.260: [goodixmoc] verify entering state 2 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.260: [goodixmoc] FP_CMD_NUM_STATES entering state 0 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.260: [goodixmoc] FP_CMD_NUM_STATES completed successfully 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.260: [goodixmoc] FP_CMD_NUM_STATES entering state 1 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.261: [goodixmoc] FP_CMD_NUM_STATES entering state 1 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.261: [goodixmoc] FP_CMD_NUM_STATES entering state 2 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.262: [goodixmoc] FP_CMD_NUM_STATES entering state 2 163s (process:2125): libfprint-DEBUG: 16:48:00.262: match, score: 35, study: 0 163s (process:2125): libfprint-device-DEBUG: 16:48:00.262: Device reported identify result 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.262: [goodixmoc] verify entering state 3 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.262: [goodixmoc] FP_CMD_NUM_STATES entering state 0 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.263: [goodixmoc] FP_CMD_NUM_STATES completed successfully 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.263: [goodixmoc] FP_CMD_NUM_STATES entering state 1 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.263: [goodixmoc] FP_CMD_NUM_STATES entering state 1 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.264: [goodixmoc] FP_CMD_NUM_STATES entering state 2 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.264: [goodixmoc] FP_CMD_NUM_STATES entering state 2 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.264: [goodixmoc] verify completed successfully 163s (process:2125): libfprint-goodixmoc-DEBUG: 16:48:00.264: Verify complete! 163s (process:2125): libfprint-device-DEBUG: 16:48:00.264: Device reported identify completion 163s (process:2125): libfprint-device-DEBUG: 16:48:00.264: Device reported finger status change: FP_FINGER_STATUS_NONE 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.264: [goodixmoc] FP_CMD_NUM_STATES completed successfully 163s (process:2125): libfprint-device-DEBUG: 16:48:00.264: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 163s (process:2125): libfprint-device-DEBUG: 16:48:00.264: Not updating temperature model, device can run continuously! 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.265: [goodixmoc] FP_CMD_NUM_STATES entering state 0 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.265: [goodixmoc] FP_CMD_NUM_STATES entering state 1 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.266: [goodixmoc] FP_CMD_NUM_STATES entering state 1 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.266: [goodixmoc] FP_CMD_NUM_STATES entering state 2 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.267: [goodixmoc] FP_CMD_NUM_STATES entering state 2 163s (process:2125): libfprint-goodixmoc-DEBUG: 16:48:00.267: Successfully deleted enrolled user 163s (process:2125): libfprint-device-DEBUG: 16:48:00.267: Device reported deletion completion 163s (process:2125): libfprint-SSM-DEBUG: 16:48:00.267: [goodixmoc] FP_CMD_NUM_STATES completed successfully 163s (process:2125): libfprint-device-DEBUG: 16:48:00.267: Completing action FPI_DEVICE_ACTION_DELETE in idle! 163s (process:2125): libfprint-device-DEBUG: 16:48:00.267: Not updating temperature model, device can run continuously! 163s (process:2125): libfprint-device-DEBUG: 16:48:00.268: Device reported close completion 163s (process:2125): libfprint-device-DEBUG: 16:48:00.268: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 163s (process:2125): libfprint-device-DEBUG: 16:48:00.268: Not updating temperature model, device can run continuously! 163s enrolling 163s enroll progress: (<__gi__.FpiDeviceGoodixMoc object at 0xfd3528b37680 (FpiDeviceGoodixMoc at 0x7cd0860)>, 1, None, None, None) 163s enroll progress: (<__gi__.FpiDeviceGoodixMoc object at 0xfd3528b37680 (FpiDeviceGoodixMoc at 0x7cd0860)>, 2, None, None, None) 163s enroll progress: (<__gi__.FpiDeviceGoodixMoc object at 0xfd3528b37680 (FpiDeviceGoodixMoc at 0x7cd0860)>, 3, None, None, None) 163s enroll progress: (<__gi__.FpiDeviceGoodixMoc object at 0xfd3528b37680 (FpiDeviceGoodixMoc at 0x7cd0860)>, 4, None, None, None) 163s enroll progress: (<__gi__.FpiDeviceGoodixMoc object at 0xfd3528b37680 (FpiDeviceGoodixMoc at 0x7cd0860)>, 5, None, None, None) 163s enroll progress: (<__gi__.FpiDeviceGoodixMoc object at 0xfd3528b37680 (FpiDeviceGoodixMoc at 0x7cd0860)>, 6, None, None, None) 163s enroll progress: (<__gi__.FpiDeviceGoodixMoc object at 0xfd3528b37680 (FpiDeviceGoodixMoc at 0x7cd0860)>, 7, None, None, None) 163s enroll progress: (<__gi__.FpiDeviceGoodixMoc object at 0xfd3528b37680 (FpiDeviceGoodixMoc at 0x7cd0860)>, 8, None, None, None) 163s enroll progress: (<__gi__.FpiDeviceGoodixMoc object at 0xfd3528b37680 (FpiDeviceGoodixMoc at 0x7cd0860)>, 9, None, None, None) 163s enroll progress: (<__gi__.FpiDeviceGoodixMoc object at 0xfd3528b37680 (FpiDeviceGoodixMoc at 0x7cd0860)>, 10, None, None, None) 163s enroll progress: (<__gi__.FpiDeviceGoodixMoc object at 0xfd3528b37680 (FpiDeviceGoodixMoc at 0x7cd0860)>, 11, None, None, None) 163s enroll progress: (<__gi__.FpiDeviceGoodixMoc object at 0xfd3528b37680 (FpiDeviceGoodixMoc at 0x7cd0860)>, 12, None, None, None) 163s enroll done 163s listing 163s listing done 163s verifying 163s verify done 163s async identifying 163s indentification_done: 163s deleting 163s delete done 163s ** (umockdev-run:2121): DEBUG: 16:48:00.281: umockdev.vala:150: Removing test bed /tmp/umockdev.72BDK2 163s (umockdev-run:2121): GLib-DEBUG: 16:48:00.285: unsetenv() is not thread-safe and should not be used after threads are created 163s PASS: libfprint-2/driver-goodixmoc.test 163s Running test: libfprint-2/driver-aes3500.test 163s ** (umockdev-run:2133): DEBUG: 16:48:00.343: umockdev.vala:123: Created udev test bed /tmp/umockdev.UQH9J2 163s ** (umockdev-run:2133): DEBUG: 16:48:00.343: umockdev.vala:1297: 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 163s ** (umockdev-run:2133): DEBUG: 16:48:00.345: umockdev.vala:1366: 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) 163s ** (umockdev-run:2133): DEBUG: 16:48:00.348: umockdev.vala:1411: create_node_for_device: creating file device /tmp/umockdev.UQH9J2/dev/bus/usb/003/004 163s ** (umockdev-run:2133): DEBUG: 16:48:00.348: umockdev.vala:1297: 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 163s ** (umockdev-run:2133): DEBUG: 16:48:00.350: umockdev.vala:1366: 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) 163s ** (umockdev-run:2133): DEBUG: 16:48:00.352: umockdev.vala:1411: create_node_for_device: creating file device /tmp/umockdev.UQH9J2/dev/bus/usb/003/003 163s ** (umockdev-run:2133): DEBUG: 16:48:00.353: umockdev.vala:1297: 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 163s ** (umockdev-run:2133): DEBUG: 16:48:00.355: umockdev.vala:1366: 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) 163s ** (umockdev-run:2133): DEBUG: 16:48:00.357: umockdev.vala:1411: create_node_for_device: creating file device /tmp/umockdev.UQH9J2/dev/bus/usb/003/002 163s ** (umockdev-run:2133): DEBUG: 16:48:00.357: umockdev.vala:1297: parsing device description for /devices/pci0000:00/0000:00:1c.0/0000:01:00.0/0000:02:02.0/0000:39:00.0/usb3 163s ** (umockdev-run:2133): DEBUG: 16:48:00.359: umockdev.vala:1366: creating device /devices/pci0000:00/0000:00:1c.0/0000:01:00.0/0000:02:02.0/0000:39:00.0/usb3 (subsystem usb) 163s ** (umockdev-run:2133): DEBUG: 16:48:00.361: umockdev.vala:1411: create_node_for_device: creating file device /tmp/umockdev.UQH9J2/dev/bus/usb/003/001 163s ** (umockdev-run:2133): DEBUG: 16:48:00.361: umockdev.vala:1297: parsing device description for /devices/pci0000:00/0000:00:1c.0/0000:01:00.0/0000:02:02.0/0000:39:00.0 163s ** (umockdev-run:2133): DEBUG: 16:48:00.362: umockdev.vala:1366: creating device /devices/pci0000:00/0000:00:1c.0/0000:01:00.0/0000:02:02.0/0000:39:00.0 (subsystem pci) 163s ** (umockdev-run:2133): DEBUG: 16:48:00.364: umockdev.vala:1297: parsing device description for /devices/pci0000:00/0000:00:1c.0/0000:01:00.0/0000:02:02.0 163s ** (umockdev-run:2133): DEBUG: 16:48:00.365: umockdev.vala:1366: creating device /devices/pci0000:00/0000:00:1c.0/0000:01:00.0/0000:02:02.0 (subsystem pci) 163s ** (umockdev-run:2133): DEBUG: 16:48:00.366: umockdev.vala:1297: parsing device description for /devices/pci0000:00/0000:00:1c.0/0000:01:00.0 163s ** (umockdev-run:2133): DEBUG: 16:48:00.367: umockdev.vala:1366: creating device /devices/pci0000:00/0000:00:1c.0/0000:01:00.0 (subsystem pci) 163s ** (umockdev-run:2133): DEBUG: 16:48:00.369: umockdev.vala:1297: parsing device description for /devices/pci0000:00/0000:00:1c.0 163s ** (umockdev-run:2133): DEBUG: 16:48:00.369: umockdev.vala:1366: creating device /devices/pci0000:00/0000:00:1c.0 (subsystem pci) 163s (umockdev-run:2133): GLib-GIO-DEBUG: 16:48:00.370: _g_io_module_get_default: Found default implementation local (GLocalVfs) for ?gio-vfs? 163s (process:2137): libfprint-context-DEBUG: 16:48:00.427: Initializing FpContext (libfprint version 1.94.7+tod1) 163s (process:2137): libfprint-tod-DEBUG: 16:48:00.428: Impossible to load the shared drivers dir Error opening directory “/usr/lib/aarch64-linux-gnu/libfprint-2/tod-1”: No such file or directory 163s (process:2137): libfprint-context-DEBUG: 16:48:00.431: No driver found for USB device 2230:0006 163s (process:2137): libfprint-context-DEBUG: 16:48:00.431: No driver found for USB device 2230:0006 163s (process:2137): libfprint-context-DEBUG: 16:48:00.431: No driver found for USB device 1D6B:0002 163s (process:2137): libfprint-device-DEBUG: 16:48:00.431: Device reported probe completion 163s (process:2137): libfprint-device-DEBUG: 16:48:00.432: Completing action FPI_DEVICE_ACTION_PROBE in idle! 163s (process:2137): libfprint-device-DEBUG: 16:48:00.432: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 163s (process:2137): libfprint-image_device-DEBUG: 16:48:00.433: Image device open completed 163s (process:2137): libfprint-device-DEBUG: 16:48:00.433: Device reported open completion 163s (process:2137): libfprint-device-DEBUG: 16:48:00.433: Completing action FPI_DEVICE_ACTION_OPEN in idle! 163s (process:2137): libfprint-device-DEBUG: 16:48:00.434: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 163s (process:2137): libfprint-device-DEBUG: 16:48:00.434: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 163s (process:2137): libfprint-image_device-DEBUG: 16:48:00.434: Activating image device 163s (process:2137): libfprint-image_device-DEBUG: 16:48:00.434: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING 163s (process:2137): libfprint-aeslib-DEBUG: 16:48:00.434: write 50 regs 163s (process:2137): libfprint-aeslib-DEBUG: 16:48:00.438: all registers written 163s (process:2137): libfprint-image_device-DEBUG: 16:48:00.438: Image device activation completed 163s (process:2137): libfprint-image_device-DEBUG: 16:48:00.438: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE 163s (process:2137): libfprint-image_device-DEBUG: 16:48:00.439: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 163s (process:2137): libfprint-aeslib-DEBUG: 16:48:00.439: write 6 regs 163s (process:2137): libfprint-device-DEBUG: 16:48:00.439: Device reported finger status change: FP_FINGER_STATUS_NEEDED 163s (process:2137): libfprint-aeslib-DEBUG: 16:48:00.440: all registers written 163s (process:2137): libfprint-device-DEBUG: 16:48:00.440: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 163s (process:2137): libfprint-image_device-DEBUG: 16:48:00.441: Image device reported finger status: on 163s (process:2137): libfprint-image_device-DEBUG: 16:48:00.441: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 163s (process:2137): libfprint-aes3k-DEBUG: 16:48:00.441: frame header byte e0 163s (process:2137): libfprint-aes3k-DEBUG: 16:48:00.441: frame header byte e1 163s (process:2137): libfprint-aes3k-DEBUG: 16:48:00.441: frame header byte e2 163s (process:2137): libfprint-aes3k-DEBUG: 16:48:00.441: frame header byte e3 163s (process:2137): libfprint-aes3k-DEBUG: 16:48:00.441: frame header byte e4 163s (process:2137): libfprint-aes3k-DEBUG: 16:48:00.441: frame header byte e5 163s (process:2137): libfprint-aes3k-DEBUG: 16:48:00.441: frame header byte e6 163s (process:2137): libfprint-aes3k-DEBUG: 16:48:00.441: frame header byte e7 163s (process:2137): libfprint-image_device-DEBUG: 16:48:00.442: Image device captured an image 163s (process:2137): libfprint-image_device-DEBUG: 16:48:00.442: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 163s (process:2137): libfprint-device-DEBUG: 16:48:00.442: Device reported finger status change: FP_FINGER_STATUS_PRESENT 163s (process:2137): libfprint-device-DEBUG: 16:48:00.442: Device reported finger status change: FP_FINGER_STATUS_NONE 163s (process:2137): libfprint-image_device-DEBUG: 16:48:00.442: Image device reported finger status: off 163s (process:2137): libfprint-image_device-DEBUG: 16:48:00.442: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 163s (process:2137): libfprint-image_device-DEBUG: 16:48:00.442: Deactivating image device 163s (process:2137): libfprint-image_device-DEBUG: 16:48:00.442: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_DEACTIVATING 163s (process:2137): libfprint-image_device-DEBUG: 16:48:00.442: Image device deactivation completed 163s (process:2137): libfprint-image_device-DEBUG: 16:48:00.442: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE 163s (process:2137): libfprint-image-DEBUG: 16:48:00.462: Minutiae scan completed in 0.019544 secs 163s (process:2137): libfprint-device-DEBUG: 16:48:00.462: Device reported capture completion 163s (process:2137): libfprint-device-DEBUG: 16:48:00.462: Completing action FPI_DEVICE_ACTION_CAPTURE in idle! 163s (process:2137): libfprint-device-DEBUG: 16:48:00.462: Updated temperature model after 0.03 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 163s (process:2137): libfprint-image_device-DEBUG: 16:48:00.463: Image device close completed 163s (process:2137): libfprint-device-DEBUG: 16:48:00.463: Device reported close completion 163s (process:2137): libfprint-device-DEBUG: 16:48:00.463: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 163s (process:2137): libfprint-device-DEBUG: 16:48:00.463: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 163s ** (umockdev-run:2133): DEBUG: 16:48:00.551: umockdev.vala:150: Removing test bed /tmp/umockdev.UQH9J2 163s (umockdev-run:2133): GLib-DEBUG: 16:48:00.560: unsetenv() is not thread-safe and should not be used after threads are created 163s Comparing PNGs /tmp/libfprint-umockdev-test-5cu5zq51/capture.png and /usr/share/installed-tests/libfprint-2/aes3500/capture.png 163s PASS: libfprint-2/driver-aes3500.test 163s Running test: libfprint-2/driver-uru4000-4500.test 163s ** (umockdev-run:2146): DEBUG: 16:48:00.634: umockdev.vala:123: Created udev test bed /tmp/umockdev.5992J2 163s ** (umockdev-run:2146): DEBUG: 16:48:00.634: umockdev.vala:1297: parsing device description for /devices/pci0000:00/0000:00:14.0/usb1/1-10 163s ** (umockdev-run:2146): DEBUG: 16:48:00.636: umockdev.vala:1366: creating device /devices/pci0000:00/0000:00:14.0/usb1/1-10 (subsystem usb) 163s ** (umockdev-run:2146): DEBUG: 16:48:00.637: umockdev.vala:1411: create_node_for_device: creating file device /tmp/umockdev.5992J2/dev/bus/usb/001/050 163s ** (umockdev-run:2146): DEBUG: 16:48:00.638: umockdev.vala:1297: parsing device description for /devices/pci0000:00/0000:00:14.0/usb1 163s ** (umockdev-run:2146): DEBUG: 16:48:00.638: umockdev.vala:1366: creating device /devices/pci0000:00/0000:00:14.0/usb1 (subsystem usb) 163s ** (umockdev-run:2146): DEBUG: 16:48:00.640: umockdev.vala:1411: create_node_for_device: creating file device /tmp/umockdev.5992J2/dev/bus/usb/001/001 163s ** (umockdev-run:2146): DEBUG: 16:48:00.641: umockdev.vala:1297: parsing device description for /devices/pci0000:00/0000:00:14.0 163s ** (umockdev-run:2146): DEBUG: 16:48:00.641: umockdev.vala:1366: creating device /devices/pci0000:00/0000:00:14.0 (subsystem pci) 163s (process:2150): libfprint-context-DEBUG: 16:48:00.697: Initializing FpContext (libfprint version 1.94.7+tod1) 163s (process:2150): libfprint-tod-DEBUG: 16:48:00.697: Impossible to load the shared drivers dir Error opening directory “/usr/lib/aarch64-linux-gnu/libfprint-2/tod-1”: No such file or directory 163s (process:2150): libfprint-context-DEBUG: 16:48:00.699: No driver found for USB device 1D6B:0002 163s (process:2150): libfprint-device-DEBUG: 16:48:00.699: Device reported probe completion 163s (process:2150): libfprint-device-DEBUG: 16:48:00.699: Completing action FPI_DEVICE_ACTION_PROBE in idle! 163s (process:2150): libfprint-device-DEBUG: 16:48:00.700: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 163s (process:2150): GLib-DEBUG: 16:48:00.701: setenv()/putenv() are not thread-safe and should not be used after threads are created 163s (process:2150): libfprint-image_device-DEBUG: 16:48:00.703: Image device open completed 163s (process:2150): libfprint-device-DEBUG: 16:48:00.703: Device reported open completion 163s (process:2150): libfprint-device-DEBUG: 16:48:00.703: Completing action FPI_DEVICE_ACTION_OPEN in idle! 163s (process:2150): libfprint-device-DEBUG: 16:48:00.703: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 163s (process:2150): libfprint-device-DEBUG: 16:48:00.703: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 163s (process:2150): libfprint-image_device-DEBUG: 16:48:00.703: Activating image device 163s (process:2150): libfprint-image_device-DEBUG: 16:48:00.703: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING 163s (process:2150): libfprint-SSM-DEBUG: 16:48:00.704: [uru4000] INIT_NUM_STATES entering state 0 163s (process:2150): libfprint-uru4000-DEBUG: 16:48:00.704: read 1 regs at 7 163s (process:2150): libfprint-uru4000-DEBUG: 16:48:00.705: reg value 1 163s (process:2150): libfprint-SSM-DEBUG: 16:48:00.705: [uru4000] INIT_NUM_STATES entering state 1 163s (process:2150): libfprint-SSM-DEBUG: 16:48:00.705: [uru4000] INIT_NUM_STATES entering state 3 163s (process:2150): libfprint-uru4000-DEBUG: 16:48:00.705: set 81 163s (process:2150): libfprint-SSM-DEBUG: 16:48:00.705: [uru4000] INIT_NUM_STATES entering state 4 163s (process:2150): libfprint-SSM-DEBUG: 16:48:00.705: [uru4000] POWERUP_NUM_STATES entering state 0 163s (process:2150): libfprint-SSM-DEBUG: 16:48:00.705: [uru4000] POWERUP_NUM_STATES entering state 1 163s (process:2150): libfprint-uru4000-DEBUG: 16:48:00.705: set 01 163s (process:2150): libfprint-uru4000-DEBUG: 16:48:00.706: recv irq type 56aa 163s (process:2150): libfprint-uru4000-DEBUG: 16:48:00.706: early scanpwr interrupt 163s (process:2150): libfprint-SSM-DEBUG: 16:48:00.706: [uru4000] POWERUP_NUM_STATES entering state 2 163s (process:2150): libfprint-uru4000-DEBUG: 16:48:00.706: read 1 regs at 7 163s (process:2150): libfprint-uru4000-DEBUG: 16:48:00.707: reg value 1 163s (process:2150): libfprint-SSM-DEBUG: 16:48:00.707: [uru4000] POWERUP_NUM_STATES entering state 3 163s (process:2150): libfprint-SSM-DEBUG: 16:48:00.707: [uru4000] POWERUP_NUM_STATES completed successfully 163s (process:2150): libfprint-SSM-DEBUG: 16:48:00.707: [uru4000] INIT_NUM_STATES entering state 5 163s (process:2150): libfprint-SSM-DEBUG: 16:48:00.707: [uru4000] INIT_NUM_STATES entering state 6 163s (process:2150): libfprint-SSM-DEBUG: 16:48:00.707: [uru4000] INIT_NUM_STATES entering state 7 163s (process:2150): libfprint-uru4000-DEBUG: 16:48:00.707: read 16 regs at f0 163s (process:2150): libfprint-uru4000-DEBUG: 16:48:00.707: reg value 1a 163s (process:2150): libfprint-SSM-DEBUG: 16:48:00.707: [uru4000] INIT_NUM_STATES entering state 8 163s (process:2150): libfprint-uru4000-DEBUG: 16:48:00.707: Versions 0010 and 0115 163s (process:2150): libfprint-SSM-DEBUG: 16:48:00.707: [uru4000] INIT_NUM_STATES completed successfully 163s (process:2150): libfprint-image_device-DEBUG: 16:48:00.707: Image device activation completed 163s (process:2150): libfprint-image_device-DEBUG: 16:48:00.707: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE 163s (process:2150): libfprint-image_device-DEBUG: 16:48:00.707: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 163s (process:2150): libfprint-uru4000-DEBUG: 16:48:00.707: wait finger on 163s (process:2150): libfprint-device-DEBUG: 16:48:00.708: Device reported finger status change: FP_FINGER_STATUS_NEEDED 163s (process:2150): libfprint-uru4000-DEBUG: 16:48:00.708: recv irq type 56aa 163s (process:2150): libfprint-uru4000-DEBUG: 16:48:00.709: recv irq type 56aa 163s (process:2150): libfprint-uru4000-DEBUG: 16:48:00.709: recv irq type 0101 163s (process:2150): libfprint-device-DEBUG: 16:48:00.709: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 163s (process:2150): libfprint-image_device-DEBUG: 16:48:00.709: Image device reported finger status: on 163s (process:2150): libfprint-image_device-DEBUG: 16:48:00.709: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 163s (process:2150): libfprint-uru4000-DEBUG: 16:48:00.709: starting capture 163s (process:2150): libfprint-uru4000-DEBUG: 16:48:00.709: Image encryption seed: 1374298404 163s (process:2150): libfprint-SSM-DEBUG: 16:48:00.709: [uru4000] IMAGING_NUM_STATES entering state 0 163s (process:2150): libfprint-SSM-DEBUG: 16:48:00.711: [uru4000] IMAGING_NUM_STATES entering state 1 163s (process:2150): libfprint-uru4000-DEBUG: 16:48:00.711: hw header lines 289 163s (process:2150): libfprint-uru4000-DEBUG: 16:48:00.711: dev2: 11240 163s (process:2150): libfprint-uru4000-DEBUG: 16:48:00.711: image seems to be encrypted 163s (process:2150): libfprint-SSM-DEBUG: 16:48:00.711: [uru4000] IMAGING_NUM_STATES entering state 2 163s (process:2150): libfprint-uru4000-DEBUG: 16:48:00.711: read 4 regs at 34 163s (process:2150): libfprint-uru4000-DEBUG: 16:48:00.712: reg value f2 163s (process:2150): libfprint-SSM-DEBUG: 16:48:00.712: [uru4000] IMAGING_NUM_STATES entering state 3 163s (process:2150): libfprint-uru4000-DEBUG: 16:48:00.712: encryption id 00 -> key 544409d6 163s (process:2150): libfprint-uru4000-DEBUG: 16:48:00.712: 0 02 72 163s (process:2150): libfprint-uru4000-DEBUG: 16:48:00.712: decoding 72 lines 163s (process:2150): libfprint-uru4000-DEBUG: 16:48:00.712: 1 00 1 163s (process:2150): libfprint-uru4000-DEBUG: 16:48:00.712: skipping 1 lines 163s (process:2150): libfprint-uru4000-DEBUG: 16:48:00.712: 2 02 49 163s (process:2150): libfprint-uru4000-DEBUG: 16:48:00.712: decoding 49 lines 163s (process:2150): libfprint-uru4000-DEBUG: 16:48:00.712: 3 01 1 163s (process:2150): libfprint-uru4000-DEBUG: 16:48:00.712: skipping 1 lines 163s (process:2150): libfprint-uru4000-DEBUG: 16:48:00.712: 4 00 1 163s (process:2150): libfprint-uru4000-DEBUG: 16:48:00.712: skipping 1 lines 163s (process:2150): libfprint-uru4000-DEBUG: 16:48:00.712: 5 02 49 163s (process:2150): libfprint-uru4000-DEBUG: 16:48:00.712: decoding 49 lines 163s (process:2150): libfprint-uru4000-DEBUG: 16:48:00.712: 6 00 1 163s (process:2150): libfprint-uru4000-DEBUG: 16:48:00.712: skipping 1 lines 163s (process:2150): libfprint-uru4000-DEBUG: 16:48:00.712: 7 02 116 163s (process:2150): libfprint-uru4000-DEBUG: 16:48:00.712: decoding 116 lines 163s (process:2150): libfprint-SSM-DEBUG: 16:48:00.712: [uru4000] IMAGING_NUM_STATES entering state 4 163s (process:2150): libfprint-image_device-DEBUG: 16:48:00.712: Image device captured an image 163s (process:2150): libfprint-image_device-DEBUG: 16:48:00.715: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 163s (process:2150): libfprint-device-DEBUG: 16:48:00.715: Device reported finger status change: FP_FINGER_STATUS_PRESENT 163s (process:2150): libfprint-SSM-DEBUG: 16:48:00.715: [uru4000] IMAGING_NUM_STATES completed successfully 163s (process:2150): libfprint-uru4000-DEBUG: 16:48:00.715: await finger off 163s (process:2150): libfprint-uru4000-DEBUG: 16:48:00.716: recv irq type 0200 163s (process:2150): libfprint-device-DEBUG: 16:48:00.716: Device reported finger status change: FP_FINGER_STATUS_NONE 163s (process:2150): libfprint-image_device-DEBUG: 16:48:00.716: Image device reported finger status: off 163s (process:2150): libfprint-image_device-DEBUG: 16:48:00.716: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 163s (process:2150): libfprint-image_device-DEBUG: 16:48:00.716: Deactivating image device 163s (process:2150): libfprint-image_device-DEBUG: 16:48:00.716: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_DEACTIVATING 163s (process:2150): libfprint-uru4000-DEBUG: 16:48:00.716: deactivating 163s (process:2150): libfprint-uru4000-DEBUG: 16:48:00.717: cancelled 163s (process:2150): libfprint-image_device-DEBUG: 16:48:00.717: Image device deactivation completed 163s (process:2150): libfprint-image_device-DEBUG: 16:48:00.717: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE 163s (process:2150): libfprint-image-DEBUG: 16:48:00.735: Minutiae scan completed in 0.021639 secs 163s (process:2150): libfprint-device-DEBUG: 16:48:00.735: Device reported capture completion 163s (process:2150): libfprint-device-DEBUG: 16:48:00.735: Completing action FPI_DEVICE_ACTION_CAPTURE in idle! 163s (process:2150): libfprint-device-DEBUG: 16:48:00.735: Updated temperature model after 0.03 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 163s (process:2150): libfprint-image_device-DEBUG: 16:48:00.736: Image device close completed 163s (process:2150): libfprint-device-DEBUG: 16:48:00.736: Device reported close completion 163s (process:2150): libfprint-device-DEBUG: 16:48:00.736: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 163s (process:2150): libfprint-device-DEBUG: 16:48:00.736: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 163s ** (umockdev-run:2146): DEBUG: 16:48:00.880: umockdev.vala:150: Removing test bed /tmp/umockdev.5992J2 163s (umockdev-run:2146): GLib-DEBUG: 16:48:00.883: unsetenv() is not thread-safe and should not be used after threads are created 163s Comparing PNGs /tmp/libfprint-umockdev-test-lad3k3ns/capture.png and /usr/share/installed-tests/libfprint-2/uru4000-4500/capture.png 163s PASS: libfprint-2/driver-uru4000-4500.test 163s Running test: libfprint-2/driver-aes2501.test 163s ** (umockdev-run:2159): DEBUG: 16:48:01.005: umockdev.vala:123: Created udev test bed /tmp/umockdev.XGHDK2 163s ** (umockdev-run:2159): DEBUG: 16:48:01.005: umockdev.vala:1297: parsing device description for /devices/pci0000:00/0000:00:14.0/usb1/1-10 164s ** (umockdev-run:2159): DEBUG: 16:48:01.007: umockdev.vala:1366: creating device /devices/pci0000:00/0000:00:14.0/usb1/1-10 (subsystem usb) 164s ** (umockdev-run:2159): DEBUG: 16:48:01.009: umockdev.vala:1411: create_node_for_device: creating file device /tmp/umockdev.XGHDK2/dev/bus/usb/001/044 164s ** (umockdev-run:2159): DEBUG: 16:48:01.009: umockdev.vala:1297: parsing device description for /devices/pci0000:00/0000:00:14.0/usb1 164s ** (umockdev-run:2159): DEBUG: 16:48:01.010: umockdev.vala:1366: creating device /devices/pci0000:00/0000:00:14.0/usb1 (subsystem usb) 164s ** (umockdev-run:2159): DEBUG: 16:48:01.011: umockdev.vala:1411: create_node_for_device: creating file device /tmp/umockdev.XGHDK2/dev/bus/usb/001/001 164s ** (umockdev-run:2159): DEBUG: 16:48:01.011: umockdev.vala:1297: parsing device description for /devices/pci0000:00/0000:00:14.0 164s ** (umockdev-run:2159): DEBUG: 16:48:01.012: umockdev.vala:1366: creating device /devices/pci0000:00/0000:00:14.0 (subsystem pci) 164s (process:2163): libfprint-context-DEBUG: 16:48:01.071: Initializing FpContext (libfprint version 1.94.7+tod1) 164s (process:2163): libfprint-tod-DEBUG: 16:48:01.071: Impossible to load the shared drivers dir Error opening directory “/usr/lib/aarch64-linux-gnu/libfprint-2/tod-1”: No such file or directory 164s (process:2163): libfprint-context-DEBUG: 16:48:01.073: No driver found for USB device 1D6B:0002 164s (process:2163): libfprint-device-DEBUG: 16:48:01.073: Device reported probe completion 164s (process:2163): libfprint-device-DEBUG: 16:48:01.073: Completing action FPI_DEVICE_ACTION_PROBE in idle! 164s (process:2163): libfprint-device-DEBUG: 16:48:01.073: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 164s (process:2163): libfprint-image_device-DEBUG: 16:48:01.075: Image device open completed 164s (process:2163): libfprint-device-DEBUG: 16:48:01.075: Device reported open completion 164s (process:2163): libfprint-device-DEBUG: 16:48:01.075: Completing action FPI_DEVICE_ACTION_OPEN in idle! 164s (process:2163): libfprint-device-DEBUG: 16:48:01.075: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 164s (process:2163): libfprint-device-DEBUG: 16:48:01.076: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 164s (process:2163): libfprint-image_device-DEBUG: 16:48:01.076: Activating image device 164s (process:2163): libfprint-image_device-DEBUG: 16:48:01.076: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING 164s (process:2163): libfprint-SSM-DEBUG: 16:48:01.076: [aes2501] ACTIVATE_NUM_STATES entering state 0 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.076: write 38 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.077: all registers written 164s (process:2163): libfprint-SSM-DEBUG: 16:48:01.077: [aes2501] ACTIVATE_NUM_STATES entering state 1 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.077: read data 1 164s (process:2163): libfprint-SSM-DEBUG: 16:48:01.078: [aes2501] ACTIVATE_NUM_STATES entering state 2 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.078: write 7 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.079: all registers written 164s (process:2163): libfprint-SSM-DEBUG: 16:48:01.079: [aes2501] ACTIVATE_NUM_STATES entering state 3 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.079: 52079750: ../libfprint/drivers/aes2501.c:140 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.079: write 1 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.079: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.080: reg 0xaf = 20 164s (process:2163): libfprint-SSM-DEBUG: 16:48:01.080: [aes2501] ACTIVATE_NUM_STATES entering state 5 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.080: write 7 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.080: all registers written 164s (process:2163): libfprint-SSM-DEBUG: 16:48:01.080: [aes2501] ACTIVATE_NUM_STATES entering state 6 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.080: write 16 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.081: all registers written 164s (process:2163): libfprint-SSM-DEBUG: 16:48:01.081: [aes2501] ACTIVATE_NUM_STATES completed successfully 164s (process:2163): libfprint-image_device-DEBUG: 16:48:01.081: Image device activation completed 164s (process:2163): libfprint-image_device-DEBUG: 16:48:01.081: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE 164s (process:2163): libfprint-image_device-DEBUG: 16:48:01.081: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 164s (process:2163): libfprint-device-DEBUG: 16:48:01.081: Device reported finger status change: FP_FINGER_STATUS_NEEDED 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.081: 52081950: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.081: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.082: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.083: 52083847: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.083: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.084: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.085: 52085822: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.085: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.086: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.087: 52087779: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.087: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.088: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.089: 52089748: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.089: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.090: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.090: 52091677: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.090: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.092: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.092: 52093567: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.092: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.094: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.094: 52095480: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.094: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.096: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.096: 52097484: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.096: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.098: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.098: 52099412: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.098: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.100: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.100: 52101386: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.100: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.102: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.102: 52103301: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.102: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.104: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.104: 52105281: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.104: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.105: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.106: 52107177: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.106: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.107: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.108: 52109189: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.108: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.109: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.110: 52111128: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.110: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.111: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.112: 52113097: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.112: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.113: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.114: 52115069: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.114: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.115: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.116: 52117011: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.116: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.117: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.118: 52119046: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.118: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.119: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.120: 52121002: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.120: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.121: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.122: 52122959: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.122: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.123: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.124: 52124932: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.124: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.125: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.126: 52126848: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.126: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.127: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.128: 52128750: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.128: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.129: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.129: 52130675: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.130: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.131: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.132: 52132715: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.132: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.133: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.133: 52134645: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.133: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.135: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.135: 52136567: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.135: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.137: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.137: 52138463: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.137: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.139: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.139: 52140438: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.139: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.141: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.141: 52142414: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.141: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.143: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.143: 52144363: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.143: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.145: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.145: 52146262: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.145: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.146: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.147: 52148238: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.147: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.148: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.149: 52150139: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.149: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.150: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.151: 52152153: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.151: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.152: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.153: 52154065: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.153: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.154: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.155: 52156029: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.155: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.156: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.157: 52158045: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.157: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.158: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.159: 52160022: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.159: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.160: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.161: 52162015: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.161: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.162: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.163: 52163992: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.163: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.164: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.165: 52165915: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.165: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.166: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.167: 52167913: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.167: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.168: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.169: 52169834: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.169: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.170: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.171: 52171763: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.171: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.172: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.172: 52173675: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.172: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.174: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.174: 52175647: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.174: write 23 regs 164s (process:2163): libfprint-device-DEBUG: 16:48:01.175: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.176: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.177: 52177699: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.177: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.178: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.178: 52179669: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.178: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.180: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.180: 52181633: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.180: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.182: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.182: 52183579: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.182: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.184: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.184: 52185577: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.184: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.186: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.186: 52187504: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.186: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.188: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.188: 52189485: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.188: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.190: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.190: 52191509: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.190: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.192: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.192: 52193412: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.192: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.194: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.194: 52195393: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.194: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.196: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.196: 52197388: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.196: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.198: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.198: 52199326: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.198: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.200: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.200: 52201444: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.200: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.202: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.202: 52203308: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.202: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.203: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.204: 52205249: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.204: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.205: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.206: 52207165: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.206: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.207: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.208: 52209125: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.208: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.209: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.210: 52211043: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.210: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.211: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.212: 52212955: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.212: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.213: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.214: 52214901: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.214: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.215: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.216: 52216852: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.216: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.217: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.218: 52218842: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.218: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.219: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.220: 52220845: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.220: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.221: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.222: 52222794: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.222: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.223: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.224: 52224715: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.224: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.225: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.225: 52226632: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.225: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.227: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.227: 52228585: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.227: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.229: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.229: 52230521: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.229: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.231: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.231: 52232493: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.231: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.233: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.233: 52234463: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.233: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.235: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.235: 52236393: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.235: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.237: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.237: 52238399: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.237: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.239: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.239: 52240455: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.239: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.241: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.241: 52242535: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.241: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.243: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.243: 52244456: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.243: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.245: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.245: 52246426: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.245: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.247: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.247: 52248328: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.247: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.248: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.249: 52250328: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.249: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.251: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.251: 52252269: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.251: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.253: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.253: 52254259: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.253: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.254: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.255: 52256188: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.255: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.256: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.257: 52258213: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.257: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.258: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.259: 52260138: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.259: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.260: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.261: 52262140: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.261: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.262: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.263: 52264123: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.263: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.264: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.265: 52266037: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.265: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.266: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.267: 52267971: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.267: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.268: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.269: 52269927: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.269: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.270: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.271: 52271879: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.271: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.272: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.273: 52273855: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.273: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.274: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.275: 52275818: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.275: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.276: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.277: 52277830: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.277: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.278: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.279: 52279738: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.279: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.280: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.280: 52281675: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.280: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.282: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.282: 52283630: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.282: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.284: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.284: 52285613: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.284: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.286: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.286: 52287543: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.286: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.288: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.288: 52289469: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.288: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.290: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.290: 52291393: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.290: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.292: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.292: 52293272: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.292: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.293: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.294: 52295225: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.294: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.295: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.296: 52297150: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.296: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.297: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.298: 52299132: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.298: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.299: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.300: 52301038: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.300: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.301: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.302: 52303005: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.302: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.303: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.304: 52304985: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.304: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.305: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.306: 52307017: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.306: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.307: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.308: 52309037: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.308: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.309: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.310: 52311065: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.310: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.311: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.312: 52313087: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.312: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.313: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.314: 52315118: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.314: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.315: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.316: 52317073: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.316: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.317: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.318: 52319038: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.318: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.319: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.320: 52321068: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.320: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.321: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.322: 52322962: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.322: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.323: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.324: 52324957: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.324: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.325: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.326: 52326946: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.326: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.327: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.328: 52328884: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.328: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.329: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.330: 52330843: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.330: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.331: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.332: 52332776: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.332: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.333: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.334: 52334693: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.334: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.335: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.335: 52336606: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.335: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.337: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.337: 52338580: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.337: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.339: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.339: 52340579: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.339: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.341: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.341: 52342620: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.341: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.343: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.343: 52344634: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.343: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.345: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.345: 52346542: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.345: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.347: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.347: 52348489: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.347: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.349: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.349: 52350527: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.349: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.351: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.351: 52352484: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.351: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.353: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.353: 52354524: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.353: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.355: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.355: 52356500: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.355: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.357: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.357: 52358417: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.357: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.359: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.359: 52360429: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.359: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.361: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.361: 52362365: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.361: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.363: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.363: 52364321: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.363: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.364: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.365: 52366224: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.365: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.366: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.367: 52368146: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.367: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.368: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.369: 52370170: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.369: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.370: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.371: 52372106: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.371: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.372: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.373: 52374072: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.373: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.374: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.375: 52375983: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.375: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.376: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.377: 52377959: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.377: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.378: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.379: 52379851: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.379: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.380: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.381: 52381841: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.381: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.382: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.383: 52383799: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.383: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.384: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.385: 52385721: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.385: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.386: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.386: 52387638: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.386: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.388: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.388: 52389670: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.388: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.390: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.390: 52391602: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.390: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.392: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.392: 52393593: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.392: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.394: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.394: 52395524: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.394: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.396: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.396: 52397460: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.396: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.398: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.398: 52399372: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.398: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.400: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.400: 52401307: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.400: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.402: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.402: 52403307: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.402: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.404: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.404: 52405273: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.404: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.406: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.406: 52407245: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.406: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.407: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.408: 52409175: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.408: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.409: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.410: 52411209: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.410: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.411: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.412: 52413210: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.412: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.413: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.414: 52415154: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.414: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.415: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.416: 52417160: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.416: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.417: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.418: 52419077: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.418: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.419: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.420: 52421064: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.420: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.421: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.422: 52422984: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.422: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.423: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.424: 52425010: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.424: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.425: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.426: 52426968: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.426: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.427: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.428: 52428865: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.428: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.429: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.430: 52430785: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.430: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.431: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.432: 52432746: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.432: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.433: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.433: 52434642: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.433: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.435: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.435: 52436610: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.435: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.437: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.437: 52438496: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.437: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.439: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.439: 52440498: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.439: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.441: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.441: 52442313: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.441: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.442: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.443: 52444175: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.443: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.444: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.445: 52446000: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.445: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.446: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.447: 52447823: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.447: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.448: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.448: 52449662: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.448: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.450: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.450: 52451455: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.450: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.452: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.452: 52453411: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.452: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.454: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.454: 52455259: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.454: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.455: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.456: 52457143: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.456: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.457: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.458: 52458916: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.458: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.459: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.460: 52460774: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.460: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.461: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.461: 52462663: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.461: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.463: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.463: 52464489: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.463: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.465: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.465: 52466288: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.465: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.466: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.467: 52468143: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.467: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.468: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.469: 52470015: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.469: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.470: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.471: 52471892: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.471: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.472: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.473: 52473791: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.473: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.474: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.474: 52475592: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.474: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.476: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.476: 52477441: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.476: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.478: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.478: 52479250: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.478: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.479: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.480: 52481068: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.480: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.481: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.482: 52482868: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.482: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.483: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.484: 52484695: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.484: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.485: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.485: 52486507: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.485: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.487: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.487: 52488263: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.487: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.488: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.489: 52490115: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.489: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.490: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.491: 52491969: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.491: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.492: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.493: 52493928: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.493: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.494: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.495: 52495707: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.495: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.496: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.496: 52497603: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.496: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.498: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.498: 52499357: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.498: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.500: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.500: 52501202: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.500: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.501: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.502: 52503006: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.502: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.503: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.504: 52504909: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.504: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.505: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.505: 52506671: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.505: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.507: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.507: 52508496: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.507: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.509: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.509: 52510291: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.509: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.510: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.511: 52512124: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.511: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.512: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.513: 52513933: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.513: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.514: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.515: 52515718: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.515: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.516: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.516: 52517539: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.516: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.518: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.518: 52519246: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.518: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.519: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.520: 52521066: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.520: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.521: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.522: 52522871: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.522: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.523: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.524: 52524712: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.524: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.525: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.525: 52526507: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.525: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.527: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.527: 52528286: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.527: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.528: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.529: 52530115: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.529: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.530: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.531: 52531984: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.531: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.532: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.533: 52533803: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.533: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.534: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.534: 52535567: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.534: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.536: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.536: 52537349: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.536: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.537: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.538: 52539076: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.538: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.539: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.540: 52540920: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.540: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.541: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.542: 52542716: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.542: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.543: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.543: 52544560: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.543: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.545: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.545: 52546362: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.545: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.547: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.547: 52548278: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.547: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.548: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.549: 52550110: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.549: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.550: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.551: 52551899: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.551: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.552: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.553: 52553829: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.553: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.554: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.554: 52555638: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.554: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.556: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.556: 52557531: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.556: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.558: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.558: 52559313: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.558: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.559: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.560: 52561119: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.560: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.561: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.562: 52562906: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.562: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.563: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.563: 52564668: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.563: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.565: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.565: 52566452: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.565: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.567: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.567: 52568266: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.567: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.568: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.569: 52570014: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.569: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.570: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.571: 52571768: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.571: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.572: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.572: 52573598: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.572: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.574: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.574: 52575367: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.574: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.576: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.576: 52577214: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.576: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.577: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.578: 52579055: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.578: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.579: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.580: 52580883: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.580: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.581: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.581: 52582668: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.581: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.583: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.583: 52584491: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.583: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.585: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.585: 52586317: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.585: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.586: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.587: 52588111: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.587: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.588: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.589: 52589918: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.589: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.590: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.591: 52591695: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.591: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.592: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.592: 52593487: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.592: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.594: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.594: 52595234: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.594: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.595: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.596: 52597033: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.596: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.597: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.598: 52598825: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.598: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.599: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.599: 52600632: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.599: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.601: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.601: 52602299: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.601: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.602: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.603: 52603966: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.603: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.604: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.605: 52605763: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.605: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.606: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.606: 52607426: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.606: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.608: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.608: 52609364: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.608: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.609: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.610: 52611016: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.610: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.611: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.612: 52612780: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.612: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.613: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.613: 52614499: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.613: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.615: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.615: 52616257: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.615: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.616: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.617: 52617988: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.617: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.618: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.619: 52619697: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.619: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.620: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.620: 52621518: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.620: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.622: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.622: 52623180: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.622: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.623: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.624: 52624937: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.624: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.625: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.625: 52626599: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.625: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.627: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.627: 52628297: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.627: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.628: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.629: 52629983: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.629: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.630: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.630: 52631659: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.631: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.632: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.632: 52633458: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.632: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.633: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.634: 52635158: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.634: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.635: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.636: 52636912: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.636: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.637: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.637: 52638582: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.637: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.639: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.639: 52640356: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.639: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.640: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.641: 52642080: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.641: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.642: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.643: 52643774: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.643: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.644: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.644: 52645512: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.644: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.646: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.646: 52647186: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.646: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.647: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.648: 52648836: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.648: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.649: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.649: 52650568: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.649: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.651: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.651: 52652310: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.651: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.652: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.653: 52653913: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.653: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.654: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.654: 52655589: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.654: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.656: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.656: 52657426: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.656: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.658: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.658: 52659362: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.658: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.660: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.660: 52661259: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.660: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.661: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.662: 52662980: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.662: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.663: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.663: 52664647: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.663: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.665: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.665: 52666350: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.665: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.666: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.667: 52668151: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.667: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.668: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.669: 52669871: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.669: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.670: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.670: 52671568: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.670: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.672: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.672: 52673250: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.672: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.673: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.674: 52674999: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.674: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.675: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.676: 52676921: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.676: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.677: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.678: 52678904: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.678: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.679: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.679: 52680604: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.679: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.681: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.681: 52682333: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.681: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.682: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.683: 52684050: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.683: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.684: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.685: 52685769: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.685: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.686: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.686: 52687413: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.686: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.687: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.688: 52689157: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.688: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.689: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.690: 52690867: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.690: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.691: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.691: 52692606: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.691: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.693: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.693: 52694366: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.693: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.695: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.695: 52696297: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.695: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.696: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.697: 52698154: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.697: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.698: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.699: 52699902: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.699: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.700: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.700: 52701656: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.700: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.702: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.702: 52703310: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.702: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.703: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.704: 52705054: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.704: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.705: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.706: 52706785: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.706: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.707: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.707: 52708543: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.707: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.709: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.709: 52710214: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.709: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.710: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.711: 52711893: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.711: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.712: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.712: 52713639: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.712: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.714: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.714: 52715387: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.714: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.715: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.716: 52717176: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.716: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.717: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.718: 52718908: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.718: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.719: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.719: 52720619: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.719: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.721: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.721: 52722251: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.721: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.722: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.723: 52724052: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.723: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.724: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.725: 52725806: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.725: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.726: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.726: 52727531: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.726: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.728: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.728: 52729301: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.728: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.729: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.730: 52731070: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.730: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.731: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.732: 52732836: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.732: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.733: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.733: 52734578: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.733: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.735: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.735: 52736312: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.735: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.736: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.737: 52738100: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.737: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.738: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.739: 52739838: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.739: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.740: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.740: 52741687: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.741: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.742: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.742: 52743562: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.742: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.744: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.744: 52745384: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.744: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.745: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.746: 52747112: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.746: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.747: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.748: 52748903: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.748: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.749: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.749: 52750615: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.749: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.751: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.751: 52752416: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.751: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.752: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.753: 52754149: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.753: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.754: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.755: 52755963: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.755: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.756: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.757: 52757862: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.757: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.758: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.758: 52759561: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.758: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.760: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.760: 52761307: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.760: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.761: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.762: 52762960: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.762: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.763: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.764: 52764704: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.764: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.765: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.765: 52766414: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.765: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.766: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.767: 52768129: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.767: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.768: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.769: 52769824: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.769: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.770: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.770: 52771584: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.770: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.772: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.772: 52773406: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.772: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.773: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.774: 52775154: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.774: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.775: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.776: 52776863: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.776: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.777: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.777: 52778559: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.777: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.779: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.779: 52780318: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.779: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.780: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.781: 52781992: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.781: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.782: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.783: 52783742: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.783: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.784: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.784: 52785499: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.784: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.786: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.786: 52787153: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.786: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.787: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.788: 52788973: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.788: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.789: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.789: 52790631: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.789: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.791: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.791: 52792393: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.791: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.793: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.793: 52794240: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.793: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.794: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.795: 52796030: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.795: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.796: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.797: 52797819: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.797: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.798: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.798: 52799619: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.798: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.800: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.800: 52801344: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.800: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.801: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.802: 52803077: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.802: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.803: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.804: 52805041: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.804: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.805: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.806: 52806797: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.806: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.807: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.807: 52808520: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.807: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.809: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.809: 52810269: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.809: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.810: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.811: 52812034: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.811: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.812: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.813: 52813895: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.813: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.814: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.815: 52815701: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.815: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.816: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.816: 52817448: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.816: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.818: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.818: 52819211: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.818: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.819: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.820: 52820899: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.820: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.821: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.821: 52822679: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.822: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.823: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.823: 52824418: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.823: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.825: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.825: 52826196: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.825: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.826: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.827: 52828025: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.827: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.828: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.829: 52829765: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.829: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.830: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.830: 52831514: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.830: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.832: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.832: 52833219: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.832: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.833: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.834: 52834953: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.834: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.835: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.835: 52836639: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.835: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.837: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.837: 52838355: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.837: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.838: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.839: 52840077: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.839: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.840: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.841: 52841823: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.841: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.842: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.842: 52843574: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.842: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.844: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.844: 52845327: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.844: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.846: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.846: 52847265: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.846: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.847: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.848: 52849018: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.848: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.849: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.850: 52850705: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.850: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.851: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.851: 52852495: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.851: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.853: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.853: 52854245: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.853: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.854: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.855: 52856057: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.855: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.856: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.857: 52857786: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.857: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.858: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.858: 52859551: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.858: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.860: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.860: 52861322: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.860: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.861: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.862: 52862988: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.862: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.863: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.864: 52864702: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.864: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.865: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.865: 52866443: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.865: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.867: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.867: 52868291: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.867: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.868: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.869: 52870030: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.869: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.870: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.871: 52871783: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.871: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.872: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.872: 52873534: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.872: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.874: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.874: 52875291: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.874: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.875: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.876: 52877036: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.876: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.877: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.878: 52878875: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.878: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.879: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.879: 52880565: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.879: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.881: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.881: 52882263: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.881: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.882: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.883: 52883994: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.883: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.884: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.885: 52885815: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.885: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.886: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.886: 52887593: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.886: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.888: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.888: 52889273: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.888: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.889: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.890: 52891010: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.890: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.891: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.892: 52892770: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.892: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.893: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.893: 52894513: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.893: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.895: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.895: 52896328: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.895: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.896: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.897: 52898050: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.897: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.898: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.899: 52899745: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.899: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.900: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.900: 52901512: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.900: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.902: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.902: 52903225: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.902: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.903: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.904: 52904963: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.904: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.905: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.905: 52906664: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.906: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.907: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.907: 52908426: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.907: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.909: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.909: 52910180: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.909: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.910: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.911: 52911892: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.911: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.912: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.912: 52913657: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.912: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.914: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.914: 52915419: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.914: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.915: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.916: 52917170: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.916: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.917: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.918: 52918864: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.918: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.919: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.919: 52920565: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.919: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.921: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.921: 52922208: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.921: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.922: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.923: 52923931: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.923: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.924: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.924: 52925666: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.925: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.926: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.926: 52927363: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.926: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.927: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.928: 52929063: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.928: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.929: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.930: 52930730: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.930: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.931: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.931: 52932417: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.931: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.932: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.933: 52934098: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.933: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.934: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.935: 52935781: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.935: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.936: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.936: 52937382: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.936: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.937: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.938: 52939030: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.938: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.939: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.940: 52940706: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.940: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.941: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.941: 52942397: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.941: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.942: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.943: 52944126: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.943: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.944: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.945: 52945790: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.945: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.946: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.946: 52947446: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.946: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.947: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.948: 52949125: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.948: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.949: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.950: 52950772: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.950: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.951: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.951: 52952466: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.951: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.953: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.953: 52954188: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.953: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.954: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.955: 52955996: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.955: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.956: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.957: 52957742: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.957: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.958: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.958: 52959404: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.958: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.959: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.960: 52961079: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.960: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.961: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.962: 52962752: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.962: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.963: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.963: 52964488: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.963: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.964: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.965: 52966130: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.965: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.966: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.967: 52967777: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.967: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.968: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.968: 52969435: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.968: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.970: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.970: 52971151: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.970: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.971: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.972: 52972846: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.972: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.973: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.973: 52974582: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.973: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.975: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.975: 52976327: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.975: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.976: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.977: 52978105: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.977: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.978: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.979: 52979804: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.979: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.980: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.980: 52981573: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.980: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.982: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.982: 52983298: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.982: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.983: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.984: 52985007: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.984: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.985: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.985: 52986684: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.986: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.987: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.987: 52988424: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.987: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.988: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.989: 52990124: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.989: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.990: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.991: 52991863: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.991: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.992: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.992: 52993570: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.992: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.994: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.994: 52995295: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.994: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.995: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.996: 52997024: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.996: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.997: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.998: 52998845: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.998: write 23 regs 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.999: all registers written 164s (process:2163): libfprint-aes2501-DEBUG: 16:48:01.999: 53000589: ../libfprint/drivers/aes2501.c:310 164s (process:2163): libfprint-aeslib-DEBUG: 16:48:01.999: write 23 regs 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.001: all registers written 165s (process:2163): libfprint-aes2501-DEBUG: 16:48:02.001: 53002286: ../libfprint/drivers/aes2501.c:310 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.001: write 23 regs 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.002: all registers written 165s (process:2163): libfprint-aes2501-DEBUG: 16:48:02.003: 53003983: ../libfprint/drivers/aes2501.c:310 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.003: write 23 regs 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.004: all registers written 165s (process:2163): libfprint-aes2501-DEBUG: 16:48:02.004: 53005687: ../libfprint/drivers/aes2501.c:310 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.005: write 23 regs 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.006: all registers written 165s (process:2163): libfprint-aes2501-DEBUG: 16:48:02.006: 53007338: ../libfprint/drivers/aes2501.c:310 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.006: write 23 regs 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.007: all registers written 165s (process:2163): libfprint-aes2501-DEBUG: 16:48:02.008: 53009068: ../libfprint/drivers/aes2501.c:310 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.008: write 23 regs 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.009: all registers written 165s (process:2163): libfprint-aes2501-DEBUG: 16:48:02.010: 53010766: ../libfprint/drivers/aes2501.c:310 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.010: write 23 regs 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.011: all registers written 165s (process:2163): libfprint-aes2501-DEBUG: 16:48:02.011: 53012487: ../libfprint/drivers/aes2501.c:310 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.011: write 23 regs 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.013: all registers written 165s (process:2163): libfprint-aes2501-DEBUG: 16:48:02.013: 53014176: ../libfprint/drivers/aes2501.c:310 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.013: write 23 regs 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.014: all registers written 165s (process:2163): libfprint-aes2501-DEBUG: 16:48:02.015: 53015859: ../libfprint/drivers/aes2501.c:310 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.015: write 23 regs 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.016: all registers written 165s (process:2163): libfprint-aes2501-DEBUG: 16:48:02.016: 53017553: ../libfprint/drivers/aes2501.c:310 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.016: write 23 regs 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.018: all registers written 165s (process:2163): libfprint-aes2501-DEBUG: 16:48:02.018: 53019288: ../libfprint/drivers/aes2501.c:310 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.018: write 23 regs 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.019: all registers written 165s (process:2163): libfprint-aes2501-DEBUG: 16:48:02.020: 53021177: ../libfprint/drivers/aes2501.c:310 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.020: write 23 regs 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.021: all registers written 165s (process:2163): libfprint-aes2501-DEBUG: 16:48:02.022: 53022914: ../libfprint/drivers/aes2501.c:310 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.022: write 23 regs 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.023: all registers written 165s (process:2163): libfprint-aes2501-DEBUG: 16:48:02.023: 53024597: ../libfprint/drivers/aes2501.c:310 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.023: write 23 regs 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.025: all registers written 165s (process:2163): libfprint-aes2501-DEBUG: 16:48:02.025: 53026320: ../libfprint/drivers/aes2501.c:310 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.025: write 23 regs 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.026: all registers written 165s (process:2163): libfprint-aes2501-DEBUG: 16:48:02.027: 53028063: ../libfprint/drivers/aes2501.c:310 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.027: write 23 regs 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.028: all registers written 165s (process:2163): libfprint-aes2501-DEBUG: 16:48:02.029: 53029781: ../libfprint/drivers/aes2501.c:310 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.029: write 23 regs 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.030: all registers written 165s (process:2163): libfprint-aes2501-DEBUG: 16:48:02.030: 53031457: ../libfprint/drivers/aes2501.c:310 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.030: write 23 regs 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.032: all registers written 165s (process:2163): libfprint-aes2501-DEBUG: 16:48:02.032: 53033190: ../libfprint/drivers/aes2501.c:310 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.032: write 23 regs 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.033: all registers written 165s (process:2163): libfprint-aes2501-DEBUG: 16:48:02.034: 53034896: ../libfprint/drivers/aes2501.c:310 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.034: write 23 regs 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.035: all registers written 165s (process:2163): libfprint-aes2501-DEBUG: 16:48:02.035: 53036666: ../libfprint/drivers/aes2501.c:310 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.036: write 23 regs 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.037: all registers written 165s (process:2163): libfprint-aes2501-DEBUG: 16:48:02.037: 53038413: ../libfprint/drivers/aes2501.c:310 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.037: write 23 regs 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.038: all registers written 165s (process:2163): libfprint-aes2501-DEBUG: 16:48:02.039: 53040143: ../libfprint/drivers/aes2501.c:310 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.039: write 23 regs 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.040: all registers written 165s (process:2163): libfprint-aes2501-DEBUG: 16:48:02.041: 53041856: ../libfprint/drivers/aes2501.c:310 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.041: write 23 regs 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.042: all registers written 165s (process:2163): libfprint-aes2501-DEBUG: 16:48:02.042: 53043560: ../libfprint/drivers/aes2501.c:310 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.042: write 23 regs 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.044: all registers written 165s (process:2163): libfprint-aes2501-DEBUG: 16:48:02.044: 53045236: ../libfprint/drivers/aes2501.c:310 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.044: write 23 regs 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.045: all registers written 165s (process:2163): libfprint-aes2501-DEBUG: 16:48:02.046: 53046960: ../libfprint/drivers/aes2501.c:310 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.046: write 23 regs 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.047: all registers written 165s (process:2163): libfprint-aes2501-DEBUG: 16:48:02.047: 53048675: ../libfprint/drivers/aes2501.c:310 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.048: write 23 regs 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.049: all registers written 165s (process:2163): libfprint-aes2501-DEBUG: 16:48:02.049: 53050397: ../libfprint/drivers/aes2501.c:310 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.049: write 23 regs 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.050: all registers written 165s (process:2163): libfprint-aes2501-DEBUG: 16:48:02.051: 53052158: ../libfprint/drivers/aes2501.c:310 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.051: write 23 regs 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.052: all registers written 165s (process:2163): libfprint-aes2501-DEBUG: 16:48:02.053: 53053998: ../libfprint/drivers/aes2501.c:310 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.053: write 23 regs 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.054: all registers written 165s (process:2163): libfprint-aes2501-DEBUG: 16:48:02.055: 53055722: ../libfprint/drivers/aes2501.c:310 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.055: write 23 regs 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.056: all registers written 165s (process:2163): libfprint-aes2501-DEBUG: 16:48:02.056: 53057446: ../libfprint/drivers/aes2501.c:310 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.056: write 23 regs 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.058: all registers written 165s (process:2163): libfprint-aes2501-DEBUG: 16:48:02.058: 53059227: ../libfprint/drivers/aes2501.c:310 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.058: write 23 regs 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.059: all registers written 165s (process:2163): libfprint-aes2501-DEBUG: 16:48:02.060: 53060908: ../libfprint/drivers/aes2501.c:310 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.060: write 23 regs 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.061: all registers written 165s (process:2163): libfprint-aes2501-DEBUG: 16:48:02.062: 53062815: ../libfprint/drivers/aes2501.c:310 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.062: write 23 regs 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.063: all registers written 165s (process:2163): libfprint-aes2501-DEBUG: 16:48:02.063: 53064528: ../libfprint/drivers/aes2501.c:310 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.063: write 23 regs 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.065: all registers written 165s (process:2163): libfprint-aes2501-DEBUG: 16:48:02.065: 53066260: ../libfprint/drivers/aes2501.c:310 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.065: write 23 regs 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.066: all registers written 165s (process:2163): libfprint-aes2501-DEBUG: 16:48:02.067: 53068012: ../libfprint/drivers/aes2501.c:310 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.067: write 23 regs 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.068: all registers written 165s (process:2163): libfprint-aes2501-DEBUG: 16:48:02.069: 53069734: ../libfprint/drivers/aes2501.c:310 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.069: write 23 regs 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.070: all registers written 165s (process:2163): libfprint-aes2501-DEBUG: 16:48:02.070: 53071461: ../libfprint/drivers/aes2501.c:310 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.070: write 23 regs 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.071: all registers written 165s (process:2163): libfprint-aes2501-DEBUG: 16:48:02.072: 53073152: ../libfprint/drivers/aes2501.c:310 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.072: write 23 regs 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.073: all registers written 165s (process:2163): libfprint-aes2501-DEBUG: 16:48:02.074: 53074853: ../libfprint/drivers/aes2501.c:310 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.074: write 23 regs 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.075: all registers written 165s (process:2163): libfprint-aes2501-DEBUG: 16:48:02.075: 53076627: ../libfprint/drivers/aes2501.c:310 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.075: write 23 regs 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.077: all registers written 165s (process:2163): libfprint-aes2501-DEBUG: 16:48:02.077: 53078284: ../libfprint/drivers/aes2501.c:310 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.077: write 23 regs 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.078: all registers written 165s (process:2163): libfprint-aes2501-DEBUG: 16:48:02.079: 53079975: ../libfprint/drivers/aes2501.c:310 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.079: write 23 regs 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.080: all registers written 165s (process:2163): libfprint-aes2501-DEBUG: 16:48:02.081: 53081693: ../libfprint/drivers/aes2501.c:310 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.081: write 23 regs 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.082: all registers written 165s (process:2163): libfprint-aes2501-DEBUG: 16:48:02.082: 53083368: ../libfprint/drivers/aes2501.c:310 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.082: write 23 regs 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.083: all registers written 165s (process:2163): libfprint-aes2501-DEBUG: 16:48:02.084: 53085054: ../libfprint/drivers/aes2501.c:310 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.084: write 23 regs 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.085: all registers written 165s (process:2163): libfprint-aes2501-DEBUG: 16:48:02.086: 53086787: ../libfprint/drivers/aes2501.c:310 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.086: write 23 regs 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.087: all registers written 165s (process:2163): libfprint-aes2501-DEBUG: 16:48:02.087: 53088558: ../libfprint/drivers/aes2501.c:310 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.087: write 23 regs 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.089: all registers written 165s (process:2163): libfprint-aes2501-DEBUG: 16:48:02.089: 53090231: ../libfprint/drivers/aes2501.c:310 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.089: write 23 regs 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.090: all registers written 165s (process:2163): libfprint-aes2501-DEBUG: 16:48:02.091: 53091894: ../libfprint/drivers/aes2501.c:310 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.091: write 23 regs 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.092: all registers written 165s (process:2163): libfprint-aes2501-DEBUG: 16:48:02.092: 53093637: ../libfprint/drivers/aes2501.c:310 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.093: write 23 regs 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.094: all registers written 165s (process:2163): libfprint-aes2501-DEBUG: 16:48:02.094: 53095406: ../libfprint/drivers/aes2501.c:310 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.094: write 23 regs 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.095: all registers written 165s (process:2163): libfprint-aes2501-DEBUG: 16:48:02.096: 53097134: ../libfprint/drivers/aes2501.c:310 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.096: write 23 regs 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.097: all registers written 165s (process:2163): libfprint-aes2501-DEBUG: 16:48:02.098: 53098843: ../libfprint/drivers/aes2501.c:310 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.098: write 23 regs 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.099: all registers written 165s (process:2163): libfprint-aes2501-DEBUG: 16:48:02.099: 53100553: ../libfprint/drivers/aes2501.c:310 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.099: write 23 regs 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.101: all registers written 165s (process:2163): libfprint-aes2501-DEBUG: 16:48:02.101: 53102348: ../libfprint/drivers/aes2501.c:310 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.101: write 23 regs 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.102: all registers written 165s (process:2163): libfprint-aes2501-DEBUG: 16:48:02.103: 53104014: ../libfprint/drivers/aes2501.c:310 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.103: write 23 regs 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.104: all registers written 165s (process:2163): libfprint-aes2501-DEBUG: 16:48:02.105: 53105743: ../libfprint/drivers/aes2501.c:310 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.105: write 23 regs 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.106: all registers written 165s (process:2163): libfprint-aes2501-DEBUG: 16:48:02.106: 53107406: ../libfprint/drivers/aes2501.c:310 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.106: write 23 regs 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.107: all registers written 165s (process:2163): libfprint-aes2501-DEBUG: 16:48:02.108: 53109100: ../libfprint/drivers/aes2501.c:310 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.108: write 23 regs 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.109: all registers written 165s (process:2163): libfprint-aes2501-DEBUG: 16:48:02.110: 53110798: ../libfprint/drivers/aes2501.c:310 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.110: write 23 regs 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.111: all registers written 165s (process:2163): libfprint-aes2501-DEBUG: 16:48:02.111: 53112577: ../libfprint/drivers/aes2501.c:310 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.111: write 23 regs 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.113: all registers written 165s (process:2163): libfprint-aes2501-DEBUG: 16:48:02.113: 53114318: ../libfprint/drivers/aes2501.c:310 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.113: write 23 regs 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.114: all registers written 165s (process:2163): libfprint-aes2501-DEBUG: 16:48:02.115: 53115997: ../libfprint/drivers/aes2501.c:310 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.115: write 23 regs 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.116: all registers written 165s (process:2163): libfprint-aes2501-DEBUG: 16:48:02.117: 53117764: ../libfprint/drivers/aes2501.c:310 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.117: write 23 regs 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.118: all registers written 165s (process:2163): libfprint-aes2501-DEBUG: 16:48:02.118: 53119499: ../libfprint/drivers/aes2501.c:310 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.118: write 23 regs 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.120: all registers written 165s (process:2163): libfprint-aes2501-DEBUG: 16:48:02.120: 53121259: ../libfprint/drivers/aes2501.c:310 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.120: write 23 regs 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.121: all registers written 165s (process:2163): libfprint-aes2501-DEBUG: 16:48:02.122: 53122999: ../libfprint/drivers/aes2501.c:310 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.122: write 23 regs 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.123: all registers written 165s (process:2163): libfprint-aes2501-DEBUG: 16:48:02.124: 53124740: ../libfprint/drivers/aes2501.c:310 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.124: write 23 regs 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.125: all registers written 165s (process:2163): libfprint-aes2501-DEBUG: 16:48:02.125: 53126467: ../libfprint/drivers/aes2501.c:310 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.125: write 23 regs 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.127: all registers written 165s (process:2163): libfprint-aes2501-DEBUG: 16:48:02.127: 53128252: ../libfprint/drivers/aes2501.c:310 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.127: write 23 regs 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.128: all registers written 165s (process:2163): libfprint-aes2501-DEBUG: 16:48:02.129: 53129887: ../libfprint/drivers/aes2501.c:310 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.129: write 23 regs 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.130: all registers written 165s (process:2163): libfprint-aes2501-DEBUG: 16:48:02.130: 53131602: ../libfprint/drivers/aes2501.c:310 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.130: write 23 regs 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.132: all registers written 165s (process:2163): libfprint-aes2501-DEBUG: 16:48:02.132: 53133327: ../libfprint/drivers/aes2501.c:310 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.132: write 23 regs 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.133: all registers written 165s (process:2163): libfprint-aes2501-DEBUG: 16:48:02.134: 53135005: ../libfprint/drivers/aes2501.c:310 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.134: write 23 regs 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.135: all registers written 165s (process:2163): libfprint-aes2501-DEBUG: 16:48:02.136: 53136768: ../libfprint/drivers/aes2501.c:310 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.136: write 23 regs 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.137: all registers written 165s (process:2163): libfprint-aes2501-DEBUG: 16:48:02.137: 53138488: ../libfprint/drivers/aes2501.c:310 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.137: write 23 regs 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.139: all registers written 165s (process:2163): libfprint-aes2501-DEBUG: 16:48:02.139: 53140201: ../libfprint/drivers/aes2501.c:310 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.139: write 23 regs 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.140: all registers written 165s (process:2163): libfprint-aes2501-DEBUG: 16:48:02.141: 53141942: ../libfprint/drivers/aes2501.c:310 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.141: write 23 regs 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.142: all registers written 165s (process:2163): libfprint-aes2501-DEBUG: 16:48:02.142: 53143635: ../libfprint/drivers/aes2501.c:310 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.143: write 23 regs 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.144: all registers written 165s (process:2163): libfprint-aes2501-DEBUG: 16:48:02.144: 53145389: ../libfprint/drivers/aes2501.c:310 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.144: write 23 regs 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.145: all registers written 165s (process:2163): libfprint-aes2501-DEBUG: 16:48:02.146: 53147100: ../libfprint/drivers/aes2501.c:310 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.146: write 23 regs 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.147: all registers written 165s (process:2163): libfprint-aes2501-DEBUG: 16:48:02.148: 53148827: ../libfprint/drivers/aes2501.c:310 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.148: write 23 regs 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.149: all registers written 165s (process:2163): libfprint-aes2501-DEBUG: 16:48:02.149: 53150546: ../libfprint/drivers/aes2501.c:310 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.149: write 23 regs 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.151: all registers written 165s (process:2163): libfprint-aes2501-DEBUG: 16:48:02.151: 53152264: ../libfprint/drivers/aes2501.c:310 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.151: write 23 regs 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.152: all registers written 165s (process:2163): libfprint-aes2501-DEBUG: 16:48:02.153: 53154031: ../libfprint/drivers/aes2501.c:310 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.153: write 23 regs 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.154: all registers written 165s (process:2163): libfprint-aes2501-DEBUG: 16:48:02.155: 53155747: ../libfprint/drivers/aes2501.c:310 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.155: write 23 regs 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.156: all registers written 165s (process:2163): libfprint-aes2501-DEBUG: 16:48:02.156: 53157515: ../libfprint/drivers/aes2501.c:310 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.156: write 23 regs 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.158: all registers written 165s (process:2163): libfprint-aes2501-DEBUG: 16:48:02.158: 53159247: ../libfprint/drivers/aes2501.c:310 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.158: write 23 regs 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.159: all registers written 165s (process:2163): libfprint-aes2501-DEBUG: 16:48:02.160: 53160951: ../libfprint/drivers/aes2501.c:310 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.160: write 23 regs 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.161: all registers written 165s (process:2163): libfprint-aes2501-DEBUG: 16:48:02.162: 53162731: ../libfprint/drivers/aes2501.c:310 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.162: write 23 regs 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.163: all registers written 165s (process:2163): libfprint-aes2501-DEBUG: 16:48:02.163: 53164442: ../libfprint/drivers/aes2501.c:310 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.163: write 23 regs 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.164: all registers written 165s (process:2163): libfprint-aes2501-DEBUG: 16:48:02.165: 53166111: ../libfprint/drivers/aes2501.c:310 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.165: write 23 regs 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.166: all registers written 165s (process:2163): libfprint-aes2501-DEBUG: 16:48:02.167: 53167818: ../libfprint/drivers/aes2501.c:310 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.167: write 23 regs 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.168: all registers written 165s (process:2163): libfprint-aes2501-DEBUG: 16:48:02.168: 53169607: ../libfprint/drivers/aes2501.c:310 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.168: write 23 regs 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.170: all registers written 165s (process:2163): libfprint-aes2501-DEBUG: 16:48:02.170: 53171288: ../libfprint/drivers/aes2501.c:310 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.170: write 23 regs 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.171: all registers written 165s (process:2163): libfprint-aes2501-DEBUG: 16:48:02.172: 53173001: ../libfprint/drivers/aes2501.c:310 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.172: write 23 regs 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.173: all registers written 165s (process:2163): libfprint-aes2501-DEBUG: 16:48:02.173: 53174654: ../libfprint/drivers/aes2501.c:310 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.174: write 23 regs 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.175: all registers written 165s (process:2163): libfprint-aes2501-DEBUG: 16:48:02.175: 53176326: ../libfprint/drivers/aes2501.c:310 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.175: write 23 regs 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.176: all registers written 165s (process:2163): libfprint-aes2501-DEBUG: 16:48:02.177: 53178077: ../libfprint/drivers/aes2501.c:310 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.177: write 23 regs 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.178: all registers written 165s (process:2163): libfprint-aes2501-DEBUG: 16:48:02.179: 53179771: ../libfprint/drivers/aes2501.c:310 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.179: write 23 regs 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.180: all registers written 165s (process:2163): libfprint-aes2501-DEBUG: 16:48:02.180: 53181541: ../libfprint/drivers/aes2501.c:310 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.180: write 23 regs 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.182: all registers written 165s (process:2163): libfprint-aes2501-DEBUG: 16:48:02.182: 53183239: ../libfprint/drivers/aes2501.c:310 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.182: write 23 regs 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.183: all registers written 165s (process:2163): libfprint-aes2501-DEBUG: 16:48:02.184: 53184938: ../libfprint/drivers/aes2501.c:310 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.184: write 23 regs 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.185: all registers written 165s (process:2163): libfprint-aes2501-DEBUG: 16:48:02.186: 53186692: ../libfprint/drivers/aes2501.c:310 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.186: write 23 regs 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.187: all registers written 165s (process:2163): libfprint-aes2501-DEBUG: 16:48:02.187: 53188387: ../libfprint/drivers/aes2501.c:310 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.187: write 23 regs 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.188: all registers written 165s (process:2163): libfprint-aes2501-DEBUG: 16:48:02.189: 53190115: ../libfprint/drivers/aes2501.c:310 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.189: write 23 regs 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.190: all registers written 165s (process:2163): libfprint-aes2501-DEBUG: 16:48:02.191: 53191794: ../libfprint/drivers/aes2501.c:310 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.191: write 23 regs 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.192: all registers written 165s (process:2163): libfprint-aes2501-DEBUG: 16:48:02.192: 53193522: ../libfprint/drivers/aes2501.c:310 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.192: write 23 regs 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.194: all registers written 165s (process:2163): libfprint-aes2501-DEBUG: 16:48:02.194: 53195223: ../libfprint/drivers/aes2501.c:310 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.194: write 23 regs 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.195: all registers written 165s (process:2163): libfprint-aes2501-DEBUG: 16:48:02.196: 53196908: ../libfprint/drivers/aes2501.c:310 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.196: write 23 regs 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.197: all registers written 165s (process:2163): libfprint-aes2501-DEBUG: 16:48:02.197: 53198541: ../libfprint/drivers/aes2501.c:310 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.197: write 23 regs 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.199: all registers written 165s (process:2163): libfprint-aes2501-DEBUG: 16:48:02.199: 53200257: ../libfprint/drivers/aes2501.c:310 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.199: write 23 regs 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.200: all registers written 165s (process:2163): libfprint-aes2501-DEBUG: 16:48:02.201: 53201935: ../libfprint/drivers/aes2501.c:310 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.201: write 23 regs 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.202: all registers written 165s (process:2163): libfprint-aes2501-DEBUG: 16:48:02.202: 53203651: ../libfprint/drivers/aes2501.c:310 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.202: write 23 regs 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.204: all registers written 165s (process:2163): libfprint-aes2501-DEBUG: 16:48:02.204: 53205383: ../libfprint/drivers/aes2501.c:310 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.204: write 23 regs 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.205: all registers written 165s (process:2163): libfprint-aes2501-DEBUG: 16:48:02.206: 53207099: ../libfprint/drivers/aes2501.c:310 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.206: write 23 regs 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.207: all registers written 165s (process:2163): libfprint-aes2501-DEBUG: 16:48:02.208: 53208808: ../libfprint/drivers/aes2501.c:310 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.208: write 23 regs 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.209: all registers written 165s (process:2163): libfprint-aes2501-DEBUG: 16:48:02.209: 53210580: ../libfprint/drivers/aes2501.c:310 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.209: write 23 regs 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.211: all registers written 165s (process:2163): libfprint-aes2501-DEBUG: 16:48:02.211: 53212271: ../libfprint/drivers/aes2501.c:310 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.211: write 23 regs 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.212: all registers written 165s (process:2163): libfprint-aes2501-DEBUG: 16:48:02.213: 53213962: ../libfprint/drivers/aes2501.c:310 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.213: write 23 regs 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.214: all registers written 165s (process:2163): libfprint-aes2501-DEBUG: 16:48:02.214: 53215677: ../libfprint/drivers/aes2501.c:310 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.215: write 23 regs 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.216: all registers written 165s (process:2163): libfprint-aes2501-DEBUG: 16:48:02.216: 53217419: ../libfprint/drivers/aes2501.c:310 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.216: write 23 regs 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.217: all registers written 165s (process:2163): libfprint-aes2501-DEBUG: 16:48:02.218: 53219168: ../libfprint/drivers/aes2501.c:310 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.218: write 23 regs 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.219: all registers written 165s (process:2163): libfprint-aes2501-DEBUG: 16:48:02.220: 53220862: ../libfprint/drivers/aes2501.c:310 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.220: write 23 regs 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.221: all registers written 165s (process:2163): libfprint-aes2501-DEBUG: 16:48:02.221: 53222585: ../libfprint/drivers/aes2501.c:310 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.221: write 23 regs 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.223: all registers written 165s (process:2163): libfprint-aes2501-DEBUG: 16:48:02.223: 53224403: ../libfprint/drivers/aes2501.c:310 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.223: write 23 regs 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.224: all registers written 165s (process:2163): libfprint-aes2501-DEBUG: 16:48:02.225: 53226116: ../libfprint/drivers/aes2501.c:310 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.225: write 23 regs 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.226: all registers written 165s (process:2163): libfprint-aes2501-DEBUG: 16:48:02.227: 53227816: ../libfprint/drivers/aes2501.c:310 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.227: write 23 regs 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.228: all registers written 165s (process:2163): libfprint-aes2501-DEBUG: 16:48:02.228: 53229581: ../libfprint/drivers/aes2501.c:310 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.228: write 23 regs 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.230: all registers written 165s (process:2163): libfprint-aes2501-DEBUG: 16:48:02.230: 53231192: ../libfprint/drivers/aes2501.c:310 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.230: write 23 regs 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.231: all registers written 165s (process:2163): libfprint-aes2501-DEBUG: 16:48:02.232: 53232931: ../libfprint/drivers/aes2501.c:310 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.232: write 23 regs 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.233: all registers written 165s (process:2163): libfprint-aes2501-DEBUG: 16:48:02.233: 53234636: ../libfprint/drivers/aes2501.c:310 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.234: write 23 regs 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.235: all registers written 165s (process:2163): libfprint-aes2501-DEBUG: 16:48:02.235: 53236335: ../libfprint/drivers/aes2501.c:310 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.235: write 23 regs 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.236: all registers written 165s (process:2163): libfprint-aes2501-DEBUG: 16:48:02.237: 53238076: ../libfprint/drivers/aes2501.c:310 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.237: write 23 regs 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.238: all registers written 165s (process:2163): libfprint-aes2501-DEBUG: 16:48:02.239: 53239794: ../libfprint/drivers/aes2501.c:310 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.239: write 23 regs 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.240: all registers written 165s (process:2163): libfprint-aes2501-DEBUG: 16:48:02.240: 53241526: ../libfprint/drivers/aes2501.c:310 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.240: write 23 regs 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.242: all registers written 165s (process:2163): libfprint-aes2501-DEBUG: 16:48:02.242: 53243210: ../libfprint/drivers/aes2501.c:310 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.242: write 23 regs 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.243: all registers written 165s (process:2163): libfprint-aes2501-DEBUG: 16:48:02.244: 53244924: ../libfprint/drivers/aes2501.c:310 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.244: write 23 regs 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.245: all registers written 165s (process:2163): libfprint-aes2501-DEBUG: 16:48:02.245: 53246615: ../libfprint/drivers/aes2501.c:310 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.245: write 23 regs 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.247: all registers written 165s (process:2163): libfprint-aes2501-DEBUG: 16:48:02.247: 53248249: ../libfprint/drivers/aes2501.c:310 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.247: write 23 regs 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.248: all registers written 165s (process:2163): libfprint-aes2501-DEBUG: 16:48:02.249: 53249945: ../libfprint/drivers/aes2501.c:310 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.249: write 23 regs 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.250: all registers written 165s (process:2163): libfprint-aes2501-DEBUG: 16:48:02.250: 53251575: ../libfprint/drivers/aes2501.c:310 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.250: write 23 regs 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.252: all registers written 165s (process:2163): libfprint-aes2501-DEBUG: 16:48:02.252: 53253228: ../libfprint/drivers/aes2501.c:310 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.252: write 23 regs 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.253: all registers written 165s (process:2163): libfprint-aes2501-DEBUG: 16:48:02.254: 53254935: ../libfprint/drivers/aes2501.c:310 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.254: write 23 regs 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.255: all registers written 165s (process:2163): libfprint-aes2501-DEBUG: 16:48:02.255: 53256582: ../libfprint/drivers/aes2501.c:310 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.255: write 23 regs 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.257: all registers written 165s (process:2163): libfprint-aes2501-DEBUG: 16:48:02.257: 53258377: ../libfprint/drivers/aes2501.c:310 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.257: write 23 regs 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.258: all registers written 165s (process:2163): libfprint-aes2501-DEBUG: 16:48:02.259: 53260111: ../libfprint/drivers/aes2501.c:310 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.259: write 23 regs 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.260: all registers written 165s (process:2163): libfprint-aes2501-DEBUG: 16:48:02.261: 53261908: ../libfprint/drivers/aes2501.c:310 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.261: write 23 regs 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.262: all registers written 165s (process:2163): libfprint-aes2501-DEBUG: 16:48:02.262: 53263579: ../libfprint/drivers/aes2501.c:310 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.262: write 23 regs 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.264: all registers written 165s (process:2163): libfprint-aes2501-DEBUG: 16:48:02.264: 53265298: ../libfprint/drivers/aes2501.c:310 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.264: write 23 regs 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.265: all registers written 165s (process:2163): libfprint-aes2501-DEBUG: 16:48:02.266: 53267032: ../libfprint/drivers/aes2501.c:310 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.266: write 23 regs 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.267: all registers written 165s (process:2163): libfprint-aes2501-DEBUG: 16:48:02.268: 53268729: ../libfprint/drivers/aes2501.c:310 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.268: write 23 regs 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.269: all registers written 165s (process:2163): libfprint-aes2501-DEBUG: 16:48:02.269: 53270409: ../libfprint/drivers/aes2501.c:310 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.269: write 23 regs 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.270: all registers written 165s (process:2163): libfprint-aes2501-DEBUG: 16:48:02.271: 53272139: ../libfprint/drivers/aes2501.c:310 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.271: write 23 regs 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.272: all registers written 165s (process:2163): libfprint-aes2501-DEBUG: 16:48:02.273: 53273842: ../libfprint/drivers/aes2501.c:310 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.273: write 23 regs 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.274: all registers written 165s (process:2163): libfprint-aes2501-DEBUG: 16:48:02.274: 53275547: ../libfprint/drivers/aes2501.c:310 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.274: write 23 regs 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.276: all registers written 165s (process:2163): libfprint-aes2501-DEBUG: 16:48:02.276: 53277279: ../libfprint/drivers/aes2501.c:310 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.276: write 23 regs 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.277: all registers written 165s (process:2163): libfprint-aes2501-DEBUG: 16:48:02.278: 53278965: ../libfprint/drivers/aes2501.c:310 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.278: write 23 regs 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.279: all registers written 165s (process:2163): libfprint-aes2501-DEBUG: 16:48:02.279: 53280626: ../libfprint/drivers/aes2501.c:310 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.279: write 23 regs 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.281: all registers written 165s (process:2163): libfprint-aes2501-DEBUG: 16:48:02.281: 53282348: ../libfprint/drivers/aes2501.c:310 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.281: write 23 regs 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.282: all registers written 165s (process:2163): libfprint-aes2501-DEBUG: 16:48:02.283: 53284085: ../libfprint/drivers/aes2501.c:310 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.283: write 23 regs 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.284: all registers written 165s (process:2163): libfprint-aes2501-DEBUG: 16:48:02.285: 53285782: ../libfprint/drivers/aes2501.c:310 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.285: write 23 regs 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.286: all registers written 165s (process:2163): libfprint-aes2501-DEBUG: 16:48:02.286: 53287489: ../libfprint/drivers/aes2501.c:310 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.286: write 23 regs 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.288: all registers written 165s (process:2163): libfprint-aes2501-DEBUG: 16:48:02.288: 53289200: ../libfprint/drivers/aes2501.c:310 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.288: write 23 regs 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.289: all registers written 165s (process:2163): libfprint-aes2501-DEBUG: 16:48:02.290: 53290893: ../libfprint/drivers/aes2501.c:310 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.290: write 23 regs 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.291: all registers written 165s (process:2163): libfprint-aes2501-DEBUG: 16:48:02.291: 53292514: ../libfprint/drivers/aes2501.c:310 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.291: write 23 regs 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.293: all registers written 165s (process:2163): libfprint-aes2501-DEBUG: 16:48:02.293: 53294244: ../libfprint/drivers/aes2501.c:310 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.293: write 23 regs 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.294: all registers written 165s (process:2163): libfprint-aes2501-DEBUG: 16:48:02.295: 53295934: ../libfprint/drivers/aes2501.c:310 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.295: write 23 regs 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.296: all registers written 165s (process:2163): libfprint-aes2501-DEBUG: 16:48:02.296: 53297680: ../libfprint/drivers/aes2501.c:310 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.297: write 23 regs 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.298: all registers written 165s (process:2163): libfprint-aes2501-DEBUG: 16:48:02.298: 53299361: ../libfprint/drivers/aes2501.c:310 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.298: write 23 regs 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.300: all registers written 165s (process:2163): libfprint-aes2501-DEBUG: 16:48:02.300: 53301213: ../libfprint/drivers/aes2501.c:310 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.300: write 23 regs 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.301: all registers written 165s (process:2163): libfprint-aes2501-DEBUG: 16:48:02.302: 53302948: ../libfprint/drivers/aes2501.c:310 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.302: write 23 regs 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.303: all registers written 165s (process:2163): libfprint-aes2501-DEBUG: 16:48:02.303: 53304686: ../libfprint/drivers/aes2501.c:310 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.304: write 23 regs 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.305: all registers written 165s (process:2163): libfprint-aes2501-DEBUG: 16:48:02.305: 53306399: ../libfprint/drivers/aes2501.c:310 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.305: write 23 regs 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.306: all registers written 165s (process:2163): libfprint-aes2501-DEBUG: 16:48:02.307: 53308105: ../libfprint/drivers/aes2501.c:310 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.307: write 23 regs 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.308: all registers written 165s (process:2163): libfprint-aes2501-DEBUG: 16:48:02.309: 53309819: ../libfprint/drivers/aes2501.c:310 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.309: write 23 regs 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.310: all registers written 165s (process:2163): libfprint-aes2501-DEBUG: 16:48:02.310: 53311503: ../libfprint/drivers/aes2501.c:310 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.310: write 23 regs 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.312: all registers written 165s (process:2163): libfprint-aes2501-DEBUG: 16:48:02.312: 53313261: ../libfprint/drivers/aes2501.c:310 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.312: write 23 regs 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.313: all registers written 165s (process:2163): libfprint-aes2501-DEBUG: 16:48:02.314: 53314946: ../libfprint/drivers/aes2501.c:310 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.314: write 23 regs 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.315: all registers written 165s (process:2163): libfprint-aes2501-DEBUG: 16:48:02.315: 53316665: ../libfprint/drivers/aes2501.c:310 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.316: write 23 regs 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.317: all registers written 165s (process:2163): libfprint-aes2501-DEBUG: 16:48:02.317: 53318318: ../libfprint/drivers/aes2501.c:310 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.317: write 23 regs 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.318: all registers written 165s (process:2163): libfprint-aes2501-DEBUG: 16:48:02.319: 53319993: ../libfprint/drivers/aes2501.c:310 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.319: write 23 regs 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.320: all registers written 165s (process:2163): libfprint-aes2501-DEBUG: 16:48:02.321: 53321742: ../libfprint/drivers/aes2501.c:310 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.321: write 23 regs 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.322: all registers written 165s (process:2163): libfprint-aes2501-DEBUG: 16:48:02.322: 53323433: ../libfprint/drivers/aes2501.c:310 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.322: write 23 regs 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.323: all registers written 165s (process:2163): libfprint-aes2501-DEBUG: 16:48:02.324: 53325130: ../libfprint/drivers/aes2501.c:310 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.324: write 23 regs 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.325: all registers written 165s (process:2163): libfprint-aes2501-DEBUG: 16:48:02.326: 53326900: ../libfprint/drivers/aes2501.c:310 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.326: write 23 regs 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.327: all registers written 165s (process:2163): libfprint-aes2501-DEBUG: 16:48:02.328: 53328697: ../libfprint/drivers/aes2501.c:310 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.328: write 23 regs 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.329: all registers written 165s (process:2163): libfprint-aes2501-DEBUG: 16:48:02.329: 53330404: ../libfprint/drivers/aes2501.c:310 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.329: write 23 regs 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.330: all registers written 165s (process:2163): libfprint-aes2501-DEBUG: 16:48:02.331: 53332102: ../libfprint/drivers/aes2501.c:310 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.331: write 23 regs 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.332: all registers written 165s (process:2163): libfprint-aes2501-DEBUG: 16:48:02.333: 53333868: ../libfprint/drivers/aes2501.c:310 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.333: write 23 regs 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.334: all registers written 165s (process:2163): libfprint-aes2501-DEBUG: 16:48:02.334: 53335537: ../libfprint/drivers/aes2501.c:310 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.334: write 23 regs 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.336: all registers written 165s (process:2163): libfprint-aes2501-DEBUG: 16:48:02.336: 53337259: ../libfprint/drivers/aes2501.c:310 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.336: write 23 regs 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.337: all registers written 165s (process:2163): libfprint-aes2501-DEBUG: 16:48:02.338: 53338904: ../libfprint/drivers/aes2501.c:310 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.338: write 23 regs 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.339: all registers written 165s (process:2163): libfprint-aes2501-DEBUG: 16:48:02.339: 53340607: ../libfprint/drivers/aes2501.c:310 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.339: write 23 regs 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.341: all registers written 165s (process:2163): libfprint-aes2501-DEBUG: 16:48:02.341: 53342307: ../libfprint/drivers/aes2501.c:310 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.341: write 23 regs 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.342: all registers written 165s (process:2163): libfprint-aes2501-DEBUG: 16:48:02.343: 53344033: ../libfprint/drivers/aes2501.c:310 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.343: write 23 regs 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.344: all registers written 165s (process:2163): libfprint-aes2501-DEBUG: 16:48:02.345: 53345794: ../libfprint/drivers/aes2501.c:310 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.345: write 23 regs 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.346: all registers written 165s (process:2163): libfprint-aes2501-DEBUG: 16:48:02.346: 53347488: ../libfprint/drivers/aes2501.c:310 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.346: write 23 regs 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.348: all registers written 165s (process:2163): libfprint-aes2501-DEBUG: 16:48:02.348: 53349240: ../libfprint/drivers/aes2501.c:310 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.348: write 23 regs 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.349: all registers written 165s (process:2163): libfprint-aes2501-DEBUG: 16:48:02.350: 53350891: ../libfprint/drivers/aes2501.c:310 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.350: write 23 regs 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.351: all registers written 165s (process:2163): libfprint-device-DEBUG: 16:48:02.351: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 165s (process:2163): libfprint-image_device-DEBUG: 16:48:02.351: Image device reported finger status: on 165s (process:2163): libfprint-image_device-DEBUG: 16:48:02.351: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 165s (process:2163): libfprint-aes2501-DEBUG: 16:48:02.351: 53352683: ../libfprint/drivers/aes2501.c:581 165s (process:2163): libfprint-SSM-DEBUG: 16:48:02.351: [aes2501] CAPTURE_NUM_STATES entering state 0 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.351: write 26 regs 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.353: all registers written 165s (process:2163): libfprint-SSM-DEBUG: 16:48:02.353: [aes2501] CAPTURE_NUM_STATES entering state 1 165s (process:2163): libfprint-SSM-DEBUG: 16:48:02.353: [aes2501] CAPTURE_NUM_STATES entering state 2 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.353: write 7 regs 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.354: all registers written 165s (process:2163): libfprint-SSM-DEBUG: 16:48:02.354: [aes2501] CAPTURE_NUM_STATES entering state 3 165s (process:2163): libfprint-SSM-DEBUG: 16:48:02.354: [aes2501] CAPTURE_NUM_STATES entering state 4 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.354: write 7 regs 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.355: all registers written 165s (process:2163): libfprint-SSM-DEBUG: 16:48:02.355: [aes2501] CAPTURE_NUM_STATES entering state 5 165s (process:2163): libfprint-aes2501-DEBUG: 16:48:02.355: sum=5 165s (process:2163): libfprint-aes2501-DEBUG: 16:48:02.355: ADREFHI is 50 165s (process:2163): libfprint-SSM-DEBUG: 16:48:02.355: [aes2501] CAPTURE_NUM_STATES entering state 4 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.355: write 7 regs 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.356: all registers written 165s (process:2163): libfprint-SSM-DEBUG: 16:48:02.356: [aes2501] CAPTURE_NUM_STATES entering state 5 165s (process:2163): libfprint-aes2501-DEBUG: 16:48:02.356: sum=8 165s (process:2163): libfprint-aes2501-DEBUG: 16:48:02.356: ADREFHI is 48 165s (process:2163): libfprint-SSM-DEBUG: 16:48:02.356: [aes2501] CAPTURE_NUM_STATES entering state 4 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.356: write 7 regs 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.357: all registers written 165s (process:2163): libfprint-SSM-DEBUG: 16:48:02.357: [aes2501] CAPTURE_NUM_STATES entering state 5 165s (process:2163): libfprint-aes2501-DEBUG: 16:48:02.357: sum=19 165s (process:2163): libfprint-aes2501-DEBUG: 16:48:02.357: ADREFHI is 40 165s (process:2163): libfprint-SSM-DEBUG: 16:48:02.357: [aes2501] CAPTURE_NUM_STATES entering state 4 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.357: write 7 regs 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.358: all registers written 165s (process:2163): libfprint-SSM-DEBUG: 16:48:02.358: [aes2501] CAPTURE_NUM_STATES entering state 5 165s (process:2163): libfprint-aes2501-DEBUG: 16:48:02.358: sum=60 165s (process:2163): libfprint-aes2501-DEBUG: 16:48:02.358: ADREFHI is 38 165s (process:2163): libfprint-SSM-DEBUG: 16:48:02.358: [aes2501] CAPTURE_NUM_STATES entering state 4 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.358: write 7 regs 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.359: all registers written 165s (process:2163): libfprint-SSM-DEBUG: 16:48:02.359: [aes2501] CAPTURE_NUM_STATES entering state 5 165s (process:2163): libfprint-aes2501-DEBUG: 16:48:02.359: sum=123 165s (process:2163): libfprint-aes2501-DEBUG: 16:48:02.359: ADREFHI is 30 165s (process:2163): libfprint-SSM-DEBUG: 16:48:02.359: [aes2501] CAPTURE_NUM_STATES entering state 4 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.359: write 7 regs 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.360: all registers written 165s (process:2163): libfprint-SSM-DEBUG: 16:48:02.360: [aes2501] CAPTURE_NUM_STATES entering state 5 165s (process:2163): libfprint-aes2501-DEBUG: 16:48:02.360: sum=226 165s (process:2163): libfprint-aes2501-DEBUG: 16:48:02.360: ADREFHI is 28 165s (process:2163): libfprint-SSM-DEBUG: 16:48:02.360: [aes2501] CAPTURE_NUM_STATES entering state 4 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.360: write 7 regs 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.361: all registers written 165s (process:2163): libfprint-SSM-DEBUG: 16:48:02.361: [aes2501] CAPTURE_NUM_STATES entering state 5 165s (process:2163): libfprint-aes2501-DEBUG: 16:48:02.361: sum=461 165s (process:2163): libfprint-aes2501-DEBUG: 16:48:02.361: ADREFHI is 28 165s (process:2163): libfprint-SSM-DEBUG: 16:48:02.361: [aes2501] CAPTURE_NUM_STATES entering state 4 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.361: write 7 regs 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.362: all registers written 165s (process:2163): libfprint-SSM-DEBUG: 16:48:02.362: [aes2501] CAPTURE_NUM_STATES entering state 5 165s (process:2163): libfprint-aes2501-DEBUG: 16:48:02.362: sum=466 165s (process:2163): libfprint-aes2501-DEBUG: 16:48:02.362: ADREFHI is 28 165s (process:2163): libfprint-SSM-DEBUG: 16:48:02.362: [aes2501] CAPTURE_NUM_STATES entering state 4 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.362: write 7 regs 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.362: all registers written 165s (process:2163): libfprint-SSM-DEBUG: 16:48:02.362: [aes2501] CAPTURE_NUM_STATES entering state 5 165s (process:2163): libfprint-aes2501-DEBUG: 16:48:02.363: sum=465 165s (process:2163): libfprint-aes2501-DEBUG: 16:48:02.363: ADREFHI is 28 165s (process:2163): libfprint-SSM-DEBUG: 16:48:02.363: [aes2501] CAPTURE_NUM_STATES entering state 4 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.363: write 7 regs 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.363: all registers written 165s (process:2163): libfprint-SSM-DEBUG: 16:48:02.363: [aes2501] CAPTURE_NUM_STATES entering state 5 165s (process:2163): libfprint-aes2501-DEBUG: 16:48:02.364: sum=620 165s (process:2163): libfprint-aes2501-DEBUG: 16:48:02.364: ADREFHI is 28 165s (process:2163): libfprint-SSM-DEBUG: 16:48:02.364: [aes2501] CAPTURE_NUM_STATES entering state 4 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.364: write 7 regs 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.364: all registers written 165s (process:2163): libfprint-SSM-DEBUG: 16:48:02.364: [aes2501] CAPTURE_NUM_STATES entering state 5 165s (process:2163): libfprint-aes2501-DEBUG: 16:48:02.365: sum=629 165s (process:2163): libfprint-aes2501-DEBUG: 16:48:02.365: ADREFHI is 28 165s (process:2163): libfprint-SSM-DEBUG: 16:48:02.365: [aes2501] CAPTURE_NUM_STATES entering state 4 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.365: write 7 regs 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.365: all registers written 165s (process:2163): libfprint-SSM-DEBUG: 16:48:02.365: [aes2501] CAPTURE_NUM_STATES entering state 5 165s (process:2163): libfprint-aes2501-DEBUG: 16:48:02.366: sum=615 165s (process:2163): libfprint-aes2501-DEBUG: 16:48:02.366: ADREFHI is 28 165s (process:2163): libfprint-SSM-DEBUG: 16:48:02.366: [aes2501] CAPTURE_NUM_STATES entering state 4 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.366: write 7 regs 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.366: all registers written 165s (process:2163): libfprint-SSM-DEBUG: 16:48:02.366: [aes2501] CAPTURE_NUM_STATES entering state 5 165s (process:2163): libfprint-aes2501-DEBUG: 16:48:02.367: sum=585 165s (process:2163): libfprint-aes2501-DEBUG: 16:48:02.367: ADREFHI is 28 165s (process:2163): libfprint-SSM-DEBUG: 16:48:02.367: [aes2501] CAPTURE_NUM_STATES entering state 4 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.367: write 7 regs 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.367: all registers written 165s (process:2163): libfprint-SSM-DEBUG: 16:48:02.367: [aes2501] CAPTURE_NUM_STATES entering state 5 165s (process:2163): libfprint-aes2501-DEBUG: 16:48:02.368: sum=581 165s (process:2163): libfprint-aes2501-DEBUG: 16:48:02.368: ADREFHI is 28 165s (process:2163): libfprint-SSM-DEBUG: 16:48:02.368: [aes2501] CAPTURE_NUM_STATES entering state 4 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.368: write 7 regs 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.368: all registers written 165s (process:2163): libfprint-SSM-DEBUG: 16:48:02.368: [aes2501] CAPTURE_NUM_STATES entering state 5 165s (process:2163): libfprint-aes2501-DEBUG: 16:48:02.369: sum=418 165s (process:2163): libfprint-aes2501-DEBUG: 16:48:02.369: ADREFHI is 28 165s (process:2163): libfprint-SSM-DEBUG: 16:48:02.369: [aes2501] CAPTURE_NUM_STATES entering state 4 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.369: write 7 regs 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.369: all registers written 165s (process:2163): libfprint-SSM-DEBUG: 16:48:02.369: [aes2501] CAPTURE_NUM_STATES entering state 5 165s (process:2163): libfprint-aes2501-DEBUG: 16:48:02.370: sum=406 165s (process:2163): libfprint-aes2501-DEBUG: 16:48:02.370: ADREFHI is 28 165s (process:2163): libfprint-SSM-DEBUG: 16:48:02.370: [aes2501] CAPTURE_NUM_STATES entering state 4 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.370: write 7 regs 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.370: all registers written 165s (process:2163): libfprint-SSM-DEBUG: 16:48:02.370: [aes2501] CAPTURE_NUM_STATES entering state 5 165s (process:2163): libfprint-aes2501-DEBUG: 16:48:02.371: sum=389 165s (process:2163): libfprint-aes2501-DEBUG: 16:48:02.371: ADREFHI is 28 165s (process:2163): libfprint-SSM-DEBUG: 16:48:02.371: [aes2501] CAPTURE_NUM_STATES entering state 4 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.371: write 7 regs 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.371: all registers written 165s (process:2163): libfprint-SSM-DEBUG: 16:48:02.371: [aes2501] CAPTURE_NUM_STATES entering state 5 165s (process:2163): libfprint-aes2501-DEBUG: 16:48:02.372: sum=388 165s (process:2163): libfprint-aes2501-DEBUG: 16:48:02.372: ADREFHI is 28 165s (process:2163): libfprint-SSM-DEBUG: 16:48:02.372: [aes2501] CAPTURE_NUM_STATES entering state 4 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.372: write 7 regs 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.372: all registers written 165s (process:2163): libfprint-SSM-DEBUG: 16:48:02.372: [aes2501] CAPTURE_NUM_STATES entering state 5 165s (process:2163): libfprint-aes2501-DEBUG: 16:48:02.373: sum=393 165s (process:2163): libfprint-aes2501-DEBUG: 16:48:02.373: ADREFHI is 28 165s (process:2163): libfprint-SSM-DEBUG: 16:48:02.373: [aes2501] CAPTURE_NUM_STATES entering state 4 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.373: write 7 regs 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.373: all registers written 165s (process:2163): libfprint-SSM-DEBUG: 16:48:02.373: [aes2501] CAPTURE_NUM_STATES entering state 5 165s (process:2163): libfprint-aes2501-DEBUG: 16:48:02.374: sum=389 165s (process:2163): libfprint-aes2501-DEBUG: 16:48:02.374: ADREFHI is 28 165s (process:2163): libfprint-SSM-DEBUG: 16:48:02.374: [aes2501] CAPTURE_NUM_STATES entering state 4 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.374: write 7 regs 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.374: all registers written 165s (process:2163): libfprint-SSM-DEBUG: 16:48:02.374: [aes2501] CAPTURE_NUM_STATES entering state 5 165s (process:2163): libfprint-aes2501-DEBUG: 16:48:02.374: sum=379 165s (process:2163): libfprint-aes2501-DEBUG: 16:48:02.374: ADREFHI is 28 165s (process:2163): libfprint-SSM-DEBUG: 16:48:02.374: [aes2501] CAPTURE_NUM_STATES entering state 4 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.374: write 7 regs 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.375: all registers written 165s (process:2163): libfprint-SSM-DEBUG: 16:48:02.375: [aes2501] CAPTURE_NUM_STATES entering state 5 165s (process:2163): libfprint-aes2501-DEBUG: 16:48:02.375: sum=361 165s (process:2163): libfprint-aes2501-DEBUG: 16:48:02.375: ADREFHI is 28 165s (process:2163): libfprint-SSM-DEBUG: 16:48:02.376: [aes2501] CAPTURE_NUM_STATES entering state 4 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.376: write 7 regs 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.376: all registers written 165s (process:2163): libfprint-SSM-DEBUG: 16:48:02.376: [aes2501] CAPTURE_NUM_STATES entering state 5 165s (process:2163): libfprint-aes2501-DEBUG: 16:48:02.376: sum=356 165s (process:2163): libfprint-aes2501-DEBUG: 16:48:02.376: ADREFHI is 28 165s (process:2163): libfprint-SSM-DEBUG: 16:48:02.376: [aes2501] CAPTURE_NUM_STATES entering state 4 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.376: write 7 regs 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.377: all registers written 165s (process:2163): libfprint-SSM-DEBUG: 16:48:02.377: [aes2501] CAPTURE_NUM_STATES entering state 5 165s (process:2163): libfprint-aes2501-DEBUG: 16:48:02.377: sum=193 165s (process:2163): libfprint-aes2501-DEBUG: 16:48:02.377: ADREFHI is 28 165s (process:2163): libfprint-SSM-DEBUG: 16:48:02.377: [aes2501] CAPTURE_NUM_STATES entering state 4 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.377: write 7 regs 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.378: all registers written 165s (process:2163): libfprint-SSM-DEBUG: 16:48:02.378: [aes2501] CAPTURE_NUM_STATES entering state 5 165s (process:2163): libfprint-aes2501-DEBUG: 16:48:02.378: sum=178 165s (process:2163): libfprint-aes2501-DEBUG: 16:48:02.378: ADREFHI is 28 165s (process:2163): libfprint-SSM-DEBUG: 16:48:02.378: [aes2501] CAPTURE_NUM_STATES entering state 4 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.378: write 7 regs 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.379: all registers written 165s (process:2163): libfprint-SSM-DEBUG: 16:48:02.379: [aes2501] CAPTURE_NUM_STATES entering state 5 165s (process:2163): libfprint-aes2501-DEBUG: 16:48:02.379: sum=164 165s (process:2163): libfprint-aes2501-DEBUG: 16:48:02.379: ADREFHI is 28 165s (process:2163): libfprint-SSM-DEBUG: 16:48:02.379: [aes2501] CAPTURE_NUM_STATES entering state 4 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.379: write 7 regs 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.380: all registers written 165s (process:2163): libfprint-SSM-DEBUG: 16:48:02.380: [aes2501] CAPTURE_NUM_STATES entering state 5 165s (process:2163): libfprint-aes2501-DEBUG: 16:48:02.380: sum=157 165s (process:2163): libfprint-aes2501-DEBUG: 16:48:02.380: ADREFHI is 28 165s (process:2163): libfprint-SSM-DEBUG: 16:48:02.380: [aes2501] CAPTURE_NUM_STATES entering state 4 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.380: write 7 regs 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.381: all registers written 165s (process:2163): libfprint-SSM-DEBUG: 16:48:02.381: [aes2501] CAPTURE_NUM_STATES entering state 5 165s (process:2163): libfprint-aes2501-DEBUG: 16:48:02.381: sum=152 165s (process:2163): libfprint-aes2501-DEBUG: 16:48:02.381: ADREFHI is 28 165s (process:2163): libfprint-SSM-DEBUG: 16:48:02.381: [aes2501] CAPTURE_NUM_STATES entering state 4 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.381: write 7 regs 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.382: all registers written 165s (process:2163): libfprint-SSM-DEBUG: 16:48:02.382: [aes2501] CAPTURE_NUM_STATES entering state 5 165s (process:2163): libfprint-aes2501-DEBUG: 16:48:02.382: sum=154 165s (process:2163): libfprint-aes2501-DEBUG: 16:48:02.382: ADREFHI is 28 165s (process:2163): libfprint-SSM-DEBUG: 16:48:02.382: [aes2501] CAPTURE_NUM_STATES entering state 4 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.382: write 7 regs 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.382: all registers written 165s (process:2163): libfprint-SSM-DEBUG: 16:48:02.383: [aes2501] CAPTURE_NUM_STATES entering state 5 165s (process:2163): libfprint-aes2501-DEBUG: 16:48:02.383: sum=157 165s (process:2163): libfprint-aes2501-DEBUG: 16:48:02.383: ADREFHI is 28 165s (process:2163): libfprint-SSM-DEBUG: 16:48:02.383: [aes2501] CAPTURE_NUM_STATES entering state 4 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.383: write 7 regs 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.384: all registers written 165s (process:2163): libfprint-SSM-DEBUG: 16:48:02.384: [aes2501] CAPTURE_NUM_STATES entering state 5 165s (process:2163): libfprint-aes2501-DEBUG: 16:48:02.384: sum=161 165s (process:2163): libfprint-aes2501-DEBUG: 16:48:02.384: ADREFHI is 28 165s (process:2163): libfprint-SSM-DEBUG: 16:48:02.384: [aes2501] CAPTURE_NUM_STATES entering state 4 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.384: write 7 regs 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.385: all registers written 165s (process:2163): libfprint-SSM-DEBUG: 16:48:02.385: [aes2501] CAPTURE_NUM_STATES entering state 5 165s (process:2163): libfprint-aes2501-DEBUG: 16:48:02.385: sum=161 165s (process:2163): libfprint-aes2501-DEBUG: 16:48:02.385: ADREFHI is 28 165s (process:2163): libfprint-SSM-DEBUG: 16:48:02.385: [aes2501] CAPTURE_NUM_STATES entering state 4 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.385: write 7 regs 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.385: all registers written 165s (process:2163): libfprint-SSM-DEBUG: 16:48:02.385: [aes2501] CAPTURE_NUM_STATES entering state 5 165s (process:2163): libfprint-aes2501-DEBUG: 16:48:02.386: sum=161 165s (process:2163): libfprint-aes2501-DEBUG: 16:48:02.386: ADREFHI is 28 165s (process:2163): libfprint-SSM-DEBUG: 16:48:02.386: [aes2501] CAPTURE_NUM_STATES entering state 4 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.386: write 7 regs 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.386: all registers written 165s (process:2163): libfprint-SSM-DEBUG: 16:48:02.386: [aes2501] CAPTURE_NUM_STATES entering state 5 165s (process:2163): libfprint-aes2501-DEBUG: 16:48:02.387: sum=162 165s (process:2163): libfprint-aes2501-DEBUG: 16:48:02.387: ADREFHI is 28 165s (process:2163): libfprint-SSM-DEBUG: 16:48:02.387: [aes2501] CAPTURE_NUM_STATES entering state 4 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.387: write 7 regs 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.387: all registers written 165s (process:2163): libfprint-SSM-DEBUG: 16:48:02.387: [aes2501] CAPTURE_NUM_STATES entering state 5 165s (process:2163): libfprint-aes2501-DEBUG: 16:48:02.388: sum=166 165s (process:2163): libfprint-aes2501-DEBUG: 16:48:02.388: ADREFHI is 28 165s (process:2163): libfprint-SSM-DEBUG: 16:48:02.388: [aes2501] CAPTURE_NUM_STATES entering state 4 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.388: write 7 regs 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.388: all registers written 165s (process:2163): libfprint-SSM-DEBUG: 16:48:02.388: [aes2501] CAPTURE_NUM_STATES entering state 5 165s (process:2163): libfprint-aes2501-DEBUG: 16:48:02.389: sum=143 165s (process:2163): libfprint-aes2501-DEBUG: 16:48:02.389: ADREFHI is 28 165s (process:2163): libfprint-SSM-DEBUG: 16:48:02.389: [aes2501] CAPTURE_NUM_STATES entering state 4 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.389: write 7 regs 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.389: all registers written 165s (process:2163): libfprint-SSM-DEBUG: 16:48:02.389: [aes2501] CAPTURE_NUM_STATES entering state 5 165s (process:2163): libfprint-aes2501-DEBUG: 16:48:02.390: sum=106 165s (process:2163): libfprint-aes2501-DEBUG: 16:48:02.390: ADREFHI is 28 165s (process:2163): libfprint-SSM-DEBUG: 16:48:02.390: [aes2501] CAPTURE_NUM_STATES entering state 4 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.390: write 7 regs 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.390: all registers written 165s (process:2163): libfprint-SSM-DEBUG: 16:48:02.390: [aes2501] CAPTURE_NUM_STATES entering state 5 165s (process:2163): libfprint-aes2501-DEBUG: 16:48:02.391: sum=74 165s (process:2163): libfprint-aes2501-DEBUG: 16:48:02.391: ADREFHI is 28 165s (process:2163): libfprint-SSM-DEBUG: 16:48:02.391: [aes2501] CAPTURE_NUM_STATES entering state 4 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.391: write 7 regs 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.391: all registers written 165s (process:2163): libfprint-SSM-DEBUG: 16:48:02.391: [aes2501] CAPTURE_NUM_STATES entering state 5 165s (process:2163): libfprint-aes2501-DEBUG: 16:48:02.392: sum=51 165s (process:2163): libfprint-aes2501-DEBUG: 16:48:02.392: ADREFHI is 28 165s (process:2163): libfprint-SSM-DEBUG: 16:48:02.392: [aes2501] CAPTURE_NUM_STATES entering state 4 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.392: write 7 regs 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.392: all registers written 165s (process:2163): libfprint-SSM-DEBUG: 16:48:02.392: [aes2501] CAPTURE_NUM_STATES entering state 5 165s (process:2163): libfprint-aes2501-DEBUG: 16:48:02.393: sum=40 165s (process:2163): libfprint-aes2501-DEBUG: 16:48:02.393: ADREFHI is 28 165s (process:2163): libfprint-SSM-DEBUG: 16:48:02.393: [aes2501] CAPTURE_NUM_STATES entering state 4 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.393: write 7 regs 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.393: all registers written 165s (process:2163): libfprint-SSM-DEBUG: 16:48:02.393: [aes2501] CAPTURE_NUM_STATES entering state 5 165s (process:2163): libfprint-aes2501-DEBUG: 16:48:02.394: sum=39 165s (process:2163): libfprint-aes2501-DEBUG: 16:48:02.394: ADREFHI is 28 165s (process:2163): libfprint-SSM-DEBUG: 16:48:02.394: [aes2501] CAPTURE_NUM_STATES entering state 4 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.394: write 7 regs 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.394: all registers written 165s (process:2163): libfprint-SSM-DEBUG: 16:48:02.394: [aes2501] CAPTURE_NUM_STATES entering state 5 165s (process:2163): libfprint-aes2501-DEBUG: 16:48:02.395: sum=19 165s (process:2163): libfprint-aes2501-DEBUG: 16:48:02.395: ADREFHI is 28 165s (process:2163): libfprint-SSM-DEBUG: 16:48:02.395: [aes2501] CAPTURE_NUM_STATES entering state 4 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.395: write 7 regs 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.395: all registers written 165s (process:2163): libfprint-SSM-DEBUG: 16:48:02.395: [aes2501] CAPTURE_NUM_STATES entering state 5 165s (process:2163): libfprint-aes2501-DEBUG: 16:48:02.396: sum=13 165s (process:2163): libfprint-aes2501-DEBUG: 16:48:02.396: ADREFHI is 28 165s (process:2163): libfprint-SSM-DEBUG: 16:48:02.396: [aes2501] CAPTURE_NUM_STATES entering state 4 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.396: write 7 regs 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.396: all registers written 165s (process:2163): libfprint-SSM-DEBUG: 16:48:02.396: [aes2501] CAPTURE_NUM_STATES entering state 5 165s (process:2163): libfprint-aes2501-DEBUG: 16:48:02.397: sum=5 165s (process:2163): libfprint-aes2501-DEBUG: 16:48:02.397: ADREFHI is 28 165s (process:2163): libfprint-SSM-DEBUG: 16:48:02.397: [aes2501] CAPTURE_NUM_STATES entering state 4 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.397: write 7 regs 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.397: all registers written 165s (process:2163): libfprint-SSM-DEBUG: 16:48:02.397: [aes2501] CAPTURE_NUM_STATES entering state 5 165s (process:2163): libfprint-aes2501-DEBUG: 16:48:02.397: sum=2 165s (process:2163): libfprint-aes2501-DEBUG: 16:48:02.398: ADREFHI is 28 165s (process:2163): libfprint-SSM-DEBUG: 16:48:02.398: [aes2501] CAPTURE_NUM_STATES entering state 4 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.398: write 7 regs 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.398: all registers written 165s (process:2163): libfprint-SSM-DEBUG: 16:48:02.398: [aes2501] CAPTURE_NUM_STATES entering state 5 165s (process:2163): libfprint-aes2501-DEBUG: 16:48:02.398: sum=0 165s (process:2163): libfprint-aes2501-DEBUG: 16:48:02.399: ADREFHI is 28 165s (process:2163): libfprint-SSM-DEBUG: 16:48:02.399: [aes2501] CAPTURE_NUM_STATES entering state 4 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.399: write 7 regs 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.399: all registers written 165s (process:2163): libfprint-SSM-DEBUG: 16:48:02.399: [aes2501] CAPTURE_NUM_STATES entering state 5 165s (process:2163): libfprint-aes2501-DEBUG: 16:48:02.400: sum=0 165s (process:2163): libfprint-aes2501-DEBUG: 16:48:02.400: ADREFHI is 28 165s (process:2163): libfprint-SSM-DEBUG: 16:48:02.400: [aes2501] CAPTURE_NUM_STATES entering state 4 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.400: write 7 regs 165s (process:2163): libfprint-aeslib-DEBUG: 16:48:02.400: all registers written 165s (process:2163): libfprint-SSM-DEBUG: 16:48:02.400: [aes2501] CAPTURE_NUM_STATES entering state 5 165s (process:2163): libfprint-aes2501-DEBUG: 16:48:02.401: sum=0 165s (process:2163): libfprint-aes2501-DEBUG: 16:48:02.401: ADREFHI is 28 165s (process:2163): libfprint-assembling-DEBUG: 16:48:02.550: calc delta completed in 0.149215 secs 165s (process:2163): libfprint-assembling-DEBUG: 16:48:02.701: calc delta completed in 0.151040 secs 165s (process:2163): libfprint-assembling-DEBUG: 16:48:02.701: errors: 53228 rev: 72653 165s (process:2163): libfprint-assembling-DEBUG: 16:48:02.851: calc delta completed in 0.149749 secs 165s (process:2163): libfprint-assembling-DEBUG: 16:48:02.851: height is 102 165s (process:2163): libfprint-image_device-DEBUG: 16:48:02.852: Image device captured an image 165s (process:2163): libfprint-image_device-DEBUG: 16:48:02.853: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 165s (process:2163): libfprint-device-DEBUG: 16:48:02.853: Device reported finger status change: FP_FINGER_STATUS_PRESENT 165s (process:2163): libfprint-device-DEBUG: 16:48:02.853: Device reported finger status change: FP_FINGER_STATUS_NONE 165s (process:2163): libfprint-image_device-DEBUG: 16:48:02.853: Image device reported finger status: off 165s (process:2163): libfprint-image_device-DEBUG: 16:48:02.853: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 165s (process:2163): libfprint-image_device-DEBUG: 16:48:02.853: Deactivating image device 165s (process:2163): libfprint-image_device-DEBUG: 16:48:02.853: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_DEACTIVATING 165s (process:2163): libfprint-SSM-DEBUG: 16:48:02.853: [aes2501] CAPTURE_NUM_STATES completed successfully 165s (process:2163): libfprint-aes2501-DEBUG: 16:48:02.853: 53854520: ../libfprint/drivers/aes2501.c:547 165s (process:2163): libfprint-aes2501-DEBUG: 16:48:02.853: 53854523: ../libfprint/drivers/aes2501.c:820 165s (process:2163): libfprint-image_device-DEBUG: 16:48:02.853: Image device deactivation completed 165s (process:2163): libfprint-image_device-DEBUG: 16:48:02.853: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE 165s (process:2163): libfprint-image-DEBUG: 16:48:02.859: Minutiae scan completed in 0.005656 secs 165s (process:2163): libfprint-device-DEBUG: 16:48:02.859: Device reported capture completion 165s (process:2163): libfprint-device-DEBUG: 16:48:02.860: Completing action FPI_DEVICE_ACTION_CAPTURE in idle! 165s (process:2163): libfprint-device-DEBUG: 16:48:02.860: Updated temperature model after 1.68 seconds, ratio 0.27 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 165s (process:2163): libfprint-image_device-DEBUG: 16:48:02.860: Image device close completed 165s (process:2163): libfprint-device-DEBUG: 16:48:02.860: Device reported close completion 165s (process:2163): libfprint-device-DEBUG: 16:48:02.860: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 165s (process:2163): libfprint-device-DEBUG: 16:48:02.860: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 165s ** (umockdev-run:2159): DEBUG: 16:48:02.905: umockdev.vala:150: Removing test bed /tmp/umockdev.XGHDK2 165s (umockdev-run:2159): GLib-DEBUG: 16:48:02.909: unsetenv() is not thread-safe and should not be used after threads are created 165s Comparing PNGs /tmp/libfprint-umockdev-test-n126vedd/capture.png and /usr/share/installed-tests/libfprint-2/aes2501/capture.png 165s PASS: libfprint-2/driver-aes2501.test 165s Running test: libfprint-2/driver-vfs0050.test 165s ** (umockdev-run:2172): DEBUG: 16:48:02.972: umockdev.vala:123: Created udev test bed /tmp/umockdev.273YJ2 165s ** (umockdev-run:2172): DEBUG: 16:48:02.972: umockdev.vala:1297: parsing device description for /devices/pci0000:00/0000:00:14.0/usb1/1-9 165s ** (umockdev-run:2172): DEBUG: 16:48:02.973: umockdev.vala:1366: creating device /devices/pci0000:00/0000:00:14.0/usb1/1-9 (subsystem usb) 165s ** (umockdev-run:2172): DEBUG: 16:48:02.975: umockdev.vala:1411: create_node_for_device: creating file device /tmp/umockdev.273YJ2/dev/bus/usb/001/004 165s ** (umockdev-run:2172): DEBUG: 16:48:02.975: umockdev.vala:1297: parsing device description for /devices/pci0000:00/0000:00:14.0/usb1 165s ** (umockdev-run:2172): DEBUG: 16:48:02.976: umockdev.vala:1366: creating device /devices/pci0000:00/0000:00:14.0/usb1 (subsystem usb) 165s ** (umockdev-run:2172): DEBUG: 16:48:02.978: umockdev.vala:1411: create_node_for_device: creating file device /tmp/umockdev.273YJ2/dev/bus/usb/001/001 165s ** (umockdev-run:2172): DEBUG: 16:48:02.978: umockdev.vala:1297: parsing device description for /devices/pci0000:00/0000:00:14.0 165s ** (umockdev-run:2172): DEBUG: 16:48:02.978: umockdev.vala:1366: creating device /devices/pci0000:00/0000:00:14.0 (subsystem pci) 165s (umockdev-run:2172): GLib-GIO-DEBUG: 16:48:02.980: _g_io_module_get_default: Found default implementation local (GLocalVfs) for ?gio-vfs? 166s (process:2176): libfprint-context-DEBUG: 16:48:03.056: Initializing FpContext (libfprint version 1.94.7+tod1) 166s (process:2176): libfprint-tod-DEBUG: 16:48:03.056: Impossible to load the shared drivers dir Error opening directory “/usr/lib/aarch64-linux-gnu/libfprint-2/tod-1”: No such file or directory 166s (process:2176): libfprint-context-DEBUG: 16:48:03.058: No driver found for USB device 1D6B:0002 166s (process:2176): libfprint-device-DEBUG: 16:48:03.058: Device reported probe completion 166s (process:2176): libfprint-device-DEBUG: 16:48:03.058: Completing action FPI_DEVICE_ACTION_PROBE in idle! 166s (process:2176): libfprint-device-DEBUG: 16:48:03.059: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 166s (process:2176): libfprint-SSM-DEBUG: 16:48:03.060: [vfs0050] SSM_STATES entering state 0 166s (process:2176): libfprint-SSM-DEBUG: 16:48:03.061: [vfs0050] SSM_STATES entering state 1 166s (process:2176): libfprint-SSM-DEBUG: 16:48:03.062: [vfs0050] SSM_STATES entering state 2 166s (process:2176): libfprint-SSM-DEBUG: 16:48:03.062: [vfs0050] SSM_STATES entering state 3 166s (process:2176): libfprint-SSM-DEBUG: 16:48:03.062: [vfs0050] SUBSM1_STATES entering state 0 166s (process:2176): libfprint-SSM-DEBUG: 16:48:03.063: [vfs0050] SUBSM1_STATES entering state 1 166s (process:2176): libfprint-SSM-DEBUG: 16:48:03.063: [vfs0050] SUBSM1_STATES entering state 2 166s (process:2176): libfprint-SSM-DEBUG: 16:48:03.064: [vfs0050] SUBSM1_STATES completed successfully 166s (process:2176): libfprint-SSM-DEBUG: 16:48:03.064: [vfs0050] SSM_STATES entering state 4 166s (process:2176): libfprint-SSM-DEBUG: 16:48:03.064: [vfs0050] SUBSM2_STATES entering state 0 166s (process:2176): libfprint-SSM-DEBUG: 16:48:03.065: [vfs0050] SUBSM2_STATES entering state 1 166s (process:2176): libfprint-SSM-DEBUG: 16:48:03.065: [vfs0050] SUBSM2_STATES entering state 2 166s (process:2176): libfprint-SSM-DEBUG: 16:48:03.066: [vfs0050] SUBSM2_STATES entering state 3 166s (process:2176): libfprint-SSM-DEBUG: 16:48:03.066: [vfs0050] SUBSM2_STATES entering state 4 166s (process:2176): libfprint-SSM-DEBUG: 16:48:03.067: [vfs0050] SUBSM2_STATES entering state 5 166s (process:2176): libfprint-SSM-DEBUG: 16:48:03.067: [vfs0050] SUBSM2_STATES entering state 6 166s (process:2176): libfprint-SSM-DEBUG: 16:48:03.067: [vfs0050] SUBSM1_STATES entering state 0 166s (process:2176): libfprint-SSM-DEBUG: 16:48:03.068: [vfs0050] SUBSM1_STATES entering state 1 166s (process:2176): libfprint-SSM-DEBUG: 16:48:03.068: [vfs0050] SUBSM1_STATES entering state 2 166s (process:2176): libfprint-SSM-DEBUG: 16:48:03.069: [vfs0050] SUBSM1_STATES completed successfully 166s (process:2176): libfprint-SSM-DEBUG: 16:48:03.069: [vfs0050] SUBSM2_STATES completed successfully 166s (process:2176): libfprint-SSM-DEBUG: 16:48:03.069: [vfs0050] SSM_STATES entering state 5 166s (process:2176): libfprint-SSM-DEBUG: 16:48:03.069: [vfs0050] SSM_STATES completed successfully 166s (process:2176): libfprint-image_device-DEBUG: 16:48:03.069: Image device open completed 166s (process:2176): libfprint-device-DEBUG: 16:48:03.069: Device reported open completion 166s (process:2176): libfprint-device-DEBUG: 16:48:03.069: Completing action FPI_DEVICE_ACTION_OPEN in idle! 166s (process:2176): libfprint-device-DEBUG: 16:48:03.069: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 166s (process:2176): libfprint-device-DEBUG: 16:48:03.069: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 166s (process:2176): libfprint-image_device-DEBUG: 16:48:03.069: Activating image device 166s (process:2176): libfprint-image_device-DEBUG: 16:48:03.069: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING 166s (process:2176): libfprint-SSM-DEBUG: 16:48:03.069: [vfs0050] SSM_STATES entering state 0 166s (process:2176): libfprint-SSM-DEBUG: 16:48:03.070: [vfs0050] SSM_STATES entering state 1 166s (process:2176): libfprint-SSM-DEBUG: 16:48:03.070: [vfs0050] SSM_STATES entering state 2 166s (process:2176): libfprint-SSM-DEBUG: 16:48:03.071: [vfs0050] SSM_STATES entering state 3 166s (process:2176): libfprint-SSM-DEBUG: 16:48:03.071: [vfs0050] SUBSM1_STATES entering state 0 166s (process:2176): libfprint-SSM-DEBUG: 16:48:03.071: [vfs0050] SUBSM1_STATES entering state 1 166s (process:2176): libfprint-SSM-DEBUG: 16:48:03.072: [vfs0050] SUBSM1_STATES entering state 2 166s (process:2176): libfprint-SSM-DEBUG: 16:48:03.072: [vfs0050] SUBSM1_STATES completed successfully 166s (process:2176): libfprint-SSM-DEBUG: 16:48:03.072: [vfs0050] SSM_STATES entering state 4 166s (process:2176): libfprint-SSM-DEBUG: 16:48:03.072: [vfs0050] SUBSM2_STATES entering state 0 166s (process:2176): libfprint-SSM-DEBUG: 16:48:03.073: [vfs0050] SUBSM2_STATES entering state 1 166s (process:2176): libfprint-SSM-DEBUG: 16:48:03.073: [vfs0050] SUBSM2_STATES entering state 2 166s (process:2176): libfprint-SSM-DEBUG: 16:48:03.074: [vfs0050] SUBSM2_STATES entering state 3 166s (process:2176): libfprint-SSM-DEBUG: 16:48:03.074: [vfs0050] SUBSM2_STATES entering state 4 166s (process:2176): libfprint-SSM-DEBUG: 16:48:03.075: [vfs0050] SUBSM2_STATES entering state 5 166s (process:2176): libfprint-SSM-DEBUG: 16:48:03.075: [vfs0050] SUBSM2_STATES entering state 6 166s (process:2176): libfprint-SSM-DEBUG: 16:48:03.076: [vfs0050] SUBSM1_STATES entering state 0 166s (process:2176): libfprint-SSM-DEBUG: 16:48:03.076: [vfs0050] SUBSM1_STATES entering state 1 166s (process:2176): libfprint-SSM-DEBUG: 16:48:03.076: [vfs0050] SUBSM1_STATES entering state 2 166s (process:2176): libfprint-SSM-DEBUG: 16:48:03.077: [vfs0050] SUBSM1_STATES completed successfully 166s (process:2176): libfprint-SSM-DEBUG: 16:48:03.077: [vfs0050] SUBSM2_STATES completed successfully 166s (process:2176): libfprint-SSM-DEBUG: 16:48:03.077: [vfs0050] SSM_STATES entering state 5 166s (process:2176): libfprint-SSM-DEBUG: 16:48:03.077: [vfs0050] SUBSM2_STATES entering state 0 166s (process:2176): libfprint-SSM-DEBUG: 16:48:03.078: [vfs0050] SUBSM2_STATES entering state 1 166s (process:2176): libfprint-SSM-DEBUG: 16:48:03.078: [vfs0050] SUBSM2_STATES entering state 2 166s (process:2176): libfprint-SSM-DEBUG: 16:48:03.079: [vfs0050] SUBSM2_STATES entering state 3 166s (process:2176): libfprint-SSM-DEBUG: 16:48:03.079: [vfs0050] SUBSM2_STATES entering state 4 166s (process:2176): libfprint-SSM-DEBUG: 16:48:03.080: [vfs0050] SUBSM2_STATES entering state 5 166s (process:2176): libfprint-SSM-DEBUG: 16:48:03.080: [vfs0050] SUBSM2_STATES entering state 6 166s (process:2176): libfprint-SSM-DEBUG: 16:48:03.080: [vfs0050] SUBSM2_STATES completed successfully 166s (process:2176): libfprint-SSM-DEBUG: 16:48:03.080: [vfs0050] SSM_STATES entering state 6 166s (process:2176): libfprint-image_device-DEBUG: 16:48:03.080: Image device activation completed 166s (process:2176): libfprint-image_device-DEBUG: 16:48:03.080: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE 166s (process:2176): libfprint-image_device-DEBUG: 16:48:03.080: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 166s (process:2176): libfprint-device-DEBUG: 16:48:03.080: Device reported finger status change: FP_FINGER_STATUS_NEEDED 166s (process:2176): libfprint-SSM-DEBUG: 16:48:03.081: [vfs0050] SSM_STATES entering state 7 166s (process:2176): libfprint-SSM-DEBUG: 16:48:03.081: [vfs0050] SSM_STATES entering state 8 166s (process:2176): libfprint-device-DEBUG: 16:48:03.081: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 166s (process:2176): libfprint-image_device-DEBUG: 16:48:03.081: Image device reported finger status: on 166s (process:2176): libfprint-image_device-DEBUG: 16:48:03.081: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 166s (process:2176): libfprint-SSM-DEBUG: 16:48:03.082: [vfs0050] SSM_STATES entering state 8 166s (process:2176): libfprint-SSM-DEBUG: 16:48:03.082: [vfs0050] SSM_STATES entering state 8 166s (process:2176): libfprint-SSM-DEBUG: 16:48:03.083: [vfs0050] SSM_STATES entering state 8 166s (process:2176): libfprint-SSM-DEBUG: 16:48:03.084: [vfs0050] SSM_STATES entering state 8 166s (process:2176): libfprint-SSM-DEBUG: 16:48:03.085: [vfs0050] SSM_STATES entering state 8 166s (process:2176): libfprint-SSM-DEBUG: 16:48:03.085: [vfs0050] SSM_STATES entering state 8 166s (process:2176): libfprint-SSM-DEBUG: 16:48:03.086: [vfs0050] SSM_STATES entering state 8 166s (process:2176): libfprint-SSM-DEBUG: 16:48:03.086: [vfs0050] SSM_STATES entering state 8 166s (process:2176): libfprint-SSM-DEBUG: 16:48:03.087: [vfs0050] SSM_STATES entering state 8 166s (process:2176): libfprint-SSM-DEBUG: 16:48:03.088: [vfs0050] SSM_STATES entering state 8 166s (process:2176): libfprint-SSM-DEBUG: 16:48:03.089: [vfs0050] SSM_STATES entering state 8 166s (process:2176): libfprint-SSM-DEBUG: 16:48:03.089: [vfs0050] SSM_STATES entering state 8 166s (process:2176): libfprint-SSM-DEBUG: 16:48:03.090: [vfs0050] SSM_STATES entering state 8 166s (process:2176): libfprint-SSM-DEBUG: 16:48:03.090: [vfs0050] SSM_STATES entering state 8 166s (process:2176): libfprint-SSM-DEBUG: 16:48:03.091: [vfs0050] SSM_STATES entering state 8 166s (process:2176): libfprint-SSM-DEBUG: 16:48:03.092: [vfs0050] SSM_STATES entering state 8 166s (process:2176): libfprint-SSM-DEBUG: 16:48:03.092: [vfs0050] SSM_STATES entering state 8 166s (process:2176): libfprint-SSM-DEBUG: 16:48:03.093: [vfs0050] SSM_STATES entering state 8 166s (process:2176): libfprint-SSM-DEBUG: 16:48:03.094: [vfs0050] SSM_STATES entering state 8 166s (process:2176): libfprint-SSM-DEBUG: 16:48:03.095: [vfs0050] SSM_STATES entering state 8 166s (process:2176): libfprint-SSM-DEBUG: 16:48:03.095: [vfs0050] SSM_STATES entering state 8 166s (process:2176): libfprint-SSM-DEBUG: 16:48:03.096: [vfs0050] SSM_STATES entering state 8 166s (process:2176): libfprint-SSM-DEBUG: 16:48:03.097: [vfs0050] SSM_STATES entering state 8 166s (process:2176): libfprint-SSM-DEBUG: 16:48:03.098: [vfs0050] SSM_STATES entering state 8 166s (process:2176): libfprint-SSM-DEBUG: 16:48:03.098: [vfs0050] SSM_STATES entering state 9 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.099: 1710002883099024 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.099: 1 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.099: 1 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.099: 2 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.099: 1 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.099: 13 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.099: 51 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.099: 9 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.099: 7 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.099: 5 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.099: 3 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.099: 1 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.099: 8 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.099: 6 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.099: 35 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.099: 2 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.099: 31 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.099: 29 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.099: 27 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.099: 25 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.099: 23 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.099: 21 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.099: 19 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.099: 17 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.099: 15 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.099: 13 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.099: 11 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.099: 9 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.099: 7 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.099: 5 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.099: 3 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.099: 1 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.099: 26 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.099: 24 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.099: 22 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.099: 20 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.099: 18 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.099: 16 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.099: 14 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.099: 12 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.099: 10 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.099: 8 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.099: 6 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.099: 4 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.099: 2 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.099: 38 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.099: 36 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.099: 34 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.099: 32 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.099: 30 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.099: 28 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.099: 26 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.099: 24 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.099: 22 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.099: 20 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.099: 18 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.099: 16 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.099: 14 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.099: 12 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.099: 10 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.099: 8 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.099: 6 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.099: 4 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.099: 100 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.099: 98 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.099: 96 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.099: 94 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.099: 92 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.099: 90 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.099: 100 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.099: 98 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.099: 96 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.099: 100 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.099: 99 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.099: 100 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.099: 98 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.099: 96 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.099: 99 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.099: 97 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.099: 95 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.099: 93 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.099: 100 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.099: 98 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.099: 96 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.099: 94 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.099: 92 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.099: 90 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.099: 88 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.099: 86 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.099: 84 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.099: 100 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.099: 98 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.099: 96 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.099: 100 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.099: 99 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.099: 97 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.099: 70 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.099: 68 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.099: 66 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.099: 64 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.099: 97 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.099: 8 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.099: 6 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.099: 4 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.099: 2 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.099: 10 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.099: 8 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.099: 6 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.099: 4 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.099: 2 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.099: 3 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.099: 100 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.099: 99 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.099: 100 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.099: 100 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.099: 99 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.099: 99 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.099: 99 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.099: 99 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.099: 99 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.099: 99 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.099: 100 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.099: 100 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.099: 100 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.099: 99 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.099: 100 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.099: 99 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.099: 99 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.099: 100 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.099: 100 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.099: 100 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.099: 98 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.099: 100 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.099: 100 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.099: 98 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.099: 96 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.099: 94 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.099: 100 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.099: 98 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.099: 96 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.099: 94 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.099: 92 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.099: 90 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.099: 88 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.099: 86 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.099: 84 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.099: 97 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.099: 95 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.099: 93 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.099: 97 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.099: 95 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.099: 93 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.099: 91 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.099: 89 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.099: 87 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.099: 85 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.099: 83 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.099: 87 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.099: 85 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.099: 83 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.099: 81 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.099: 79 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.099: 81 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.099: 79 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.099: 77 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.099: 79 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.099: 77 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.099: 75 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.099: 79 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.099: 75 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.099: 79 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.099: 77 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.099: 75 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.099: 73 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.099: 71 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.099: 71 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.099: 69 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.099: 70 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.099: 68 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.099: 66 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.099: 64 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.099: 66 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.099: 64 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.099: 62 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.099: 60 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.099: 58 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.099: 59 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.099: 60 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.099: 59 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.099: 62 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.099: 61 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.099: 59 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.099: 57 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.099: 58 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.099: 56 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.099: 54 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.099: 52 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.099: 50 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.099: 57 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.099: 54 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.099: 55 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.099: 57 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.099: 54 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.099: 55 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.099: 54 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.099: 56 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.099: 58 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.099: 56 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.099: 54 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.099: 55 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.099: 54 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.099: 52 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.099: 53 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.099: 52 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.099: 50 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.099: 48 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.099: 54 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.099: 54 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.099: 53 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.099: 54 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.099: 53 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.099: 52 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.099: 52 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.099: 50 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.099: 50 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.099: 50 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.099: 49 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 49 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 48 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 49 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 47 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 46 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 45 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 44 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 44 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 44 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 44 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 44 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 44 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 46 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 47 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 47 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 46 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 46 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 44 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 44 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 42 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 43 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 41 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 42 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 40 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 42 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 43 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 43 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 41 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 42 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 40 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 42 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 43 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 42 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 43 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 41 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 42 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 42 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 40 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 42 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 40 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 42 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 43 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 41 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 41 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 40 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 42 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 40 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 42 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 42 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 41 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 41 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 43 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 41 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 41 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 41 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 41 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 41 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 40 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 39 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 38 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 39 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 38 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 38 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 38 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 36 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 34 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 36 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 37 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 38 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 36 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 36 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 35 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 35 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 35 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 36 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 35 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 35 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 33 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 33 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 32 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 32 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 34 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 35 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 35 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 34 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 35 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 33 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 32 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 33 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 34 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 33 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 33 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 33 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 33 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 33 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 34 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 35 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 35 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 34 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 34 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 33 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 33 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 33 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 32 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 32 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 32 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 32 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 31 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 33 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 34 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 32 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 33 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 33 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 32 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 30 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 31 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 31 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 34 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 32 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 33 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 33 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 33 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 31 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 31 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 31 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 29 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 28 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 33 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 32 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 31 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 31 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 29 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 31 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 32 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 31 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 32 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 30 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 33 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 31 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 29 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 29 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 29 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 29 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 30 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 30 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 29 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 29 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 27 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 26 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 24 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 27 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 25 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 27 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 28 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 28 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 61 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 30 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 29 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 29 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 27 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 27 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 26 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 25 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 28 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 27 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 27 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 27 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 27 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 28 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 27 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 27 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 27 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 28 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 28 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 27 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 28 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 26 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 25 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 23 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 24 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 27 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 27 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 28 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 28 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 26 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 27 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 28 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 28 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 28 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 29 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 28 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 28 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 29 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 28 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 27 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 26 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 28 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 28 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 28 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 28 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 28 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 27 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 27 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 28 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 28 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 27 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 26 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 27 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 27 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 26 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 26 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 28 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 27 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 28 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 29 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 29 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 29 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 29 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 28 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 28 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 28 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 27 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 27 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 27 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 28 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 28 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 27 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 27 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 28 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 28 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 28 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 28 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 28 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 28 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 28 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 29 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 28 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 29 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 29 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 27 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 28 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 29 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 29 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 29 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 31 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 29 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 29 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 29 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 29 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 28 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 29 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 28 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 29 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 28 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 28 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 28 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 28 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 29 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 29 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 30 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 30 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 30 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 30 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 29 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 29 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 29 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 29 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 29 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 29 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 31 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 30 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 30 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 30 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 31 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 31 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 30 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 30 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 30 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 29 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 29 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 30 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 30 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 30 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 29 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 30 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 31 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 31 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 31 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 30 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 30 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 31 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 31 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 31 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 30 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 1 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 29 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 30 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 30 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 30 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 29 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 31 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 31 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 31 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 31 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 31 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 32 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 91 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 89 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 86 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 30 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 30 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 30 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 30 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 31 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 30 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 60 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 60 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 31 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 30 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 31 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 30 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 30 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 29 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 28 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 30 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 30 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 30 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 30 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 30 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 62 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 61 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 59 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 57 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 30 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 29 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 29 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 57 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 56 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 53 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 51 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 46 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 31 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 31 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 32 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 32 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 31 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.100: 30 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 30 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 30 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 30 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 30 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 30 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 30 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 30 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 30 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 29 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 30 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 31 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 30 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 29 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 29 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 31 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 31 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 32 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 31 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 31 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 31 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 30 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 30 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 29 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 29 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 29 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 29 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 28 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 27 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 31 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 31 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 30 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 31 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 31 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 31 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 31 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 30 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 29 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 30 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 30 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 29 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 29 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 28 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 27 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 29 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 29 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 30 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 30 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 30 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 30 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 30 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 30 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 31 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 30 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 30 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 30 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 30 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 31 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 30 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 30 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 29 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 29 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 31 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 29 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 30 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 30 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 29 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 29 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 30 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 30 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 30 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 29 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 29 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 29 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 30 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 29 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 29 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 28 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 28 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 28 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 28 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 29 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 28 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 29 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 29 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 29 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 29 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 28 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 28 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 27 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 27 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 27 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 29 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 30 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 29 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 29 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 29 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 29 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 30 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 29 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 30 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 29 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 31 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 30 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 29 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 29 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 29 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 29 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 27 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 28 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 29 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 29 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 28 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 27 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 27 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 29 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 29 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 29 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 28 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 28 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 28 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 28 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 28 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 27 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 28 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 26 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 26 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 26 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 25 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 26 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 26 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 27 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 27 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 28 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 53 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 27 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 28 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 28 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 26 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 25 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 24 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 25 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 24 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 25 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 26 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 26 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 25 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 26 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 27 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 27 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 26 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 25 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 25 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 24 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 24 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 24 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 24 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 25 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 25 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 24 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 26 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 25 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 25 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 25 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 25 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 24 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 24 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 24 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 24 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 24 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 23 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 23 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 26 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 25 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 25 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 24 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 26 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 25 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 24 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 24 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 24 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 23 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 23 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 22 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 22 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 24 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 23 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 24 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 23 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 22 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 22 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 24 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 23 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 22 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 22 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 22 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 23 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 23 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 24 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 23 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 23 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 24 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 23 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 22 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 24 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 22 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 93 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 24 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 22 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 22 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 22 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 22 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 22 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 21 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 21 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 23 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 21 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 22 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 22 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 22 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 21 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 22 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 21 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 24 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 23 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 23 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 22 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 22 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 22 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 22 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 22 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 22 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 21 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 22 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 22 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 21 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 21 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 22 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 21 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 21 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 21 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 21 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 20 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 20 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 20 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 21 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 21 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 20 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 21 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 20 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 21 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 21 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 21 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 92 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 20 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 22 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 22 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 21 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 22 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 21 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 21 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 20 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 21 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 20 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 20 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 20 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 20 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 20 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 19 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 20 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 20 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 20 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 19 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 20 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 19 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 19 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 19 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 19 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 19 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 19 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 19 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 19 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 19 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 18 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 18 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 19 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 18 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 17 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 19 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 18 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 19 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 18 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 18 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 18 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 18 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 18 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 18 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 18 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 19 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 19 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 19 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 18 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 17 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 18 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 92 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 18 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 18 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 19 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 18 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 18 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 18 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 18 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 59 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 75 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 74 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 18 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 18 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 17 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 17 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 17 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 18 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 17 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 17 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.101: 37 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.102: 36 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.102: 54 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.102: 17 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.102: 17 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.102: 16 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.102: 17 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.102: 17 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.102: 73 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.102: 71 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.102: 17 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.102: 16 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.102: 16 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.102: 15 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.102: 16 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.102: 17 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.102: 16 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.102: 17 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.102: 17 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.102: 16 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.102: 16 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.102: 16 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.102: 15 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.102: 16 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.102: 16 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.102: 16 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.102: 15 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.102: 15 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.102: 15 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.102: 15 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.102: 16 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.102: 16 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.102: 15 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.102: 15 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.102: 15 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.102: 14 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.102: 16 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.102: 16 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.102: 15 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.102: 14 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.102: 14 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.102: 14 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.102: 15 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.102: 14 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.102: 15 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.102: 15 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.102: 15 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.102: 15 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.102: 15 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.102: 15 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.102: 14 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.102: 14 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.102: 13 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.102: 13 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.102: 14 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.102: 15 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.102: 14 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.102: 14 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.102: 14 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.102: 14 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.102: 13 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.102: 14 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.102: 13 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.102: 52 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.102: 51 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.102: 15 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.102: 34 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.102: 32 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.102: 13 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.102: 13 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.102: 13 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.102: 13 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.102: 13 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.102: 13 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.102: 12 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.102: 13 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.102: 13 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.102: 12 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.102: 12 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.102: 12 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.102: 12 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.102: 13 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.102: 13 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.102: 12 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.102: 27 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.102: 13 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.102: 14 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.102: 12 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.102: 12 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.102: 13 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.102: 12 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.102: 12 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.102: 12 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.102: 11 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.102: 84 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.102: 45 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.102: 14 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.102: 13 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.102: 12 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.102: 11 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.102: 11 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.102: 11 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.102: 68 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.102: 100 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.102: 12 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.102: 13 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.102: 13 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.102: 14 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.102: 12 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.102: 11 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.102: 12 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.102: 12 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.102: 12 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.102: 12 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.102: 12 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.102: 11 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.102: 10 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.102: 38 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.102: 12 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.102: 79 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.102: 12 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.102: 11 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.102: 10 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.102: 9 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.102: 68 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.102: 67 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.102: 66 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.102: 66 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.102: 11 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.102: 10 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.102: 11 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.102: 27 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.102: 11 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.102: 23 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.102: 21 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.102: 11 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.102: 36 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.102: 23 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.102: 98 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.102: 11 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.102: 25 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.102: 23 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.102: 34 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.102: 33 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.102: 29 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.102: 9 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.102: 11 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.102: 11 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.102: 10 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.102: 10 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.102: 9 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.102: 9 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.102: 12 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.102: 10 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.102: 10 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.102: 10 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.102: 9 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.102: 7 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.102: 12 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.102: 10 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.102: 9 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.102: 9 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.102: 50 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.102: 61 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.102: 83 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.102: 26 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.102: 24 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.102: 38 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.102: 9 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.102: 92 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.102: 69 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.102: 67 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.102: 66 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.102: 92 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.102: 90 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.102: 79 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.102: 73 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.102: 71 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.102: 70 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.102: 68 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.102: 67 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.102: 89 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.102: 87 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.102: 90 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.102: 88 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.102: 86 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.102: 37 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.102: 53 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.102: 75 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.102: 73 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.102: 76 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.102: 74 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.102: 42 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.103: 41 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.103: 39 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.103: 48 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.103: 64 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.103: 62 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.103: 83 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.103: 29 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.103: 27 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.103: 86 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.103: 52 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.103: 50 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.103: 71 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.103: 20 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.103: 76 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.103: 42 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.103: 40 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.103: 70 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.103: 7 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.103: 34 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.103: 32 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.104: 30 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.104: 7 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.104: 8 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.104: 6 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.104: 4 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.104: 51 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.104: 41 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.104: 11 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.104: 9 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.104: 7 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.104: 100 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.104: 100 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.104: 100 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.104: 98 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.104: 100 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.104: 92 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.104: 90 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.104: 95 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.104: 94 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.104: 92 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.104: 83 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.104: 81 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.104: 97 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.104: 100 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.104: 98 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.104: 96 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.104: 89 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.104: 87 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.104: 70 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.104: 97 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.104: 81 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.104: 98 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.104: 77 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.104: 55 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.104: 53 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.104: 51 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.104: 49 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.104: 47 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.104: 45 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.104: 43 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.104: 41 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.104: 38 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.104: 37 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.105: 35 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.105: 33 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.105: 31 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.105: 29 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.105: 26 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.105: 25 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.105: 23 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.105: 21 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.105: 19 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.105: 16 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.105: 15 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.105: 12 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.105: 11 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.105: 9 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.105: 7 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.105: 44 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.105: 12 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.105: 52 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.105: 19 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.105: 6 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.105: 98 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.105: 26 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.105: 24 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.105: 34 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.105: 26 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.105: 99 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.105: 41 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.105: 26 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.105: 13 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.105: 22 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.105: 20 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.105: 12 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.105: 71 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.105: 3 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.105: 70 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.105: 10 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.105: 77 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.105: 6 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.105: 85 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.105: 60 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.105: 58 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.105: 4 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.105: 51 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.105: 63 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.105: 69 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.105: 74 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.105: 51 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.105: 99 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.105: 61 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.106: 59 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.106: 93 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.106: 41 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.106: 34 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.106: 59 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.106: 55 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.106: 83 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.106: 81 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.106: 48 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.106: 77 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.106: 39 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.106: 93 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.106: 35 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.106: 17 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.106: 36 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.106: 85 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.106: 83 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.106: 86 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.106: 4 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.106: 77 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.106: 80 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.106: 17 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.106: 51 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.106: 74 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.106: 72 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.106: 45 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.106: 43 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.106: 66 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.106: 3 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.106: 37 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.106: 60 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.106: 53 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.106: 56 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.106: 54 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.106: 47 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.106: 50 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.106: 44 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.106: 41 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.106: 40 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.106: 42 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.106: 56 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.106: 33 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.106: 36 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.106: 58 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.106: 62 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.106: 30 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.106: 28 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.106: 26 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.106: 16 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.106: 17 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.106: 36 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.106: 18 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.106: 68 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.107: 14 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.107: 40 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.107: 10 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.107: 8 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.107: 6 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.107: 4 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.107: 93 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.107: 53 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.107: 51 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.107: 52 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.107: 47 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.107: 93 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.107: 46 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.107: 89 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.107: 52 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.107: 91 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.107: 73 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.107: 46 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.107: 69 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.107: 32 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.107: 40 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.107: 32 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.107: 26 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.107: 24 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.107: 32 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.107: 65 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.107: 69 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.107: 26 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.107: 11 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.107: 22 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.107: 55 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.107: 59 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.107: 16 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.107: 4 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.107: 2 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.107: 10 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.107: 18 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.107: 31 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.107: 86 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.107: 27 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.107: 25 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.107: 23 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.107: 31 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.107: 19 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.107: 87 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.107: 31 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.107: 23 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.107: 27 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.107: 9 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.107: 96 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.108: 15 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.108: 92 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.108: 1 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.108: 39 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.108: 7 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.108: 17 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.108: 50 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.108: 89 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.108: 99 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.108: 12 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.108: 92 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.108: 3 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.108: 39 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.108: 89 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.108: 75 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.108: 73 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.108: 30 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.108: 81 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.108: 27 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.108: 24 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.108: 75 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.108: 70 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.108: 59 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.108: 57 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.108: 55 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.108: 44 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.108: 68 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.108: 40 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.108: 100 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.108: 62 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.108: 96 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.108: 94 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.108: 56 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.108: 28 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.108: 91 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.108: 33 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.108: 22 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.108: 93 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.108: 44 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.108: 89 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.108: 76 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.108: 38 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.108: 19 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.108: 72 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.108: 6 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.108: 25 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.108: 66 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.108: 21 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.108: 19 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.108: 59 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.108: 3 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.108: 13 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.108: 55 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.108: 83 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.108: 49 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.108: 5 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.108: 3 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.108: 6 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.108: 4 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.108: 41 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.108: 38 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.108: 37 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.108: 98 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.108: 33 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.108: 81 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.108: 29 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.108: 88 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.108: 88 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.108: 22 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.108: 21 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.108: 89 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.108: 17 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.108: 13 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.108: 12 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.108: 11 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.108: 9 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.108: 41 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.108: 75 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.108: 3 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.108: 71 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.108: 80 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.108: 67 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.108: 76 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.108: 74 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.108: 52 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.108: 59 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.108: 79 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.108: 77 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.108: 23 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.108: 97 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.108: 40 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.108: 1 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.108: 45 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.108: 84 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.108: 5 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.108: 68 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.108: 83 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.108: 81 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.108: 74 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.108: 1 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.108: 75 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.108: 73 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.108: 66 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.108: 69 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.108: 67 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.108: 65 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.108: 17 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.108: 61 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.108: 59 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.108: 57 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.108: 9 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.108: 53 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.108: 51 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.108: 100 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.108: 1 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.108: 96 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.108: 95 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.109: 6 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.109: 34 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.109: 88 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.109: 86 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.109: 33 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.109: 31 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.109: 5 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.109: 27 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.109: 93 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.109: 23 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.109: 21 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.109: 14 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.109: 17 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.109: 15 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.109: 75 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.109: 81 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.109: 9 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.109: 77 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.109: 67 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.109: 73 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.109: 69 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.109: 50 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.109: 67 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.109: 65 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.109: 63 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.109: 84 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.109: 40 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.109: 95 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.109: 55 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.109: 53 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.109: 65 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.109: 84 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.109: 65 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.109: 45 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.109: 24 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.109: 41 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.109: 39 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.109: 58 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.109: 35 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.109: 31 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.109: 29 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.109: 11 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.109: 27 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.109: 63 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.109: 15 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.109: 21 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.109: 54 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.109: 17 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.109: 49 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.109: 13 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.109: 9 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.109: 9 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.109: 7 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.109: 5 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.109: 1 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.109: 36 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.109: 37 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.109: 5 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.109: 30 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.109: 28 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.109: 29 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.109: 3 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.109: 22 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.109: 8 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.109: 1 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.109: 4 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.109: 14 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.109: 7 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.109: 10 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.109: 7 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.109: 6 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.109: 4 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.109: 2 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.109: 6 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.109: 1 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.109: 2 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.109: 6 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.109: 4 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.109: 2 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.109: 1 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.110: offsets_filtered: 1710002883110322 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.110: 5 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.110: 6 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.110: 5 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.110: 6 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.110: 6 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.110: 7 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.110: 7 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.110: 8 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.110: 8 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.110: 9 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.110: 9 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.110: 13 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.110: 13 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.110: 13 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.110: 13 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.110: 13 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.110: 13 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.110: 11 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.110: 9 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.110: 11 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.110: 13 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.110: 15 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.110: 17 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.110: 18 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.110: 18 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.110: 18 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.110: 17 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.110: 17 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.110: 16 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.110: 15 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.110: 14 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.110: 13 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.110: 13 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.110: 13 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.110: 13 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.110: 13 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.110: 13 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.110: 14 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.110: 16 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.110: 18 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.110: 20 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.110: 20 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.110: 20 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.110: 20 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.110: 20 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.110: 18 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.110: 18 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.110: 16 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.110: 16 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.110: 14 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.110: 16 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.110: 18 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.110: 20 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.110: 22 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.110: 24 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.110: 26 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.110: 28 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.110: 28 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.110: 28 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.110: 28 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.110: 28 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.110: 28 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.110: 90 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.110: 92 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.110: 94 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.110: 96 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.110: 96 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.110: 96 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.110: 96 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.110: 96 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.110: 96 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.110: 96 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.110: 96 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.110: 96 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.110: 96 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.110: 96 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.110: 96 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.110: 96 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.110: 96 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.110: 96 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.110: 97 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.110: 97 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.110: 97 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.110: 97 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.110: 96 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.110: 96 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.110: 96 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.110: 96 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.110: 95 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.110: 94 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.110: 93 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.110: 92 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.110: 90 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.110: 88 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.110: 86 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.110: 84 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.110: 70 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.110: 68 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.110: 68 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.110: 68 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.110: 68 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.110: 68 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.110: 68 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.110: 68 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.110: 68 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.110: 68 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.110: 68 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.110: 68 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.110: 68 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.110: 97 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.110: 99 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.110: 99 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.110: 99 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.110: 99 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.110: 99 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.110: 99 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.110: 99 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.110: 99 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.110: 99 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.110: 99 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.110: 99 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.110: 99 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.110: 99 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.110: 99 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.110: 99 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.110: 99 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.110: 99 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.110: 99 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.110: 99 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.110: 99 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.110: 99 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.110: 99 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.110: 99 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.110: 98 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.110: 98 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.110: 98 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.110: 97 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.110: 97 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.110: 96 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.110: 96 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.110: 95 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.110: 95 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.110: 94 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.110: 94 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.110: 93 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.110: 93 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.110: 92 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.110: 91 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.110: 90 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.110: 89 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.110: 88 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.110: 87 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.110: 87 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.110: 86 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.110: 85 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.110: 85 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.110: 84 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.110: 83 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.110: 83 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.110: 81 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.110: 81 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.110: 79 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.110: 79 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.110: 79 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.110: 79 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.110: 79 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.110: 77 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.110: 77 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.110: 77 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.110: 75 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.110: 75 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.110: 75 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.110: 73 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.110: 71 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.110: 71 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.110: 70 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.110: 69 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.110: 68 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.110: 66 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.110: 66 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.110: 64 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.110: 64 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.110: 62 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.110: 62 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.110: 61 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.110: 60 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.110: 60 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.110: 59 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.110: 59 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.110: 59 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.110: 58 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.110: 58 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.110: 57 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.110: 57 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.110: 57 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.110: 57 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.110: 56 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.110: 56 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.110: 56 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.110: 55 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.110: 55 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.110: 55 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.110: 54 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.110: 54 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.110: 54 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.110: 54 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.110: 54 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.110: 54 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.110: 54 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.110: 54 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.110: 54 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.110: 54 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.110: 54 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.110: 53 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.110: 53 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.110: 53 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.110: 52 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.110: 52 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.110: 52 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.110: 52 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.110: 50 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.110: 50 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.110: 50 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.110: 50 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.110: 49 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.110: 49 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.110: 49 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.110: 49 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.110: 48 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.110: 47 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.110: 47 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.110: 47 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.110: 46 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.110: 46 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.110: 46 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.110: 46 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.110: 45 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.110: 44 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.110: 44 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.110: 44 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.110: 44 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.110: 44 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.110: 44 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.110: 44 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.110: 44 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.110: 43 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.110: 43 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.110: 43 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.110: 43 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.110: 43 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.110: 42 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.110: 42 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.110: 42 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.110: 42 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.110: 42 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.110: 42 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.110: 42 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.110: 42 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.110: 42 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.110: 42 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.110: 42 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.110: 42 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.110: 42 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.110: 42 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.110: 42 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.110: 42 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.110: 42 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.110: 42 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.110: 42 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.110: 41 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.110: 41 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.110: 41 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.110: 41 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.110: 41 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.110: 41 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.110: 41 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.110: 41 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.110: 41 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.110: 41 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.110: 41 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.110: 41 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.110: 40 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.110: 40 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.110: 40 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.110: 39 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.110: 39 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.110: 38 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.110: 38 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.110: 38 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.110: 38 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.110: 38 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.111: 37 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.111: 36 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.111: 36 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.111: 36 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.111: 36 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.111: 36 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.111: 35 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.111: 35 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.111: 35 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.111: 35 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.111: 35 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.111: 35 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.111: 35 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.111: 35 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.111: 35 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.111: 34 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.111: 34 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.111: 34 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.111: 34 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.111: 34 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.111: 34 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.111: 34 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.111: 34 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.111: 33 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.111: 33 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.111: 33 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.111: 33 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.111: 33 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.111: 33 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.111: 33 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.111: 33 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.111: 33 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.111: 33 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.111: 33 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.111: 33 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.111: 33 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.111: 33 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.111: 33 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.111: 33 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.111: 33 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.111: 33 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.111: 33 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.111: 33 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.111: 33 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.111: 33 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.111: 33 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.111: 32 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.111: 32 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.111: 32 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.111: 32 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.111: 32 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.111: 32 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.111: 32 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.111: 32 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.111: 32 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.111: 32 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.111: 32 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.111: 31 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.111: 31 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.111: 31 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.111: 31 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.111: 31 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.111: 31 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.111: 31 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.111: 31 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.111: 31 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.111: 31 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.111: 31 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.111: 31 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.111: 31 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.111: 30 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.111: 30 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.111: 30 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.111: 30 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.111: 30 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.111: 29 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.111: 29 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.111: 29 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.111: 29 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.111: 29 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.111: 29 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.111: 29 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.111: 29 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.111: 29 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.111: 29 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.111: 29 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.111: 28 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.111: 28 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.111: 28 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.111: 27 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.111: 27 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.111: 27 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.111: 27 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.111: 27 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.111: 27 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.111: 27 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.111: 27 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.111: 27 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.111: 27 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.111: 27 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.111: 27 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.111: 27 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.111: 27 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.111: 27 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.111: 27 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.111: 27 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.111: 27 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.111: 27 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.111: 27 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.111: 27 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.111: 27 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.111: 27 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.111: 27 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.111: 27 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.111: 27 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.111: 28 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.111: 28 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.111: 28 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.111: 28 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.111: 28 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.111: 28 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.111: 28 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.111: 28 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.111: 28 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.111: 28 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.111: 28 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.111: 28 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.111: 28 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.111: 28 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.111: 28 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.111: 28 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.111: 28 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.111: 28 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.111: 28 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.111: 28 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.111: 28 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.111: 28 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.111: 28 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.111: 28 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.111: 28 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.111: 28 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.111: 28 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.111: 28 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.112: 28 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.112: 28 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.112: 28 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.112: 28 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.112: 28 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.112: 28 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.112: 28 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.112: 28 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.112: 28 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.112: 28 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.112: 28 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.112: 28 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.112: 28 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.112: 28 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.112: 28 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.112: 28 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.112: 28 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.112: 28 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.112: 28 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.112: 28 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.112: 28 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.112: 28 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.112: 28 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.112: 28 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.112: 28 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.112: 28 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.112: 28 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.112: 28 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.112: 28 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.112: 28 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.112: 28 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.112: 28 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.112: 29 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.112: 29 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.112: 29 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.113: 29 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.113: 29 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.113: 29 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.113: 29 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.113: 29 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.113: 29 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.113: 29 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.113: 29 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.113: 29 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.113: 29 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.113: 29 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.113: 29 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.113: 29 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.113: 29 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.113: 29 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.113: 29 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.113: 29 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.113: 29 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.113: 29 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.113: 29 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.113: 29 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.113: 29 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.113: 30 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.113: 30 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.113: 30 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.113: 30 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.113: 30 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.113: 30 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.113: 30 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.113: 30 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.113: 30 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.113: 30 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.113: 30 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.113: 30 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.113: 30 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.113: 30 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.113: 30 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.113: 30 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.113: 30 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.113: 30 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.113: 30 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.113: 30 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.113: 30 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.113: 30 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.113: 30 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.113: 30 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.113: 30 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.113: 30 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.113: 30 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.113: 30 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.113: 30 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.114: 31 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.114: 31 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.114: 31 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.114: 31 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.114: 31 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.114: 31 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.114: 30 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.114: 31 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.114: 31 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.114: 31 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.114: 31 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.114: 31 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.114: 31 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.114: 31 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.114: 31 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.114: 31 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.114: 31 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.114: 31 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.114: 31 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.114: 31 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.114: 30 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.114: 30 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.114: 30 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.114: 30 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.114: 30 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.114: 30 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.114: 30 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.114: 30 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.114: 30 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.114: 30 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.114: 30 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.114: 30 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.114: 30 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.114: 30 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.114: 30 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.114: 30 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.114: 30 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.114: 31 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.114: 31 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.114: 31 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.114: 31 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.114: 31 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.114: 31 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.114: 31 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.114: 31 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.114: 31 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.114: 31 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.114: 31 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.114: 31 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.114: 30 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.114: 30 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.114: 30 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.114: 30 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.114: 30 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.114: 30 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.114: 30 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.114: 30 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.114: 30 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.114: 30 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.114: 30 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.114: 30 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.114: 30 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.114: 30 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.114: 30 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.114: 30 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.114: 30 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.114: 30 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.114: 30 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.114: 30 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.115: 30 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.115: 30 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.115: 30 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.115: 30 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.115: 30 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.115: 30 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.115: 31 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.115: 30 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.115: 30 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.115: 30 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.115: 30 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.115: 30 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.115: 30 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.115: 30 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.115: 30 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.115: 30 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.115: 29 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.115: 29 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.115: 29 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.115: 30 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.115: 30 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.115: 30 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.115: 30 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.115: 30 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.115: 30 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.115: 30 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.115: 30 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.115: 30 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.115: 30 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.115: 30 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.115: 30 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.115: 30 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.115: 30 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.115: 30 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.115: 30 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.115: 30 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.115: 30 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.115: 30 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.115: 30 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.115: 30 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.115: 30 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.115: 30 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.115: 30 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.115: 30 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.115: 30 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.115: 30 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.115: 30 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.115: 30 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.115: 30 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.115: 30 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.115: 29 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.115: 29 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.115: 29 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.115: 29 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.115: 29 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.115: 29 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.115: 29 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.115: 29 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.115: 29 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.115: 29 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.115: 29 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.115: 29 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.115: 29 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.115: 29 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.115: 29 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.115: 29 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.115: 29 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.115: 29 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.115: 29 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.115: 29 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.115: 29 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.115: 29 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.115: 29 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.115: 29 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.115: 29 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.115: 29 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.115: 29 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.115: 29 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.115: 29 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.115: 29 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.115: 29 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.115: 29 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.115: 29 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.115: 29 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.115: 29 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.115: 29 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.115: 29 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.115: 29 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.115: 29 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.115: 29 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.115: 29 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.115: 29 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.115: 29 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.115: 29 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.115: 29 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.115: 29 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.115: 28 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.115: 28 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.115: 28 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.115: 28 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.115: 28 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.115: 28 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.115: 28 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.115: 28 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.115: 28 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.115: 28 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.115: 28 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.115: 28 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.115: 28 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.115: 28 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.115: 28 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.115: 27 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.115: 27 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.115: 27 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.115: 27 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.115: 26 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.115: 26 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.115: 26 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.115: 26 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.115: 26 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.115: 26 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.115: 26 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.115: 26 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.115: 26 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.115: 26 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.115: 26 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.115: 26 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.115: 26 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.115: 25 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.115: 25 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.115: 25 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 25 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 25 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 25 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 25 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 25 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 25 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 25 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 25 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 25 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 25 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 25 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 25 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 25 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 25 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 25 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 24 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 24 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 24 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 24 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 24 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 24 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 24 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 24 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 24 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 24 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 24 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 24 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 24 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 24 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 24 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 24 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 24 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 24 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 24 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 23 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 23 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 23 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 23 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 23 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 23 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 23 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 23 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 23 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 23 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 23 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 23 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 23 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 23 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 23 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 23 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 23 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 23 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 23 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 22 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 22 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 23 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 22 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 22 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 22 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 22 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 22 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 22 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 22 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 22 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 22 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 22 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 22 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 22 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 22 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 22 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 22 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 22 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 22 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 22 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 22 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 22 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 22 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 22 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 22 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 22 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 22 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 22 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 22 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 22 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 22 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 22 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 21 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 21 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 21 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 21 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 21 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 21 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 21 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 21 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 21 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 21 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 21 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 21 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 21 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 21 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 21 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 21 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 21 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 21 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 21 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 21 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 21 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 21 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 21 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 21 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 21 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 20 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 20 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 20 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 20 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 20 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 20 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 20 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 20 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 20 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 20 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 20 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 20 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 20 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 19 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 19 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 19 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 19 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 19 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 19 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 19 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 19 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 19 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 19 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 19 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 19 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 19 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 19 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 19 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 19 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 19 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 18 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 18 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 18 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 18 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 18 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 18 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 18 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 18 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 18 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 18 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 18 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 18 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 18 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 18 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 18 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 18 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 18 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 18 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 18 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 18 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 18 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 18 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 18 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 18 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 18 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 18 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 18 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 18 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 18 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 18 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 18 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 18 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 18 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 18 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 17 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 17 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 17 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 17 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 17 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 17 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 17 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 17 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 17 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 17 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 17 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 17 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 17 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 16 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 16 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 16 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 16 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 16 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 16 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 16 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 16 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 16 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 16 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 16 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 16 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 16 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 16 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 16 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 16 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 15 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 15 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 15 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 15 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 15 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 15 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 15 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 15 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 15 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 15 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 15 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 15 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 15 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 15 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 15 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 15 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 15 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 14 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 14 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 14 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 14 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 14 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 14 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 14 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 14 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 14 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 14 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 14 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 14 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 14 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 14 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 14 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 14 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 14 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 14 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 13 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 13 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 13 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 13 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 13 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 13 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 13 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 13 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 13 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 13 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 13 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 13 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 13 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 13 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 13 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 13 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 13 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 13 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 13 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 13 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 13 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 13 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 12 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 12 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 12 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 12 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 12 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 12 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 12 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 13 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 13 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 13 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 13 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 12 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 12 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 12 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 12 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 12 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 12 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 12 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 12 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 12 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 12 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 12 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 12 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 12 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 12 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 12 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 12 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 12 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 12 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 12 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 12 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 12 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 12 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 12 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 12 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 12 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 12 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 12 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 12 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 12 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 12 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 12 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 21 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 23 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 23 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 23 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 23 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 23 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 23 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 23 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 23 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 23 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 21 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 11 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 11 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 11 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 11 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 11 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 11 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 11 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 11 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 11 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 11 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 10 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 10 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 10 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 10 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 10 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 10 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 10 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 10 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 10 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 10 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 10 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 10 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 12 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 12 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 24 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 26 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 38 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 50 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 61 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 66 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 67 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 67 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 68 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 69 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 70 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 70 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 70 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 71 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 71 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 73 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 73 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 73 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 73 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 73 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 73 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 73 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 73 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 73 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 71 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 70 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 70 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 68 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 67 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 67 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 64 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 64 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 62 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 53 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 53 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 52 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 52 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 50 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 48 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 42 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 42 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 41 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 40 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 40 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 41 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 40 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 34 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 32 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 32 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 34 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 40 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 40 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 40 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 40 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 40 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 41 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 41 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 41 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 51 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 51 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 81 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 83 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 90 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 92 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 92 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 92 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 92 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 92 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 92 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 94 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 94 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 94 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 94 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 92 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 92 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 90 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 89 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 87 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 83 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 81 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 81 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 77 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 70 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 55 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 53 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 51 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 49 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 47 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 45 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 43 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 41 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 38 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 37 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 35 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 33 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 31 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 31 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 29 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 29 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 26 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 25 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 25 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.116: 25 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 24 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 24 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 24 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 24 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 24 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 24 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 23 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 22 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 21 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 20 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 20 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 20 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 22 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 22 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 24 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 24 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 26 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 26 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 26 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 26 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 26 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 26 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 34 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 34 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 41 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 51 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 51 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 58 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 58 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 58 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 58 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 59 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 59 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 59 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 60 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 59 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 60 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 59 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 60 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 59 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 59 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 59 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 59 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 59 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 61 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 61 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 61 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 61 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 59 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 59 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 59 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 59 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 59 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 55 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 59 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 59 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 55 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 60 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 53 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 53 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 54 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 53 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 53 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 51 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 51 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 51 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 51 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 51 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 50 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 47 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 50 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 50 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 47 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 47 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 45 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 44 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 43 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 42 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 41 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 41 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 41 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 41 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 40 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 40 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 36 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 36 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 36 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 36 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 36 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 36 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 36 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 36 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 36 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 36 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 40 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 40 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 40 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 46 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 46 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 46 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 46 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 46 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 46 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 46 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 46 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 46 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 47 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 47 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 47 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 47 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 51 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 51 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 47 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 46 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 46 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 40 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 32 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 32 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 32 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 32 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 31 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 27 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 27 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 26 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 26 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 26 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 26 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 26 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 26 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 26 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 25 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 25 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 23 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 25 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 25 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 23 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 23 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 25 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 27 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 27 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 27 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 27 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 27 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 27 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 31 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 31 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 31 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 39 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 39 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 31 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 39 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 39 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 50 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 57 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 55 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 55 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 55 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 55 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 57 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 59 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 62 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 68 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 62 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 59 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 62 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 59 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 59 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 62 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 59 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 59 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 59 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 59 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 57 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 59 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 59 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 57 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 57 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 56 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 55 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 56 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 56 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 44 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 55 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 55 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 49 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 44 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 38 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 33 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 33 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 33 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 38 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 38 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 38 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 37 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 37 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 33 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 33 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 37 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 33 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 33 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 37 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 33 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 33 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 33 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 29 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 29 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 33 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 33 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 29 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 29 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 33 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 37 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 38 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 41 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 41 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 52 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 59 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 59 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 59 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 59 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 59 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 52 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 45 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 52 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 52 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 52 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 59 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 67 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 68 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 68 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 71 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 73 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 71 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 71 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 69 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 68 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 68 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 67 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 66 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 66 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 66 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 65 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 61 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 65 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 61 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 65 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 66 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 66 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 65 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 66 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 66 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 65 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 61 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 59 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 59 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 59 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 57 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 53 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 51 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 34 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 33 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 34 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 34 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 33 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 33 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 34 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 34 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 34 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 34 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 50 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 50 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 50 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 63 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 63 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 63 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 55 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 55 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 63 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 65 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 65 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 65 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 65 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 65 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 65 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 65 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 65 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 63 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 58 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 58 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 55 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 55 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 53 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 50 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 53 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 45 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 45 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 41 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 40 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 39 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 35 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 31 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 29 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 29 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 29 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 27 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 27 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 28 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 28 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 27 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 22 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 21 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 17 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 15 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 15 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 14 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 13 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 10 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 9 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 9 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 8 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 7 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 7 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 7 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 6 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 6 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 6 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 6 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 6 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 6 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 6 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 6 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 6 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 6 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 6 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 6 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 4 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 6 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 6 166s (process:2176): libfprint-assembling-DEBUG: 16:48:03.117: 1 166s (process:2176): libfprint-image_device-DEBUG: 16:48:03.118: Image device captured an image 166s (process:2176): libfprint-image_device-DEBUG: 16:48:03.119: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 166s (process:2176): libfprint-device-DEBUG: 16:48:03.119: Device reported finger status change: FP_FINGER_STATUS_PRESENT 166s (process:2176): libfprint-device-DEBUG: 16:48:03.119: Device reported finger status change: FP_FINGER_STATUS_NONE 166s (process:2176): libfprint-image_device-DEBUG: 16:48:03.119: Image device reported finger status: off 166s (process:2176): libfprint-image_device-DEBUG: 16:48:03.119: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 166s (process:2176): libfprint-image_device-DEBUG: 16:48:03.119: Deactivating image device 166s (process:2176): libfprint-image_device-DEBUG: 16:48:03.119: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_DEACTIVATING 166s (process:2176): libfprint-image-DEBUG: 16:48:03.169: Minutiae scan completed in 0.050335 secs 166s (process:2176): libfprint-device-DEBUG: 16:48:03.170: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 166s (process:2176): libfprint-SSM-DEBUG: 16:48:03.199: [vfs0050] SSM_STATES entering state 10 166s (process:2176): libfprint-SSM-DEBUG: 16:48:03.199: [vfs0050] SSM_STATES entering state 3 166s (process:2176): libfprint-SSM-DEBUG: 16:48:03.199: [vfs0050] SUBSM1_STATES entering state 0 166s (process:2176): libfprint-SSM-DEBUG: 16:48:03.200: [vfs0050] SUBSM1_STATES entering state 1 166s (process:2176): libfprint-SSM-DEBUG: 16:48:03.200: [vfs0050] SUBSM1_STATES entering state 2 166s (process:2176): libfprint-SSM-DEBUG: 16:48:03.201: [vfs0050] SUBSM1_STATES completed successfully 166s (process:2176): libfprint-SSM-DEBUG: 16:48:03.201: [vfs0050] SSM_STATES entering state 4 166s (process:2176): libfprint-SSM-DEBUG: 16:48:03.201: [vfs0050] SUBSM2_STATES entering state 0 166s (process:2176): libfprint-SSM-DEBUG: 16:48:03.202: [vfs0050] SUBSM2_STATES entering state 1 166s (process:2176): libfprint-SSM-DEBUG: 16:48:03.202: [vfs0050] SUBSM2_STATES entering state 2 166s (process:2176): libfprint-SSM-DEBUG: 16:48:03.203: [vfs0050] SUBSM2_STATES entering state 3 166s (process:2176): libfprint-SSM-DEBUG: 16:48:03.203: [vfs0050] SUBSM2_STATES entering state 4 166s (process:2176): libfprint-SSM-DEBUG: 16:48:03.204: [vfs0050] SUBSM2_STATES entering state 5 166s (process:2176): libfprint-SSM-DEBUG: 16:48:03.205: [vfs0050] SUBSM2_STATES entering state 6 166s (process:2176): libfprint-SSM-DEBUG: 16:48:03.205: [vfs0050] SUBSM1_STATES entering state 0 166s (process:2176): libfprint-SSM-DEBUG: 16:48:03.205: [vfs0050] SUBSM1_STATES entering state 1 166s (process:2176): libfprint-SSM-DEBUG: 16:48:03.206: [vfs0050] SUBSM1_STATES entering state 2 166s (process:2176): libfprint-SSM-DEBUG: 16:48:03.206: [vfs0050] SUBSM1_STATES completed successfully 166s (process:2176): libfprint-SSM-DEBUG: 16:48:03.206: [vfs0050] SUBSM2_STATES completed successfully 166s (process:2176): libfprint-SSM-DEBUG: 16:48:03.206: [vfs0050] SSM_STATES entering state 5 166s (process:2176): libfprint-SSM-DEBUG: 16:48:03.206: [vfs0050] SSM_STATES completed successfully 166s (process:2176): libfprint-image_device-DEBUG: 16:48:03.206: Image device deactivation completed 166s (process:2176): libfprint-image_device-DEBUG: 16:48:03.206: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE 166s (process:2176): libfprint-device-DEBUG: 16:48:03.206: Device reported capture completion 166s (process:2176): libfprint-device-DEBUG: 16:48:03.206: Completing action FPI_DEVICE_ACTION_CAPTURE in idle! 166s (process:2176): libfprint-device-DEBUG: 16:48:03.206: Updated temperature model after 0.04 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 166s (process:2176): libfprint-image_device-DEBUG: 16:48:03.207: Image device close completed 166s (process:2176): libfprint-device-DEBUG: 16:48:03.207: Device reported close completion 166s (process:2176): libfprint-device-DEBUG: 16:48:03.207: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 166s (process:2176): libfprint-device-DEBUG: 16:48:03.207: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 166s ** (umockdev-run:2172): DEBUG: 16:48:03.356: umockdev.vala:150: Removing test bed /tmp/umockdev.273YJ2 166s (umockdev-run:2172): GLib-DEBUG: 16:48:03.360: unsetenv() is not thread-safe and should not be used after threads are created 166s Comparing PNGs /tmp/libfprint-umockdev-test-kjrmq7mx/capture.png and /usr/share/installed-tests/libfprint-2/vfs0050/capture.png 166s PASS: libfprint-2/driver-vfs0050.test 166s Running test: libfprint-2/fp-context.test 166s TAP version 13 166s # random seed: R02S4fea70aae2a5e11dc330864a0aa0e727 166s 1..9 166s # Start of context tests 166s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.7+tod1) 166s # libfprint-tod-DEBUG: Impossible to load the shared drivers dir Error opening directory ?/usr/lib/aarch64-linux-gnu/libfprint-2/tod-1?: No such file or directory 166s ok 1 /context/new 166s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.7+tod1) 166s # libfprint-tod-DEBUG: Impossible to load the shared drivers dir Error opening directory ?/usr/lib/aarch64-linux-gnu/libfprint-2/tod-1?: No such file or directory 166s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0003 166s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 166s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0002 166s ok 2 /context/no-devices 166s # GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used after threads are created 166s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.7+tod1) 166s # libfprint-tod-DEBUG: Impossible to load the shared drivers dir Error opening directory ?/usr/lib/aarch64-linux-gnu/libfprint-2/tod-1?: No such file or directory 166s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0003 166s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 166s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0002 166s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_IMAGE, /tmp/libfprint-KOCBK2/virtual_image.socket 166s # libfprint-context-DEBUG: created 166s # libfprint-device-DEBUG: Device reported probe completion 166s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 166s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 166s # GLib-DEBUG: unsetenv() is not thread-safe and should not be used after threads are created 166s ok 3 /context/has-virtual-device 166s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.7+tod1) 166s # libfprint-tod-DEBUG: Impossible to load the shared drivers dir Error opening directory ?/usr/lib/aarch64-linux-gnu/libfprint-2/tod-1?: No such file or directory 166s # GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used after threads are created 166s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0003 166s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 166s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0002 166s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_IMAGE, /tmp/libfprint-5O29J2/virtual_image.socket 166s # libfprint-context-DEBUG: created 166s # libfprint-device-DEBUG: Device reported probe completion 166s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 166s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 166s # GLib-DEBUG: unsetenv() is not thread-safe and should not be used after threads are created 166s ok 4 /context/enumerates-new-devices 166s # GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used after threads are created 166s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.7+tod1) 166s # libfprint-tod-DEBUG: Impossible to load the shared drivers dir Error opening directory ?/usr/lib/aarch64-linux-gnu/libfprint-2/tod-1?: No such file or directory 166s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0003 166s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 166s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0002 166s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_IMAGE, /tmp/libfprint-X429J2/virtual_image.socket 166s # libfprint-context-DEBUG: created 166s # libfprint-device-DEBUG: Device reported probe completion 166s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 166s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 166s # GLib-DEBUG: unsetenv() is not thread-safe and should not be used after threads are created 166s ok 5 /context/remove-device-closed 166s # GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used after threads are created 166s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.7+tod1) 166s # libfprint-tod-DEBUG: Impossible to load the shared drivers dir Error opening directory ?/usr/lib/aarch64-linux-gnu/libfprint-2/tod-1?: No such file or directory 166s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0003 166s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 166s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0002 166s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_IMAGE, /tmp/libfprint-6JZ9J2/virtual_image.socket 166s # libfprint-context-DEBUG: created 166s # libfprint-device-DEBUG: Device reported probe completion 166s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 166s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 166s (/usr/libexec/installed-tests/libfprint-2/test-fp-context:2183): libfprint-virtual_image-DEBUG: 16:48:03.432: 54433531: ../libfprint/drivers/virtual-image.c:216 166s (/usr/libexec/installed-tests/libfprint-2/test-fp-context:2183): libfprint-virtual_device_connection-DEBUG: 16:48:03.432: 54433646: ../libfprint/drivers/virtual-device-listener.c:153 166s # libfprint-image_device-DEBUG: Image device open completed 166s # libfprint-device-DEBUG: Device reported open completion 166s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 166s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 166s (/usr/libexec/installed-tests/libfprint-2/test-fp-context:2183): libfprint-virtual_image-DEBUG: 16:48:03.533: 54534131: ../libfprint/drivers/virtual-image.c:244 166s # libfprint-image_device-DEBUG: Image device close completed 166s # libfprint-device-DEBUG: Device reported close completion 166s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 166s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 166s # GLib-DEBUG: unsetenv() is not thread-safe and should not be used after threads are created 166s ok 6 /context/remove-device-closing 166s # GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used after threads are created 166s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.7+tod1) 166s # libfprint-tod-DEBUG: Impossible to load the shared drivers dir Error opening directory ?/usr/lib/aarch64-linux-gnu/libfprint-2/tod-1?: No such file or directory 166s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0003 166s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 166s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0002 166s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_IMAGE, /tmp/libfprint-IKA3J2/virtual_image.socket 166s # libfprint-context-DEBUG: created 166s # libfprint-device-DEBUG: Device reported probe completion 166s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 166s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 166s (/usr/libexec/installed-tests/libfprint-2/test-fp-context:2183): libfprint-virtual_image-DEBUG: 16:48:03.636: 54637450: ../libfprint/drivers/virtual-image.c:216 166s (/usr/libexec/installed-tests/libfprint-2/test-fp-context:2183): libfprint-virtual_device_connection-DEBUG: 16:48:03.636: 54637496: ../libfprint/drivers/virtual-device-listener.c:153 166s # libfprint-image_device-DEBUG: Image device open completed 166s # libfprint-device-DEBUG: Device reported open completion 166s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 166s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 166s (/usr/libexec/installed-tests/libfprint-2/test-fp-context:2183): libfprint-virtual_image-DEBUG: 16:48:03.737: 54737928: ../libfprint/drivers/virtual-image.c:244 166s # libfprint-image_device-DEBUG: Image device close completed 166s # libfprint-device-DEBUG: Device reported close completion 166s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 166s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 166s # GLib-DEBUG: unsetenv() is not thread-safe and should not be used after threads are created 166s ok 7 /context/remove-device-open 166s # GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used after threads are created 166s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.7+tod1) 166s # libfprint-tod-DEBUG: Impossible to load the shared drivers dir Error opening directory ?/usr/lib/aarch64-linux-gnu/libfprint-2/tod-1?: No such file or directory 166s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0003 166s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 166s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0002 166s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_IMAGE, /tmp/libfprint-A5EWJ2/virtual_image.socket 166s # libfprint-context-DEBUG: created 166s # libfprint-device-DEBUG: Device reported probe completion 166s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 166s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 166s (/usr/libexec/installed-tests/libfprint-2/test-fp-context:2183): libfprint-virtual_image-DEBUG: 16:48:03.840: 54841432: ../libfprint/drivers/virtual-image.c:216 166s (/usr/libexec/installed-tests/libfprint-2/test-fp-context:2183): libfprint-virtual_device_connection-DEBUG: 16:48:03.840: 54841448: ../libfprint/drivers/virtual-device-listener.c:153 166s # libfprint-image_device-DEBUG: Image device open completed 166s # libfprint-device-DEBUG: Device reported open completion 166s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 166s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 166s (/usr/libexec/installed-tests/libfprint-2/test-fp-context:2183): libfprint-virtual_image-DEBUG: 16:48:03.940: 54941675: ../libfprint/drivers/virtual-image.c:244 167s Executing: libfprint-2/fp-context.test 167s # libfprint-image_device-DEBUG: Image device close completed 167s # libfprint-device-DEBUG: Device reported close completion 167s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 167s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 167s # GLib-DEBUG: unsetenv() is not thread-safe and should not be used after threads are created 167s ok 8 /context/remove-device-opening 167s # GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used after threads are created 167s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.7+tod1) 167s # libfprint-tod-DEBUG: Impossible to load the shared drivers dir Error opening directory ?/usr/lib/aarch64-linux-gnu/libfprint-2/tod-1?: No such file or directory 167s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0003 167s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 167s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0002 167s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_IMAGE, /tmp/libfprint-5S1CK2/virtual_image.socket 167s # libfprint-context-DEBUG: created 167s # libfprint-device-DEBUG: Device reported probe completion 167s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 167s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 167s (/usr/libexec/installed-tests/libfprint-2/test-fp-context:2183): libfprint-virtual_image-DEBUG: 16:48:04.044: 55044805: ../libfprint/drivers/virtual-image.c:216 167s (/usr/libexec/installed-tests/libfprint-2/test-fp-context:2183): libfprint-virtual_device_connection-DEBUG: 16:48:04.044: 55044826: ../libfprint/drivers/virtual-device-listener.c:153 167s # libfprint-image_device-DEBUG: Image device open completed 167s # libfprint-device-DEBUG: Device reported open completion 167s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 167s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 167s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 167s # libfprint-image_device-DEBUG: Activating image device 167s # libfprint-image_device-DEBUG: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING 167s # libfprint-image_device-DEBUG: Image device activation completed 167s # libfprint-image_device-DEBUG: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE 167s # libfprint-image_device-DEBUG: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 167s # libfprint-device-DEBUG: Device reported finger status change: FP_FINGER_STATUS_NEEDED 167s # libfprint-image_device-DEBUG: Deactivating image device 167s # libfprint-image_device-DEBUG: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_DEACTIVATING 167s # libfprint-image_device-DEBUG: Image device deactivation completed 167s # libfprint-image_device-DEBUG: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE 167s # libfprint-device-DEBUG: Device reported generic error (The driver encountered a protocol error with the device.) during action; action was: FPI_DEVICE_ACTION_ENROLL 167s # libfprint-device-DEBUG: Device reported enroll completion 167s # libfprint-device-DEBUG: Device reported finger status change: FP_FINGER_STATUS_NONE 167s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 167s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 167s (/usr/libexec/installed-tests/libfprint-2/test-fp-context:2183): libfprint-virtual_image-DEBUG: 16:48:04.144: 55145476: ../libfprint/drivers/virtual-image.c:244 167s # libfprint-image_device-DEBUG: Image device close completed 167s # libfprint-device-DEBUG: Device reported close completion 167s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 167s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 167s # GLib-DEBUG: unsetenv() is not thread-safe and should not be used after threads are created 167s ok 9 /context/remove-device-active 167s # End of context tests 167s PASS: libfprint-2/fp-context.test 167s Running test: libfprint-2/driver-elan.test 167s ** (umockdev-run:2207): DEBUG: 16:48:04.285: umockdev.vala:123: Created udev test bed /tmp/umockdev.8X97J2 167s ** (umockdev-run:2207): DEBUG: 16:48:04.285: umockdev.vala:1297: parsing device description for /devices/pci0000:00/0000:00:14.0/usb1/1-4/1-4.4 167s ** (umockdev-run:2207): DEBUG: 16:48:04.286: umockdev.vala:1366: creating device /devices/pci0000:00/0000:00:14.0/usb1/1-4/1-4.4 (subsystem usb) 167s ** (umockdev-run:2207): DEBUG: 16:48:04.288: umockdev.vala:1411: create_node_for_device: creating file device /tmp/umockdev.8X97J2/dev/bus/usb/001/094 167s ** (umockdev-run:2207): DEBUG: 16:48:04.288: umockdev.vala:1297: parsing device description for /devices/pci0000:00/0000:00:14.0/usb1/1-4 167s ** (umockdev-run:2207): DEBUG: 16:48:04.289: umockdev.vala:1366: creating device /devices/pci0000:00/0000:00:14.0/usb1/1-4 (subsystem usb) 167s ** (umockdev-run:2207): DEBUG: 16:48:04.290: umockdev.vala:1411: create_node_for_device: creating file device /tmp/umockdev.8X97J2/dev/bus/usb/001/083 167s ** (umockdev-run:2207): DEBUG: 16:48:04.290: umockdev.vala:1297: parsing device description for /devices/pci0000:00/0000:00:14.0/usb1 167s ** (umockdev-run:2207): DEBUG: 16:48:04.291: umockdev.vala:1366: creating device /devices/pci0000:00/0000:00:14.0/usb1 (subsystem usb) 167s ** (umockdev-run:2207): DEBUG: 16:48:04.293: umockdev.vala:1411: create_node_for_device: creating file device /tmp/umockdev.8X97J2/dev/bus/usb/001/001 167s ** (umockdev-run:2207): DEBUG: 16:48:04.293: umockdev.vala:1297: parsing device description for /devices/pci0000:00/0000:00:14.0 167s ** (umockdev-run:2207): DEBUG: 16:48:04.293: umockdev.vala:1366: creating device /devices/pci0000:00/0000:00:14.0 (subsystem pci) 167s (umockdev-run:2207): GLib-GIO-DEBUG: 16:48:04.295: _g_io_module_get_default: Found default implementation local (GLocalVfs) for ?gio-vfs? 167s (process:2211): libfprint-context-DEBUG: 16:48:04.352: Initializing FpContext (libfprint version 1.94.7+tod1) 167s (process:2211): libfprint-tod-DEBUG: 16:48:04.352: Impossible to load the shared drivers dir Error opening directory “/usr/lib/aarch64-linux-gnu/libfprint-2/tod-1”: No such file or directory 167s (process:2211): libfprint-context-DEBUG: 16:48:04.354: No driver found for USB device 17EF:1018 167s (process:2211): libfprint-context-DEBUG: 16:48:04.354: No driver found for USB device 1D6B:0002 167s (process:2211): libfprint-device-DEBUG: 16:48:04.355: Device reported probe completion 167s (process:2211): libfprint-device-DEBUG: 16:48:04.355: Completing action FPI_DEVICE_ACTION_PROBE in idle! 167s (process:2211): libfprint-device-DEBUG: 16:48:04.355: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 167s (process:2211): libfprint-elan-DEBUG: 16:48:04.356: 55357197: ../libfprint/drivers/elan.c:908 167s (process:2211): libfprint-image_device-DEBUG: 16:48:04.356: Image device open completed 167s (process:2211): libfprint-device-DEBUG: 16:48:04.356: Device reported open completion 167s (process:2211): libfprint-device-DEBUG: 16:48:04.356: Completing action FPI_DEVICE_ACTION_OPEN in idle! 167s (process:2211): libfprint-device-DEBUG: 16:48:04.356: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 167s (process:2211): libfprint-device-DEBUG: 16:48:04.357: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 167s (process:2211): libfprint-image_device-DEBUG: 16:48:04.357: Activating image device 167s (process:2211): libfprint-image_device-DEBUG: 16:48:04.357: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING 167s (process:2211): libfprint-elan-DEBUG: 16:48:04.357: 55357829: ../libfprint/drivers/elan.c:960 167s (process:2211): libfprint-elan-DEBUG: 16:48:04.357: 55357833: ../libfprint/drivers/elan.c:951 167s (process:2211): libfprint-elan-DEBUG: 16:48:04.357: 55357836: ../libfprint/drivers/elan.c:892 167s (process:2211): libfprint-elan-DEBUG: 16:48:04.357: 55357839: ../libfprint/drivers/elan.c:100 167s (process:2211): libfprint-SSM-DEBUG: 16:48:04.357: [elan] ACTIVATE_NUM_STATES entering state 0 167s (process:2211): libfprint-elan-DEBUG: 16:48:04.357: 55357852: ../libfprint/drivers/elan.c:820 167s (process:2211): libfprint-elan-DEBUG: 16:48:04.357: 55358508: ../libfprint/drivers/elan.c:346 167s (process:2211): libfprint-elan-DEBUG: 16:48:04.357: 55358523: ../libfprint/drivers/elan.c:366 167s (process:2211): libfprint-elan-DEBUG: 16:48:04.357: 55358526: ../libfprint/drivers/elan.c:379 167s (process:2211): libfprint-elan-DEBUG: 16:48:04.358: 55359102: ../libfprint/drivers/elan.c:346 167s (process:2211): libfprint-elan-DEBUG: 16:48:04.358: 55359223: ../libfprint/drivers/elan.c:335 167s (process:2211): libfprint-SSM-DEBUG: 16:48:04.358: [elan] ACTIVATE_NUM_STATES entering state 1 167s (process:2211): libfprint-elan-DEBUG: 16:48:04.358: 55359246: ../libfprint/drivers/elan.c:820 167s (process:2211): libfprint-elan-DEBUG: 16:48:04.358: FW ver 0x0140 167s (process:2211): libfprint-SSM-DEBUG: 16:48:04.358: [elan] ACTIVATE_NUM_STATES entering state 2 167s (process:2211): libfprint-elan-DEBUG: 16:48:04.358: 55359255: ../libfprint/drivers/elan.c:820 167s (process:2211): libfprint-elan-DEBUG: 16:48:04.359: 55359764: ../libfprint/drivers/elan.c:346 167s (process:2211): libfprint-elan-DEBUG: 16:48:04.359: 55359822: ../libfprint/drivers/elan.c:366 167s (process:2211): libfprint-elan-DEBUG: 16:48:04.359: 55359958: ../libfprint/drivers/elan.c:379 167s (process:2211): libfprint-elan-DEBUG: 16:48:04.359: 55360466: ../libfprint/drivers/elan.c:346 167s (process:2211): libfprint-elan-DEBUG: 16:48:04.359: 55360586: ../libfprint/drivers/elan.c:335 167s (process:2211): libfprint-SSM-DEBUG: 16:48:04.359: [elan] ACTIVATE_NUM_STATES entering state 3 167s (process:2211): libfprint-elan-DEBUG: 16:48:04.359: 55360609: ../libfprint/drivers/elan.c:820 167s (process:2211): libfprint-elan-DEBUG: 16:48:04.359: sensor dimensions, WxH: 144x64 167s (process:2211): libfprint-SSM-DEBUG: 16:48:04.359: [elan] ACTIVATE_NUM_STATES entering state 4 167s (process:2211): libfprint-elan-DEBUG: 16:48:04.359: 55360619: ../libfprint/drivers/elan.c:820 167s (process:2211): libfprint-elan-DEBUG: 16:48:04.359: skipping command 0x40 0x2a for this device (for devices 0x1 but device is 0x0) 167s (process:2211): libfprint-elan-DEBUG: 16:48:04.359: 55360626: ../libfprint/drivers/elan.c:335 167s (process:2211): libfprint-SSM-DEBUG: 16:48:04.359: [elan] ACTIVATE_NUM_STATES completed successfully 167s (process:2211): libfprint-elan-DEBUG: 16:48:04.359: 55360632: ../libfprint/drivers/elan.c:881 167s (process:2211): libfprint-image_device-DEBUG: 16:48:04.359: Image device activation completed 167s (process:2211): libfprint-image_device-DEBUG: 16:48:04.359: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE 167s (process:2211): libfprint-elan-DEBUG: 16:48:04.359: 55360648: ../libfprint/drivers/elan.c:960 167s (process:2211): libfprint-image_device-DEBUG: 16:48:04.359: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 167s (process:2211): libfprint-elan-DEBUG: 16:48:04.359: 55360656: ../libfprint/drivers/elan.c:960 167s (process:2211): libfprint-elan-DEBUG: 16:48:04.359: 55360658: ../libfprint/drivers/elan.c:792 167s (process:2211): libfprint-elan-DEBUG: 16:48:04.359: 55360661: ../libfprint/drivers/elan.c:100 167s (process:2211): libfprint-SSM-DEBUG: 16:48:04.359: [elan] CALIBRATE_NUM_STATES entering state 0 167s (process:2211): libfprint-elan-DEBUG: 16:48:04.359: 55360668: ../libfprint/drivers/elan.c:691 167s (process:2211): libfprint-device-DEBUG: 16:48:04.360: Device reported finger status change: FP_FINGER_STATUS_NEEDED 167s (process:2211): libfprint-elan-DEBUG: 16:48:04.360: 55361350: ../libfprint/drivers/elan.c:346 167s (process:2211): libfprint-elan-DEBUG: 16:48:04.360: 55361367: ../libfprint/drivers/elan.c:366 167s (process:2211): libfprint-elan-DEBUG: 16:48:04.360: 55361370: ../libfprint/drivers/elan.c:379 167s (process:2211): libfprint-elan-DEBUG: 16:48:04.361: 55361979: ../libfprint/drivers/elan.c:346 167s (process:2211): libfprint-elan-DEBUG: 16:48:04.361: 55362010: ../libfprint/drivers/elan.c:335 167s (process:2211): libfprint-SSM-DEBUG: 16:48:04.361: [elan] CALIBRATE_NUM_STATES entering state 1 167s (process:2211): libfprint-elan-DEBUG: 16:48:04.361: 55362019: ../libfprint/drivers/elan.c:691 167s (process:2211): libfprint-elan-DEBUG: 16:48:04.361: 55362021: ../libfprint/drivers/elan.c:156 167s (process:2211): libfprint-elan-DEBUG: 16:48:04.361: 55362025: ../libfprint/drivers/elan.c:118 167s (process:2211): libfprint-SSM-DEBUG: 16:48:04.361: [elan] CALIBRATE_NUM_STATES entering state 2 167s (process:2211): libfprint-elan-DEBUG: 16:48:04.361: 55362043: ../libfprint/drivers/elan.c:691 167s (process:2211): libfprint-elan-DEBUG: 16:48:04.361: 55362583: ../libfprint/drivers/elan.c:346 167s (process:2211): libfprint-elan-DEBUG: 16:48:04.361: 55362596: ../libfprint/drivers/elan.c:366 167s (process:2211): libfprint-elan-DEBUG: 16:48:04.361: 55362599: ../libfprint/drivers/elan.c:379 167s (process:2211): libfprint-elan-DEBUG: 16:48:04.362: 55363122: ../libfprint/drivers/elan.c:346 167s (process:2211): libfprint-elan-DEBUG: 16:48:04.362: 55363135: ../libfprint/drivers/elan.c:335 167s (process:2211): libfprint-SSM-DEBUG: 16:48:04.362: [elan] CALIBRATE_NUM_STATES entering state 3 167s (process:2211): libfprint-elan-DEBUG: 16:48:04.362: 55363143: ../libfprint/drivers/elan.c:691 167s (process:2211): libfprint-elan-DEBUG: 16:48:04.362: 55363146: ../libfprint/drivers/elan.c:634 167s (process:2211): libfprint-elan-DEBUG: 16:48:04.362: calibration mean: 8421, bg mean: 5805, delta: 2616 167s (process:2211): libfprint-SSM-DEBUG: 16:48:04.362: [elan] CALIBRATE_NUM_STATES entering state 4 167s (process:2211): libfprint-elan-DEBUG: 16:48:04.362: 55363158: ../libfprint/drivers/elan.c:691 167s (process:2211): libfprint-elan-DEBUG: 16:48:04.362: 55363659: ../libfprint/drivers/elan.c:346 167s (process:2211): libfprint-elan-DEBUG: 16:48:04.362: 55363672: ../libfprint/drivers/elan.c:366 167s (process:2211): libfprint-elan-DEBUG: 16:48:04.362: 55363675: ../libfprint/drivers/elan.c:379 167s (process:2211): libfprint-elan-DEBUG: 16:48:04.363: 55364249: ../libfprint/drivers/elan.c:346 167s (process:2211): libfprint-elan-DEBUG: 16:48:04.363: 55364389: ../libfprint/drivers/elan.c:335 167s (process:2211): libfprint-SSM-DEBUG: 16:48:04.363: [elan] CALIBRATE_NUM_STATES entering state 5 167s (process:2211): libfprint-elan-DEBUG: 16:48:04.363: 55364442: ../libfprint/drivers/elan.c:691 167s (process:2211): libfprint-elan-DEBUG: 16:48:04.363: calibration status: 0x01 167s (process:2211): libfprint-SSM-DEBUG: 16:48:04.414: [elan] CALIBRATE_NUM_STATES entering state 6 167s (process:2211): libfprint-elan-DEBUG: 16:48:04.414: 55414737: ../libfprint/drivers/elan.c:691 167s (process:2211): libfprint-SSM-DEBUG: 16:48:04.414: [elan] CALIBRATE_NUM_STATES entering state 4 167s (process:2211): libfprint-elan-DEBUG: 16:48:04.414: 55414752: ../libfprint/drivers/elan.c:691 167s (process:2211): libfprint-elan-DEBUG: 16:48:04.414: 55415470: ../libfprint/drivers/elan.c:346 167s (process:2211): libfprint-elan-DEBUG: 16:48:04.414: 55415484: ../libfprint/drivers/elan.c:366 167s (process:2211): libfprint-elan-DEBUG: 16:48:04.414: 55415488: ../libfprint/drivers/elan.c:379 167s (process:2211): libfprint-elan-DEBUG: 16:48:04.415: 55416077: ../libfprint/drivers/elan.c:346 167s (process:2211): libfprint-elan-DEBUG: 16:48:04.415: 55416091: ../libfprint/drivers/elan.c:335 167s (process:2211): libfprint-SSM-DEBUG: 16:48:04.415: [elan] CALIBRATE_NUM_STATES entering state 5 167s (process:2211): libfprint-elan-DEBUG: 16:48:04.415: 55416099: ../libfprint/drivers/elan.c:691 167s (process:2211): libfprint-elan-DEBUG: 16:48:04.415: calibration status: 0x01 167s (process:2211): libfprint-device-DEBUG: 16:48:04.457: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 167s (process:2211): libfprint-SSM-DEBUG: 16:48:04.465: [elan] CALIBRATE_NUM_STATES entering state 6 167s (process:2211): libfprint-elan-DEBUG: 16:48:04.465: 55466624: ../libfprint/drivers/elan.c:691 167s (process:2211): libfprint-SSM-DEBUG: 16:48:04.466: [elan] CALIBRATE_NUM_STATES entering state 4 167s (process:2211): libfprint-elan-DEBUG: 16:48:04.466: 55466765: ../libfprint/drivers/elan.c:691 167s (process:2211): libfprint-elan-DEBUG: 16:48:04.466: 55467464: ../libfprint/drivers/elan.c:346 167s (process:2211): libfprint-elan-DEBUG: 16:48:04.466: 55467478: ../libfprint/drivers/elan.c:366 167s (process:2211): libfprint-elan-DEBUG: 16:48:04.466: 55467485: ../libfprint/drivers/elan.c:379 167s (process:2211): libfprint-elan-DEBUG: 16:48:04.467: 55468124: ../libfprint/drivers/elan.c:346 167s (process:2211): libfprint-elan-DEBUG: 16:48:04.467: 55468254: ../libfprint/drivers/elan.c:335 167s (process:2211): libfprint-SSM-DEBUG: 16:48:04.467: [elan] CALIBRATE_NUM_STATES entering state 5 167s (process:2211): libfprint-elan-DEBUG: 16:48:04.467: 55468303: ../libfprint/drivers/elan.c:691 167s (process:2211): libfprint-elan-DEBUG: 16:48:04.467: calibration status: 0x01 167s (process:2211): libfprint-SSM-DEBUG: 16:48:04.517: [elan] CALIBRATE_NUM_STATES entering state 6 167s (process:2211): libfprint-elan-DEBUG: 16:48:04.517: 55518499: ../libfprint/drivers/elan.c:691 167s (process:2211): libfprint-SSM-DEBUG: 16:48:04.517: [elan] CALIBRATE_NUM_STATES entering state 4 167s (process:2211): libfprint-elan-DEBUG: 16:48:04.517: 55518510: ../libfprint/drivers/elan.c:691 167s (process:2211): libfprint-elan-DEBUG: 16:48:04.518: 55519190: ../libfprint/drivers/elan.c:346 167s (process:2211): libfprint-elan-DEBUG: 16:48:04.518: 55519204: ../libfprint/drivers/elan.c:366 167s (process:2211): libfprint-elan-DEBUG: 16:48:04.518: 55519208: ../libfprint/drivers/elan.c:379 167s (process:2211): libfprint-elan-DEBUG: 16:48:04.519: 55519816: ../libfprint/drivers/elan.c:346 167s (process:2211): libfprint-elan-DEBUG: 16:48:04.519: 55519830: ../libfprint/drivers/elan.c:335 167s (process:2211): libfprint-SSM-DEBUG: 16:48:04.519: [elan] CALIBRATE_NUM_STATES entering state 5 167s (process:2211): libfprint-elan-DEBUG: 16:48:04.519: 55519837: ../libfprint/drivers/elan.c:691 167s (process:2211): libfprint-elan-DEBUG: 16:48:04.519: calibration status: 0x01 167s (process:2211): libfprint-SSM-DEBUG: 16:48:04.569: [elan] CALIBRATE_NUM_STATES entering state 6 167s (process:2211): libfprint-elan-DEBUG: 16:48:04.569: 55570111: ../libfprint/drivers/elan.c:691 167s (process:2211): libfprint-SSM-DEBUG: 16:48:04.569: [elan] CALIBRATE_NUM_STATES entering state 4 167s (process:2211): libfprint-elan-DEBUG: 16:48:04.569: 55570234: ../libfprint/drivers/elan.c:691 167s (process:2211): libfprint-elan-DEBUG: 16:48:04.570: 55570935: ../libfprint/drivers/elan.c:346 167s (process:2211): libfprint-elan-DEBUG: 16:48:04.570: 55570949: ../libfprint/drivers/elan.c:366 167s (process:2211): libfprint-elan-DEBUG: 16:48:04.570: 55570952: ../libfprint/drivers/elan.c:379 167s (process:2211): libfprint-elan-DEBUG: 16:48:04.570: 55571509: ../libfprint/drivers/elan.c:346 167s (process:2211): libfprint-elan-DEBUG: 16:48:04.570: 55571629: ../libfprint/drivers/elan.c:335 167s (process:2211): libfprint-SSM-DEBUG: 16:48:04.570: [elan] CALIBRATE_NUM_STATES entering state 5 167s (process:2211): libfprint-elan-DEBUG: 16:48:04.570: 55571675: ../libfprint/drivers/elan.c:691 167s (process:2211): libfprint-elan-DEBUG: 16:48:04.571: calibration status: 0x01 167s (process:2211): libfprint-SSM-DEBUG: 16:48:04.621: [elan] CALIBRATE_NUM_STATES entering state 6 167s (process:2211): libfprint-elan-DEBUG: 16:48:04.621: 55622107: ../libfprint/drivers/elan.c:691 167s (process:2211): libfprint-SSM-DEBUG: 16:48:04.621: [elan] CALIBRATE_NUM_STATES entering state 4 167s (process:2211): libfprint-elan-DEBUG: 16:48:04.621: 55622126: ../libfprint/drivers/elan.c:691 167s (process:2211): libfprint-elan-DEBUG: 16:48:04.622: 55622752: ../libfprint/drivers/elan.c:346 167s (process:2211): libfprint-elan-DEBUG: 16:48:04.622: 55622764: ../libfprint/drivers/elan.c:366 167s (process:2211): libfprint-elan-DEBUG: 16:48:04.622: 55622767: ../libfprint/drivers/elan.c:379 167s (process:2211): libfprint-elan-DEBUG: 16:48:04.622: 55623339: ../libfprint/drivers/elan.c:346 167s (process:2211): libfprint-elan-DEBUG: 16:48:04.622: 55623455: ../libfprint/drivers/elan.c:335 167s (process:2211): libfprint-SSM-DEBUG: 16:48:04.622: [elan] CALIBRATE_NUM_STATES entering state 5 167s (process:2211): libfprint-elan-DEBUG: 16:48:04.622: 55623486: ../libfprint/drivers/elan.c:691 167s (process:2211): libfprint-elan-DEBUG: 16:48:04.622: calibration status: 0x03 167s (process:2211): libfprint-SSM-DEBUG: 16:48:04.622: [elan] CALIBRATE_NUM_STATES entering state 0 167s (process:2211): libfprint-elan-DEBUG: 16:48:04.622: 55623497: ../libfprint/drivers/elan.c:691 167s (process:2211): libfprint-elan-DEBUG: 16:48:04.623: 55624128: ../libfprint/drivers/elan.c:346 167s (process:2211): libfprint-elan-DEBUG: 16:48:04.623: 55624141: ../libfprint/drivers/elan.c:366 167s (process:2211): libfprint-elan-DEBUG: 16:48:04.623: 55624144: ../libfprint/drivers/elan.c:379 167s (process:2211): libfprint-elan-DEBUG: 16:48:04.624: 55624736: ../libfprint/drivers/elan.c:346 167s (process:2211): libfprint-elan-DEBUG: 16:48:04.624: 55624855: ../libfprint/drivers/elan.c:335 167s (process:2211): libfprint-SSM-DEBUG: 16:48:04.624: [elan] CALIBRATE_NUM_STATES entering state 1 167s (process:2211): libfprint-elan-DEBUG: 16:48:04.624: 55624895: ../libfprint/drivers/elan.c:691 167s (process:2211): libfprint-elan-DEBUG: 16:48:04.624: 55624899: ../libfprint/drivers/elan.c:156 167s (process:2211): libfprint-elan-DEBUG: 16:48:04.624: 55624902: ../libfprint/drivers/elan.c:118 167s (process:2211): libfprint-SSM-DEBUG: 16:48:04.624: [elan] CALIBRATE_NUM_STATES entering state 2 167s (process:2211): libfprint-elan-DEBUG: 16:48:04.624: 55624915: ../libfprint/drivers/elan.c:691 167s (process:2211): libfprint-elan-DEBUG: 16:48:04.624: 55625527: ../libfprint/drivers/elan.c:346 167s (process:2211): libfprint-elan-DEBUG: 16:48:04.624: 55625641: ../libfprint/drivers/elan.c:366 167s (process:2211): libfprint-elan-DEBUG: 16:48:04.624: 55625658: ../libfprint/drivers/elan.c:379 167s (process:2211): libfprint-elan-DEBUG: 16:48:04.625: 55626286: ../libfprint/drivers/elan.c:346 167s (process:2211): libfprint-elan-DEBUG: 16:48:04.625: 55626299: ../libfprint/drivers/elan.c:335 167s (process:2211): libfprint-SSM-DEBUG: 16:48:04.625: [elan] CALIBRATE_NUM_STATES entering state 3 167s (process:2211): libfprint-elan-DEBUG: 16:48:04.625: 55626306: ../libfprint/drivers/elan.c:691 167s (process:2211): libfprint-elan-DEBUG: 16:48:04.625: 55626309: ../libfprint/drivers/elan.c:634 167s (process:2211): libfprint-elan-DEBUG: 16:48:04.625: calibration mean: 8339, bg mean: 8146, delta: 193 167s (process:2211): libfprint-SSM-DEBUG: 16:48:04.625: [elan] CALIBRATE_NUM_STATES completed successfully 167s (process:2211): libfprint-elan-DEBUG: 16:48:04.625: 55626328: ../libfprint/drivers/elan.c:776 167s (process:2211): libfprint-elan-DEBUG: 16:48:04.625: 55626330: ../libfprint/drivers/elan.c:620 167s (process:2211): libfprint-elan-DEBUG: 16:48:04.625: 55626333: ../libfprint/drivers/elan.c:100 167s (process:2211): libfprint-SSM-DEBUG: 16:48:04.625: [elan] CAPTURE_NUM_STATES entering state 0 167s (process:2211): libfprint-elan-DEBUG: 16:48:04.626: 55626858: ../libfprint/drivers/elan.c:346 167s (process:2211): libfprint-elan-DEBUG: 16:48:04.626: 55626870: ../libfprint/drivers/elan.c:366 167s (process:2211): libfprint-elan-DEBUG: 16:48:04.626: 55626873: ../libfprint/drivers/elan.c:379 167s (process:2211): libfprint-elan-DEBUG: 16:48:04.626: skipping read, not expecting anything 167s (process:2211): libfprint-elan-DEBUG: 16:48:04.626: 55626878: ../libfprint/drivers/elan.c:335 167s (process:2211): libfprint-SSM-DEBUG: 16:48:04.626: [elan] CAPTURE_NUM_STATES entering state 1 167s (process:2211): libfprint-elan-DEBUG: 16:48:04.626: 55627430: ../libfprint/drivers/elan.c:346 167s (process:2211): libfprint-elan-DEBUG: 16:48:04.626: 55627443: ../libfprint/drivers/elan.c:366 167s (process:2211): libfprint-elan-DEBUG: 16:48:04.626: 55627446: ../libfprint/drivers/elan.c:379 167s (process:2211): libfprint-elan-DEBUG: 16:48:04.627: 55627992: ../libfprint/drivers/elan.c:346 167s (process:2211): libfprint-elan-DEBUG: 16:48:04.627: 55628147: ../libfprint/drivers/elan.c:335 167s (process:2211): libfprint-SSM-DEBUG: 16:48:04.627: [elan] CAPTURE_NUM_STATES entering state 2 167s (process:2211): libfprint-device-DEBUG: 16:48:04.627: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 167s (process:2211): libfprint-image_device-DEBUG: 16:48:04.627: Image device reported finger status: on 167s (process:2211): libfprint-image_device-DEBUG: 16:48:04.627: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 167s (process:2211): libfprint-elan-DEBUG: 16:48:04.627: 55628384: ../libfprint/drivers/elan.c:960 167s (process:2211): libfprint-elan-DEBUG: 16:48:04.628: 55628912: ../libfprint/drivers/elan.c:346 167s (process:2211): libfprint-elan-DEBUG: 16:48:04.628: 55628924: ../libfprint/drivers/elan.c:366 167s (process:2211): libfprint-elan-DEBUG: 16:48:04.628: 55628927: ../libfprint/drivers/elan.c:379 167s (process:2211): libfprint-elan-DEBUG: 16:48:04.628: 55629502: ../libfprint/drivers/elan.c:346 167s (process:2211): libfprint-elan-DEBUG: 16:48:04.628: 55629516: ../libfprint/drivers/elan.c:335 167s (process:2211): libfprint-SSM-DEBUG: 16:48:04.628: [elan] CAPTURE_NUM_STATES entering state 3 167s (process:2211): libfprint-elan-DEBUG: 16:48:04.628: 55629524: ../libfprint/drivers/elan.c:203 167s (process:2211): libfprint-elan-DEBUG: 16:48:04.628: 55629536: ../libfprint/drivers/elan.c:118 167s (process:2211): libfprint-SSM-DEBUG: 16:48:04.628: [elan] CAPTURE_NUM_STATES entering state 1 167s (process:2211): libfprint-elan-DEBUG: 16:48:04.629: 55630115: ../libfprint/drivers/elan.c:346 167s (process:2211): libfprint-elan-DEBUG: 16:48:04.629: 55630128: ../libfprint/drivers/elan.c:366 167s (process:2211): libfprint-elan-DEBUG: 16:48:04.629: 55630131: ../libfprint/drivers/elan.c:379 167s (process:2211): libfprint-elan-DEBUG: 16:48:04.629: 55630683: ../libfprint/drivers/elan.c:346 167s (process:2211): libfprint-elan-DEBUG: 16:48:04.630: 55630696: ../libfprint/drivers/elan.c:335 167s (process:2211): libfprint-SSM-DEBUG: 16:48:04.630: [elan] CAPTURE_NUM_STATES entering state 2 167s (process:2211): libfprint-image_device-DEBUG: 16:48:04.630: Image device reported finger status: on 167s (process:2211): libfprint-elan-DEBUG: 16:48:04.630: 55631235: ../libfprint/drivers/elan.c:346 167s (process:2211): libfprint-elan-DEBUG: 16:48:04.630: 55631248: ../libfprint/drivers/elan.c:366 167s (process:2211): libfprint-elan-DEBUG: 16:48:04.630: 55631251: ../libfprint/drivers/elan.c:379 167s (process:2211): libfprint-elan-DEBUG: 16:48:04.631: 55631887: ../libfprint/drivers/elan.c:346 167s (process:2211): libfprint-elan-DEBUG: 16:48:04.631: 55632079: ../libfprint/drivers/elan.c:335 167s (process:2211): libfprint-SSM-DEBUG: 16:48:04.631: [elan] CAPTURE_NUM_STATES entering state 3 167s (process:2211): libfprint-elan-DEBUG: 16:48:04.631: 55632172: ../libfprint/drivers/elan.c:203 167s (process:2211): libfprint-elan-DEBUG: 16:48:04.631: 55632186: ../libfprint/drivers/elan.c:118 167s (process:2211): libfprint-SSM-DEBUG: 16:48:04.631: [elan] CAPTURE_NUM_STATES entering state 1 167s (process:2211): libfprint-elan-DEBUG: 16:48:04.632: 55632756: ../libfprint/drivers/elan.c:346 167s (process:2211): libfprint-elan-DEBUG: 16:48:04.632: 55632767: ../libfprint/drivers/elan.c:366 167s (process:2211): libfprint-elan-DEBUG: 16:48:04.632: 55632770: ../libfprint/drivers/elan.c:379 167s (process:2211): libfprint-elan-DEBUG: 16:48:04.632: 55633334: ../libfprint/drivers/elan.c:346 167s (process:2211): libfprint-elan-DEBUG: 16:48:04.632: 55633452: ../libfprint/drivers/elan.c:335 167s (process:2211): libfprint-SSM-DEBUG: 16:48:04.632: [elan] CAPTURE_NUM_STATES entering state 2 167s (process:2211): libfprint-image_device-DEBUG: 16:48:04.632: Image device reported finger status: on 167s (process:2211): libfprint-elan-DEBUG: 16:48:04.633: 55634101: ../libfprint/drivers/elan.c:346 167s (process:2211): libfprint-elan-DEBUG: 16:48:04.633: 55634114: ../libfprint/drivers/elan.c:366 167s (process:2211): libfprint-elan-DEBUG: 16:48:04.633: 55634117: ../libfprint/drivers/elan.c:379 167s (process:2211): libfprint-elan-DEBUG: 16:48:04.634: 55634749: ../libfprint/drivers/elan.c:346 167s (process:2211): libfprint-elan-DEBUG: 16:48:04.634: 55634825: ../libfprint/drivers/elan.c:335 167s (process:2211): libfprint-SSM-DEBUG: 16:48:04.634: [elan] CAPTURE_NUM_STATES entering state 3 167s (process:2211): libfprint-elan-DEBUG: 16:48:04.634: 55634848: ../libfprint/drivers/elan.c:203 167s (process:2211): libfprint-elan-DEBUG: 16:48:04.634: 55634856: ../libfprint/drivers/elan.c:118 167s (process:2211): libfprint-SSM-DEBUG: 16:48:04.634: [elan] CAPTURE_NUM_STATES entering state 1 167s (process:2211): libfprint-elan-DEBUG: 16:48:04.634: 55635567: ../libfprint/drivers/elan.c:346 167s (process:2211): libfprint-elan-DEBUG: 16:48:04.634: 55635580: ../libfprint/drivers/elan.c:366 167s (process:2211): libfprint-elan-DEBUG: 16:48:04.634: 55635583: ../libfprint/drivers/elan.c:379 167s (process:2211): libfprint-elan-DEBUG: 16:48:04.635: 55636138: ../libfprint/drivers/elan.c:346 167s (process:2211): libfprint-elan-DEBUG: 16:48:04.635: 55636181: ../libfprint/drivers/elan.c:335 167s (process:2211): libfprint-SSM-DEBUG: 16:48:04.635: [elan] CAPTURE_NUM_STATES entering state 2 167s (process:2211): libfprint-image_device-DEBUG: 16:48:04.635: Image device reported finger status: on 167s (process:2211): libfprint-elan-DEBUG: 16:48:04.635: 55636642: ../libfprint/drivers/elan.c:346 167s (process:2211): libfprint-elan-DEBUG: 16:48:04.635: 55636652: ../libfprint/drivers/elan.c:366 167s (process:2211): libfprint-elan-DEBUG: 16:48:04.635: 55636664: ../libfprint/drivers/elan.c:379 167s (process:2211): libfprint-elan-DEBUG: 16:48:04.636: 55637158: ../libfprint/drivers/elan.c:346 167s (process:2211): libfprint-elan-DEBUG: 16:48:04.636: 55637171: ../libfprint/drivers/elan.c:335 167s (process:2211): libfprint-SSM-DEBUG: 16:48:04.636: [elan] CAPTURE_NUM_STATES entering state 3 167s (process:2211): libfprint-elan-DEBUG: 16:48:04.636: 55637186: ../libfprint/drivers/elan.c:203 167s (process:2211): libfprint-elan-DEBUG: 16:48:04.636: 55637195: ../libfprint/drivers/elan.c:118 167s (process:2211): libfprint-SSM-DEBUG: 16:48:04.636: [elan] CAPTURE_NUM_STATES entering state 1 167s (process:2211): libfprint-elan-DEBUG: 16:48:04.637: 55637697: ../libfprint/drivers/elan.c:346 167s (process:2211): libfprint-elan-DEBUG: 16:48:04.637: 55637708: ../libfprint/drivers/elan.c:366 167s (process:2211): libfprint-elan-DEBUG: 16:48:04.637: 55637718: ../libfprint/drivers/elan.c:379 167s (process:2211): libfprint-elan-DEBUG: 16:48:04.637: 55638245: ../libfprint/drivers/elan.c:346 167s (process:2211): libfprint-elan-DEBUG: 16:48:04.637: 55638262: ../libfprint/drivers/elan.c:335 167s (process:2211): libfprint-SSM-DEBUG: 16:48:04.637: [elan] CAPTURE_NUM_STATES entering state 2 167s (process:2211): libfprint-image_device-DEBUG: 16:48:04.637: Image device reported finger status: on 167s (process:2211): libfprint-elan-DEBUG: 16:48:04.638: 55638737: ../libfprint/drivers/elan.c:346 167s (process:2211): libfprint-elan-DEBUG: 16:48:04.638: 55638751: ../libfprint/drivers/elan.c:366 167s (process:2211): libfprint-elan-DEBUG: 16:48:04.638: 55638755: ../libfprint/drivers/elan.c:379 167s (process:2211): libfprint-elan-DEBUG: 16:48:04.638: 55639284: ../libfprint/drivers/elan.c:346 167s (process:2211): libfprint-elan-DEBUG: 16:48:04.638: 55639297: ../libfprint/drivers/elan.c:335 167s (process:2211): libfprint-SSM-DEBUG: 16:48:04.638: [elan] CAPTURE_NUM_STATES entering state 3 167s (process:2211): libfprint-elan-DEBUG: 16:48:04.638: 55639312: ../libfprint/drivers/elan.c:203 167s (process:2211): libfprint-elan-DEBUG: 16:48:04.638: 55639320: ../libfprint/drivers/elan.c:118 167s (process:2211): libfprint-SSM-DEBUG: 16:48:04.638: [elan] CAPTURE_NUM_STATES entering state 1 167s (process:2211): libfprint-elan-DEBUG: 16:48:04.639: 55639810: ../libfprint/drivers/elan.c:346 167s (process:2211): libfprint-elan-DEBUG: 16:48:04.639: 55639827: ../libfprint/drivers/elan.c:366 167s (process:2211): libfprint-elan-DEBUG: 16:48:04.639: 55639831: ../libfprint/drivers/elan.c:379 167s (process:2211): libfprint-elan-DEBUG: 16:48:04.639: 55640358: ../libfprint/drivers/elan.c:346 167s (process:2211): libfprint-elan-DEBUG: 16:48:04.639: 55640376: ../libfprint/drivers/elan.c:335 167s (process:2211): libfprint-SSM-DEBUG: 16:48:04.639: [elan] CAPTURE_NUM_STATES entering state 2 167s (process:2211): libfprint-image_device-DEBUG: 16:48:04.639: Image device reported finger status: on 167s (process:2211): libfprint-elan-DEBUG: 16:48:04.640: 55640934: ../libfprint/drivers/elan.c:346 167s (process:2211): libfprint-elan-DEBUG: 16:48:04.640: 55640945: ../libfprint/drivers/elan.c:366 167s (process:2211): libfprint-elan-DEBUG: 16:48:04.640: 55640957: ../libfprint/drivers/elan.c:379 167s (process:2211): libfprint-elan-DEBUG: 16:48:04.640: 55641469: ../libfprint/drivers/elan.c:346 167s (process:2211): libfprint-elan-DEBUG: 16:48:04.640: 55641486: ../libfprint/drivers/elan.c:335 167s (process:2211): libfprint-SSM-DEBUG: 16:48:04.640: [elan] CAPTURE_NUM_STATES entering state 3 167s (process:2211): libfprint-elan-DEBUG: 16:48:04.640: 55641494: ../libfprint/drivers/elan.c:203 167s (process:2211): libfprint-elan-DEBUG: 16:48:04.640: 55641502: ../libfprint/drivers/elan.c:118 167s (process:2211): libfprint-SSM-DEBUG: 16:48:04.640: [elan] CAPTURE_NUM_STATES entering state 1 167s (process:2211): libfprint-elan-DEBUG: 16:48:04.641: 55642038: ../libfprint/drivers/elan.c:346 167s (process:2211): libfprint-elan-DEBUG: 16:48:04.641: 55642056: ../libfprint/drivers/elan.c:366 167s (process:2211): libfprint-elan-DEBUG: 16:48:04.641: 55642061: ../libfprint/drivers/elan.c:379 167s (process:2211): libfprint-elan-DEBUG: 16:48:04.641: 55642546: ../libfprint/drivers/elan.c:346 167s (process:2211): libfprint-elan-DEBUG: 16:48:04.641: 55642558: ../libfprint/drivers/elan.c:335 167s (process:2211): libfprint-SSM-DEBUG: 16:48:04.641: [elan] CAPTURE_NUM_STATES entering state 2 167s (process:2211): libfprint-image_device-DEBUG: 16:48:04.641: Image device reported finger status: on 167s (process:2211): libfprint-elan-DEBUG: 16:48:04.642: 55643034: ../libfprint/drivers/elan.c:346 167s (process:2211): libfprint-elan-DEBUG: 16:48:04.642: 55643048: ../libfprint/drivers/elan.c:366 167s (process:2211): libfprint-elan-DEBUG: 16:48:04.642: 55643052: ../libfprint/drivers/elan.c:379 167s (process:2211): libfprint-elan-DEBUG: 16:48:04.642: 55643582: ../libfprint/drivers/elan.c:346 167s (process:2211): libfprint-elan-DEBUG: 16:48:04.642: 55643601: ../libfprint/drivers/elan.c:335 167s (process:2211): libfprint-SSM-DEBUG: 16:48:04.642: [elan] CAPTURE_NUM_STATES entering state 3 167s (process:2211): libfprint-elan-DEBUG: 16:48:04.642: 55643610: ../libfprint/drivers/elan.c:203 167s (process:2211): libfprint-elan-DEBUG: 16:48:04.642: 55643618: ../libfprint/drivers/elan.c:118 167s (process:2211): libfprint-SSM-DEBUG: 16:48:04.642: [elan] CAPTURE_NUM_STATES entering state 1 167s (process:2211): libfprint-elan-DEBUG: 16:48:04.643: 55644125: ../libfprint/drivers/elan.c:346 167s (process:2211): libfprint-elan-DEBUG: 16:48:04.643: 55644145: ../libfprint/drivers/elan.c:366 167s (process:2211): libfprint-elan-DEBUG: 16:48:04.643: 55644151: ../libfprint/drivers/elan.c:379 167s (process:2211): libfprint-elan-DEBUG: 16:48:04.643: 55644635: ../libfprint/drivers/elan.c:346 167s (process:2211): libfprint-elan-DEBUG: 16:48:04.643: 55644645: ../libfprint/drivers/elan.c:335 167s (process:2211): libfprint-SSM-DEBUG: 16:48:04.643: [elan] CAPTURE_NUM_STATES entering state 2 167s (process:2211): libfprint-image_device-DEBUG: 16:48:04.643: Image device reported finger status: on 167s (process:2211): libfprint-elan-DEBUG: 16:48:04.644: 55645089: ../libfprint/drivers/elan.c:346 167s (process:2211): libfprint-elan-DEBUG: 16:48:04.644: 55645099: ../libfprint/drivers/elan.c:366 167s (process:2211): libfprint-elan-DEBUG: 16:48:04.644: 55645109: ../libfprint/drivers/elan.c:379 167s (process:2211): libfprint-elan-DEBUG: 16:48:04.644: 55645600: ../libfprint/drivers/elan.c:346 167s (process:2211): libfprint-elan-DEBUG: 16:48:04.644: 55645614: ../libfprint/drivers/elan.c:335 167s (process:2211): libfprint-SSM-DEBUG: 16:48:04.644: [elan] CAPTURE_NUM_STATES entering state 3 167s (process:2211): libfprint-elan-DEBUG: 16:48:04.644: 55645628: ../libfprint/drivers/elan.c:203 167s (process:2211): libfprint-elan-DEBUG: 16:48:04.644: 55645639: ../libfprint/drivers/elan.c:118 167s (process:2211): libfprint-SSM-DEBUG: 16:48:04.644: [elan] CAPTURE_NUM_STATES entering state 1 167s (process:2211): libfprint-elan-DEBUG: 16:48:04.645: 55646128: ../libfprint/drivers/elan.c:346 167s (process:2211): libfprint-elan-DEBUG: 16:48:04.645: 55646145: ../libfprint/drivers/elan.c:366 167s (process:2211): libfprint-elan-DEBUG: 16:48:04.645: 55646150: ../libfprint/drivers/elan.c:379 167s (process:2211): libfprint-elan-DEBUG: 16:48:04.645: 55646633: ../libfprint/drivers/elan.c:346 167s (process:2211): libfprint-elan-DEBUG: 16:48:04.645: 55646649: ../libfprint/drivers/elan.c:335 167s (process:2211): libfprint-SSM-DEBUG: 16:48:04.645: [elan] CAPTURE_NUM_STATES entering state 2 167s (process:2211): libfprint-image_device-DEBUG: 16:48:04.645: Image device reported finger status: on 167s (process:2211): libfprint-elan-DEBUG: 16:48:04.646: 55647111: ../libfprint/drivers/elan.c:346 167s (process:2211): libfprint-elan-DEBUG: 16:48:04.646: 55647121: ../libfprint/drivers/elan.c:366 167s (process:2211): libfprint-elan-DEBUG: 16:48:04.646: 55647130: ../libfprint/drivers/elan.c:379 167s (process:2211): libfprint-elan-DEBUG: 16:48:04.647: 55647731: ../libfprint/drivers/elan.c:346 167s (process:2211): libfprint-elan-DEBUG: 16:48:04.647: 55647748: ../libfprint/drivers/elan.c:335 167s (process:2211): libfprint-SSM-DEBUG: 16:48:04.647: [elan] CAPTURE_NUM_STATES entering state 3 167s (process:2211): libfprint-elan-DEBUG: 16:48:04.647: 55647755: ../libfprint/drivers/elan.c:203 167s (process:2211): libfprint-elan-DEBUG: 16:48:04.647: 55647772: ../libfprint/drivers/elan.c:118 167s (process:2211): libfprint-SSM-DEBUG: 16:48:04.647: [elan] CAPTURE_NUM_STATES entering state 1 167s (process:2211): libfprint-elan-DEBUG: 16:48:04.647: 55648252: ../libfprint/drivers/elan.c:346 167s (process:2211): libfprint-elan-DEBUG: 16:48:04.647: 55648266: ../libfprint/drivers/elan.c:366 167s (process:2211): libfprint-elan-DEBUG: 16:48:04.647: 55648270: ../libfprint/drivers/elan.c:379 167s (process:2211): libfprint-elan-DEBUG: 16:48:04.648: 55648795: ../libfprint/drivers/elan.c:346 167s (process:2211): libfprint-elan-DEBUG: 16:48:04.648: 55648809: ../libfprint/drivers/elan.c:335 167s (process:2211): libfprint-SSM-DEBUG: 16:48:04.648: [elan] CAPTURE_NUM_STATES entering state 2 167s (process:2211): libfprint-image_device-DEBUG: 16:48:04.648: Image device reported finger status: on 167s (process:2211): libfprint-elan-DEBUG: 16:48:04.648: 55649257: ../libfprint/drivers/elan.c:346 167s (process:2211): libfprint-elan-DEBUG: 16:48:04.648: 55649272: ../libfprint/drivers/elan.c:366 167s (process:2211): libfprint-elan-DEBUG: 16:48:04.648: 55649276: ../libfprint/drivers/elan.c:379 167s (process:2211): libfprint-elan-DEBUG: 16:48:04.649: 55649771: ../libfprint/drivers/elan.c:346 167s (process:2211): libfprint-elan-DEBUG: 16:48:04.649: 55649782: ../libfprint/drivers/elan.c:335 167s (process:2211): libfprint-SSM-DEBUG: 16:48:04.649: [elan] CAPTURE_NUM_STATES entering state 3 167s (process:2211): libfprint-elan-DEBUG: 16:48:04.649: 55649796: ../libfprint/drivers/elan.c:203 167s (process:2211): libfprint-elan-DEBUG: 16:48:04.649: 55649803: ../libfprint/drivers/elan.c:118 167s (process:2211): libfprint-SSM-DEBUG: 16:48:04.649: [elan] CAPTURE_NUM_STATES entering state 1 167s (process:2211): libfprint-elan-DEBUG: 16:48:04.649: 55650292: ../libfprint/drivers/elan.c:346 167s (process:2211): libfprint-elan-DEBUG: 16:48:04.649: 55650308: ../libfprint/drivers/elan.c:366 167s (process:2211): libfprint-elan-DEBUG: 16:48:04.649: 55650314: ../libfprint/drivers/elan.c:379 167s (process:2211): libfprint-elan-DEBUG: 16:48:04.650: 55650780: ../libfprint/drivers/elan.c:346 167s (process:2211): libfprint-elan-DEBUG: 16:48:04.650: 55650794: ../libfprint/drivers/elan.c:335 167s (process:2211): libfprint-SSM-DEBUG: 16:48:04.650: [elan] CAPTURE_NUM_STATES entering state 2 167s (process:2211): libfprint-image_device-DEBUG: 16:48:04.650: Image device reported finger status: on 167s (process:2211): libfprint-elan-DEBUG: 16:48:04.650: 55651261: ../libfprint/drivers/elan.c:346 167s (process:2211): libfprint-elan-DEBUG: 16:48:04.650: 55651273: ../libfprint/drivers/elan.c:366 167s (process:2211): libfprint-elan-DEBUG: 16:48:04.650: 55651277: ../libfprint/drivers/elan.c:379 167s (process:2211): libfprint-elan-DEBUG: 16:48:04.651: 55651827: ../libfprint/drivers/elan.c:346 167s (process:2211): libfprint-elan-DEBUG: 16:48:04.651: 55651839: ../libfprint/drivers/elan.c:335 167s (process:2211): libfprint-SSM-DEBUG: 16:48:04.651: [elan] CAPTURE_NUM_STATES entering state 3 167s (process:2211): libfprint-elan-DEBUG: 16:48:04.651: 55651855: ../libfprint/drivers/elan.c:203 167s (process:2211): libfprint-elan-DEBUG: 16:48:04.651: 55651862: ../libfprint/drivers/elan.c:118 167s (process:2211): libfprint-SSM-DEBUG: 16:48:04.651: [elan] CAPTURE_NUM_STATES entering state 1 167s (process:2211): libfprint-elan-DEBUG: 16:48:04.651: 55652413: ../libfprint/drivers/elan.c:346 167s (process:2211): libfprint-elan-DEBUG: 16:48:04.651: 55652428: ../libfprint/drivers/elan.c:366 167s (process:2211): libfprint-elan-DEBUG: 16:48:04.651: 55652432: ../libfprint/drivers/elan.c:379 167s (process:2211): libfprint-elan-DEBUG: 16:48:04.652: 55652904: ../libfprint/drivers/elan.c:346 167s (process:2211): libfprint-elan-DEBUG: 16:48:04.652: 55652917: ../libfprint/drivers/elan.c:335 167s (process:2211): libfprint-SSM-DEBUG: 16:48:04.652: [elan] CAPTURE_NUM_STATES entering state 2 167s (process:2211): libfprint-image_device-DEBUG: 16:48:04.652: Image device reported finger status: on 167s (process:2211): libfprint-elan-DEBUG: 16:48:04.652: 55653413: ../libfprint/drivers/elan.c:346 167s (process:2211): libfprint-elan-DEBUG: 16:48:04.652: 55653423: ../libfprint/drivers/elan.c:366 167s (process:2211): libfprint-elan-DEBUG: 16:48:04.652: 55653431: ../libfprint/drivers/elan.c:379 167s (process:2211): libfprint-elan-DEBUG: 16:48:04.653: 55653923: ../libfprint/drivers/elan.c:346 167s (process:2211): libfprint-elan-DEBUG: 16:48:04.653: 55653939: ../libfprint/drivers/elan.c:335 167s (process:2211): libfprint-SSM-DEBUG: 16:48:04.653: [elan] CAPTURE_NUM_STATES entering state 3 167s (process:2211): libfprint-elan-DEBUG: 16:48:04.653: 55653946: ../libfprint/drivers/elan.c:203 167s (process:2211): libfprint-elan-DEBUG: 16:48:04.653: 55653955: ../libfprint/drivers/elan.c:118 167s (process:2211): libfprint-SSM-DEBUG: 16:48:04.653: [elan] CAPTURE_NUM_STATES entering state 1 167s (process:2211): libfprint-elan-DEBUG: 16:48:04.653: 55654455: ../libfprint/drivers/elan.c:346 167s (process:2211): libfprint-elan-DEBUG: 16:48:04.653: 55654466: ../libfprint/drivers/elan.c:366 167s (process:2211): libfprint-elan-DEBUG: 16:48:04.653: 55654475: ../libfprint/drivers/elan.c:379 167s (process:2211): libfprint-elan-DEBUG: 16:48:04.654: 55654953: ../libfprint/drivers/elan.c:346 167s (process:2211): libfprint-elan-DEBUG: 16:48:04.654: 55654963: ../libfprint/drivers/elan.c:335 167s (process:2211): libfprint-SSM-DEBUG: 16:48:04.654: [elan] CAPTURE_NUM_STATES entering state 2 167s (process:2211): libfprint-SSM-DEBUG: 16:48:04.654: [elan] CAPTURE_NUM_STATES completed successfully 167s (process:2211): libfprint-elan-DEBUG: 16:48:04.654: 55654987: ../libfprint/drivers/elan.c:586 167s (process:2211): libfprint-elan-DEBUG: 16:48:04.654: 55654990: ../libfprint/drivers/elan.c:315 167s (process:2211): libfprint-elan-DEBUG: 16:48:04.654: 55654996: ../libfprint/drivers/elan.c:272 167s (process:2211): libfprint-elan-DEBUG: 16:48:04.655: 55655766: ../libfprint/drivers/elan.c:272 167s (process:2211): libfprint-elan-DEBUG: 16:48:04.655: 55656538: ../libfprint/drivers/elan.c:272 167s (process:2211): libfprint-elan-DEBUG: 16:48:04.656: 55657278: ../libfprint/drivers/elan.c:272 167s (process:2211): libfprint-elan-DEBUG: 16:48:04.657: 55658016: ../libfprint/drivers/elan.c:272 167s (process:2211): libfprint-elan-DEBUG: 16:48:04.658: 55658753: ../libfprint/drivers/elan.c:272 167s (process:2211): libfprint-elan-DEBUG: 16:48:04.658: 55659513: ../libfprint/drivers/elan.c:272 167s (process:2211): libfprint-elan-DEBUG: 16:48:04.659: 55660273: ../libfprint/drivers/elan.c:272 167s (process:2211): libfprint-elan-DEBUG: 16:48:04.660: 55661007: ../libfprint/drivers/elan.c:272 167s (process:2211): libfprint-elan-DEBUG: 16:48:04.661: 55661748: ../libfprint/drivers/elan.c:272 167s (process:2211): libfprint-assembling-DEBUG: 16:48:04.811: calc delta completed in 0.150035 secs 167s (process:2211): libfprint-assembling-DEBUG: 16:48:04.960: calc delta completed in 0.149023 secs 167s (process:2211): libfprint-assembling-DEBUG: 16:48:04.960: errors: 233151 rev: 207411 167s (process:2211): libfprint-assembling-DEBUG: 16:48:04.960: height is -185 167s (process:2211): libfprint-image_device-DEBUG: 16:48:04.961: Image device captured an image 167s (process:2211): libfprint-image_device-DEBUG: 16:48:04.961: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 167s (process:2211): libfprint-elan-DEBUG: 16:48:04.961: 55962083: ../libfprint/drivers/elan.c:960 167s (process:2211): libfprint-device-DEBUG: 16:48:04.961: Device reported finger status change: FP_FINGER_STATUS_PRESENT 167s (process:2211): libfprint-elan-DEBUG: 16:48:04.961: 55962096: ../libfprint/drivers/elan.c:507 167s (process:2211): libfprint-elan-DEBUG: 16:48:04.961: 55962099: ../libfprint/drivers/elan.c:100 167s (process:2211): libfprint-SSM-DEBUG: 16:48:04.961: [elan] STOP_CAPTURE_NUM_STATES entering state 0 167s (process:2211): libfprint-elan-DEBUG: 16:48:04.961: 55962130: ../libfprint/drivers/elan.c:466 167s (process:2211): libfprint-elan-DEBUG: 16:48:04.963: 55964577: ../libfprint/drivers/elan.c:346 167s (process:2211): libfprint-elan-DEBUG: 16:48:04.963: 55964594: ../libfprint/drivers/elan.c:366 167s (process:2211): libfprint-elan-DEBUG: 16:48:04.963: 55964598: ../libfprint/drivers/elan.c:379 167s (process:2211): libfprint-elan-DEBUG: 16:48:04.963: skipping read, not expecting anything 167s (process:2211): libfprint-elan-DEBUG: 16:48:04.963: 55964604: ../libfprint/drivers/elan.c:335 167s (process:2211): libfprint-SSM-DEBUG: 16:48:04.963: [elan] STOP_CAPTURE_NUM_STATES completed successfully 167s (process:2211): libfprint-elan-DEBUG: 16:48:04.963: 55964611: ../libfprint/drivers/elan.c:483 167s (process:2211): libfprint-device-DEBUG: 16:48:04.963: Device reported finger status change: FP_FINGER_STATUS_NONE 167s (process:2211): libfprint-image_device-DEBUG: 16:48:04.963: Image device reported finger status: off 167s (process:2211): libfprint-image_device-DEBUG: 16:48:04.963: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 167s (process:2211): libfprint-elan-DEBUG: 16:48:04.963: 55964632: ../libfprint/drivers/elan.c:960 167s (process:2211): libfprint-image_device-DEBUG: 16:48:04.963: Deactivating image device 167s (process:2211): libfprint-image_device-DEBUG: 16:48:04.963: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_DEACTIVATING 167s (process:2211): libfprint-elan-DEBUG: 16:48:04.963: 55964642: ../libfprint/drivers/elan.c:960 167s (process:2211): libfprint-elan-DEBUG: 16:48:04.963: 55964645: ../libfprint/drivers/elan.c:975 167s (process:2211): libfprint-image_device-DEBUG: 16:48:04.963: Image device deactivation completed 167s (process:2211): libfprint-image_device-DEBUG: 16:48:04.963: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE 167s (process:2211): libfprint-elan-DEBUG: 16:48:04.963: 55964658: ../libfprint/drivers/elan.c:960 167s (process:2211): libfprint-image-DEBUG: 16:48:04.985: Minutiae scan completed in 0.023614 secs 167s (process:2211): libfprint-device-DEBUG: 16:48:04.985: Device reported capture completion 167s (process:2211): libfprint-device-DEBUG: 16:48:04.985: Completing action FPI_DEVICE_ACTION_CAPTURE in idle! 167s (process:2211): libfprint-device-DEBUG: 16:48:04.985: Updated temperature model after 0.53 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 167s (process:2211): libfprint-elan-DEBUG: 16:48:04.985: 55986079: ../libfprint/drivers/elan.c:939 167s (process:2211): libfprint-elan-DEBUG: 16:48:04.985: 55986093: ../libfprint/drivers/elan.c:100 167s (process:2211): libfprint-image_device-DEBUG: 16:48:04.985: Image device close completed 167s (process:2211): libfprint-device-DEBUG: 16:48:04.985: Device reported close completion 167s (process:2211): libfprint-device-DEBUG: 16:48:04.985: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 167s (process:2211): libfprint-device-DEBUG: 16:48:04.985: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 168s ** (umockdev-run:2207): DEBUG: 16:48:05.054: umockdev.vala:150: Removing test bed /tmp/umockdev.8X97J2 168s (umockdev-run:2207): GLib-DEBUG: 16:48:05.059: unsetenv() is not thread-safe and should not be used after threads are created 168s Comparing PNGs /tmp/libfprint-umockdev-test-jywa99q8/capture.png and /usr/share/installed-tests/libfprint-2/elan/capture.png 168s PASS: libfprint-2/driver-elan.test 168s Running test: libfprint-2/fpi-ssm.test 168s TAP version 13 168s # random seed: R02S6e4f95198b6f667a02c9a9a6a4356a43 168s 1..42 168s # Start of ssm tests 168s ok 1 /ssm/new 168s ok 2 /ssm/set_data 168s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 0 168s ok 3 /ssm/start 168s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 0 168s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 1 168s ok 4 /ssm/next 168s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 0 168s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 2 168s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 1 168s ok 5 /ssm/jump_to_state 168s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 0 168s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM completed successfully 168s ok 6 /ssm/mark_completed 168s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 0 168s # 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. 168s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM completed with error: The driver encountered a protocol error with the device. 168s ok 7 /ssm/mark_failed 168s # Start of new tests 168s ok 8 /ssm/new/full 168s ok 9 /ssm/new/no_handler 168s ok 10 /ssm/new/wrong_states 168s # End of new tests 168s # Start of set_data tests 168s ok 11 /ssm/set_data/cleanup 168s # End of set_data tests 168s # Start of start tests 168s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM_SINGLE_STATE entering state 0 168s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM_SINGLE_STATE completed successfully 168s ok 12 /ssm/start/single 168s # End of start tests 168s # Start of next tests 168s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 0 168s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 1 168s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 2 168s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 3 168s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM completed successfully 168s ok 13 /ssm/next/complete 168s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 1 168s ok 14 /ssm/next/not_started 168s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 0 168s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 1 168s ok 15 /ssm/next/with_delayed 168s # End of next tests 168s # Start of jump_to_state tests 168s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 2 168s ok 16 /ssm/jump_to_state/not_started 168s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 0 168s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 2 168s ok 17 /ssm/jump_to_state/with_delayed 168s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 0 168s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 3 168s ok 18 /ssm/jump_to_state/last 168s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 0 168s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 14 168s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state -10 168s ok 19 /ssm/jump_to_state/wrong 168s # End of jump_to_state tests 168s # Start of mark_completed tests 168s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM completed successfully 168s ok 20 /ssm/mark_completed/not_started 168s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 0 168s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM completed successfully 168s ok 21 /ssm/mark_completed/with_delayed 168s # End of mark_completed tests 168s # Start of mark_failed tests 168s # 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. 168s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM completed with error: The driver encountered a protocol error with the device. 168s ok 22 /ssm/mark_failed/not_started 168s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 0 168s # 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. 168s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM completed with error: The driver encountered a protocol error with the device. 168s ok 23 /ssm/mark_failed/with_delayed 168s # End of mark_failed tests 168s # Start of delayed tests 168s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 0 168s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 1 168s ok 24 /ssm/delayed/next 168s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 0 168s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 2 168s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 1 168s ok 25 /ssm/delayed/jump_to_state 168s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 0 168s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM completed successfully 168s ok 26 /ssm/delayed/mark_completed 168s # Start of next tests 168s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 0 168s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM cancelled delayed state change 168s ok 27 /ssm/delayed/next/cancel 168s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 1 168s ok 28 /ssm/delayed/next/not_started 168s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 0 168s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 1 168s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 2 168s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 3 168s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM completed successfully 168s ok 29 /ssm/delayed/next/complete 168s # End of next tests 168s # Start of jump_to_state tests 168s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 0 168s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM cancelled delayed state change 168s ok 30 /ssm/delayed/jump_to_state/cancel 168s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 2 168s ok 31 /ssm/delayed/jump_to_state/not_started 168s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 0 168s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 3 168s ok 32 /ssm/delayed/jump_to_state/last 168s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 0 168s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 14 168s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state -10 168s ok 33 /ssm/delayed/jump_to_state/wrong 168s # End of jump_to_state tests 168s # Start of mark_completed tests 168s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 0 168s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM cancelled delayed state change 168s ok 34 /ssm/delayed/mark_completed/cancel 168s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM completed successfully 169s ok 35 /ssm/delayed/mark_completed/not_started 169s # End of mark_completed tests 169s # Start of cancel tests 169s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM cancelled delayed state change 169s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 0 169s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM cancelled delayed state change 169s ok 36 /ssm/delayed/cancel/error 169s # End of cancel tests 169s # End of delayed tests 169s # Start of subssm tests 169s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 0 169s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SUB_SSM entering state 0 169s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SUB_SSM entering state 1 169s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SUB_SSM completed successfully 169s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 1 169s ok 37 /ssm/subssm/start 169s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 0 169s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SUB_SSM entering state 0 169s # 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. 169s # 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. 169s # 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. 169s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM completed with error: The device is still busy with another operation, please try again later. 169s ok 38 /ssm/subssm/mark_failed 169s # Start of start tests 169s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 0 169s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SUB_SSM entering state 0 169s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SUB_SSM entering state 0 169s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SUB_SSM completed successfully 169s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 1 169s ok 39 /ssm/subssm/start/with_started 169s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 0 169s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SUB_SSM entering state 0 169s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SUB_SSM completed successfully 169s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 1 169s ok 40 /ssm/subssm/start/with_delayed 169s # End of start tests 169s # End of subssm tests 169s # Start of cleanup tests 169s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 0 169s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 2 169s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 3 169s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM completed successfully 169s ok 41 /ssm/cleanup/complete 169s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 0 169s # libfprint-SSM-DEBUG: [fake_test_dev] SSM FPI_TEST_SSM failed in state 0 with error: non-cleanup 169s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 2 169s # libfprint-SSM-DEBUG: [fake_test_dev] SSM FPI_TEST_SSM failed in state 2 (cleanup) with error: cleanup 1 169s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 3 169s # libfprint-SSM-DEBUG: [fake_test_dev] SSM FPI_TEST_SSM failed in state 3 (cleanup) with error: cleanup 2 169s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM completed with error: non-cleanup 169s ok 42 /ssm/cleanup/fail 169s # End of cleanup tests 169s # End of ssm tests 169s PASS: libfprint-2/fpi-ssm.test 169s Running test: libfprint-2/driver-elan-cobo.test 169s ** (umockdev-run:2222): DEBUG: 16:48:06.205: umockdev.vala:123: Created udev test bed /tmp/umockdev.O1YHK2 169s ** (umockdev-run:2222): DEBUG: 16:48:06.206: umockdev.vala:1297: parsing device description for /devices/pci0000:00/0000:00:14.0/usb1/1-10 169s ** (umockdev-run:2222): DEBUG: 16:48:06.206: umockdev.vala:1366: creating device /devices/pci0000:00/0000:00:14.0/usb1/1-10 (subsystem usb) 169s ** (umockdev-run:2222): DEBUG: 16:48:06.209: umockdev.vala:1411: create_node_for_device: creating file device /tmp/umockdev.O1YHK2/dev/bus/usb/001/045 169s ** (umockdev-run:2222): DEBUG: 16:48:06.209: umockdev.vala:1297: parsing device description for /devices/pci0000:00/0000:00:14.0/usb1 169s ** (umockdev-run:2222): DEBUG: 16:48:06.209: umockdev.vala:1366: creating device /devices/pci0000:00/0000:00:14.0/usb1 (subsystem usb) 169s ** (umockdev-run:2222): DEBUG: 16:48:06.211: umockdev.vala:1411: create_node_for_device: creating file device /tmp/umockdev.O1YHK2/dev/bus/usb/001/001 169s ** (umockdev-run:2222): DEBUG: 16:48:06.211: umockdev.vala:1297: parsing device description for /devices/pci0000:00/0000:00:14.0 169s ** (umockdev-run:2222): DEBUG: 16:48:06.211: umockdev.vala:1366: creating device /devices/pci0000:00/0000:00:14.0 (subsystem pci) 169s (process:2226): libfprint-context-DEBUG: 16:48:06.290: Initializing FpContext (libfprint version 1.94.7+tod1) 169s (process:2226): libfprint-tod-DEBUG: 16:48:06.291: Impossible to load the shared drivers dir Error opening directory “/usr/lib/aarch64-linux-gnu/libfprint-2/tod-1”: No such file or directory 169s (process:2226): libfprint-context-DEBUG: 16:48:06.293: No driver found for USB device 1D6B:0002 169s (process:2226): libfprint-device-DEBUG: 16:48:06.293: Device reported probe completion 169s (process:2226): libfprint-device-DEBUG: 16:48:06.293: Completing action FPI_DEVICE_ACTION_PROBE in idle! 169s (process:2226): libfprint-device-DEBUG: 16:48:06.293: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 169s (process:2226): libfprint-elan-DEBUG: 16:48:06.295: 57296635: ../libfprint/drivers/elan.c:908 169s (process:2226): libfprint-image_device-DEBUG: 16:48:06.296: Image device open completed 169s (process:2226): libfprint-device-DEBUG: 16:48:06.296: Device reported open completion 169s (process:2226): libfprint-device-DEBUG: 16:48:06.296: Completing action FPI_DEVICE_ACTION_OPEN in idle! 169s (process:2226): libfprint-device-DEBUG: 16:48:06.296: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 169s (process:2226): libfprint-device-DEBUG: 16:48:06.296: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 169s (process:2226): libfprint-image_device-DEBUG: 16:48:06.296: Activating image device 169s (process:2226): libfprint-image_device-DEBUG: 16:48:06.296: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING 169s (process:2226): libfprint-elan-DEBUG: 16:48:06.296: 57297139: ../libfprint/drivers/elan.c:960 169s (process:2226): libfprint-elan-DEBUG: 16:48:06.296: 57297143: ../libfprint/drivers/elan.c:951 169s (process:2226): libfprint-elan-DEBUG: 16:48:06.296: 57297145: ../libfprint/drivers/elan.c:892 169s (process:2226): libfprint-elan-DEBUG: 16:48:06.296: 57297148: ../libfprint/drivers/elan.c:100 169s (process:2226): libfprint-SSM-DEBUG: 16:48:06.296: [elan] ACTIVATE_NUM_STATES entering state 0 169s (process:2226): libfprint-elan-DEBUG: 16:48:06.296: 57297160: ../libfprint/drivers/elan.c:820 169s (process:2226): libfprint-elan-DEBUG: 16:48:06.297: 57297720: ../libfprint/drivers/elan.c:346 169s (process:2226): libfprint-elan-DEBUG: 16:48:06.297: 57297787: ../libfprint/drivers/elan.c:366 169s (process:2226): libfprint-elan-DEBUG: 16:48:06.297: 57297844: ../libfprint/drivers/elan.c:379 169s (process:2226): libfprint-elan-DEBUG: 16:48:06.297: 57298298: ../libfprint/drivers/elan.c:346 169s (process:2226): libfprint-elan-DEBUG: 16:48:06.297: 57298364: ../libfprint/drivers/elan.c:335 169s (process:2226): libfprint-SSM-DEBUG: 16:48:06.297: [elan] ACTIVATE_NUM_STATES entering state 1 169s (process:2226): libfprint-elan-DEBUG: 16:48:06.297: 57298477: ../libfprint/drivers/elan.c:820 169s (process:2226): libfprint-elan-DEBUG: 16:48:06.297: FW ver 0x0140 169s (process:2226): libfprint-SSM-DEBUG: 16:48:06.297: [elan] ACTIVATE_NUM_STATES entering state 2 169s (process:2226): libfprint-elan-DEBUG: 16:48:06.297: 57298532: ../libfprint/drivers/elan.c:820 169s (process:2226): libfprint-elan-DEBUG: 16:48:06.298: 57298946: ../libfprint/drivers/elan.c:346 169s (process:2226): libfprint-elan-DEBUG: 16:48:06.298: 57298966: ../libfprint/drivers/elan.c:366 169s (process:2226): libfprint-elan-DEBUG: 16:48:06.298: 57298980: ../libfprint/drivers/elan.c:379 169s (process:2226): libfprint-elan-DEBUG: 16:48:06.298: 57299402: ../libfprint/drivers/elan.c:346 169s (process:2226): libfprint-elan-DEBUG: 16:48:06.298: 57299422: ../libfprint/drivers/elan.c:335 169s (process:2226): libfprint-SSM-DEBUG: 16:48:06.298: [elan] ACTIVATE_NUM_STATES entering state 3 169s (process:2226): libfprint-elan-DEBUG: 16:48:06.298: 57299432: ../libfprint/drivers/elan.c:820 169s (process:2226): libfprint-elan-DEBUG: 16:48:06.298: sensor dimensions, WxH: 144x64 169s (process:2226): libfprint-SSM-DEBUG: 16:48:06.298: [elan] ACTIVATE_NUM_STATES entering state 4 169s (process:2226): libfprint-elan-DEBUG: 16:48:06.298: 57299441: ../libfprint/drivers/elan.c:820 169s (process:2226): libfprint-elan-DEBUG: 16:48:06.298: skipping command 0x40 0x2a for this device (for devices 0x1 but device is 0x0) 169s (process:2226): libfprint-elan-DEBUG: 16:48:06.298: 57299447: ../libfprint/drivers/elan.c:335 169s (process:2226): libfprint-SSM-DEBUG: 16:48:06.298: [elan] ACTIVATE_NUM_STATES completed successfully 169s (process:2226): libfprint-elan-DEBUG: 16:48:06.298: 57299454: ../libfprint/drivers/elan.c:881 169s (process:2226): libfprint-image_device-DEBUG: 16:48:06.298: Image device activation completed 169s (process:2226): libfprint-image_device-DEBUG: 16:48:06.298: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE 169s (process:2226): libfprint-elan-DEBUG: 16:48:06.298: 57299468: ../libfprint/drivers/elan.c:960 169s (process:2226): libfprint-image_device-DEBUG: 16:48:06.298: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 169s (process:2226): libfprint-elan-DEBUG: 16:48:06.298: 57299476: ../libfprint/drivers/elan.c:960 169s (process:2226): libfprint-elan-DEBUG: 16:48:06.298: 57299478: ../libfprint/drivers/elan.c:792 169s (process:2226): libfprint-elan-DEBUG: 16:48:06.298: 57299481: ../libfprint/drivers/elan.c:100 169s (process:2226): libfprint-SSM-DEBUG: 16:48:06.298: [elan] CALIBRATE_NUM_STATES entering state 0 169s (process:2226): libfprint-elan-DEBUG: 16:48:06.298: 57299488: ../libfprint/drivers/elan.c:691 169s (process:2226): libfprint-device-DEBUG: 16:48:06.299: Device reported finger status change: FP_FINGER_STATUS_NEEDED 169s (process:2226): libfprint-elan-DEBUG: 16:48:06.299: 57299895: ../libfprint/drivers/elan.c:346 169s (process:2226): libfprint-elan-DEBUG: 16:48:06.299: 57299905: ../libfprint/drivers/elan.c:366 169s (process:2226): libfprint-elan-DEBUG: 16:48:06.299: 57299908: ../libfprint/drivers/elan.c:379 169s (process:2226): libfprint-elan-DEBUG: 16:48:06.300: 57300788: ../libfprint/drivers/elan.c:346 169s (process:2226): libfprint-elan-DEBUG: 16:48:06.300: 57300843: ../libfprint/drivers/elan.c:335 169s (process:2226): libfprint-SSM-DEBUG: 16:48:06.300: [elan] CALIBRATE_NUM_STATES entering state 1 169s (process:2226): libfprint-elan-DEBUG: 16:48:06.300: 57300856: ../libfprint/drivers/elan.c:691 169s (process:2226): libfprint-elan-DEBUG: 16:48:06.300: 57300858: ../libfprint/drivers/elan.c:156 169s (process:2226): libfprint-elan-DEBUG: 16:48:06.300: 57300863: ../libfprint/drivers/elan.c:118 169s (process:2226): libfprint-SSM-DEBUG: 16:48:06.300: [elan] CALIBRATE_NUM_STATES entering state 2 169s (process:2226): libfprint-elan-DEBUG: 16:48:06.300: 57300878: ../libfprint/drivers/elan.c:691 169s (process:2226): libfprint-elan-DEBUG: 16:48:06.300: 57301385: ../libfprint/drivers/elan.c:346 169s (process:2226): libfprint-elan-DEBUG: 16:48:06.300: 57301450: ../libfprint/drivers/elan.c:366 169s (process:2226): libfprint-elan-DEBUG: 16:48:06.300: 57301506: ../libfprint/drivers/elan.c:379 169s (process:2226): libfprint-elan-DEBUG: 16:48:06.301: 57301945: ../libfprint/drivers/elan.c:346 169s (process:2226): libfprint-elan-DEBUG: 16:48:06.301: 57302005: ../libfprint/drivers/elan.c:335 169s (process:2226): libfprint-SSM-DEBUG: 16:48:06.301: [elan] CALIBRATE_NUM_STATES entering state 3 169s (process:2226): libfprint-elan-DEBUG: 16:48:06.301: 57302098: ../libfprint/drivers/elan.c:691 169s (process:2226): libfprint-elan-DEBUG: 16:48:06.301: 57302107: ../libfprint/drivers/elan.c:634 169s (process:2226): libfprint-elan-DEBUG: 16:48:06.301: calibration mean: 8248, bg mean: 7978, delta: 270 169s (process:2226): libfprint-SSM-DEBUG: 16:48:06.301: [elan] CALIBRATE_NUM_STATES completed successfully 169s (process:2226): libfprint-elan-DEBUG: 16:48:06.301: 57302123: ../libfprint/drivers/elan.c:776 169s (process:2226): libfprint-elan-DEBUG: 16:48:06.301: 57302126: ../libfprint/drivers/elan.c:620 169s (process:2226): libfprint-elan-DEBUG: 16:48:06.301: 57302129: ../libfprint/drivers/elan.c:100 169s (process:2226): libfprint-SSM-DEBUG: 16:48:06.301: [elan] CAPTURE_NUM_STATES entering state 0 169s (process:2226): libfprint-elan-DEBUG: 16:48:06.301: 57302520: ../libfprint/drivers/elan.c:346 169s (process:2226): libfprint-elan-DEBUG: 16:48:06.301: 57302530: ../libfprint/drivers/elan.c:366 169s (process:2226): libfprint-elan-DEBUG: 16:48:06.301: 57302533: ../libfprint/drivers/elan.c:379 169s (process:2226): libfprint-elan-DEBUG: 16:48:06.301: skipping read, not expecting anything 169s (process:2226): libfprint-elan-DEBUG: 16:48:06.301: 57302538: ../libfprint/drivers/elan.c:335 169s (process:2226): libfprint-SSM-DEBUG: 16:48:06.301: [elan] CAPTURE_NUM_STATES entering state 1 169s (process:2226): libfprint-elan-DEBUG: 16:48:06.302: 57302943: ../libfprint/drivers/elan.c:346 169s (process:2226): libfprint-elan-DEBUG: 16:48:06.302: 57302952: ../libfprint/drivers/elan.c:366 169s (process:2226): libfprint-elan-DEBUG: 16:48:06.302: 57302955: ../libfprint/drivers/elan.c:379 169s (process:2226): libfprint-elan-DEBUG: 16:48:06.302: 57303436: ../libfprint/drivers/elan.c:346 169s (process:2226): libfprint-elan-DEBUG: 16:48:06.302: 57303459: ../libfprint/drivers/elan.c:335 169s (process:2226): libfprint-SSM-DEBUG: 16:48:06.302: [elan] CAPTURE_NUM_STATES entering state 2 169s (process:2226): libfprint-device-DEBUG: 16:48:06.302: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 169s (process:2226): libfprint-image_device-DEBUG: 16:48:06.302: Image device reported finger status: on 169s (process:2226): libfprint-image_device-DEBUG: 16:48:06.302: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 169s (process:2226): libfprint-elan-DEBUG: 16:48:06.302: 57303488: ../libfprint/drivers/elan.c:960 169s (process:2226): libfprint-elan-DEBUG: 16:48:06.303: 57303868: ../libfprint/drivers/elan.c:346 169s (process:2226): libfprint-elan-DEBUG: 16:48:06.303: 57303926: ../libfprint/drivers/elan.c:366 169s (process:2226): libfprint-elan-DEBUG: 16:48:06.303: 57303951: ../libfprint/drivers/elan.c:379 169s (process:2226): libfprint-elan-DEBUG: 16:48:06.303: 57304403: ../libfprint/drivers/elan.c:346 169s (process:2226): libfprint-elan-DEBUG: 16:48:06.303: 57304433: ../libfprint/drivers/elan.c:335 169s (process:2226): libfprint-SSM-DEBUG: 16:48:06.303: [elan] CAPTURE_NUM_STATES entering state 3 169s (process:2226): libfprint-elan-DEBUG: 16:48:06.303: 57304445: ../libfprint/drivers/elan.c:203 169s (process:2226): libfprint-elan-DEBUG: 16:48:06.303: 57304455: ../libfprint/drivers/elan.c:118 169s (process:2226): libfprint-SSM-DEBUG: 16:48:06.303: [elan] CAPTURE_NUM_STATES entering state 1 169s (process:2226): libfprint-elan-DEBUG: 16:48:06.304: 57304889: ../libfprint/drivers/elan.c:346 169s (process:2226): libfprint-elan-DEBUG: 16:48:06.304: 57304945: ../libfprint/drivers/elan.c:366 169s (process:2226): libfprint-elan-DEBUG: 16:48:06.304: 57304998: ../libfprint/drivers/elan.c:379 169s (process:2226): libfprint-elan-DEBUG: 16:48:06.304: 57305420: ../libfprint/drivers/elan.c:346 169s (process:2226): libfprint-elan-DEBUG: 16:48:06.304: 57305475: ../libfprint/drivers/elan.c:335 169s (process:2226): libfprint-SSM-DEBUG: 16:48:06.304: [elan] CAPTURE_NUM_STATES entering state 2 169s (process:2226): libfprint-image_device-DEBUG: 16:48:06.304: Image device reported finger status: on 169s (process:2226): libfprint-elan-DEBUG: 16:48:06.305: 57305874: ../libfprint/drivers/elan.c:346 169s (process:2226): libfprint-elan-DEBUG: 16:48:06.305: 57305926: ../libfprint/drivers/elan.c:366 169s (process:2226): libfprint-elan-DEBUG: 16:48:06.305: 57305951: ../libfprint/drivers/elan.c:379 169s (process:2226): libfprint-elan-DEBUG: 16:48:06.305: 57306432: ../libfprint/drivers/elan.c:346 169s (process:2226): libfprint-elan-DEBUG: 16:48:06.305: 57306458: ../libfprint/drivers/elan.c:335 169s (process:2226): libfprint-SSM-DEBUG: 16:48:06.305: [elan] CAPTURE_NUM_STATES entering state 3 169s (process:2226): libfprint-elan-DEBUG: 16:48:06.305: 57306532: ../libfprint/drivers/elan.c:203 169s (process:2226): libfprint-elan-DEBUG: 16:48:06.305: 57306550: ../libfprint/drivers/elan.c:118 169s (process:2226): libfprint-SSM-DEBUG: 16:48:06.305: [elan] CAPTURE_NUM_STATES entering state 1 169s (process:2226): libfprint-elan-DEBUG: 16:48:06.306: 57307016: ../libfprint/drivers/elan.c:346 169s (process:2226): libfprint-elan-DEBUG: 16:48:06.306: 57307072: ../libfprint/drivers/elan.c:366 169s (process:2226): libfprint-elan-DEBUG: 16:48:06.306: 57307126: ../libfprint/drivers/elan.c:379 169s (process:2226): libfprint-elan-DEBUG: 16:48:06.306: 57307550: ../libfprint/drivers/elan.c:346 169s (process:2226): libfprint-elan-DEBUG: 16:48:06.306: 57307603: ../libfprint/drivers/elan.c:335 169s (process:2226): libfprint-SSM-DEBUG: 16:48:06.306: [elan] CAPTURE_NUM_STATES entering state 2 169s (process:2226): libfprint-image_device-DEBUG: 16:48:06.306: Image device reported finger status: on 169s (process:2226): libfprint-elan-DEBUG: 16:48:06.307: 57308198: ../libfprint/drivers/elan.c:346 169s (process:2226): libfprint-elan-DEBUG: 16:48:06.307: 57308267: ../libfprint/drivers/elan.c:366 169s (process:2226): libfprint-elan-DEBUG: 16:48:06.307: 57308294: ../libfprint/drivers/elan.c:379 169s (process:2226): libfprint-elan-DEBUG: 16:48:06.308: 57308737: ../libfprint/drivers/elan.c:346 169s (process:2226): libfprint-elan-DEBUG: 16:48:06.308: 57308789: ../libfprint/drivers/elan.c:335 169s (process:2226): libfprint-SSM-DEBUG: 16:48:06.308: [elan] CAPTURE_NUM_STATES entering state 3 169s (process:2226): libfprint-elan-DEBUG: 16:48:06.308: 57308809: ../libfprint/drivers/elan.c:203 169s (process:2226): libfprint-elan-DEBUG: 16:48:06.308: 57308825: ../libfprint/drivers/elan.c:118 169s (process:2226): libfprint-SSM-DEBUG: 16:48:06.308: [elan] CAPTURE_NUM_STATES entering state 1 169s (process:2226): libfprint-elan-DEBUG: 16:48:06.308: 57309253: ../libfprint/drivers/elan.c:346 169s (process:2226): libfprint-elan-DEBUG: 16:48:06.308: 57309308: ../libfprint/drivers/elan.c:366 169s (process:2226): libfprint-elan-DEBUG: 16:48:06.308: 57309362: ../libfprint/drivers/elan.c:379 169s (process:2226): libfprint-elan-DEBUG: 16:48:06.309: 57309796: ../libfprint/drivers/elan.c:346 169s (process:2226): libfprint-elan-DEBUG: 16:48:06.309: 57309849: ../libfprint/drivers/elan.c:335 169s (process:2226): libfprint-SSM-DEBUG: 16:48:06.309: [elan] CAPTURE_NUM_STATES entering state 2 169s (process:2226): libfprint-image_device-DEBUG: 16:48:06.309: Image device reported finger status: on 169s (process:2226): libfprint-elan-DEBUG: 16:48:06.309: 57310254: ../libfprint/drivers/elan.c:346 169s (process:2226): libfprint-elan-DEBUG: 16:48:06.309: 57310275: ../libfprint/drivers/elan.c:366 169s (process:2226): libfprint-elan-DEBUG: 16:48:06.309: 57310283: ../libfprint/drivers/elan.c:379 169s (process:2226): libfprint-elan-DEBUG: 16:48:06.310: 57310775: ../libfprint/drivers/elan.c:346 169s (process:2226): libfprint-elan-DEBUG: 16:48:06.310: 57310832: ../libfprint/drivers/elan.c:335 169s (process:2226): libfprint-SSM-DEBUG: 16:48:06.310: [elan] CAPTURE_NUM_STATES entering state 3 169s (process:2226): libfprint-elan-DEBUG: 16:48:06.310: 57310866: ../libfprint/drivers/elan.c:203 169s (process:2226): libfprint-elan-DEBUG: 16:48:06.310: 57310876: ../libfprint/drivers/elan.c:118 169s (process:2226): libfprint-SSM-DEBUG: 16:48:06.310: [elan] CAPTURE_NUM_STATES entering state 1 169s (process:2226): libfprint-elan-DEBUG: 16:48:06.310: 57311298: ../libfprint/drivers/elan.c:346 169s (process:2226): libfprint-elan-DEBUG: 16:48:06.310: 57311308: ../libfprint/drivers/elan.c:366 169s (process:2226): libfprint-elan-DEBUG: 16:48:06.310: 57311311: ../libfprint/drivers/elan.c:379 169s (process:2226): libfprint-elan-DEBUG: 16:48:06.311: 57311716: ../libfprint/drivers/elan.c:346 169s (process:2226): libfprint-elan-DEBUG: 16:48:06.311: 57311726: ../libfprint/drivers/elan.c:335 169s (process:2226): libfprint-SSM-DEBUG: 16:48:06.311: [elan] CAPTURE_NUM_STATES entering state 2 169s (process:2226): libfprint-image_device-DEBUG: 16:48:06.311: Image device reported finger status: on 169s (process:2226): libfprint-elan-DEBUG: 16:48:06.311: 57312170: ../libfprint/drivers/elan.c:346 169s (process:2226): libfprint-elan-DEBUG: 16:48:06.311: 57312198: ../libfprint/drivers/elan.c:366 169s (process:2226): libfprint-elan-DEBUG: 16:48:06.311: 57312206: ../libfprint/drivers/elan.c:379 169s (process:2226): libfprint-elan-DEBUG: 16:48:06.312: 57312691: ../libfprint/drivers/elan.c:346 169s (process:2226): libfprint-elan-DEBUG: 16:48:06.312: 57312704: ../libfprint/drivers/elan.c:335 169s (process:2226): libfprint-SSM-DEBUG: 16:48:06.312: [elan] CAPTURE_NUM_STATES entering state 3 169s (process:2226): libfprint-elan-DEBUG: 16:48:06.312: 57312711: ../libfprint/drivers/elan.c:203 169s (process:2226): libfprint-elan-DEBUG: 16:48:06.312: 57312720: ../libfprint/drivers/elan.c:118 169s (process:2226): libfprint-SSM-DEBUG: 16:48:06.312: [elan] CAPTURE_NUM_STATES entering state 1 169s (process:2226): libfprint-elan-DEBUG: 16:48:06.312: 57313128: ../libfprint/drivers/elan.c:346 169s (process:2226): libfprint-elan-DEBUG: 16:48:06.312: 57313182: ../libfprint/drivers/elan.c:366 169s (process:2226): libfprint-elan-DEBUG: 16:48:06.312: 57313207: ../libfprint/drivers/elan.c:379 169s (process:2226): libfprint-elan-DEBUG: 16:48:06.312: 57313579: ../libfprint/drivers/elan.c:346 169s (process:2226): libfprint-elan-DEBUG: 16:48:06.312: 57313634: ../libfprint/drivers/elan.c:335 169s (process:2226): libfprint-SSM-DEBUG: 16:48:06.312: [elan] CAPTURE_NUM_STATES entering state 2 169s (process:2226): libfprint-image_device-DEBUG: 16:48:06.312: Image device reported finger status: on 169s (process:2226): libfprint-elan-DEBUG: 16:48:06.313: 57314064: ../libfprint/drivers/elan.c:346 169s (process:2226): libfprint-elan-DEBUG: 16:48:06.313: 57314123: ../libfprint/drivers/elan.c:366 169s (process:2226): libfprint-elan-DEBUG: 16:48:06.313: 57314161: ../libfprint/drivers/elan.c:379 169s (process:2226): libfprint-elan-DEBUG: 16:48:06.313: 57314632: ../libfprint/drivers/elan.c:346 169s (process:2226): libfprint-elan-DEBUG: 16:48:06.313: 57314657: ../libfprint/drivers/elan.c:335 169s (process:2226): libfprint-SSM-DEBUG: 16:48:06.313: [elan] CAPTURE_NUM_STATES entering state 3 169s (process:2226): libfprint-elan-DEBUG: 16:48:06.314: 57314726: ../libfprint/drivers/elan.c:203 169s (process:2226): libfprint-elan-DEBUG: 16:48:06.314: 57314760: ../libfprint/drivers/elan.c:118 169s (process:2226): libfprint-SSM-DEBUG: 16:48:06.314: [elan] CAPTURE_NUM_STATES entering state 1 169s (process:2226): libfprint-elan-DEBUG: 16:48:06.314: 57315212: ../libfprint/drivers/elan.c:346 169s (process:2226): libfprint-elan-DEBUG: 16:48:06.314: 57315266: ../libfprint/drivers/elan.c:366 169s (process:2226): libfprint-elan-DEBUG: 16:48:06.314: 57315291: ../libfprint/drivers/elan.c:379 169s (process:2226): libfprint-elan-DEBUG: 16:48:06.314: 57315671: ../libfprint/drivers/elan.c:346 169s (process:2226): libfprint-elan-DEBUG: 16:48:06.314: 57315680: ../libfprint/drivers/elan.c:335 169s (process:2226): libfprint-SSM-DEBUG: 16:48:06.314: [elan] CAPTURE_NUM_STATES entering state 2 169s (process:2226): libfprint-image_device-DEBUG: 16:48:06.314: Image device reported finger status: on 169s (process:2226): libfprint-elan-DEBUG: 16:48:06.315: 57316154: ../libfprint/drivers/elan.c:346 169s (process:2226): libfprint-elan-DEBUG: 16:48:06.315: 57316183: ../libfprint/drivers/elan.c:366 169s (process:2226): libfprint-elan-DEBUG: 16:48:06.315: 57316190: ../libfprint/drivers/elan.c:379 169s (process:2226): libfprint-elan-DEBUG: 16:48:06.315: 57316676: ../libfprint/drivers/elan.c:346 169s (process:2226): libfprint-elan-DEBUG: 16:48:06.316: 57316700: ../libfprint/drivers/elan.c:335 169s (process:2226): libfprint-SSM-DEBUG: 16:48:06.316: [elan] CAPTURE_NUM_STATES entering state 3 169s (process:2226): libfprint-elan-DEBUG: 16:48:06.316: 57316710: ../libfprint/drivers/elan.c:203 169s (process:2226): libfprint-elan-DEBUG: 16:48:06.316: 57316719: ../libfprint/drivers/elan.c:118 169s (process:2226): libfprint-SSM-DEBUG: 16:48:06.316: [elan] CAPTURE_NUM_STATES entering state 1 169s (process:2226): libfprint-elan-DEBUG: 16:48:06.316: 57317116: ../libfprint/drivers/elan.c:346 169s (process:2226): libfprint-elan-DEBUG: 16:48:06.316: 57317166: ../libfprint/drivers/elan.c:366 169s (process:2226): libfprint-elan-DEBUG: 16:48:06.316: 57317172: ../libfprint/drivers/elan.c:379 169s (process:2226): libfprint-elan-DEBUG: 16:48:06.316: 57317551: ../libfprint/drivers/elan.c:346 169s (process:2226): libfprint-elan-DEBUG: 16:48:06.316: 57317605: ../libfprint/drivers/elan.c:335 169s (process:2226): libfprint-SSM-DEBUG: 16:48:06.316: [elan] CAPTURE_NUM_STATES entering state 2 169s (process:2226): libfprint-image_device-DEBUG: 16:48:06.316: Image device reported finger status: on 169s (process:2226): libfprint-elan-DEBUG: 16:48:06.317: 57318009: ../libfprint/drivers/elan.c:346 169s (process:2226): libfprint-elan-DEBUG: 16:48:06.317: 57318080: ../libfprint/drivers/elan.c:366 169s (process:2226): libfprint-elan-DEBUG: 16:48:06.317: 57318090: ../libfprint/drivers/elan.c:379 169s (process:2226): libfprint-elan-DEBUG: 16:48:06.317: 57318535: ../libfprint/drivers/elan.c:346 169s (process:2226): libfprint-elan-DEBUG: 16:48:06.317: 57318558: ../libfprint/drivers/elan.c:335 169s (process:2226): libfprint-SSM-DEBUG: 16:48:06.317: [elan] CAPTURE_NUM_STATES entering state 3 169s (process:2226): libfprint-elan-DEBUG: 16:48:06.317: 57318634: ../libfprint/drivers/elan.c:203 169s (process:2226): libfprint-elan-DEBUG: 16:48:06.317: 57318657: ../libfprint/drivers/elan.c:118 169s (process:2226): libfprint-SSM-DEBUG: 16:48:06.317: [elan] CAPTURE_NUM_STATES entering state 1 169s (process:2226): libfprint-elan-DEBUG: 16:48:06.318: 57319189: ../libfprint/drivers/elan.c:346 169s (process:2226): libfprint-elan-DEBUG: 16:48:06.318: 57319245: ../libfprint/drivers/elan.c:366 169s (process:2226): libfprint-elan-DEBUG: 16:48:06.318: 57319270: ../libfprint/drivers/elan.c:379 169s (process:2226): libfprint-elan-DEBUG: 16:48:06.319: 57319716: ../libfprint/drivers/elan.c:346 169s (process:2226): libfprint-elan-DEBUG: 16:48:06.319: 57319748: ../libfprint/drivers/elan.c:335 169s (process:2226): libfprint-SSM-DEBUG: 16:48:06.319: [elan] CAPTURE_NUM_STATES entering state 2 169s (process:2226): libfprint-image_device-DEBUG: 16:48:06.319: Image device reported finger status: on 169s (process:2226): libfprint-elan-DEBUG: 16:48:06.319: 57320260: ../libfprint/drivers/elan.c:346 169s (process:2226): libfprint-elan-DEBUG: 16:48:06.319: 57320288: ../libfprint/drivers/elan.c:366 169s (process:2226): libfprint-elan-DEBUG: 16:48:06.319: 57320295: ../libfprint/drivers/elan.c:379 169s (process:2226): libfprint-elan-DEBUG: 16:48:06.320: 57320754: ../libfprint/drivers/elan.c:346 169s (process:2226): libfprint-elan-DEBUG: 16:48:06.320: 57320813: ../libfprint/drivers/elan.c:335 169s (process:2226): libfprint-SSM-DEBUG: 16:48:06.320: [elan] CAPTURE_NUM_STATES entering state 3 169s (process:2226): libfprint-elan-DEBUG: 16:48:06.320: 57320847: ../libfprint/drivers/elan.c:203 169s (process:2226): libfprint-elan-DEBUG: 16:48:06.320: 57320857: ../libfprint/drivers/elan.c:118 169s (process:2226): libfprint-SSM-DEBUG: 16:48:06.320: [elan] CAPTURE_NUM_STATES entering state 1 169s (process:2226): libfprint-elan-DEBUG: 16:48:06.320: 57321320: ../libfprint/drivers/elan.c:346 169s (process:2226): libfprint-elan-DEBUG: 16:48:06.320: 57321379: ../libfprint/drivers/elan.c:366 169s (process:2226): libfprint-elan-DEBUG: 16:48:06.320: 57321394: ../libfprint/drivers/elan.c:379 169s (process:2226): libfprint-elan-DEBUG: 16:48:06.321: 57321752: ../libfprint/drivers/elan.c:346 169s (process:2226): libfprint-elan-DEBUG: 16:48:06.321: 57321772: ../libfprint/drivers/elan.c:335 169s (process:2226): libfprint-SSM-DEBUG: 16:48:06.321: [elan] CAPTURE_NUM_STATES entering state 2 169s (process:2226): libfprint-image_device-DEBUG: 16:48:06.321: Image device reported finger status: on 169s (process:2226): libfprint-elan-DEBUG: 16:48:06.321: 57322287: ../libfprint/drivers/elan.c:346 169s (process:2226): libfprint-elan-DEBUG: 16:48:06.321: 57322343: ../libfprint/drivers/elan.c:366 169s (process:2226): libfprint-elan-DEBUG: 16:48:06.321: 57322352: ../libfprint/drivers/elan.c:379 169s (process:2226): libfprint-elan-DEBUG: 16:48:06.322: 57322810: ../libfprint/drivers/elan.c:346 169s (process:2226): libfprint-elan-DEBUG: 16:48:06.322: 57322868: ../libfprint/drivers/elan.c:335 169s (process:2226): libfprint-SSM-DEBUG: 16:48:06.322: [elan] CAPTURE_NUM_STATES entering state 3 169s (process:2226): libfprint-elan-DEBUG: 16:48:06.322: 57322903: ../libfprint/drivers/elan.c:203 169s (process:2226): libfprint-elan-DEBUG: 16:48:06.322: 57322921: ../libfprint/drivers/elan.c:118 169s (process:2226): libfprint-SSM-DEBUG: 16:48:06.322: [elan] CAPTURE_NUM_STATES entering state 1 169s (process:2226): libfprint-elan-DEBUG: 16:48:06.322: 57323395: ../libfprint/drivers/elan.c:346 169s (process:2226): libfprint-elan-DEBUG: 16:48:06.322: 57323453: ../libfprint/drivers/elan.c:366 169s (process:2226): libfprint-elan-DEBUG: 16:48:06.322: 57323509: ../libfprint/drivers/elan.c:379 169s (process:2226): libfprint-elan-DEBUG: 16:48:06.323: 57323928: ../libfprint/drivers/elan.c:346 169s (process:2226): libfprint-elan-DEBUG: 16:48:06.323: 57323982: ../libfprint/drivers/elan.c:335 169s (process:2226): libfprint-SSM-DEBUG: 16:48:06.323: [elan] CAPTURE_NUM_STATES entering state 2 169s (process:2226): libfprint-image_device-DEBUG: 16:48:06.323: Image device reported finger status: on 169s (process:2226): libfprint-elan-DEBUG: 16:48:06.323: 57324473: ../libfprint/drivers/elan.c:346 169s (process:2226): libfprint-elan-DEBUG: 16:48:06.323: 57324529: ../libfprint/drivers/elan.c:366 169s (process:2226): libfprint-elan-DEBUG: 16:48:06.323: 57324546: ../libfprint/drivers/elan.c:379 169s (process:2226): libfprint-elan-DEBUG: 16:48:06.324: 57324947: ../libfprint/drivers/elan.c:346 169s (process:2226): libfprint-elan-DEBUG: 16:48:06.324: 57325005: ../libfprint/drivers/elan.c:335 169s (process:2226): libfprint-SSM-DEBUG: 16:48:06.324: [elan] CAPTURE_NUM_STATES entering state 3 169s (process:2226): libfprint-elan-DEBUG: 16:48:06.324: 57325039: ../libfprint/drivers/elan.c:203 169s (process:2226): libfprint-elan-DEBUG: 16:48:06.324: 57325049: ../libfprint/drivers/elan.c:118 169s (process:2226): libfprint-SSM-DEBUG: 16:48:06.324: [elan] CAPTURE_NUM_STATES entering state 1 169s (process:2226): libfprint-elan-DEBUG: 16:48:06.324: 57325524: ../libfprint/drivers/elan.c:346 169s (process:2226): libfprint-elan-DEBUG: 16:48:06.324: 57325580: ../libfprint/drivers/elan.c:366 169s (process:2226): libfprint-elan-DEBUG: 16:48:06.324: 57325637: ../libfprint/drivers/elan.c:379 169s (process:2226): libfprint-elan-DEBUG: 16:48:06.325: 57326062: ../libfprint/drivers/elan.c:346 169s (process:2226): libfprint-elan-DEBUG: 16:48:06.325: 57326121: ../libfprint/drivers/elan.c:335 169s (process:2226): libfprint-SSM-DEBUG: 16:48:06.325: [elan] CAPTURE_NUM_STATES entering state 2 169s (process:2226): libfprint-image_device-DEBUG: 16:48:06.325: Image device reported finger status: on 169s (process:2226): libfprint-elan-DEBUG: 16:48:06.325: 57326615: ../libfprint/drivers/elan.c:346 169s (process:2226): libfprint-elan-DEBUG: 16:48:06.325: 57326635: ../libfprint/drivers/elan.c:366 169s (process:2226): libfprint-elan-DEBUG: 16:48:06.325: 57326686: ../libfprint/drivers/elan.c:379 169s (process:2226): libfprint-elan-DEBUG: 16:48:06.326: 57327122: ../libfprint/drivers/elan.c:346 169s (process:2226): libfprint-elan-DEBUG: 16:48:06.326: 57327179: ../libfprint/drivers/elan.c:335 169s (process:2226): libfprint-SSM-DEBUG: 16:48:06.326: [elan] CAPTURE_NUM_STATES entering state 3 169s (process:2226): libfprint-elan-DEBUG: 16:48:06.326: 57327212: ../libfprint/drivers/elan.c:203 169s (process:2226): libfprint-elan-DEBUG: 16:48:06.326: 57327222: ../libfprint/drivers/elan.c:118 169s (process:2226): libfprint-SSM-DEBUG: 16:48:06.326: [elan] CAPTURE_NUM_STATES entering state 1 169s (process:2226): libfprint-elan-DEBUG: 16:48:06.326: 57327657: ../libfprint/drivers/elan.c:346 169s (process:2226): libfprint-elan-DEBUG: 16:48:06.327: 57327712: ../libfprint/drivers/elan.c:366 169s (process:2226): libfprint-elan-DEBUG: 16:48:06.327: 57327726: ../libfprint/drivers/elan.c:379 169s (process:2226): libfprint-elan-DEBUG: 16:48:06.327: 57328107: ../libfprint/drivers/elan.c:346 169s (process:2226): libfprint-elan-DEBUG: 16:48:06.327: 57328167: ../libfprint/drivers/elan.c:335 169s (process:2226): libfprint-SSM-DEBUG: 16:48:06.327: [elan] CAPTURE_NUM_STATES entering state 2 169s (process:2226): libfprint-image_device-DEBUG: 16:48:06.327: Image device reported finger status: on 169s (process:2226): libfprint-elan-DEBUG: 16:48:06.327: 57328539: ../libfprint/drivers/elan.c:346 169s (process:2226): libfprint-elan-DEBUG: 16:48:06.327: 57328590: ../libfprint/drivers/elan.c:366 169s (process:2226): libfprint-elan-DEBUG: 16:48:06.327: 57328597: ../libfprint/drivers/elan.c:379 169s (process:2226): libfprint-elan-DEBUG: 16:48:06.328: 57329057: ../libfprint/drivers/elan.c:346 169s (process:2226): libfprint-elan-DEBUG: 16:48:06.328: 57329115: ../libfprint/drivers/elan.c:335 169s (process:2226): libfprint-SSM-DEBUG: 16:48:06.328: [elan] CAPTURE_NUM_STATES entering state 3 169s (process:2226): libfprint-elan-DEBUG: 16:48:06.328: 57329157: ../libfprint/drivers/elan.c:203 169s (process:2226): libfprint-elan-DEBUG: 16:48:06.328: 57329172: ../libfprint/drivers/elan.c:118 169s (process:2226): libfprint-SSM-DEBUG: 16:48:06.328: [elan] CAPTURE_NUM_STATES entering state 1 169s (process:2226): libfprint-elan-DEBUG: 16:48:06.329: 57329719: ../libfprint/drivers/elan.c:346 169s (process:2226): libfprint-elan-DEBUG: 16:48:06.329: 57329779: ../libfprint/drivers/elan.c:366 169s (process:2226): libfprint-elan-DEBUG: 16:48:06.329: 57329832: ../libfprint/drivers/elan.c:379 169s (process:2226): libfprint-elan-DEBUG: 16:48:06.329: 57330277: ../libfprint/drivers/elan.c:346 169s (process:2226): libfprint-elan-DEBUG: 16:48:06.329: 57330337: ../libfprint/drivers/elan.c:335 169s (process:2226): libfprint-SSM-DEBUG: 16:48:06.329: [elan] CAPTURE_NUM_STATES entering state 2 169s (process:2226): libfprint-image_device-DEBUG: 16:48:06.329: Image device reported finger status: on 169s (process:2226): libfprint-elan-DEBUG: 16:48:06.330: 57330778: ../libfprint/drivers/elan.c:346 169s (process:2226): libfprint-elan-DEBUG: 16:48:06.330: 57330798: ../libfprint/drivers/elan.c:366 169s (process:2226): libfprint-elan-DEBUG: 16:48:06.330: 57330805: ../libfprint/drivers/elan.c:379 169s (process:2226): libfprint-elan-DEBUG: 16:48:06.330: 57331291: ../libfprint/drivers/elan.c:346 169s (process:2226): libfprint-elan-DEBUG: 16:48:06.330: 57331359: ../libfprint/drivers/elan.c:335 169s (process:2226): libfprint-SSM-DEBUG: 16:48:06.330: [elan] CAPTURE_NUM_STATES entering state 3 169s (process:2226): libfprint-elan-DEBUG: 16:48:06.330: 57331379: ../libfprint/drivers/elan.c:203 169s (process:2226): libfprint-elan-DEBUG: 16:48:06.330: 57331390: ../libfprint/drivers/elan.c:118 169s (process:2226): libfprint-SSM-DEBUG: 16:48:06.330: [elan] CAPTURE_NUM_STATES entering state 1 169s (process:2226): libfprint-elan-DEBUG: 16:48:06.331: 57331829: ../libfprint/drivers/elan.c:346 169s (process:2226): libfprint-elan-DEBUG: 16:48:06.331: 57331884: ../libfprint/drivers/elan.c:366 169s (process:2226): libfprint-elan-DEBUG: 16:48:06.331: 57331938: ../libfprint/drivers/elan.c:379 169s (process:2226): libfprint-elan-DEBUG: 16:48:06.331: 57332383: ../libfprint/drivers/elan.c:346 169s (process:2226): libfprint-elan-DEBUG: 16:48:06.331: 57332447: ../libfprint/drivers/elan.c:335 169s (process:2226): libfprint-SSM-DEBUG: 16:48:06.331: [elan] CAPTURE_NUM_STATES entering state 2 169s (process:2226): libfprint-image_device-DEBUG: 16:48:06.331: Image device reported finger status: on 169s (process:2226): libfprint-elan-DEBUG: 16:48:06.332: 57332852: ../libfprint/drivers/elan.c:346 169s (process:2226): libfprint-elan-DEBUG: 16:48:06.332: 57332905: ../libfprint/drivers/elan.c:366 169s (process:2226): libfprint-elan-DEBUG: 16:48:06.332: 57332930: ../libfprint/drivers/elan.c:379 169s (process:2226): libfprint-elan-DEBUG: 16:48:06.332: 57333373: ../libfprint/drivers/elan.c:346 169s (process:2226): libfprint-elan-DEBUG: 16:48:06.332: 57333428: ../libfprint/drivers/elan.c:335 169s (process:2226): libfprint-SSM-DEBUG: 16:48:06.332: [elan] CAPTURE_NUM_STATES entering state 3 169s (process:2226): libfprint-elan-DEBUG: 16:48:06.332: 57333468: ../libfprint/drivers/elan.c:203 169s (process:2226): libfprint-elan-DEBUG: 16:48:06.332: 57333532: ../libfprint/drivers/elan.c:118 169s (process:2226): libfprint-SSM-DEBUG: 16:48:06.332: [elan] CAPTURE_NUM_STATES entering state 1 169s (process:2226): libfprint-elan-DEBUG: 16:48:06.333: 57333955: ../libfprint/drivers/elan.c:346 169s (process:2226): libfprint-elan-DEBUG: 16:48:06.333: 57334028: ../libfprint/drivers/elan.c:366 169s (process:2226): libfprint-elan-DEBUG: 16:48:06.333: 57334049: ../libfprint/drivers/elan.c:379 169s (process:2226): libfprint-elan-DEBUG: 16:48:06.333: 57334441: ../libfprint/drivers/elan.c:346 169s (process:2226): libfprint-elan-DEBUG: 16:48:06.333: 57334462: ../libfprint/drivers/elan.c:335 169s (process:2226): libfprint-SSM-DEBUG: 16:48:06.333: [elan] CAPTURE_NUM_STATES entering state 2 169s (process:2226): libfprint-image_device-DEBUG: 16:48:06.333: Image device reported finger status: on 169s (process:2226): libfprint-elan-DEBUG: 16:48:06.334: 57334893: ../libfprint/drivers/elan.c:346 169s (process:2226): libfprint-elan-DEBUG: 16:48:06.334: 57334901: ../libfprint/drivers/elan.c:366 169s (process:2226): libfprint-elan-DEBUG: 16:48:06.334: 57334904: ../libfprint/drivers/elan.c:379 169s (process:2226): libfprint-elan-DEBUG: 16:48:06.334: 57335394: ../libfprint/drivers/elan.c:346 169s (process:2226): libfprint-elan-DEBUG: 16:48:06.334: 57335449: ../libfprint/drivers/elan.c:335 169s (process:2226): libfprint-SSM-DEBUG: 16:48:06.334: [elan] CAPTURE_NUM_STATES entering state 3 169s (process:2226): libfprint-elan-DEBUG: 16:48:06.334: 57335468: ../libfprint/drivers/elan.c:203 169s (process:2226): libfprint-elan-DEBUG: 16:48:06.334: 57335481: ../libfprint/drivers/elan.c:118 169s (process:2226): libfprint-SSM-DEBUG: 16:48:06.334: [elan] CAPTURE_NUM_STATES entering state 1 169s (process:2226): libfprint-elan-DEBUG: 16:48:06.335: 57335936: ../libfprint/drivers/elan.c:346 169s (process:2226): libfprint-elan-DEBUG: 16:48:06.335: 57335991: ../libfprint/drivers/elan.c:366 169s (process:2226): libfprint-elan-DEBUG: 16:48:06.335: 57336031: ../libfprint/drivers/elan.c:379 169s (process:2226): libfprint-elan-DEBUG: 16:48:06.335: 57336449: ../libfprint/drivers/elan.c:346 169s (process:2226): libfprint-elan-DEBUG: 16:48:06.335: 57336502: ../libfprint/drivers/elan.c:335 169s (process:2226): libfprint-SSM-DEBUG: 16:48:06.335: [elan] CAPTURE_NUM_STATES entering state 2 169s (process:2226): libfprint-SSM-DEBUG: 16:48:06.335: [elan] CAPTURE_NUM_STATES completed successfully 169s (process:2226): libfprint-elan-DEBUG: 16:48:06.335: 57336531: ../libfprint/drivers/elan.c:586 169s (process:2226): libfprint-elan-DEBUG: 16:48:06.335: 57336533: ../libfprint/drivers/elan.c:315 169s (process:2226): libfprint-elan-DEBUG: 16:48:06.335: 57336538: ../libfprint/drivers/elan.c:272 169s (process:2226): libfprint-elan-DEBUG: 16:48:06.336: 57337232: ../libfprint/drivers/elan.c:272 169s (process:2226): libfprint-elan-DEBUG: 16:48:06.337: 57337909: ../libfprint/drivers/elan.c:272 169s (process:2226): libfprint-elan-DEBUG: 16:48:06.337: 57338607: ../libfprint/drivers/elan.c:272 169s (process:2226): libfprint-elan-DEBUG: 16:48:06.338: 57339293: ../libfprint/drivers/elan.c:272 169s (process:2226): libfprint-elan-DEBUG: 16:48:06.339: 57339973: ../libfprint/drivers/elan.c:272 169s (process:2226): libfprint-elan-DEBUG: 16:48:06.340: 57340754: ../libfprint/drivers/elan.c:272 169s (process:2226): libfprint-elan-DEBUG: 16:48:06.340: 57341508: ../libfprint/drivers/elan.c:272 169s (process:2226): libfprint-elan-DEBUG: 16:48:06.341: 57342340: ../libfprint/drivers/elan.c:272 169s (process:2226): libfprint-elan-DEBUG: 16:48:06.342: 57343074: ../libfprint/drivers/elan.c:272 169s (process:2226): libfprint-elan-DEBUG: 16:48:06.343: 57343807: ../libfprint/drivers/elan.c:272 169s (process:2226): libfprint-elan-DEBUG: 16:48:06.343: 57344551: ../libfprint/drivers/elan.c:272 169s (process:2226): libfprint-elan-DEBUG: 16:48:06.344: 57345289: ../libfprint/drivers/elan.c:272 169s (process:2226): libfprint-elan-DEBUG: 16:48:06.345: 57346027: ../libfprint/drivers/elan.c:272 169s (process:2226): libfprint-assembling-DEBUG: 16:48:06.561: calc delta completed in 0.215422 secs 169s (process:2226): libfprint-assembling-DEBUG: 16:48:06.829: calc delta completed in 0.267955 secs 169s (process:2226): libfprint-assembling-DEBUG: 16:48:06.847: errors: 133465 rev: 143589 170s (process:2226): libfprint-assembling-DEBUG: 16:48:07.267: calc delta completed in 0.419984 secs 170s (process:2226): libfprint-assembling-DEBUG: 16:48:07.290: height is 225 170s (process:2226): libfprint-image_device-DEBUG: 16:48:07.290: Image device captured an image 170s (process:2226): libfprint-image_device-DEBUG: 16:48:07.310: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 170s (process:2226): libfprint-elan-DEBUG: 16:48:07.310: 58310735: ../libfprint/drivers/elan.c:960 170s (process:2226): libfprint-device-DEBUG: 16:48:07.310: Device reported finger status change: FP_FINGER_STATUS_PRESENT 170s (process:2226): libfprint-elan-DEBUG: 16:48:07.310: 58310747: ../libfprint/drivers/elan.c:507 170s (process:2226): libfprint-elan-DEBUG: 16:48:07.310: 58310751: ../libfprint/drivers/elan.c:100 170s (process:2226): libfprint-SSM-DEBUG: 16:48:07.310: [elan] STOP_CAPTURE_NUM_STATES entering state 0 170s (process:2226): libfprint-elan-DEBUG: 16:48:07.310: 58310764: ../libfprint/drivers/elan.c:466 170s (process:2226): libfprint-image-DEBUG: 16:48:07.327: Minutiae scan completed in 0.016978 secs 170s (process:2226): libfprint-device-DEBUG: 16:48:07.331: Updated temperature model after 1.03 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 170s (process:2226): libfprint-elan-DEBUG: 16:48:07.331: 58332216: ../libfprint/drivers/elan.c:346 170s (process:2226): libfprint-elan-DEBUG: 16:48:07.331: 58332268: ../libfprint/drivers/elan.c:366 170s (process:2226): libfprint-elan-DEBUG: 16:48:07.331: 58332321: ../libfprint/drivers/elan.c:379 170s (process:2226): libfprint-elan-DEBUG: 16:48:07.331: skipping read, not expecting anything 170s (process:2226): libfprint-elan-DEBUG: 16:48:07.331: 58332424: ../libfprint/drivers/elan.c:335 170s (process:2226): libfprint-SSM-DEBUG: 16:48:07.331: [elan] STOP_CAPTURE_NUM_STATES completed successfully 170s (process:2226): libfprint-elan-DEBUG: 16:48:07.331: 58332532: ../libfprint/drivers/elan.c:483 170s (process:2226): libfprint-device-DEBUG: 16:48:07.331: Device reported finger status change: FP_FINGER_STATUS_NONE 170s (process:2226): libfprint-image_device-DEBUG: 16:48:07.331: Image device reported finger status: off 170s (process:2226): libfprint-image_device-DEBUG: 16:48:07.332: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 170s (process:2226): libfprint-elan-DEBUG: 16:48:07.332: 58332774: ../libfprint/drivers/elan.c:960 170s (process:2226): libfprint-image_device-DEBUG: 16:48:07.332: Deactivating image device 170s (process:2226): libfprint-image_device-DEBUG: 16:48:07.332: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_DEACTIVATING 170s (process:2226): libfprint-elan-DEBUG: 16:48:07.332: 58332936: ../libfprint/drivers/elan.c:960 170s (process:2226): libfprint-elan-DEBUG: 16:48:07.332: 58332989: ../libfprint/drivers/elan.c:975 170s (process:2226): libfprint-image_device-DEBUG: 16:48:07.332: Image device deactivation completed 170s (process:2226): libfprint-image_device-DEBUG: 16:48:07.332: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE 170s (process:2226): libfprint-elan-DEBUG: 16:48:07.332: 58333153: ../libfprint/drivers/elan.c:960 170s (process:2226): libfprint-device-DEBUG: 16:48:07.332: Device reported capture completion 170s (process:2226): libfprint-device-DEBUG: 16:48:07.332: Completing action FPI_DEVICE_ACTION_CAPTURE in idle! 170s (process:2226): libfprint-device-DEBUG: 16:48:07.332: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 170s (process:2226): libfprint-elan-DEBUG: 16:48:07.332: 58333492: ../libfprint/drivers/elan.c:939 170s (process:2226): libfprint-elan-DEBUG: 16:48:07.332: 58333565: ../libfprint/drivers/elan.c:100 170s (process:2226): libfprint-image_device-DEBUG: 16:48:07.333: Image device close completed 170s (process:2226): libfprint-device-DEBUG: 16:48:07.333: Device reported close completion 170s (process:2226): libfprint-device-DEBUG: 16:48:07.333: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 170s (process:2226): libfprint-device-DEBUG: 16:48:07.333: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 170s ** (umockdev-run:2222): DEBUG: 16:48:07.443: umockdev.vala:150: Removing test bed /tmp/umockdev.O1YHK2 170s (umockdev-run:2222): GLib-DEBUG: 16:48:07.446: unsetenv() is not thread-safe and should not be used after threads are created 170s Comparing PNGs /tmp/libfprint-umockdev-test-ym8znceo/capture.png and /usr/share/installed-tests/libfprint-2/elan-cobo/capture.png 170s PASS: libfprint-2/driver-elan-cobo.test 170s Running test: libfprint-2/tod-fpi-device-tod-fake_test_dev_tod_current.test 170s (process:2233): libfprint-context-DEBUG: 16:48:07.514: Initializing FpContext (libfprint version 1.94.7+tod1) 170s (process:2233): libfprint-tod-DEBUG: 16:48:07.514: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/current/libdevice-fake-tod-driver.so 170s (process:2233): libfprint-tod-DEBUG: 16:48:07.514: Found TOD entry point symbol 0xfdea2a1c2580, GType is 219368973567456 170s (process:2233): libfprint-tod-DEBUG: 16:48:07.514: Loading driver fake_test_dev_tod_current (Virtual device for debugging) 170s (process:2233): libfprint-context-DEBUG: 16:48:07.517: No driver found for USB device 1D6B:0003 170s (process:2233): libfprint-context-DEBUG: 16:48:07.517: No driver found for USB device 0627:0001 170s (process:2233): libfprint-context-DEBUG: 16:48:07.517: No driver found for USB device 1D6B:0002 170s (process:2233): libfprint-context-DEBUG: 16:48:07.517: Found virtual environment device: FP_VIRTUAL_FAKE_DEVICE, yes 170s (process:2233): libfprint-context-DEBUG: 16:48:07.518: created 170s (process:2233): libfprint-fake_test_dev_tod_current-DEBUG: 16:48:07.518: fpi_device_fake_probe: Device Virtual device for debugging in action FPI_DEVICE_ACTION_PROBE 170s 170s (process:2233): libfprint-device-DEBUG: 16:48:07.518: Device reported probe completion 170s (process:2233): libfprint-device-DEBUG: 16:48:07.518: Completing action FPI_DEVICE_ACTION_PROBE in idle! 170s (process:2233): libfprint-device-DEBUG: 16:48:07.518: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 170s (/usr/libexec/installed-tests/libfprint-2/test-fpi-device-tod:2233): GLib-DEBUG: 16:48:07.518: setenv()/putenv() are not thread-safe and should not be used after threads are created 170s TAP version 13 170s # random seed: R02S04ffba53d77eca12ec18d5012a98d418 170s 1..97 170s # Start of driver tests 170s ok 1 /driver/get_driver 170s ok 2 /driver/get_device_id 170s ok 3 /driver/get_name 170s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 170s # 170s # libfprint-device-DEBUG: Device reported open completion 170s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 170s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 170s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 170s # 170s # libfprint-device-DEBUG: Device reported close completion 170s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 170s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 170s ok 4 /driver/is_open 170s ok 5 /driver/get_nr_enroll_stages 170s ok 6 /driver/set_nr_enroll_stages 170s ok 7 /driver/supports_identify 170s ok 8 /driver/supports_capture 170s ok 9 /driver/has_storage 170s ok 10 /driver/do_not_support_identify 170s ok 11 /driver/do_not_support_capture 170s ok 12 /driver/has_not_storage 170s ok 13 /driver/get_usb_device 170s ok 14 /driver/get_virtual_env 170s ok 15 /driver/get_driver_data 170s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_current' 170s # libfprint-device-DEBUG: Tod version info is 'current' 170s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_probe: Device Virtual device for debugging in action FPI_DEVICE_ACTION_PROBE 170s # 170s # libfprint-device-DEBUG: Device reported probe completion 170s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 170s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 170s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_current' 170s # libfprint-device-DEBUG: Tod version info is 'current' 170s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_current' 170s # libfprint-device-DEBUG: Tod version info is 'current' 170s ok 16 /driver/initial_features 170s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_probe: Device Probed device name in action FPI_DEVICE_ACTION_PROBE 170s # 170s # libfprint-device-DEBUG: Device reported probe completion 170s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 170s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 170s ok 17 /driver/probe 170s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 170s # 170s # libfprint-device-DEBUG: Device reported open completion 170s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 170s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 170s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 170s # 170s # libfprint-device-DEBUG: Device reported close completion 170s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 170s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 170s ok 18 /driver/open 170s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 170s # 170s # libfprint-device-DEBUG: Device reported open completion 170s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 170s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 170s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 170s # 170s # libfprint-device-DEBUG: Device reported close completion 170s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 170s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 170s ok 19 /driver/close 170s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 170s # 170s # libfprint-device-DEBUG: Device reported open completion 170s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 170s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 170s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 170s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_enroll: Device Virtual device for debugging in action FPI_DEVICE_ACTION_ENROLL 170s # 170s # libfprint-device-DEBUG: Device reported enroll completion 170s # libfprint-device-DEBUG: Print for finger FP_FINGER_UNKNOWN enrolled 170s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 170s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 170s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 170s # 170s # libfprint-device-DEBUG: Device reported close completion 170s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 170s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 170s ok 20 /driver/enroll 170s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 170s # 170s # libfprint-device-DEBUG: Device reported open completion 170s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 170s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 170s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 170s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_verify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_VERIFY 170s # 170s # libfprint-device-DEBUG: Device reported verify result 170s # libfprint-device-DEBUG: Device reported verify completion 170s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 170s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 170s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 170s # 170s # libfprint-device-DEBUG: Device reported close completion 170s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 170s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 170s ok 21 /driver/verify 170s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 170s # 170s # libfprint-device-DEBUG: Device reported open completion 170s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 170s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 170s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 170s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_identify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY 170s # 170s # libfprint-device-DEBUG: Device reported identify result 170s # libfprint-device-DEBUG: Device reported identify completion 170s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 170s # libfprint-device-DEBUG: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 170s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 170s # 170s # libfprint-device-DEBUG: Device reported close completion 170s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 170s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 170s ok 22 /driver/identify 170s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 170s # 170s # libfprint-device-DEBUG: Device reported open completion 170s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 170s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 170s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 170s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_capture: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CAPTURE 170s # 170s # libfprint-device-DEBUG: Device reported capture completion 170s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CAPTURE in idle! 170s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 170s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 170s # 170s # libfprint-device-DEBUG: Device reported close completion 170s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 170s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 170s ok 23 /driver/capture 170s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 170s # 170s # libfprint-device-DEBUG: Device reported open completion 170s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 170s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 170s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_list: Device Virtual device for debugging in action FPI_DEVICE_ACTION_LIST 170s # 170s # libfprint-device-DEBUG: Device reported listing completion 170s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_LIST in idle! 170s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 170s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 170s # 170s # libfprint-device-DEBUG: Device reported close completion 170s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 170s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 170s ok 24 /driver/list 170s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 170s # 170s # libfprint-device-DEBUG: Device reported open completion 170s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 170s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 170s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_delete: Device Virtual device for debugging in action FPI_DEVICE_ACTION_DELETE 170s # 170s # libfprint-device-DEBUG: Device reported deletion completion 170s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_DELETE in idle! 170s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 170s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 170s # 170s # libfprint-device-DEBUG: Device reported close completion 170s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 170s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 170s ok 25 /driver/delete 170s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 170s # 170s # libfprint-device-DEBUG: Device reported open completion 170s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 170s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 170s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_current' 170s # libfprint-device-DEBUG: Tod version info is 'current' 170s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_clear_storage: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLEAR_STORAGE 170s # 170s # libfprint-device-DEBUG: Device reported deletion completion 170s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 170s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 170s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 170s # 170s # libfprint-device-DEBUG: Device reported close completion 170s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 170s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 170s ok 26 /driver/clear_storage 170s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 170s # 170s # libfprint-device-DEBUG: Device reported open completion 170s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 170s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 170s # libfprint-device-DEBUG: Idle cancelling on ongoing operation! 170s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_cancel: Device Virtual device for debugging in action FPI_DEVICE_ACTION_DELETE 170s # 170s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_delete: Device Virtual device for debugging in action FPI_DEVICE_ACTION_DELETE 170s # 170s # libfprint-device-DEBUG: Device reported deletion completion 170s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_DELETE in idle! 170s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 170s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 170s # 170s # libfprint-device-DEBUG: Device reported close completion 170s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 170s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 170s ok 27 /driver/cancel 170s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 170s # 170s # libfprint-device-DEBUG: Device reported open completion 170s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 170s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 170s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_current' 170s # libfprint-device-DEBUG: Tod version info is 'current' 170s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 170s # libfprint-device-DEBUG: Idle cancelling on ongoing operation! 170s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_cancel: Device Virtual device for debugging in action FPI_DEVICE_ACTION_VERIFY 170s # 170s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_suspend: Device Virtual device for debugging in action FPI_DEVICE_ACTION_VERIFY 170s # 170s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_resume: Device Virtual device for debugging in action FPI_DEVICE_ACTION_VERIFY 170s # 170s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_verify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_VERIFY 170s # 170s # libfprint-device-DEBUG: Device reported verify result 170s # libfprint-device-DEBUG: Device reported verify completion 170s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 170s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 170s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 170s # 170s # libfprint-device-DEBUG: Device reported close completion 170s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 170s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 170s ok 28 /driver/critical 170s ok 29 /driver/get_current_action 170s ok 30 /driver/timeout 170s ok 31 /driver/error_types 170s ok 32 /driver/retry_error_types 170s # Start of get_scan_type tests 170s ok 33 /driver/get_scan_type/press 170s ok 34 /driver/get_scan_type/swipe 170s # End of get_scan_type tests 170s # Start of set_scan_type tests 170s ok 35 /driver/set_scan_type/press 170s ok 36 /driver/set_scan_type/swipe 170s # End of set_scan_type tests 170s # Start of finger_status tests 170s ok 37 /driver/finger_status/inactive 170s # libfprint-device-DEBUG: Device reported finger status change: FP_FINGER_STATUS_NEEDED 170s ok 38 /driver/finger_status/waiting 170s # libfprint-device-DEBUG: Device reported finger status change: FP_FINGER_STATUS_PRESENT 170s ok 39 /driver/finger_status/present 170s # libfprint-device-DEBUG: Device reported finger status change: FP_FINGER_STATUS_NEEDED 170s # libfprint-device-DEBUG: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 170s # libfprint-device-DEBUG: Device reported finger status change: FP_FINGER_STATUS_PRESENT 170s # libfprint-device-DEBUG: Device reported finger status change: FP_FINGER_STATUS_NONE 170s ok 40 /driver/finger_status/changes 170s # End of finger_status tests 170s # Start of features tests 170s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_current' 170s # libfprint-device-DEBUG: Tod version info is 'current' 170s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_probe: Device Virtual device for debugging in action FPI_DEVICE_ACTION_PROBE 170s # 170s # libfprint-device-DEBUG: Device reported probe completion 170s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 170s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 170s ok 41 /driver/features/probe_updates 170s # End of features tests 170s # Start of initial_features tests 170s ok 42 /driver/initial_features/none 170s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_current' 170s # libfprint-device-DEBUG: Tod version info is 'current' 170s ok 43 /driver/initial_features/no_capture 170s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_current' 170s # libfprint-device-DEBUG: Tod version info is 'current' 170s ok 44 /driver/initial_features/no_verify 170s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_current' 170s # libfprint-device-DEBUG: Tod version info is 'current' 170s ok 45 /driver/initial_features/no_identify 170s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_current' 170s # libfprint-device-DEBUG: Tod version info is 'current' 170s ok 46 /driver/initial_features/no_storage 170s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_current' 170s # libfprint-device-DEBUG: Tod version info is 'current' 170s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_current' 170s # libfprint-device-DEBUG: Tod version info is 'current' 170s ok 47 /driver/initial_features/no_list 170s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_current' 170s # libfprint-device-DEBUG: Tod version info is 'current' 170s ok 48 /driver/initial_features/no_delete 170s ok 49 /driver/initial_features/no_clear 170s # End of initial_features tests 170s # Start of probe tests 170s # libfprint-device-DEBUG: Device reported probe completion 170s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 170s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 170s ok 50 /driver/probe/error 170s # libfprint-device-DEBUG: Device reported generic error (The operation is not supported on this device!) during action; action was: FPI_DEVICE_ACTION_PROBE 170s # libfprint-device-DEBUG: Device reported probe completion 170s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 170s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 170s ok 51 /driver/probe/action_error 170s # End of probe tests 170s # Start of open tests 170s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 170s # 170s # libfprint-device-DEBUG: Device reported open completion 170s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 170s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 170s ok 52 /driver/open/error 170s # End of open tests 170s # Start of close tests 170s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 170s # 170s # libfprint-device-DEBUG: Device reported open completion 170s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 170s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 170s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 170s # 170s # libfprint-device-DEBUG: Device reported close completion 170s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 170s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 170s ok 53 /driver/close/error 170s # End of close tests 170s # Start of enroll tests 170s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 170s # 170s # libfprint-device-DEBUG: Device reported open completion 170s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 170s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 170s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 170s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_enroll: Device Virtual device for debugging in action FPI_DEVICE_ACTION_ENROLL 170s # 170s # libfprint-device-DEBUG: Device reported enroll completion 170s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 170s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 170s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 170s # 170s # libfprint-device-DEBUG: Device reported close completion 170s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 170s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 170s ok 54 /driver/enroll/error 170s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 170s # 170s # libfprint-device-DEBUG: Device reported open completion 170s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 170s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 170s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 170s # libfprint-device-DEBUG: Device reported enroll progress, reported 2008054409 of 877814734 have been completed 170s # libfprint-device-DEBUG: Device reported enroll progress, reported 1987592927 of 877814734 have been completed 170s # libfprint-device-DEBUG: Device reported enroll progress, reported 944380556 of 877814734 have been completed 170s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_enroll: Device Virtual device for debugging in action FPI_DEVICE_ACTION_ENROLL 170s # 170s # libfprint-device-DEBUG: Device reported enroll completion 170s # libfprint-device-DEBUG: Print for finger FP_FINGER_UNKNOWN enrolled 170s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 170s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 170s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 170s # 170s # libfprint-device-DEBUG: Device reported close completion 170s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 170s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 170s ok 55 /driver/enroll/progress 170s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 170s # 170s # libfprint-device-DEBUG: Device reported open completion 170s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 170s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 170s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 170s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_enroll: Device Virtual device for debugging in action FPI_DEVICE_ACTION_ENROLL 170s # 170s # libfprint-device-DEBUG: Device reported enroll completion 170s # libfprint-device-DEBUG: Print for finger FP_FINGER_UNKNOWN enrolled 170s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 170s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 170s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 170s # 170s # libfprint-device-DEBUG: Device reported close completion 170s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 170s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 170s ok 56 /driver/enroll/update_nbis 170s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 170s # 170s # libfprint-device-DEBUG: Device reported open completion 170s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 170s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 170s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 170s # 170s # libfprint-device-DEBUG: Device reported close completion 170s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 170s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 170s ok 57 /driver/enroll/update_nbis_wrong_device 170s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 170s # 170s # libfprint-device-DEBUG: Device reported open completion 170s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 170s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 170s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 170s # 170s # libfprint-device-DEBUG: Device reported close completion 170s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 170s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 170s ok 58 /driver/enroll/update_nbis_wrong_driver 170s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 170s # 170s # libfprint-device-DEBUG: Device reported open completion 170s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 170s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 170s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 170s # 170s # libfprint-device-DEBUG: Device reported close completion 170s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 170s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 170s ok 59 /driver/enroll/update_nbis_missing_feature 170s # Start of error tests 170s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 170s # 170s # libfprint-device-DEBUG: Device reported open completion 170s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 170s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 170s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 170s # libfprint-device-DEBUG: Device reported enroll completion 170s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 170s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 170s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 170s # libfprint-device-DEBUG: Device reported enroll completion 170s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 170s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 170s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 170s # libfprint-device-DEBUG: Device reported enroll completion 170s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 170s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 170s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 170s # 170s # libfprint-device-DEBUG: Device reported close completion 170s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 170s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 170s ok 60 /driver/enroll/error/no_print 170s # End of error tests 170s # End of enroll tests 170s # Start of verify tests 170s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 170s # 170s # libfprint-device-DEBUG: Device reported open completion 170s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 170s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 170s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 170s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_verify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_VERIFY 170s # 170s # libfprint-device-DEBUG: Device reported verify result 170s # libfprint-device-DEBUG: Device reported verify completion 170s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 170s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 170s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 170s # 170s # libfprint-device-DEBUG: Device reported close completion 170s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 170s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 170s ok 61 /driver/verify/fail 170s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 170s # 170s # libfprint-device-DEBUG: Device reported open completion 170s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 170s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 170s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 170s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_verify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_VERIFY 170s # 170s # libfprint-device-DEBUG: Device reported verify result 170s # libfprint-device-DEBUG: Device reported verify completion 170s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 170s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 170s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 170s # 170s # libfprint-device-DEBUG: Device reported close completion 170s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 170s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 170s ok 62 /driver/verify/retry 170s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 170s # 170s # libfprint-device-DEBUG: Device reported open completion 170s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 170s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 170s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 170s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_verify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_VERIFY 170s # 170s # libfprint-device-DEBUG: Device reported verify completion 170s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 170s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 170s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 170s # 170s # libfprint-device-DEBUG: Device reported close completion 170s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 170s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 170s ok 63 /driver/verify/error 170s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 170s # 170s # libfprint-device-DEBUG: Device reported open completion 170s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 170s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 170s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 170s # 170s # libfprint-device-DEBUG: Device reported close completion 170s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 170s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 170s ok 64 /driver/verify/not_supported 170s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 170s # 170s # libfprint-device-DEBUG: Device reported open completion 170s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 170s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 170s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 170s # libfprint-device-DEBUG: Device reported verify result 170s # libfprint-device-DEBUG: Device reported verify completion 170s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 170s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 170s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 170s # 170s # libfprint-device-DEBUG: Device reported close completion 170s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 170s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 170s ok 65 /driver/verify/report_no_cb 170s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 170s # 170s # libfprint-device-DEBUG: Device reported open completion 170s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 170s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 170s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 170s # libfprint-device-DEBUG: Device reported verify completion 170s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 170s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 170s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 170s # 170s # libfprint-device-DEBUG: Device reported close completion 170s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 170s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 170s ok 66 /driver/verify/not_reported 170s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 170s # 170s # libfprint-device-DEBUG: Device reported open completion 170s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 170s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 170s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 170s # libfprint-device-DEBUG: Device reported verify result 170s # libfprint-device-DEBUG: Device reported verify completion 170s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 170s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 170s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 170s # libfprint-device-DEBUG: Device reported verify result 170s # libfprint-device-DEBUG: Device reported verify completion 170s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 170s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 170s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 170s # libfprint-device-DEBUG: Device reported verify result 170s # libfprint-device-DEBUG: Device reported verify completion 170s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 170s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 170s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 170s # libfprint-device-DEBUG: Device reported verify result 170s # libfprint-device-DEBUG: Device reported verify completion 170s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 170s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 170s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 170s # libfprint-device-DEBUG: Device reported verify result 170s # libfprint-device-DEBUG: Device reported verify completion 170s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 170s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 170s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 170s # 170s # libfprint-device-DEBUG: Device reported close completion 170s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 170s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 170s ok 67 /driver/verify/complete_retry 170s # End of verify tests 170s # Start of identify tests 170s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 170s # 170s # libfprint-device-DEBUG: Device reported open completion 170s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 170s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 170s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 170s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_identify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY 170s # 170s # libfprint-device-DEBUG: Device reported identify result 170s # libfprint-device-DEBUG: Device reported identify completion 170s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 170s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 170s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 170s # 170s # libfprint-device-DEBUG: Device reported close completion 170s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 170s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 170s ok 68 /driver/identify/fail 170s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 170s # 170s # libfprint-device-DEBUG: Device reported open completion 170s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 170s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 170s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 170s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_identify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY 170s # 170s # libfprint-device-DEBUG: Device reported identify result 170s # libfprint-device-DEBUG: Device reported identify completion 170s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 170s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 170s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 170s # 170s # libfprint-device-DEBUG: Device reported close completion 170s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 170s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 170s ok 69 /driver/identify/retry 170s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 170s # 170s # libfprint-device-DEBUG: Device reported open completion 170s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 170s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 170s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 170s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_identify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY 170s # 170s # libfprint-device-DEBUG: Device reported identify completion 170s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 170s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 170s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 170s # 170s # libfprint-device-DEBUG: Device reported close completion 170s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 170s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 170s ok 70 /driver/identify/error 170s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 170s # 170s # libfprint-device-DEBUG: Device reported open completion 170s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 170s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 170s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 170s # libfprint-device-DEBUG: Device reported identify completion 170s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 170s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 170s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 170s # 170s # libfprint-device-DEBUG: Device reported close completion 170s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 170s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_COLD 170s ok 71 /driver/identify/not_reported 170s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 170s # 170s # libfprint-device-DEBUG: Device reported open completion 170s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 170s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 170s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 170s # libfprint-device-DEBUG: Device reported identify result 170s # libfprint-device-DEBUG: Device reported identify completion 170s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 170s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 170s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 170s # libfprint-device-DEBUG: Device reported identify result 170s # libfprint-device-DEBUG: Device reported identify completion 170s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 170s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 170s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 170s # libfprint-device-DEBUG: Device reported identify result 170s # libfprint-device-DEBUG: Device reported identify completion 170s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 170s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 170s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 170s # 170s # libfprint-device-DEBUG: Device reported close completion 170s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 170s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 170s ok 72 /driver/identify/complete_retry 170s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 170s # 170s # libfprint-device-DEBUG: Device reported open completion 170s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 170s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 170s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 170s # libfprint-device-DEBUG: Device reported identify result 170s # libfprint-device-DEBUG: Device reported identify completion 170s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 170s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 170s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 170s # 170s # libfprint-device-DEBUG: Device reported close completion 170s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 170s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 170s ok 73 /driver/identify/report_no_cb 170s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_current' 170s # libfprint-device-DEBUG: Tod version info is 'current' 170s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 170s # 170s # libfprint-device-DEBUG: Device reported open completion 170s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 170s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 170s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 170s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_suspend: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY 170s # 170s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_resume: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY 170s # 170s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_identify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY 170s # 170s # libfprint-device-DEBUG: Device reported identify result 170s # libfprint-device-DEBUG: Device reported identify completion 170s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 170s # libfprint-device-DEBUG: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 170s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 170s # 170s # libfprint-device-DEBUG: Device reported close completion 170s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 170s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 170s ok 74 /driver/identify/suspend_continues 170s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_current' 170s # libfprint-device-DEBUG: Tod version info is 'current' 170s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 170s # 170s # libfprint-device-DEBUG: Device reported open completion 170s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 170s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 170s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 170s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_suspend: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY 170s # 170s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_identify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY 170s # 170s # libfprint-device-DEBUG: Device reported identify result 170s # libfprint-device-DEBUG: Device reported identify completion 170s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 170s # libfprint-device-DEBUG: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 170s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 170s # 170s # libfprint-device-DEBUG: Device reported close completion 170s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 170s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 170s ok 75 /driver/identify/suspend_succeeds 170s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_current' 170s # libfprint-device-DEBUG: Tod version info is 'current' 170s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 170s # 170s # libfprint-device-DEBUG: Device reported open completion 170s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 170s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 170s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 170s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_suspend: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY 170s # 170s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_identify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY 170s # 170s # libfprint-device-DEBUG: Device reported identify completion 170s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 170s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 170s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 170s # 170s # libfprint-device-DEBUG: Device reported close completion 170s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 170s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 170s ok 76 /driver/identify/suspend_busy_error 170s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_current' 170s # libfprint-device-DEBUG: Tod version info is 'current' 170s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 170s # 170s # libfprint-device-DEBUG: Device reported open completion 170s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 170s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 170s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 170s # 170s # libfprint-device-DEBUG: Device reported close completion 170s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 170s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 170s ok 77 /driver/identify/suspend_while_idle 170s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_current' 170s # libfprint-device-DEBUG: Tod version info is 'current' 170s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 170s # 170s # libfprint-device-DEBUG: Device reported open completion 170s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 170s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 170s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 170s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.30, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 172s Executing: libfprint-2/tod-fpi-device-tod-fake_test_dev_tod_current.test 172s # libfprint-device-DEBUG: Updated temperature model after 2.00 seconds, ratio 0.30 -> 0.74, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_HOT 172s # libfprint-device-DEBUG: Idle cancelling on ongoing operation! 172s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_cancel: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY 172s # 172s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_identify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY 172s # 172s # libfprint-device-DEBUG: Device reported identify completion 172s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 172s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.74 -> 0.74, active 0 -> 0, FP_TEMPERATURE_HOT -> FP_TEMPERATURE_HOT 172s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.74 -> 0.74, active 1 -> 1, FP_TEMPERATURE_HOT -> FP_TEMPERATURE_HOT 172s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.74 -> 0.74, active 0 -> 0, FP_TEMPERATURE_HOT -> FP_TEMPERATURE_HOT 174s # libfprint-device-DEBUG: Updated temperature model after 2.09 seconds, ratio 0.74 -> 0.49, active 0 -> 0, FP_TEMPERATURE_HOT -> FP_TEMPERATURE_WARM 177s Executing: libfprint-2/tod-fpi-device-tod-fake_test_dev_tod_current.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_tod_current-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_tod_current-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_tod_current-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_tod_current-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 178s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_capture: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CAPTURE 178s # 178s # libfprint-device-DEBUG: Device reported capture completion 178s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CAPTURE 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_WARM 178s # libfprint-fake_test_dev_tod_current-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_WARM -> FP_TEMPERATURE_WARM 178s ok 80 /driver/capture/error 178s # End of capture tests 178s # Start of list tests 178s # libfprint-fake_test_dev_tod_current-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_tod_current-DEBUG: fpi_device_fake_list: Device Virtual device for debugging in action FPI_DEVICE_ACTION_LIST 178s # 178s # libfprint-device-DEBUG: Device reported listing completion 178s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_LIST 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_tod_current-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 81 /driver/list/error 178s # libfprint-fake_test_dev_tod_current-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_tod_current-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 82 /driver/list/no_storage 178s # End of list tests 178s # Start of delete tests 178s # libfprint-fake_test_dev_tod_current-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_tod_current-DEBUG: fpi_device_fake_delete: Device Virtual device for debugging in action FPI_DEVICE_ACTION_DELETE 178s # 178s # libfprint-device-DEBUG: Device reported deletion completion 178s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_DELETE 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_tod_current-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 83 /driver/delete/error 178s # End of delete tests 178s # Start of clear_storage tests 178s # libfprint-fake_test_dev_tod_current-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: Getting TOD version for driver 'fake_test_dev_tod_current' 178s # libfprint-device-DEBUG: Tod version info is 'current' 178s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_clear_storage: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLEAR_STORAGE 178s # 178s # libfprint-device-DEBUG: Device reported deletion completion 178s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE 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_tod_current-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 84 /driver/clear_storage/error 178s # End of clear_storage tests 178s # Start of cancel tests 178s # libfprint-fake_test_dev_tod_current-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_tod_current-DEBUG: fpi_device_fake_delete: Device Virtual device for debugging in action FPI_DEVICE_ACTION_DELETE 178s # 178s # libfprint-device-DEBUG: Device reported deletion completion 178s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_DELETE 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_tod_current-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 85 /driver/cancel/fail 178s # End of cancel tests 178s # Start of get_current_action tests 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_tod_current-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 86 /driver/get_current_action/open 178s # End of get_current_action tests 178s # Start of get_cancellable tests 178s ok 87 /driver/get_cancellable/error 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_tod_current-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 88 /driver/get_cancellable/open 178s # Start of open tests 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_tod_current-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 89 /driver/get_cancellable/open/internal 178s # End of open tests 178s # End of get_cancellable tests 178s # Start of action_is_cancelled tests 178s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_current' 178s # libfprint-device-DEBUG: Tod version info is 'current' 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_tod_current-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 90 /driver/action_is_cancelled/open 178s ok 91 /driver/action_is_cancelled/error 178s # Start of open tests 178s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_current' 178s # libfprint-device-DEBUG: Tod version info is 'current' 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_tod_current-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 92 /driver/action_is_cancelled/open/internal 178s # End of open tests 178s # End of action_is_cancelled tests 178s # Start of complete_action tests 178s # Start of all tests 178s ok 93 /driver/complete_action/all/error 178s # End of all tests 178s # End of complete_action tests 178s # Start of action_error tests 178s ok 94 /driver/action_error/error 178s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 178s # 178s # libfprint-device-DEBUG: Device reported generic error (Passed (print) data is not valid.) during action; action was: FPI_DEVICE_ACTION_OPEN 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_tod_current-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 178s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_enroll: Device Virtual device for debugging in action FPI_DEVICE_ACTION_ENROLL 178s # 178s # libfprint-device-DEBUG: Device reported generic error (Passed (print) data is not valid.) during action; action was: FPI_DEVICE_ACTION_ENROLL 178s # libfprint-device-DEBUG: Device reported enroll completion 178s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_ENROLL 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_WARM 178s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 178s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_verify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_VERIFY 178s # 178s # libfprint-device-DEBUG: Device reported generic error (Passed (print) data is not valid.) during action; action was: FPI_DEVICE_ACTION_VERIFY 178s # libfprint-device-DEBUG: Device reported verify completion 178s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 178s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 178s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 178s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_identify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY 178s # 178s # libfprint-device-DEBUG: Device reported generic error (Passed (print) data is not valid.) during action; action was: FPI_DEVICE_ACTION_IDENTIFY 178s # libfprint-device-DEBUG: Device reported identify completion 178s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 178s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 178s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 178s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_capture: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CAPTURE 178s # 178s # libfprint-device-DEBUG: Device reported generic error (Passed (print) data is not valid.) during action; action was: FPI_DEVICE_ACTION_CAPTURE 178s # libfprint-device-DEBUG: Device reported capture completion 178s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CAPTURE in idle! 178s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 178s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_list: Device Virtual device for debugging in action FPI_DEVICE_ACTION_LIST 178s # 178s # libfprint-device-DEBUG: Device reported generic error (Passed (print) data is not valid.) during action; action was: FPI_DEVICE_ACTION_LIST 178s # libfprint-device-DEBUG: Device reported listing completion 178s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_LIST in idle! 178s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 178s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_delete: Device Virtual device for debugging in action FPI_DEVICE_ACTION_DELETE 178s # 178s # libfprint-device-DEBUG: Device reported generic error (Passed (print) data is not valid.) during action; action was: FPI_DEVICE_ACTION_DELETE 178s # libfprint-device-DEBUG: Device reported deletion completion 178s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_DELETE in idle! 178s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 178s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_current' 178s # libfprint-device-DEBUG: Tod version info is 'current' 178s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_clear_storage: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLEAR_STORAGE 178s # 178s # libfprint-device-DEBUG: Device reported generic error (Passed (print) data is not valid.) during action; action was: FPI_DEVICE_ACTION_CLEAR_STORAGE 178s # libfprint-device-DEBUG: Device reported deletion completion 178s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 178s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 178s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 178s # 178s # libfprint-device-DEBUG: Device reported generic error (Passed (print) data is not valid.) during action; action was: FPI_DEVICE_ACTION_CLOSE 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_WARM -> FP_TEMPERATURE_WARM 178s ok 95 /driver/action_error/all 178s # libfprint-fake_test_dev_tod_current-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_tod_current-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 178s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_enroll: Device Virtual device for debugging in action FPI_DEVICE_ACTION_ENROLL 178s # 178s # libfprint-device-DEBUG: Device reported enroll completion 178s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_ENROLL 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_WARM 178s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 178s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_verify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_VERIFY 178s # 178s # libfprint-device-DEBUG: Device reported verify completion 178s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 178s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 178s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 178s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_identify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY 178s # 178s # libfprint-device-DEBUG: Device reported identify completion 178s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 178s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 178s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 178s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_capture: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CAPTURE 178s # 178s # libfprint-device-DEBUG: Device reported capture completion 178s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CAPTURE in idle! 178s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 178s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_list: Device Virtual device for debugging in action FPI_DEVICE_ACTION_LIST 178s # 178s # libfprint-device-DEBUG: Device reported listing completion 178s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_LIST in idle! 178s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 178s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_delete: Device Virtual device for debugging in action FPI_DEVICE_ACTION_DELETE 178s # 178s # libfprint-device-DEBUG: Device reported deletion completion 178s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_DELETE in idle! 178s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 178s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_current' 178s # libfprint-device-DEBUG: Tod version info is 'current' 178s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_clear_storage: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLEAR_STORAGE 178s # 178s # libfprint-device-DEBUG: Device reported deletion completion 178s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 178s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 178s # libfprint-fake_test_dev_tod_current-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_WARM -> FP_TEMPERATURE_WARM 178s ok 96 /driver/action_error/fail 178s # End of action_error tests 178s # Start of timeout tests 178s ok 97 /driver/timeout/cancelled 178s # End of timeout tests 178s # End of driver tests 178s PASS: libfprint-2/tod-fpi-device-tod-fake_test_dev_tod_current.test 178s Running test: libfprint-2/driver-focaltech_moc.test 178s ** (umockdev-run:2241): DEBUG: 16:48:15.095: umockdev.vala:123: Created udev test bed /tmp/umockdev.Y2EFK2 178s ** (umockdev-run:2241): DEBUG: 16:48:15.095: umockdev.vala:1297: parsing device description for /devices/pci0000:00/0000:00:1c.4/0000:0b:00.0/usb3/3-1/3-1.4 178s ** (umockdev-run:2241): DEBUG: 16:48:15.099: umockdev.vala:1366: creating device /devices/pci0000:00/0000:00:1c.4/0000:0b:00.0/usb3/3-1/3-1.4 (subsystem usb) 178s ** (umockdev-run:2241): DEBUG: 16:48:15.102: umockdev.vala:1411: create_node_for_device: creating file device /tmp/umockdev.Y2EFK2/dev/bus/usb/003/006 178s ** (umockdev-run:2241): DEBUG: 16:48:15.102: umockdev.vala:1297: parsing device description for /devices/pci0000:00/0000:00:1c.4/0000:0b:00.0/usb3/3-1 178s ** (umockdev-run:2241): DEBUG: 16:48:15.105: umockdev.vala:1366: creating device /devices/pci0000:00/0000:00:1c.4/0000:0b:00.0/usb3/3-1 (subsystem usb) 178s ** (umockdev-run:2241): DEBUG: 16:48:15.107: umockdev.vala:1411: create_node_for_device: creating file device /tmp/umockdev.Y2EFK2/dev/bus/usb/003/002 178s ** (umockdev-run:2241): DEBUG: 16:48:15.107: umockdev.vala:1297: parsing device description for /devices/pci0000:00/0000:00:1c.4/0000:0b:00.0/usb3 178s ** (umockdev-run:2241): DEBUG: 16:48:15.110: umockdev.vala:1366: creating device /devices/pci0000:00/0000:00:1c.4/0000:0b:00.0/usb3 (subsystem usb) 178s ** (umockdev-run:2241): DEBUG: 16:48:15.112: umockdev.vala:1411: create_node_for_device: creating file device /tmp/umockdev.Y2EFK2/dev/bus/usb/003/001 178s ** (umockdev-run:2241): DEBUG: 16:48:15.112: umockdev.vala:1297: parsing device description for /devices/pci0000:00/0000:00:1c.4/0000:0b:00.0 178s ** (umockdev-run:2241): DEBUG: 16:48:15.114: umockdev.vala:1366: creating device /devices/pci0000:00/0000:00:1c.4/0000:0b:00.0 (subsystem pci) 178s ** (umockdev-run:2241): DEBUG: 16:48:15.116: umockdev.vala:1297: parsing device description for /devices/pci0000:00/0000:00:1c.4 178s ** (umockdev-run:2241): DEBUG: 16:48:15.116: umockdev.vala:1366: creating device /devices/pci0000:00/0000:00:1c.4 (subsystem pci) 178s (process:2245): libfprint-context-DEBUG: 16:48:15.168: Initializing FpContext (libfprint version 1.94.7+tod1) 178s (process:2245): libfprint-tod-DEBUG: 16:48:15.169: Impossible to load the shared drivers dir Error opening directory “/usr/lib/aarch64-linux-gnu/libfprint-2/tod-1”: No such file or directory 178s (process:2245): libfprint-focaltech_moc-DEBUG: 16:48:15.171: 66171700: ../libfprint/drivers/focaltech_moc/focaltech_moc.c:1849 178s (process:2245): libfprint-context-DEBUG: 16:48:15.171: No driver found for USB device 05E3:0608 178s (process:2245): libfprint-context-DEBUG: 16:48:15.171: No driver found for USB device 1D6B:0002 178s (process:2245): libfprint-device-DEBUG: 16:48:15.171: Device reported probe completion 178s (process:2245): libfprint-device-DEBUG: 16:48:15.171: Completing action FPI_DEVICE_ACTION_PROBE in idle! 178s (process:2245): libfprint-device-DEBUG: 16:48:15.171: Not updating temperature model, device can run continuously! 178s (process:2245): libfprint-focaltech_moc-DEBUG: 16:48:15.172: class:dc, subclass:a0, protocol:b0 178s (process:2245): libfprint-focaltech_moc-DEBUG: 16:48:15.173: bytes size:0 178s (process:2245): libfprint-focaltech_moc-DEBUG: 16:48:15.173: 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 178s (process:2245): libfprint-focaltech_moc-DEBUG: 16:48:15.173: bytes size:0 178s (process:2245): libfprint-focaltech_moc-DEBUG: 16:48:15.173: 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 178s libusb: warning [read_sysfs_attr] attribute bConfigurationValue doesn't end with newline? 178s libusb: warning [read_sysfs_attr] attribute bConfigurationValue doesn't end with newline? 178s (process:2245): libfprint-SSM-DEBUG: 16:48:15.173: [focaltech_moc] DEV_INIT_STATES entering state 0 178s (process:2245): libfprint-SSM-DEBUG: 16:48:15.173: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 178s (process:2245): libfprint-SSM-DEBUG: 16:48:15.174: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 178s (process:2245): libfprint-focaltech_moc-DEBUG: 16:48:15.174: focaltechmoc enroll_times: 10 178s (process:2245): libfprint-SSM-DEBUG: 16:48:15.174: [focaltech_moc] DEV_INIT_STATES entering state 1 178s (process:2245): libfprint-SSM-DEBUG: 16:48:15.174: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 178s (process:2245): libfprint-SSM-DEBUG: 16:48:15.174: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 178s (process:2245): libfprint-SSM-DEBUG: 16:48:15.174: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 178s (process:2245): libfprint-SSM-DEBUG: 16:48:15.175: [focaltech_moc] DEV_INIT_STATES completed successfully 178s (process:2245): libfprint-device-DEBUG: 16:48:15.175: Device reported open completion 178s (process:2245): libfprint-SSM-DEBUG: 16:48:15.175: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 178s (process:2245): libfprint-device-DEBUG: 16:48:15.175: Completing action FPI_DEVICE_ACTION_OPEN in idle! 178s (process:2245): libfprint-device-DEBUG: 16:48:15.175: Not updating temperature model, device can run continuously! 178s (process:2245): libfprint-device-DEBUG: 16:48:15.182: Not updating temperature model, device can run continuously! 178s (process:2245): libfprint-SSM-DEBUG: 16:48:15.182: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 0 178s (process:2245): libfprint-SSM-DEBUG: 16:48:15.182: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 178s (process:2245): libfprint-SSM-DEBUG: 16:48:15.182: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 178s (process:2245): libfprint-SSM-DEBUG: 16:48:15.183: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 1 178s (process:2245): libfprint-SSM-DEBUG: 16:48:15.183: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 178s (process:2245): libfprint-SSM-DEBUG: 16:48:15.183: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 178s (process:2245): libfprint-SSM-DEBUG: 16:48:15.183: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 178s (process:2245): libfprint-SSM-DEBUG: 16:48:15.184: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 2 178s (process:2245): libfprint-SSM-DEBUG: 16:48:15.184: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 178s (process:2245): libfprint-SSM-DEBUG: 16:48:15.184: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 178s (process:2245): libfprint-SSM-DEBUG: 16:48:15.185: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 178s (process:2245): libfprint-SSM-DEBUG: 16:48:15.185: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 3 178s (process:2245): libfprint-SSM-DEBUG: 16:48:15.185: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 178s (process:2245): libfprint-SSM-DEBUG: 16:48:15.185: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 178s (process:2245): libfprint-SSM-DEBUG: 16:48:15.186: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 178s (process:2245): libfprint-focaltech_moc-DEBUG: 16:48:15.186: focaltechmoc user id: FP1-00000000-0-00000000-nobody 178s (process:2245): libfprint-SSM-DEBUG: 16:48:15.186: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 178s (process:2245): libfprint-SSM-DEBUG: 16:48:15.186: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 178s (process:2245): libfprint-SSM-DEBUG: 16:48:15.186: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 178s (process:2245): libfprint-SSM-DEBUG: 16:48:15.187: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 178s (process:2245): libfprint-SSM-DEBUG: 16:48:15.187: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5 178s (process:2245): libfprint-SSM-DEBUG: 16:48:15.187: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 178s (process:2245): libfprint-SSM-DEBUG: 16:48:15.237: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 178s (process:2245): libfprint-SSM-DEBUG: 16:48:15.237: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 178s (process:2245): libfprint-SSM-DEBUG: 16:48:15.238: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 178s (process:2245): libfprint-SSM-DEBUG: 16:48:15.238: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5 178s (process:2245): libfprint-SSM-DEBUG: 16:48:15.238: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 178s (process:2245): libfprint-SSM-DEBUG: 16:48:15.289: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 178s (process:2245): libfprint-SSM-DEBUG: 16:48:15.289: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 178s (process:2245): libfprint-SSM-DEBUG: 16:48:15.289: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 178s (process:2245): libfprint-SSM-DEBUG: 16:48:15.290: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5 178s (process:2245): libfprint-SSM-DEBUG: 16:48:15.290: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 178s (process:2245): libfprint-SSM-DEBUG: 16:48:15.340: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 178s (process:2245): libfprint-SSM-DEBUG: 16:48:15.340: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 178s (process:2245): libfprint-SSM-DEBUG: 16:48:15.340: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 178s (process:2245): libfprint-SSM-DEBUG: 16:48:15.341: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5 178s (process:2245): libfprint-SSM-DEBUG: 16:48:15.341: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 178s (process:2245): libfprint-SSM-DEBUG: 16:48:15.391: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 178s (process:2245): libfprint-SSM-DEBUG: 16:48:15.391: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 178s (process:2245): libfprint-SSM-DEBUG: 16:48:15.392: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 178s (process:2245): libfprint-SSM-DEBUG: 16:48:15.392: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5 178s (process:2245): libfprint-SSM-DEBUG: 16:48:15.392: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 178s (process:2245): libfprint-SSM-DEBUG: 16:48:15.442: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 178s (process:2245): libfprint-SSM-DEBUG: 16:48:15.443: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 178s (process:2245): libfprint-SSM-DEBUG: 16:48:15.443: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 178s (process:2245): libfprint-SSM-DEBUG: 16:48:15.444: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5 178s (process:2245): libfprint-SSM-DEBUG: 16:48:15.444: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 178s (process:2245): libfprint-SSM-DEBUG: 16:48:15.494: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 178s (process:2245): libfprint-SSM-DEBUG: 16:48:15.494: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 178s (process:2245): libfprint-SSM-DEBUG: 16:48:15.494: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 178s (process:2245): libfprint-SSM-DEBUG: 16:48:15.495: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 6 178s (process:2245): libfprint-SSM-DEBUG: 16:48:15.495: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 178s (process:2245): libfprint-SSM-DEBUG: 16:48:15.495: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 178s (process:2245): libfprint-SSM-DEBUG: 16:48:15.496: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 178s (process:2245): libfprint-device-DEBUG: 16:48:15.496: Device reported enroll progress, reported 1 of 10 have been completed 178s (process:2245): libfprint-focaltech_moc-DEBUG: 16:48:15.496: focaltechmoc remain: 9 178s (process:2245): libfprint-SSM-DEBUG: 16:48:15.496: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 178s (process:2245): libfprint-SSM-DEBUG: 16:48:15.496: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 178s (process:2245): libfprint-SSM-DEBUG: 16:48:15.497: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 178s (process:2245): libfprint-SSM-DEBUG: 16:48:15.497: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 178s (process:2245): libfprint-SSM-DEBUG: 16:48:15.497: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5 178s (process:2245): libfprint-SSM-DEBUG: 16:48:15.497: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 178s (process:2245): libfprint-SSM-DEBUG: 16:48:15.547: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 178s (process:2245): libfprint-SSM-DEBUG: 16:48:15.547: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 178s (process:2245): libfprint-SSM-DEBUG: 16:48:15.548: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 178s (process:2245): libfprint-SSM-DEBUG: 16:48:15.548: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5 178s (process:2245): libfprint-SSM-DEBUG: 16:48:15.549: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 178s (process:2245): libfprint-SSM-DEBUG: 16:48:15.599: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 178s (process:2245): libfprint-SSM-DEBUG: 16:48:15.599: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 178s (process:2245): libfprint-SSM-DEBUG: 16:48:15.599: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 178s (process:2245): libfprint-SSM-DEBUG: 16:48:15.600: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5 178s (process:2245): libfprint-SSM-DEBUG: 16:48:15.600: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 178s (process:2245): libfprint-SSM-DEBUG: 16:48:15.650: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 178s (process:2245): libfprint-SSM-DEBUG: 16:48:15.650: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 178s (process:2245): libfprint-SSM-DEBUG: 16:48:15.650: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 178s (process:2245): libfprint-SSM-DEBUG: 16:48:15.651: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5 178s (process:2245): libfprint-SSM-DEBUG: 16:48:15.651: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 178s (process:2245): libfprint-SSM-DEBUG: 16:48:15.701: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 178s (process:2245): libfprint-SSM-DEBUG: 16:48:15.701: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 178s (process:2245): libfprint-SSM-DEBUG: 16:48:15.702: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 178s (process:2245): libfprint-SSM-DEBUG: 16:48:15.702: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5 178s (process:2245): libfprint-SSM-DEBUG: 16:48:15.702: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 178s (process:2245): libfprint-SSM-DEBUG: 16:48:15.752: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 178s (process:2245): libfprint-SSM-DEBUG: 16:48:15.752: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 178s (process:2245): libfprint-SSM-DEBUG: 16:48:15.753: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 178s (process:2245): libfprint-SSM-DEBUG: 16:48:15.753: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 6 178s (process:2245): libfprint-SSM-DEBUG: 16:48:15.753: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 178s (process:2245): libfprint-SSM-DEBUG: 16:48:15.753: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 178s (process:2245): libfprint-SSM-DEBUG: 16:48:15.754: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 178s (process:2245): libfprint-device-DEBUG: 16:48:15.754: Device reported enroll progress, reported 2 of 10 have been completed 178s (process:2245): libfprint-focaltech_moc-DEBUG: 16:48:15.754: focaltechmoc remain: 8 178s (process:2245): libfprint-SSM-DEBUG: 16:48:15.754: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 178s (process:2245): libfprint-SSM-DEBUG: 16:48:15.754: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 178s (process:2245): libfprint-SSM-DEBUG: 16:48:15.754: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 178s (process:2245): libfprint-SSM-DEBUG: 16:48:15.755: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 178s (process:2245): libfprint-SSM-DEBUG: 16:48:15.755: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5 178s (process:2245): libfprint-SSM-DEBUG: 16:48:15.755: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 178s (process:2245): libfprint-SSM-DEBUG: 16:48:15.805: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 178s (process:2245): libfprint-SSM-DEBUG: 16:48:15.805: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 178s (process:2245): libfprint-SSM-DEBUG: 16:48:15.806: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 178s (process:2245): libfprint-SSM-DEBUG: 16:48:15.806: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 6 178s (process:2245): libfprint-SSM-DEBUG: 16:48:15.806: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 178s (process:2245): libfprint-SSM-DEBUG: 16:48:15.807: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 178s (process:2245): libfprint-SSM-DEBUG: 16:48:15.807: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 178s (process:2245): libfprint-device-DEBUG: 16:48:15.807: Device reported enroll progress, reported 3 of 10 have been completed 178s (process:2245): libfprint-focaltech_moc-DEBUG: 16:48:15.807: focaltechmoc remain: 7 178s (process:2245): libfprint-SSM-DEBUG: 16:48:15.807: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 178s (process:2245): libfprint-SSM-DEBUG: 16:48:15.807: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 178s (process:2245): libfprint-SSM-DEBUG: 16:48:15.808: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 178s (process:2245): libfprint-SSM-DEBUG: 16:48:15.808: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 178s (process:2245): libfprint-SSM-DEBUG: 16:48:15.808: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5 178s (process:2245): libfprint-SSM-DEBUG: 16:48:15.808: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 178s (process:2245): libfprint-SSM-DEBUG: 16:48:15.859: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 178s (process:2245): libfprint-SSM-DEBUG: 16:48:15.859: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 178s (process:2245): libfprint-SSM-DEBUG: 16:48:15.859: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 178s (process:2245): libfprint-SSM-DEBUG: 16:48:15.860: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5 178s (process:2245): libfprint-SSM-DEBUG: 16:48:15.860: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 178s (process:2245): libfprint-SSM-DEBUG: 16:48:15.910: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 178s (process:2245): libfprint-SSM-DEBUG: 16:48:15.910: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 178s (process:2245): libfprint-SSM-DEBUG: 16:48:15.910: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 178s (process:2245): libfprint-SSM-DEBUG: 16:48:15.911: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5 178s (process:2245): libfprint-SSM-DEBUG: 16:48:15.911: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 178s (process:2245): libfprint-SSM-DEBUG: 16:48:15.961: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 178s (process:2245): libfprint-SSM-DEBUG: 16:48:15.961: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 178s (process:2245): libfprint-SSM-DEBUG: 16:48:15.962: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 178s (process:2245): libfprint-SSM-DEBUG: 16:48:15.962: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5 178s (process:2245): libfprint-SSM-DEBUG: 16:48:15.962: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 179s (process:2245): libfprint-SSM-DEBUG: 16:48:16.012: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 179s (process:2245): libfprint-SSM-DEBUG: 16:48:16.012: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 179s (process:2245): libfprint-SSM-DEBUG: 16:48:16.013: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 179s (process:2245): libfprint-SSM-DEBUG: 16:48:16.013: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5 179s (process:2245): libfprint-SSM-DEBUG: 16:48:16.013: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 179s (process:2245): libfprint-SSM-DEBUG: 16:48:16.063: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 179s (process:2245): libfprint-SSM-DEBUG: 16:48:16.063: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 179s (process:2245): libfprint-SSM-DEBUG: 16:48:16.064: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 179s (process:2245): libfprint-SSM-DEBUG: 16:48:16.064: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 6 179s (process:2245): libfprint-SSM-DEBUG: 16:48:16.064: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 179s (process:2245): libfprint-SSM-DEBUG: 16:48:16.065: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 179s (process:2245): libfprint-SSM-DEBUG: 16:48:16.065: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 179s (process:2245): libfprint-device-DEBUG: 16:48:16.065: Device reported enroll progress, reported 4 of 10 have been completed 179s (process:2245): libfprint-focaltech_moc-DEBUG: 16:48:16.065: focaltechmoc remain: 6 179s (process:2245): libfprint-SSM-DEBUG: 16:48:16.065: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 179s (process:2245): libfprint-SSM-DEBUG: 16:48:16.065: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 179s (process:2245): libfprint-SSM-DEBUG: 16:48:16.066: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 179s (process:2245): libfprint-SSM-DEBUG: 16:48:16.066: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 179s (process:2245): libfprint-SSM-DEBUG: 16:48:16.066: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5 179s (process:2245): libfprint-SSM-DEBUG: 16:48:16.066: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 179s (process:2245): libfprint-SSM-DEBUG: 16:48:16.116: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 179s (process:2245): libfprint-SSM-DEBUG: 16:48:16.116: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 179s (process:2245): libfprint-SSM-DEBUG: 16:48:16.117: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 179s (process:2245): libfprint-SSM-DEBUG: 16:48:16.117: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5 179s (process:2245): libfprint-SSM-DEBUG: 16:48:16.117: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 179s (process:2245): libfprint-SSM-DEBUG: 16:48:16.168: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 179s (process:2245): libfprint-SSM-DEBUG: 16:48:16.168: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 179s (process:2245): libfprint-SSM-DEBUG: 16:48:16.168: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 179s (process:2245): libfprint-SSM-DEBUG: 16:48:16.169: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5 179s (process:2245): libfprint-SSM-DEBUG: 16:48:16.169: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 179s (process:2245): libfprint-SSM-DEBUG: 16:48:16.219: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 179s (process:2245): libfprint-SSM-DEBUG: 16:48:16.219: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 179s (process:2245): libfprint-SSM-DEBUG: 16:48:16.219: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 179s (process:2245): libfprint-SSM-DEBUG: 16:48:16.220: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 6 179s (process:2245): libfprint-SSM-DEBUG: 16:48:16.220: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 179s (process:2245): libfprint-SSM-DEBUG: 16:48:16.220: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 179s (process:2245): libfprint-SSM-DEBUG: 16:48:16.220: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 179s (process:2245): libfprint-device-DEBUG: 16:48:16.221: Device reported enroll progress, reported 5 of 10 have been completed 179s (process:2245): libfprint-focaltech_moc-DEBUG: 16:48:16.221: focaltechmoc remain: 5 179s (process:2245): libfprint-SSM-DEBUG: 16:48:16.221: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 179s (process:2245): libfprint-SSM-DEBUG: 16:48:16.221: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 179s (process:2245): libfprint-SSM-DEBUG: 16:48:16.221: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 179s (process:2245): libfprint-SSM-DEBUG: 16:48:16.221: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 179s (process:2245): libfprint-SSM-DEBUG: 16:48:16.222: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5 179s (process:2245): libfprint-SSM-DEBUG: 16:48:16.222: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 179s (process:2245): libfprint-SSM-DEBUG: 16:48:16.272: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 179s (process:2245): libfprint-SSM-DEBUG: 16:48:16.272: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 179s (process:2245): libfprint-SSM-DEBUG: 16:48:16.273: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 179s (process:2245): libfprint-SSM-DEBUG: 16:48:16.273: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5 179s (process:2245): libfprint-SSM-DEBUG: 16:48:16.273: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 179s (process:2245): libfprint-SSM-DEBUG: 16:48:16.323: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 179s (process:2245): libfprint-SSM-DEBUG: 16:48:16.323: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 179s (process:2245): libfprint-SSM-DEBUG: 16:48:16.324: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 179s (process:2245): libfprint-SSM-DEBUG: 16:48:16.324: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5 179s (process:2245): libfprint-SSM-DEBUG: 16:48:16.324: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 179s (process:2245): libfprint-SSM-DEBUG: 16:48:16.374: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 179s (process:2245): libfprint-SSM-DEBUG: 16:48:16.374: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 179s (process:2245): libfprint-SSM-DEBUG: 16:48:16.375: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 179s (process:2245): libfprint-SSM-DEBUG: 16:48:16.375: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5 179s (process:2245): libfprint-SSM-DEBUG: 16:48:16.375: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 179s (process:2245): libfprint-SSM-DEBUG: 16:48:16.426: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 179s (process:2245): libfprint-SSM-DEBUG: 16:48:16.426: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 179s (process:2245): libfprint-SSM-DEBUG: 16:48:16.426: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 179s (process:2245): libfprint-SSM-DEBUG: 16:48:16.427: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 6 179s (process:2245): libfprint-SSM-DEBUG: 16:48:16.427: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 179s (process:2245): libfprint-SSM-DEBUG: 16:48:16.427: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 179s (process:2245): libfprint-SSM-DEBUG: 16:48:16.427: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 179s (process:2245): libfprint-device-DEBUG: 16:48:16.428: Device reported enroll progress, reported 6 of 10 have been completed 179s (process:2245): libfprint-focaltech_moc-DEBUG: 16:48:16.428: focaltechmoc remain: 4 179s (process:2245): libfprint-SSM-DEBUG: 16:48:16.428: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 179s (process:2245): libfprint-SSM-DEBUG: 16:48:16.428: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 179s (process:2245): libfprint-SSM-DEBUG: 16:48:16.428: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 179s (process:2245): libfprint-SSM-DEBUG: 16:48:16.428: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 179s (process:2245): libfprint-SSM-DEBUG: 16:48:16.429: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 6 179s (process:2245): libfprint-SSM-DEBUG: 16:48:16.429: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 179s (process:2245): libfprint-SSM-DEBUG: 16:48:16.429: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 179s (process:2245): libfprint-SSM-DEBUG: 16:48:16.429: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 179s (process:2245): libfprint-device-DEBUG: 16:48:16.429: Device reported enroll progress, reported 6 of 10 have been completed 179s (process:2245): libfprint-SSM-DEBUG: 16:48:16.430: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 179s (process:2245): libfprint-SSM-DEBUG: 16:48:16.430: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 179s (process:2245): libfprint-SSM-DEBUG: 16:48:16.430: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 179s (process:2245): libfprint-SSM-DEBUG: 16:48:16.430: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 179s (process:2245): libfprint-SSM-DEBUG: 16:48:16.430: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5 179s (process:2245): libfprint-SSM-DEBUG: 16:48:16.430: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 179s (process:2245): libfprint-SSM-DEBUG: 16:48:16.481: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 179s (process:2245): libfprint-SSM-DEBUG: 16:48:16.481: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 179s (process:2245): libfprint-SSM-DEBUG: 16:48:16.481: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 179s (process:2245): libfprint-SSM-DEBUG: 16:48:16.482: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5 179s (process:2245): libfprint-SSM-DEBUG: 16:48:16.482: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 179s (process:2245): libfprint-SSM-DEBUG: 16:48:16.532: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 179s (process:2245): libfprint-SSM-DEBUG: 16:48:16.532: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 179s (process:2245): libfprint-SSM-DEBUG: 16:48:16.532: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 179s (process:2245): libfprint-SSM-DEBUG: 16:48:16.533: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5 179s (process:2245): libfprint-SSM-DEBUG: 16:48:16.533: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 179s (process:2245): libfprint-SSM-DEBUG: 16:48:16.583: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 179s (process:2245): libfprint-SSM-DEBUG: 16:48:16.583: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 179s (process:2245): libfprint-SSM-DEBUG: 16:48:16.584: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 179s (process:2245): libfprint-SSM-DEBUG: 16:48:16.584: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5 179s (process:2245): libfprint-SSM-DEBUG: 16:48:16.584: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 179s (process:2245): libfprint-SSM-DEBUG: 16:48:16.634: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 179s (process:2245): libfprint-SSM-DEBUG: 16:48:16.634: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 179s (process:2245): libfprint-SSM-DEBUG: 16:48:16.635: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 179s (process:2245): libfprint-SSM-DEBUG: 16:48:16.635: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 6 179s (process:2245): libfprint-SSM-DEBUG: 16:48:16.635: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 179s (process:2245): libfprint-SSM-DEBUG: 16:48:16.636: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 179s (process:2245): libfprint-SSM-DEBUG: 16:48:16.636: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 179s (process:2245): libfprint-device-DEBUG: 16:48:16.636: Device reported enroll progress, reported 7 of 10 have been completed 179s (process:2245): libfprint-focaltech_moc-DEBUG: 16:48:16.636: focaltechmoc remain: 3 179s (process:2245): libfprint-SSM-DEBUG: 16:48:16.636: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 179s (process:2245): libfprint-SSM-DEBUG: 16:48:16.636: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 179s (process:2245): libfprint-SSM-DEBUG: 16:48:16.637: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 179s (process:2245): libfprint-SSM-DEBUG: 16:48:16.637: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 179s (process:2245): libfprint-SSM-DEBUG: 16:48:16.637: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5 179s (process:2245): libfprint-SSM-DEBUG: 16:48:16.637: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 179s (process:2245): libfprint-SSM-DEBUG: 16:48:16.687: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 179s (process:2245): libfprint-SSM-DEBUG: 16:48:16.687: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 179s (process:2245): libfprint-SSM-DEBUG: 16:48:16.688: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 179s (process:2245): libfprint-SSM-DEBUG: 16:48:16.688: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5 179s (process:2245): libfprint-SSM-DEBUG: 16:48:16.688: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 179s (process:2245): libfprint-SSM-DEBUG: 16:48:16.738: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 179s (process:2245): libfprint-SSM-DEBUG: 16:48:16.739: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 179s (process:2245): libfprint-SSM-DEBUG: 16:48:16.739: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 179s (process:2245): libfprint-SSM-DEBUG: 16:48:16.740: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 6 179s (process:2245): libfprint-SSM-DEBUG: 16:48:16.740: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 179s (process:2245): libfprint-SSM-DEBUG: 16:48:16.740: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 179s (process:2245): libfprint-SSM-DEBUG: 16:48:16.740: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 179s (process:2245): libfprint-device-DEBUG: 16:48:16.741: Device reported enroll progress, reported 8 of 10 have been completed 179s (process:2245): libfprint-focaltech_moc-DEBUG: 16:48:16.741: focaltechmoc remain: 2 179s (process:2245): libfprint-SSM-DEBUG: 16:48:16.741: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 179s (process:2245): libfprint-SSM-DEBUG: 16:48:16.741: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 179s (process:2245): libfprint-SSM-DEBUG: 16:48:16.741: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 179s (process:2245): libfprint-SSM-DEBUG: 16:48:16.741: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 179s (process:2245): libfprint-SSM-DEBUG: 16:48:16.742: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5 179s (process:2245): libfprint-SSM-DEBUG: 16:48:16.742: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 179s (process:2245): libfprint-SSM-DEBUG: 16:48:16.792: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 179s (process:2245): libfprint-SSM-DEBUG: 16:48:16.792: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 179s (process:2245): libfprint-SSM-DEBUG: 16:48:16.792: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 179s (process:2245): libfprint-SSM-DEBUG: 16:48:16.793: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 6 179s (process:2245): libfprint-SSM-DEBUG: 16:48:16.793: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 179s (process:2245): libfprint-SSM-DEBUG: 16:48:16.793: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 179s (process:2245): libfprint-SSM-DEBUG: 16:48:16.793: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 179s (process:2245): libfprint-device-DEBUG: 16:48:16.794: Device reported enroll progress, reported 9 of 10 have been completed 179s (process:2245): libfprint-focaltech_moc-DEBUG: 16:48:16.794: focaltechmoc remain: 1 179s (process:2245): libfprint-SSM-DEBUG: 16:48:16.794: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 179s (process:2245): libfprint-SSM-DEBUG: 16:48:16.794: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 179s (process:2245): libfprint-SSM-DEBUG: 16:48:16.794: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 179s (process:2245): libfprint-SSM-DEBUG: 16:48:16.794: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 179s (process:2245): libfprint-SSM-DEBUG: 16:48:16.795: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5 179s (process:2245): libfprint-SSM-DEBUG: 16:48:16.795: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 179s (process:2245): libfprint-SSM-DEBUG: 16:48:16.845: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 179s (process:2245): libfprint-SSM-DEBUG: 16:48:16.845: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 179s (process:2245): libfprint-SSM-DEBUG: 16:48:16.845: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 179s (process:2245): libfprint-SSM-DEBUG: 16:48:16.846: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 6 179s (process:2245): libfprint-SSM-DEBUG: 16:48:16.846: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 179s (process:2245): libfprint-SSM-DEBUG: 16:48:16.846: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 179s (process:2245): libfprint-SSM-DEBUG: 16:48:16.846: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 179s (process:2245): libfprint-device-DEBUG: 16:48:16.847: Device reported enroll progress, reported 10 of 10 have been completed 179s (process:2245): libfprint-focaltech_moc-DEBUG: 16:48:16.847: focaltechmoc remain: 0 179s (process:2245): libfprint-SSM-DEBUG: 16:48:16.847: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 7 179s (process:2245): libfprint-SSM-DEBUG: 16:48:16.847: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 179s (process:2245): libfprint-SSM-DEBUG: 16:48:16.847: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 179s (process:2245): libfprint-SSM-DEBUG: 16:48:16.847: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 179s (process:2245): libfprint-SSM-DEBUG: 16:48:16.848: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 8 179s (process:2245): libfprint-SSM-DEBUG: 16:48:16.848: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 179s (process:2245): libfprint-SSM-DEBUG: 16:48:16.848: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 179s (process:2245): libfprint-SSM-DEBUG: 16:48:16.848: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 179s (process:2245): libfprint-focaltech_moc-DEBUG: 16:48:16.849: focaltech_moc_commit_cb success 179s (process:2245): libfprint-focaltech_moc-DEBUG: 16:48:16.849: Enrollment was successful! 179s (process:2245): libfprint-device-DEBUG: 16:48:16.849: Device reported enroll completion 179s (process:2245): libfprint-device-DEBUG: 16:48:16.849: Print for finger FP_FINGER_UNKNOWN enrolled 179s (process:2245): libfprint-SSM-DEBUG: 16:48:16.849: [focaltech_moc] MOC_ENROLL_NUM_STATES completed successfully 179s (process:2245): libfprint-SSM-DEBUG: 16:48:16.849: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 179s (process:2245): libfprint-device-DEBUG: 16:48:16.849: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 179s (process:2245): libfprint-device-DEBUG: 16:48:16.849: Not updating temperature model, device can run continuously! 179s (process:2245): libfprint-SSM-DEBUG: 16:48:16.849: [focaltech_moc] MOC_LIST_NUM_STATES entering state 0 179s (process:2245): libfprint-SSM-DEBUG: 16:48:16.849: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 179s (process:2245): libfprint-SSM-DEBUG: 16:48:16.849: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 179s (process:2245): libfprint-SSM-DEBUG: 16:48:16.850: [focaltech_moc] MOC_LIST_NUM_STATES entering state 1 179s (process:2245): libfprint-SSM-DEBUG: 16:48:16.850: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 179s (process:2245): libfprint-SSM-DEBUG: 16:48:16.850: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 179s (process:2245): libfprint-SSM-DEBUG: 16:48:16.850: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 179s (process:2245): libfprint-focaltech_moc-DEBUG: 16:48:16.851: focaltechmoc add slot: 0 179s (process:2245): libfprint-focaltech_moc-DEBUG: 16:48:16.851: FP1-00000000-0-00000000-nobody 179s (process:2245): libfprint-SSM-DEBUG: 16:48:16.851: [focaltech_moc] MOC_LIST_NUM_STATES entering state 2 179s (process:2245): libfprint-device-DEBUG: 16:48:16.851: Device reported listing completion 179s (process:2245): libfprint-SSM-DEBUG: 16:48:16.851: [focaltech_moc] MOC_LIST_NUM_STATES completed successfully 179s (process:2245): libfprint-SSM-DEBUG: 16:48:16.851: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 179s (process:2245): libfprint-device-DEBUG: 16:48:16.851: Completing action FPI_DEVICE_ACTION_LIST in idle! 179s (process:2245): libfprint-device-DEBUG: 16:48:16.851: Not updating temperature model, device can run continuously! 179s (process:2245): libfprint-device-DEBUG: 16:48:16.851: Not updating temperature model, device can run continuously! 179s (process:2245): libfprint-SSM-DEBUG: 16:48:16.851: [focaltech_moc] MOC_IDENTIFY_NUM_STATES entering state 0 179s (process:2245): libfprint-SSM-DEBUG: 16:48:16.851: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 179s (process:2245): libfprint-SSM-DEBUG: 16:48:16.852: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 179s (process:2245): libfprint-SSM-DEBUG: 16:48:16.852: [focaltech_moc] MOC_IDENTIFY_NUM_STATES entering state 1 179s (process:2245): libfprint-SSM-DEBUG: 16:48:16.852: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 179s (process:2245): libfprint-SSM-DEBUG: 16:48:16.852: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 179s (process:2245): libfprint-SSM-DEBUG: 16:48:16.853: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 179s (process:2245): libfprint-SSM-DEBUG: 16:48:16.853: [focaltech_moc] MOC_IDENTIFY_NUM_STATES entering state 2 179s (process:2245): libfprint-SSM-DEBUG: 16:48:16.853: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 179s (process:2245): libfprint-SSM-DEBUG: 16:48:16.903: [focaltech_moc] MOC_IDENTIFY_NUM_STATES entering state 1 179s (process:2245): libfprint-SSM-DEBUG: 16:48:16.903: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 179s (process:2245): libfprint-SSM-DEBUG: 16:48:16.904: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 179s (process:2245): libfprint-SSM-DEBUG: 16:48:16.904: [focaltech_moc] MOC_IDENTIFY_NUM_STATES entering state 2 179s (process:2245): libfprint-SSM-DEBUG: 16:48:16.904: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 179s (process:2245): libfprint-SSM-DEBUG: 16:48:16.954: [focaltech_moc] MOC_IDENTIFY_NUM_STATES entering state 1 179s (process:2245): libfprint-SSM-DEBUG: 16:48:16.954: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 179s (process:2245): libfprint-SSM-DEBUG: 16:48:16.955: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 179s (process:2245): libfprint-SSM-DEBUG: 16:48:16.955: [focaltech_moc] MOC_IDENTIFY_NUM_STATES entering state 2 179s (process:2245): libfprint-SSM-DEBUG: 16:48:16.956: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 180s (process:2245): libfprint-SSM-DEBUG: 16:48:17.006: [focaltech_moc] MOC_IDENTIFY_NUM_STATES entering state 1 180s (process:2245): libfprint-SSM-DEBUG: 16:48:17.006: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 180s (process:2245): libfprint-SSM-DEBUG: 16:48:17.006: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 180s (process:2245): libfprint-SSM-DEBUG: 16:48:17.007: [focaltech_moc] MOC_IDENTIFY_NUM_STATES entering state 2 180s (process:2245): libfprint-SSM-DEBUG: 16:48:17.007: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 180s (process:2245): libfprint-SSM-DEBUG: 16:48:17.057: [focaltech_moc] MOC_IDENTIFY_NUM_STATES entering state 1 180s (process:2245): libfprint-SSM-DEBUG: 16:48:17.057: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 180s (process:2245): libfprint-SSM-DEBUG: 16:48:17.058: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 180s (process:2245): libfprint-SSM-DEBUG: 16:48:17.058: [focaltech_moc] MOC_IDENTIFY_NUM_STATES entering state 3 180s (process:2245): libfprint-SSM-DEBUG: 16:48:17.058: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 180s (process:2245): libfprint-SSM-DEBUG: 16:48:17.058: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 180s (process:2245): libfprint-SSM-DEBUG: 16:48:17.058: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 180s (process:2245): libfprint-SSM-DEBUG: 16:48:17.059: [focaltech_moc] MOC_IDENTIFY_NUM_STATES entering state 4 180s (process:2245): libfprint-SSM-DEBUG: 16:48:17.059: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 180s (process:2245): libfprint-SSM-DEBUG: 16:48:17.059: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 180s (process:2245): libfprint-SSM-DEBUG: 16:48:17.059: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 180s (process:2245): libfprint-device-DEBUG: 16:48:17.060: Device reported verify result 180s (process:2245): libfprint-device-DEBUG: 16:48:17.060: Device reported verify completion 180s (process:2245): libfprint-SSM-DEBUG: 16:48:17.060: [focaltech_moc] MOC_IDENTIFY_NUM_STATES completed successfully 180s (process:2245): libfprint-SSM-DEBUG: 16:48:17.060: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 180s (process:2245): libfprint-device-DEBUG: 16:48:17.060: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 180s (process:2245): libfprint-device-DEBUG: 16:48:17.060: Not updating temperature model, device can run continuously! 180s (process:2245): libfprint-device-DEBUG: 16:48:17.060: Not updating temperature model, device can run continuously! 180s (process:2245): libfprint-SSM-DEBUG: 16:48:17.060: [focaltech_moc] MOC_IDENTIFY_NUM_STATES entering state 0 180s (process:2245): libfprint-SSM-DEBUG: 16:48:17.060: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 180s (process:2245): libfprint-SSM-DEBUG: 16:48:17.061: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 180s (process:2245): libfprint-SSM-DEBUG: 16:48:17.061: [focaltech_moc] MOC_IDENTIFY_NUM_STATES entering state 1 180s (process:2245): libfprint-SSM-DEBUG: 16:48:17.062: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 180s (process:2245): libfprint-SSM-DEBUG: 16:48:17.062: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 180s (process:2245): libfprint-SSM-DEBUG: 16:48:17.062: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 180s (process:2245): libfprint-SSM-DEBUG: 16:48:17.062: [focaltech_moc] MOC_IDENTIFY_NUM_STATES entering state 2 180s (process:2245): libfprint-SSM-DEBUG: 16:48:17.062: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 180s (process:2245): libfprint-SSM-DEBUG: 16:48:17.113: [focaltech_moc] MOC_IDENTIFY_NUM_STATES entering state 1 180s (process:2245): libfprint-SSM-DEBUG: 16:48:17.113: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 180s (process:2245): libfprint-SSM-DEBUG: 16:48:17.113: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 180s (process:2245): libfprint-SSM-DEBUG: 16:48:17.114: [focaltech_moc] MOC_IDENTIFY_NUM_STATES entering state 2 180s (process:2245): libfprint-SSM-DEBUG: 16:48:17.114: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 180s (process:2245): libfprint-SSM-DEBUG: 16:48:17.164: [focaltech_moc] MOC_IDENTIFY_NUM_STATES entering state 1 180s (process:2245): libfprint-SSM-DEBUG: 16:48:17.164: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 180s (process:2245): libfprint-SSM-DEBUG: 16:48:17.164: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 180s (process:2245): libfprint-SSM-DEBUG: 16:48:17.165: [focaltech_moc] MOC_IDENTIFY_NUM_STATES entering state 3 180s (process:2245): libfprint-SSM-DEBUG: 16:48:17.165: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 180s (process:2245): libfprint-SSM-DEBUG: 16:48:17.165: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 180s (process:2245): libfprint-SSM-DEBUG: 16:48:17.165: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 180s (process:2245): libfprint-SSM-DEBUG: 16:48:17.166: [focaltech_moc] MOC_IDENTIFY_NUM_STATES entering state 4 180s (process:2245): libfprint-SSM-DEBUG: 16:48:17.166: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 180s (process:2245): libfprint-SSM-DEBUG: 16:48:17.166: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 180s (process:2245): libfprint-SSM-DEBUG: 16:48:17.166: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 180s (process:2245): libfprint-device-DEBUG: 16:48:17.167: Device reported identify result 180s (process:2245): libfprint-device-DEBUG: 16:48:17.167: Device reported identify completion 180s (process:2245): libfprint-SSM-DEBUG: 16:48:17.167: [focaltech_moc] MOC_IDENTIFY_NUM_STATES completed successfully 180s (process:2245): libfprint-SSM-DEBUG: 16:48:17.167: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 180s (process:2245): libfprint-device-DEBUG: 16:48:17.167: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 180s (process:2245): libfprint-device-DEBUG: 16:48:17.167: Not updating temperature model, device can run continuously! 180s (process:2245): libfprint-SSM-DEBUG: 16:48:17.167: [focaltech_moc] MOC_DELETE_NUM_STATES entering state 0 180s (process:2245): libfprint-SSM-DEBUG: 16:48:17.167: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 180s (process:2245): libfprint-SSM-DEBUG: 16:48:17.168: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 180s (process:2245): libfprint-SSM-DEBUG: 16:48:17.168: [focaltech_moc] MOC_DELETE_NUM_STATES entering state 1 180s (process:2245): libfprint-SSM-DEBUG: 16:48:17.168: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 180s (process:2245): libfprint-SSM-DEBUG: 16:48:17.168: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 180s (process:2245): libfprint-SSM-DEBUG: 16:48:17.169: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 180s (process:2245): libfprint-focaltech_moc-DEBUG: 16:48:17.169: focaltechmoc add slot: 0 180s (process:2245): libfprint-focaltech_moc-DEBUG: 16:48:17.169: FP1-00000000-0-00000000-nobody 180s (process:2245): libfprint-SSM-DEBUG: 16:48:17.169: [focaltech_moc] MOC_DELETE_NUM_STATES entering state 2 180s (process:2245): libfprint-SSM-DEBUG: 16:48:17.169: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 180s (process:2245): libfprint-SSM-DEBUG: 16:48:17.169: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 180s (process:2245): libfprint-SSM-DEBUG: 16:48:17.170: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 180s (process:2245): libfprint-SSM-DEBUG: 16:48:17.170: [focaltech_moc] MOC_DELETE_NUM_STATES entering state 3 180s (process:2245): libfprint-SSM-DEBUG: 16:48:17.170: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 180s (process:2245): libfprint-SSM-DEBUG: 16:48:17.170: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 180s (process:2245): libfprint-SSM-DEBUG: 16:48:17.171: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 180s (process:2245): libfprint-focaltech_moc-DEBUG: 16:48:17.171: delete slot 0 180s (process:2245): libfprint-SSM-DEBUG: 16:48:17.171: [focaltech_moc] MOC_DELETE_NUM_STATES entering state 3 180s (process:2245): libfprint-SSM-DEBUG: 16:48:17.171: [focaltech_moc] MOC_DELETE_NUM_STATES entering state 4 180s (process:2245): libfprint-device-DEBUG: 16:48:17.171: Device reported deletion completion 180s (process:2245): libfprint-SSM-DEBUG: 16:48:17.171: [focaltech_moc] MOC_DELETE_NUM_STATES completed successfully 180s (process:2245): libfprint-SSM-DEBUG: 16:48:17.171: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 180s (process:2245): libfprint-device-DEBUG: 16:48:17.171: Completing action FPI_DEVICE_ACTION_DELETE in idle! 180s (process:2245): libfprint-device-DEBUG: 16:48:17.171: Not updating temperature model, device can run continuously! 180s (process:2245): libfprint-focaltech_moc-DEBUG: 16:48:17.171: Focaltechmoc dev_exit 180s (process:2245): libfprint-SSM-DEBUG: 16:48:17.171: [focaltech_moc] DEV_EXIT_STATES entering state 0 180s (process:2245): libfprint-SSM-DEBUG: 16:48:17.171: [focaltech_moc] DEV_EXIT_STATES completed successfully 180s (process:2245): libfprint-focaltech_moc-DEBUG: 16:48:17.171: class:dc, subclass:a0, protocol:b0 180s (process:2245): libfprint-device-DEBUG: 16:48:17.171: Device reported close completion 180s (process:2245): libfprint-device-DEBUG: 16:48:17.172: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 180s (process:2245): libfprint-device-DEBUG: 16:48:17.172: Not updating temperature model, device can run continuously! 180s enrolling 180s finger status: 180s enroll progress: (<__gi__.FpiDeviceFocaltechMoc object at 0xe19925f00a40 (FpiDeviceFocaltechMoc at 0xff20540)>, 1, None, None, None) 180s finger status: 180s enroll progress: (<__gi__.FpiDeviceFocaltechMoc object at 0xe19925f00a40 (FpiDeviceFocaltechMoc at 0xff20540)>, 2, None, None, None) 180s finger status: 180s enroll progress: (<__gi__.FpiDeviceFocaltechMoc object at 0xe19925f00a40 (FpiDeviceFocaltechMoc at 0xff20540)>, 3, None, None, None) 180s finger status: 180s enroll progress: (<__gi__.FpiDeviceFocaltechMoc object at 0xe19925f00a40 (FpiDeviceFocaltechMoc at 0xff20540)>, 4, None, None, None) 180s finger status: 180s enroll progress: (<__gi__.FpiDeviceFocaltechMoc object at 0xe19925f00a40 (FpiDeviceFocaltechMoc at 0xff20540)>, 5, None, None, None) 180s finger status: 180s enroll progress: (<__gi__.FpiDeviceFocaltechMoc object at 0xe19925f00a40 (FpiDeviceFocaltechMoc at 0xff20540)>, 6, None, None, None) 180s finger status: 180s enroll progress: (<__gi__.FpiDeviceFocaltechMoc object at 0xe19925f00a40 (FpiDeviceFocaltechMoc at 0xff20540)>, 6, None, None, GLib.Error('The finger was not centered properly, please try again.', 'fp - device - retry - quark', 2)) 180s finger status: 180s enroll progress: (<__gi__.FpiDeviceFocaltechMoc object at 0xe19925f00a40 (FpiDeviceFocaltechMoc at 0xff20540)>, 7, None, None, None) 180s finger status: 180s enroll progress: (<__gi__.FpiDeviceFocaltechMoc object at 0xe19925f00a40 (FpiDeviceFocaltechMoc at 0xff20540)>, 8, None, None, None) 180s finger status: 180s enroll progress: (<__gi__.FpiDeviceFocaltechMoc object at 0xe19925f00a40 (FpiDeviceFocaltechMoc at 0xff20540)>, 9, None, None, None) 180s finger status: 180s enroll progress: (<__gi__.FpiDeviceFocaltechMoc object at 0xe19925f00a40 (FpiDeviceFocaltechMoc at 0xff20540)>, 10, None, None, None) 180s enroll done 180s listing 180s listing done 180s verifying 180s verify done 180s async identifying 180s indentification_done: 180s deleting 180s delete done 180s ** (umockdev-run:2241): DEBUG: 16:48:17.184: umockdev.vala:150: Removing test bed /tmp/umockdev.Y2EFK2 180s (umockdev-run:2241): GLib-DEBUG: 16:48:17.190: unsetenv() is not thread-safe and should not be used after threads are created 180s PASS: libfprint-2/driver-focaltech_moc.test 180s Running test: libfprint-2/tod-fp-device-tod-fake_test_dev_tod_current.test 180s TAP version 13 180s # random seed: R02S6ab5dcdc93198b6346d07f969cff598c 180s 1..14 180s # Start of device tests 180s # Start of async tests 180s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.7+tod1) 180s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/current/libdevice-fake-tod-driver.so 180s # libfprint-tod-DEBUG: Found TOD entry point symbol 0xe64e00fa2580, GType is 203302864013008 180s # libfprint-tod-DEBUG: Loading driver fake_test_dev_tod_current (Virtual device for debugging) 180s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0003 180s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 180s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0002 180s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_FAKE_DEVICE, yes 180s # libfprint-context-DEBUG: created 180s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_probe: Device Virtual device for debugging in action FPI_DEVICE_ACTION_PROBE 180s # 180s # libfprint-device-DEBUG: Device reported probe completion 180s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 180s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 180s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 180s # 180s # libfprint-device-DEBUG: Device reported open completion 180s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 180s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 180s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 180s # 180s # libfprint-device-DEBUG: Device reported close completion 180s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 180s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 180s ok 1 /device/async/open 180s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.7+tod1) 180s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/current/libdevice-fake-tod-driver.so 180s # libfprint-tod-DEBUG: Found TOD entry point symbol 0xe64e00fa2580, GType is 203302864013008 180s # libfprint-tod-DEBUG: Loading driver fake_test_dev_tod_current (Virtual device for debugging) 180s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0003 180s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 180s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0002 180s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_FAKE_DEVICE, yes 180s # libfprint-context-DEBUG: created 180s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_probe: Device Virtual device for debugging in action FPI_DEVICE_ACTION_PROBE 180s # 180s # libfprint-device-DEBUG: Device reported probe completion 180s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 180s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 180s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 180s # 180s # libfprint-device-DEBUG: Device reported open completion 180s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 180s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 180s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 180s # 180s # libfprint-device-DEBUG: Device reported close completion 180s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 180s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 180s ok 2 /device/async/close 180s # End of async tests 180s # Start of sync tests 180s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.7+tod1) 180s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/current/libdevice-fake-tod-driver.so 180s # libfprint-tod-DEBUG: Found TOD entry point symbol 0xe64e00fa2580, GType is 203302864013008 180s # libfprint-tod-DEBUG: Loading driver fake_test_dev_tod_current (Virtual device for debugging) 180s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0003 180s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 180s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0002 180s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_FAKE_DEVICE, yes 180s # libfprint-context-DEBUG: created 180s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_probe: Device Virtual device for debugging in action FPI_DEVICE_ACTION_PROBE 180s # 180s # libfprint-device-DEBUG: Device reported probe completion 180s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 180s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 180s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 180s # 180s # libfprint-device-DEBUG: Device reported open completion 180s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 180s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 180s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 180s # 180s # libfprint-device-DEBUG: Device reported close completion 180s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 180s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 180s ok 3 /device/sync/open 180s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.7+tod1) 180s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/current/libdevice-fake-tod-driver.so 180s # libfprint-tod-DEBUG: Found TOD entry point symbol 0xe64e00fa2580, GType is 203302864013008 180s # libfprint-tod-DEBUG: Loading driver fake_test_dev_tod_current (Virtual device for debugging) 180s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0003 180s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 180s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0002 180s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_FAKE_DEVICE, yes 180s # libfprint-context-DEBUG: created 180s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_probe: Device Virtual device for debugging in action FPI_DEVICE_ACTION_PROBE 180s # 180s # libfprint-device-DEBUG: Device reported probe completion 180s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 180s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 180s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 180s # 180s # libfprint-device-DEBUG: Device reported open completion 180s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 180s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 180s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 180s # 180s # libfprint-device-DEBUG: Device reported close completion 180s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 180s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 180s ok 4 /device/sync/close 180s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.7+tod1) 180s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/current/libdevice-fake-tod-driver.so 180s # libfprint-tod-DEBUG: Found TOD entry point symbol 0xe64e00fa2580, GType is 203302864013008 180s # libfprint-tod-DEBUG: Loading driver fake_test_dev_tod_current (Virtual device for debugging) 180s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0003 180s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 180s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0002 180s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_FAKE_DEVICE, yes 180s # libfprint-context-DEBUG: created 180s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_probe: Device Virtual device for debugging in action FPI_DEVICE_ACTION_PROBE 180s # 180s # libfprint-device-DEBUG: Device reported probe completion 180s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 180s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 180s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 180s # 180s # libfprint-device-DEBUG: Device reported open completion 180s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 180s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 180s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 180s # 180s # libfprint-device-DEBUG: Device reported close completion 180s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 180s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 180s ok 5 /device/sync/get_driver 180s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.7+tod1) 180s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/current/libdevice-fake-tod-driver.so 180s # libfprint-tod-DEBUG: Found TOD entry point symbol 0xe64e00fa2580, GType is 203302864013008 180s # libfprint-tod-DEBUG: Loading driver fake_test_dev_tod_current (Virtual device for debugging) 180s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0003 180s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 180s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0002 180s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_FAKE_DEVICE, yes 180s # libfprint-context-DEBUG: created 180s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_probe: Device Virtual device for debugging in action FPI_DEVICE_ACTION_PROBE 180s # 180s # libfprint-device-DEBUG: Device reported probe completion 180s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 180s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 180s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 180s # 180s # libfprint-device-DEBUG: Device reported open completion 180s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 180s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 180s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 180s # 180s # libfprint-device-DEBUG: Device reported close completion 180s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 180s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 180s ok 6 /device/sync/get_device_id 180s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.7+tod1) 180s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/current/libdevice-fake-tod-driver.so 180s # libfprint-tod-DEBUG: Found TOD entry point symbol 0xe64e00fa2580, GType is 203302864013008 180s # libfprint-tod-DEBUG: Loading driver fake_test_dev_tod_current (Virtual device for debugging) 180s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0003 180s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 180s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0002 180s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_FAKE_DEVICE, yes 180s # libfprint-context-DEBUG: created 180s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_probe: Device Virtual device for debugging in action FPI_DEVICE_ACTION_PROBE 180s # 180s # libfprint-device-DEBUG: Device reported probe completion 180s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 180s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 180s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 180s # 180s # libfprint-device-DEBUG: Device reported open completion 180s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 180s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 180s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 180s # 180s # libfprint-device-DEBUG: Device reported close completion 180s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 180s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 180s ok 7 /device/sync/get_name 180s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.7+tod1) 180s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/current/libdevice-fake-tod-driver.so 180s # libfprint-tod-DEBUG: Found TOD entry point symbol 0xe64e00fa2580, GType is 203302864013008 180s # libfprint-tod-DEBUG: Loading driver fake_test_dev_tod_current (Virtual device for debugging) 180s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0003 180s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 180s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0002 180s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_FAKE_DEVICE, yes 180s # libfprint-context-DEBUG: created 180s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_probe: Device Virtual device for debugging in action FPI_DEVICE_ACTION_PROBE 180s # 180s # libfprint-device-DEBUG: Device reported probe completion 180s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 180s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 180s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 180s # 180s # libfprint-device-DEBUG: Device reported open completion 180s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 180s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 180s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 180s # 180s # libfprint-device-DEBUG: Device reported close completion 180s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 180s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 180s ok 8 /device/sync/get_scan_type 180s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.7+tod1) 180s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/current/libdevice-fake-tod-driver.so 180s # libfprint-tod-DEBUG: Found TOD entry point symbol 0xe64e00fa2580, GType is 203302864013008 180s # libfprint-tod-DEBUG: Loading driver fake_test_dev_tod_current (Virtual device for debugging) 180s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0003 180s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 180s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0002 180s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_FAKE_DEVICE, yes 180s # libfprint-context-DEBUG: created 180s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_probe: Device Virtual device for debugging in action FPI_DEVICE_ACTION_PROBE 180s # 180s # libfprint-device-DEBUG: Device reported probe completion 180s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 180s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 180s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 180s # 180s # libfprint-device-DEBUG: Device reported open completion 180s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 180s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 180s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 180s # 180s # libfprint-device-DEBUG: Device reported close completion 180s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 180s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 180s ok 9 /device/sync/get_nr_enroll_stages 180s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.7+tod1) 180s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/current/libdevice-fake-tod-driver.so 180s # libfprint-tod-DEBUG: Found TOD entry point symbol 0xe64e00fa2580, GType is 203302864013008 180s # libfprint-tod-DEBUG: Loading driver fake_test_dev_tod_current (Virtual device for debugging) 180s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0003 180s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 180s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0002 180s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_FAKE_DEVICE, yes 180s # libfprint-context-DEBUG: created 180s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_probe: Device Virtual device for debugging in action FPI_DEVICE_ACTION_PROBE 180s # 180s # libfprint-device-DEBUG: Device reported probe completion 180s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 180s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 180s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 180s # 180s # libfprint-device-DEBUG: Device reported open completion 180s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 180s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 180s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 180s # 180s # libfprint-device-DEBUG: Device reported close completion 180s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 180s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 180s ok 10 /device/sync/supports_identify 180s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.7+tod1) 180s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/current/libdevice-fake-tod-driver.so 180s # libfprint-tod-DEBUG: Found TOD entry point symbol 0xe64e00fa2580, GType is 203302864013008 180s # libfprint-tod-DEBUG: Loading driver fake_test_dev_tod_current (Virtual device for debugging) 180s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0003 180s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 180s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0002 180s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_FAKE_DEVICE, yes 180s # libfprint-context-DEBUG: created 180s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_probe: Device Virtual device for debugging in action FPI_DEVICE_ACTION_PROBE 180s # 180s # libfprint-device-DEBUG: Device reported probe completion 180s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 180s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 180s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 180s # 180s # libfprint-device-DEBUG: Device reported open completion 180s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 180s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 180s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 180s # 180s # libfprint-device-DEBUG: Device reported close completion 180s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 180s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 180s ok 11 /device/sync/supports_capture 180s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.7+tod1) 180s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/current/libdevice-fake-tod-driver.so 180s # libfprint-tod-DEBUG: Found TOD entry point symbol 0xe64e00fa2580, GType is 203302864013008 180s # libfprint-tod-DEBUG: Loading driver fake_test_dev_tod_current (Virtual device for debugging) 180s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0003 180s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 180s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0002 180s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_FAKE_DEVICE, yes 180s # libfprint-context-DEBUG: created 180s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_probe: Device Virtual device for debugging in action FPI_DEVICE_ACTION_PROBE 180s # 180s # libfprint-device-DEBUG: Device reported probe completion 180s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 180s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 180s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 180s # 180s # libfprint-device-DEBUG: Device reported open completion 180s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 180s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 180s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 180s # 180s # libfprint-device-DEBUG: Device reported close completion 180s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 180s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 180s ok 12 /device/sync/has_storage 180s # Start of open tests 180s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.7+tod1) 180s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/current/libdevice-fake-tod-driver.so 180s # libfprint-tod-DEBUG: Found TOD entry point symbol 0xe64e00fa2580, GType is 203302864013008 180s # libfprint-tod-DEBUG: Loading driver fake_test_dev_tod_current (Virtual device for debugging) 180s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0003 180s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 180s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0002 180s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_FAKE_DEVICE, yes 180s # libfprint-context-DEBUG: created 180s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_probe: Device Virtual device for debugging in action FPI_DEVICE_ACTION_PROBE 180s # 180s # libfprint-device-DEBUG: Device reported probe completion 180s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 180s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 180s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 180s # 180s # libfprint-device-DEBUG: Device reported open completion 180s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 180s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 180s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 180s # 180s # libfprint-device-DEBUG: Device reported close completion 180s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 180s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 180s ok 13 /device/sync/open/notify 180s # End of open tests 180s # Start of close tests 180s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.7+tod1) 180s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/current/libdevice-fake-tod-driver.so 180s # libfprint-tod-DEBUG: Found TOD entry point symbol 0xe64e00fa2580, GType is 203302864013008 180s # libfprint-tod-DEBUG: Loading driver fake_test_dev_tod_current (Virtual device for debugging) 180s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0003 180s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 180s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0002 180s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_FAKE_DEVICE, yes 180s # libfprint-context-DEBUG: created 180s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_probe: Device Virtual device for debugging in action FPI_DEVICE_ACTION_PROBE 180s # 180s # libfprint-device-DEBUG: Device reported probe completion 180s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 180s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 180s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 180s # 180s # libfprint-device-DEBUG: Device reported open completion 180s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 180s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 180s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 180s # 180s # libfprint-device-DEBUG: Device reported close completion 180s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 180s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 180s ok 14 /device/sync/close/notify 180s # End of close tests 180s # End of sync tests 180s # End of device tests 180s PASS: libfprint-2/tod-fp-device-tod-fake_test_dev_tod_current.test 180s Running test: libfprint-2/driver-nb1010.test 180s ** (umockdev-run:2285): DEBUG: 16:48:17.291: umockdev.vala:123: Created udev test bed /tmp/umockdev.RFE8J2 180s ** (umockdev-run:2285): DEBUG: 16:48:17.291: umockdev.vala:1297: parsing device description for /devices/pci0000:00/0000:00:01.3/0000:02:00.0/usb1/1-7 180s ** (umockdev-run:2285): DEBUG: 16:48:17.294: umockdev.vala:1366: creating device /devices/pci0000:00/0000:00:01.3/0000:02:00.0/usb1/1-7 (subsystem usb) 180s ** (umockdev-run:2285): DEBUG: 16:48:17.297: umockdev.vala:1411: create_node_for_device: creating file device /tmp/umockdev.RFE8J2/dev/bus/usb/001/003 180s ** (umockdev-run:2285): DEBUG: 16:48:17.297: umockdev.vala:1297: parsing device description for /devices/pci0000:00/0000:00:01.3/0000:02:00.0/usb1 180s ** (umockdev-run:2285): DEBUG: 16:48:17.301: umockdev.vala:1366: creating device /devices/pci0000:00/0000:00:01.3/0000:02:00.0/usb1 (subsystem usb) 180s ** (umockdev-run:2285): DEBUG: 16:48:17.303: umockdev.vala:1411: create_node_for_device: creating file device /tmp/umockdev.RFE8J2/dev/bus/usb/001/001 180s ** (umockdev-run:2285): DEBUG: 16:48:17.303: umockdev.vala:1297: parsing device description for /devices/pci0000:00/0000:00:01.3/0000:02:00.0 180s ** (umockdev-run:2285): DEBUG: 16:48:17.305: umockdev.vala:1366: creating device /devices/pci0000:00/0000:00:01.3/0000:02:00.0 (subsystem pci) 180s ** (umockdev-run:2285): DEBUG: 16:48:17.307: umockdev.vala:1297: parsing device description for /devices/pci0000:00/0000:00:01.3 180s ** (umockdev-run:2285): DEBUG: 16:48:17.307: umockdev.vala:1366: creating device /devices/pci0000:00/0000:00:01.3 (subsystem pci) 180s (umockdev-run:2285): GLib-GIO-DEBUG: 16:48:17.309: _g_io_module_get_default: Found default implementation local (GLocalVfs) for ?gio-vfs? 180s (process:2289): libfprint-context-DEBUG: 16:48:17.363: Initializing FpContext (libfprint version 1.94.7+tod1) 180s (process:2289): libfprint-tod-DEBUG: 16:48:17.363: Impossible to load the shared drivers dir Error opening directory “/usr/lib/aarch64-linux-gnu/libfprint-2/tod-1”: No such file or directory 180s (process:2289): libfprint-context-DEBUG: 16:48:17.365: No driver found for USB device 1D6B:0002 180s (process:2289): libfprint-device-DEBUG: 16:48:17.365: Device reported probe completion 180s (process:2289): libfprint-device-DEBUG: 16:48:17.365: Completing action FPI_DEVICE_ACTION_PROBE in idle! 180s (process:2289): libfprint-device-DEBUG: 16:48:17.365: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 180s (process:2289): libfprint-image_device-DEBUG: 16:48:17.366: Image device open completed 180s (process:2289): libfprint-device-DEBUG: 16:48:17.366: Device reported open completion 180s (process:2289): libfprint-nb1010-DEBUG: 16:48:17.366: nb1010 Initialized 180s (process:2289): libfprint-device-DEBUG: 16:48:17.366: Completing action FPI_DEVICE_ACTION_OPEN in idle! 180s (process:2289): libfprint-device-DEBUG: 16:48:17.366: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 180s (process:2289): libfprint-device-DEBUG: 16:48:17.367: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 180s (process:2289): libfprint-image_device-DEBUG: 16:48:17.367: Activating image device 180s (process:2289): libfprint-image_device-DEBUG: 16:48:17.367: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING 180s (process:2289): libfprint-image_device-DEBUG: 16:48:17.367: Image device activation completed 180s (process:2289): libfprint-image_device-DEBUG: 16:48:17.367: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE 180s (process:2289): libfprint-image_device-DEBUG: 16:48:17.367: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 180s (process:2289): libfprint-SSM-DEBUG: 16:48:17.367: [nb1010] M_LOOP_NUM_STATES entering state 0 180s (process:2289): libfprint-device-DEBUG: 16:48:17.367: Device reported finger status change: FP_FINGER_STATUS_NEEDED 180s (process:2289): libfprint-nb1010-DEBUG: 16:48:17.367: nb1010 Activated 180s (process:2289): libfprint-SSM-DEBUG: 16:48:17.417: [nb1010] M_LOOP_NUM_STATES entering state 1 180s (process:2289): libfprint-SSM-DEBUG: 16:48:17.417: [nb1010] M_LOOP_NUM_STATES entering state 2 180s (process:2289): libfprint-SSM-DEBUG: 16:48:17.418: [nb1010] M_LOOP_NUM_STATES entering state 3 180s (process:2289): libfprint-device-DEBUG: 16:48:17.418: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 180s (process:2289): libfprint-image_device-DEBUG: 16:48:17.418: Image device reported finger status: on 180s (process:2289): libfprint-image_device-DEBUG: 16:48:17.418: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 180s (process:2289): libfprint-SSM-DEBUG: 16:48:17.419: [nb1010] M_LOOP_NUM_STATES entering state 4 180s (process:2289): libfprint-SSM-DEBUG: 16:48:17.420: [nb1010] M_LOOP_NUM_STATES entering state 5 180s (process:2289): libfprint-SSM-DEBUG: 16:48:17.457: [nb1010] M_LOOP_NUM_STATES entering state 6 180s (process:2289): libfprint-image_device-DEBUG: 16:48:17.457: Image device captured an image 180s (process:2289): libfprint-image_device-DEBUG: 16:48:17.459: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 180s (process:2289): libfprint-device-DEBUG: 16:48:17.459: Device reported finger status change: FP_FINGER_STATUS_PRESENT 180s (process:2289): libfprint-SSM-DEBUG: 16:48:17.459: [nb1010] M_LOOP_NUM_STATES completed successfully 180s (process:2289): libfprint-nb1010-DEBUG: 16:48:17.459: nb1010 ssm complete cb 180s (process:2289): libfprint-device-DEBUG: 16:48:17.459: Device reported finger status change: FP_FINGER_STATUS_NONE 180s (process:2289): libfprint-image_device-DEBUG: 16:48:17.459: Image device reported finger status: off 180s (process:2289): libfprint-image_device-DEBUG: 16:48:17.459: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 180s (process:2289): libfprint-image_device-DEBUG: 16:48:17.459: Deactivating image device 180s (process:2289): libfprint-image_device-DEBUG: 16:48:17.459: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_DEACTIVATING 180s (process:2289): libfprint-image_device-DEBUG: 16:48:17.459: Image device deactivation completed 180s (process:2289): libfprint-image_device-DEBUG: 16:48:17.459: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE 180s (process:2289): libfprint-nb1010-DEBUG: 16:48:17.459: nb1010 Deactivated 180s (process:2289): libfprint-device-DEBUG: 16:48:17.467: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 180s (process:2289): libfprint-image-DEBUG: 16:48:17.472: Minutiae scan completed in 0.014498 secs 180s (process:2289): libfprint-device-DEBUG: 16:48:17.472: Device reported capture completion 180s (process:2289): libfprint-device-DEBUG: 16:48:17.472: Completing action FPI_DEVICE_ACTION_CAPTURE in idle! 180s (process:2289): libfprint-device-DEBUG: 16:48:17.472: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 180s (process:2289): libfprint-image_device-DEBUG: 16:48:17.472: Image device close completed 180s (process:2289): libfprint-device-DEBUG: 16:48:17.472: Device reported close completion 180s (process:2289): libfprint-nb1010-DEBUG: 16:48:17.473: nb1010 Deinitialized 180s (process:2289): libfprint-device-DEBUG: 16:48:17.473: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 180s (process:2289): libfprint-device-DEBUG: 16:48:17.473: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 180s ** (umockdev-run:2285): DEBUG: 16:48:17.765: umockdev.vala:150: Removing test bed /tmp/umockdev.RFE8J2 180s (umockdev-run:2285): GLib-DEBUG: 16:48:17.771: unsetenv() is not thread-safe and should not be used after threads are created 180s Comparing PNGs /tmp/libfprint-umockdev-test-qgdo82yd/capture.png and /usr/share/installed-tests/libfprint-2/nb1010/capture.png 180s PASS: libfprint-2/driver-nb1010.test 180s Running test: libfprint-2/driver-egismoc.test 180s ** (umockdev-run:2298): DEBUG: 16:48:17.923: umockdev.vala:123: Created udev test bed /tmp/umockdev.3SFZJ2 180s ** (umockdev-run:2298): DEBUG: 16:48:17.923: umockdev.vala:1297: parsing device description for /devices/pci0000:00/0000:00:14.0/usb3/3-5 180s ** (umockdev-run:2298): DEBUG: 16:48:17.924: umockdev.vala:1366: creating device /devices/pci0000:00/0000:00:14.0/usb3/3-5 (subsystem usb) 180s ** (umockdev-run:2298): DEBUG: 16:48:17.927: umockdev.vala:1411: create_node_for_device: creating file device /tmp/umockdev.3SFZJ2/dev/bus/usb/003/012 180s ** (umockdev-run:2298): DEBUG: 16:48:17.927: umockdev.vala:1297: parsing device description for /devices/pci0000:00/0000:00:14.0/usb3 180s ** (umockdev-run:2298): DEBUG: 16:48:17.928: umockdev.vala:1366: creating device /devices/pci0000:00/0000:00:14.0/usb3 (subsystem usb) 180s ** (umockdev-run:2298): DEBUG: 16:48:17.930: umockdev.vala:1411: create_node_for_device: creating file device /tmp/umockdev.3SFZJ2/dev/bus/usb/003/001 180s ** (umockdev-run:2298): DEBUG: 16:48:17.930: umockdev.vala:1297: parsing device description for /devices/pci0000:00/0000:00:14.0 180s ** (umockdev-run:2298): DEBUG: 16:48:17.930: umockdev.vala:1366: creating device /devices/pci0000:00/0000:00:14.0 (subsystem pci) 181s (process:2302): libfprint-context-DEBUG: 16:48:18.033: Initializing FpContext (libfprint version 1.94.7+tod1) 181s (process:2302): libfprint-tod-DEBUG: 16:48:18.034: Impossible to load the shared drivers dir Error opening directory “/usr/lib/aarch64-linux-gnu/libfprint-2/tod-1”: No such file or directory 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.043: 69044279: ../libfprint/drivers/egismoc/egismoc.c:1515 181s (process:2302): libfprint-context-DEBUG: 16:48:18.043: No driver found for USB device 1D6B:0002 181s (process:2302): libfprint-device-DEBUG: 16:48:18.044: Device reported probe completion 181s (process:2302): libfprint-device-DEBUG: 16:48:18.044: Completing action FPI_DEVICE_ACTION_PROBE in idle! 181s (process:2302): libfprint-device-DEBUG: 16:48:18.044: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.045: Opening device 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.046: [egismoc] DEV_INIT_STATES entering state 0 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.046: [egismoc] DEV_INIT_STATES entering state 1 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.046: [egismoc] DEV_INIT_STATES entering state 2 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.047: [egismoc] DEV_INIT_STATES entering state 3 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.047: [egismoc] DEV_INIT_STATES entering state 4 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.048: [egismoc] DEV_INIT_STATES entering state 5 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.048: Execute command and get response 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.048: Get check bytes 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.048: [egismoc] CMD_STATES entering state 0 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.048: [egismoc] CMD_STATES entering state 1 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.049: Command receive callback 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.049: [egismoc] CMD_STATES completed successfully 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.049: Firmware version callback 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.049: Response suffix valid: yes 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.049: Device firmware version is 9050.1.1.81 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.049: [egismoc] DEV_INIT_STATES completed successfully 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.049: Task SSM done 181s (process:2302): libfprint-device-DEBUG: 16:48:18.049: Device reported open completion 181s (process:2302): libfprint-device-DEBUG: 16:48:18.049: Completing action FPI_DEVICE_ACTION_OPEN in idle! 181s (process:2302): libfprint-device-DEBUG: 16:48:18.049: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.049: List 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.049: [egismoc] LIST_STATES entering state 0 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.049: Execute command and get response 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.049: Get check bytes 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.049: [egismoc] CMD_STATES entering state 0 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.050: [egismoc] CMD_STATES entering state 1 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.050: Command receive callback 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.050: [egismoc] CMD_STATES completed successfully 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.050: List callback 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.050: Device fingerprint 0: FP1-20231016-1-AAA9163E-root 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.050: Device fingerprint 1: FP1-20231016-2-5102A0A3-root 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.050: Device fingerprint 2: FP1-20231016-3-5159A026-root 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.050: Device fingerprint 3: FP1-20231016-4-A25C1212-root 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.050: Device fingerprint 4: FP1-20231016-5-EC893AA9-root 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.050: Device fingerprint 5: \u0006\u001d\xcbc$ir%\xa22U֨\o\xff\x8ddY\x84\u0003\xbac\xcfO\xde\xc2!L\u001eN( 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.050: Device fingerprint 6: \xd7pܖsT3\xf6>\xd9\u0002"/[\xf8\u0017Iqpz\u000c\xfa,M\xdfm5\u007fq\xc6\xdew 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.050: Number of currently enrolled fingerprints on the device is 7 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.050: [egismoc] LIST_STATES entering state 1 181s (process:2302): libfprint-device-DEBUG: 16:48:18.051: Device reported listing completion 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.051: [egismoc] LIST_STATES completed successfully 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.051: Task SSM done 181s (process:2302): libfprint-device-DEBUG: 16:48:18.051: Completing action FPI_DEVICE_ACTION_LIST in idle! 181s (process:2302): libfprint-device-DEBUG: 16:48:18.051: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.051: Clear storage 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.051: [egismoc] DELETE_STATES entering state 0 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.051: Execute command and get response 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.051: Get check bytes 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.051: [egismoc] CMD_STATES entering state 0 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.051: [egismoc] CMD_STATES entering state 1 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.052: Command receive callback 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.052: [egismoc] CMD_STATES completed successfully 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.052: List callback 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.052: Device fingerprint 0: FP1-20231016-1-AAA9163E-root 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.052: Device fingerprint 1: FP1-20231016-2-5102A0A3-root 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.052: Device fingerprint 2: FP1-20231016-3-5159A026-root 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.052: Device fingerprint 3: FP1-20231016-4-A25C1212-root 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.052: Device fingerprint 4: FP1-20231016-5-EC893AA9-root 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.052: Device fingerprint 5: \u0006\u001d\xcbc$ir%\xa22U֨\o\xff\x8ddY\x84\u0003\xbac\xcfO\xde\xc2!L\u001eN( 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.052: Device fingerprint 6: \xd7pܖsT3\xf6>\xd9\u0002"/[\xf8\u0017Iqpz\u000c\xfa,M\xdfm5\u007fq\xc6\xdew 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.052: Number of currently enrolled fingerprints on the device is 7 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.052: [egismoc] DELETE_STATES entering state 1 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.052: Get delete command 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.052: Execute command and get response 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.053: Get check bytes 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.053: [egismoc] CMD_STATES entering state 0 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.053: [egismoc] CMD_STATES entering state 1 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.054: Command receive callback 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.054: [egismoc] CMD_STATES completed successfully 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.054: Delete callback 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.054: Response prefix valid: yes 181s (process:2302): libfprint-device-DEBUG: 16:48:18.054: Device reported deletion completion 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.054: [egismoc] DELETE_STATES completed successfully 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.054: Task SSM done 181s (process:2302): libfprint-device-DEBUG: 16:48:18.054: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 181s (process:2302): libfprint-device-DEBUG: 16:48:18.054: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.054: List 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.054: [egismoc] LIST_STATES entering state 0 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.054: Execute command and get response 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.054: Get check bytes 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.054: [egismoc] CMD_STATES entering state 0 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.054: [egismoc] CMD_STATES entering state 1 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.055: Command receive callback 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.055: [egismoc] CMD_STATES completed successfully 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.055: List callback 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.055: Number of currently enrolled fingerprints on the device is 0 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.055: [egismoc] LIST_STATES entering state 1 181s (process:2302): libfprint-device-DEBUG: 16:48:18.055: Device reported listing completion 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.055: [egismoc] LIST_STATES completed successfully 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.055: Task SSM done 181s (process:2302): libfprint-device-DEBUG: 16:48:18.055: Completing action FPI_DEVICE_ACTION_LIST in idle! 181s (process:2302): libfprint-device-DEBUG: 16:48:18.055: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 181s (process:2302): libfprint-device-DEBUG: 16:48:18.056: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.056: Enroll 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.056: [egismoc] ENROLL_STATES entering state 0 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.056: Execute command and get response 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.056: Get check bytes 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.056: [egismoc] CMD_STATES entering state 0 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.056: [egismoc] CMD_STATES entering state 1 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.057: Command receive callback 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.057: [egismoc] CMD_STATES completed successfully 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.057: List callback 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.057: Number of currently enrolled fingerprints on the device is 0 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.057: [egismoc] ENROLL_STATES entering state 1 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.057: [egismoc] ENROLL_STATES entering state 2 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.057: Execute command and get response 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.057: Get check bytes 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.057: [egismoc] CMD_STATES entering state 0 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.058: [egismoc] CMD_STATES entering state 1 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.058: Command receive callback 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.058: [egismoc] CMD_STATES completed successfully 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.058: Task SSM next state callback 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.058: [egismoc] ENROLL_STATES entering state 3 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.058: Execute command and get response 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.058: Get check bytes 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.058: [egismoc] CMD_STATES entering state 0 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.059: [egismoc] CMD_STATES entering state 1 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.059: Command receive callback 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.059: [egismoc] CMD_STATES completed successfully 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.059: Task SSM next state callback 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.059: [egismoc] ENROLL_STATES entering state 4 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.059: Wait for finger on sensor 181s (process:2302): libfprint-device-DEBUG: 16:48:18.059: Device reported finger status change: FP_FINGER_STATUS_NEEDED 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.059: Finger on sensor callback 181s (process:2302): libfprint-device-DEBUG: 16:48:18.059: Device reported finger status change: FP_FINGER_STATUS_PRESENT 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.059: [egismoc] ENROLL_STATES entering state 5 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.059: Execute command and get response 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.059: Get check bytes 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.059: [egismoc] CMD_STATES entering state 0 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.060: [egismoc] CMD_STATES entering state 1 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.060: Command receive callback 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.060: [egismoc] CMD_STATES completed successfully 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.060: Task SSM next state callback 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.060: [egismoc] ENROLL_STATES entering state 6 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.060: Get check command 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.060: Execute command and get response 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.060: Get check bytes 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.060: [egismoc] CMD_STATES entering state 0 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.061: [egismoc] CMD_STATES entering state 1 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.061: Command receive callback 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.061: [egismoc] CMD_STATES completed successfully 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.061: Enroll check callback 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.061: Response suffix valid: yes 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.061: [egismoc] ENROLL_STATES entering state 7 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.061: Execute command and get response 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.061: Get check bytes 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.061: [egismoc] CMD_STATES entering state 0 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.062: [egismoc] CMD_STATES entering state 1 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.062: Command receive callback 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.062: [egismoc] CMD_STATES completed successfully 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.062: Task SSM next state callback 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.062: [egismoc] ENROLL_STATES entering state 8 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.062: Execute command and get response 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.062: Get check bytes 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.062: [egismoc] CMD_STATES entering state 0 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.063: [egismoc] CMD_STATES entering state 1 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.063: Command receive callback 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.063: [egismoc] CMD_STATES completed successfully 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.063: Task SSM next state callback 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.063: [egismoc] ENROLL_STATES entering state 9 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.063: Execute command and get response 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.063: Get check bytes 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.063: [egismoc] CMD_STATES entering state 0 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.064: [egismoc] CMD_STATES entering state 1 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.064: Command receive callback 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.064: [egismoc] CMD_STATES completed successfully 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.064: Task SSM next state callback 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.064: [egismoc] ENROLL_STATES entering state 10 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.064: Wait for finger on sensor 181s (process:2302): libfprint-device-DEBUG: 16:48:18.064: Device reported finger status change: FP_FINGER_STATUS_NEEDED 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.065: Finger on sensor callback 181s (process:2302): libfprint-device-DEBUG: 16:48:18.065: Device reported finger status change: FP_FINGER_STATUS_PRESENT 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.065: [egismoc] ENROLL_STATES entering state 11 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.065: Execute command and get response 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.065: Get check bytes 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.065: [egismoc] CMD_STATES entering state 0 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.065: [egismoc] CMD_STATES entering state 1 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.065: Command receive callback 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.065: [egismoc] CMD_STATES completed successfully 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.065: Read capture callback 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.065: Response prefix valid: yes 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.065: Response suffix valid: yes 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.066: Partial capture successful. Please touch the sensor again (1/10) 181s (process:2302): libfprint-device-DEBUG: 16:48:18.066: Device reported enroll progress, reported 1 of 10 have been completed 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.076: [egismoc] ENROLL_STATES entering state 8 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.076: Execute command and get response 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.076: Get check bytes 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.076: [egismoc] CMD_STATES entering state 0 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.076: [egismoc] CMD_STATES entering state 1 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.077: Command receive callback 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.077: [egismoc] CMD_STATES completed successfully 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.077: Task SSM next state callback 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.077: [egismoc] ENROLL_STATES entering state 9 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.077: Execute command and get response 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.077: Get check bytes 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.077: [egismoc] CMD_STATES entering state 0 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.078: [egismoc] CMD_STATES entering state 1 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.078: Command receive callback 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.078: [egismoc] CMD_STATES completed successfully 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.078: Task SSM next state callback 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.078: [egismoc] ENROLL_STATES entering state 10 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.078: Wait for finger on sensor 181s (process:2302): libfprint-device-DEBUG: 16:48:18.078: Device reported finger status change: FP_FINGER_STATUS_NEEDED 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.079: Finger on sensor callback 181s (process:2302): libfprint-device-DEBUG: 16:48:18.079: Device reported finger status change: FP_FINGER_STATUS_PRESENT 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.079: [egismoc] ENROLL_STATES entering state 11 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.079: Execute command and get response 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.079: Get check bytes 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.079: [egismoc] CMD_STATES entering state 0 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.079: [egismoc] CMD_STATES entering state 1 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.080: Command receive callback 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.080: [egismoc] CMD_STATES completed successfully 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.080: Read capture callback 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.080: Response prefix valid: yes 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.080: Response suffix valid: yes 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.080: Partial capture successful. Please touch the sensor again (2/10) 181s (process:2302): libfprint-device-DEBUG: 16:48:18.080: Device reported enroll progress, reported 2 of 10 have been completed 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.080: [egismoc] ENROLL_STATES entering state 8 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.080: Execute command and get response 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.080: Get check bytes 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.080: [egismoc] CMD_STATES entering state 0 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.081: [egismoc] CMD_STATES entering state 1 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.081: Command receive callback 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.081: [egismoc] CMD_STATES completed successfully 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.081: Task SSM next state callback 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.081: [egismoc] ENROLL_STATES entering state 9 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.081: Execute command and get response 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.081: Get check bytes 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.081: [egismoc] CMD_STATES entering state 0 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.082: [egismoc] CMD_STATES entering state 1 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.082: Command receive callback 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.082: [egismoc] CMD_STATES completed successfully 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.082: Task SSM next state callback 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.082: [egismoc] ENROLL_STATES entering state 10 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.082: Wait for finger on sensor 181s (process:2302): libfprint-device-DEBUG: 16:48:18.082: Device reported finger status change: FP_FINGER_STATUS_NEEDED 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.083: Finger on sensor callback 181s (process:2302): libfprint-device-DEBUG: 16:48:18.083: Device reported finger status change: FP_FINGER_STATUS_PRESENT 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.083: [egismoc] ENROLL_STATES entering state 11 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.083: Execute command and get response 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.083: Get check bytes 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.083: [egismoc] CMD_STATES entering state 0 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.083: [egismoc] CMD_STATES entering state 1 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.083: Command receive callback 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.083: [egismoc] CMD_STATES completed successfully 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.083: Read capture callback 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.083: Response prefix valid: yes 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.083: Response suffix valid: NO 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.083: Response prefix valid: yes 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.083: Response suffix valid: yes 181s (process:2302): libfprint-device-DEBUG: 16:48:18.083: Device reported enroll progress, reported 2 of 10 have been completed 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.084: [egismoc] ENROLL_STATES entering state 8 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.084: Execute command and get response 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.084: Get check bytes 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.084: [egismoc] CMD_STATES entering state 0 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.084: [egismoc] CMD_STATES entering state 1 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.084: Command receive callback 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.084: [egismoc] CMD_STATES completed successfully 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.084: Task SSM next state callback 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.085: [egismoc] ENROLL_STATES entering state 9 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.085: Execute command and get response 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.085: Get check bytes 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.085: [egismoc] CMD_STATES entering state 0 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.085: [egismoc] CMD_STATES entering state 1 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.086: Command receive callback 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.086: [egismoc] CMD_STATES completed successfully 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.086: Task SSM next state callback 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.086: [egismoc] ENROLL_STATES entering state 10 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.086: Wait for finger on sensor 181s (process:2302): libfprint-device-DEBUG: 16:48:18.086: Device reported finger status change: FP_FINGER_STATUS_NEEDED 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.086: Finger on sensor callback 181s (process:2302): libfprint-device-DEBUG: 16:48:18.086: Device reported finger status change: FP_FINGER_STATUS_PRESENT 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.086: [egismoc] ENROLL_STATES entering state 11 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.086: Execute command and get response 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.086: Get check bytes 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.086: [egismoc] CMD_STATES entering state 0 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.086: [egismoc] CMD_STATES entering state 1 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.087: Command receive callback 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.087: [egismoc] CMD_STATES completed successfully 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.087: Read capture callback 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.087: Response prefix valid: yes 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.087: Response suffix valid: yes 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.087: Partial capture successful. Please touch the sensor again (3/10) 181s (process:2302): libfprint-device-DEBUG: 16:48:18.087: Device reported enroll progress, reported 3 of 10 have been completed 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.087: [egismoc] ENROLL_STATES entering state 8 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.087: Execute command and get response 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.087: Get check bytes 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.087: [egismoc] CMD_STATES entering state 0 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.087: [egismoc] CMD_STATES entering state 1 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.088: Command receive callback 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.088: [egismoc] CMD_STATES completed successfully 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.088: Task SSM next state callback 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.088: [egismoc] ENROLL_STATES entering state 9 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.088: Execute command and get response 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.088: Get check bytes 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.088: [egismoc] CMD_STATES entering state 0 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.088: [egismoc] CMD_STATES entering state 1 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.089: Command receive callback 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.089: [egismoc] CMD_STATES completed successfully 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.089: Task SSM next state callback 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.089: [egismoc] ENROLL_STATES entering state 10 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.089: Wait for finger on sensor 181s (process:2302): libfprint-device-DEBUG: 16:48:18.089: Device reported finger status change: FP_FINGER_STATUS_NEEDED 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.089: Finger on sensor callback 181s (process:2302): libfprint-device-DEBUG: 16:48:18.089: Device reported finger status change: FP_FINGER_STATUS_PRESENT 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.089: [egismoc] ENROLL_STATES entering state 11 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.089: Execute command and get response 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.089: Get check bytes 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.089: [egismoc] CMD_STATES entering state 0 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.090: [egismoc] CMD_STATES entering state 1 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.090: Command receive callback 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.090: [egismoc] CMD_STATES completed successfully 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.090: Read capture callback 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.090: Response prefix valid: yes 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.090: Response suffix valid: yes 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.090: Partial capture successful. Please touch the sensor again (4/10) 181s (process:2302): libfprint-device-DEBUG: 16:48:18.090: Device reported enroll progress, reported 4 of 10 have been completed 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.090: [egismoc] ENROLL_STATES entering state 8 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.090: Execute command and get response 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.090: Get check bytes 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.091: [egismoc] CMD_STATES entering state 0 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.091: [egismoc] CMD_STATES entering state 1 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.091: Command receive callback 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.091: [egismoc] CMD_STATES completed successfully 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.091: Task SSM next state callback 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.092: [egismoc] ENROLL_STATES entering state 9 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.092: Execute command and get response 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.092: Get check bytes 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.092: [egismoc] CMD_STATES entering state 0 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.092: [egismoc] CMD_STATES entering state 1 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.092: Command receive callback 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.092: [egismoc] CMD_STATES completed successfully 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.092: Task SSM next state callback 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.092: [egismoc] ENROLL_STATES entering state 10 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.092: Wait for finger on sensor 181s (process:2302): libfprint-device-DEBUG: 16:48:18.092: Device reported finger status change: FP_FINGER_STATUS_NEEDED 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.093: Finger on sensor callback 181s (process:2302): libfprint-device-DEBUG: 16:48:18.093: Device reported finger status change: FP_FINGER_STATUS_PRESENT 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.093: [egismoc] ENROLL_STATES entering state 11 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.093: Execute command and get response 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.093: Get check bytes 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.093: [egismoc] CMD_STATES entering state 0 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.093: [egismoc] CMD_STATES entering state 1 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.094: Command receive callback 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.094: [egismoc] CMD_STATES completed successfully 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.094: Read capture callback 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.094: Response prefix valid: yes 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.094: Response suffix valid: NO 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.094: Response prefix valid: yes 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.094: Response suffix valid: yes 181s (process:2302): libfprint-device-DEBUG: 16:48:18.094: Device reported enroll progress, reported 4 of 10 have been completed 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.094: [egismoc] ENROLL_STATES entering state 8 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.094: Execute command and get response 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.094: Get check bytes 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.094: [egismoc] CMD_STATES entering state 0 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.095: [egismoc] CMD_STATES entering state 1 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.095: Command receive callback 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.095: [egismoc] CMD_STATES completed successfully 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.095: Task SSM next state callback 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.095: [egismoc] ENROLL_STATES entering state 9 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.095: Execute command and get response 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.095: Get check bytes 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.095: [egismoc] CMD_STATES entering state 0 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.095: [egismoc] CMD_STATES entering state 1 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.096: Command receive callback 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.096: [egismoc] CMD_STATES completed successfully 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.096: Task SSM next state callback 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.096: [egismoc] ENROLL_STATES entering state 10 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.096: Wait for finger on sensor 181s (process:2302): libfprint-device-DEBUG: 16:48:18.096: Device reported finger status change: FP_FINGER_STATUS_NEEDED 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.096: Finger on sensor callback 181s (process:2302): libfprint-device-DEBUG: 16:48:18.096: Device reported finger status change: FP_FINGER_STATUS_PRESENT 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.096: [egismoc] ENROLL_STATES entering state 11 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.096: Execute command and get response 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.096: Get check bytes 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.096: [egismoc] CMD_STATES entering state 0 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.097: [egismoc] CMD_STATES entering state 1 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.097: Command receive callback 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.097: [egismoc] CMD_STATES completed successfully 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.097: Read capture callback 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.097: Response prefix valid: yes 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.097: Response suffix valid: yes 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.097: Partial capture successful. Please touch the sensor again (5/10) 181s (process:2302): libfprint-device-DEBUG: 16:48:18.097: Device reported enroll progress, reported 5 of 10 have been completed 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.097: [egismoc] ENROLL_STATES entering state 8 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.097: Execute command and get response 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.097: Get check bytes 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.097: [egismoc] CMD_STATES entering state 0 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.098: [egismoc] CMD_STATES entering state 1 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.098: Command receive callback 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.098: [egismoc] CMD_STATES completed successfully 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.098: Task SSM next state callback 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.098: [egismoc] ENROLL_STATES entering state 9 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.098: Execute command and get response 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.098: Get check bytes 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.098: [egismoc] CMD_STATES entering state 0 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.099: [egismoc] CMD_STATES entering state 1 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.099: Command receive callback 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.099: [egismoc] CMD_STATES completed successfully 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.099: Task SSM next state callback 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.099: [egismoc] ENROLL_STATES entering state 10 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.099: Wait for finger on sensor 181s (process:2302): libfprint-device-DEBUG: 16:48:18.099: Device reported finger status change: FP_FINGER_STATUS_NEEDED 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.100: Finger on sensor callback 181s (process:2302): libfprint-device-DEBUG: 16:48:18.100: Device reported finger status change: FP_FINGER_STATUS_PRESENT 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.100: [egismoc] ENROLL_STATES entering state 11 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.100: Execute command and get response 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.100: Get check bytes 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.100: [egismoc] CMD_STATES entering state 0 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.100: [egismoc] CMD_STATES entering state 1 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.101: Command receive callback 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.101: [egismoc] CMD_STATES completed successfully 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.101: Read capture callback 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.101: Response prefix valid: yes 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.101: Response suffix valid: yes 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.101: Partial capture successful. Please touch the sensor again (6/10) 181s (process:2302): libfprint-device-DEBUG: 16:48:18.101: Device reported enroll progress, reported 6 of 10 have been completed 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.101: [egismoc] ENROLL_STATES entering state 8 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.101: Execute command and get response 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.101: Get check bytes 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.101: [egismoc] CMD_STATES entering state 0 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.101: [egismoc] CMD_STATES entering state 1 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.102: Command receive callback 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.102: [egismoc] CMD_STATES completed successfully 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.102: Task SSM next state callback 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.102: [egismoc] ENROLL_STATES entering state 9 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.102: Execute command and get response 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.102: Get check bytes 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.102: [egismoc] CMD_STATES entering state 0 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.102: [egismoc] CMD_STATES entering state 1 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.102: Command receive callback 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.102: [egismoc] CMD_STATES completed successfully 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.102: Task SSM next state callback 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.102: [egismoc] ENROLL_STATES entering state 10 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.102: Wait for finger on sensor 181s (process:2302): libfprint-device-DEBUG: 16:48:18.102: Device reported finger status change: FP_FINGER_STATUS_NEEDED 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.103: Finger on sensor callback 181s (process:2302): libfprint-device-DEBUG: 16:48:18.103: Device reported finger status change: FP_FINGER_STATUS_PRESENT 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.103: [egismoc] ENROLL_STATES entering state 11 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.103: Execute command and get response 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.103: Get check bytes 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.103: [egismoc] CMD_STATES entering state 0 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.103: [egismoc] CMD_STATES entering state 1 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.104: Command receive callback 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.104: [egismoc] CMD_STATES completed successfully 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.104: Read capture callback 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.104: Response prefix valid: yes 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.104: Response suffix valid: NO 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.104: Response prefix valid: yes 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.104: Response suffix valid: yes 181s (process:2302): libfprint-device-DEBUG: 16:48:18.104: Device reported enroll progress, reported 6 of 10 have been completed 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.104: [egismoc] ENROLL_STATES entering state 8 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.104: Execute command and get response 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.104: Get check bytes 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.104: [egismoc] CMD_STATES entering state 0 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.104: [egismoc] CMD_STATES entering state 1 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.105: Command receive callback 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.105: [egismoc] CMD_STATES completed successfully 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.105: Task SSM next state callback 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.105: [egismoc] ENROLL_STATES entering state 9 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.105: Execute command and get response 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.105: Get check bytes 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.105: [egismoc] CMD_STATES entering state 0 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.105: [egismoc] CMD_STATES entering state 1 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.106: Command receive callback 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.106: [egismoc] CMD_STATES completed successfully 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.106: Task SSM next state callback 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.106: [egismoc] ENROLL_STATES entering state 10 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.106: Wait for finger on sensor 181s (process:2302): libfprint-device-DEBUG: 16:48:18.106: Device reported finger status change: FP_FINGER_STATUS_NEEDED 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.106: Finger on sensor callback 181s (process:2302): libfprint-device-DEBUG: 16:48:18.106: Device reported finger status change: FP_FINGER_STATUS_PRESENT 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.106: [egismoc] ENROLL_STATES entering state 11 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.106: Execute command and get response 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.106: Get check bytes 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.106: [egismoc] CMD_STATES entering state 0 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.106: [egismoc] CMD_STATES entering state 1 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.107: Command receive callback 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.107: [egismoc] CMD_STATES completed successfully 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.107: Read capture callback 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.107: Response prefix valid: yes 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.107: Response suffix valid: NO 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.107: Response prefix valid: yes 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.107: Response suffix valid: yes 181s (process:2302): libfprint-device-DEBUG: 16:48:18.107: Device reported enroll progress, reported 6 of 10 have been completed 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.107: [egismoc] ENROLL_STATES entering state 8 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.107: Execute command and get response 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.107: Get check bytes 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.107: [egismoc] CMD_STATES entering state 0 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.107: [egismoc] CMD_STATES entering state 1 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.108: Command receive callback 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.108: [egismoc] CMD_STATES completed successfully 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.108: Task SSM next state callback 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.108: [egismoc] ENROLL_STATES entering state 9 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.108: Execute command and get response 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.108: Get check bytes 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.108: [egismoc] CMD_STATES entering state 0 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.109: [egismoc] CMD_STATES entering state 1 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.109: Command receive callback 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.109: [egismoc] CMD_STATES completed successfully 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.109: Task SSM next state callback 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.109: [egismoc] ENROLL_STATES entering state 10 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.109: Wait for finger on sensor 181s (process:2302): libfprint-device-DEBUG: 16:48:18.109: Device reported finger status change: FP_FINGER_STATUS_NEEDED 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.109: Finger on sensor callback 181s (process:2302): libfprint-device-DEBUG: 16:48:18.109: Device reported finger status change: FP_FINGER_STATUS_PRESENT 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.110: [egismoc] ENROLL_STATES entering state 11 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.110: Execute command and get response 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.110: Get check bytes 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.110: [egismoc] CMD_STATES entering state 0 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.110: [egismoc] CMD_STATES entering state 1 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.110: Command receive callback 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.110: [egismoc] CMD_STATES completed successfully 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.110: Read capture callback 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.110: Response prefix valid: yes 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.110: Response suffix valid: yes 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.110: Partial capture successful. Please touch the sensor again (7/10) 181s (process:2302): libfprint-device-DEBUG: 16:48:18.110: Device reported enroll progress, reported 7 of 10 have been completed 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.110: [egismoc] ENROLL_STATES entering state 8 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.110: Execute command and get response 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.110: Get check bytes 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.110: [egismoc] CMD_STATES entering state 0 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.111: [egismoc] CMD_STATES entering state 1 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.111: Command receive callback 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.111: [egismoc] CMD_STATES completed successfully 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.111: Task SSM next state callback 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.111: [egismoc] ENROLL_STATES entering state 9 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.111: Execute command and get response 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.111: Get check bytes 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.111: [egismoc] CMD_STATES entering state 0 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.112: [egismoc] CMD_STATES entering state 1 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.112: Command receive callback 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.112: [egismoc] CMD_STATES completed successfully 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.112: Task SSM next state callback 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.112: [egismoc] ENROLL_STATES entering state 10 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.112: Wait for finger on sensor 181s (process:2302): libfprint-device-DEBUG: 16:48:18.112: Device reported finger status change: FP_FINGER_STATUS_NEEDED 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.113: Finger on sensor callback 181s (process:2302): libfprint-device-DEBUG: 16:48:18.113: Device reported finger status change: FP_FINGER_STATUS_PRESENT 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.113: [egismoc] ENROLL_STATES entering state 11 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.113: Execute command and get response 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.113: Get check bytes 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.113: [egismoc] CMD_STATES entering state 0 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.113: [egismoc] CMD_STATES entering state 1 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.114: Command receive callback 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.114: [egismoc] CMD_STATES completed successfully 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.114: Read capture callback 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.114: Response prefix valid: yes 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.114: Response suffix valid: yes 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.114: Partial capture successful. Please touch the sensor again (8/10) 181s (process:2302): libfprint-device-DEBUG: 16:48:18.114: Device reported enroll progress, reported 8 of 10 have been completed 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.114: [egismoc] ENROLL_STATES entering state 8 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.114: Execute command and get response 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.114: Get check bytes 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.114: [egismoc] CMD_STATES entering state 0 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.114: [egismoc] CMD_STATES entering state 1 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.115: Command receive callback 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.115: [egismoc] CMD_STATES completed successfully 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.115: Task SSM next state callback 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.115: [egismoc] ENROLL_STATES entering state 9 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.115: Execute command and get response 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.115: Get check bytes 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.115: [egismoc] CMD_STATES entering state 0 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.115: [egismoc] CMD_STATES entering state 1 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.116: Command receive callback 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.116: [egismoc] CMD_STATES completed successfully 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.116: Task SSM next state callback 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.116: [egismoc] ENROLL_STATES entering state 10 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.116: Wait for finger on sensor 181s (process:2302): libfprint-device-DEBUG: 16:48:18.116: Device reported finger status change: FP_FINGER_STATUS_NEEDED 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.116: Finger on sensor callback 181s (process:2302): libfprint-device-DEBUG: 16:48:18.116: Device reported finger status change: FP_FINGER_STATUS_PRESENT 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.116: [egismoc] ENROLL_STATES entering state 11 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.116: Execute command and get response 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.116: Get check bytes 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.116: [egismoc] CMD_STATES entering state 0 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.117: [egismoc] CMD_STATES entering state 1 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.117: Command receive callback 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.117: [egismoc] CMD_STATES completed successfully 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.117: Read capture callback 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.117: Response prefix valid: yes 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.117: Response suffix valid: yes 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.117: Partial capture successful. Please touch the sensor again (9/10) 181s (process:2302): libfprint-device-DEBUG: 16:48:18.117: Device reported enroll progress, reported 9 of 10 have been completed 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.117: [egismoc] ENROLL_STATES entering state 8 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.117: Execute command and get response 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.117: Get check bytes 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.117: [egismoc] CMD_STATES entering state 0 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.118: [egismoc] CMD_STATES entering state 1 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.118: Command receive callback 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.119: [egismoc] CMD_STATES completed successfully 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.119: Task SSM next state callback 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.119: [egismoc] ENROLL_STATES entering state 9 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.119: Execute command and get response 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.119: Get check bytes 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.119: [egismoc] CMD_STATES entering state 0 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.119: [egismoc] CMD_STATES entering state 1 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.120: Command receive callback 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.120: [egismoc] CMD_STATES completed successfully 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.120: Task SSM next state callback 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.120: [egismoc] ENROLL_STATES entering state 10 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.120: Wait for finger on sensor 181s (process:2302): libfprint-device-DEBUG: 16:48:18.120: Device reported finger status change: FP_FINGER_STATUS_NEEDED 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.120: Finger on sensor callback 181s (process:2302): libfprint-device-DEBUG: 16:48:18.120: Device reported finger status change: FP_FINGER_STATUS_PRESENT 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.120: [egismoc] ENROLL_STATES entering state 11 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.120: Execute command and get response 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.120: Get check bytes 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.120: [egismoc] CMD_STATES entering state 0 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.121: [egismoc] CMD_STATES entering state 1 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.121: Command receive callback 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.121: [egismoc] CMD_STATES completed successfully 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.121: Read capture callback 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.121: Response prefix valid: yes 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.121: Response suffix valid: NO 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.121: Response prefix valid: yes 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.121: Response suffix valid: yes 181s (process:2302): libfprint-device-DEBUG: 16:48:18.121: Device reported enroll progress, reported 9 of 10 have been completed 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.121: [egismoc] ENROLL_STATES entering state 8 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.121: Execute command and get response 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.121: Get check bytes 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.121: [egismoc] CMD_STATES entering state 0 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.122: [egismoc] CMD_STATES entering state 1 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.122: Command receive callback 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.122: [egismoc] CMD_STATES completed successfully 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.122: Task SSM next state callback 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.122: [egismoc] ENROLL_STATES entering state 9 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.122: Execute command and get response 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.122: Get check bytes 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.122: [egismoc] CMD_STATES entering state 0 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.123: [egismoc] CMD_STATES entering state 1 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.123: Command receive callback 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.123: [egismoc] CMD_STATES completed successfully 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.123: Task SSM next state callback 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.123: [egismoc] ENROLL_STATES entering state 10 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.123: Wait for finger on sensor 181s (process:2302): libfprint-device-DEBUG: 16:48:18.123: Device reported finger status change: FP_FINGER_STATUS_NEEDED 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.124: Finger on sensor callback 181s (process:2302): libfprint-device-DEBUG: 16:48:18.124: Device reported finger status change: FP_FINGER_STATUS_PRESENT 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.124: [egismoc] ENROLL_STATES entering state 11 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.124: Execute command and get response 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.124: Get check bytes 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.124: [egismoc] CMD_STATES entering state 0 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.124: [egismoc] CMD_STATES entering state 1 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.125: Command receive callback 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.125: [egismoc] CMD_STATES completed successfully 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.125: Read capture callback 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.125: Response prefix valid: yes 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.125: Response suffix valid: yes 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.125: Partial capture successful. Please touch the sensor again (10/10) 181s (process:2302): libfprint-device-DEBUG: 16:48:18.125: Device reported enroll progress, reported 10 of 10 have been completed 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.125: [egismoc] ENROLL_STATES entering state 12 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.125: Execute command and get response 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.125: Get check bytes 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.125: [egismoc] CMD_STATES entering state 0 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.125: [egismoc] CMD_STATES entering state 1 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.126: Command receive callback 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.126: [egismoc] CMD_STATES completed successfully 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.126: Task SSM next state callback 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.126: [egismoc] ENROLL_STATES entering state 13 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.126: New fingerprint ID: FP1-00000000-2-00000000-nobody 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.126: Execute command and get response 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.126: Get check bytes 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.126: [egismoc] CMD_STATES entering state 0 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.126: [egismoc] CMD_STATES entering state 1 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.127: Command receive callback 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.127: [egismoc] CMD_STATES completed successfully 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.127: Task SSM next state callback 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.127: [egismoc] ENROLL_STATES entering state 14 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.127: Execute command and get response 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.127: Get check bytes 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.127: [egismoc] CMD_STATES entering state 0 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.127: [egismoc] CMD_STATES entering state 1 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.128: Command receive callback 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.128: [egismoc] CMD_STATES completed successfully 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.128: Task SSM next state callback 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.128: [egismoc] ENROLL_STATES entering state 15 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.128: Enrollment was successful! 181s (process:2302): libfprint-device-DEBUG: 16:48:18.128: Device reported enroll completion 181s (process:2302): libfprint-device-DEBUG: 16:48:18.128: Device reported finger status change: FP_FINGER_STATUS_NONE 181s (process:2302): libfprint-device-DEBUG: 16:48:18.128: Print for finger FP_FINGER_LEFT_INDEX enrolled 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.128: [egismoc] ENROLL_STATES completed successfully 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.128: Task SSM done 181s (process:2302): libfprint-device-DEBUG: 16:48:18.128: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 181s (process:2302): libfprint-device-DEBUG: 16:48:18.128: Updated temperature model after 0.07 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.128: List 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.128: [egismoc] LIST_STATES entering state 0 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.128: Execute command and get response 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.128: Get check bytes 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.128: [egismoc] CMD_STATES entering state 0 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.128: [egismoc] CMD_STATES entering state 1 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.129: Command receive callback 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.129: [egismoc] CMD_STATES completed successfully 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.129: List callback 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.129: Device fingerprint 0: FP1-00000000-2-00000000-nobody 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.129: Number of currently enrolled fingerprints on the device is 1 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.129: [egismoc] LIST_STATES entering state 1 181s (process:2302): libfprint-device-DEBUG: 16:48:18.129: Device reported listing completion 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.129: [egismoc] LIST_STATES completed successfully 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.129: Task SSM done 181s (process:2302): libfprint-device-DEBUG: 16:48:18.129: Completing action FPI_DEVICE_ACTION_LIST in idle! 181s (process:2302): libfprint-device-DEBUG: 16:48:18.129: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 181s (process:2302): libfprint-device-DEBUG: 16:48:18.129: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.129: Identify or Verify 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.129: [egismoc] IDENTIFY_STATES entering state 0 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.129: Execute command and get response 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.129: Get check bytes 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.129: [egismoc] CMD_STATES entering state 0 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.130: [egismoc] CMD_STATES entering state 1 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.130: Command receive callback 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.130: [egismoc] CMD_STATES completed successfully 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.130: List callback 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.131: Device fingerprint 0: FP1-00000000-2-00000000-nobody 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.131: Number of currently enrolled fingerprints on the device is 1 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.131: [egismoc] IDENTIFY_STATES entering state 1 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.131: [egismoc] IDENTIFY_STATES entering state 2 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.131: Execute command and get response 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.131: Get check bytes 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.131: [egismoc] CMD_STATES entering state 0 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.132: [egismoc] CMD_STATES entering state 1 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.132: Command receive callback 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.132: [egismoc] CMD_STATES completed successfully 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.132: Task SSM next state callback 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.132: [egismoc] IDENTIFY_STATES entering state 3 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.132: Execute command and get response 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.132: Get check bytes 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.132: [egismoc] CMD_STATES entering state 0 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.133: [egismoc] CMD_STATES entering state 1 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.133: Command receive callback 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.133: [egismoc] CMD_STATES completed successfully 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.133: Task SSM next state callback 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.133: [egismoc] IDENTIFY_STATES entering state 4 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.133: Wait for finger on sensor 181s (process:2302): libfprint-device-DEBUG: 16:48:18.133: Device reported finger status change: FP_FINGER_STATUS_NEEDED 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.133: Finger on sensor callback 181s (process:2302): libfprint-device-DEBUG: 16:48:18.133: Device reported finger status change: FP_FINGER_STATUS_PRESENT 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.133: [egismoc] IDENTIFY_STATES entering state 5 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.133: Execute command and get response 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.133: Get check bytes 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.133: [egismoc] CMD_STATES entering state 0 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.134: [egismoc] CMD_STATES entering state 1 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.134: Command receive callback 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.134: [egismoc] CMD_STATES completed successfully 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.134: Task SSM next state callback 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.134: [egismoc] IDENTIFY_STATES entering state 6 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.134: Get check command 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.134: Execute command and get response 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.134: Get check bytes 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.134: [egismoc] CMD_STATES entering state 0 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.135: [egismoc] CMD_STATES entering state 1 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.135: Command receive callback 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.135: [egismoc] CMD_STATES completed successfully 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.135: Identify check callback 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.135: Response suffix valid: yes 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.135: Identify successful for: FP1-00000000-2-00000000-nobody 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.135: Verifying against: FP1-00000000-2-00000000-nobody 181s (process:2302): libfprint-device-DEBUG: 16:48:18.135: Device reported verify result 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.135: [egismoc] IDENTIFY_STATES entering state 7 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.135: Execute command and get response 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.135: Get check bytes 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.135: [egismoc] CMD_STATES entering state 0 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.136: [egismoc] CMD_STATES entering state 1 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.136: Command receive callback 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.136: [egismoc] CMD_STATES completed successfully 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.136: Task SSM next state callback 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.136: [egismoc] IDENTIFY_STATES entering state 8 181s (process:2302): libfprint-device-DEBUG: 16:48:18.136: Device reported verify completion 181s (process:2302): libfprint-device-DEBUG: 16:48:18.136: Device reported finger status change: FP_FINGER_STATUS_NONE 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.136: [egismoc] IDENTIFY_STATES completed successfully 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.136: Task SSM done 181s (process:2302): libfprint-device-DEBUG: 16:48:18.136: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 181s (process:2302): libfprint-device-DEBUG: 16:48:18.137: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 181s (process:2302): libfprint-device-DEBUG: 16:48:18.137: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.137: Identify or Verify 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.137: [egismoc] IDENTIFY_STATES entering state 0 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.137: Execute command and get response 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.137: Get check bytes 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.137: [egismoc] CMD_STATES entering state 0 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.138: [egismoc] CMD_STATES entering state 1 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.138: Command receive callback 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.138: [egismoc] CMD_STATES completed successfully 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.138: List callback 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.138: Device fingerprint 0: FP1-00000000-2-00000000-nobody 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.138: Number of currently enrolled fingerprints on the device is 1 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.138: [egismoc] IDENTIFY_STATES entering state 1 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.138: [egismoc] IDENTIFY_STATES entering state 2 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.138: Execute command and get response 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.138: Get check bytes 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.139: [egismoc] CMD_STATES entering state 0 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.139: [egismoc] CMD_STATES entering state 1 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.140: Command receive callback 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.140: [egismoc] CMD_STATES completed successfully 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.140: Task SSM next state callback 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.140: [egismoc] IDENTIFY_STATES entering state 3 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.140: Execute command and get response 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.140: Get check bytes 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.140: [egismoc] CMD_STATES entering state 0 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.140: [egismoc] CMD_STATES entering state 1 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.141: Command receive callback 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.141: [egismoc] CMD_STATES completed successfully 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.141: Task SSM next state callback 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.141: [egismoc] IDENTIFY_STATES entering state 4 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.141: Wait for finger on sensor 181s (process:2302): libfprint-device-DEBUG: 16:48:18.141: Device reported finger status change: FP_FINGER_STATUS_NEEDED 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.141: Finger on sensor callback 181s (process:2302): libfprint-device-DEBUG: 16:48:18.141: Device reported finger status change: FP_FINGER_STATUS_PRESENT 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.141: [egismoc] IDENTIFY_STATES entering state 5 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.141: Execute command and get response 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.141: Get check bytes 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.141: [egismoc] CMD_STATES entering state 0 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.142: [egismoc] CMD_STATES entering state 1 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.143: Command receive callback 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.143: [egismoc] CMD_STATES completed successfully 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.143: Task SSM next state callback 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.143: [egismoc] IDENTIFY_STATES entering state 6 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.143: Get check command 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.143: Execute command and get response 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.143: Get check bytes 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.143: [egismoc] CMD_STATES entering state 0 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.143: [egismoc] CMD_STATES entering state 1 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.144: Command receive callback 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.144: [egismoc] CMD_STATES completed successfully 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.144: Identify check callback 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.144: Response suffix valid: yes 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.144: Identify successful for: FP1-00000000-2-00000000-nobody 181s (process:2302): libfprint-device-DEBUG: 16:48:18.144: Device reported identify result 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.144: [egismoc] IDENTIFY_STATES entering state 7 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.144: Execute command and get response 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.144: Get check bytes 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.144: [egismoc] CMD_STATES entering state 0 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.144: [egismoc] CMD_STATES entering state 1 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.145: Command receive callback 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.145: [egismoc] CMD_STATES completed successfully 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.145: Task SSM next state callback 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.145: [egismoc] IDENTIFY_STATES entering state 8 181s (process:2302): libfprint-device-DEBUG: 16:48:18.145: Device reported identify completion 181s (process:2302): libfprint-device-DEBUG: 16:48:18.145: Device reported finger status change: FP_FINGER_STATUS_NONE 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.145: [egismoc] IDENTIFY_STATES completed successfully 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.145: Task SSM done 181s (process:2302): libfprint-device-DEBUG: 16:48:18.145: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 181s (process:2302): libfprint-device-DEBUG: 16:48:18.145: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 181s (process:2302): libfprint-device-DEBUG: 16:48:18.145: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.146: Enroll 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.146: [egismoc] ENROLL_STATES entering state 0 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.146: Execute command and get response 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.146: Get check bytes 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.146: [egismoc] CMD_STATES entering state 0 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.146: [egismoc] CMD_STATES entering state 1 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.146: Command receive callback 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.146: [egismoc] CMD_STATES completed successfully 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.147: List callback 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.147: Device fingerprint 0: FP1-00000000-2-00000000-nobody 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.147: Number of currently enrolled fingerprints on the device is 1 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.147: [egismoc] ENROLL_STATES entering state 1 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.147: [egismoc] ENROLL_STATES entering state 2 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.147: Execute command and get response 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.147: Get check bytes 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.147: [egismoc] CMD_STATES entering state 0 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.147: [egismoc] CMD_STATES entering state 1 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.148: Command receive callback 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.148: [egismoc] CMD_STATES completed successfully 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.148: Task SSM next state callback 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.148: [egismoc] ENROLL_STATES entering state 3 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.148: Execute command and get response 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.148: Get check bytes 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.148: [egismoc] CMD_STATES entering state 0 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.148: [egismoc] CMD_STATES entering state 1 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.149: Command receive callback 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.149: [egismoc] CMD_STATES completed successfully 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.149: Task SSM next state callback 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.149: [egismoc] ENROLL_STATES entering state 4 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.149: Wait for finger on sensor 181s (process:2302): libfprint-device-DEBUG: 16:48:18.149: Device reported finger status change: FP_FINGER_STATUS_NEEDED 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.149: Finger on sensor callback 181s (process:2302): libfprint-device-DEBUG: 16:48:18.149: Device reported finger status change: FP_FINGER_STATUS_PRESENT 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.149: [egismoc] ENROLL_STATES entering state 5 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.149: Execute command and get response 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.149: Get check bytes 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.149: [egismoc] CMD_STATES entering state 0 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.150: [egismoc] CMD_STATES entering state 1 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.150: Command receive callback 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.150: [egismoc] CMD_STATES completed successfully 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.150: Task SSM next state callback 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.150: [egismoc] ENROLL_STATES entering state 6 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.150: Get check command 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.150: Execute command and get response 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.150: Get check bytes 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.150: [egismoc] CMD_STATES entering state 0 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.151: [egismoc] CMD_STATES entering state 1 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.151: Command receive callback 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.151: [egismoc] CMD_STATES completed successfully 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.151: Enroll check callback 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.151: Response suffix valid: NO 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.151: [egismoc] SSM ENROLL_STATES failed in state 6 with error: This finger has already enrolled, please try a different finger 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.151: [egismoc] ENROLL_STATES completed with error: This finger has already enrolled, please try a different finger 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.151: Task SSM done 181s (process:2302): libfprint-device-DEBUG: 16:48:18.151: Device reported generic error (This finger has already enrolled, please try a different finger) during action; action was: FPI_DEVICE_ACTION_ENROLL 181s (process:2302): libfprint-device-DEBUG: 16:48:18.151: Device reported enroll completion 181s (process:2302): libfprint-device-DEBUG: 16:48:18.151: Device reported finger status change: FP_FINGER_STATUS_NONE 181s (process:2302): libfprint-device-DEBUG: 16:48:18.151: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 181s (process:2302): libfprint-device-DEBUG: 16:48:18.151: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.151: List 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.151: [egismoc] LIST_STATES entering state 0 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.151: Execute command and get response 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.151: Get check bytes 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.151: [egismoc] CMD_STATES entering state 0 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.152: [egismoc] CMD_STATES entering state 1 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.152: Command receive callback 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.152: [egismoc] CMD_STATES completed successfully 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.153: List callback 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.153: Device fingerprint 0: FP1-00000000-2-00000000-nobody 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.153: Number of currently enrolled fingerprints on the device is 1 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.153: [egismoc] LIST_STATES entering state 1 181s (process:2302): libfprint-device-DEBUG: 16:48:18.153: Device reported listing completion 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.153: [egismoc] LIST_STATES completed successfully 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.153: Task SSM done 181s (process:2302): libfprint-device-DEBUG: 16:48:18.153: Completing action FPI_DEVICE_ACTION_LIST in idle! 181s (process:2302): libfprint-device-DEBUG: 16:48:18.153: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 181s (process:2302): libfprint-device-DEBUG: 16:48:18.153: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.153: Enroll 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.153: [egismoc] ENROLL_STATES entering state 0 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.153: Execute command and get response 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.153: Get check bytes 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.153: [egismoc] CMD_STATES entering state 0 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.153: [egismoc] CMD_STATES entering state 1 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.154: Command receive callback 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.154: [egismoc] CMD_STATES completed successfully 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.154: List callback 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.154: Device fingerprint 0: FP1-00000000-2-00000000-nobody 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.154: Number of currently enrolled fingerprints on the device is 1 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.154: [egismoc] ENROLL_STATES entering state 1 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.154: [egismoc] ENROLL_STATES entering state 2 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.154: Execute command and get response 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.154: Get check bytes 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.154: [egismoc] CMD_STATES entering state 0 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.154: [egismoc] CMD_STATES entering state 1 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.155: Command receive callback 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.155: [egismoc] CMD_STATES completed successfully 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.155: Task SSM next state callback 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.155: [egismoc] ENROLL_STATES entering state 3 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.155: Execute command and get response 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.155: Get check bytes 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.155: [egismoc] CMD_STATES entering state 0 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.155: [egismoc] CMD_STATES entering state 1 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.156: Command receive callback 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.156: [egismoc] CMD_STATES completed successfully 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.156: Task SSM next state callback 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.156: [egismoc] ENROLL_STATES entering state 4 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.156: Wait for finger on sensor 181s (process:2302): libfprint-device-DEBUG: 16:48:18.156: Device reported finger status change: FP_FINGER_STATUS_NEEDED 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.156: Finger on sensor callback 181s (process:2302): libfprint-device-DEBUG: 16:48:18.156: Device reported finger status change: FP_FINGER_STATUS_PRESENT 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.156: [egismoc] ENROLL_STATES entering state 5 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.156: Execute command and get response 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.156: Get check bytes 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.156: [egismoc] CMD_STATES entering state 0 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.157: [egismoc] CMD_STATES entering state 1 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.157: Command receive callback 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.157: [egismoc] CMD_STATES completed successfully 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.157: Task SSM next state callback 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.157: [egismoc] ENROLL_STATES entering state 6 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.157: Get check command 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.157: Execute command and get response 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.157: Get check bytes 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.157: [egismoc] CMD_STATES entering state 0 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.158: [egismoc] CMD_STATES entering state 1 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.158: Command receive callback 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.158: [egismoc] CMD_STATES completed successfully 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.158: Enroll check callback 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.158: Response suffix valid: yes 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.158: [egismoc] ENROLL_STATES entering state 7 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.158: Execute command and get response 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.158: Get check bytes 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.158: [egismoc] CMD_STATES entering state 0 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.159: [egismoc] CMD_STATES entering state 1 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.159: Command receive callback 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.159: [egismoc] CMD_STATES completed successfully 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.159: Task SSM next state callback 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.159: [egismoc] ENROLL_STATES entering state 8 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.160: Execute command and get response 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.160: Get check bytes 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.160: [egismoc] CMD_STATES entering state 0 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.160: [egismoc] CMD_STATES entering state 1 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.161: Command receive callback 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.161: [egismoc] CMD_STATES completed successfully 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.161: Task SSM next state callback 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.161: [egismoc] ENROLL_STATES entering state 9 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.161: Execute command and get response 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.161: Get check bytes 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.161: [egismoc] CMD_STATES entering state 0 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.161: [egismoc] CMD_STATES entering state 1 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.162: Command receive callback 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.162: [egismoc] CMD_STATES completed successfully 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.162: Task SSM next state callback 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.162: [egismoc] ENROLL_STATES entering state 10 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.162: Wait for finger on sensor 181s (process:2302): libfprint-device-DEBUG: 16:48:18.162: Device reported finger status change: FP_FINGER_STATUS_NEEDED 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.162: Finger on sensor callback 181s (process:2302): libfprint-device-DEBUG: 16:48:18.162: Device reported finger status change: FP_FINGER_STATUS_PRESENT 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.162: [egismoc] ENROLL_STATES entering state 11 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.162: Execute command and get response 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.162: Get check bytes 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.162: [egismoc] CMD_STATES entering state 0 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.163: [egismoc] CMD_STATES entering state 1 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.163: Command receive callback 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.163: [egismoc] CMD_STATES completed successfully 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.163: Read capture callback 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.163: Response prefix valid: yes 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.163: Response suffix valid: yes 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.163: Partial capture successful. Please touch the sensor again (1/10) 181s (process:2302): libfprint-device-DEBUG: 16:48:18.163: Device reported enroll progress, reported 1 of 10 have been completed 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.163: [egismoc] ENROLL_STATES entering state 8 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.163: Execute command and get response 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.163: Get check bytes 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.163: [egismoc] CMD_STATES entering state 0 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.164: [egismoc] CMD_STATES entering state 1 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.164: Command receive callback 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.164: [egismoc] CMD_STATES completed successfully 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.164: Task SSM next state callback 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.164: [egismoc] ENROLL_STATES entering state 9 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.164: Execute command and get response 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.164: Get check bytes 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.164: [egismoc] CMD_STATES entering state 0 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.165: [egismoc] CMD_STATES entering state 1 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.165: Command receive callback 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.165: [egismoc] CMD_STATES completed successfully 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.165: Task SSM next state callback 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.165: [egismoc] ENROLL_STATES entering state 10 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.165: Wait for finger on sensor 181s (process:2302): libfprint-device-DEBUG: 16:48:18.165: Device reported finger status change: FP_FINGER_STATUS_NEEDED 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.166: Finger on sensor callback 181s (process:2302): libfprint-device-DEBUG: 16:48:18.166: Device reported finger status change: FP_FINGER_STATUS_PRESENT 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.166: [egismoc] ENROLL_STATES entering state 11 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.166: Execute command and get response 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.166: Get check bytes 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.166: [egismoc] CMD_STATES entering state 0 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.166: [egismoc] CMD_STATES entering state 1 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.166: Command receive callback 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.166: [egismoc] CMD_STATES completed successfully 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.167: Read capture callback 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.167: Response prefix valid: yes 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.167: Response suffix valid: NO 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.167: Response prefix valid: yes 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.167: Response suffix valid: yes 181s (process:2302): libfprint-device-DEBUG: 16:48:18.167: Device reported enroll progress, reported 1 of 10 have been completed 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.167: [egismoc] ENROLL_STATES entering state 8 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.167: Execute command and get response 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.167: Get check bytes 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.167: [egismoc] CMD_STATES entering state 0 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.167: [egismoc] CMD_STATES entering state 1 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.167: Command receive callback 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.167: [egismoc] CMD_STATES completed successfully 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.168: Task SSM next state callback 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.168: [egismoc] ENROLL_STATES entering state 9 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.168: Execute command and get response 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.168: Get check bytes 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.168: [egismoc] CMD_STATES entering state 0 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.168: [egismoc] CMD_STATES entering state 1 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.168: Command receive callback 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.168: [egismoc] CMD_STATES completed successfully 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.168: Task SSM next state callback 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.168: [egismoc] ENROLL_STATES entering state 10 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.168: Wait for finger on sensor 181s (process:2302): libfprint-device-DEBUG: 16:48:18.168: Device reported finger status change: FP_FINGER_STATUS_NEEDED 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.169: Finger on sensor callback 181s (process:2302): libfprint-device-DEBUG: 16:48:18.169: Device reported finger status change: FP_FINGER_STATUS_PRESENT 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.169: [egismoc] ENROLL_STATES entering state 11 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.169: Execute command and get response 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.169: Get check bytes 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.169: [egismoc] CMD_STATES entering state 0 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.169: [egismoc] CMD_STATES entering state 1 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.170: Command receive callback 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.170: [egismoc] CMD_STATES completed successfully 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.170: Read capture callback 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.170: Response prefix valid: yes 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.170: Response suffix valid: yes 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.170: Partial capture successful. Please touch the sensor again (2/10) 181s (process:2302): libfprint-device-DEBUG: 16:48:18.170: Device reported enroll progress, reported 2 of 10 have been completed 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.170: [egismoc] ENROLL_STATES entering state 8 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.170: Execute command and get response 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.170: Get check bytes 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.170: [egismoc] CMD_STATES entering state 0 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.170: [egismoc] CMD_STATES entering state 1 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.171: Command receive callback 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.171: [egismoc] CMD_STATES completed successfully 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.171: Task SSM next state callback 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.171: [egismoc] ENROLL_STATES entering state 9 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.171: Execute command and get response 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.171: Get check bytes 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.171: [egismoc] CMD_STATES entering state 0 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.171: [egismoc] CMD_STATES entering state 1 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.171: Command receive callback 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.171: [egismoc] CMD_STATES completed successfully 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.171: Task SSM next state callback 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.171: [egismoc] ENROLL_STATES entering state 10 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.171: Wait for finger on sensor 181s (process:2302): libfprint-device-DEBUG: 16:48:18.171: Device reported finger status change: FP_FINGER_STATUS_NEEDED 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.172: Finger on sensor callback 181s (process:2302): libfprint-device-DEBUG: 16:48:18.172: Device reported finger status change: FP_FINGER_STATUS_PRESENT 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.172: [egismoc] ENROLL_STATES entering state 11 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.172: Execute command and get response 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.172: Get check bytes 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.172: [egismoc] CMD_STATES entering state 0 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.173: [egismoc] CMD_STATES entering state 1 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.173: Command receive callback 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.173: [egismoc] CMD_STATES completed successfully 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.173: Read capture callback 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.173: Response prefix valid: yes 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.173: Response suffix valid: yes 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.173: Partial capture successful. Please touch the sensor again (3/10) 181s (process:2302): libfprint-device-DEBUG: 16:48:18.173: Device reported enroll progress, reported 3 of 10 have been completed 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.173: [egismoc] ENROLL_STATES entering state 8 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.173: Execute command and get response 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.173: Get check bytes 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.173: [egismoc] CMD_STATES entering state 0 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.174: [egismoc] CMD_STATES entering state 1 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.174: Command receive callback 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.174: [egismoc] CMD_STATES completed successfully 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.174: Task SSM next state callback 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.174: [egismoc] ENROLL_STATES entering state 9 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.174: Execute command and get response 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.174: Get check bytes 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.174: [egismoc] CMD_STATES entering state 0 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.175: [egismoc] CMD_STATES entering state 1 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.175: Command receive callback 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.175: [egismoc] CMD_STATES completed successfully 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.175: Task SSM next state callback 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.175: [egismoc] ENROLL_STATES entering state 10 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.175: Wait for finger on sensor 181s (process:2302): libfprint-device-DEBUG: 16:48:18.175: Device reported finger status change: FP_FINGER_STATUS_NEEDED 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.176: Finger on sensor callback 181s (process:2302): libfprint-device-DEBUG: 16:48:18.176: Device reported finger status change: FP_FINGER_STATUS_PRESENT 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.176: [egismoc] ENROLL_STATES entering state 11 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.176: Execute command and get response 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.176: Get check bytes 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.176: [egismoc] CMD_STATES entering state 0 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.176: [egismoc] CMD_STATES entering state 1 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.176: Command receive callback 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.176: [egismoc] CMD_STATES completed successfully 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.176: Read capture callback 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.177: Response prefix valid: yes 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.177: Response suffix valid: NO 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.177: Response prefix valid: yes 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.177: Response suffix valid: yes 181s (process:2302): libfprint-device-DEBUG: 16:48:18.177: Device reported enroll progress, reported 3 of 10 have been completed 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.177: [egismoc] ENROLL_STATES entering state 8 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.177: Execute command and get response 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.177: Get check bytes 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.177: [egismoc] CMD_STATES entering state 0 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.177: [egismoc] CMD_STATES entering state 1 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.178: Command receive callback 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.178: [egismoc] CMD_STATES completed successfully 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.178: Task SSM next state callback 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.178: [egismoc] ENROLL_STATES entering state 9 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.178: Execute command and get response 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.178: Get check bytes 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.178: [egismoc] CMD_STATES entering state 0 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.178: [egismoc] CMD_STATES entering state 1 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.179: Command receive callback 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.179: [egismoc] CMD_STATES completed successfully 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.179: Task SSM next state callback 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.179: [egismoc] ENROLL_STATES entering state 10 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.179: Wait for finger on sensor 181s (process:2302): libfprint-device-DEBUG: 16:48:18.179: Device reported finger status change: FP_FINGER_STATUS_NEEDED 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.179: Finger on sensor callback 181s (process:2302): libfprint-device-DEBUG: 16:48:18.179: Device reported finger status change: FP_FINGER_STATUS_PRESENT 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.179: [egismoc] ENROLL_STATES entering state 11 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.179: Execute command and get response 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.179: Get check bytes 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.179: [egismoc] CMD_STATES entering state 0 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.180: [egismoc] CMD_STATES entering state 1 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.180: Command receive callback 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.180: [egismoc] CMD_STATES completed successfully 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.180: Read capture callback 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.180: Response prefix valid: yes 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.180: Response suffix valid: NO 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.180: Response prefix valid: yes 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.180: Response suffix valid: yes 181s (process:2302): libfprint-device-DEBUG: 16:48:18.180: Device reported enroll progress, reported 3 of 10 have been completed 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.180: [egismoc] ENROLL_STATES entering state 8 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.180: Execute command and get response 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.180: Get check bytes 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.180: [egismoc] CMD_STATES entering state 0 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.181: [egismoc] CMD_STATES entering state 1 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.181: Command receive callback 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.181: [egismoc] CMD_STATES completed successfully 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.181: Task SSM next state callback 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.181: [egismoc] ENROLL_STATES entering state 9 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.181: Execute command and get response 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.181: Get check bytes 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.181: [egismoc] CMD_STATES entering state 0 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.182: [egismoc] CMD_STATES entering state 1 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.182: Command receive callback 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.182: [egismoc] CMD_STATES completed successfully 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.182: Task SSM next state callback 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.182: [egismoc] ENROLL_STATES entering state 10 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.182: Wait for finger on sensor 181s (process:2302): libfprint-device-DEBUG: 16:48:18.182: Device reported finger status change: FP_FINGER_STATUS_NEEDED 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.183: Finger on sensor callback 181s (process:2302): libfprint-device-DEBUG: 16:48:18.183: Device reported finger status change: FP_FINGER_STATUS_PRESENT 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.183: [egismoc] ENROLL_STATES entering state 11 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.183: Execute command and get response 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.183: Get check bytes 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.183: [egismoc] CMD_STATES entering state 0 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.183: [egismoc] CMD_STATES entering state 1 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.184: Command receive callback 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.184: [egismoc] CMD_STATES completed successfully 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.184: Read capture callback 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.184: Response prefix valid: yes 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.184: Response suffix valid: yes 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.184: Partial capture successful. Please touch the sensor again (4/10) 181s (process:2302): libfprint-device-DEBUG: 16:48:18.184: Device reported enroll progress, reported 4 of 10 have been completed 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.184: [egismoc] ENROLL_STATES entering state 8 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.184: Execute command and get response 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.184: Get check bytes 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.184: [egismoc] CMD_STATES entering state 0 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.184: [egismoc] CMD_STATES entering state 1 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.185: Command receive callback 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.185: [egismoc] CMD_STATES completed successfully 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.185: Task SSM next state callback 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.185: [egismoc] ENROLL_STATES entering state 9 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.185: Execute command and get response 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.185: Get check bytes 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.185: [egismoc] CMD_STATES entering state 0 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.185: [egismoc] CMD_STATES entering state 1 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.186: Command receive callback 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.186: [egismoc] CMD_STATES completed successfully 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.186: Task SSM next state callback 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.186: [egismoc] ENROLL_STATES entering state 10 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.186: Wait for finger on sensor 181s (process:2302): libfprint-device-DEBUG: 16:48:18.186: Device reported finger status change: FP_FINGER_STATUS_NEEDED 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.186: Finger on sensor callback 181s (process:2302): libfprint-device-DEBUG: 16:48:18.186: Device reported finger status change: FP_FINGER_STATUS_PRESENT 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.186: [egismoc] ENROLL_STATES entering state 11 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.186: Execute command and get response 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.186: Get check bytes 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.186: [egismoc] CMD_STATES entering state 0 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.187: [egismoc] CMD_STATES entering state 1 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.187: Command receive callback 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.187: [egismoc] CMD_STATES completed successfully 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.187: Read capture callback 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.187: Response prefix valid: yes 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.187: Response suffix valid: yes 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.187: Partial capture successful. Please touch the sensor again (5/10) 181s (process:2302): libfprint-device-DEBUG: 16:48:18.187: Device reported enroll progress, reported 5 of 10 have been completed 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.187: [egismoc] ENROLL_STATES entering state 8 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.187: Execute command and get response 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.187: Get check bytes 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.187: [egismoc] CMD_STATES entering state 0 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.188: [egismoc] CMD_STATES entering state 1 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.188: Command receive callback 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.188: [egismoc] CMD_STATES completed successfully 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.188: Task SSM next state callback 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.188: [egismoc] ENROLL_STATES entering state 9 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.188: Execute command and get response 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.188: Get check bytes 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.188: [egismoc] CMD_STATES entering state 0 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.189: [egismoc] CMD_STATES entering state 1 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.189: Command receive callback 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.189: [egismoc] CMD_STATES completed successfully 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.189: Task SSM next state callback 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.189: [egismoc] ENROLL_STATES entering state 10 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.189: Wait for finger on sensor 181s (process:2302): libfprint-device-DEBUG: 16:48:18.189: Device reported finger status change: FP_FINGER_STATUS_NEEDED 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.190: Finger on sensor callback 181s (process:2302): libfprint-device-DEBUG: 16:48:18.190: Device reported finger status change: FP_FINGER_STATUS_PRESENT 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.190: [egismoc] ENROLL_STATES entering state 11 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.190: Execute command and get response 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.190: Get check bytes 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.190: [egismoc] CMD_STATES entering state 0 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.190: [egismoc] CMD_STATES entering state 1 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.191: Command receive callback 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.191: [egismoc] CMD_STATES completed successfully 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.191: Read capture callback 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.191: Response prefix valid: yes 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.191: Response suffix valid: yes 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.191: Partial capture successful. Please touch the sensor again (6/10) 181s (process:2302): libfprint-device-DEBUG: 16:48:18.191: Device reported enroll progress, reported 6 of 10 have been completed 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.191: [egismoc] ENROLL_STATES entering state 8 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.191: Execute command and get response 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.191: Get check bytes 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.191: [egismoc] CMD_STATES entering state 0 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.191: [egismoc] CMD_STATES entering state 1 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.192: Command receive callback 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.192: [egismoc] CMD_STATES completed successfully 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.192: Task SSM next state callback 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.192: [egismoc] ENROLL_STATES entering state 9 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.192: Execute command and get response 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.192: Get check bytes 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.192: [egismoc] CMD_STATES entering state 0 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.193: [egismoc] CMD_STATES entering state 1 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.193: Command receive callback 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.193: [egismoc] CMD_STATES completed successfully 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.193: Task SSM next state callback 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.193: [egismoc] ENROLL_STATES entering state 10 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.193: Wait for finger on sensor 181s (process:2302): libfprint-device-DEBUG: 16:48:18.193: Device reported finger status change: FP_FINGER_STATUS_NEEDED 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.193: Finger on sensor callback 181s (process:2302): libfprint-device-DEBUG: 16:48:18.194: Device reported finger status change: FP_FINGER_STATUS_PRESENT 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.194: [egismoc] ENROLL_STATES entering state 11 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.194: Execute command and get response 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.194: Get check bytes 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.194: [egismoc] CMD_STATES entering state 0 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.194: [egismoc] CMD_STATES entering state 1 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.194: Command receive callback 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.195: [egismoc] CMD_STATES completed successfully 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.195: Read capture callback 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.195: Response prefix valid: yes 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.195: Response suffix valid: yes 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.195: Partial capture successful. Please touch the sensor again (7/10) 181s (process:2302): libfprint-device-DEBUG: 16:48:18.195: Device reported enroll progress, reported 7 of 10 have been completed 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.195: [egismoc] ENROLL_STATES entering state 8 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.195: Execute command and get response 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.195: Get check bytes 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.195: [egismoc] CMD_STATES entering state 0 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.195: [egismoc] CMD_STATES entering state 1 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.196: Command receive callback 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.196: [egismoc] CMD_STATES completed successfully 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.196: Task SSM next state callback 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.196: [egismoc] ENROLL_STATES entering state 9 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.196: Execute command and get response 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.196: Get check bytes 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.196: [egismoc] CMD_STATES entering state 0 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.196: [egismoc] CMD_STATES entering state 1 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.197: Command receive callback 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.197: [egismoc] CMD_STATES completed successfully 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.197: Task SSM next state callback 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.197: [egismoc] ENROLL_STATES entering state 10 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.197: Wait for finger on sensor 181s (process:2302): libfprint-device-DEBUG: 16:48:18.197: Device reported finger status change: FP_FINGER_STATUS_NEEDED 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.197: Finger on sensor callback 181s (process:2302): libfprint-device-DEBUG: 16:48:18.197: Device reported finger status change: FP_FINGER_STATUS_PRESENT 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.197: [egismoc] ENROLL_STATES entering state 11 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.197: Execute command and get response 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.197: Get check bytes 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.197: [egismoc] CMD_STATES entering state 0 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.198: [egismoc] CMD_STATES entering state 1 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.198: Command receive callback 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.198: [egismoc] CMD_STATES completed successfully 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.198: Read capture callback 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.198: Response prefix valid: yes 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.198: Response suffix valid: yes 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.198: Partial capture successful. Please touch the sensor again (8/10) 181s (process:2302): libfprint-device-DEBUG: 16:48:18.198: Device reported enroll progress, reported 8 of 10 have been completed 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.198: [egismoc] ENROLL_STATES entering state 8 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.198: Execute command and get response 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.198: Get check bytes 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.198: [egismoc] CMD_STATES entering state 0 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.199: [egismoc] CMD_STATES entering state 1 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.199: Command receive callback 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.199: [egismoc] CMD_STATES completed successfully 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.199: Task SSM next state callback 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.199: [egismoc] ENROLL_STATES entering state 9 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.199: Execute command and get response 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.199: Get check bytes 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.199: [egismoc] CMD_STATES entering state 0 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.200: [egismoc] CMD_STATES entering state 1 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.200: Command receive callback 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.200: [egismoc] CMD_STATES completed successfully 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.200: Task SSM next state callback 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.200: [egismoc] ENROLL_STATES entering state 10 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.200: Wait for finger on sensor 181s (process:2302): libfprint-device-DEBUG: 16:48:18.200: Device reported finger status change: FP_FINGER_STATUS_NEEDED 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.201: Finger on sensor callback 181s (process:2302): libfprint-device-DEBUG: 16:48:18.201: Device reported finger status change: FP_FINGER_STATUS_PRESENT 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.201: [egismoc] ENROLL_STATES entering state 11 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.201: Execute command and get response 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.201: Get check bytes 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.201: [egismoc] CMD_STATES entering state 0 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.201: [egismoc] CMD_STATES entering state 1 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.201: Command receive callback 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.201: [egismoc] CMD_STATES completed successfully 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.202: Read capture callback 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.202: Response prefix valid: yes 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.202: Response suffix valid: yes 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.202: Partial capture successful. Please touch the sensor again (9/10) 181s (process:2302): libfprint-device-DEBUG: 16:48:18.202: Device reported enroll progress, reported 9 of 10 have been completed 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.202: [egismoc] ENROLL_STATES entering state 8 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.202: Execute command and get response 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.202: Get check bytes 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.202: [egismoc] CMD_STATES entering state 0 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.202: [egismoc] CMD_STATES entering state 1 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.203: Command receive callback 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.203: [egismoc] CMD_STATES completed successfully 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.203: Task SSM next state callback 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.203: [egismoc] ENROLL_STATES entering state 9 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.203: Execute command and get response 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.203: Get check bytes 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.203: [egismoc] CMD_STATES entering state 0 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.203: [egismoc] CMD_STATES entering state 1 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.204: Command receive callback 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.204: [egismoc] CMD_STATES completed successfully 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.204: Task SSM next state callback 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.204: [egismoc] ENROLL_STATES entering state 10 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.204: Wait for finger on sensor 181s (process:2302): libfprint-device-DEBUG: 16:48:18.204: Device reported finger status change: FP_FINGER_STATUS_NEEDED 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.204: Finger on sensor callback 181s (process:2302): libfprint-device-DEBUG: 16:48:18.204: Device reported finger status change: FP_FINGER_STATUS_PRESENT 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.204: [egismoc] ENROLL_STATES entering state 11 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.204: Execute command and get response 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.204: Get check bytes 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.204: [egismoc] CMD_STATES entering state 0 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.205: [egismoc] CMD_STATES entering state 1 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.205: Command receive callback 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.205: [egismoc] CMD_STATES completed successfully 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.205: Read capture callback 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.205: Response prefix valid: yes 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.205: Response suffix valid: NO 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.205: Response prefix valid: yes 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.205: Response suffix valid: yes 181s (process:2302): libfprint-device-DEBUG: 16:48:18.205: Device reported enroll progress, reported 9 of 10 have been completed 181s listing - device should have prints 181s clear device storage 181s clear done 181s listing - device should be empty 181s enrolling 181s finger status: 181s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xf1f82dec8200 (FpiDeviceEgisMoc at 0x15c41080)>, 1, , None, None) 181s finger status: 181s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xf1f82dec8200 (FpiDeviceEgisMoc at 0x15c41080)>, 2, , None, None) 181s finger status: 181s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xf1f82dec8200 (FpiDeviceEgisMoc at 0x15c41080)>, 2, None, None, GLib.Error('The finger was not centered properly, please try again.', 'fp - device - retry - quark', 2)) 181s finger status: 181s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xf1f82dec8200 (FpiDeviceEgisMoc at 0x15c41080)>, 3, , None, None) 181s finger status: 181s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xf1f82dec8200 (FpiDeviceEgisMoc at 0x15c41080)>, 4, , None, None) 181s finger status: 181s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xf1f82dec8200 (FpiDeviceEgisMoc at 0x15c41080)>, 4, None, None, GLib.Error('The finger was not centered properly, please try again.', 'fp - device - retry - quark', 2)) 181s finger status: 181s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xf1f82dec8200 (FpiDeviceEgisMoc at 0x15c41080)>, 5, , None, None) 181s finger status: 181s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xf1f82dec8200 (FpiDeviceEgisMoc at 0x15c41080)>, 6, , None, None) 181s finger status: 181s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xf1f82dec8200 (FpiDeviceEgisMoc at 0x15c41080)>, 6, None, None, GLib.Error('The finger was not centered properly, please try again.', 'fp - device - retry - quark', 2)) 181s finger status: 181s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xf1f82dec8200 (FpiDeviceEgisMoc at 0x15c41080)>, 6, None, None, GLib.Error('The finger was not centered properly, please try again.', 'fp - device - retry - quark', 2)) 181s finger status: 181s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xf1f82dec8200 (FpiDeviceEgisMoc at 0x15c41080)>, 7, , None, None) 181s finger status: 181s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xf1f82dec8200 (FpiDeviceEgisMoc at 0x15c41080)>, 8, , None, None) 181s finger status: 181s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xf1f82dec8200 (FpiDeviceEgisMoc at 0x15c41080)>, 9, , None, None) 181s finger status: 181s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xf1f82dec8200 (FpiDeviceEgisMoc at 0x15c41080)>, 9, None, None, GLib.Error('The finger was not centered properly, please try again.', 'fp - device - retry - quark', 2)) 181s finger status: 181s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xf1f82dec8200 (FpiDeviceEgisMoc at 0x15c41080)>, 10, , None, None) 181s enroll done 181s listing - device should have 1 print 181s verifying 181s verify done 181s async identifying 181s indentification_done: 181s try to enroll duplicate 181s duplicate enroll attempt done 181s listing - device should still only have 1 print 181s enroll new finger 181s finger status: 181s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xf1f82dec8200 (FpiDeviceEgisMoc at 0x15c41080)>, 1, , None, None) 181s finger status: 181s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xf1f82dec8200 (FpiDeviceEgisMoc at 0x15c41080)>, 1, None, None, GLib.Error('The finger was not centered properly, please try again.', 'fp - device - retry - quark', 2)) 181s finger status: 181s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xf1f82dec8200 (FpiDeviceEgisMoc at 0x15c41080)>, 2, , None, None) 181s finger status: 181s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xf1f82dec8200 (FpiDeviceEgisMoc at 0x15c41080)>, 3, , None, None) 181s finger status: 181s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xf1f82dec8200 (FpiDeviceEgisMoc at 0x15c41080)>, 3, None, None, GLib.Error('The finger was not centered properly, please try again.', 'fp - device - retry - quark', 2)) 181s finger status: 181s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xf1f82dec8200 (FpiDeviceEgisMoc at 0x15c41080)>, 3, None, None, GLib.Error('The finger was not centered properly, please try again.', 'fp - device - retry - quark', 2)) 181s finger status: 181s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xf1f82dec8200 (FpiDeviceEgisMoc at 0x15c41080)>, 4, , None, None) 181s finger status: 181s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xf1f82dec8200 (FpiDeviceEgisMoc at 0x15c41080)>, 5, , None, None) 181s finger status: 181s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xf1f82dec8200 (FpiDeviceEgisMoc at 0x15c41080)>, 6, , None, None) 181s finger status: 181s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xf1f82dec8200 (FpiDeviceEgisMoc at 0x15c41080)>, 7, , None, None) 181s finger status: 181s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xf1f82dec8200 (FpiDeviceEgisMoc at 0x15c41080)>, 8, , None, None) 181s finger status: 181s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xf1f82dec8200 (FpiDeviceEgisMoc at 0x15c41080)>, 9, , None, None) 181s finger status: 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.205: [egismoc] ENROLL_STATES entering state 8 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.205: Execute command and get response 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.205: Get check bytes 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.205: [egismoc] CMD_STATES entering state 0 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.206: [egismoc] CMD_STATES entering state 1 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.206: Command receive callback 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.206: [egismoc] CMD_STATES completed successfully 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.206: Task SSM next state callback 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.206: [egismoc] ENROLL_STATES entering state 9 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.206: Execute command and get response 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.206: Get check bytes 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.206: [egismoc] CMD_STATES entering state 0 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.207: [egismoc] CMD_STATES entering state 1 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.207: Command receive callback 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.207: [egismoc] CMD_STATES completed successfully 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.207: Task SSM next state callback 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.207: [egismoc] ENROLL_STATES entering state 10 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.207: Wait for finger on sensor 181s (process:2302): libfprint-device-DEBUG: 16:48:18.207: Device reported finger status change: FP_FINGER_STATUS_NEEDED 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.208: Finger on sensor callback 181s (process:2302): libfprint-device-DEBUG: 16:48:18.208: Device reported finger status change: FP_FINGER_STATUS_PRESENT 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.208: [egismoc] ENROLL_STATES entering state 11 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.208: Execute command and get response 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.208: Get check bytes 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.208: [egismoc] CMD_STATES entering state 0 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.208: [egismoc] CMD_STATES entering state 1 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.209: Command receive callback 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.209: [egismoc] CMD_STATES completed successfully 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.209: Read capture callback 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.209: Response prefix valid: yes 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.209: Response suffix valid: NO 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.209: Response prefix valid: yes 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.209: Response suffix valid: yes 181s (process:2302): libfprint-device-DEBUG: 16:48:18.209: Device reported enroll progress, reported 9 of 10 have been completed 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.209: [egismoc] ENROLL_STATES entering state 8 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.209: Execute command and get response 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.209: Get check bytes 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.209: [egismoc] CMD_STATES entering state 0 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.209: [egismoc] CMD_STATES entering state 1 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.210: Command receive callback 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.210: [egismoc] CMD_STATES completed successfully 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.210: Task SSM next state callback 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.210: [egismoc] ENROLL_STATES entering state 9 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.210: Execute command and get response 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.210: Get check bytes 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.210: [egismoc] CMD_STATES entering state 0 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.210: [egismoc] CMD_STATES entering state 1 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.211: Command receive callback 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.211: [egismoc] CMD_STATES completed successfully 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.211: Task SSM next state callback 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.211: [egismoc] ENROLL_STATES entering state 10 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.211: Wait for finger on sensor 181s (process:2302): libfprint-device-DEBUG: 16:48:18.211: Device reported finger status change: FP_FINGER_STATUS_NEEDED 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.211: Finger on sensor callback 181s (process:2302): libfprint-device-DEBUG: 16:48:18.211: Device reported finger status change: FP_FINGER_STATUS_PRESENT 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.211: [egismoc] ENROLL_STATES entering state 11 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.211: Execute command and get response 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.211: Get check bytes 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.211: [egismoc] CMD_STATES entering state 0 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.212: [egismoc] CMD_STATES entering state 1 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.212: Command receive callback 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.212: [egismoc] CMD_STATES completed successfully 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.212: Read capture callback 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.212: Response prefix valid: yes 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.212: Response suffix valid: NO 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.212: Response prefix valid: yes 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.212: Response suffix valid: yes 181s (process:2302): libfprint-device-DEBUG: 16:48:18.212: Device reported enroll progress, reported 9 of 10 have been completed 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.212: [egismoc] ENROLL_STATES entering state 8 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.212: Execute command and get response 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.212: Get check bytes 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.212: [egismoc] CMD_STATES entering state 0 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.213: [egismoc] CMD_STATES entering state 1 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.213: Command receive callback 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.213: [egismoc] CMD_STATES completed successfully 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.213: Task SSM next state callback 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.213: [egismoc] ENROLL_STATES entering state 9 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.213: Execute command and get response 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.213: Get check bytes 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.213: [egismoc] CMD_STATES entering state 0 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.214: [egismoc] CMD_STATES entering state 1 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.214: Command receive callback 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.214: [egismoc] CMD_STATES completed successfully 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.214: Task SSM next state callback 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.214: [egismoc] ENROLL_STATES entering state 10 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.214: Wait for finger on sensor 181s (process:2302): libfprint-device-DEBUG: 16:48:18.214: Device reported finger status change: FP_FINGER_STATUS_NEEDED 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.215: Finger on sensor callback 181s (process:2302): libfprint-device-DEBUG: 16:48:18.215: Device reported finger status change: FP_FINGER_STATUS_PRESENT 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.215: [egismoc] ENROLL_STATES entering state 11 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.215: Execute command and get response 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.215: Get check bytes 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.215: [egismoc] CMD_STATES entering state 0 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.215: [egismoc] CMD_STATES entering state 1 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.216: Command receive callback 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.216: [egismoc] CMD_STATES completed successfully 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.216: Read capture callback 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.216: Response prefix valid: yes 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.216: Response suffix valid: yes 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.216: Partial capture successful. Please touch the sensor again (10/10) 181s (process:2302): libfprint-device-DEBUG: 16:48:18.216: Device reported enroll progress, reported 10 of 10 have been completed 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.216: [egismoc] ENROLL_STATES entering state 12 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.216: Execute command and get response 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.216: Get check bytes 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.216: [egismoc] CMD_STATES entering state 0 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.216: [egismoc] CMD_STATES entering state 1 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.217: Command receive callback 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.217: [egismoc] CMD_STATES completed successfully 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.217: Task SSM next state callback 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.217: [egismoc] ENROLL_STATES entering state 13 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.217: New fingerprint ID: FP1-00000000-7-00000000-nobody 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.217: Execute command and get response 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.217: Get check bytes 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.217: [egismoc] CMD_STATES entering state 0 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.217: [egismoc] CMD_STATES entering state 1 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.218: Command receive callback 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.218: [egismoc] CMD_STATES completed successfully 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.218: Task SSM next state callback 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.218: [egismoc] ENROLL_STATES entering state 14 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.218: Execute command and get response 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.218: Get check bytes 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.218: [egismoc] CMD_STATES entering state 0 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.218: [egismoc] CMD_STATES entering state 1 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.219: Command receive callback 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.219: [egismoc] CMD_STATES completed successfully 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.219: Task SSM next state callback 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.219: [egismoc] ENROLL_STATES entering state 15 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.219: Enrollment was successful! 181s (process:2302): libfprint-device-DEBUG: 16:48:18.219: Device reported enroll completion 181s (process:2302): libfprint-device-DEBUG: 16:48:18.219: Device reported finger status change: FP_FINGER_STATUS_NONE 181s (process:2302): libfprint-device-DEBUG: 16:48:18.219: Print for finger FP_FINGER_RIGHT_INDEX enrolled 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.219: [egismoc] ENROLL_STATES completed successfully 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.219: Task SSM done 181s (process:2302): libfprint-device-DEBUG: 16:48:18.219: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 181s (process:2302): libfprint-device-DEBUG: 16:48:18.219: Updated temperature model after 0.07 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.219: List 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.219: [egismoc] LIST_STATES entering state 0 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.219: Execute command and get response 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.219: Get check bytes 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.219: [egismoc] CMD_STATES entering state 0 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.219: [egismoc] CMD_STATES entering state 1 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.220: Command receive callback 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.220: [egismoc] CMD_STATES completed successfully 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.220: List callback 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.220: Device fingerprint 0: FP1-00000000-2-00000000-nobody 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.220: Device fingerprint 1: FP1-00000000-7-00000000-nobody 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.220: Number of currently enrolled fingerprints on the device is 2 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.220: [egismoc] LIST_STATES entering state 1 181s (process:2302): libfprint-device-DEBUG: 16:48:18.220: Device reported listing completion 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.220: [egismoc] LIST_STATES completed successfully 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.220: Task SSM done 181s (process:2302): libfprint-device-DEBUG: 16:48:18.220: Completing action FPI_DEVICE_ACTION_LIST in idle! 181s (process:2302): libfprint-device-DEBUG: 16:48:18.220: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.220: Delete 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.220: [egismoc] DELETE_STATES entering state 0 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.220: Execute command and get response 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.220: Get check bytes 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.220: [egismoc] CMD_STATES entering state 0 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.221: [egismoc] CMD_STATES entering state 1 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.221: Command receive callback 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.221: [egismoc] CMD_STATES completed successfully 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.221: List callback 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.221: Device fingerprint 0: FP1-00000000-2-00000000-nobody 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.221: Device fingerprint 1: FP1-00000000-7-00000000-nobody 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.221: Number of currently enrolled fingerprints on the device is 2 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.221: [egismoc] DELETE_STATES entering state 1 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.221: Get delete command 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.221: Delete fingerprint FP1-00000000-2-00000000-nobody (FP1-00000000-2-00000000-nobody) 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.221: Execute command and get response 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.221: Get check bytes 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.221: [egismoc] CMD_STATES entering state 0 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.222: [egismoc] CMD_STATES entering state 1 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.222: Command receive callback 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.222: [egismoc] CMD_STATES completed successfully 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.222: Delete callback 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.222: Response prefix valid: yes 181s (process:2302): libfprint-device-DEBUG: 16:48:18.222: Device reported deletion completion 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.222: [egismoc] DELETE_STATES completed successfully 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.222: Task SSM done 181s (process:2302): libfprint-device-DEBUG: 16:48:18.222: Completing action FPI_DEVICE_ACTION_DELETE in idle! 181s (process:2302): libfprint-device-DEBUG: 16:48:18.222: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.222: List 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.222: [egismoc] LIST_STATES entering state 0 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.222: Execute command and get response 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.222: Get check bytes 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.222: [egismoc] CMD_STATES entering state 0 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.223: [egismoc] CMD_STATES entering state 1 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.223: Command receive callback 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.223: [egismoc] CMD_STATES completed successfully 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.223: List callback 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.223: Device fingerprint 0: FP1-00000000-7-00000000-nobody 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.223: Number of currently enrolled fingerprints on the device is 1 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.223: [egismoc] LIST_STATES entering state 1 181s (process:2302): libfprint-device-DEBUG: 16:48:18.223: Device reported listing completion 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.223: [egismoc] LIST_STATES completed successfully 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.223: Task SSM done 181s (process:2302): libfprint-device-DEBUG: 16:48:18.223: Completing action FPI_DEVICE_ACTION_LIST in idle! 181s (process:2302): libfprint-device-DEBUG: 16:48:18.223: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.223: Clear storage 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.223: [egismoc] DELETE_STATES entering state 0 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.223: Execute command and get response 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.223: Get check bytes 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.223: [egismoc] CMD_STATES entering state 0 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.224: [egismoc] CMD_STATES entering state 1 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.224: Command receive callback 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.224: [egismoc] CMD_STATES completed successfully 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.224: List callback 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.224: Device fingerprint 0: FP1-00000000-7-00000000-nobody 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.225: Number of currently enrolled fingerprints on the device is 1 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.225: [egismoc] DELETE_STATES entering state 1 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.225: Get delete command 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.225: Execute command and get response 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.225: Get check bytes 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.225: [egismoc] CMD_STATES entering state 0 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.225: [egismoc] CMD_STATES entering state 1 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.225: Command receive callback 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.225: [egismoc] CMD_STATES completed successfully 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.226: Delete callback 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.226: Response prefix valid: yes 181s (process:2302): libfprint-device-DEBUG: 16:48:18.226: Device reported deletion completion 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.226: [egismoc] DELETE_STATES completed successfully 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.226: Task SSM done 181s (process:2302): libfprint-device-DEBUG: 16:48:18.226: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 181s (process:2302): libfprint-device-DEBUG: 16:48:18.226: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.226: List 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.226: [egismoc] LIST_STATES entering state 0 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.226: Execute command and get response 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.226: Get check bytes 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.226: [egismoc] CMD_STATES entering state 0 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.226: [egismoc] CMD_STATES entering state 1 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.227: Command receive callback 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.227: [egismoc] CMD_STATES completed successfully 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.227: List callback 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.227: Number of currently enrolled fingerprints on the device is 0 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.227: [egismoc] LIST_STATES entering state 1 181s (process:2302): libfprint-device-DEBUG: 16:48:18.227: Device reported listing completion 181s (process:2302): libfprint-SSM-DEBUG: 16:48:18.227: [egismoc] LIST_STATES completed successfully 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.227: Task SSM done 181s (process:2302): libfprint-device-DEBUG: 16:48:18.227: Completing action FPI_DEVICE_ACTION_LIST in idle! 181s (process:2302): libfprint-device-DEBUG: 16:48:18.227: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.227: Closing device 181s (process:2302): libfprint-egismoc-DEBUG: 16:48:18.227: Cancel 181s (process:2302): libfprint-device-DEBUG: 16:48:18.227: Device reported close completion 181s (process:2302): libfprint-device-DEBUG: 16:48:18.227: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 181s (process:2302): libfprint-device-DEBUG: 16:48:18.227: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 181s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xf1f82dec8200 (FpiDeviceEgisMoc at 0x15c41080)>, 9, None, None, GLib.Error('The finger was not centered properly, please try again.', 'fp - device - retry - quark', 2)) 181s finger status: 181s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xf1f82dec8200 (FpiDeviceEgisMoc at 0x15c41080)>, 9, None, None, GLib.Error('The finger was not centered properly, please try again.', 'fp - device - retry - quark', 2)) 181s finger status: 181s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xf1f82dec8200 (FpiDeviceEgisMoc at 0x15c41080)>, 9, None, None, GLib.Error('The finger was not centered properly, please try again.', 'fp - device - retry - quark', 2)) 181s finger status: 181s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xf1f82dec8200 (FpiDeviceEgisMoc at 0x15c41080)>, 10, , None, None) 181s enroll new finger done 181s listing - device should have 2 prints 181s deleting first print 181s delete done 181s listing - device should only have second print 181s clear device storage 181s clear done 181s listing - device should be empty 181s ** (umockdev-run:2298): DEBUG: 16:48:18.240: umockdev.vala:150: Removing test bed /tmp/umockdev.3SFZJ2 181s (umockdev-run:2298): GLib-DEBUG: 16:48:18.245: unsetenv() is not thread-safe and should not be used after threads are created 181s PASS: libfprint-2/driver-egismoc.test 181s Running test: libfprint-2/driver-vfs7552.test 181s ** (umockdev-run:2310): DEBUG: 16:48:18.334: umockdev.vala:123: Created udev test bed /tmp/umockdev.DPB9J2 181s ** (umockdev-run:2310): DEBUG: 16:48:18.334: umockdev.vala:1297: parsing device description for /devices/pci0000:00/0000:00:14.0/usb1/1-7 181s ** (umockdev-run:2310): DEBUG: 16:48:18.335: umockdev.vala:1366: creating device /devices/pci0000:00/0000:00:14.0/usb1/1-7 (subsystem usb) 181s ** (umockdev-run:2310): DEBUG: 16:48:18.337: umockdev.vala:1411: create_node_for_device: creating file device /tmp/umockdev.DPB9J2/dev/bus/usb/001/003 181s ** (umockdev-run:2310): DEBUG: 16:48:18.337: umockdev.vala:1297: parsing device description for /devices/pci0000:00/0000:00:14.0/usb1 181s ** (umockdev-run:2310): DEBUG: 16:48:18.338: umockdev.vala:1366: creating device /devices/pci0000:00/0000:00:14.0/usb1 (subsystem usb) 181s ** (umockdev-run:2310): DEBUG: 16:48:18.339: umockdev.vala:1411: create_node_for_device: creating file device /tmp/umockdev.DPB9J2/dev/bus/usb/001/001 181s ** (umockdev-run:2310): DEBUG: 16:48:18.340: umockdev.vala:1297: parsing device description for /devices/pci0000:00/0000:00:14.0 181s ** (umockdev-run:2310): DEBUG: 16:48:18.340: umockdev.vala:1366: creating device /devices/pci0000:00/0000:00:14.0 (subsystem pci) 181s (umockdev-run:2310): GLib-GIO-DEBUG: 16:48:18.341: _g_io_module_get_default: Found default implementation local (GLocalVfs) for ?gio-vfs? 181s (process:2314): libfprint-context-DEBUG: 16:48:18.430: Initializing FpContext (libfprint version 1.94.7+tod1) 181s (process:2314): libfprint-tod-DEBUG: 16:48:18.430: Impossible to load the shared drivers dir Error opening directory “/usr/lib/aarch64-linux-gnu/libfprint-2/tod-1”: No such file or directory 181s (process:2314): libfprint-context-DEBUG: 16:48:18.432: No driver found for USB device 1D6B:0002 181s (process:2314): libfprint-device-DEBUG: 16:48:18.432: Device reported probe completion 181s (process:2314): libfprint-device-DEBUG: 16:48:18.432: Completing action FPI_DEVICE_ACTION_PROBE in idle! 181s (process:2314): libfprint-device-DEBUG: 16:48:18.432: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.436: [vfs7552] DEV_OPEN_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.437: [vfs7552] DEVICE OPEN entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.437: Sending vfs7552_cmd_01 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.437: [vfs7552] DEVICE OPEN entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.437: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.437: Got 38 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.437: [vfs7552] DEVICE OPEN entering state 2 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.437: Sending vfs7552_cmd_19 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.438: [vfs7552] DEVICE OPEN entering state 3 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.438: Receiving 128 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.438: Got 68 bytes out of 128 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.438: [vfs7552] DEVICE OPEN entering state 4 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.438: Sending vfs7552_init_00 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.439: [vfs7552] DEVICE OPEN entering state 5 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.439: Receiving 64 bytes 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.439: [vfs7552] DEVICE OPEN entering state 6 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.439: Sending vfs7552_init_01 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.440: [vfs7552] DEVICE OPEN entering state 7 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.440: Receiving 64 bytes 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.440: [vfs7552] DEVICE OPEN entering state 8 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.440: Sending vfs7552_init_02 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.441: [vfs7552] DEVICE OPEN entering state 9 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.441: Receiving 64 bytes 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.441: [vfs7552] DEVICE OPEN entering state 10 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.441: Sending vfs7552_init_03 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.442: [vfs7552] DEVICE OPEN entering state 11 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.442: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.442: Got 10 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.442: [vfs7552] DEVICE OPEN entering state 12 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.442: Sending vfs7552_init_04 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.443: [vfs7552] DEVICE OPEN entering state 13 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.443: Receiving 64 bytes 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.443: [vfs7552] DEVICE OPEN completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.443: [vfs7552] DEV_OPEN_NUM_STATES completed successfully 181s (process:2314): libfprint-image_device-DEBUG: 16:48:18.443: Image device open completed 181s (process:2314): libfprint-device-DEBUG: 16:48:18.443: Device reported open completion 181s (process:2314): libfprint-device-DEBUG: 16:48:18.443: Completing action FPI_DEVICE_ACTION_OPEN in idle! 181s (process:2314): libfprint-device-DEBUG: 16:48:18.443: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 181s (process:2314): libfprint-device-DEBUG: 16:48:18.444: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 181s (process:2314): libfprint-image_device-DEBUG: 16:48:18.444: Activating image device 181s (process:2314): libfprint-image_device-DEBUG: 16:48:18.444: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING 181s (process:2314): libfprint-image_device-DEBUG: 16:48:18.444: Image device activation completed 181s (process:2314): libfprint-image_device-DEBUG: 16:48:18.444: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE 181s (process:2314): libfprint-image_device-DEBUG: 16:48:18.444: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 181s (process:2314): libfprint-device-DEBUG: 16:48:18.444: Device reported finger status change: FP_FINGER_STATUS_NEEDED 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.494: changing to 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.494: [vfs7552] ACTIVATE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.494: [vfs7552] ACTIVATE INIT entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.494: Sending vfs7552_image_start 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.494: [vfs7552] ACTIVATE INIT entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.494: Receiving 2048 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.495: Got 1962 bytes out of 2048 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.495: [vfs7552] ACTIVATE INIT completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.495: [vfs7552] ACTIVATE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.495: [vfs7552] ACTIVATE INTERRUPT QUERY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.495: Receiving 8 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.495: Got 5 bytes out of 8 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.495: [vfs7552] ACTIVATE INTERRUPT QUERY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.495: [vfs7552] ACTIVATE_NUM_STATES entering state 2 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.495: [vfs7552] ACTIVATE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.495: [vfs7552] ACTIVATE INTERRUPT QUERY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.495: Receiving 8 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.496: Got 5 bytes out of 8 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.496: [vfs7552] ACTIVATE INTERRUPT QUERY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.496: [vfs7552] ACTIVATE_NUM_STATES entering state 2 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.496: [vfs7552] ACTIVATE_NUM_STATES entering state 3 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.496: [vfs7552] ACTIVATE_NUM_STATES completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.496: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.496: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.496: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.496: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.496: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.497: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.497: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.497: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.497: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.497: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.497: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.497: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.497: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.498: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.498: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.498: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.498: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.498: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.498: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.498: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.498: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.499: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.499: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.499: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.499: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.499: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.499: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.499: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.499: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.500: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.500: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.500: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.500: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.500: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.500: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-device-DEBUG: 16:48:18.554: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.585: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.585: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.594: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.594: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.594: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.594: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.594: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.594: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.595: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.595: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.595: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.595: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.595: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.595: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.595: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.595: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.596: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.596: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.596: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.596: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.596: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.596: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.596: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.596: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.597: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.597: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.597: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.597: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.597: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.597: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.597: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.597: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.598: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.598: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.598: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.598: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.598: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.598: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.598: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.598: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.599: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.599: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.599: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.599: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.599: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.599: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.599: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.599: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.600: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.600: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.600: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.600: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.600: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.600: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.600: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.600: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.601: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.601: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.601: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.601: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.601: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.601: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.601: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.601: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.601: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.601: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.602: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.602: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.602: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.602: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.602: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.602: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.602: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.602: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.603: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.603: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.603: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.603: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.603: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.603: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.603: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.603: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.604: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.604: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.604: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.604: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.604: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.604: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.604: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.604: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.605: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.605: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.605: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.605: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.605: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.605: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.605: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.605: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.605: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.605: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.605: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.605: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.605: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.605: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.606: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.606: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.606: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.606: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.606: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.606: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.606: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.606: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.607: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.607: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.607: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.607: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.607: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.607: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.607: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.607: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.608: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.608: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.608: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.608: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.608: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.608: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.608: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.608: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.609: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.609: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.609: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.609: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.609: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.609: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.609: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.609: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.610: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.610: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.610: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.610: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.610: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.610: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.610: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.610: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.611: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.611: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.611: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.611: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.611: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.611: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.611: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.611: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.611: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.611: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.612: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.612: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.612: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.612: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.612: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.612: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.612: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.613: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.613: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.613: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.613: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.613: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.613: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.613: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.613: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.613: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.614: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.614: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.614: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.614: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.614: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.614: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.614: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.614: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.615: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.615: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.615: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.615: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.615: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.615: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.615: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.615: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.616: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.616: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.616: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.616: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.616: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.616: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.616: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.616: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.617: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.617: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.617: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.617: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.617: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.617: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.617: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.617: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.618: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.618: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.618: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.618: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.618: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.618: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.618: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.618: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.619: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.619: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.619: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.619: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.619: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.619: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.619: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.619: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.620: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.620: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.620: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.620: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.620: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.620: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.620: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.620: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.621: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.621: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.621: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.621: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.621: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.621: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.621: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.621: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.622: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.622: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.622: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.622: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.622: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.622: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.622: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.622: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.623: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.623: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.623: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.623: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.623: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.623: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.623: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.623: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.624: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.624: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.624: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.624: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.624: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.624: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.624: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.624: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.625: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.625: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.625: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.625: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.625: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.625: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.625: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.625: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.625: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.625: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.625: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.625: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.625: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.625: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.626: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.626: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.626: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.626: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.626: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.626: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.626: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.626: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.627: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.627: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.627: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.627: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.627: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.627: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.627: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.627: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.628: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.628: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.629: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.629: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.629: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.629: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.629: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.629: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.629: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.629: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.630: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.630: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.630: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.630: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.630: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.630: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.630: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.630: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.630: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.630: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.630: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.630: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.630: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.631: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.631: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.631: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.631: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.631: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.631: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.631: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.631: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.631: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.632: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.632: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.632: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.632: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.632: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.632: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.632: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.632: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.633: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.633: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.633: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.633: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.633: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.633: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.633: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.633: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.634: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.634: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.634: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.634: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.634: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.634: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.634: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.634: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.635: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.635: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.635: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.635: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.635: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.635: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.635: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.635: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.636: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.636: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.636: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.636: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.636: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.636: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.636: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.636: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.637: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.637: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.637: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.637: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.637: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.637: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.637: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.637: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.638: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.638: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.638: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.638: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.638: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.638: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.638: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.638: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.639: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.639: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.639: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.639: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.639: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.639: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.639: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.639: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.640: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.640: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.640: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.640: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.640: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.640: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.640: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.640: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.641: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.641: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.641: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.641: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.641: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.641: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.641: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.641: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.642: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.642: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.642: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.642: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.642: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.642: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.642: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.642: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.643: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.643: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.643: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.643: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.643: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.643: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.643: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.643: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.644: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.644: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.644: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.644: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.644: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.644: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.644: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.644: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.645: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.645: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.645: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.645: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.645: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.645: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.645: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.645: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.646: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.646: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.646: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.646: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.646: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.646: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.646: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.646: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.646: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.646: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.647: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.647: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.647: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.647: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.647: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.647: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.647: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.647: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.648: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.648: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.648: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.648: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.648: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.648: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.648: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.648: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.649: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.649: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.649: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.649: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.649: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.649: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.649: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.649: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.650: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.650: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.650: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.650: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.650: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.650: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.650: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.650: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.651: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.651: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.651: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.651: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.651: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.651: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.651: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.651: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.652: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.652: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.652: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.652: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.652: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.652: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.652: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.652: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.653: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.653: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.653: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.653: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.653: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.653: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.653: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.653: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.654: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.654: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.654: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.654: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.654: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.654: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.654: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.654: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.655: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.655: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.655: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.655: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.655: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.655: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.655: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.655: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.656: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.656: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.656: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.656: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.656: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.656: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.656: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.656: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.657: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.657: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.657: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.657: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.657: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.657: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.657: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.657: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.658: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.658: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.658: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.658: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.658: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.658: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.658: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.658: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.658: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.658: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.658: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.658: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.658: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.658: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.659: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.659: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.659: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.659: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.659: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.659: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.659: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.659: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.660: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.660: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.660: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.660: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.660: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.660: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.660: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.660: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.661: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.661: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.661: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.661: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.661: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.661: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.661: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.661: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.662: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.662: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.662: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.662: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.662: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.662: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.662: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.662: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.663: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.663: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.663: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.663: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.663: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.663: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.663: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.663: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.664: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.664: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.664: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.664: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.664: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.664: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.664: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.664: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.665: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.665: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.665: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.665: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.665: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.665: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.665: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.665: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.666: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.666: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.666: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.666: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.666: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.666: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.666: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.666: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.667: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.667: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.667: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.667: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.667: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.667: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.667: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.667: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.668: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.668: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.668: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.668: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.668: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.668: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.668: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.668: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.669: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.669: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.669: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.669: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.669: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.669: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.669: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.669: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.670: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.670: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.670: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.670: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.670: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.670: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.670: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.670: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.671: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.671: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.671: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.671: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.671: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.671: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.671: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.671: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.672: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.672: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.672: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.672: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.672: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.672: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.672: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.672: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.673: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.673: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.673: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.673: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.673: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.673: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.673: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.673: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.674: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.674: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.674: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.674: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.674: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.674: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.674: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.674: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.675: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.675: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.675: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.675: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.675: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.675: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.675: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.675: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.676: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.676: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.676: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.676: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.676: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.676: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.676: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.676: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.676: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.676: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.677: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.677: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.677: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.677: [vfs7552] CAPTURE_NUM_STATES entering state 2 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.677: [vfs7552] REQUEST CHUNK entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.677: Sending vfs7552_read_image_chunk 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.677: [vfs7552] REQUEST CHUNK completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.677: [vfs7552] CAPTURE_NUM_STATES entering state 3 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.678: [vfs7552] CAPTURE_NUM_STATES entering state 2 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.678: [vfs7552] REQUEST CHUNK entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.678: Sending vfs7552_read_image_chunk 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.678: [vfs7552] REQUEST CHUNK completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.678: [vfs7552] CAPTURE_NUM_STATES entering state 3 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.679: [vfs7552] CAPTURE_NUM_STATES entering state 2 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.679: [vfs7552] REQUEST CHUNK entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.679: Sending vfs7552_read_image_chunk 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.679: [vfs7552] REQUEST CHUNK completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.679: [vfs7552] CAPTURE_NUM_STATES entering state 3 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.680: [vfs7552] CAPTURE_NUM_STATES entering state 4 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.680: variance_before = 396 181s 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.680: background stored 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.680: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.680: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.680: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.681: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.681: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.681: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.681: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.681: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.681: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.681: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.681: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.681: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.682: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.682: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.682: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.682: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.682: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.682: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.682: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.682: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.682: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.683: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.683: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.683: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.683: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.683: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.683: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.684: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.684: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.684: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.684: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.684: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.684: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.684: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.684: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.684: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.684: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.685: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.685: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.685: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.685: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.685: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.685: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.686: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.686: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.686: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.686: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.686: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.686: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.686: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.686: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.686: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.686: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.687: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.687: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.687: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.687: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.687: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.687: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.687: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.687: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.688: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.688: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.688: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.688: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.688: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.688: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.688: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.688: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.689: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.689: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.689: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.689: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.689: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.689: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.689: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.689: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.690: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.690: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.690: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.690: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.690: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.690: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.691: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.691: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.691: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.691: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.691: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.691: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.691: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.691: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.691: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.691: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.692: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.692: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.692: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.692: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.692: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.692: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.692: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.692: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.693: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.693: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.693: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.693: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.693: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.693: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.693: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.693: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.694: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.694: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.694: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.694: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.694: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.694: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.695: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.695: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.695: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.695: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.695: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.695: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.695: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.695: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.695: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.695: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.696: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.696: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.696: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.696: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.696: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.696: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.697: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.697: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.697: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.697: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.697: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.697: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.697: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.697: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.697: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.697: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.698: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.698: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.698: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.698: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.698: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.698: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.698: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.698: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.699: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.699: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.699: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.699: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.699: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.699: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.699: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.699: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.700: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.700: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.700: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.700: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.700: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.700: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.700: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.700: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.701: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.701: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.701: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.701: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.701: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.701: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.701: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.701: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.702: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.702: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.702: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.702: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.702: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.702: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.702: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.702: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.703: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.703: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.703: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.703: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.703: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.703: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.703: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.703: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.704: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.704: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.704: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.704: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.704: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.704: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.704: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.704: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.705: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.705: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.705: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.705: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.705: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.705: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.705: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.705: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.706: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.706: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.706: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.706: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.706: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.706: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.706: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.706: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.707: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.707: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.707: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.707: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.707: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.707: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.707: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.707: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.708: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.708: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.708: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.708: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.708: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.708: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.708: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.708: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.709: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.709: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.709: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.709: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.709: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.709: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.709: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.709: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.710: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.710: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.710: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.710: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.710: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.710: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.710: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.710: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.711: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.711: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.711: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.711: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.711: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.711: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.711: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.711: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.712: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.712: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.712: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.712: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.712: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.712: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.712: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.712: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.713: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.713: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.713: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.713: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.713: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.713: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.713: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.713: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.713: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.714: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.714: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.714: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.714: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.714: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.714: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.714: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.714: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.714: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.715: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.715: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.715: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.715: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.715: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.715: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.716: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.716: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.716: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.716: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.716: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.716: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.716: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.716: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.716: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.716: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.716: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.716: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.716: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.716: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.717: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.717: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.717: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.717: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.717: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.717: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.717: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.717: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.718: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.718: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.718: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.718: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.718: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.718: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.718: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.718: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.719: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.719: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.719: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.719: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.719: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.719: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.719: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.719: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.720: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.720: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.720: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.720: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.720: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.720: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.720: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.720: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.721: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.721: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.721: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.721: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.721: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.721: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.721: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.721: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.722: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.722: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.722: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.722: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.722: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.722: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.722: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.722: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.723: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.723: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.723: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.723: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.723: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.723: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.723: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.723: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.724: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.724: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.724: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.724: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.724: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.724: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.724: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.724: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.725: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.725: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.725: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.725: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.725: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.725: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.725: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.725: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.725: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.726: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.726: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.726: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.726: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.726: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.726: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.726: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.726: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.726: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.727: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.727: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.727: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.727: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.727: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.727: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.727: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.727: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.728: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.728: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.728: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.728: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.728: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.728: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.728: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.728: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.729: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.729: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.729: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.729: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.729: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.729: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.729: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.729: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.730: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.730: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.730: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.730: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.730: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.730: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.730: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.730: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.731: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.731: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.731: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.731: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.731: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.731: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.731: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.731: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.732: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.732: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.732: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.732: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.732: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.732: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.732: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.732: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.733: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.733: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.733: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.733: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.733: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.733: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.733: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.733: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.734: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.734: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.734: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.734: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.734: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.734: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.734: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.734: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.735: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.735: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.735: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.735: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.735: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.735: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.735: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.735: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.736: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.736: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.736: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.736: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.736: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.736: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.736: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.736: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.737: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.737: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.737: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.737: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.737: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.737: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.737: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.737: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.738: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.738: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.738: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.738: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.738: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.738: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.738: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.738: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.739: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.739: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.739: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.739: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.739: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.739: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.739: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.739: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.740: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.740: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.740: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.740: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.740: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.740: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.740: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.740: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.741: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.741: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.741: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.741: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.741: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.741: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.741: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.741: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.742: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.742: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.742: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.742: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.742: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.742: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.743: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.743: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.743: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.743: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.743: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.743: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.743: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.743: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.744: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.744: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.744: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.744: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.744: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.744: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.744: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.744: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.744: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.744: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.745: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.745: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.745: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.745: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.745: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.745: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.745: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.746: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.746: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.746: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.746: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.746: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.746: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.746: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.746: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.746: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.747: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.747: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.747: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.747: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.747: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.747: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.747: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.747: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.748: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.748: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.748: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.748: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.748: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.748: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.749: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.749: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.749: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.749: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.749: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.749: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.749: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.749: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.750: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.750: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.750: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.750: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.750: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.750: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.750: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.750: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.751: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.751: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.751: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.751: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.751: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.751: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.751: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.751: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.752: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.752: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.752: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.752: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.752: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.752: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.752: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.752: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.753: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.753: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.753: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.753: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.753: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.753: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.753: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.753: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.753: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.753: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.754: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.754: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.754: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.754: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.754: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.754: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.754: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.754: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.755: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.755: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.755: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.755: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.755: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.755: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.755: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.755: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.756: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.756: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.756: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.756: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.756: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.756: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.756: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.756: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.757: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.757: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.757: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.757: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.757: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.757: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.757: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.757: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.758: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.758: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.758: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.758: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.758: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.758: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.758: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.758: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.759: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.759: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.759: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.759: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.759: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.759: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.759: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.759: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.760: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.760: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.760: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.760: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.760: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.760: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.760: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.760: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.761: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.761: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.761: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.761: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.761: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.761: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.761: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.761: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.761: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.761: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.761: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.761: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.761: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.761: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.762: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.762: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.762: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.762: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.762: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.762: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.762: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.762: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.763: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.763: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.763: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.763: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.763: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.763: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.763: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.763: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.764: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.764: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.764: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.764: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.764: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.764: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.764: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.764: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.765: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.765: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.765: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.765: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.765: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.765: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.765: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.765: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.766: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.766: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.766: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.766: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.766: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.766: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.766: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.766: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.767: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.767: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.767: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.767: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.767: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.767: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.767: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.767: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.768: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.768: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.768: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.768: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.768: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.768: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.768: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.768: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.769: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.769: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.769: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.769: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.769: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.769: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.769: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.769: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.770: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.770: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.770: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.770: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.770: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.770: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.770: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.770: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.771: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.771: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.771: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.771: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.771: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.771: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.771: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.771: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.772: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.772: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.772: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.772: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.772: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.772: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.772: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.772: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.772: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.773: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.773: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.773: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.773: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.773: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.773: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.773: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.773: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.773: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.774: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.774: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.774: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.774: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.774: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.774: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.774: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.774: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.775: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.775: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.775: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.775: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.775: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.775: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.775: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.775: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.776: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.776: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.776: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.776: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.776: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.776: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.776: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.776: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.777: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.777: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.777: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.777: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.777: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.777: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.777: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.777: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.778: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.778: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.778: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.778: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.778: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.778: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.778: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.778: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.779: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.779: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.779: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.779: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.779: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.779: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.779: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.779: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.779: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.780: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.780: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.780: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.780: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.780: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.780: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.780: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.780: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.780: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.780: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.780: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.780: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.780: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.781: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.781: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.781: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.781: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.781: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.781: [vfs7552] CAPTURE_NUM_STATES entering state 2 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.781: [vfs7552] REQUEST CHUNK entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.781: Sending vfs7552_read_image_chunk 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.782: [vfs7552] REQUEST CHUNK completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.782: [vfs7552] CAPTURE_NUM_STATES entering state 3 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.782: [vfs7552] CAPTURE_NUM_STATES entering state 2 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.782: [vfs7552] REQUEST CHUNK entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.782: Sending vfs7552_read_image_chunk 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.783: [vfs7552] REQUEST CHUNK completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.783: [vfs7552] CAPTURE_NUM_STATES entering state 3 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.783: [vfs7552] CAPTURE_NUM_STATES entering state 2 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.783: [vfs7552] REQUEST CHUNK entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.783: Sending vfs7552_read_image_chunk 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.784: [vfs7552] REQUEST CHUNK completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.784: [vfs7552] CAPTURE_NUM_STATES entering state 3 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.784: [vfs7552] CAPTURE_NUM_STATES entering state 4 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.784: Cleaning image 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.784: variance_after = 20 181s 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.784: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.784: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.784: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.785: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.785: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.785: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.785: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.785: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.785: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.785: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.785: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.786: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.786: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.786: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.786: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.786: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.786: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.786: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.786: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.787: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.787: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.787: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.787: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.787: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.787: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.787: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.787: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.788: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.788: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.788: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.788: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.788: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.788: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.788: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.788: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.789: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.789: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.789: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.789: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.789: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.789: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.789: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.789: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.789: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.789: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.790: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.790: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.790: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.790: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.790: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.790: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.790: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.790: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.791: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.791: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.791: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.791: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.791: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.791: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.791: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.791: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.792: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.792: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.792: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.792: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.792: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.792: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.792: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.792: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.793: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.793: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.793: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.793: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.793: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.793: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.793: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.793: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.794: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.794: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.794: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.794: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.794: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.794: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.794: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.794: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.795: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.795: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.795: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.795: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.795: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.795: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.795: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.795: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.796: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.796: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.796: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.796: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.796: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.796: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.796: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.796: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.796: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.796: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.796: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.796: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.796: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.796: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.797: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.797: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.797: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.797: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.797: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.797: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.797: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.797: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.798: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.798: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.798: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.798: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.798: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.798: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.798: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.798: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.799: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.799: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.799: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.799: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.799: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.799: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.799: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.799: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.800: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.800: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.800: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.800: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.800: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.800: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.800: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.800: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.801: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.801: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.801: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.801: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.801: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.801: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.801: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.801: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.802: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.802: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.802: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.802: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.802: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.802: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.802: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.802: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.803: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.803: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.803: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.803: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.803: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.803: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.803: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.803: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.804: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.804: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.804: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.804: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.804: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.804: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.804: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.804: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.805: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.805: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.805: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.805: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.805: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.805: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.805: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.805: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.805: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.805: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.806: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.806: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.806: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.806: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.806: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.806: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.806: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.806: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.807: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.807: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.807: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.807: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.807: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.807: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.807: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.807: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.808: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.808: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.808: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.808: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.808: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.808: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.808: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.808: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.809: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.809: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.809: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.809: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.809: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.809: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.809: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.809: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.810: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.810: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.810: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.810: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.810: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.810: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.810: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.810: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.811: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.811: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.811: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.811: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.811: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.811: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.811: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.811: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.811: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.811: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.811: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.811: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.811: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.811: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.812: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.812: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.812: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.812: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.812: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.812: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.812: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.812: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.813: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.813: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.813: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.814: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.814: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.814: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.814: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.814: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.814: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.814: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.814: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.814: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.814: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.814: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.815: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.815: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.815: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.815: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.815: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.816: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.816: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.816: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.816: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.816: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.816: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.816: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.817: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.817: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.817: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.817: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.817: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.817: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.817: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.817: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.817: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.818: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.818: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.818: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.818: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.818: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.818: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.818: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.818: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.818: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.819: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.819: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.819: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.819: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.819: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.819: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.819: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.819: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.819: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.819: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.819: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.819: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.820: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.820: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.820: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.820: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.820: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.820: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.820: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.820: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.821: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.821: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.821: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.821: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.821: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.821: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.821: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.821: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.822: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.822: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.822: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.822: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.822: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.822: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.822: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.822: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.823: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.823: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.823: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.823: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.823: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.823: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.823: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.823: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.824: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.824: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.824: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.824: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.824: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.824: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.824: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.824: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.825: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.825: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.825: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.825: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.825: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.825: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.825: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.825: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.826: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.826: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.826: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.826: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.826: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.826: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.826: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.826: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.827: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.827: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.827: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.827: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.827: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.827: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.827: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.827: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.828: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.828: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.828: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.828: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.828: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.828: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.828: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.828: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.829: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.829: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.829: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.829: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.829: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.829: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.829: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.829: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.830: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.830: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.830: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.830: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.830: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.830: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.830: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.830: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.831: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.831: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.831: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.831: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.831: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.831: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.831: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.831: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.832: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.832: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.832: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.832: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.832: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.832: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.832: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.832: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.833: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.833: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.833: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.833: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.833: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.833: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.833: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.833: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.834: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.834: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.834: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.834: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.834: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.834: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.834: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.834: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.835: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.835: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.835: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.835: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.835: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.835: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.835: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.835: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.836: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.836: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.836: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.836: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.836: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.836: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.836: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.836: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.837: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.837: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.837: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.837: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.837: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.837: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.837: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.837: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.838: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.838: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.838: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.838: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.838: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.838: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.838: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.838: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.839: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.839: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.839: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.839: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.839: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.839: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.839: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.839: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.840: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.840: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.840: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.840: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.840: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.840: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.840: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.840: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.841: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.841: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.841: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.841: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.841: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.841: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.841: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.841: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.842: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.842: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.842: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.842: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.842: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.842: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.842: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.842: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.843: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.843: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.843: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.843: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.843: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.843: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.843: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.843: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.844: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.844: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.844: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.844: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.844: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.844: [vfs7552] CAPTURE_NUM_STATES entering state 2 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.844: [vfs7552] REQUEST CHUNK entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.844: Sending vfs7552_read_image_chunk 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.845: [vfs7552] REQUEST CHUNK completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.845: [vfs7552] CAPTURE_NUM_STATES entering state 3 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.845: [vfs7552] CAPTURE_NUM_STATES entering state 2 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.845: [vfs7552] REQUEST CHUNK entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.845: Sending vfs7552_read_image_chunk 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.846: [vfs7552] REQUEST CHUNK completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.846: [vfs7552] CAPTURE_NUM_STATES entering state 3 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.846: [vfs7552] CAPTURE_NUM_STATES entering state 2 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.846: [vfs7552] REQUEST CHUNK entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.846: Sending vfs7552_read_image_chunk 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.847: [vfs7552] REQUEST CHUNK completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.847: [vfs7552] CAPTURE_NUM_STATES entering state 3 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.847: [vfs7552] CAPTURE_NUM_STATES entering state 4 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.847: Cleaning image 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.847: variance_after = 18 181s 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.847: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.847: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.847: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.848: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.848: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.848: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.848: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.848: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.848: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.848: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.848: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.849: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.849: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.849: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.849: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.849: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.849: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.849: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.849: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.850: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.850: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.850: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.850: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.850: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.850: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.850: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.850: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.851: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.851: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.851: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.851: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.851: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.851: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.851: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.851: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.852: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.852: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.852: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.852: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.852: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.852: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.852: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.852: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.853: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.853: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.853: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.853: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.853: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.853: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.853: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.853: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.854: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.854: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.854: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.854: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.854: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.854: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.854: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.854: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.855: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.855: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.855: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.855: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.855: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.855: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.855: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.855: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.856: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.856: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.856: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.856: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.856: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.856: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.856: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.856: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.857: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.857: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.857: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.857: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.857: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.857: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.857: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.857: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.858: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.858: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.858: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.858: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.858: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.858: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.858: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.858: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.859: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.859: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.859: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.859: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.859: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.859: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.859: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.859: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.860: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.860: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.860: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.860: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.860: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.860: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.860: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.860: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.861: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.861: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.861: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.861: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.861: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.861: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.861: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.861: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.862: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.862: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.862: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.862: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.862: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.862: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.862: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.862: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.862: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.862: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.863: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.863: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.863: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.863: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.863: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.863: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.863: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.863: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.864: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.864: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.864: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.864: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.864: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.864: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.864: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.864: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.865: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.865: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.865: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.865: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.865: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.865: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.865: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.865: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.866: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.866: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.866: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.866: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.866: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.866: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.866: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.866: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.867: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.867: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.867: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.867: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.867: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.867: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.867: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.867: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.868: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.868: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.868: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.868: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.868: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.868: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.868: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.868: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.869: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.869: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.869: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.869: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.869: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.869: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.869: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.869: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.870: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.870: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.870: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.870: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.870: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.870: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.870: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.870: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.871: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.871: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.871: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.871: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.871: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.871: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.871: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.871: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.872: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.872: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.872: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.872: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.872: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.872: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.872: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.872: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.873: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.873: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.873: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.873: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.873: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.873: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.873: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.873: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.874: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.874: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.874: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.874: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.874: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.874: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.874: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.874: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.875: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.875: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.875: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.875: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.875: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.875: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.875: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.875: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.876: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.876: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.876: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.876: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.876: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.876: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.876: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.876: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.877: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.877: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.877: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.877: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.877: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.877: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.877: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.877: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.878: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.878: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.878: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.878: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.878: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.878: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.878: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.878: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.879: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.879: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.879: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.879: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.879: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.879: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.879: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.879: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.880: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.880: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.880: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.880: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.880: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.880: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.880: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.880: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.881: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.881: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.881: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.881: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.881: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.881: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.881: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.881: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.882: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.882: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.882: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.882: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.882: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.882: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.882: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.882: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.883: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.883: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.883: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.883: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.883: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.883: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.883: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.883: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.884: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.884: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.884: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.884: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.884: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.884: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.884: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.884: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.885: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.885: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.885: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.885: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.885: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.885: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.885: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.885: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.885: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.885: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.885: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.885: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.885: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.885: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.886: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.886: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.886: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.886: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.886: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.886: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.886: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.886: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.887: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.887: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.887: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.887: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.887: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.887: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.887: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.887: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.888: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.888: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.888: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.888: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.888: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.888: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.888: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.888: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.889: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.889: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.889: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.889: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.889: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.889: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.889: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.889: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.890: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.890: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.890: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.890: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.890: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.890: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.890: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.890: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.891: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.891: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.891: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.891: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.891: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.891: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.891: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.891: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.892: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.892: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.892: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.892: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.892: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.892: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.892: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.892: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.893: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.893: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.893: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.893: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.893: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.893: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.893: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.893: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.894: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.894: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.894: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.894: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.894: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.894: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.894: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.894: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.895: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.895: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.895: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.895: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.895: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.895: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.895: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.895: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.896: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.896: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.896: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.896: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.896: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.896: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.896: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.896: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.897: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.897: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.897: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.897: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.897: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.897: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.897: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.897: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.898: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.898: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.898: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.898: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.898: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.898: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.898: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.898: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.899: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.899: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.899: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.899: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.899: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.899: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.899: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.899: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.900: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.900: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.900: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.900: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.900: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.900: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.900: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.900: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.901: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.901: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.901: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.901: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.901: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.901: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.901: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.901: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.902: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.902: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.902: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.902: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.902: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.902: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.902: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.902: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.902: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.902: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.903: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.903: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.903: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.903: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.903: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.903: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.903: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.903: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.904: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.904: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.904: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.904: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.904: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.904: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.904: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.904: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.905: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.905: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.905: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.905: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.905: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.905: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.905: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.905: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.906: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.906: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.906: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.906: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.906: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.906: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.906: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.906: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.907: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.907: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.907: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.907: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.907: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.907: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.907: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.907: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.908: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.908: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.908: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.908: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.908: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.908: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.908: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.908: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.909: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.909: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.909: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.909: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.909: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.909: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.909: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.909: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.910: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.910: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.910: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.910: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.910: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.910: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.910: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.910: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.911: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.911: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.911: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.911: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.911: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.911: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.911: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.911: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.912: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.912: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.912: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.912: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.912: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.912: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.912: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.912: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.913: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.913: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.913: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.913: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.913: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.913: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.913: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.913: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.914: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.914: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.914: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.914: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.914: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.914: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.914: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.914: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.915: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.915: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.915: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.915: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.915: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.915: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.915: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.915: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.916: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.916: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.916: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.916: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.916: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.916: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.916: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.916: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.917: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.917: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.917: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.917: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.917: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.917: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.917: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.917: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.918: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.918: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.918: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.918: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.918: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.918: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.918: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.918: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.919: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.919: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.919: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.919: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.919: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.919: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.919: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.919: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.920: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.920: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.920: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.920: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.920: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.920: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.920: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.920: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.921: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.921: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.921: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.921: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.921: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.921: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.921: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.921: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.922: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.922: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.922: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.922: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.922: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.922: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.922: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.922: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.922: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.922: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.923: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.923: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.923: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.923: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.923: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.923: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.923: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.923: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.923: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.923: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.923: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.923: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.924: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.924: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.924: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.924: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.924: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.924: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.924: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.924: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.925: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.925: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.925: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.925: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.925: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.925: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.925: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.925: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.926: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.926: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.926: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.926: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.926: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.926: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.926: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.926: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.927: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.927: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.927: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.927: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.927: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.927: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.927: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.927: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.928: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.928: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.928: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.928: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.928: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.928: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.928: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.928: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.929: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.929: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.929: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.929: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.929: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.929: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.929: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.929: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.930: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.930: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.930: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.930: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.930: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.930: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.930: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.930: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.931: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.931: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.931: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.931: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.931: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.931: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.931: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.931: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.932: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.932: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.932: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.932: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.932: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.932: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.932: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.932: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.933: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.933: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.933: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.933: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.933: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.933: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.933: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.933: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.934: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.934: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.934: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.934: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.934: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.934: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.934: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.934: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.935: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.935: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.935: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.935: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.935: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.935: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.935: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.935: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.936: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.936: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.936: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.936: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.936: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.936: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.936: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.936: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.937: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.937: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.937: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.937: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.937: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.937: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.937: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.937: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.938: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.938: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.938: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.938: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.938: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.938: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.938: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.938: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.939: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.939: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.939: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.939: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.939: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.939: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.939: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.939: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.940: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.940: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.940: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.940: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.940: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.940: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.940: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.940: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.941: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.941: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.941: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.941: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.941: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.941: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.941: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.941: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.942: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.942: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.942: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.942: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.942: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.942: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.942: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.942: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.943: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.943: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.943: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.943: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.943: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.943: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.943: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.943: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.944: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.944: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.944: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.944: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.944: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.944: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.944: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.944: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.945: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.945: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.945: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.945: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.945: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.945: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.945: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.945: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.946: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.946: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.946: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.946: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.946: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.946: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.946: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.946: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.946: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.946: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.947: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.947: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.947: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.947: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.947: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.947: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.947: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.947: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.948: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.948: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.948: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.948: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.948: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.948: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.948: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.949: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.949: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.949: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.949: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.949: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.949: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.949: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.949: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.949: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.950: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.950: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.950: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.950: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.950: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.950: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.950: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.950: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.951: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.951: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.951: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.951: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.951: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.951: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.951: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.951: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.952: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.952: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.952: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.952: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.952: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.952: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.952: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.952: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.953: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.953: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.953: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.953: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.953: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.953: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.953: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.953: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.954: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.954: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.954: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.954: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.954: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.954: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.954: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.954: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.955: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.955: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.955: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.955: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.955: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.955: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.955: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.955: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.956: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.956: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.956: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.956: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.956: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.956: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.956: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.956: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.957: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.957: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.957: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.957: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.957: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.957: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.957: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.957: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.958: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.958: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.958: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.958: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.958: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.958: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.958: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.958: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.958: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.958: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.958: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.958: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.958: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.958: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.959: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.959: Receiving 64 bytes 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.960: Got 6 bytes out of 64 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.960: [vfs7552] QUERY DATA READY completed successfully 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.960: [vfs7552] CAPTURE_NUM_STATES entering state 1 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.960: [vfs7552] CAPTURE_NUM_STATES entering state 0 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.960: [vfs7552] QUERY DATA READY entering state 0 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.960: Sending vfs7552_is_image_ready 181s (process:2314): libfprint-SSM-DEBUG: 16:48:18.960: [vfs7552] QUERY DATA READY entering state 1 181s (process:2314): libfprint-vfs7552-DEBUG: 16:48:18.960: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.031: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.031: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.031: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.031: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.031: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.031: Sending vfs7552_is_image_ready 182s Executing: libfprint-2/driver-vfs7552.test 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.059: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.059: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.135: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.135: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.135: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.135: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.135: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.135: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.136: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.136: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.137: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.137: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.137: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.137: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.137: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.137: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.137: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.137: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.137: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.138: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.138: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.138: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.138: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.138: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.138: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.138: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.138: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.139: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.139: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.139: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.139: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.139: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.139: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.139: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.140: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.140: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.140: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.140: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.140: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.140: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.140: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.140: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.141: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.141: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.141: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.141: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.141: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.141: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.141: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.141: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.141: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.141: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.141: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.141: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.141: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.141: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.142: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.142: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.142: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.142: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.142: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.142: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.142: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.142: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.143: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.143: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.143: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.143: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.143: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.143: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.143: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.143: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.144: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.144: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.144: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.144: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.144: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.144: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.144: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.144: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.145: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.145: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.145: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.145: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.145: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.145: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.145: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.145: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.146: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.146: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.146: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.146: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.146: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.146: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.146: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.146: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.147: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.147: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.147: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.147: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.147: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.147: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.147: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.147: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.147: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.148: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.148: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.148: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.148: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.148: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.148: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.148: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.148: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.148: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.149: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.149: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.149: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.149: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.149: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.149: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.149: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.149: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.150: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.150: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.150: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.150: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.150: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.150: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.150: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.150: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.151: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.151: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.151: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.151: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.151: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.151: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.151: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.151: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.152: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.152: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.152: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.152: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.152: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.152: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.152: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.152: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.153: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.153: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.153: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.153: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.153: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.153: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.153: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.153: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.154: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.154: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.154: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.154: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.154: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.154: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.154: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.154: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.154: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.155: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.155: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.155: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.155: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.155: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.155: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.155: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.155: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.155: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.155: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.155: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.156: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.156: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.156: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.156: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.156: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.156: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.156: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.156: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.156: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.156: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.157: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.157: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.157: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.157: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.157: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.157: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.157: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.157: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.158: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.158: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.158: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.158: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.158: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.158: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.158: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.158: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.159: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.159: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.159: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.159: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.159: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.159: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.159: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.159: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.160: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.160: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.160: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.160: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.160: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.160: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.160: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.160: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.161: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.161: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.161: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.161: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.161: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.161: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.161: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.161: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.162: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.162: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.162: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.162: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.162: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.162: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.162: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.162: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.163: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.163: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.163: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.163: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.163: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.163: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.163: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.163: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.164: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.164: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.164: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.164: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.164: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.164: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.164: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.164: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.165: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.165: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.165: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.165: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.165: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.165: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.165: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.165: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.166: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.166: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.166: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.166: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.166: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.166: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.166: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.166: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.166: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.167: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.167: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.167: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.167: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.167: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.167: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.167: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.167: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.167: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.168: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.168: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.168: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.168: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.168: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.168: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.168: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.168: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.169: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.169: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.169: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.169: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.169: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.169: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.169: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.169: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.170: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.170: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.170: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.170: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.170: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.170: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.171: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.171: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.171: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.171: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.171: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.171: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.171: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.171: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.172: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.172: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.172: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.172: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.172: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.172: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.172: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.172: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.173: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.173: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.173: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.173: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.173: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.173: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.173: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.173: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.174: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.174: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.174: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.174: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.174: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.174: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.174: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.174: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.175: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.175: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.175: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.175: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.175: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.175: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.175: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.175: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.176: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.176: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.176: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.176: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.176: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.176: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.176: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.176: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.177: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.177: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.177: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.177: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.177: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.177: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.177: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.177: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.178: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.178: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.178: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.178: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.178: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.178: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.178: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.178: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.178: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.178: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.179: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.179: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.179: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.179: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.179: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.179: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.179: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.179: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.180: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.180: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.180: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.180: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.180: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.180: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.180: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.180: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.181: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.181: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.181: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.181: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.181: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.181: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.181: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.181: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.182: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.182: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.182: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.182: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.182: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.182: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.182: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.182: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.183: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.183: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.183: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.183: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.183: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.183: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.183: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.183: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.184: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.184: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.184: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.184: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.184: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.184: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.184: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.184: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.184: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.184: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.184: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.184: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.185: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.185: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.185: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.185: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.185: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.185: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.185: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.185: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.185: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.185: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.186: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.186: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.186: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.186: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.186: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.186: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.186: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.186: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.187: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.187: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.187: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.187: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.187: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.187: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.187: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.187: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.188: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.188: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.188: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.188: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.188: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.188: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.188: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.188: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.189: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.189: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.189: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.189: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.189: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.189: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.189: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.189: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.190: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.190: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.190: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.190: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.190: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.190: [vfs7552] CAPTURE_NUM_STATES entering state 2 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.190: [vfs7552] REQUEST CHUNK entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.190: Sending vfs7552_read_image_chunk 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.191: [vfs7552] REQUEST CHUNK completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.191: [vfs7552] CAPTURE_NUM_STATES entering state 3 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.191: [vfs7552] CAPTURE_NUM_STATES entering state 2 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.191: [vfs7552] REQUEST CHUNK entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.191: Sending vfs7552_read_image_chunk 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.192: [vfs7552] REQUEST CHUNK completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.192: [vfs7552] CAPTURE_NUM_STATES entering state 3 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.192: [vfs7552] CAPTURE_NUM_STATES entering state 2 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.192: [vfs7552] REQUEST CHUNK entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.192: Sending vfs7552_read_image_chunk 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.193: [vfs7552] REQUEST CHUNK completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.193: [vfs7552] CAPTURE_NUM_STATES entering state 3 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.193: [vfs7552] CAPTURE_NUM_STATES entering state 4 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.193: Cleaning image 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.193: variance_after = 20 182s 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.193: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.193: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.193: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.194: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.194: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.194: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.194: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.194: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.194: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.194: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.194: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.195: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.195: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.195: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.195: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.195: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.195: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.195: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.195: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.196: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.196: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.196: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.196: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.196: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.196: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.196: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.196: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.197: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.197: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.197: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.197: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.197: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.197: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.197: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.197: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.198: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.198: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.198: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.198: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.198: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.198: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.198: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.198: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.199: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.199: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.199: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.199: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.199: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.199: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.199: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.199: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.200: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.200: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.200: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.200: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.200: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.200: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.200: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.200: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.201: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.201: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.201: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.201: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.201: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.201: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.201: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.201: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.202: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.202: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.202: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.202: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.202: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.202: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.202: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.202: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.202: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.202: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.203: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.203: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.203: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.203: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.203: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.203: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.203: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.203: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.204: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.204: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.204: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.204: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.204: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.204: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.204: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.204: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.205: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.205: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.205: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.205: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.205: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.205: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.205: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.205: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.206: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.206: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.206: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.206: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.206: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.206: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.206: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.206: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.207: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.207: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.207: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.207: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.207: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.207: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.207: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.207: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.208: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.208: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.208: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.208: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.208: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.208: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.208: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.208: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.209: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.209: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.209: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.209: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.209: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.209: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.209: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.209: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.210: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.210: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.210: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.210: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.210: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.210: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.210: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.210: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.211: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.211: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.211: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.211: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.211: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.211: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.211: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.211: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.211: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.211: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.211: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.211: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.211: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.211: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.212: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.212: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.212: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.212: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.212: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.212: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.212: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.212: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.213: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.213: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.213: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.213: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.213: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.213: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.213: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.213: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.214: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.214: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.214: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.214: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.214: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.214: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.214: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.214: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.215: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.215: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.215: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.215: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.215: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.215: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.215: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.215: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.216: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.216: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.216: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.216: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.216: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.216: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.216: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.216: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.217: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.217: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.217: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.217: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.217: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.217: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.217: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.217: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.218: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.218: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.218: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.218: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.218: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.218: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.218: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.218: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.219: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.219: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.219: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.219: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.219: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.219: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.219: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.219: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.220: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.220: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.220: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.220: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.220: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.220: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.220: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.220: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.221: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.221: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.221: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.221: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.221: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.221: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.221: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.221: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.222: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.222: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.222: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.222: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.222: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.222: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.222: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.222: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.222: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.223: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.223: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.223: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.223: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.223: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.223: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.223: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.223: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.223: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.224: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.224: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.224: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.224: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.224: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.224: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.224: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.224: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.225: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.225: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.225: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.225: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.225: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.225: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.225: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.225: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.226: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.226: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.226: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.226: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.226: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.226: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.226: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.226: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.227: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.227: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.227: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.227: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.227: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.227: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.227: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.227: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.228: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.228: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.228: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.228: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.228: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.228: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.228: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.228: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.229: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.229: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.229: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.229: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.229: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.229: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.229: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.229: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.230: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.230: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.230: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.230: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.230: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.230: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.230: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.230: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.231: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.231: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.231: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.231: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.231: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.231: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.231: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.231: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.232: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.232: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.232: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.232: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.232: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.232: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.232: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.232: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.233: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.233: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.233: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.233: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.233: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.233: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.233: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.233: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.234: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.234: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.234: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.234: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.234: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.234: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.234: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.234: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.235: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.235: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.235: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.235: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.235: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.235: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.235: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.235: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.236: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.236: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.236: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.236: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.236: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.236: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.236: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.236: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.237: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.237: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.237: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.237: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.237: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.237: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.237: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.237: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.237: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.237: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.238: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.238: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.238: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.238: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.238: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.238: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.238: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.238: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.239: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.239: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.239: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.239: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.239: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.239: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.239: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.239: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.239: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.239: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.239: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.239: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.240: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.240: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.240: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.240: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.240: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.240: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.240: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.240: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.241: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.241: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.241: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.241: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.241: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.241: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.241: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.241: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.242: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.242: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.242: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.242: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.242: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.242: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.242: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.242: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.243: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.243: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.243: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.243: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.243: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.243: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.243: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.243: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.244: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.244: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.244: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.244: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.244: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.244: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.244: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.244: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.245: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.245: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.245: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.245: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.245: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.245: [vfs7552] CAPTURE_NUM_STATES entering state 2 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.245: [vfs7552] REQUEST CHUNK entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.245: Sending vfs7552_read_image_chunk 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.246: [vfs7552] REQUEST CHUNK completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.246: [vfs7552] CAPTURE_NUM_STATES entering state 3 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.246: [vfs7552] CAPTURE_NUM_STATES entering state 2 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.246: [vfs7552] REQUEST CHUNK entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.246: Sending vfs7552_read_image_chunk 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.247: [vfs7552] REQUEST CHUNK completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.247: [vfs7552] CAPTURE_NUM_STATES entering state 3 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.247: [vfs7552] CAPTURE_NUM_STATES entering state 2 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.247: [vfs7552] REQUEST CHUNK entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.247: Sending vfs7552_read_image_chunk 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.248: [vfs7552] REQUEST CHUNK completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.248: [vfs7552] CAPTURE_NUM_STATES entering state 3 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.248: [vfs7552] CAPTURE_NUM_STATES entering state 4 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.248: Cleaning image 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.248: variance_after = 18 182s 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.248: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.248: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.248: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.249: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.249: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.249: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.249: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.249: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.249: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.249: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.249: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.250: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.250: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.250: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.250: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.250: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.250: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.250: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.250: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.251: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.251: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.251: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.251: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.251: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.251: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.251: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.251: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.252: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.252: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.252: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.252: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.252: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.252: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.252: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.252: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.252: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.253: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.253: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.253: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.253: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.253: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.253: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.253: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.253: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.253: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.254: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.254: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.254: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.254: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.254: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.254: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.254: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.254: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.255: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.255: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.255: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.255: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.255: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.255: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.255: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.255: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.256: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.256: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.256: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.256: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.256: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.256: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.256: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.256: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.257: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.257: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.257: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.257: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.257: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.257: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.257: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.257: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.258: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.258: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.258: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.258: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.258: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.258: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.258: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.258: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.259: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.259: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.259: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.259: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.259: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.259: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.259: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.259: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.260: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.260: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.260: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.260: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.260: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.260: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.260: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.260: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.261: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.261: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.261: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.261: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.261: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.261: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.261: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.261: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.262: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.262: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.262: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.262: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.262: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.262: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.262: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.262: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.263: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.263: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.263: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.263: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.263: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.263: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.263: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.263: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.264: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.264: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.264: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.264: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.264: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.264: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.264: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.264: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.265: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.265: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.265: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.265: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.265: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.265: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.265: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.265: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.266: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.266: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.266: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.266: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.266: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.266: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.266: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.266: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.267: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.267: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.267: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.267: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.267: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.267: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.267: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.267: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.267: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.267: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.268: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.268: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.268: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.268: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.268: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.268: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.268: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.268: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.268: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.268: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.268: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.268: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.269: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.269: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.269: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.269: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.269: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.269: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.269: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.269: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.270: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.270: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.270: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.270: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.270: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.270: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.270: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.270: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.271: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.271: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.271: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.271: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.271: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.271: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.271: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.271: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.272: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.272: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.272: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.272: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.272: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.272: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.272: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.272: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.273: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.273: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.273: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.273: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.273: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.273: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.273: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.273: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.274: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.274: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.274: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.274: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.274: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.274: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.274: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.274: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.275: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.275: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.275: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.275: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.275: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.275: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.275: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.275: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.276: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.276: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.276: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.276: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.276: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.276: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.276: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.276: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.277: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.277: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.277: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.277: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.277: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.277: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.277: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.277: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.278: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.278: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.278: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.278: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.278: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.278: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.278: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.278: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.279: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.279: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.279: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.279: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.279: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.279: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.279: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.279: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.280: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.280: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.280: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.280: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.280: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.280: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.280: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.280: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.281: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.281: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.281: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.281: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.281: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.281: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.281: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.281: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.282: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.282: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.282: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.282: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.282: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.282: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.282: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.282: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.283: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.283: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.283: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.283: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.283: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.283: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.283: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.283: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.284: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.284: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.284: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.284: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.284: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.284: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.284: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.284: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.285: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.285: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.285: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.285: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.285: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.285: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.285: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.285: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.286: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.286: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.286: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.286: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.286: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.286: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.286: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.286: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.286: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.287: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.287: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.287: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.287: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.287: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.287: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.287: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.287: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.287: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.288: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.288: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.288: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.288: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.288: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.288: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.288: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.288: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.289: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.289: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.289: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.289: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.289: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.289: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.289: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.289: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.290: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.290: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.290: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.290: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.290: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.290: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.290: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.290: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.291: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.291: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.291: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.291: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.291: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.291: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.291: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.291: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.292: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.292: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.292: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.292: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.292: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.292: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.292: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.292: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.293: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.293: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.293: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.293: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.293: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.293: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.293: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.293: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.294: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.294: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.294: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.294: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.294: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.294: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.294: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.294: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.295: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.295: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.295: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.295: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.295: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.295: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.295: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.295: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.296: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.296: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.296: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.296: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.296: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.296: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.296: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.296: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.297: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.297: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.297: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.297: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.297: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.297: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.297: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.297: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.297: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.297: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.298: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.298: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.298: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.298: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.298: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.298: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.298: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.299: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.299: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.299: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.299: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.299: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.299: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.299: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.299: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.299: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.299: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.300: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.300: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.300: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.300: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.300: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.300: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.300: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.300: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.300: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.300: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.300: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.301: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.301: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.301: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.301: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.301: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.301: [vfs7552] CAPTURE_NUM_STATES entering state 2 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.301: [vfs7552] REQUEST CHUNK entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.301: Sending vfs7552_read_image_chunk 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.302: [vfs7552] REQUEST CHUNK completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.302: [vfs7552] CAPTURE_NUM_STATES entering state 3 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.302: [vfs7552] CAPTURE_NUM_STATES entering state 2 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.302: [vfs7552] REQUEST CHUNK entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.302: Sending vfs7552_read_image_chunk 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.303: [vfs7552] REQUEST CHUNK completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.303: [vfs7552] CAPTURE_NUM_STATES entering state 3 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.303: [vfs7552] CAPTURE_NUM_STATES entering state 2 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.303: [vfs7552] REQUEST CHUNK entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.303: Sending vfs7552_read_image_chunk 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.304: [vfs7552] REQUEST CHUNK completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.304: [vfs7552] CAPTURE_NUM_STATES entering state 3 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.304: [vfs7552] CAPTURE_NUM_STATES entering state 4 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.304: Cleaning image 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.304: variance_after = 18 182s 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.304: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.304: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.304: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.305: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.305: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.305: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.305: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.305: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.305: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.305: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.305: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.306: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.306: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.306: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.306: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.306: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.306: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.306: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.306: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.307: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.307: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.307: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.307: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.307: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.307: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.307: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.307: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.308: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.308: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.308: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.308: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.308: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.308: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.308: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.308: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.309: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.309: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.309: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.309: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.309: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.309: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.309: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.309: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.310: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.310: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.310: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.310: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.310: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.310: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.310: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.310: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.310: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.311: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.311: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.311: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.311: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.311: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.311: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.311: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.311: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.311: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.312: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.312: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.312: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.312: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.312: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.312: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.312: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.312: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.313: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.313: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.313: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.313: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.313: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.313: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.313: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.313: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.314: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.314: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.314: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.314: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.314: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.314: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.314: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.314: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.315: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.315: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.315: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.315: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.315: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.315: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.315: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.315: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.316: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.316: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.316: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.316: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.316: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.316: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.316: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.316: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.317: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.317: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.317: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.317: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.317: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.317: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.317: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.317: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.317: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.318: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.318: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.318: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.318: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.318: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.318: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.318: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.318: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.318: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.318: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.318: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.318: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.318: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.319: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.319: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.319: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.319: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.319: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.319: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.319: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.319: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.320: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.320: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.320: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.320: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.320: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.320: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.320: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.320: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.321: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.321: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.321: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.321: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.321: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.322: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.322: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.322: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.322: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.322: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.322: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.322: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.322: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.322: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.322: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.322: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.323: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.323: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.323: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.323: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.323: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.323: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.323: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.323: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.324: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.324: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.324: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.324: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.324: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.324: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.324: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.324: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.325: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.325: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.325: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.325: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.325: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.325: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.325: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.325: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.326: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.326: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.326: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.326: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.326: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.326: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.326: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.326: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.327: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.327: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.327: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.327: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.327: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.327: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.327: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.327: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.328: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.328: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.328: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.328: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.328: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.328: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.328: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.328: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.329: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.329: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.329: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.329: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.329: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.329: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.329: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.329: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.330: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.330: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.330: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.330: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.330: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.330: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.330: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.330: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.331: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.331: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.331: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.331: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.331: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.331: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.331: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.331: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.332: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.332: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.332: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.332: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.332: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.332: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.332: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.332: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.333: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.333: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.333: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.333: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.333: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.333: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.333: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.333: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.334: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.334: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.334: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.334: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.334: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.334: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.334: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.334: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.335: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.335: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.335: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.335: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.335: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.335: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.335: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.335: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.336: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.336: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.336: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.336: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.336: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.336: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.336: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.336: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.337: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.337: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.337: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.337: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.337: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.337: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.337: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.337: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.338: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.338: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.338: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.338: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.338: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.338: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.338: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.338: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.339: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.339: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.339: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.339: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.339: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.339: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.339: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.339: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.340: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.340: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.340: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.340: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.340: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.340: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.340: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.340: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.341: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.341: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.341: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.341: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.341: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.341: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.341: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.341: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.342: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.342: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.342: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.342: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.342: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.342: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.342: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.342: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.343: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.343: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.343: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.343: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.343: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.343: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.343: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.343: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.344: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.344: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.344: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.344: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.344: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.344: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.344: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.344: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.345: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.345: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.345: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.345: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.345: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.345: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.345: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.345: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.346: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.346: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.346: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.346: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.346: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.346: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.346: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.346: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.347: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.347: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.347: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.347: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.347: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.347: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.347: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.347: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.348: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.348: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.348: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.348: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.348: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.348: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.348: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.348: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.349: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.349: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.349: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.349: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.349: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.349: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.349: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.349: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.350: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.350: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.350: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.350: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.350: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.350: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.350: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.350: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.350: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.350: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.351: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.351: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.351: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.351: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.351: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.351: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.351: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.351: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.352: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.352: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.352: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.352: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.352: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.352: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.352: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.352: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.353: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.353: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.353: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.353: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.353: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.353: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.353: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.353: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.354: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.354: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.354: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.354: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.354: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.354: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.354: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.354: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.355: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.355: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.355: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.355: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.355: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.355: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.355: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.355: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.356: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.356: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.356: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.356: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.356: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.356: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.356: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.356: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.357: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.357: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.357: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.357: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.357: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.357: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.357: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.357: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.358: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.358: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.358: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.358: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.358: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.358: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.358: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.358: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.358: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.358: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.358: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.359: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.359: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.359: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.359: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.359: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.359: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.360: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.360: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.360: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.360: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.360: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.360: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.360: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.361: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.361: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.361: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.361: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.361: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.361: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.361: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.361: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.362: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.362: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.362: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.362: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.362: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.362: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.362: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.362: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.362: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.362: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.362: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.362: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.362: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.362: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.363: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.363: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.363: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.363: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.363: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.363: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.363: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.363: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.364: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.364: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.364: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.364: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.364: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.364: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.364: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.364: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.365: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.365: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.365: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.365: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.365: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.365: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.365: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.365: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.366: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.366: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.366: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.366: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.366: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.366: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.366: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.366: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.367: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.367: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.367: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.367: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.367: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.367: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.367: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.367: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.368: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.368: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.368: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.368: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.368: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.368: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.368: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.368: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.369: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.369: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.369: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.369: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.369: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.369: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.369: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.369: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.370: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.370: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.370: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.370: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.370: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.370: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.370: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.370: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.371: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.371: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.371: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.371: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.371: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.371: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.371: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.371: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.372: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.372: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.372: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.372: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.372: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.372: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.372: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.372: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.373: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.373: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.373: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.373: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.373: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.373: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.373: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.373: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.374: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.374: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.374: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.374: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.374: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.374: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.374: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.374: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.375: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.375: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.375: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.375: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.375: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.375: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.375: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.375: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.376: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.376: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.376: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.376: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.376: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.376: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.376: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.376: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.376: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.377: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.377: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.377: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.377: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.377: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.377: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.377: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.377: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.377: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.378: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.378: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.378: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.378: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.378: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.378: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.378: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.378: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.379: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.379: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.379: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.379: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.379: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.379: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.379: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.379: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.380: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.380: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.380: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.380: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.380: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.380: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.380: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.380: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.381: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.381: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.381: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.381: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.381: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.381: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.381: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.381: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.382: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.382: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.382: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.382: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.382: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.382: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.382: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.382: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.383: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.383: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.383: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.383: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.383: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.383: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.383: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.383: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.384: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.384: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.384: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.384: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.384: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.384: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.384: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.384: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.385: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.385: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.385: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.385: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.385: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.385: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.385: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.385: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.386: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.386: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.386: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.386: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.386: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.386: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.386: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.386: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.386: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.386: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.387: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.387: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.387: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.387: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.387: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.387: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.387: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.388: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.388: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.388: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.388: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.388: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.388: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.388: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.388: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.388: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.389: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.389: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.389: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.389: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.389: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.389: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.401: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.401: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.401: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.401: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.401: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.401: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.402: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.402: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.402: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.402: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.402: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.402: [vfs7552] CAPTURE_NUM_STATES entering state 2 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.402: [vfs7552] REQUEST CHUNK entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.402: Sending vfs7552_read_image_chunk 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.403: [vfs7552] REQUEST CHUNK completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.403: [vfs7552] CAPTURE_NUM_STATES entering state 3 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.403: [vfs7552] CAPTURE_NUM_STATES entering state 2 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.403: [vfs7552] REQUEST CHUNK entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.403: Sending vfs7552_read_image_chunk 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.404: [vfs7552] REQUEST CHUNK completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.404: [vfs7552] CAPTURE_NUM_STATES entering state 3 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.404: [vfs7552] CAPTURE_NUM_STATES entering state 2 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.404: [vfs7552] REQUEST CHUNK entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.404: Sending vfs7552_read_image_chunk 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.405: [vfs7552] REQUEST CHUNK completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.405: [vfs7552] CAPTURE_NUM_STATES entering state 3 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.405: [vfs7552] CAPTURE_NUM_STATES entering state 4 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.405: Cleaning image 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.405: variance_after = 18 182s 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.405: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.405: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.405: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.406: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.406: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.406: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.406: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.406: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.406: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.406: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.406: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.407: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.407: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.407: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.407: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.407: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.407: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.407: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.407: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.407: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.407: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.408: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.408: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.408: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.408: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.408: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.408: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.408: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.409: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.409: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.409: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.409: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.409: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.409: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.409: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.410: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.410: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.410: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.410: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.410: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.410: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.410: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.410: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.410: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.410: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.411: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.411: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.411: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.411: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.411: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.411: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.411: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.411: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.412: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.412: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.412: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.412: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.412: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.412: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.412: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.412: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.413: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.413: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.413: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.413: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.413: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.413: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.413: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.413: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.414: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.414: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.414: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.414: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.414: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.414: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.414: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.414: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.415: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.415: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.415: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.415: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.415: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.415: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.415: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.415: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.416: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.416: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.416: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.416: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.416: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.416: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.416: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.416: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.417: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.417: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.417: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.417: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.417: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.417: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.417: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.417: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.418: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.418: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.418: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.418: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.418: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.418: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.418: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.418: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.419: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.419: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.419: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.419: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.419: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.419: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.419: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.419: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.420: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.420: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.420: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.420: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.420: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.420: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.421: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.421: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.421: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.421: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.421: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.421: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.421: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.421: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.422: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.422: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.422: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.422: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.422: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.422: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.422: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.422: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.423: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.423: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.424: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.424: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.424: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.424: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.424: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.424: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.424: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.424: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.425: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.425: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.425: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.425: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.425: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.425: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.425: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.425: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.426: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.426: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.426: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.426: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.426: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.426: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.427: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.427: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.427: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.427: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.427: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.427: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.427: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.427: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.428: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.428: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.428: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.428: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.428: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.428: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.428: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.428: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.429: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.429: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.430: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.430: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.430: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.430: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.430: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.430: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.430: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.430: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.431: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.431: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.431: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.431: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.431: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.431: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.431: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.431: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.432: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.432: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.432: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.432: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.432: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.432: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.432: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.432: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.433: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.433: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.433: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.433: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.433: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.433: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.434: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.434: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.434: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.434: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.434: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.434: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.434: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.434: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.435: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.435: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.435: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.435: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.435: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.435: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.435: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.435: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.436: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.436: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.436: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.436: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.436: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.436: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.436: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.436: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.437: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.437: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.438: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.438: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.438: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.438: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.438: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.438: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.439: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.439: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.439: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.439: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.439: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.439: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.439: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.439: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.440: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.440: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.440: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.440: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.440: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.440: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.440: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.440: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.441: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.441: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.442: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.442: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.442: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.442: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.442: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.442: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.442: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.442: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.443: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.443: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.443: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.443: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.443: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.443: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.443: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.443: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.444: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.444: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.444: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.444: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.444: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.444: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.445: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.445: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.445: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.445: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.445: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.445: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.445: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.445: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.446: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.446: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.446: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.446: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.446: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.446: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.446: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.446: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.447: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.447: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.448: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.448: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.448: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.448: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.448: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.448: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.448: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.448: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.449: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.449: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.449: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.449: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.449: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.449: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.449: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.449: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.450: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.450: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.450: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.450: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.450: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.450: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.451: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.451: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.451: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.451: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.451: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.451: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.451: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.451: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.452: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.452: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.452: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.452: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.452: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.452: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.452: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.452: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.453: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.453: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.453: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.453: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.453: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.453: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.453: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.453: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.454: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.454: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.454: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.454: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.455: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.455: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.455: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.455: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.455: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.455: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.456: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.456: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.456: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.456: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.456: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.456: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.456: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.456: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.457: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.457: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.457: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.457: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.457: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.457: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.457: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.457: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.458: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.458: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.458: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.458: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.458: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.458: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.458: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.458: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.459: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.459: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.459: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.459: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.459: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.459: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.459: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.459: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.460: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.460: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.460: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.460: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.460: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.460: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.461: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.461: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.461: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.461: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.461: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.461: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.461: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.461: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.462: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.462: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.462: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.462: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.462: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.462: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.462: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.462: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.463: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.463: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.463: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.463: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.463: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.463: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.463: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.463: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.464: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.464: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.464: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.464: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.464: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.464: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.464: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.464: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.465: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.465: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.465: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.465: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.465: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.465: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.465: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.465: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.466: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.466: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.466: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.466: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.466: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.466: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.466: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.466: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.467: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.467: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.467: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.467: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.467: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.467: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.467: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.467: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.468: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.468: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.468: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.468: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.468: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.468: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.468: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.468: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.468: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.468: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.469: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.469: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.469: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.469: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.469: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.469: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.469: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.469: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.470: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.470: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.470: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.470: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.470: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.470: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.470: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.470: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.471: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.471: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.471: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.471: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.471: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.471: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.471: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.471: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.472: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.472: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.472: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.472: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.472: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.472: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.472: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.472: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.473: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.473: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.473: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.473: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.473: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.473: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.473: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.473: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.474: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.474: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.474: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.474: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.474: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.474: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.474: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.474: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.475: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.475: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.475: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.475: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.475: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.475: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.475: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.475: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.476: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.476: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.476: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.476: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.476: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.476: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.476: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.476: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.477: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.477: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.477: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.477: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.477: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.477: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.477: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.477: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.477: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.478: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.478: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.478: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.478: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.478: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.478: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.478: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.478: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.479: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.479: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.479: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.479: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.479: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.479: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.479: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.479: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.479: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.479: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.479: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.479: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.479: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.480: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.480: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.480: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.480: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.480: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.480: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.480: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.480: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.481: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.481: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.481: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.481: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.481: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.481: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.481: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.481: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.482: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.482: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.482: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.482: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.482: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.482: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.482: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.482: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.483: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.483: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.483: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.483: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.483: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.483: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.483: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.483: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.484: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.484: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.484: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.484: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.484: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.484: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.484: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.484: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.485: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.485: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.485: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.485: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.485: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.485: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.485: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.485: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.486: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.486: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.486: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.486: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.486: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.486: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.486: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.486: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.486: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.486: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.487: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.487: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.487: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.487: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.487: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.487: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.487: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.488: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.488: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.488: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.488: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.488: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.488: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.488: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.488: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.488: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.489: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.489: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.489: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.489: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.489: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.489: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.489: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.489: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.490: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.490: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.490: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.490: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.490: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.490: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.490: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.490: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.491: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.491: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.491: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.491: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.491: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.491: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.491: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.491: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.492: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.492: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.492: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.492: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.492: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.492: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.492: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.492: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.493: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.493: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.493: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.493: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.493: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.493: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.493: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.493: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.494: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.494: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.494: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.494: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.494: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.494: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.494: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.494: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.495: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.495: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.495: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.495: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.495: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.495: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.495: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.495: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.496: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.496: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.496: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.496: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.496: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.496: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.496: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.496: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.496: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.496: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.496: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.497: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.497: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.497: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.497: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.497: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.497: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.498: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.498: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.498: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.498: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.498: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.498: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.498: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.498: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.498: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.499: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.499: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.499: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.499: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.499: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.499: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.499: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.499: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.499: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.499: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.499: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.499: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.500: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.500: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.500: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.500: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.500: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.500: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.500: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.500: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.501: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.501: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.501: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.501: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.501: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.501: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.501: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.501: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.502: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.502: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.502: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.502: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.502: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.502: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.502: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.502: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.503: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.503: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.503: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.503: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.503: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.503: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.503: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.503: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.504: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.504: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.504: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.504: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.504: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.504: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.504: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.504: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.505: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.505: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.505: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.505: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.505: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.505: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.505: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.505: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.506: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.506: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.506: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.506: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.506: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.506: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.506: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.506: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.507: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.507: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.507: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.507: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.507: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.507: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.507: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.507: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.508: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.508: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.508: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.508: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.508: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.508: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.508: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.508: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.509: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.509: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.509: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.509: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.509: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.509: [vfs7552] CAPTURE_NUM_STATES entering state 2 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.509: [vfs7552] REQUEST CHUNK entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.509: Sending vfs7552_read_image_chunk 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.510: [vfs7552] REQUEST CHUNK completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.510: [vfs7552] CAPTURE_NUM_STATES entering state 3 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.510: [vfs7552] CAPTURE_NUM_STATES entering state 2 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.510: [vfs7552] REQUEST CHUNK entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.510: Sending vfs7552_read_image_chunk 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.510: [vfs7552] REQUEST CHUNK completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.511: [vfs7552] CAPTURE_NUM_STATES entering state 3 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.511: [vfs7552] CAPTURE_NUM_STATES entering state 2 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.511: [vfs7552] REQUEST CHUNK entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.511: Sending vfs7552_read_image_chunk 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.511: [vfs7552] REQUEST CHUNK completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.512: [vfs7552] CAPTURE_NUM_STATES entering state 3 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.512: [vfs7552] CAPTURE_NUM_STATES entering state 4 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.512: Cleaning image 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.512: variance_after = 18 182s 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.512: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.512: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.512: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.512: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.512: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.513: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.513: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.513: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.513: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.513: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.513: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.513: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.514: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.514: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.514: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.514: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.514: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.514: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.514: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.514: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.514: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.515: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.515: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.515: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.515: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.515: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.515: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.515: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.515: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.516: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.516: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.516: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.516: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.516: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.516: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.516: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.516: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.517: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.517: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.517: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.517: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.517: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.517: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.517: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.517: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.518: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.518: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.518: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.518: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.518: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.518: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.518: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.518: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.519: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.519: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.519: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.519: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.519: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.519: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.519: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.519: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.520: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.520: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.520: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.520: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.520: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.520: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.520: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.520: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.521: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.521: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.521: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.521: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.521: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.521: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.521: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.521: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.521: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.521: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.521: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.521: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.521: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.521: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.522: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.522: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.522: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.522: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.522: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.522: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.522: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.522: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.523: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.523: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.523: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.523: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.523: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.523: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.523: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.523: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.524: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.524: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.524: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.524: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.524: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.524: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.524: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.524: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.525: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.525: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.525: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.525: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.525: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.525: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.525: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.525: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.526: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.526: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.526: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.526: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.526: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.526: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.526: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.526: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.526: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.527: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.527: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.527: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.527: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.527: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.527: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.527: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.527: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.527: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.528: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.528: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.528: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.528: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.528: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.528: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.528: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.528: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.529: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.529: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.529: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.529: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.529: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.529: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.529: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.529: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.530: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.530: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.530: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.530: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.530: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.530: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.530: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.530: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.531: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.531: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.531: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.531: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.531: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.531: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.531: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.531: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.531: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.531: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.532: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.532: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.532: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.532: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.532: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.532: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.532: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.532: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.532: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.533: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.533: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.533: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.533: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.533: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.533: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.533: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.533: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.533: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.533: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.533: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.534: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.534: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.534: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.534: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.534: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.534: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.534: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.534: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.535: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.535: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.535: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.535: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.535: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.535: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.535: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.535: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.536: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.536: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.536: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.536: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.536: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.536: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.536: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.536: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.537: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.537: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.537: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.537: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.537: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.537: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.537: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.537: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.538: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.538: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.538: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.538: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.538: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.538: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.538: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.538: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.539: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.539: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.539: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.539: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.539: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.539: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.539: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.539: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.539: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.540: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.540: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.540: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.540: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.540: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.540: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.540: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.540: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.540: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.541: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.541: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.541: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.541: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.541: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.541: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.541: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.541: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.542: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.542: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.542: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.542: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.542: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.542: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.542: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.542: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.543: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.543: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.543: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.543: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.543: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.543: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.543: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.543: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.544: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.544: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.544: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.544: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.544: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.544: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.544: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.544: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.545: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.545: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.545: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.545: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.545: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.545: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.545: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.545: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.546: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.546: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.546: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.546: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.546: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.546: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.546: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.546: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.547: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.547: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.547: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.547: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.547: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.547: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.547: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.547: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.548: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.548: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.548: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.548: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.548: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.548: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.548: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.548: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.549: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.549: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.549: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.549: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.549: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.549: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.549: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.549: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.550: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.550: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.550: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.550: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.550: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.550: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.550: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.550: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.550: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.551: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.551: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.551: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.551: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.551: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.551: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.551: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.552: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.552: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.552: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.552: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.552: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.552: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.552: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.552: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.552: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.553: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.553: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.553: [vfs7552] CAPTURE_NUM_STATES entering state 2 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.553: [vfs7552] REQUEST CHUNK entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.553: Sending vfs7552_read_image_chunk 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.553: [vfs7552] REQUEST CHUNK completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.553: [vfs7552] CAPTURE_NUM_STATES entering state 3 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.554: [vfs7552] CAPTURE_NUM_STATES entering state 2 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.554: [vfs7552] REQUEST CHUNK entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.554: Sending vfs7552_read_image_chunk 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.554: [vfs7552] REQUEST CHUNK completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.554: [vfs7552] CAPTURE_NUM_STATES entering state 3 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.555: [vfs7552] CAPTURE_NUM_STATES entering state 2 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.555: [vfs7552] REQUEST CHUNK entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.555: Sending vfs7552_read_image_chunk 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.555: [vfs7552] REQUEST CHUNK completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.555: [vfs7552] CAPTURE_NUM_STATES entering state 3 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.556: [vfs7552] CAPTURE_NUM_STATES entering state 4 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.556: Cleaning image 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.556: variance_after = 17 182s 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.556: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.556: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.556: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.556: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.556: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.557: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.557: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.557: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.557: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.557: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.557: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.557: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.557: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.558: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.558: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.558: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.558: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.558: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.558: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.558: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.558: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.559: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.559: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.559: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.559: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.559: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.559: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.559: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.559: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.559: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.560: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.560: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.560: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.560: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.560: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.560: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.560: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.560: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.561: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.561: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.561: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.561: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.561: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.561: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.561: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.561: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.561: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.561: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.561: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.561: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.561: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.562: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.562: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.562: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.562: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.562: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.562: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.562: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.562: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.563: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.563: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.563: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.563: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.563: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.563: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.563: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.563: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.564: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.564: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.564: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.564: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.564: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.564: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.564: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.564: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.565: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.565: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.565: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.565: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.565: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.565: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.565: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.565: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.566: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.566: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.566: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.566: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.566: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.566: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.566: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.566: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.567: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.567: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.567: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.567: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.567: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.567: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.567: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.567: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.568: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.568: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.568: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.568: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.568: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.568: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.568: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.568: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.569: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.569: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.569: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.569: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.569: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.569: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.569: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.569: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.569: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.570: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.570: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.570: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.570: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.570: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.570: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.570: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.570: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.570: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.571: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.571: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.571: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.571: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.571: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.571: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.571: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.571: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.572: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.572: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.572: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.572: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.572: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.572: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.572: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.572: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.573: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.573: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.573: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.573: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.573: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.573: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.573: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.573: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.574: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.574: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.574: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.574: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.574: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.574: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.574: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.574: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.575: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.575: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.575: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.575: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.575: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.575: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.575: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.575: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.576: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.576: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.576: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.576: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.576: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.576: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.576: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.576: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.577: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.577: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.577: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.577: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.577: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.577: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.577: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.577: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.578: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.578: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.578: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.578: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.578: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.578: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.578: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.578: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.579: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.579: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.579: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.579: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.579: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.579: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.579: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.579: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.580: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.580: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.580: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.580: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.580: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.580: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.580: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.580: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.581: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.581: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.581: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.581: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.581: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.581: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.581: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.581: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.581: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.581: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.581: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.582: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.582: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.582: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.582: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.582: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.582: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.582: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.583: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.583: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.583: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.583: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.583: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.583: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.583: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.583: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.583: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.583: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.583: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.583: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.584: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.584: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.584: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.585: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.585: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.585: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.585: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.585: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.585: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.585: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.585: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.585: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.585: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.585: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.585: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.585: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.586: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.586: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.586: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.586: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.586: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.586: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.586: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.586: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.587: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.587: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.587: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.587: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.587: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.587: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.587: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.587: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.588: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.588: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.588: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.588: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.588: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.588: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.588: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.588: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.589: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.589: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.589: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.589: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.589: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.589: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.589: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.589: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.590: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.590: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.590: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.590: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.590: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.590: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.590: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.590: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.591: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.591: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.591: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.591: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.591: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.591: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.591: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.591: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.592: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.592: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.592: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.592: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.592: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.592: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.592: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.592: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.592: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.592: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.593: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.593: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.593: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.593: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.593: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.593: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.593: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.593: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.594: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.594: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.594: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.594: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.594: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.594: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.594: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.594: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.595: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.595: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.595: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.595: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.595: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.595: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.595: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.595: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.596: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.596: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.596: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.596: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.596: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.596: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.597: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.597: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.597: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.597: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.597: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.597: [vfs7552] CAPTURE_NUM_STATES entering state 2 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.597: [vfs7552] REQUEST CHUNK entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.597: Sending vfs7552_read_image_chunk 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.598: [vfs7552] REQUEST CHUNK completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.598: [vfs7552] CAPTURE_NUM_STATES entering state 3 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.598: [vfs7552] CAPTURE_NUM_STATES entering state 2 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.598: [vfs7552] REQUEST CHUNK entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.598: Sending vfs7552_read_image_chunk 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.598: [vfs7552] REQUEST CHUNK completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.599: [vfs7552] CAPTURE_NUM_STATES entering state 3 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.599: [vfs7552] CAPTURE_NUM_STATES entering state 2 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.599: [vfs7552] REQUEST CHUNK entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.599: Sending vfs7552_read_image_chunk 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.599: [vfs7552] REQUEST CHUNK completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.600: [vfs7552] CAPTURE_NUM_STATES entering state 3 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.600: [vfs7552] CAPTURE_NUM_STATES entering state 4 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.600: Cleaning image 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.600: variance_after = 16 182s 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.600: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.600: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.600: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.601: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.601: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.601: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.601: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.601: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.601: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.601: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.602: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.602: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.602: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.602: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.602: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.602: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.602: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.602: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.602: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.603: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.603: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.603: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.603: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.603: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.603: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.603: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.603: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.604: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.604: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.604: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.604: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.604: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.604: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.604: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.604: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.605: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.605: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.605: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.605: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.605: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.605: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.605: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.605: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.606: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.606: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.606: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.606: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.606: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.606: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.606: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.606: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.607: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.607: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.607: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.607: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.607: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.607: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.607: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.607: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.608: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.608: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.608: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.608: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.608: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.608: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.608: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.608: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.609: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.609: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.609: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.609: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.609: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.609: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.609: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.609: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.610: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.610: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.610: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.610: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.610: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.610: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.610: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.610: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.610: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.610: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.611: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.611: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.611: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.611: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.611: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.611: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.611: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.611: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.612: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.612: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.612: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.612: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.612: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.612: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.612: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.612: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.613: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.613: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.613: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.613: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.613: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.613: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.613: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.613: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.614: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.614: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.614: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.614: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.614: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.614: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.614: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.614: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.615: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.615: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.615: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.615: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.615: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.615: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.615: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.615: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.615: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.616: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.616: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.616: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.616: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.616: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.616: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.616: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.616: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.616: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.616: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.616: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.616: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.616: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.617: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.617: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.617: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.617: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.617: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.617: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.617: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.617: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.618: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.618: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.618: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.618: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.618: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.618: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.618: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.618: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.619: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.619: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.619: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.619: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.619: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.619: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.619: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.619: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.620: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.620: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.620: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.620: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.620: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.620: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.620: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.620: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.621: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.621: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.621: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.621: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.621: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.621: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.621: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.621: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.622: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.622: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.622: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.622: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.622: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.622: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.622: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.622: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.622: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.622: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.623: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.623: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.623: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.623: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.623: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.623: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.623: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.623: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.624: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.624: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.624: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.624: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.624: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.624: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.624: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.624: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.625: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.625: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.625: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.625: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.625: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.625: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.625: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.625: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.626: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.626: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.626: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.626: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.626: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.626: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.626: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.626: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.627: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.627: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.627: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.627: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.627: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.627: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.627: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.627: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.628: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.628: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.628: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.628: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.628: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.628: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.628: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.628: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.629: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.629: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.629: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.629: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.629: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.629: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.629: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.629: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.630: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.630: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.630: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.630: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.630: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.630: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.630: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.630: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.631: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.631: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.631: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.631: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.631: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.631: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.631: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.631: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.632: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.632: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.632: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.632: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.632: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.632: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.632: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.632: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.633: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.633: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.633: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.633: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.633: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.633: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.633: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.633: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.633: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.633: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.633: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.633: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.633: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.633: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.634: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.634: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.634: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.634: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.634: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.634: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.634: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.634: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.635: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.635: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.635: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.635: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.635: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.635: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.635: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.635: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.636: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.636: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.636: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.636: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.636: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.636: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.636: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.636: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.637: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.637: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.637: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.637: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.637: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.637: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.637: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.637: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.638: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.638: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.638: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.638: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.638: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.638: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.638: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.638: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.638: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.638: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.639: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.639: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.639: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.639: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.639: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.639: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.639: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.639: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.640: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.640: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.640: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.640: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.640: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.640: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.640: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.640: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.641: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.641: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.641: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.641: [vfs7552] CAPTURE_NUM_STATES entering state 2 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.641: [vfs7552] REQUEST CHUNK entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.641: Sending vfs7552_read_image_chunk 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.641: [vfs7552] REQUEST CHUNK completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.641: [vfs7552] CAPTURE_NUM_STATES entering state 3 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.642: [vfs7552] CAPTURE_NUM_STATES entering state 2 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.642: [vfs7552] REQUEST CHUNK entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.642: Sending vfs7552_read_image_chunk 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.642: [vfs7552] REQUEST CHUNK completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.643: [vfs7552] CAPTURE_NUM_STATES entering state 3 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.643: [vfs7552] CAPTURE_NUM_STATES entering state 2 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.643: [vfs7552] REQUEST CHUNK entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.643: Sending vfs7552_read_image_chunk 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.643: [vfs7552] REQUEST CHUNK completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.643: [vfs7552] CAPTURE_NUM_STATES entering state 3 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.644: [vfs7552] CAPTURE_NUM_STATES entering state 4 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.644: Cleaning image 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.644: variance_after = 17 182s 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.644: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.644: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.644: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.644: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.645: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.645: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.645: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.645: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.645: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.645: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.645: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.645: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.645: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.646: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.646: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.646: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.646: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.646: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.646: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.646: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.646: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.647: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.647: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.647: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.647: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.647: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.647: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.647: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.647: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.648: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.648: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.648: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.648: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.648: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.648: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.648: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.648: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.649: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.649: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.649: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.649: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.649: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.649: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.649: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.649: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.650: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.650: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.650: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.650: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.650: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.650: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.650: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.650: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.650: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.651: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.651: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.651: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.651: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.651: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.651: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.651: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.651: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.651: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.651: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.651: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.651: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.651: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.652: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.652: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.652: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.652: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.652: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.652: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.652: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.652: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.653: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.653: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.653: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.653: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.653: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.653: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.653: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.653: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.654: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.654: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.654: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.654: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.654: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.654: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.654: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.654: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.655: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.655: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.655: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.655: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.655: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.655: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.655: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.655: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.656: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.656: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.656: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.656: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.656: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.656: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.656: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.656: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.657: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.657: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.657: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.657: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.657: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.657: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.657: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.657: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.658: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.658: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.658: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.658: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.658: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.658: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.658: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.658: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.659: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.659: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.659: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.659: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.659: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.659: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.659: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.659: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.660: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.660: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.660: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.660: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.660: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.660: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.660: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.660: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.661: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.661: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.661: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.661: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.661: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.661: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.661: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.661: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.662: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.662: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.662: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.662: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.662: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.662: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.662: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.662: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.663: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.663: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.663: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.664: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.664: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.664: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.664: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.664: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.664: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.664: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.665: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.665: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.665: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.665: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.665: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.665: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.665: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.665: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.666: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.666: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.666: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.666: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.666: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.666: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.666: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.666: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.667: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.667: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.667: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.667: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.667: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.667: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.667: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.667: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.668: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.668: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.668: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.668: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.668: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.668: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.668: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.668: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.669: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.669: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.669: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.669: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.669: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.669: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.669: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.669: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.670: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.670: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.670: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.670: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.670: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.670: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.670: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.670: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.671: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.671: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.671: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.671: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.671: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.671: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.671: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.671: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.672: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.672: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.672: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.672: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.672: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.672: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.672: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.672: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.673: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.673: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.673: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.673: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.673: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.673: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.673: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.673: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.674: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.674: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.674: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.674: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.674: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.674: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.674: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.674: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.675: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.675: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.675: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.675: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.675: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.675: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.675: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.676: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.676: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.676: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.676: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.676: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.676: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.676: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.677: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.677: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.677: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.677: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.677: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.677: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.677: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.677: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.678: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.678: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.678: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.678: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.678: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.678: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.678: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.678: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.679: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.679: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.679: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.679: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.679: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.679: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.679: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.679: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.680: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.680: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.680: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.680: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.680: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.680: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.680: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.680: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.681: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.681: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.681: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.681: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.681: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.681: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.681: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.681: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.682: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.682: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.682: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.682: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.682: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.682: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.682: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.682: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.683: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.683: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.683: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.683: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.683: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.683: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.683: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.683: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.684: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.684: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.684: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.684: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.684: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.684: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.684: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.684: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.685: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.685: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.685: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.685: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.685: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.685: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.685: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.685: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.686: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.686: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.686: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.686: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.686: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.686: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.686: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.686: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.687: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.687: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.687: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.687: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.687: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.687: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.687: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.687: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.688: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.688: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.688: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.688: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.688: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.688: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.688: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.688: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.689: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.689: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.689: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.689: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.689: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.689: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.689: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.689: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.690: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.690: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.690: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.690: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.690: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.690: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.690: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.690: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.691: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.691: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.691: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.691: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.691: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.691: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.691: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.691: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.692: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.692: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.692: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.692: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.692: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.692: [vfs7552] CAPTURE_NUM_STATES entering state 2 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.692: [vfs7552] REQUEST CHUNK entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.692: Sending vfs7552_read_image_chunk 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.693: [vfs7552] REQUEST CHUNK completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.693: [vfs7552] CAPTURE_NUM_STATES entering state 3 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.693: [vfs7552] CAPTURE_NUM_STATES entering state 2 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.693: [vfs7552] REQUEST CHUNK entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.693: Sending vfs7552_read_image_chunk 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.694: [vfs7552] REQUEST CHUNK completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.694: [vfs7552] CAPTURE_NUM_STATES entering state 3 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.695: [vfs7552] CAPTURE_NUM_STATES entering state 2 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.695: [vfs7552] REQUEST CHUNK entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.695: Sending vfs7552_read_image_chunk 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.695: [vfs7552] REQUEST CHUNK completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.695: [vfs7552] CAPTURE_NUM_STATES entering state 3 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.696: [vfs7552] CAPTURE_NUM_STATES entering state 4 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.696: Cleaning image 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.696: variance_after = 17 182s 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.696: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.696: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.696: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.696: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.696: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.697: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.697: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.697: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.697: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.697: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.697: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.697: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.697: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.698: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.698: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.698: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.698: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.698: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.698: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.698: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.698: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.699: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.699: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.699: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.699: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.699: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.699: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.699: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.699: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.700: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.700: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.700: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.700: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.700: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.700: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.700: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.700: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.701: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.701: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.701: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.701: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.701: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.701: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.701: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.701: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.702: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.702: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.702: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.702: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.702: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.702: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.702: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.702: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.703: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.703: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.703: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.703: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.703: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.703: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.703: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.703: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.704: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.704: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.704: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.704: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.704: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.704: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.705: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.705: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.705: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.705: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.705: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.705: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.705: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.705: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.706: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.706: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.706: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.706: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.706: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.706: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.706: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.706: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.707: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.707: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.707: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.707: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.707: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.707: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.707: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.707: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.708: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.708: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.708: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.708: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.708: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.708: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.708: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.708: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.709: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.709: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.709: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.709: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.709: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.709: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.709: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.709: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.710: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.710: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.710: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.710: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.710: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.710: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.710: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.710: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.711: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.711: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.711: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.711: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.711: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.711: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.711: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.711: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.712: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.712: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.712: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.712: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.712: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.712: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.712: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.712: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.713: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.713: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.713: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.713: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.713: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.713: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.713: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.713: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.714: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.714: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.714: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.714: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.714: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.714: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.714: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.714: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.715: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.715: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.715: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.715: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.715: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.715: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.715: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.715: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.716: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.716: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.716: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.716: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.716: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.716: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.716: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.716: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.717: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.717: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.717: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.717: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.717: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.717: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.717: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.717: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.718: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.718: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.718: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.718: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.718: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.718: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.718: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.718: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.719: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.719: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.719: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.719: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.719: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.719: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.719: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.719: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.720: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.720: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.720: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.721: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.721: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.721: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.721: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.721: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.721: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.721: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.722: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.722: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.722: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.722: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.722: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.722: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.722: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.722: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.723: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.723: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.723: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.723: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.723: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.723: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.723: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.723: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.724: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.724: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.724: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.724: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.724: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.724: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.724: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.724: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.725: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.725: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.725: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.725: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.725: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.725: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.725: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.725: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.726: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.726: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.726: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.726: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.726: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.726: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.726: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.726: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.727: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.727: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.727: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.727: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.727: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.727: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.727: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.727: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.728: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.728: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.728: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.728: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.728: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.728: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.728: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.728: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.729: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.729: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.729: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.729: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.729: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.729: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.729: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.729: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.730: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.730: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.730: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.730: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.730: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.730: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.730: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.730: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.731: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.731: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.731: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.731: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.731: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.731: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.731: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.731: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.732: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.732: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.732: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.732: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.732: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.732: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.732: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.732: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.733: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.733: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.733: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.733: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.733: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.733: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.733: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.733: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.734: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.734: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.734: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.734: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.734: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.734: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.734: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.734: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.735: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.735: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.735: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.735: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.735: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.735: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.736: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.736: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.736: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.736: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.736: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.736: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.736: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.736: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.737: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.737: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.737: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.737: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.737: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.737: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.737: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.737: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.738: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.738: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.738: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.738: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.738: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.738: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.738: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.738: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.739: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.739: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.739: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.739: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.739: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.739: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.739: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.739: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.740: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.740: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.740: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.740: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.740: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.740: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.740: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.740: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.741: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.741: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.741: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.741: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.741: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.741: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.741: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.741: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.742: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.742: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.742: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.742: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.742: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.742: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.742: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.742: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.743: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.743: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.743: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.743: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.743: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.743: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.743: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.743: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.744: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.744: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.744: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.744: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.744: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.744: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.744: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.744: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.745: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.745: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.745: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.745: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.745: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.745: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.745: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.745: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.746: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.746: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.746: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.746: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.746: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.746: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.746: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.746: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.747: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.747: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.747: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.747: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.747: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.747: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.747: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.747: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.748: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.748: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.748: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.748: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.748: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.748: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.748: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.748: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.749: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.749: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.749: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.749: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.749: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.749: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.749: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.749: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.750: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.750: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.750: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.750: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.750: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.750: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.750: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.750: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.751: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.751: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.751: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.751: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.751: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.751: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.751: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.751: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.752: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.752: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.753: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.753: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.753: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.753: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.753: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.753: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.753: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.753: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.754: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.754: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.754: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.754: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.754: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.754: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.754: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.754: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.755: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.755: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.755: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.755: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.755: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.755: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.755: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.755: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.756: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.756: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.756: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.756: [vfs7552] CAPTURE_NUM_STATES entering state 2 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.756: [vfs7552] REQUEST CHUNK entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.756: Sending vfs7552_read_image_chunk 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.756: [vfs7552] REQUEST CHUNK completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.756: [vfs7552] CAPTURE_NUM_STATES entering state 3 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.757: [vfs7552] CAPTURE_NUM_STATES entering state 2 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.757: [vfs7552] REQUEST CHUNK entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.757: Sending vfs7552_read_image_chunk 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.758: [vfs7552] REQUEST CHUNK completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.758: [vfs7552] CAPTURE_NUM_STATES entering state 3 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.758: [vfs7552] CAPTURE_NUM_STATES entering state 2 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.758: [vfs7552] REQUEST CHUNK entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.758: Sending vfs7552_read_image_chunk 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.759: [vfs7552] REQUEST CHUNK completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.759: [vfs7552] CAPTURE_NUM_STATES entering state 3 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.759: [vfs7552] CAPTURE_NUM_STATES entering state 4 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.759: Cleaning image 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.759: variance_after = 17 182s 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.759: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.759: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.759: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.760: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.760: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.761: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.761: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.761: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.761: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.761: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.761: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.761: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.761: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.762: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.762: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.762: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.762: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.762: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.762: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.762: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.762: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.763: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.763: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.763: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.763: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.763: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.763: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.763: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.763: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.764: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.764: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.764: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.764: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.764: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.764: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.764: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.764: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.765: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.765: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.765: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.765: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.765: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.765: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.765: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.765: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.766: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.766: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.766: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.766: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.766: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.766: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.767: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.767: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.767: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.767: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.767: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.767: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.767: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.767: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.768: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.768: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.768: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.768: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.768: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.768: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.768: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.768: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.769: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.769: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.769: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.769: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.769: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.769: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.769: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.769: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.770: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.770: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.770: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.770: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.770: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.770: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.771: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.771: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.771: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.771: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.772: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.772: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.772: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.772: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.772: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.772: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.772: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.772: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.773: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.773: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.773: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.773: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.773: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.773: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.773: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.773: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.774: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.774: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.774: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.774: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.774: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.774: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.774: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.774: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.775: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.775: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.775: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.775: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.775: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.775: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.775: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.775: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.776: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.776: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.776: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.776: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.776: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.776: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.777: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.777: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.777: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.777: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.777: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.777: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.777: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.777: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.778: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.778: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.778: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.778: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.778: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.778: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.778: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.778: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.779: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.779: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.779: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.779: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.779: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.779: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.779: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.779: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.780: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.780: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.780: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.780: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.780: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.780: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.780: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.780: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.781: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.781: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.781: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.781: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.781: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.781: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.781: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.781: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.782: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.782: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.782: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.782: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.782: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.782: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.782: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.782: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.783: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.783: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.783: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.783: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.783: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.783: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.783: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.783: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.784: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.784: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.785: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.785: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.785: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.785: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.785: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.785: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.785: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.785: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.786: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.786: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.786: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.786: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.786: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.786: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.786: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.786: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.787: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.787: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.787: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.787: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.787: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.787: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.787: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.787: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.788: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.788: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.788: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.788: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.788: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.788: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.788: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.788: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.789: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.789: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.789: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.789: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.789: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.789: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.789: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.789: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.790: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.790: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.790: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.790: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.790: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.790: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.790: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.790: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.791: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.791: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.791: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.791: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.791: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.791: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.792: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.792: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.792: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.792: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.792: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.792: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.792: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.792: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.793: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.793: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.793: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.793: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.793: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.793: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.793: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.793: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.794: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.794: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.794: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.794: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.794: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.794: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.794: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.794: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.795: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.795: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.795: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.795: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.795: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.795: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.795: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.795: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.796: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.796: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.796: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.796: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.796: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.796: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.796: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.796: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.797: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.797: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.798: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.798: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.798: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.798: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.798: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.798: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.798: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.798: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.799: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.799: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.799: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.799: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.799: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.799: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.799: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.799: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.800: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.800: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.800: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.800: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.800: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.800: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.800: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.800: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.801: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.801: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.801: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.801: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.801: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.801: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.801: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.801: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.802: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.802: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.802: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.802: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.802: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.802: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.803: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.803: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.803: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.803: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.803: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.803: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.803: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.803: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.804: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.804: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.804: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.804: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.804: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.804: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.804: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.804: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.805: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.805: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.805: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.805: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.805: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.805: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.805: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.805: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.806: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.806: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.806: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.806: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.806: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.806: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.806: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.806: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.807: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.807: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.807: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.807: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.807: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.807: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.807: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.807: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.808: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.808: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.809: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.809: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.809: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.809: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.809: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.809: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.809: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.809: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.810: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.810: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.810: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.810: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.810: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.810: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.810: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.810: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.811: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.811: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.811: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.811: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.811: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.811: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.811: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.811: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.812: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.812: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.812: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.812: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.812: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.812: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.812: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.812: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.813: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.813: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.813: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.813: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.813: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.813: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.813: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.813: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.814: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.814: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.814: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.814: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.814: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.814: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.814: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.814: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.815: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.815: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.815: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.815: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.815: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.815: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.816: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.816: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.816: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.816: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.816: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.816: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.816: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.816: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.817: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.817: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.817: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.817: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.817: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.817: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.817: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.817: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.818: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.818: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.818: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.818: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.818: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.818: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.818: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.818: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.819: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.819: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.819: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.819: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.819: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.819: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.819: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.819: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.820: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.820: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.821: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.821: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.821: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.821: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.821: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.821: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.821: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.821: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.822: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.822: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.822: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.822: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.822: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.822: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.822: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.822: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.823: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.823: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.823: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.823: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.823: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.823: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.824: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.824: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.824: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.824: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.824: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.824: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.824: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.824: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.825: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.825: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.825: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.825: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.825: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.825: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.825: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.825: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.826: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.826: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.827: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.827: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.827: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.827: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.827: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.827: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.827: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.827: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.828: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.828: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.828: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.828: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.828: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.828: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.829: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.829: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.829: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.829: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.829: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.829: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.829: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.829: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.830: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.830: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.830: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.831: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.831: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.831: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.831: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.831: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.831: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.831: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.832: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.832: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.832: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.832: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.832: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.832: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.832: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.832: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.833: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.833: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.833: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.833: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.833: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.833: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.834: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.834: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.834: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.834: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.834: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.834: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.834: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.834: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.835: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.835: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.835: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.835: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.835: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.835: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.835: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.835: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.836: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.836: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.836: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.836: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.836: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.836: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.836: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.836: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.837: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.837: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.837: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.838: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.838: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.838: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.838: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.838: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.838: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.838: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.839: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.839: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.839: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.839: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.839: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.839: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.839: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.839: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.840: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.840: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.840: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.840: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.840: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.840: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.840: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.840: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.841: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.841: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.841: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.841: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.841: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.841: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.841: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.841: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.842: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.842: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.842: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.842: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.842: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.842: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.842: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.842: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.843: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.843: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.843: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.843: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.843: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.843: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.843: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.843: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.844: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.844: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.844: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.844: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.844: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.844: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.844: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.845: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.845: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.845: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.845: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.845: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.845: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.845: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.846: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.846: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.846: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.846: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.846: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.846: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.846: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.846: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.847: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.847: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.847: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.847: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.847: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.847: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.847: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.847: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.848: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.848: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.848: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.848: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.848: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.848: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.848: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.848: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.849: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.849: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.849: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.849: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.849: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.849: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.849: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.849: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.850: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.850: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.850: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.850: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.850: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.850: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.850: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.850: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.851: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.851: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.851: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.851: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.851: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.851: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.851: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.851: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.852: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.852: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.853: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.853: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.853: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.853: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.853: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.853: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.853: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.853: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.854: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.854: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.854: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.854: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.854: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.854: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.854: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.854: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.855: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.855: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.855: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.855: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.855: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.855: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.855: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.855: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.856: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.856: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.856: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.856: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.856: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.856: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.856: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.856: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.857: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.857: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.857: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.857: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.857: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.857: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.857: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.857: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.858: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.858: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.858: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.858: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.858: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.858: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.858: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.858: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.859: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.859: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.859: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.859: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.859: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.859: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.859: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.859: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.860: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.860: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.860: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.860: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.860: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.860: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.860: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.860: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.861: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.861: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.861: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.861: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.861: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.861: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.861: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.861: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.862: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.862: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.862: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.862: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.862: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.862: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.862: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.862: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.863: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.863: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.863: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.863: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.863: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.863: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.863: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.863: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.864: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.864: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.864: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.864: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.864: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.864: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.864: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.864: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.865: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.865: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.865: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.865: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.865: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.865: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.865: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.865: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.866: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.866: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.866: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.866: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.866: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.866: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.867: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.867: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.867: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.867: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.867: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.867: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.867: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.867: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.868: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.868: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.868: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.868: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.868: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.868: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.868: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.868: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.869: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.869: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.869: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.869: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.869: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.869: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.869: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.869: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.870: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.870: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.870: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.870: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.870: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.870: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.870: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.870: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.871: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.871: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.871: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.871: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.871: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.871: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.871: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.871: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.872: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.872: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.872: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.872: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.872: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.872: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.872: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.872: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.873: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.873: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.873: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.873: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.873: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.873: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.873: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.873: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.874: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.874: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.874: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.874: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.874: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.874: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.874: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.874: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.877: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.877: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.878: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.878: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.878: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.878: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.878: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.878: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.878: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.878: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.879: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.879: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.879: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.879: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.879: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.879: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.879: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.879: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.880: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.880: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.880: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.880: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.880: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.880: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.880: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.880: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.881: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.881: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.881: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.881: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.881: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.881: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.882: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.882: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.883: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.883: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.883: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.883: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.883: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.883: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.884: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.884: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.884: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.884: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.884: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.884: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.884: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.884: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.885: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.885: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.885: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.885: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.885: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.885: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.885: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.885: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.887: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.887: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.888: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.888: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.888: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.888: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.888: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.888: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.888: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.888: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.889: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.889: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.889: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.889: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.889: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.889: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.889: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.889: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.890: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.890: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.890: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.890: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.890: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.890: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.890: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.890: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.891: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.891: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.891: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.891: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.891: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.891: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.892: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.892: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.893: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.893: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.893: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.893: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.893: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.893: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.894: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.894: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.894: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.894: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.894: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.894: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.894: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.894: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.894: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.894: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.895: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.895: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.895: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.895: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.895: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.895: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.896: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.896: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.896: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.896: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.896: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.896: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.896: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.896: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.897: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.897: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.897: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.897: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.897: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.897: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.897: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.897: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.897: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.897: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.898: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.898: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.898: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.898: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.898: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.898: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.898: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.898: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.899: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.899: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.899: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.899: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.899: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.899: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.899: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.899: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.900: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.900: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.900: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.900: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.900: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.900: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.900: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.900: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.901: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.901: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.901: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.901: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.901: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.901: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.901: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.901: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.902: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.902: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.902: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.902: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.902: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.902: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.902: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.902: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.903: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.903: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.903: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.903: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.903: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.903: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.903: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.903: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.904: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.904: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.904: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.904: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.904: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.904: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.904: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.904: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.905: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.905: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.905: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.905: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.905: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.905: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.905: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.905: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.905: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.905: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.905: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.905: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.905: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.906: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.906: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.906: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.906: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.906: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.906: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.906: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.906: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.906: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.907: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.907: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.907: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.907: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.907: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.907: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.907: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.907: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.908: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.908: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.908: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.908: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.908: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.908: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.908: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.908: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.909: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.909: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.909: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.909: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.909: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.909: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.909: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.909: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.910: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.910: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.910: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.910: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.910: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.910: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.910: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.910: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.911: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.911: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.911: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.911: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.911: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.911: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.911: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.911: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.911: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.911: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.912: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.912: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.912: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.912: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.912: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.912: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.912: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.912: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.913: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.913: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.913: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.913: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.913: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.913: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.913: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.913: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.914: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.914: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.914: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.914: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.914: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.914: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.914: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.914: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.915: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.915: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.915: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.915: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.915: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.915: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.915: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.915: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.916: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.916: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.916: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.916: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.916: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.916: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.916: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.916: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.917: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.917: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.917: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.917: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.917: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.917: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.917: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.917: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.918: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.918: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.918: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.918: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.918: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.918: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.918: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.918: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.919: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.919: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.919: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.919: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.919: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.919: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.919: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.919: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.920: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.920: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.920: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.920: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.920: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.920: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.920: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.920: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.921: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.921: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.921: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.921: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.921: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.921: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.921: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.921: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.922: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.922: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.922: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.922: [vfs7552] CAPTURE_NUM_STATES entering state 2 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.922: [vfs7552] REQUEST CHUNK entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.922: Sending vfs7552_read_image_chunk 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.922: [vfs7552] REQUEST CHUNK completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.922: [vfs7552] CAPTURE_NUM_STATES entering state 3 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.923: [vfs7552] CAPTURE_NUM_STATES entering state 2 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.923: [vfs7552] REQUEST CHUNK entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.923: Sending vfs7552_read_image_chunk 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.923: [vfs7552] REQUEST CHUNK completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.923: [vfs7552] CAPTURE_NUM_STATES entering state 3 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.924: [vfs7552] CAPTURE_NUM_STATES entering state 2 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.924: [vfs7552] REQUEST CHUNK entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.924: Sending vfs7552_read_image_chunk 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.924: [vfs7552] REQUEST CHUNK completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.924: [vfs7552] CAPTURE_NUM_STATES entering state 3 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.925: [vfs7552] CAPTURE_NUM_STATES entering state 4 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.925: Cleaning image 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.925: variance_after = 20 182s 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.925: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.925: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.925: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.925: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.925: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.926: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.926: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.926: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.926: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.926: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.926: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.926: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.926: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.927: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.927: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.927: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.927: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.927: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.927: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.927: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.927: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.928: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.928: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.928: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.928: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.928: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.928: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.928: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.928: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.929: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.929: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.929: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.929: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.929: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.929: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.929: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.929: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.930: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.930: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.930: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.930: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.930: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.930: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.930: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.930: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.931: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.931: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.931: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.931: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.931: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.931: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.931: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.931: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.932: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.932: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.932: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.932: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.932: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.932: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.932: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.932: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.933: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.933: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.933: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.933: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.933: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.933: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.933: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.933: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.934: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.934: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.934: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.934: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.934: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.934: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.934: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.934: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.935: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.935: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.935: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.935: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.935: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.935: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.935: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.935: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.935: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.935: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.935: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.935: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.935: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.935: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.936: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.936: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.936: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.936: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.936: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.936: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.936: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.936: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.937: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.937: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.937: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.937: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.937: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.937: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.937: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.937: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.938: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.938: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.938: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.938: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.938: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.938: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.938: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.938: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.939: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.939: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.939: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.939: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.939: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.939: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.939: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.939: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.940: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.940: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.940: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.940: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.940: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.940: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.940: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.940: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.941: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.941: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.941: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.941: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.941: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.941: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.941: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.941: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.942: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.942: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.942: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.942: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.942: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.942: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.942: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.942: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.943: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.943: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.943: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.943: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.943: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.943: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.943: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.943: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.944: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.944: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.944: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.944: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.944: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.944: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.944: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.944: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.944: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.944: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.945: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.945: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.945: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.945: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.945: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.945: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.945: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.945: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.946: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.946: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.946: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.946: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.946: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.946: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.946: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.946: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.947: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.947: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.947: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.947: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.947: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.947: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.947: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.947: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.948: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.948: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.948: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.948: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.948: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.948: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.948: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.948: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.949: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.949: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.949: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.949: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.949: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.949: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.949: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.949: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.950: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.950: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.950: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.950: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.950: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.950: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.950: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.950: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.951: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.951: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.951: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.951: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.951: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.951: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.951: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.951: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.952: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.952: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.952: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.952: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.952: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.952: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.952: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.952: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.953: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.953: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.953: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.953: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.953: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.953: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.953: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.953: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.954: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.954: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.954: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.954: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.954: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.954: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.954: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.954: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.955: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.955: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.955: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.955: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.955: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.955: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.955: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.955: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.956: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.956: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.956: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.956: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.956: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.956: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.956: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.956: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.957: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.957: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.957: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.957: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.957: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.957: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.957: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.957: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.958: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.958: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.958: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.958: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.958: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.958: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.958: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.958: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.959: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.959: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.959: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.959: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.959: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.959: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.959: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.959: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.960: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.960: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.960: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.960: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.960: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.960: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.960: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.960: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.961: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.961: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.961: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.961: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.961: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.961: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.961: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.961: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.962: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.962: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.962: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.962: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.962: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.962: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.962: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.962: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.963: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.963: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.963: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.963: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.963: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.963: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.963: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.963: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.964: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.964: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.964: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.964: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.964: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.964: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.964: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.964: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.965: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.965: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.965: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.965: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.965: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.965: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.965: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.965: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.966: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.966: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.966: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.966: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.966: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.966: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.966: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.966: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.967: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.967: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.967: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.967: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.967: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.967: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.967: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.967: Receiving 64 bytes 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.968: Got 6 bytes out of 64 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.968: [vfs7552] QUERY DATA READY completed successfully 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.968: [vfs7552] CAPTURE_NUM_STATES entering state 1 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.968: [vfs7552] CAPTURE_NUM_STATES entering state 0 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.968: [vfs7552] QUERY DATA READY entering state 0 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.968: Sending vfs7552_is_image_ready 182s (process:2314): libfprint-SSM-DEBUG: 16:48:19.968: [vfs7552] QUERY DATA READY entering state 1 182s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.968: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.969: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:19.969: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:19.969: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:19.969: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:19.969: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.969: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:19.969: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.969: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.970: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:19.970: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:19.970: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:19.970: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:19.970: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.970: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:19.970: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.970: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.971: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:19.971: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:19.971: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:19.971: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:19.971: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.971: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:19.971: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.971: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.972: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:19.972: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:19.972: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:19.972: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:19.972: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.972: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:19.972: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.972: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.972: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:19.972: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:19.972: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:19.972: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:19.972: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.972: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:19.973: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.973: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.973: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:19.973: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:19.973: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:19.973: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:19.973: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.973: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:19.974: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.974: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.974: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:19.974: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:19.974: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:19.974: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:19.974: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.974: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:19.975: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.975: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.975: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:19.975: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:19.975: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:19.975: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:19.975: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.975: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:19.976: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.976: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.976: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:19.976: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:19.976: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:19.976: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:19.976: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.976: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:19.977: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.977: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.977: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:19.977: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:19.977: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:19.977: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:19.977: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.977: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:19.978: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.978: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.978: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:19.978: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:19.978: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:19.978: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:19.978: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.978: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:19.978: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.978: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.979: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:19.979: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:19.979: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:19.979: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:19.979: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.979: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:19.979: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.979: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.980: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:19.980: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:19.980: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:19.980: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:19.980: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.980: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:19.980: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.980: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.981: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:19.981: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:19.981: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:19.981: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:19.981: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.981: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:19.981: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.981: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.982: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:19.982: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:19.982: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:19.982: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:19.982: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.982: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:19.982: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.982: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.983: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:19.983: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:19.983: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:19.983: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:19.983: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.983: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:19.983: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.983: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.983: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:19.983: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:19.983: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:19.983: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:19.984: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.984: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:19.984: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.984: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.984: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:19.984: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:19.984: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:19.984: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:19.984: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.984: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:19.985: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.985: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.985: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:19.985: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:19.985: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:19.985: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:19.985: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.985: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:19.986: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.986: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.986: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:19.986: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:19.986: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:19.986: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:19.986: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.986: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:19.987: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.987: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.987: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:19.987: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:19.987: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:19.987: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:19.987: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.987: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:19.988: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.988: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.988: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:19.988: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:19.988: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:19.988: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:19.988: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.988: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:19.989: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.989: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.989: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:19.989: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:19.989: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:19.989: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:19.989: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.989: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:19.990: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.990: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.990: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:19.990: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:19.990: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:19.990: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:19.990: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.990: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:19.991: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.991: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.991: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:19.991: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:19.991: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:19.991: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:19.991: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.991: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:19.992: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.992: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.992: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:19.992: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:19.992: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:19.992: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:19.992: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.992: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:19.993: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.993: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.993: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:19.993: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:19.993: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:19.993: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:19.993: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.993: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:19.994: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.994: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.994: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:19.994: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:19.994: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:19.994: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:19.994: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.994: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:19.995: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.995: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.995: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:19.995: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:19.995: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:19.995: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:19.995: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.995: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:19.996: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.996: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.996: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:19.996: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:19.996: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:19.996: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:19.996: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.996: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:19.997: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.997: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.997: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:19.997: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:19.997: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:19.997: [vfs7552] CAPTURE_NUM_STATES entering state 2 183s (process:2314): libfprint-SSM-DEBUG: 16:48:19.997: [vfs7552] REQUEST CHUNK entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.997: Sending vfs7552_read_image_chunk 183s (process:2314): libfprint-SSM-DEBUG: 16:48:19.997: [vfs7552] REQUEST CHUNK completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:19.997: [vfs7552] CAPTURE_NUM_STATES entering state 3 183s (process:2314): libfprint-SSM-DEBUG: 16:48:19.998: [vfs7552] CAPTURE_NUM_STATES entering state 2 183s (process:2314): libfprint-SSM-DEBUG: 16:48:19.998: [vfs7552] REQUEST CHUNK entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.998: Sending vfs7552_read_image_chunk 183s (process:2314): libfprint-SSM-DEBUG: 16:48:19.998: [vfs7552] REQUEST CHUNK completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:19.998: [vfs7552] CAPTURE_NUM_STATES entering state 3 183s (process:2314): libfprint-SSM-DEBUG: 16:48:19.999: [vfs7552] CAPTURE_NUM_STATES entering state 2 183s (process:2314): libfprint-SSM-DEBUG: 16:48:19.999: [vfs7552] REQUEST CHUNK entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:19.999: Sending vfs7552_read_image_chunk 183s (process:2314): libfprint-SSM-DEBUG: 16:48:19.999: [vfs7552] REQUEST CHUNK completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:19.999: [vfs7552] CAPTURE_NUM_STATES entering state 3 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.000: [vfs7552] CAPTURE_NUM_STATES entering state 4 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.000: Cleaning image 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.000: variance_after = 17 183s 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.000: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.000: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.000: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.001: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.001: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.001: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.001: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.001: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.001: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.001: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.001: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.001: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.001: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.002: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.002: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.002: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.002: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.002: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.002: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.002: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.002: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.003: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.003: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.003: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.003: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.003: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.003: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.003: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.003: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.004: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.004: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.004: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.004: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.004: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.004: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.004: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.004: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.005: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.005: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.005: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.005: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.005: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.005: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.005: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.006: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.006: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.006: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.006: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.006: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.006: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.006: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.006: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.006: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.007: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.007: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.007: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.007: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.007: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.007: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.007: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.007: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.008: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.008: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.008: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.008: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.008: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.008: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.008: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.008: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.009: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.009: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.009: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.009: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.009: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.009: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.009: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.009: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.010: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.010: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.010: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.010: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.010: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.010: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.010: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.010: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.011: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.011: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.011: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.011: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.011: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.011: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.011: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.011: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.012: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.012: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.012: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.012: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.012: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.012: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.012: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.012: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.013: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.013: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.013: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.013: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.013: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.013: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.013: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.013: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.014: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.014: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.014: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.014: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.014: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.014: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.014: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.014: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.015: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.015: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.015: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.015: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.015: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.015: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.015: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.015: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.016: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.016: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.016: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.016: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.016: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.016: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.016: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.016: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.017: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.017: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.017: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.017: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.017: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.017: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.017: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.017: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.018: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.018: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.018: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.018: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.018: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.018: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.018: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.018: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.019: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.019: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.019: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.019: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.019: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.019: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.019: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.019: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.020: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.020: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.020: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.020: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.020: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.020: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.020: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.020: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.021: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.021: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.021: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.021: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.021: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.021: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.021: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.021: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.022: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.022: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.022: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.022: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.022: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.022: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.022: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.022: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.023: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.023: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.023: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.023: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.023: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.023: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.023: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.023: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.023: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.023: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.023: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.024: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.024: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.024: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.024: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.024: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.025: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.025: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.025: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.025: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.025: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.025: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.025: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.025: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.026: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.026: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.026: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.026: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.026: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.026: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.026: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.026: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.027: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.027: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.027: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.027: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.027: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.027: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.027: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.027: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.027: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.028: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.028: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.028: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.028: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.028: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.028: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.028: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.029: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.029: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.029: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.029: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.029: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.029: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.029: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.029: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.029: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.029: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.029: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.029: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.029: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.029: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.030: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.030: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.030: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.030: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.030: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.030: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.030: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.030: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.031: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.031: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.031: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.031: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.031: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.031: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.031: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.031: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.032: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.032: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.032: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.032: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.032: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.032: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.032: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.032: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.033: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.033: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.033: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.033: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.033: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.033: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.033: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.033: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.034: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.034: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.034: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.034: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.034: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.034: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.034: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.034: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.035: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.035: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.035: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.035: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.035: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.035: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.035: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.035: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.036: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.036: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.036: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.036: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.036: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.036: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.036: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.036: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.037: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.037: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.037: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.037: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.037: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.037: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.037: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.037: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.038: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.038: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.038: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.038: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.038: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.038: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.038: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.038: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.039: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.039: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.039: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.039: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.039: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.039: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.039: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.039: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.040: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.040: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.040: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.040: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.040: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.040: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.040: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.040: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.041: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.041: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.041: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.041: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.041: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.041: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.041: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.041: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.042: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.042: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.042: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.042: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.042: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.042: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.042: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.042: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.042: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.043: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.043: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.043: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.043: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.043: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.043: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.043: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.044: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.044: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.044: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.044: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.044: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.044: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.044: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.044: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.044: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.044: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.045: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.045: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.045: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.045: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.045: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.045: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.045: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.045: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.046: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.046: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.046: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.046: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.046: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.046: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.046: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.046: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.047: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.047: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.047: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.047: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.047: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.047: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.047: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.047: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.048: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.048: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.048: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.048: [vfs7552] CAPTURE_NUM_STATES entering state 2 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.048: [vfs7552] REQUEST CHUNK entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.048: Sending vfs7552_read_image_chunk 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.048: [vfs7552] REQUEST CHUNK completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.048: [vfs7552] CAPTURE_NUM_STATES entering state 3 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.049: [vfs7552] CAPTURE_NUM_STATES entering state 2 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.049: [vfs7552] REQUEST CHUNK entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.049: Sending vfs7552_read_image_chunk 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.049: [vfs7552] REQUEST CHUNK completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.049: [vfs7552] CAPTURE_NUM_STATES entering state 3 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.050: [vfs7552] CAPTURE_NUM_STATES entering state 2 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.050: [vfs7552] REQUEST CHUNK entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.050: Sending vfs7552_read_image_chunk 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.050: [vfs7552] REQUEST CHUNK completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.050: [vfs7552] CAPTURE_NUM_STATES entering state 3 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.051: [vfs7552] CAPTURE_NUM_STATES entering state 4 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.051: Cleaning image 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.051: variance_after = 17 183s 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.051: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.051: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.051: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.051: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.051: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.052: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.052: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.052: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.052: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.052: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.052: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.052: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.052: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.053: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.053: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.053: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.053: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.053: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.053: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.053: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.053: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.054: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.054: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.054: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.054: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.054: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.054: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.054: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.054: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.054: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.054: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.054: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.054: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.054: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.054: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.055: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.055: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.055: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.055: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.055: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.055: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.055: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.055: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.056: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.056: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.056: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.056: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.056: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.056: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.056: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.056: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.057: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.057: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.057: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.057: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.057: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.057: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.057: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.057: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.058: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.058: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.058: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.058: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.058: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.058: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.058: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.058: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.059: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.059: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.059: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.059: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.059: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.059: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.059: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.059: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.060: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.060: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.060: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.060: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.060: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.060: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.060: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.060: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.061: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.061: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.061: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.061: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.061: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.061: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.061: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.061: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.062: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.062: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.062: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.062: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.062: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.062: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.062: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.062: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.063: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.063: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.063: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.063: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.063: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.063: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.063: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.063: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.064: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.064: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.064: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.064: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.064: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.064: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.064: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.064: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.065: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.065: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.065: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.065: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.065: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.065: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.065: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.065: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.066: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.066: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.066: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.066: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.066: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.066: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.066: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.066: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.067: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.067: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.067: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.067: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.067: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.067: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.067: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.067: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.068: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.068: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.068: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.068: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.068: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.068: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.068: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.068: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.069: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.069: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.069: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.069: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.069: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.069: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.069: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.069: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.069: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.070: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.070: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.070: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.070: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.070: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.070: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.070: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.070: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.070: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.071: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.071: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.071: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.071: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.071: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.071: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.071: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.071: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.072: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.072: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.072: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.072: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.072: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.072: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.072: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.072: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.073: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.073: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.073: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.073: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.073: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.073: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.073: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.073: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.074: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.074: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.074: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.074: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.074: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.074: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.074: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.074: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.075: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.075: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.075: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.075: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.075: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.075: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.075: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.075: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.076: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.076: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.076: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.076: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.076: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.076: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.077: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.077: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.077: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.077: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.077: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.077: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.077: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.077: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.078: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.078: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.078: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.078: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.078: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.078: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.078: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.078: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.078: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.079: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.079: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.079: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.079: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.079: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.079: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.079: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.079: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.079: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.080: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.080: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.080: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.080: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.080: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.080: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.081: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.081: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.081: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.081: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.081: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.081: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.081: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.081: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.082: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.082: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.082: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.082: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.082: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.082: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.082: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.082: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.082: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.082: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.083: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.083: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.083: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.083: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.083: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.083: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.084: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.084: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.084: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.084: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.084: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.084: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.084: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.084: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.085: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.085: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.085: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.085: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.085: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.085: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.085: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.085: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.086: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.086: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.086: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.086: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.086: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.086: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.086: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.086: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.087: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.087: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.087: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.087: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.087: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.087: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.087: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.087: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.087: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.087: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.088: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.088: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.088: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.088: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.088: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.088: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.088: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.088: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.089: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.089: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.089: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.089: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.089: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.089: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.089: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.089: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.090: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.090: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.090: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.090: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.090: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.090: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.090: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.090: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.091: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.091: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.091: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.091: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.091: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.091: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.091: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.091: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.092: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.092: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.092: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.092: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.092: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.092: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.092: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.092: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.093: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.093: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.093: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.093: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.093: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.093: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.093: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.093: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.094: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.094: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.094: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.094: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.094: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.094: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.094: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.094: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.095: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.095: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.095: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.095: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.095: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.095: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.095: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.095: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.096: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.096: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.096: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.096: [vfs7552] CAPTURE_NUM_STATES entering state 2 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.096: [vfs7552] REQUEST CHUNK entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.096: Sending vfs7552_read_image_chunk 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.096: [vfs7552] REQUEST CHUNK completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.096: [vfs7552] CAPTURE_NUM_STATES entering state 3 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.097: [vfs7552] CAPTURE_NUM_STATES entering state 2 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.097: [vfs7552] REQUEST CHUNK entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.097: Sending vfs7552_read_image_chunk 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.097: [vfs7552] REQUEST CHUNK completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.097: [vfs7552] CAPTURE_NUM_STATES entering state 3 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.098: [vfs7552] CAPTURE_NUM_STATES entering state 2 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.098: [vfs7552] REQUEST CHUNK entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.098: Sending vfs7552_read_image_chunk 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.098: [vfs7552] REQUEST CHUNK completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.098: [vfs7552] CAPTURE_NUM_STATES entering state 3 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.099: [vfs7552] CAPTURE_NUM_STATES entering state 4 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.099: Cleaning image 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.099: variance_after = 17 183s 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.099: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.099: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.099: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.099: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.099: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.100: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.100: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.100: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.100: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.100: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.100: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.100: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.100: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.101: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.101: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.101: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.101: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.101: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.101: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.101: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.101: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.102: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.102: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.102: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.102: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.102: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.102: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.102: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.102: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.103: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.103: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.103: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.103: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.103: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.103: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.103: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.103: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.104: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.104: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.104: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.104: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.104: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.104: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.104: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.104: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.104: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.104: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.104: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.104: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.104: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.104: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.105: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.105: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.105: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.105: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.105: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.105: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.105: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.105: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.106: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.106: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.106: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.106: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.106: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.106: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.106: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.106: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.107: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.107: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.107: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.107: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.107: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.107: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.107: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.107: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.108: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.108: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.108: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.108: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.108: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.108: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.108: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.108: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.109: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.109: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.109: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.109: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.109: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.109: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.109: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.109: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.110: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.110: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.110: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.110: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.110: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.110: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.110: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.110: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.111: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.111: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.111: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.111: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.111: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.111: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.111: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.111: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.112: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.112: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.112: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.112: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.112: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.112: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.112: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.112: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.113: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.113: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.113: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.113: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.113: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.113: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.113: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.113: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.113: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.113: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.114: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.114: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.114: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.114: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.114: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.114: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.114: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.114: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.115: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.115: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.115: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.115: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.115: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.115: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.115: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.115: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.116: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.116: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.116: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.116: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.116: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.116: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.116: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.116: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.117: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.117: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.117: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.117: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.117: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.117: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.117: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.117: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.118: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.118: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.118: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.118: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.118: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.118: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.118: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.118: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.119: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.119: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.119: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.119: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.119: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.119: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.119: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.119: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.120: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.120: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.120: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.120: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.120: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.120: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.120: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.120: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.121: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.121: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.121: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.121: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.121: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.121: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.121: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.121: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.121: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.121: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.121: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.122: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.122: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.122: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.122: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.122: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.122: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.122: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.122: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.122: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.122: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.122: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.123: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.123: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.123: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.123: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.123: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.123: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.123: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.123: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.124: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.124: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.124: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.124: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.124: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.124: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.124: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.124: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.125: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.125: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.125: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.125: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.125: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.125: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.125: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.125: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.126: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.126: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.126: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.126: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.126: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.126: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.126: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.126: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.127: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.127: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.127: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.127: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.127: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.127: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.127: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.127: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.128: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.128: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.128: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.128: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.128: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.128: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.128: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.128: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.129: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.129: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.129: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.129: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.129: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.129: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.129: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.129: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.130: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.130: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.131: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.131: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.131: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.131: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.131: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.131: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.132: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.132: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.133: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.133: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.133: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.133: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.133: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.133: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.134: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.134: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.134: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.134: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.134: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.134: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.134: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.134: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.134: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.135: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.135: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.135: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.135: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.135: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.135: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.135: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.136: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.136: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.136: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.136: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.136: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.136: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.136: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.136: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.137: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.137: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.137: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.137: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.137: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.137: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.137: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.137: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.137: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.137: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.138: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.138: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.138: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.138: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.138: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.138: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.138: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.138: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.139: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.139: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.139: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.139: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.139: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.139: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.139: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.139: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.140: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.140: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.140: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.140: [vfs7552] CAPTURE_NUM_STATES entering state 2 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.140: [vfs7552] REQUEST CHUNK entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.140: Sending vfs7552_read_image_chunk 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.140: [vfs7552] REQUEST CHUNK completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.140: [vfs7552] CAPTURE_NUM_STATES entering state 3 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.141: [vfs7552] CAPTURE_NUM_STATES entering state 2 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.141: [vfs7552] REQUEST CHUNK entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.141: Sending vfs7552_read_image_chunk 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.141: [vfs7552] REQUEST CHUNK completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.141: [vfs7552] CAPTURE_NUM_STATES entering state 3 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.142: [vfs7552] CAPTURE_NUM_STATES entering state 2 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.142: [vfs7552] REQUEST CHUNK entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.142: Sending vfs7552_read_image_chunk 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.142: [vfs7552] REQUEST CHUNK completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.142: [vfs7552] CAPTURE_NUM_STATES entering state 3 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.143: [vfs7552] CAPTURE_NUM_STATES entering state 4 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.143: Cleaning image 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.143: variance_after = 17 183s 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.143: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.143: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.143: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.143: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.143: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.144: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.144: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.144: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.144: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.144: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.144: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.144: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.144: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.145: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.145: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.145: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.145: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.145: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.145: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.145: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.145: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.146: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.146: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.146: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.146: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.146: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.146: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.146: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.146: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.147: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.147: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.147: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.147: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.147: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.147: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.147: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.147: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.148: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.148: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.148: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.148: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.148: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.148: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.148: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.148: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.149: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.149: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.149: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.149: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.149: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.149: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.149: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.149: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.150: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.150: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.150: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.150: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.150: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.150: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.150: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.150: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.151: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.151: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.151: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.151: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.151: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.151: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.151: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.151: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.152: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.152: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.152: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.152: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.152: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.152: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.152: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.152: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.152: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.152: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.152: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.152: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.152: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.152: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.153: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.153: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.153: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.153: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.153: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.153: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.153: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.153: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.154: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.154: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.154: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.154: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.154: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.154: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.154: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.154: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.155: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.155: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.155: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.155: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.155: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.155: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.155: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.155: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.156: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.156: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.156: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.156: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.156: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.156: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.156: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.156: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.157: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.157: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.157: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.157: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.157: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.157: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.157: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.157: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.158: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.158: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.158: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.158: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.158: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.158: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.158: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.158: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.159: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.159: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.159: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.159: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.159: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.159: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.159: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.159: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.160: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.160: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.160: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.160: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.160: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.160: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.160: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.160: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.161: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.161: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.161: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.161: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.161: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.161: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.161: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.161: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.162: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.162: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.162: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.162: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.162: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.162: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.162: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.162: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.163: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.163: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.163: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.163: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.163: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.163: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.163: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.163: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.163: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.163: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.164: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.164: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.164: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.164: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.164: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.164: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.164: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.165: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.165: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.165: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.165: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.165: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.165: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.165: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.165: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.165: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.166: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.166: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.166: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.166: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.166: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.166: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.166: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.166: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.167: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.167: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.167: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.167: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.167: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.167: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.167: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.167: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.168: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.168: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.168: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.168: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.168: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.168: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.168: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.168: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.169: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.169: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.169: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.169: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.169: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.169: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.169: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.169: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.170: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.170: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.170: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.170: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.170: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.170: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.170: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.170: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.171: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.171: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.171: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.171: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.171: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.171: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.171: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.171: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.172: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.172: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.172: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.172: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.172: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.172: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.172: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.172: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.173: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.173: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.173: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.173: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.173: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.173: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.173: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.173: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.174: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.174: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.174: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.174: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.174: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.174: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.174: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.174: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.175: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.175: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.175: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.175: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.175: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.175: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.175: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.175: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.176: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.176: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.176: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.176: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.176: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.176: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.176: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.176: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.177: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.177: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.177: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.177: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.177: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.177: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.177: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.177: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.178: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.178: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.178: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.178: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.178: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.178: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.178: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.178: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.178: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.178: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.178: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.178: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.178: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.178: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.179: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.179: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.179: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.179: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.179: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.180: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.180: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.180: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.180: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.180: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.180: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.180: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.180: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.180: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.180: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.180: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.181: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.181: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.181: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.181: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.181: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.181: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.181: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.181: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.182: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.182: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.182: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.182: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.182: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.182: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.182: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.182: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.183: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.183: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.183: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.183: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.183: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.183: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.183: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.183: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.184: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.184: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.184: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.184: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.184: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.184: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.184: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.184: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.185: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.185: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.185: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.185: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.185: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.185: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.185: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.185: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.186: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.186: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.186: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.186: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.186: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.186: [vfs7552] CAPTURE_NUM_STATES entering state 2 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.186: [vfs7552] REQUEST CHUNK entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.186: Sending vfs7552_read_image_chunk 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.187: [vfs7552] REQUEST CHUNK completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.187: [vfs7552] CAPTURE_NUM_STATES entering state 3 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.187: [vfs7552] CAPTURE_NUM_STATES entering state 2 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.187: [vfs7552] REQUEST CHUNK entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.187: Sending vfs7552_read_image_chunk 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.188: [vfs7552] REQUEST CHUNK completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.188: [vfs7552] CAPTURE_NUM_STATES entering state 3 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.188: [vfs7552] CAPTURE_NUM_STATES entering state 2 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.188: [vfs7552] REQUEST CHUNK entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.188: Sending vfs7552_read_image_chunk 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.189: [vfs7552] REQUEST CHUNK completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.189: [vfs7552] CAPTURE_NUM_STATES entering state 3 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.189: [vfs7552] CAPTURE_NUM_STATES entering state 4 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.189: Cleaning image 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.189: variance_after = 16 183s 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.189: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.189: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.189: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.190: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.190: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.190: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.190: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.190: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.190: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.190: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.190: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.191: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.191: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.191: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.191: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.191: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.191: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.191: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.191: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.192: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.192: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.192: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.192: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.192: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.192: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.192: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.192: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.193: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.193: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.193: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.193: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.193: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.193: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.193: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.193: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.193: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.193: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.194: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.194: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.194: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.194: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.194: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.194: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.194: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.194: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.195: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.195: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.195: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.195: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.195: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.195: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.195: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.195: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.196: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.196: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.196: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.196: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.196: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.196: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.196: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.196: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.197: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.197: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.197: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.197: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.197: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.197: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.197: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.197: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.198: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.198: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.198: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.198: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.198: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.198: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.198: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.198: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.199: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.199: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.199: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.199: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.199: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.199: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.199: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.199: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.200: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.200: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.200: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.200: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.200: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.200: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.200: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.200: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.201: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.201: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.201: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.201: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.201: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.201: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.201: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.201: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.202: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.202: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.202: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.202: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.202: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.202: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.202: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.202: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.203: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.203: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.203: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.203: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.203: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.203: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.203: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.203: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.204: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.204: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.204: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.204: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.204: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.204: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.204: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.204: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.205: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.205: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.205: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.205: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.205: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.205: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.205: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.205: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.206: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.206: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.206: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.206: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.206: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.206: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.206: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.206: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.207: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.207: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.207: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.207: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.207: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.207: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.207: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.207: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.208: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.208: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.208: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.208: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.208: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.208: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.208: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.208: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.209: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.209: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.209: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.209: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.209: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.209: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.209: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.209: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.210: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.210: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.210: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.210: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.210: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.210: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.210: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.210: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.211: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.211: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.211: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.211: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.211: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.211: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.211: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.211: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.212: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.212: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.212: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.212: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.212: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.212: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.212: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.212: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.213: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.213: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.213: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.213: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.213: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.213: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.213: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.213: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.214: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.214: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.214: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.214: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.214: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.214: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.214: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.214: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.215: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.215: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.215: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.215: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.215: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.215: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.215: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.215: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.216: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.216: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.216: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.216: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.216: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.216: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.216: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.216: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.217: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.217: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.217: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.217: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.217: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.217: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.217: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.217: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.218: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.218: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.218: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.218: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.218: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.218: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.218: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.218: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.219: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.219: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.219: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.219: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.219: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.219: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.219: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.219: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.220: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.220: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.220: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.220: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.220: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.220: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.220: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.221: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.221: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.221: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.221: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.221: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.221: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.221: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.221: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.222: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.222: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.222: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.222: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.222: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.222: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.222: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.223: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.223: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.223: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.223: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.223: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.223: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.223: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.223: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.223: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.223: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.224: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.224: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.224: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.224: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.224: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.224: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.224: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.224: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.225: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.225: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.225: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.225: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.225: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.225: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.225: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.225: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.226: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.226: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.226: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.226: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.226: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.226: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.226: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.226: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.227: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.227: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.227: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.227: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.227: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.227: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.227: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.227: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.228: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.228: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.228: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.228: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.228: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.228: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.228: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.228: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.229: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.229: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.229: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.229: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.229: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.229: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.229: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.229: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.230: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.230: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.230: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.230: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.230: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.230: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.230: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.230: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.231: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.231: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.231: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.231: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.231: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.231: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.231: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.231: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.232: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.232: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.232: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.232: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.232: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.232: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.232: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.232: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.233: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.233: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.233: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.233: [vfs7552] CAPTURE_NUM_STATES entering state 2 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.233: [vfs7552] REQUEST CHUNK entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.233: Sending vfs7552_read_image_chunk 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.233: [vfs7552] REQUEST CHUNK completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.233: [vfs7552] CAPTURE_NUM_STATES entering state 3 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.234: [vfs7552] CAPTURE_NUM_STATES entering state 2 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.234: [vfs7552] REQUEST CHUNK entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.234: Sending vfs7552_read_image_chunk 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.234: [vfs7552] REQUEST CHUNK completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.234: [vfs7552] CAPTURE_NUM_STATES entering state 3 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.235: [vfs7552] CAPTURE_NUM_STATES entering state 2 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.235: [vfs7552] REQUEST CHUNK entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.235: Sending vfs7552_read_image_chunk 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.235: [vfs7552] REQUEST CHUNK completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.235: [vfs7552] CAPTURE_NUM_STATES entering state 3 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.236: [vfs7552] CAPTURE_NUM_STATES entering state 4 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.236: Cleaning image 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.236: variance_after = 17 183s 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.236: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.236: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.236: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.236: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.236: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.237: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.237: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.237: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.237: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.237: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.237: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.237: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.237: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.238: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.238: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.238: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.238: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.238: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.238: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.238: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.238: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.239: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.239: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.239: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.239: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.239: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.239: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.239: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.239: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.240: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.240: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.240: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.240: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.240: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.240: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.240: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.240: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.241: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.241: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.241: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.241: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.241: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.241: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.241: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.241: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.242: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.242: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.242: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.242: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.242: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.242: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.242: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.242: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.243: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.243: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.243: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.243: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.243: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.243: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.243: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.243: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.244: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.244: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.244: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.244: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.244: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.244: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.244: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.244: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.245: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.245: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.245: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.245: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.245: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.245: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.245: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.245: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.246: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.246: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.246: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.246: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.246: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.246: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.246: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.246: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.247: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.247: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.247: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.247: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.247: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.247: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.247: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.247: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.248: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.248: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.248: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.248: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.248: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.248: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.248: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.248: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.248: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.248: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.248: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.248: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.248: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.248: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.249: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.249: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.249: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.249: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.249: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.249: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.249: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.249: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.250: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.250: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.250: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.250: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.250: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.250: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.250: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.250: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.251: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.251: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.251: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.251: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.251: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.251: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.251: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.251: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.252: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.252: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.252: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.252: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.252: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.252: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.252: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.252: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.253: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.253: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.253: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.253: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.253: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.253: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.253: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.253: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.254: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.254: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.254: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.254: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.254: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.254: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.254: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.254: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.255: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.255: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.255: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.255: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.255: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.255: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.255: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.255: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.256: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.256: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.256: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.256: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.256: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.256: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.256: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.256: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.257: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.257: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.257: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.257: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.257: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.257: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.257: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.257: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.258: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.258: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.258: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.258: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.258: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.258: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.258: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.258: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.259: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.259: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.259: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.259: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.259: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.259: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.259: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.259: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.260: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.260: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.260: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.260: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.260: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.260: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.260: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.260: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.261: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.261: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.261: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.261: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.261: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.261: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.261: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.261: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.262: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.262: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.262: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.262: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.262: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.262: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.262: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.262: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.263: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.263: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.263: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.263: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.263: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.263: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.263: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.263: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.264: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.264: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.264: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.264: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.264: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.264: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.264: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.264: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.265: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.265: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.265: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.265: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.265: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.265: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.265: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.265: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.266: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.266: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.266: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.266: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.266: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.266: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.266: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.266: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.267: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.267: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.267: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.267: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.267: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.267: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.267: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.267: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.268: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.268: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.268: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.268: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.268: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.268: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.268: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.268: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.269: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.269: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.269: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.269: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.269: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.269: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.269: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.269: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.270: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.270: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.270: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.270: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.270: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.270: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.270: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.270: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.270: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.270: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.271: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.271: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.271: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.271: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.271: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.271: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.272: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.272: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.272: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.272: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.272: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.272: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.272: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.272: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.273: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.273: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.273: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.273: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.273: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.273: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.273: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.273: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.273: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.273: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.274: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.274: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.274: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.274: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.274: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.274: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.274: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.275: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.275: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.275: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.275: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.275: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.275: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.275: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.275: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.275: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.276: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.276: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.276: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.276: [vfs7552] CAPTURE_NUM_STATES entering state 2 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.276: [vfs7552] REQUEST CHUNK entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.276: Sending vfs7552_read_image_chunk 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.276: [vfs7552] REQUEST CHUNK completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.276: [vfs7552] CAPTURE_NUM_STATES entering state 3 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.277: [vfs7552] CAPTURE_NUM_STATES entering state 2 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.277: [vfs7552] REQUEST CHUNK entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.277: Sending vfs7552_read_image_chunk 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.277: [vfs7552] REQUEST CHUNK completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.277: [vfs7552] CAPTURE_NUM_STATES entering state 3 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.278: [vfs7552] CAPTURE_NUM_STATES entering state 2 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.278: [vfs7552] REQUEST CHUNK entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.278: Sending vfs7552_read_image_chunk 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.278: [vfs7552] REQUEST CHUNK completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.278: [vfs7552] CAPTURE_NUM_STATES entering state 3 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.279: [vfs7552] CAPTURE_NUM_STATES entering state 4 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.279: Cleaning image 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.279: variance_after = 16 183s 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.279: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.279: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.279: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.279: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.279: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.280: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.280: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.280: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.280: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.280: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.280: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.280: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.280: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.281: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.281: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.281: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.281: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.281: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.281: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.281: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.281: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.282: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.282: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.282: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.282: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.282: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.282: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.282: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.282: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.283: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.283: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.283: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.283: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.283: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.283: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.283: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.283: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.284: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.284: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.284: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.284: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.284: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.284: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.284: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.284: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.285: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.285: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.285: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.285: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.285: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.285: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.285: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.285: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.286: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.286: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.286: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.286: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.286: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.286: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.286: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.286: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.287: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.287: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.287: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.287: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.287: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.287: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.287: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.287: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.288: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.288: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.288: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.288: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.288: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.288: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.288: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.288: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.289: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.289: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.289: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.289: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.289: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.289: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.289: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.289: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.290: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.290: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.290: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.290: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.290: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.290: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.290: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.290: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.291: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.291: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.291: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.291: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.291: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.291: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.291: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.291: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.291: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.291: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.291: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.291: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.291: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.291: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.292: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.292: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.292: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.292: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.292: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.292: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.292: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.292: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.293: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.293: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.293: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.293: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.293: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.293: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.293: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.293: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.294: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.294: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.294: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.294: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.294: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.294: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.294: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.294: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.295: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.295: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.295: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.295: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.295: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.295: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.295: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.295: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.295: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.296: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.296: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.296: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.296: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.296: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.296: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.296: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.296: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.296: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.297: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.297: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.297: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.297: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.297: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.297: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.297: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.297: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.298: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.298: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.298: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.298: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.298: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.298: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.298: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.298: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.299: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.299: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.299: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.299: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.299: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.299: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.299: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.299: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.300: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.300: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.300: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.300: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.300: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.300: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.300: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.300: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.301: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.301: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.301: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.301: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.301: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.301: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.301: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.301: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.302: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.302: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.302: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.302: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.302: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.302: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.302: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.302: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.303: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.303: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.303: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.303: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.303: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.303: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.303: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.303: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.304: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.304: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.304: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.304: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.304: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.304: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.304: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.304: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.305: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.305: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.305: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.305: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.305: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.305: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.305: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.305: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.306: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.306: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.306: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.306: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.306: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.306: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.306: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.306: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.307: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.307: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.307: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.307: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.307: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.307: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.307: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.307: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.308: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.308: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.308: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.308: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.308: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.308: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.308: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.308: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.309: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.309: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.309: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.309: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.309: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.309: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.309: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.309: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.310: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.310: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.310: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.310: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.310: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.310: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.310: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.310: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.310: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.310: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.310: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.310: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.310: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.310: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.311: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.311: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.311: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.311: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.311: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.311: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.311: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.311: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.312: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.312: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.312: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.312: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.312: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.312: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.312: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.312: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.313: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.313: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.313: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.313: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.313: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.313: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.313: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.313: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.314: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.314: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.314: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.314: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.314: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.314: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.314: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.314: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.315: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.315: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.315: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.315: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.315: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.315: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.315: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.315: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.316: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.316: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.316: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.316: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.316: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.316: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.316: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.316: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.317: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.317: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.317: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.317: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.317: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.317: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.317: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.317: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.318: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.318: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.318: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.318: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.318: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.318: [vfs7552] CAPTURE_NUM_STATES entering state 2 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.318: [vfs7552] REQUEST CHUNK entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.318: Sending vfs7552_read_image_chunk 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.318: [vfs7552] REQUEST CHUNK completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.318: [vfs7552] CAPTURE_NUM_STATES entering state 3 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.319: [vfs7552] CAPTURE_NUM_STATES entering state 2 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.319: [vfs7552] REQUEST CHUNK entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.319: Sending vfs7552_read_image_chunk 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.319: [vfs7552] REQUEST CHUNK completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.319: [vfs7552] CAPTURE_NUM_STATES entering state 3 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.320: [vfs7552] CAPTURE_NUM_STATES entering state 2 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.320: [vfs7552] REQUEST CHUNK entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.320: Sending vfs7552_read_image_chunk 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.320: [vfs7552] REQUEST CHUNK completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.320: [vfs7552] CAPTURE_NUM_STATES entering state 3 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.321: [vfs7552] CAPTURE_NUM_STATES entering state 4 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.321: Cleaning image 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.321: variance_after = 2168 183s 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.321: [vfs7552] CAPTURE_NUM_STATES completed successfully 183s (process:2314): libfprint-device-DEBUG: 16:48:20.321: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 183s (process:2314): libfprint-image_device-DEBUG: 16:48:20.321: Image device reported finger status: on 183s (process:2314): libfprint-image_device-DEBUG: 16:48:20.321: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.371: changing to 2 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.371: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.371: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.371: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.372: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.372: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.372: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.372: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.372: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.372: [vfs7552] CAPTURE_NUM_STATES entering state 2 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.372: [vfs7552] REQUEST CHUNK entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.372: Sending vfs7552_read_image_chunk 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.373: [vfs7552] REQUEST CHUNK completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.373: [vfs7552] CAPTURE_NUM_STATES entering state 3 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.373: [vfs7552] CAPTURE_NUM_STATES entering state 2 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.373: [vfs7552] REQUEST CHUNK entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.373: Sending vfs7552_read_image_chunk 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.373: [vfs7552] REQUEST CHUNK completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.373: [vfs7552] CAPTURE_NUM_STATES entering state 3 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.374: [vfs7552] CAPTURE_NUM_STATES entering state 2 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.374: [vfs7552] REQUEST CHUNK entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.374: Sending vfs7552_read_image_chunk 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.374: [vfs7552] REQUEST CHUNK completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.374: [vfs7552] CAPTURE_NUM_STATES entering state 3 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.375: [vfs7552] CAPTURE_NUM_STATES entering state 4 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.375: Cleaning image 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.375: variance_after = 2082 183s 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.375: [vfs7552] CAPTURE_NUM_STATES completed successfully 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.375: Image captured 183s (process:2314): libfprint-image_device-DEBUG: 16:48:20.375: Image device captured an image 183s (process:2314): libfprint-image_device-DEBUG: 16:48:20.375: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 183s (process:2314): libfprint-device-DEBUG: 16:48:20.375: Device reported finger status change: FP_FINGER_STATUS_PRESENT 183s (process:2314): libfprint-image-DEBUG: 16:48:20.392: Minutiae scan completed in 0.016598 secs 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.425: changing to 3 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.425: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.425: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.425: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.426: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.426: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.426: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.426: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.426: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.426: [vfs7552] CAPTURE_NUM_STATES entering state 2 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.426: [vfs7552] REQUEST CHUNK entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.426: Sending vfs7552_read_image_chunk 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.427: [vfs7552] REQUEST CHUNK completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.427: [vfs7552] CAPTURE_NUM_STATES entering state 3 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.427: [vfs7552] CAPTURE_NUM_STATES entering state 2 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.427: [vfs7552] REQUEST CHUNK entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.427: Sending vfs7552_read_image_chunk 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.428: [vfs7552] REQUEST CHUNK completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.428: [vfs7552] CAPTURE_NUM_STATES entering state 3 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.428: [vfs7552] CAPTURE_NUM_STATES entering state 2 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.428: [vfs7552] REQUEST CHUNK entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.428: Sending vfs7552_read_image_chunk 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.429: [vfs7552] REQUEST CHUNK completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.429: [vfs7552] CAPTURE_NUM_STATES entering state 3 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.429: [vfs7552] CAPTURE_NUM_STATES entering state 4 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.429: Cleaning image 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.429: variance_after = 2003 183s 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.429: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.429: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.429: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.430: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.430: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.430: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.430: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.430: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.430: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.430: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.430: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.431: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.431: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.431: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.431: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.431: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.431: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.431: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.431: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.432: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.432: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.432: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.432: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.432: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.432: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.432: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.432: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.433: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.433: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.433: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.433: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.433: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.433: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.433: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.433: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.434: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.434: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.434: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.434: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.434: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.434: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.434: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.434: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.435: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.435: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.436: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.436: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.436: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.436: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.436: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.436: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.436: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.436: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.437: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.437: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.437: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.437: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.437: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.437: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.437: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.437: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.438: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.438: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.438: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.438: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.438: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.438: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.438: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.438: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.439: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.439: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.439: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.439: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.439: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.439: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.439: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.439: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.440: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.440: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.440: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.440: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.440: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.440: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.440: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.440: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.441: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.441: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.441: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.441: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.441: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.441: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.441: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.441: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.442: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.442: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.442: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.442: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.442: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.442: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.442: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.442: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.443: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.443: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.443: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.443: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.443: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.443: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.443: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.443: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.444: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.444: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.444: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.444: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.444: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.444: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.444: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.444: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.445: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.445: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.445: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.445: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.445: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.445: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.445: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.445: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.446: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.446: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.446: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.446: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.446: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.446: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.446: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.446: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.447: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.447: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.447: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.447: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.447: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.447: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.447: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.447: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.448: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.448: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.448: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.448: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.448: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.448: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.448: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.448: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.449: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.449: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.449: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.449: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.449: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.449: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.449: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.449: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.450: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.450: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.450: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.450: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.450: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.450: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.450: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.450: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.451: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.451: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.451: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.451: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.451: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.451: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.451: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.451: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.452: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.452: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.452: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.452: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.452: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.452: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.452: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.452: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.453: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.453: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.453: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.453: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.453: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.453: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.453: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.453: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.454: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.454: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.454: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.454: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.454: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.454: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.454: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.455: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.455: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.455: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.455: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.455: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.455: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.455: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.456: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.456: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.456: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.456: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.456: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.456: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.456: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.456: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.457: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.457: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.457: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.457: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.457: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.457: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.457: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.457: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.458: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.458: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.458: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.458: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.458: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.458: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.458: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.458: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.459: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.459: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.459: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.459: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.459: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.459: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.459: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.459: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.460: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.460: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.460: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.460: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.460: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.460: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.460: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.460: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.461: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.461: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.461: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.461: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.461: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.461: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.461: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.461: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.462: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.462: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.462: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.462: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.462: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.462: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.462: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.462: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.463: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.463: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.463: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.463: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.463: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.463: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.463: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.463: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.464: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.464: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.464: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.464: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.464: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.464: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.464: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.464: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.465: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.465: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.465: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.465: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.465: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.465: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.465: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.465: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.466: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.466: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.466: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.466: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.466: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.466: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.466: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.466: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.467: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.467: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.467: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.467: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.467: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.467: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.467: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.467: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.468: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.468: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.468: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.468: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.468: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.468: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.468: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.468: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.469: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.469: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.469: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.469: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.469: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.469: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.469: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.469: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.470: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.470: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.470: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.470: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.470: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.470: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.470: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.470: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.471: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.471: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.471: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.471: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.471: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.471: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.471: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.471: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.472: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.472: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.472: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.472: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.472: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.472: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.472: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.472: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.473: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.473: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.473: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.473: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.473: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.473: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.473: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.473: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.474: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.474: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.474: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.474: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.474: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.474: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.474: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.474: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.475: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.475: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.476: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.476: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.476: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.476: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.476: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.476: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.476: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.476: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.477: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.477: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.477: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.477: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.477: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.477: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.477: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.477: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.478: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.478: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.478: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.478: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.478: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.478: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.478: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.478: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.479: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.479: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.479: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.479: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.479: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.479: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.479: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.479: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.480: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.480: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.480: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.480: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.480: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.480: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.480: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.480: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.480: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.480: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.480: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.480: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.480: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.481: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.481: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.481: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.481: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.481: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.482: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.482: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.482: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.482: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.482: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.482: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.482: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.482: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.482: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.482: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.482: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.482: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.483: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.483: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.483: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.483: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.483: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.483: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.483: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.483: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.484: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.484: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.484: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.484: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.484: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.484: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.484: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.484: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.485: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.485: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.485: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.485: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.485: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.485: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.485: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.485: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.486: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.486: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.486: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.486: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.486: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.486: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.486: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.486: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.487: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.487: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.487: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.487: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.487: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.487: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.487: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.487: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.488: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.488: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.488: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.488: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.488: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.488: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.488: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.488: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.489: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.489: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.489: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.489: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.489: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.489: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.489: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.489: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.489: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.489: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.490: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.490: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.490: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.490: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.490: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.490: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.490: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.490: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.491: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.491: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.491: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.491: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.491: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.491: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.491: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.491: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.492: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.492: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.492: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.492: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.492: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.492: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.492: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.492: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.493: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.493: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.493: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.493: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.493: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.493: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.493: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.493: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.494: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.494: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.494: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.494: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.494: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.494: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.494: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.494: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.495: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.495: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.495: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.495: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.495: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.495: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.495: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.495: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.496: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.496: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.496: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.496: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.496: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.496: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.496: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.496: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.496: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.497: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.497: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.497: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.497: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.497: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.497: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.497: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.497: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.497: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.497: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.497: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.497: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.497: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.498: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.498: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.498: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.498: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.498: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.498: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.498: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.498: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.499: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.499: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.499: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.499: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.499: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.499: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.499: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.499: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.500: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.500: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.500: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.500: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.500: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.500: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.500: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.500: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.501: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.501: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.501: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.501: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.501: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.501: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.501: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.501: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.502: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.502: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.502: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.502: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.502: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.502: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.502: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.502: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.503: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.503: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.503: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.503: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.503: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.503: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.503: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.503: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.504: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.504: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.504: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.504: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.504: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.504: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.504: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.504: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.505: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.505: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.505: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.505: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.505: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.505: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.505: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.505: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.506: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.506: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.506: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.506: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.506: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.506: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.506: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.506: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.507: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.507: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.507: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.507: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.507: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.507: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.507: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.507: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.508: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.508: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.508: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.508: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.508: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.508: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.508: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.508: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.509: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.509: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.509: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.509: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.509: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.509: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.509: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.509: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.509: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.509: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.510: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.510: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.510: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.510: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.510: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.510: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.510: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.510: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.511: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.511: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.511: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.511: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.511: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.511: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.511: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.511: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.512: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.512: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.512: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.512: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.512: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.512: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.512: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.512: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.513: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.513: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.513: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.513: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.513: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.513: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.513: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.513: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.514: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.514: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.514: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.514: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.514: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.514: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.514: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.514: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.515: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.515: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.515: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.515: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.515: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.515: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.515: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.515: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.516: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.516: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.516: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.516: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.516: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.516: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.516: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.516: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.517: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.517: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.517: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.517: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.517: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.517: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.517: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.517: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.518: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.518: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.518: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.518: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.518: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.518: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.518: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.518: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.519: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.519: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.519: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.519: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.519: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.519: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.519: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.519: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.520: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.520: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.520: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.520: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.520: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.520: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.520: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.521: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.521: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.521: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.521: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.521: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.521: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.521: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.521: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.521: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.522: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.522: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.522: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.522: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.522: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.522: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.522: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.522: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.523: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.523: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.523: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.523: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.523: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.523: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.523: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.523: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.524: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.524: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.524: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.524: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.524: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.524: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.524: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.524: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.525: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.525: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.525: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.525: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.525: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.525: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.525: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.525: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.526: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.526: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.526: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.526: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.526: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.526: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.526: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.526: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.527: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.527: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.527: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.527: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.527: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.527: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.527: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.527: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.528: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.528: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.528: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.528: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.528: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.528: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.528: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.528: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.529: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.529: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.529: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.529: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.529: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.529: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.529: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.529: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.529: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.529: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.529: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.529: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.529: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.529: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.530: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.530: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.530: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.530: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.530: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.530: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.530: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.530: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.531: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.531: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.531: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.531: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.531: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.531: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.531: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.531: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.532: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.532: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.532: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.532: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.532: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.532: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.532: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.532: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.533: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.533: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.533: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.533: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.533: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.533: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.533: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.533: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.534: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.534: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.534: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.534: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.534: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.534: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.534: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.534: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.535: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.535: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.535: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.535: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.535: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.535: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.535: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.535: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.536: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.536: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.536: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.536: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.536: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.536: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.536: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.536: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.537: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.537: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.537: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.537: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.537: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.537: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.537: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.537: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.538: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.538: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.538: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.538: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.538: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.538: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.538: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.538: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.539: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.539: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.539: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.539: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.539: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.539: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.539: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.539: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.540: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.540: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.540: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.540: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.540: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.540: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.540: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.540: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.541: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.541: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.541: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.541: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.541: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.541: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.541: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.541: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.542: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.542: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.542: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.542: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.542: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.542: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.542: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.542: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.543: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.543: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.543: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.543: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.543: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.543: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.543: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.543: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.544: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.544: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.544: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.544: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.544: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.544: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.544: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.544: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.545: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.545: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.545: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.545: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.545: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.545: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.545: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.545: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.546: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.546: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.546: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.546: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.546: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.546: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.546: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.546: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.546: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.546: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.547: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.547: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.547: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.547: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.547: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.547: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.547: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.547: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.548: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.548: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.548: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.548: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.548: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.548: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.548: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.548: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.549: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.549: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.549: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.549: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.549: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.549: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.549: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.549: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.550: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.550: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.550: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.550: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.550: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.550: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.550: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.550: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.551: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.551: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.551: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.551: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.551: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.551: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.551: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.551: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.552: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.552: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.552: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.552: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.552: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.552: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.552: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.552: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.553: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.553: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.553: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.553: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.553: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.553: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.553: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.553: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.554: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.554: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.554: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.554: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.554: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.554: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.554: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.554: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.555: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.555: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.555: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.555: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.555: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.555: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.555: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.555: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.556: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.556: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.556: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.556: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.556: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.556: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.556: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.556: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.557: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.557: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.557: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.557: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.557: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.557: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.557: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.557: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.558: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.558: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.558: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.558: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.558: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.558: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.558: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.558: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.559: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.559: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.559: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.559: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.559: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.559: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.559: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.559: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.560: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.560: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.560: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.560: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.560: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.560: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.560: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.560: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.561: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.561: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.561: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.561: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.561: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.561: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.561: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.561: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.562: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.562: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.562: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.562: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.562: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.562: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.562: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.562: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.563: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.563: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.563: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.563: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.563: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.563: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.563: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.563: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.564: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.564: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.564: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.564: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.564: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.564: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.564: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.564: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.565: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.565: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.565: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.565: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.565: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.565: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.565: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.565: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.566: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.566: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.566: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.566: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.566: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.566: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.566: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.566: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.567: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.567: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.567: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.567: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.567: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.567: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.567: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.567: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.568: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.568: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.568: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.568: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.568: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.568: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.568: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.568: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.569: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.569: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.569: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.569: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.569: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.569: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.569: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.569: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.570: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.570: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.570: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.570: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.570: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.570: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.570: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.570: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.571: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.571: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.571: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.571: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.571: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.571: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.571: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.571: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.572: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.572: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.572: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.572: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.572: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.572: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.572: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.572: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.573: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.573: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.573: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.573: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.573: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.573: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.573: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.573: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.574: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.574: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.574: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.574: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.574: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.574: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.574: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.574: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.575: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.575: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.575: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.575: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.575: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.575: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.575: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.575: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.576: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.576: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.576: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.576: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.576: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.576: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.576: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.576: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.577: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.577: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.577: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.577: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.577: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.577: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.577: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.577: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.578: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.578: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.578: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.578: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.578: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.578: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.578: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.578: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.579: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.579: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.579: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.579: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.579: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.579: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.579: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.579: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.579: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.579: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.580: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.580: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.580: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.580: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.580: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.580: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.580: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.580: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.580: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.580: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.580: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.581: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.581: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.581: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.581: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.581: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.582: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.582: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.582: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.582: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.582: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.582: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.582: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.582: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.582: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.582: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.582: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.582: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.583: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.583: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.583: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.583: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.583: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.583: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.583: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.583: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.584: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.584: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.584: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.584: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.584: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.584: [vfs7552] CAPTURE_NUM_STATES entering state 2 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.584: [vfs7552] REQUEST CHUNK entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.584: Sending vfs7552_read_image_chunk 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.585: [vfs7552] REQUEST CHUNK completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.585: [vfs7552] CAPTURE_NUM_STATES entering state 3 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.585: [vfs7552] CAPTURE_NUM_STATES entering state 2 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.585: [vfs7552] REQUEST CHUNK entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.585: Sending vfs7552_read_image_chunk 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.586: [vfs7552] REQUEST CHUNK completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.586: [vfs7552] CAPTURE_NUM_STATES entering state 3 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.586: [vfs7552] CAPTURE_NUM_STATES entering state 2 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.586: [vfs7552] REQUEST CHUNK entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.586: Sending vfs7552_read_image_chunk 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.587: [vfs7552] REQUEST CHUNK completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.587: [vfs7552] CAPTURE_NUM_STATES entering state 3 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.587: [vfs7552] CAPTURE_NUM_STATES entering state 4 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.587: Cleaning image 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.587: variance_after = 1737 183s 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.587: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.587: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.587: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.588: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.588: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.589: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.589: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.589: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.589: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.589: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.589: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.589: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.589: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.590: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.590: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.590: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.590: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.590: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.590: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.590: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.590: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.591: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.591: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.591: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.591: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.591: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.591: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.591: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.591: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.591: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.591: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.592: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.592: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.592: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.592: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.592: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.592: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.592: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.592: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.592: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.592: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.592: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.592: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.593: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.593: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.593: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.593: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.593: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.593: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.593: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.593: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.594: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.594: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.594: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.594: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.594: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.594: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.594: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.594: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.595: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.595: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.595: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.595: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.595: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.595: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.595: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.595: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.596: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.596: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.596: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.596: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.596: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.596: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.596: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.596: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.597: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.597: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.597: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.597: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.597: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.597: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.597: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.597: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.598: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.598: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.598: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.598: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.598: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.598: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.598: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.598: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.599: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.599: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.599: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.599: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.599: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.599: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.599: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.599: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.600: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.600: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.600: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.600: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.600: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.600: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.600: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.600: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.601: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.601: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.601: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.601: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.601: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.601: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.601: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.601: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.602: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.602: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.602: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.602: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.602: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.602: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.602: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.602: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.602: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.603: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.603: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.603: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.603: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.603: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.603: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.603: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.603: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.603: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.604: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.604: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.604: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.604: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.604: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.604: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.604: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.604: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.605: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.605: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.605: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.605: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.605: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.605: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.605: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.605: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.606: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.606: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.606: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.606: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.606: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.606: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.606: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.606: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.607: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.607: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.607: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.607: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.607: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.607: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.607: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.607: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.608: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.608: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.608: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.608: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.608: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.608: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.608: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.608: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.609: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.609: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.609: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.609: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.609: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.609: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.609: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.609: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.610: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.610: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.610: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.610: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.610: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.610: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.610: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.610: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.611: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.611: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.611: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.611: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.611: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.611: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.611: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.611: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.612: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.612: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.612: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.612: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.612: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.612: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.612: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.612: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.612: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.613: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.613: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.613: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.613: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.613: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.613: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.613: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.613: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.613: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.614: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.614: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.614: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.614: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.614: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.614: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.614: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.614: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.614: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.614: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.614: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.614: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.615: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.615: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.616: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.616: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.616: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.616: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.616: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.616: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.616: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.616: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.616: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.616: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.616: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.616: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.616: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.616: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.617: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.617: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.617: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.618: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.618: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.618: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.618: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.618: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.618: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.618: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.618: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.618: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.618: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.618: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.619: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.619: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.619: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.619: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.619: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.620: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.620: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.620: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.620: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.620: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.620: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.620: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.620: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.620: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.620: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.620: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.620: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.620: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.621: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.621: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.621: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.621: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.621: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.621: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.621: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.621: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.622: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.622: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.622: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.622: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.622: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.622: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.622: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.622: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.623: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.623: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.623: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.623: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.623: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.623: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.623: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.623: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.624: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.624: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.624: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.624: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.624: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.624: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.624: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.624: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.625: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.625: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.625: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.625: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.625: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.625: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.625: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.625: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.626: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.626: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.626: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.626: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.626: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.626: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.626: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.626: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.627: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.627: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.627: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.627: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.627: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.627: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.627: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.627: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.628: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.628: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.628: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.628: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.628: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.628: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.628: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.628: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.629: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.629: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.629: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.629: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.629: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.629: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.629: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.629: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.630: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.630: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.630: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.630: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.630: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.630: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.630: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.630: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.631: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.631: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.631: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.631: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.631: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.631: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.631: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.631: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.632: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.632: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.632: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.632: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.632: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.632: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.632: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.632: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.632: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.632: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.633: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.633: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.633: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.633: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.633: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.633: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.633: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.633: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.634: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.634: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.634: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.634: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.634: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.634: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.634: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.634: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.635: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.635: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.635: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.635: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.635: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.635: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.635: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.635: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.636: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.636: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.636: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.636: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.636: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.636: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.636: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.636: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.637: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.637: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.637: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.637: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.637: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.637: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.637: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.637: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.638: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.638: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.638: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.638: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.638: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.638: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.638: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.638: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.639: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.639: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.639: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.639: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.639: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.639: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.639: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.639: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.640: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.640: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.640: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.640: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.640: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.640: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.640: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.640: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.641: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.641: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.641: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.641: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.641: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.641: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.641: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.641: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.642: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.642: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.642: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.642: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.642: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.642: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.642: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.642: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.643: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.643: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.643: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.643: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.643: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.643: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.643: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.643: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.644: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.644: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.644: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.644: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.644: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.644: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.644: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.644: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.645: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.645: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.645: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.645: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.645: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.645: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.645: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.645: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.646: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.646: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.646: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.646: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.646: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.646: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.646: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.646: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.646: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.647: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.647: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.647: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.647: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.647: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.647: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.647: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.647: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.647: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.647: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.648: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.648: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.648: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.648: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.648: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.648: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.648: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.648: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.648: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.649: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.649: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.649: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.649: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.649: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.649: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.649: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.649: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.649: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.649: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.650: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.650: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.650: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.650: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.650: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.650: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.650: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.650: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.651: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.651: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.651: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.651: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.651: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.651: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.651: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.651: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.652: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.652: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.652: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.652: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.652: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.652: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.652: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.652: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.653: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.653: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.653: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.653: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.653: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.653: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.653: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.653: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.654: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.654: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.654: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.654: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.654: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.654: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.654: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.654: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.655: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.655: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.655: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.655: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.655: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.655: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.655: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.655: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.656: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.656: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.656: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.656: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.656: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.656: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.656: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.656: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.656: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.657: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.657: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.657: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.657: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.657: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.657: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.657: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.657: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.658: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.658: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.658: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.658: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.658: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.658: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.658: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.658: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.658: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.659: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.659: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.659: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.659: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.659: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.659: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.659: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.659: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.660: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.660: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.660: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.660: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.660: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.660: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.660: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.660: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.661: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.661: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.661: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.661: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.661: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.661: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.661: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.661: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.662: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.662: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.662: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.662: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.662: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.662: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.662: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.662: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.663: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.663: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.663: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.663: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.663: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.663: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.663: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.663: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.664: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.664: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.664: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.664: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.664: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.664: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.664: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.664: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.665: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.665: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.665: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.665: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.665: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.665: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.665: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.665: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.666: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.666: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.666: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.666: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.666: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.666: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.666: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.666: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.667: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.667: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.667: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.667: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.667: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.667: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.667: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.667: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.668: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.668: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.668: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.668: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.668: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.668: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.668: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.668: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.669: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.669: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.669: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.669: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.669: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.669: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.669: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.669: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.670: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.670: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.670: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.670: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.670: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.670: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.670: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.670: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.671: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.671: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.671: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.671: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.671: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.671: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.671: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.671: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.671: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.672: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.672: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.672: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.672: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.672: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.672: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.672: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.673: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.673: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.673: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.673: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.673: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.673: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.673: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.673: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.673: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.673: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.673: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.673: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.673: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.673: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.674: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.674: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.674: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.674: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.674: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.674: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.674: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.674: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.675: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.675: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.675: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.675: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.675: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.675: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.675: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.675: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.676: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.676: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.676: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.676: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.676: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.676: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.676: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.676: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.677: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.677: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.677: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.677: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.677: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.677: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.677: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.677: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.678: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.678: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.678: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.678: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.678: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.678: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.678: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.678: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.679: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.679: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.679: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.679: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.679: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.679: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.679: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.679: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.680: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.680: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.680: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.680: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.680: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.680: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.680: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.680: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.681: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.681: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.681: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.681: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.681: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.681: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.681: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.681: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.682: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.682: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.682: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.682: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.682: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.682: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.682: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.682: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.683: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.683: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.683: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.683: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.683: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.683: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.683: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.683: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.684: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.684: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.684: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.684: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.684: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.684: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.684: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.684: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.685: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.685: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.685: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.685: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.685: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.685: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.685: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.685: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.686: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.686: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.686: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.686: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.686: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.686: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.686: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.686: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.687: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.687: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.687: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.687: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.687: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.687: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.687: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.687: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.688: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.688: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.688: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.688: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.688: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.688: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.688: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.688: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.689: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.689: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.689: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.689: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.689: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.689: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.689: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.689: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.690: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.690: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.690: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.690: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.690: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.690: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.690: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.690: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.691: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.691: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.691: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.691: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.691: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.691: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.691: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.691: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.692: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.692: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.692: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.692: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.692: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.692: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.692: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.692: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.693: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.693: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.693: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.693: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.693: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.693: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.693: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.693: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.694: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.694: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.694: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.694: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.694: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.694: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.694: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.694: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.694: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.695: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.695: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.695: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.695: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.695: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.695: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.695: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.695: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.696: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.696: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.696: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.696: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.696: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.696: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.696: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.696: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.696: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.697: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.697: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.697: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.697: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.697: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.697: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.697: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.697: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.698: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.698: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.698: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.698: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.698: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.698: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.698: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.698: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.699: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.699: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.699: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.699: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.699: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.699: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.699: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.699: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.700: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.700: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.700: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.700: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.700: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.700: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.700: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.700: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.701: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.701: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.701: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.701: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.701: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.701: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.701: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.701: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.702: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.702: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.702: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.702: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.702: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.702: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.702: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.702: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.703: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.703: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.703: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.703: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.703: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.703: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.703: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.703: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.704: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.704: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.704: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.704: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.704: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.704: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.704: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.704: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.704: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.705: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.705: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.705: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.705: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.705: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.705: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.705: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.705: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.705: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.705: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.705: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.705: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.705: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.706: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.706: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.706: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.706: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.706: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.706: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.706: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.706: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.707: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.707: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.707: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.707: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.707: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.707: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.707: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.707: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.708: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.708: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.708: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.708: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.708: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.708: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.708: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.708: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.709: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.709: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.709: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.709: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.709: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.709: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.709: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.709: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.710: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.710: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.710: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.710: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.710: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.710: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.710: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.710: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.711: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.711: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.711: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.711: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.711: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.711: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.711: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.711: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.712: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.712: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.712: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.712: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.712: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.712: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.712: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.712: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.712: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.713: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.713: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.713: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.713: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.713: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.713: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.713: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.713: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.713: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.714: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.714: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.714: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.714: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.714: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.714: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.714: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.714: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.715: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.715: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.715: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.715: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.715: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.715: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.715: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.715: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.716: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.716: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.716: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.716: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.716: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.716: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.716: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.716: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.717: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.717: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.717: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.717: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.717: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.717: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.717: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.717: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.718: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.718: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.718: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.718: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.718: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.718: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.718: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.718: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.719: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.719: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.719: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.719: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.719: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.719: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.719: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.719: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.720: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.720: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.720: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.720: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.720: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.720: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.720: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.720: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.721: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.721: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.721: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.721: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.721: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.721: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.721: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.721: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.722: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.722: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.722: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.722: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.722: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.722: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.722: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.722: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.723: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.723: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.723: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.723: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.723: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.723: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.723: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.723: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.724: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.724: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.724: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.724: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.724: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.724: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.724: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.724: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.725: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.725: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.725: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.725: [vfs7552] CAPTURE_NUM_STATES entering state 2 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.725: [vfs7552] REQUEST CHUNK entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.725: Sending vfs7552_read_image_chunk 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.725: [vfs7552] REQUEST CHUNK completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.725: [vfs7552] CAPTURE_NUM_STATES entering state 3 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.726: [vfs7552] CAPTURE_NUM_STATES entering state 2 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.726: [vfs7552] REQUEST CHUNK entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.726: Sending vfs7552_read_image_chunk 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.726: [vfs7552] REQUEST CHUNK completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.726: [vfs7552] CAPTURE_NUM_STATES entering state 3 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.727: [vfs7552] CAPTURE_NUM_STATES entering state 2 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.727: [vfs7552] REQUEST CHUNK entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.727: Sending vfs7552_read_image_chunk 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.727: [vfs7552] REQUEST CHUNK completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.727: [vfs7552] CAPTURE_NUM_STATES entering state 3 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.728: [vfs7552] CAPTURE_NUM_STATES entering state 4 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.728: Cleaning image 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.728: variance_after = 1526 183s 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.728: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.728: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.728: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.728: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.728: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.729: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.729: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.729: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.729: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.729: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.729: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.729: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.729: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.730: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.730: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.730: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.730: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.730: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.730: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.730: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.730: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.731: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.731: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.731: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.731: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.731: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.731: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.731: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.731: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.732: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.732: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.732: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.732: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.732: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.732: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.732: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.732: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.733: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.733: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.733: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.733: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.733: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.733: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.733: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.733: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.734: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.734: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.734: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.734: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.734: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.734: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.734: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.735: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.735: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.735: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.735: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.735: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.735: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.735: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.735: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.735: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.736: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.736: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.736: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.736: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.736: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.736: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.736: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.736: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.737: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.737: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.737: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.737: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.737: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.737: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.737: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.737: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.738: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.738: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.738: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.738: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.738: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.738: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.738: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.738: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.739: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.739: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.739: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.739: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.739: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.739: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.739: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.739: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.740: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.740: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.740: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.740: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.740: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.740: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.740: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.740: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.741: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.741: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.741: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.741: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.741: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.741: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.741: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.741: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.742: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.742: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.742: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.742: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.742: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.742: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.742: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.742: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.743: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.743: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.743: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.743: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.743: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.743: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.743: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.743: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.744: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.744: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.744: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.744: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.744: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.744: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.744: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.744: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.745: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.745: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.745: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.745: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.745: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.745: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.745: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.745: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.746: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.746: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.746: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.746: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.746: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.746: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.746: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.746: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.746: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.746: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.746: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.746: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.746: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.746: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.747: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.747: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.747: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.747: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.747: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.747: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.747: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.747: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.748: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.748: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.748: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.748: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.748: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.748: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.748: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.748: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.749: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.749: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.749: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.749: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.749: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.749: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.749: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.749: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.750: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.750: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.750: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.750: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.750: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.750: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.750: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.750: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.751: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.751: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.751: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.751: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.751: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.751: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.751: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.751: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.752: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.752: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.752: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.752: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.752: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.752: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.752: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.752: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.753: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.753: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.753: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.753: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.753: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.753: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.753: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.753: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.754: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.754: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.754: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.754: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.754: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.754: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.754: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.754: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.754: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.755: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.755: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.755: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.755: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.755: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.755: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.755: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.755: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.756: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.756: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.756: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.756: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.756: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.756: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.756: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.756: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.756: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.757: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.757: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.757: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.757: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.757: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.757: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.757: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.757: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.758: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.758: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.758: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.758: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.758: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.758: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.758: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.758: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.759: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.759: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.759: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.759: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.759: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.759: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.759: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.759: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.760: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.760: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.760: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.760: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.760: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.760: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.760: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.760: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.761: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.761: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.761: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.761: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.761: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.761: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.761: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.761: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.762: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.762: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.762: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.762: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.762: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.762: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.762: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.762: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.763: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.763: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.763: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.763: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.763: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.763: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.763: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.763: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.764: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.764: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.764: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.764: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.764: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.764: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.764: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.764: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.765: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.765: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.765: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.765: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.765: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.765: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.765: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.765: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.766: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.766: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.766: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.766: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.766: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.766: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.766: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.766: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.767: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.767: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.767: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.767: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.767: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.767: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.767: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.767: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.768: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.768: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.768: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.768: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.768: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.768: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.768: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.768: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.769: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.769: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.769: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.769: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.769: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.769: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.769: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.769: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.770: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.770: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.770: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.770: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.770: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.770: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.770: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.770: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.771: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.771: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.771: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.771: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.771: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.771: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.771: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.771: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.772: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.772: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.772: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.772: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.772: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.772: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.772: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.772: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.773: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.773: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.773: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.773: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.773: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.773: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.773: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.773: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.774: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.774: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.774: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.774: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.774: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.774: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.774: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.774: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.775: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.775: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.775: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.775: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.775: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.775: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.775: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.775: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.776: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.776: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.776: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.776: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.776: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.776: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.776: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.776: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.777: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.777: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.777: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.777: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.777: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.777: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.777: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.777: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.778: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.778: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.778: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.778: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.778: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.778: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.778: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.778: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.778: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.778: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.778: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.778: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.779: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.779: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.779: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.779: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.780: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.780: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.780: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.780: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.780: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.780: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.780: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.780: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.780: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.781: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.781: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.781: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.781: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.781: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.781: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.781: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.781: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.781: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.782: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.782: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.782: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.782: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.782: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.782: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.782: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.782: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.782: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.782: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.782: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.783: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.783: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.783: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.783: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.783: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.783: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.783: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.783: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.783: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.784: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.784: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.784: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.784: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.784: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.784: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.784: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.784: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.785: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.785: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.785: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.785: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.785: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.785: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.785: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.785: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.786: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.786: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.786: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.786: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.786: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.786: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.786: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.786: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.787: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.787: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.787: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.787: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.787: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.787: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.787: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.787: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.788: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.788: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.788: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.788: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.788: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.788: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.788: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.788: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.789: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.789: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.789: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.789: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.789: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.789: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.789: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.789: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.789: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.789: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.790: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.790: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.790: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.790: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.790: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.790: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.790: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.790: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.791: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.791: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.791: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.791: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.791: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.791: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.791: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.791: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.792: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.792: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.792: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.792: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.792: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.792: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.792: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.792: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.793: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.793: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.793: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.793: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.793: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.793: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.793: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.793: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.794: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.794: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.794: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.794: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.794: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.794: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.794: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.794: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.795: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.795: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.795: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.795: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.795: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.795: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.795: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.795: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.796: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.796: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.796: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.796: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.796: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.796: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.796: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.796: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.797: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.797: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.797: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.797: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.797: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.797: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.797: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.797: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.798: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.798: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.798: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.798: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.798: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.798: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.798: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.798: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.799: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.799: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.799: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.799: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.799: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.799: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.799: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.799: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.800: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.800: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.800: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.800: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.800: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.800: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.800: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.800: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.801: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.801: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.801: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.801: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.801: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.801: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.801: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.801: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.802: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.802: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.802: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.802: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.802: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.802: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.802: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.802: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.803: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.803: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.803: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.803: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.803: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.803: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.803: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.803: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.803: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.803: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.804: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.804: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.804: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.804: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.804: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.804: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.804: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.804: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.805: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.805: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.805: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.805: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.805: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.805: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.805: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.805: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.806: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.806: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.806: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.806: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.806: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.806: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.806: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.806: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.806: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.806: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.806: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.806: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.807: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.807: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.807: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.807: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.807: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.807: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.807: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.807: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.808: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.808: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.808: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.808: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.808: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.808: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.808: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.808: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.809: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.809: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.809: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.809: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.809: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.809: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.809: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.809: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.810: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.810: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.810: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.810: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.810: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.810: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.810: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.810: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.811: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.811: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.811: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.811: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.811: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.811: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.811: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.811: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.812: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.812: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.812: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.812: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.812: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.812: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.812: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.812: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.813: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.813: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.813: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.813: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.813: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.813: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.813: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.813: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.814: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.814: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.814: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.814: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.814: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.814: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.814: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.814: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.815: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.815: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.815: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.815: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.815: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.815: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.815: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.815: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.816: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.816: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.816: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.816: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.816: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.816: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.816: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.816: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.817: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.817: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.817: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.817: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.817: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.817: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.817: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.817: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.818: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.818: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.818: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.818: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.818: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.818: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.818: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.818: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.818: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.818: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.819: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.819: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.819: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.819: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.819: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.819: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.820: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.820: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.820: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.820: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.820: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.820: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.820: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.820: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.821: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.821: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.821: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.821: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.821: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.821: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.821: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.821: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.822: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.822: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.822: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.822: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.822: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.822: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.822: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.822: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.822: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.823: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.823: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.823: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.823: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.823: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.823: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.823: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.823: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.823: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.824: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.824: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.824: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.824: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.824: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.824: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.824: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.824: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.825: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.825: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.825: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.825: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.825: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.825: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.825: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.825: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.826: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.826: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.826: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.826: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.826: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.826: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.826: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.826: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.827: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.827: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.827: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.827: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.827: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.827: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.827: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.827: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.828: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.828: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.828: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.828: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.828: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.828: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.828: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.828: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.829: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.829: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.829: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.829: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.829: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.829: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.829: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.829: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.830: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.830: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.830: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.830: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.830: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.830: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.830: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.830: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.831: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.831: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.831: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.831: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.831: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.831: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.831: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.831: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.832: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.832: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.832: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.832: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.832: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.832: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.832: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.832: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.832: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.832: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.833: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.833: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.833: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.833: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.833: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.833: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.834: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.834: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.834: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.834: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.834: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.834: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.834: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.834: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.834: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.834: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.834: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.835: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.835: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.835: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.835: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.835: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.835: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.835: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.835: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.835: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.835: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.835: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.836: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.836: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.836: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.836: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.836: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.836: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.836: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.836: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.837: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.837: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.837: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.837: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.837: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.837: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.837: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.837: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.838: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.838: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.838: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.838: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.838: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.838: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.838: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.838: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.839: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.839: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.839: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.839: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.839: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.839: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.839: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.839: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.840: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.840: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.840: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.840: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.840: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.840: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.840: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.840: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.841: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.841: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.841: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.841: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.841: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.841: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.841: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.841: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.841: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.841: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.842: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.842: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.842: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.842: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.842: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.842: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.842: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.842: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.843: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.843: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.843: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.843: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.843: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.843: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.843: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.843: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.844: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.844: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.844: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.844: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.844: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.844: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.844: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.844: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.845: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.845: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.845: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.845: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.845: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.845: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.845: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.845: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.846: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.846: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.846: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.846: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.846: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.846: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.846: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.846: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.847: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.847: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.847: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.847: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.847: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.847: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.847: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.847: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.848: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.848: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.848: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.848: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.848: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.848: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.848: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.848: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.849: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.849: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.849: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.849: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.849: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.849: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.849: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.849: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.850: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.850: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.850: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.850: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.850: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.850: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.850: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.850: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.851: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.851: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.851: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.851: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.851: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.851: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.851: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.851: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.852: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.852: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.852: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.852: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.852: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.852: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.852: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.852: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.852: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.852: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.852: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.853: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.853: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.853: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.853: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.853: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.854: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.854: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.854: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.854: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.854: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.854: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.854: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.854: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.854: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.855: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.855: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.855: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.855: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.855: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.855: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.855: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.855: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.855: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.855: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.856: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.856: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.856: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.856: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.856: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.856: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.856: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.856: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.856: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.856: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.856: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.857: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.857: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.857: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.857: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.857: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.857: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.857: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.858: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.858: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.858: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.858: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.858: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.858: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.858: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.858: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.858: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.859: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.859: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.859: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.859: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.859: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.859: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.859: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.859: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.860: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.860: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.860: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.860: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.860: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.861: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.861: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.861: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.861: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.861: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.861: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.861: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.862: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.862: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.862: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.862: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.862: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.862: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.862: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.862: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.862: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.863: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.863: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.863: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.863: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.863: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.863: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.863: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.863: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.863: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.863: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.863: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.864: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.864: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.864: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.864: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.864: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.864: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.864: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.864: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.865: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.865: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.865: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.865: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.865: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.865: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.865: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.865: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.866: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.866: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.866: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.866: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.866: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.866: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.866: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.866: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.867: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.867: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.867: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.867: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.867: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.867: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.867: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.868: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.868: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.868: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.868: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.869: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.869: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.869: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.869: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.869: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.869: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.869: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.870: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.870: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.870: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.870: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.870: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.870: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.870: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.870: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.871: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.871: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.871: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.871: [vfs7552] CAPTURE_NUM_STATES entering state 2 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.871: [vfs7552] REQUEST CHUNK entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.871: Sending vfs7552_read_image_chunk 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.871: [vfs7552] REQUEST CHUNK completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.871: [vfs7552] CAPTURE_NUM_STATES entering state 3 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.872: [vfs7552] CAPTURE_NUM_STATES entering state 2 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.872: [vfs7552] REQUEST CHUNK entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.872: Sending vfs7552_read_image_chunk 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.872: [vfs7552] REQUEST CHUNK completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.872: [vfs7552] CAPTURE_NUM_STATES entering state 3 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.873: [vfs7552] CAPTURE_NUM_STATES entering state 2 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.873: [vfs7552] REQUEST CHUNK entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.873: Sending vfs7552_read_image_chunk 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.873: [vfs7552] REQUEST CHUNK completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.873: [vfs7552] CAPTURE_NUM_STATES entering state 3 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.874: [vfs7552] CAPTURE_NUM_STATES entering state 4 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.874: Cleaning image 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.874: variance_after = 1435 183s 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.874: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.874: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.874: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.874: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.874: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.875: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.875: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.875: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.875: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.875: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.875: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.875: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.875: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.876: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.876: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.876: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.876: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.876: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.876: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.876: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.876: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.877: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.877: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.877: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.877: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.877: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.877: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.877: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.877: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.878: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.878: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.878: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.878: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.878: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.878: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.878: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.878: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.879: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.879: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.879: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.879: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.879: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.879: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.879: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.879: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.880: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.880: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.880: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.880: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.880: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.880: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.880: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.880: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.880: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.880: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.881: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.881: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.881: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.881: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.881: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.881: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.882: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.882: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.882: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.882: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.882: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.882: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.882: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.882: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.882: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.882: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.882: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.882: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.882: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.882: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.883: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.883: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.883: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.883: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.883: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.883: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.883: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.883: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.884: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.884: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.884: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.884: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.884: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.884: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.884: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.884: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.885: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.885: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.885: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.885: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.885: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.885: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.885: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.885: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.886: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.886: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.886: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.886: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.886: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.886: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.886: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.886: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.887: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.887: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.887: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.887: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.887: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.887: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.887: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.887: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.888: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.888: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.888: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.888: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.888: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.888: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.888: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.888: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.889: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.889: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.889: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.889: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.889: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.889: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.889: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.889: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.890: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.890: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.890: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.890: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.890: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.890: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.890: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.890: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.891: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.891: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.891: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.891: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.891: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.891: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.891: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.891: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.892: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.892: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.892: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.892: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.892: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.892: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.892: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.892: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.892: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.892: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.893: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.893: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.893: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.893: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.893: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.893: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.893: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.893: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.894: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.894: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.894: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.894: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.894: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.894: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.894: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.894: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.895: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.895: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.895: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.895: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.895: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.895: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.895: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.895: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.896: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.896: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.896: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.896: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.896: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.896: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.896: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.896: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.897: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.897: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.897: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.897: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.897: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.897: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.897: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.897: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.898: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.898: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.898: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.898: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.898: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.898: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.898: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.898: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.899: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.899: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.899: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.899: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.899: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.899: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.899: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.899: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.900: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.900: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.900: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.900: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.900: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.900: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.900: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.900: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.901: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.901: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.901: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.901: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.901: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.901: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.901: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.901: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.902: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.902: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.902: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.902: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.902: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.902: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.902: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.902: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.903: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.903: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.903: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.903: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.903: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.903: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.903: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.903: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.904: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.904: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.904: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.904: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.904: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.904: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.904: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.904: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.905: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.905: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.905: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.905: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.905: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.905: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.905: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.905: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.906: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.906: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.906: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.906: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.906: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.906: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.906: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.906: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.907: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.907: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.907: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.907: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.907: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.907: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.907: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.907: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.908: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.908: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.908: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.908: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.908: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.908: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.908: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.908: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.909: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.909: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.909: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.909: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.909: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.909: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.909: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.909: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.910: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.910: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.910: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.910: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.910: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.910: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.910: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.910: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.911: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.911: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.911: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.911: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.911: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.911: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.911: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.911: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.912: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.912: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.912: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.912: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.912: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.912: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.912: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.912: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.913: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.913: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.913: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.913: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.913: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.913: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.913: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.913: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.914: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.914: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.914: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.914: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.914: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.914: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.914: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.914: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.915: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.915: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.915: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.915: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.915: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.915: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.915: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.915: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.916: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.916: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.916: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.916: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.916: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.916: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.916: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.916: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.917: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.917: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.917: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.917: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.917: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.917: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.917: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.917: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.918: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.918: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.918: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.918: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.918: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.918: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.918: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.918: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.918: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.919: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.919: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.919: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.919: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.919: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.919: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.919: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.919: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.919: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.919: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.919: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.919: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.919: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.920: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.920: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.920: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.920: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.920: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.920: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.920: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.920: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.921: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.921: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.921: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.921: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.921: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.921: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.921: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.921: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.922: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.922: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.922: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.922: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.922: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.922: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.922: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.922: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.923: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.923: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.923: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.923: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.923: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.923: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.923: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.923: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.924: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.924: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.924: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.924: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.924: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.924: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.924: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.924: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.925: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.925: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.925: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.925: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.925: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.925: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.925: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.925: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.926: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.926: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.926: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.926: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.926: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.926: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.926: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.926: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.927: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.927: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.927: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.927: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.927: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.927: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.927: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.927: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.928: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.928: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.928: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.928: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.928: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.928: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.928: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.928: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.929: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.929: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.929: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.929: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.929: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.929: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.929: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.929: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.929: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.929: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.930: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.930: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.930: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.930: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.930: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.930: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.930: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.930: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.931: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.931: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.931: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.931: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.931: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.931: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.931: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.931: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.932: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.932: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.932: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.932: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.932: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.932: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.932: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.932: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.933: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.933: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.933: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.933: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.933: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.933: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.933: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.933: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.934: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.934: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.934: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.934: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.934: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.934: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.934: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.935: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.935: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.935: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.935: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.935: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.935: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.935: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.936: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.936: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.936: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.936: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.936: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.936: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.936: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.936: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.936: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.937: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.937: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.937: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.937: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.937: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.937: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.937: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.937: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.937: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.938: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.938: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.938: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.938: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.938: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.938: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.938: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.938: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.939: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.939: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.939: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.939: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.939: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.939: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.940: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.940: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.940: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.940: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.940: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.940: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.940: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.940: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.941: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.941: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.941: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.941: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.941: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.941: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.941: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.941: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.942: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.942: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.942: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.942: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.942: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.942: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.942: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.942: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.943: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.943: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.943: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.943: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.943: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.943: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.943: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.943: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.944: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.944: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.944: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.944: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.944: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.944: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.944: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.944: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.945: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.945: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.945: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.945: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.945: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.945: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.945: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.945: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.946: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.946: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.946: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.946: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.946: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.946: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.946: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.946: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.947: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.947: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.947: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.947: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.947: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.947: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.947: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.947: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.948: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.948: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.948: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.948: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.948: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.948: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.948: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.948: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.949: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.949: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.949: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.949: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.949: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.949: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.949: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.949: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.950: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.950: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.950: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.950: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.950: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.950: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.950: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.950: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.951: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.951: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.951: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.951: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.951: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.951: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.951: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.951: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.952: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.952: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.952: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.952: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.952: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.952: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.952: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.952: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.953: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.953: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.953: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.953: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.953: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.953: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.953: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.953: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.954: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.954: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.954: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.954: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.954: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.954: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.954: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.954: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.955: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.955: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.955: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.955: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.955: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.955: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.955: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.955: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.956: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.956: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.956: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.956: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.956: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.956: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.956: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.956: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.957: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.957: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.957: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.957: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.957: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.957: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.957: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.957: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.958: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.958: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.958: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.958: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.958: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.958: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.958: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.958: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.959: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.959: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.959: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.959: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.959: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.959: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.959: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.959: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.960: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.960: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.960: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.960: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.960: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.960: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.960: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.960: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.961: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.961: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.961: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.961: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.961: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.961: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.961: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.961: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.962: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.962: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.962: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.962: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.962: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.962: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.962: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.962: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.962: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.963: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.963: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.963: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.963: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.963: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.963: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.963: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.964: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.964: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.964: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.964: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.964: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.964: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.964: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.964: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.965: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.965: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.965: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.965: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.965: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.965: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.965: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.965: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.965: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.966: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.966: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.966: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.966: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.966: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.966: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.966: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.966: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.967: Receiving 64 bytes 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.967: Got 6 bytes out of 64 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.967: [vfs7552] QUERY DATA READY completed successfully 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.967: [vfs7552] CAPTURE_NUM_STATES entering state 1 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.967: [vfs7552] CAPTURE_NUM_STATES entering state 0 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.967: [vfs7552] QUERY DATA READY entering state 0 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.967: Sending vfs7552_is_image_ready 183s (process:2314): libfprint-SSM-DEBUG: 16:48:20.967: [vfs7552] QUERY DATA READY entering state 1 183s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.967: Receiving 64 bytes 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.968: Got 6 bytes out of 64 184s (process:2314): libfprint-SSM-DEBUG: 16:48:20.968: [vfs7552] QUERY DATA READY completed successfully 184s (process:2314): libfprint-SSM-DEBUG: 16:48:20.968: [vfs7552] CAPTURE_NUM_STATES entering state 1 184s (process:2314): libfprint-SSM-DEBUG: 16:48:20.968: [vfs7552] CAPTURE_NUM_STATES entering state 0 184s (process:2314): libfprint-SSM-DEBUG: 16:48:20.968: [vfs7552] QUERY DATA READY entering state 0 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.968: Sending vfs7552_is_image_ready 184s (process:2314): libfprint-SSM-DEBUG: 16:48:20.968: [vfs7552] QUERY DATA READY entering state 1 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.969: Receiving 64 bytes 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.969: Got 6 bytes out of 64 184s (process:2314): libfprint-SSM-DEBUG: 16:48:20.969: [vfs7552] QUERY DATA READY completed successfully 184s (process:2314): libfprint-SSM-DEBUG: 16:48:20.969: [vfs7552] CAPTURE_NUM_STATES entering state 1 184s (process:2314): libfprint-SSM-DEBUG: 16:48:20.969: [vfs7552] CAPTURE_NUM_STATES entering state 0 184s (process:2314): libfprint-SSM-DEBUG: 16:48:20.969: [vfs7552] QUERY DATA READY entering state 0 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.969: Sending vfs7552_is_image_ready 184s (process:2314): libfprint-SSM-DEBUG: 16:48:20.969: [vfs7552] QUERY DATA READY entering state 1 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.970: Receiving 64 bytes 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.970: Got 6 bytes out of 64 184s (process:2314): libfprint-SSM-DEBUG: 16:48:20.970: [vfs7552] QUERY DATA READY completed successfully 184s (process:2314): libfprint-SSM-DEBUG: 16:48:20.970: [vfs7552] CAPTURE_NUM_STATES entering state 1 184s (process:2314): libfprint-SSM-DEBUG: 16:48:20.970: [vfs7552] CAPTURE_NUM_STATES entering state 0 184s (process:2314): libfprint-SSM-DEBUG: 16:48:20.970: [vfs7552] QUERY DATA READY entering state 0 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.970: Sending vfs7552_is_image_ready 184s (process:2314): libfprint-SSM-DEBUG: 16:48:20.970: [vfs7552] QUERY DATA READY entering state 1 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.970: Receiving 64 bytes 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.971: Got 6 bytes out of 64 184s (process:2314): libfprint-SSM-DEBUG: 16:48:20.971: [vfs7552] QUERY DATA READY completed successfully 184s (process:2314): libfprint-SSM-DEBUG: 16:48:20.971: [vfs7552] CAPTURE_NUM_STATES entering state 1 184s (process:2314): libfprint-SSM-DEBUG: 16:48:20.971: [vfs7552] CAPTURE_NUM_STATES entering state 0 184s (process:2314): libfprint-SSM-DEBUG: 16:48:20.971: [vfs7552] QUERY DATA READY entering state 0 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.971: Sending vfs7552_is_image_ready 184s (process:2314): libfprint-SSM-DEBUG: 16:48:20.971: [vfs7552] QUERY DATA READY entering state 1 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.971: Receiving 64 bytes 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.972: Got 6 bytes out of 64 184s (process:2314): libfprint-SSM-DEBUG: 16:48:20.972: [vfs7552] QUERY DATA READY completed successfully 184s (process:2314): libfprint-SSM-DEBUG: 16:48:20.972: [vfs7552] CAPTURE_NUM_STATES entering state 1 184s (process:2314): libfprint-SSM-DEBUG: 16:48:20.972: [vfs7552] CAPTURE_NUM_STATES entering state 0 184s (process:2314): libfprint-SSM-DEBUG: 16:48:20.972: [vfs7552] QUERY DATA READY entering state 0 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.972: Sending vfs7552_is_image_ready 184s (process:2314): libfprint-SSM-DEBUG: 16:48:20.972: [vfs7552] QUERY DATA READY entering state 1 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.972: Receiving 64 bytes 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.973: Got 6 bytes out of 64 184s (process:2314): libfprint-SSM-DEBUG: 16:48:20.973: [vfs7552] QUERY DATA READY completed successfully 184s (process:2314): libfprint-SSM-DEBUG: 16:48:20.973: [vfs7552] CAPTURE_NUM_STATES entering state 1 184s (process:2314): libfprint-SSM-DEBUG: 16:48:20.973: [vfs7552] CAPTURE_NUM_STATES entering state 0 184s (process:2314): libfprint-SSM-DEBUG: 16:48:20.973: [vfs7552] QUERY DATA READY entering state 0 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.973: Sending vfs7552_is_image_ready 184s (process:2314): libfprint-SSM-DEBUG: 16:48:20.973: [vfs7552] QUERY DATA READY entering state 1 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.973: Receiving 64 bytes 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.974: Got 6 bytes out of 64 184s (process:2314): libfprint-SSM-DEBUG: 16:48:20.974: [vfs7552] QUERY DATA READY completed successfully 184s (process:2314): libfprint-SSM-DEBUG: 16:48:20.974: [vfs7552] CAPTURE_NUM_STATES entering state 1 184s (process:2314): libfprint-SSM-DEBUG: 16:48:20.974: [vfs7552] CAPTURE_NUM_STATES entering state 0 184s (process:2314): libfprint-SSM-DEBUG: 16:48:20.974: [vfs7552] QUERY DATA READY entering state 0 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.974: Sending vfs7552_is_image_ready 184s (process:2314): libfprint-SSM-DEBUG: 16:48:20.974: [vfs7552] QUERY DATA READY entering state 1 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.974: Receiving 64 bytes 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.975: Got 6 bytes out of 64 184s (process:2314): libfprint-SSM-DEBUG: 16:48:20.975: [vfs7552] QUERY DATA READY completed successfully 184s (process:2314): libfprint-SSM-DEBUG: 16:48:20.975: [vfs7552] CAPTURE_NUM_STATES entering state 1 184s (process:2314): libfprint-SSM-DEBUG: 16:48:20.975: [vfs7552] CAPTURE_NUM_STATES entering state 0 184s (process:2314): libfprint-SSM-DEBUG: 16:48:20.975: [vfs7552] QUERY DATA READY entering state 0 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.975: Sending vfs7552_is_image_ready 184s (process:2314): libfprint-SSM-DEBUG: 16:48:20.975: [vfs7552] QUERY DATA READY entering state 1 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.975: Receiving 64 bytes 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.976: Got 6 bytes out of 64 184s (process:2314): libfprint-SSM-DEBUG: 16:48:20.976: [vfs7552] QUERY DATA READY completed successfully 184s (process:2314): libfprint-SSM-DEBUG: 16:48:20.976: [vfs7552] CAPTURE_NUM_STATES entering state 1 184s (process:2314): libfprint-SSM-DEBUG: 16:48:20.976: [vfs7552] CAPTURE_NUM_STATES entering state 0 184s (process:2314): libfprint-SSM-DEBUG: 16:48:20.976: [vfs7552] QUERY DATA READY entering state 0 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.976: Sending vfs7552_is_image_ready 184s (process:2314): libfprint-SSM-DEBUG: 16:48:20.976: [vfs7552] QUERY DATA READY entering state 1 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.976: Receiving 64 bytes 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.977: Got 6 bytes out of 64 184s (process:2314): libfprint-SSM-DEBUG: 16:48:20.977: [vfs7552] QUERY DATA READY completed successfully 184s (process:2314): libfprint-SSM-DEBUG: 16:48:20.977: [vfs7552] CAPTURE_NUM_STATES entering state 1 184s (process:2314): libfprint-SSM-DEBUG: 16:48:20.977: [vfs7552] CAPTURE_NUM_STATES entering state 0 184s (process:2314): libfprint-SSM-DEBUG: 16:48:20.977: [vfs7552] QUERY DATA READY entering state 0 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.977: Sending vfs7552_is_image_ready 184s (process:2314): libfprint-SSM-DEBUG: 16:48:20.977: [vfs7552] QUERY DATA READY entering state 1 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.977: Receiving 64 bytes 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.978: Got 6 bytes out of 64 184s (process:2314): libfprint-SSM-DEBUG: 16:48:20.978: [vfs7552] QUERY DATA READY completed successfully 184s (process:2314): libfprint-SSM-DEBUG: 16:48:20.978: [vfs7552] CAPTURE_NUM_STATES entering state 1 184s (process:2314): libfprint-SSM-DEBUG: 16:48:20.978: [vfs7552] CAPTURE_NUM_STATES entering state 0 184s (process:2314): libfprint-SSM-DEBUG: 16:48:20.978: [vfs7552] QUERY DATA READY entering state 0 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.978: Sending vfs7552_is_image_ready 184s (process:2314): libfprint-SSM-DEBUG: 16:48:20.978: [vfs7552] QUERY DATA READY entering state 1 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.978: Receiving 64 bytes 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.979: Got 6 bytes out of 64 184s (process:2314): libfprint-SSM-DEBUG: 16:48:20.979: [vfs7552] QUERY DATA READY completed successfully 184s (process:2314): libfprint-SSM-DEBUG: 16:48:20.979: [vfs7552] CAPTURE_NUM_STATES entering state 1 184s (process:2314): libfprint-SSM-DEBUG: 16:48:20.979: [vfs7552] CAPTURE_NUM_STATES entering state 0 184s (process:2314): libfprint-SSM-DEBUG: 16:48:20.979: [vfs7552] QUERY DATA READY entering state 0 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.979: Sending vfs7552_is_image_ready 184s (process:2314): libfprint-SSM-DEBUG: 16:48:20.979: [vfs7552] QUERY DATA READY entering state 1 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.979: Receiving 64 bytes 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.980: Got 6 bytes out of 64 184s (process:2314): libfprint-SSM-DEBUG: 16:48:20.980: [vfs7552] QUERY DATA READY completed successfully 184s (process:2314): libfprint-SSM-DEBUG: 16:48:20.980: [vfs7552] CAPTURE_NUM_STATES entering state 1 184s (process:2314): libfprint-SSM-DEBUG: 16:48:20.980: [vfs7552] CAPTURE_NUM_STATES entering state 0 184s (process:2314): libfprint-SSM-DEBUG: 16:48:20.980: [vfs7552] QUERY DATA READY entering state 0 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.980: Sending vfs7552_is_image_ready 184s (process:2314): libfprint-SSM-DEBUG: 16:48:20.980: [vfs7552] QUERY DATA READY entering state 1 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.980: Receiving 64 bytes 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.981: Got 6 bytes out of 64 184s (process:2314): libfprint-SSM-DEBUG: 16:48:20.981: [vfs7552] QUERY DATA READY completed successfully 184s (process:2314): libfprint-SSM-DEBUG: 16:48:20.981: [vfs7552] CAPTURE_NUM_STATES entering state 1 184s (process:2314): libfprint-SSM-DEBUG: 16:48:20.981: [vfs7552] CAPTURE_NUM_STATES entering state 0 184s (process:2314): libfprint-SSM-DEBUG: 16:48:20.981: [vfs7552] QUERY DATA READY entering state 0 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.981: Sending vfs7552_is_image_ready 184s (process:2314): libfprint-SSM-DEBUG: 16:48:20.981: [vfs7552] QUERY DATA READY entering state 1 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.981: Receiving 64 bytes 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.982: Got 6 bytes out of 64 184s (process:2314): libfprint-SSM-DEBUG: 16:48:20.982: [vfs7552] QUERY DATA READY completed successfully 184s (process:2314): libfprint-SSM-DEBUG: 16:48:20.982: [vfs7552] CAPTURE_NUM_STATES entering state 1 184s (process:2314): libfprint-SSM-DEBUG: 16:48:20.982: [vfs7552] CAPTURE_NUM_STATES entering state 0 184s (process:2314): libfprint-SSM-DEBUG: 16:48:20.982: [vfs7552] QUERY DATA READY entering state 0 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.982: Sending vfs7552_is_image_ready 184s (process:2314): libfprint-SSM-DEBUG: 16:48:20.982: [vfs7552] QUERY DATA READY entering state 1 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.982: Receiving 64 bytes 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.983: Got 6 bytes out of 64 184s (process:2314): libfprint-SSM-DEBUG: 16:48:20.983: [vfs7552] QUERY DATA READY completed successfully 184s (process:2314): libfprint-SSM-DEBUG: 16:48:20.983: [vfs7552] CAPTURE_NUM_STATES entering state 1 184s (process:2314): libfprint-SSM-DEBUG: 16:48:20.983: [vfs7552] CAPTURE_NUM_STATES entering state 0 184s (process:2314): libfprint-SSM-DEBUG: 16:48:20.983: [vfs7552] QUERY DATA READY entering state 0 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.983: Sending vfs7552_is_image_ready 184s (process:2314): libfprint-SSM-DEBUG: 16:48:20.983: [vfs7552] QUERY DATA READY entering state 1 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.983: Receiving 64 bytes 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.984: Got 6 bytes out of 64 184s (process:2314): libfprint-SSM-DEBUG: 16:48:20.984: [vfs7552] QUERY DATA READY completed successfully 184s (process:2314): libfprint-SSM-DEBUG: 16:48:20.984: [vfs7552] CAPTURE_NUM_STATES entering state 1 184s (process:2314): libfprint-SSM-DEBUG: 16:48:20.984: [vfs7552] CAPTURE_NUM_STATES entering state 0 184s (process:2314): libfprint-SSM-DEBUG: 16:48:20.984: [vfs7552] QUERY DATA READY entering state 0 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.984: Sending vfs7552_is_image_ready 184s (process:2314): libfprint-SSM-DEBUG: 16:48:20.984: [vfs7552] QUERY DATA READY entering state 1 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.984: Receiving 64 bytes 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.985: Got 6 bytes out of 64 184s (process:2314): libfprint-SSM-DEBUG: 16:48:20.985: [vfs7552] QUERY DATA READY completed successfully 184s (process:2314): libfprint-SSM-DEBUG: 16:48:20.985: [vfs7552] CAPTURE_NUM_STATES entering state 1 184s (process:2314): libfprint-SSM-DEBUG: 16:48:20.985: [vfs7552] CAPTURE_NUM_STATES entering state 0 184s (process:2314): libfprint-SSM-DEBUG: 16:48:20.985: [vfs7552] QUERY DATA READY entering state 0 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.985: Sending vfs7552_is_image_ready 184s (process:2314): libfprint-SSM-DEBUG: 16:48:20.985: [vfs7552] QUERY DATA READY entering state 1 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.985: Receiving 64 bytes 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.986: Got 6 bytes out of 64 184s (process:2314): libfprint-SSM-DEBUG: 16:48:20.986: [vfs7552] QUERY DATA READY completed successfully 184s (process:2314): libfprint-SSM-DEBUG: 16:48:20.986: [vfs7552] CAPTURE_NUM_STATES entering state 1 184s (process:2314): libfprint-SSM-DEBUG: 16:48:20.986: [vfs7552] CAPTURE_NUM_STATES entering state 0 184s (process:2314): libfprint-SSM-DEBUG: 16:48:20.986: [vfs7552] QUERY DATA READY entering state 0 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.986: Sending vfs7552_is_image_ready 184s (process:2314): libfprint-SSM-DEBUG: 16:48:20.986: [vfs7552] QUERY DATA READY entering state 1 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.986: Receiving 64 bytes 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.987: Got 6 bytes out of 64 184s (process:2314): libfprint-SSM-DEBUG: 16:48:20.987: [vfs7552] QUERY DATA READY completed successfully 184s (process:2314): libfprint-SSM-DEBUG: 16:48:20.987: [vfs7552] CAPTURE_NUM_STATES entering state 1 184s (process:2314): libfprint-SSM-DEBUG: 16:48:20.987: [vfs7552] CAPTURE_NUM_STATES entering state 0 184s (process:2314): libfprint-SSM-DEBUG: 16:48:20.987: [vfs7552] QUERY DATA READY entering state 0 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.987: Sending vfs7552_is_image_ready 184s (process:2314): libfprint-SSM-DEBUG: 16:48:20.987: [vfs7552] QUERY DATA READY entering state 1 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.987: Receiving 64 bytes 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.988: Got 6 bytes out of 64 184s (process:2314): libfprint-SSM-DEBUG: 16:48:20.988: [vfs7552] QUERY DATA READY completed successfully 184s (process:2314): libfprint-SSM-DEBUG: 16:48:20.988: [vfs7552] CAPTURE_NUM_STATES entering state 1 184s (process:2314): libfprint-SSM-DEBUG: 16:48:20.988: [vfs7552] CAPTURE_NUM_STATES entering state 0 184s (process:2314): libfprint-SSM-DEBUG: 16:48:20.988: [vfs7552] QUERY DATA READY entering state 0 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.988: Sending vfs7552_is_image_ready 184s (process:2314): libfprint-SSM-DEBUG: 16:48:20.988: [vfs7552] QUERY DATA READY entering state 1 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.988: Receiving 64 bytes 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.989: Got 6 bytes out of 64 184s (process:2314): libfprint-SSM-DEBUG: 16:48:20.989: [vfs7552] QUERY DATA READY completed successfully 184s (process:2314): libfprint-SSM-DEBUG: 16:48:20.989: [vfs7552] CAPTURE_NUM_STATES entering state 1 184s (process:2314): libfprint-SSM-DEBUG: 16:48:20.989: [vfs7552] CAPTURE_NUM_STATES entering state 0 184s (process:2314): libfprint-SSM-DEBUG: 16:48:20.989: [vfs7552] QUERY DATA READY entering state 0 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.989: Sending vfs7552_is_image_ready 184s (process:2314): libfprint-SSM-DEBUG: 16:48:20.989: [vfs7552] QUERY DATA READY entering state 1 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.989: Receiving 64 bytes 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.990: Got 6 bytes out of 64 184s (process:2314): libfprint-SSM-DEBUG: 16:48:20.990: [vfs7552] QUERY DATA READY completed successfully 184s (process:2314): libfprint-SSM-DEBUG: 16:48:20.990: [vfs7552] CAPTURE_NUM_STATES entering state 1 184s (process:2314): libfprint-SSM-DEBUG: 16:48:20.990: [vfs7552] CAPTURE_NUM_STATES entering state 0 184s (process:2314): libfprint-SSM-DEBUG: 16:48:20.990: [vfs7552] QUERY DATA READY entering state 0 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.990: Sending vfs7552_is_image_ready 184s (process:2314): libfprint-SSM-DEBUG: 16:48:20.990: [vfs7552] QUERY DATA READY entering state 1 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.990: Receiving 64 bytes 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.991: Got 6 bytes out of 64 184s (process:2314): libfprint-SSM-DEBUG: 16:48:20.991: [vfs7552] QUERY DATA READY completed successfully 184s (process:2314): libfprint-SSM-DEBUG: 16:48:20.991: [vfs7552] CAPTURE_NUM_STATES entering state 1 184s (process:2314): libfprint-SSM-DEBUG: 16:48:20.991: [vfs7552] CAPTURE_NUM_STATES entering state 0 184s (process:2314): libfprint-SSM-DEBUG: 16:48:20.991: [vfs7552] QUERY DATA READY entering state 0 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.991: Sending vfs7552_is_image_ready 184s (process:2314): libfprint-SSM-DEBUG: 16:48:20.991: [vfs7552] QUERY DATA READY entering state 1 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.991: Receiving 64 bytes 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.992: Got 6 bytes out of 64 184s (process:2314): libfprint-SSM-DEBUG: 16:48:20.992: [vfs7552] QUERY DATA READY completed successfully 184s (process:2314): libfprint-SSM-DEBUG: 16:48:20.992: [vfs7552] CAPTURE_NUM_STATES entering state 1 184s (process:2314): libfprint-SSM-DEBUG: 16:48:20.992: [vfs7552] CAPTURE_NUM_STATES entering state 0 184s (process:2314): libfprint-SSM-DEBUG: 16:48:20.992: [vfs7552] QUERY DATA READY entering state 0 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.992: Sending vfs7552_is_image_ready 184s (process:2314): libfprint-SSM-DEBUG: 16:48:20.992: [vfs7552] QUERY DATA READY entering state 1 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.992: Receiving 64 bytes 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.993: Got 6 bytes out of 64 184s (process:2314): libfprint-SSM-DEBUG: 16:48:20.993: [vfs7552] QUERY DATA READY completed successfully 184s (process:2314): libfprint-SSM-DEBUG: 16:48:20.993: [vfs7552] CAPTURE_NUM_STATES entering state 1 184s (process:2314): libfprint-SSM-DEBUG: 16:48:20.993: [vfs7552] CAPTURE_NUM_STATES entering state 0 184s (process:2314): libfprint-SSM-DEBUG: 16:48:20.993: [vfs7552] QUERY DATA READY entering state 0 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.993: Sending vfs7552_is_image_ready 184s (process:2314): libfprint-SSM-DEBUG: 16:48:20.993: [vfs7552] QUERY DATA READY entering state 1 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.993: Receiving 64 bytes 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.994: Got 6 bytes out of 64 184s (process:2314): libfprint-SSM-DEBUG: 16:48:20.994: [vfs7552] QUERY DATA READY completed successfully 184s (process:2314): libfprint-SSM-DEBUG: 16:48:20.994: [vfs7552] CAPTURE_NUM_STATES entering state 1 184s (process:2314): libfprint-SSM-DEBUG: 16:48:20.994: [vfs7552] CAPTURE_NUM_STATES entering state 0 184s (process:2314): libfprint-SSM-DEBUG: 16:48:20.994: [vfs7552] QUERY DATA READY entering state 0 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.994: Sending vfs7552_is_image_ready 184s (process:2314): libfprint-SSM-DEBUG: 16:48:20.994: [vfs7552] QUERY DATA READY entering state 1 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.994: Receiving 64 bytes 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.995: Got 6 bytes out of 64 184s (process:2314): libfprint-SSM-DEBUG: 16:48:20.995: [vfs7552] QUERY DATA READY completed successfully 184s (process:2314): libfprint-SSM-DEBUG: 16:48:20.995: [vfs7552] CAPTURE_NUM_STATES entering state 1 184s (process:2314): libfprint-SSM-DEBUG: 16:48:20.995: [vfs7552] CAPTURE_NUM_STATES entering state 0 184s (process:2314): libfprint-SSM-DEBUG: 16:48:20.995: [vfs7552] QUERY DATA READY entering state 0 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.995: Sending vfs7552_is_image_ready 184s (process:2314): libfprint-SSM-DEBUG: 16:48:20.995: [vfs7552] QUERY DATA READY entering state 1 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.995: Receiving 64 bytes 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.996: Got 6 bytes out of 64 184s (process:2314): libfprint-SSM-DEBUG: 16:48:20.996: [vfs7552] QUERY DATA READY completed successfully 184s (process:2314): libfprint-SSM-DEBUG: 16:48:20.996: [vfs7552] CAPTURE_NUM_STATES entering state 1 184s (process:2314): libfprint-SSM-DEBUG: 16:48:20.996: [vfs7552] CAPTURE_NUM_STATES entering state 0 184s (process:2314): libfprint-SSM-DEBUG: 16:48:20.996: [vfs7552] QUERY DATA READY entering state 0 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.996: Sending vfs7552_is_image_ready 184s (process:2314): libfprint-SSM-DEBUG: 16:48:20.996: [vfs7552] QUERY DATA READY entering state 1 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.996: Receiving 64 bytes 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.997: Got 6 bytes out of 64 184s (process:2314): libfprint-SSM-DEBUG: 16:48:20.997: [vfs7552] QUERY DATA READY completed successfully 184s (process:2314): libfprint-SSM-DEBUG: 16:48:20.997: [vfs7552] CAPTURE_NUM_STATES entering state 1 184s (process:2314): libfprint-SSM-DEBUG: 16:48:20.997: [vfs7552] CAPTURE_NUM_STATES entering state 0 184s (process:2314): libfprint-SSM-DEBUG: 16:48:20.997: [vfs7552] QUERY DATA READY entering state 0 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.997: Sending vfs7552_is_image_ready 184s (process:2314): libfprint-SSM-DEBUG: 16:48:20.997: [vfs7552] QUERY DATA READY entering state 1 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.997: Receiving 64 bytes 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.998: Got 6 bytes out of 64 184s (process:2314): libfprint-SSM-DEBUG: 16:48:20.998: [vfs7552] QUERY DATA READY completed successfully 184s (process:2314): libfprint-SSM-DEBUG: 16:48:20.998: [vfs7552] CAPTURE_NUM_STATES entering state 1 184s (process:2314): libfprint-SSM-DEBUG: 16:48:20.998: [vfs7552] CAPTURE_NUM_STATES entering state 0 184s (process:2314): libfprint-SSM-DEBUG: 16:48:20.998: [vfs7552] QUERY DATA READY entering state 0 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.998: Sending vfs7552_is_image_ready 184s (process:2314): libfprint-SSM-DEBUG: 16:48:20.998: [vfs7552] QUERY DATA READY entering state 1 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.998: Receiving 64 bytes 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.999: Got 6 bytes out of 64 184s (process:2314): libfprint-SSM-DEBUG: 16:48:20.999: [vfs7552] QUERY DATA READY completed successfully 184s (process:2314): libfprint-SSM-DEBUG: 16:48:20.999: [vfs7552] CAPTURE_NUM_STATES entering state 1 184s (process:2314): libfprint-SSM-DEBUG: 16:48:20.999: [vfs7552] CAPTURE_NUM_STATES entering state 0 184s (process:2314): libfprint-SSM-DEBUG: 16:48:20.999: [vfs7552] QUERY DATA READY entering state 0 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.999: Sending vfs7552_is_image_ready 184s (process:2314): libfprint-SSM-DEBUG: 16:48:20.999: [vfs7552] QUERY DATA READY entering state 1 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:20.999: Receiving 64 bytes 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.000: Got 6 bytes out of 64 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.000: [vfs7552] QUERY DATA READY completed successfully 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.000: [vfs7552] CAPTURE_NUM_STATES entering state 1 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.000: [vfs7552] CAPTURE_NUM_STATES entering state 0 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.000: [vfs7552] QUERY DATA READY entering state 0 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.000: Sending vfs7552_is_image_ready 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.000: [vfs7552] QUERY DATA READY entering state 1 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.000: Receiving 64 bytes 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.001: Got 6 bytes out of 64 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.001: [vfs7552] QUERY DATA READY completed successfully 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.001: [vfs7552] CAPTURE_NUM_STATES entering state 1 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.001: [vfs7552] CAPTURE_NUM_STATES entering state 0 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.001: [vfs7552] QUERY DATA READY entering state 0 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.001: Sending vfs7552_is_image_ready 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.001: [vfs7552] QUERY DATA READY entering state 1 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.001: Receiving 64 bytes 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.002: Got 6 bytes out of 64 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.002: [vfs7552] QUERY DATA READY completed successfully 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.002: [vfs7552] CAPTURE_NUM_STATES entering state 1 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.002: [vfs7552] CAPTURE_NUM_STATES entering state 0 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.002: [vfs7552] QUERY DATA READY entering state 0 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.002: Sending vfs7552_is_image_ready 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.002: [vfs7552] QUERY DATA READY entering state 1 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.002: Receiving 64 bytes 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.003: Got 6 bytes out of 64 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.003: [vfs7552] QUERY DATA READY completed successfully 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.003: [vfs7552] CAPTURE_NUM_STATES entering state 1 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.003: [vfs7552] CAPTURE_NUM_STATES entering state 0 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.003: [vfs7552] QUERY DATA READY entering state 0 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.003: Sending vfs7552_is_image_ready 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.003: [vfs7552] QUERY DATA READY entering state 1 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.003: Receiving 64 bytes 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.003: Got 6 bytes out of 64 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.004: [vfs7552] QUERY DATA READY completed successfully 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.004: [vfs7552] CAPTURE_NUM_STATES entering state 1 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.004: [vfs7552] CAPTURE_NUM_STATES entering state 0 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.004: [vfs7552] QUERY DATA READY entering state 0 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.004: Sending vfs7552_is_image_ready 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.004: [vfs7552] QUERY DATA READY entering state 1 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.004: Receiving 64 bytes 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.004: Got 6 bytes out of 64 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.004: [vfs7552] QUERY DATA READY completed successfully 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.004: [vfs7552] CAPTURE_NUM_STATES entering state 1 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.005: [vfs7552] CAPTURE_NUM_STATES entering state 0 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.005: [vfs7552] QUERY DATA READY entering state 0 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.005: Sending vfs7552_is_image_ready 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.005: [vfs7552] QUERY DATA READY entering state 1 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.005: Receiving 64 bytes 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.005: Got 6 bytes out of 64 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.005: [vfs7552] QUERY DATA READY completed successfully 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.005: [vfs7552] CAPTURE_NUM_STATES entering state 1 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.006: [vfs7552] CAPTURE_NUM_STATES entering state 0 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.006: [vfs7552] QUERY DATA READY entering state 0 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.006: Sending vfs7552_is_image_ready 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.006: [vfs7552] QUERY DATA READY entering state 1 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.006: Receiving 64 bytes 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.006: Got 6 bytes out of 64 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.006: [vfs7552] QUERY DATA READY completed successfully 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.006: [vfs7552] CAPTURE_NUM_STATES entering state 1 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.006: [vfs7552] CAPTURE_NUM_STATES entering state 0 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.006: [vfs7552] QUERY DATA READY entering state 0 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.006: Sending vfs7552_is_image_ready 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.007: [vfs7552] QUERY DATA READY entering state 1 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.007: Receiving 64 bytes 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.007: Got 6 bytes out of 64 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.007: [vfs7552] QUERY DATA READY completed successfully 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.007: [vfs7552] CAPTURE_NUM_STATES entering state 1 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.007: [vfs7552] CAPTURE_NUM_STATES entering state 0 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.007: [vfs7552] QUERY DATA READY entering state 0 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.007: Sending vfs7552_is_image_ready 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.008: [vfs7552] QUERY DATA READY entering state 1 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.008: Receiving 64 bytes 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.008: Got 6 bytes out of 64 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.008: [vfs7552] QUERY DATA READY completed successfully 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.008: [vfs7552] CAPTURE_NUM_STATES entering state 1 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.008: [vfs7552] CAPTURE_NUM_STATES entering state 0 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.008: [vfs7552] QUERY DATA READY entering state 0 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.008: Sending vfs7552_is_image_ready 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.009: [vfs7552] QUERY DATA READY entering state 1 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.009: Receiving 64 bytes 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.009: Got 6 bytes out of 64 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.009: [vfs7552] QUERY DATA READY completed successfully 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.009: [vfs7552] CAPTURE_NUM_STATES entering state 1 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.009: [vfs7552] CAPTURE_NUM_STATES entering state 0 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.009: [vfs7552] QUERY DATA READY entering state 0 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.009: Sending vfs7552_is_image_ready 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.010: [vfs7552] QUERY DATA READY entering state 1 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.010: Receiving 64 bytes 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.010: Got 6 bytes out of 64 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.010: [vfs7552] QUERY DATA READY completed successfully 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.010: [vfs7552] CAPTURE_NUM_STATES entering state 1 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.010: [vfs7552] CAPTURE_NUM_STATES entering state 0 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.010: [vfs7552] QUERY DATA READY entering state 0 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.010: Sending vfs7552_is_image_ready 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.011: [vfs7552] QUERY DATA READY entering state 1 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.011: Receiving 64 bytes 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.011: Got 6 bytes out of 64 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.011: [vfs7552] QUERY DATA READY completed successfully 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.011: [vfs7552] CAPTURE_NUM_STATES entering state 1 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.011: [vfs7552] CAPTURE_NUM_STATES entering state 0 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.011: [vfs7552] QUERY DATA READY entering state 0 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.011: Sending vfs7552_is_image_ready 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.012: [vfs7552] QUERY DATA READY entering state 1 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.012: Receiving 64 bytes 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.012: Got 6 bytes out of 64 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.012: [vfs7552] QUERY DATA READY completed successfully 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.012: [vfs7552] CAPTURE_NUM_STATES entering state 1 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.012: [vfs7552] CAPTURE_NUM_STATES entering state 0 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.012: [vfs7552] QUERY DATA READY entering state 0 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.012: Sending vfs7552_is_image_ready 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.013: [vfs7552] QUERY DATA READY entering state 1 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.013: Receiving 64 bytes 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.013: Got 6 bytes out of 64 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.013: [vfs7552] QUERY DATA READY completed successfully 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.013: [vfs7552] CAPTURE_NUM_STATES entering state 1 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.013: [vfs7552] CAPTURE_NUM_STATES entering state 0 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.013: [vfs7552] QUERY DATA READY entering state 0 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.013: Sending vfs7552_is_image_ready 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.014: [vfs7552] QUERY DATA READY entering state 1 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.014: Receiving 64 bytes 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.014: Got 6 bytes out of 64 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.014: [vfs7552] QUERY DATA READY completed successfully 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.014: [vfs7552] CAPTURE_NUM_STATES entering state 1 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.014: [vfs7552] CAPTURE_NUM_STATES entering state 0 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.014: [vfs7552] QUERY DATA READY entering state 0 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.014: Sending vfs7552_is_image_ready 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.015: [vfs7552] QUERY DATA READY entering state 1 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.015: Receiving 64 bytes 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.015: Got 6 bytes out of 64 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.015: [vfs7552] QUERY DATA READY completed successfully 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.015: [vfs7552] CAPTURE_NUM_STATES entering state 1 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.015: [vfs7552] CAPTURE_NUM_STATES entering state 2 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.015: [vfs7552] REQUEST CHUNK entering state 0 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.015: Sending vfs7552_read_image_chunk 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.016: [vfs7552] REQUEST CHUNK completed successfully 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.016: [vfs7552] CAPTURE_NUM_STATES entering state 3 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.016: [vfs7552] CAPTURE_NUM_STATES entering state 2 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.016: [vfs7552] REQUEST CHUNK entering state 0 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.016: Sending vfs7552_read_image_chunk 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.017: [vfs7552] REQUEST CHUNK completed successfully 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.017: [vfs7552] CAPTURE_NUM_STATES entering state 3 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.017: [vfs7552] CAPTURE_NUM_STATES entering state 2 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.017: [vfs7552] REQUEST CHUNK entering state 0 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.017: Sending vfs7552_read_image_chunk 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.018: [vfs7552] REQUEST CHUNK completed successfully 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.018: [vfs7552] CAPTURE_NUM_STATES entering state 3 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.018: [vfs7552] CAPTURE_NUM_STATES entering state 4 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.018: Cleaning image 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.018: variance_after = 1425 184s 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.018: [vfs7552] CAPTURE_NUM_STATES entering state 0 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.018: [vfs7552] QUERY DATA READY entering state 0 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.018: Sending vfs7552_is_image_ready 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.019: [vfs7552] QUERY DATA READY entering state 1 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.019: Receiving 64 bytes 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.019: Got 6 bytes out of 64 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.019: [vfs7552] QUERY DATA READY completed successfully 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.019: [vfs7552] CAPTURE_NUM_STATES entering state 1 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.019: [vfs7552] CAPTURE_NUM_STATES entering state 0 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.019: [vfs7552] QUERY DATA READY entering state 0 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.019: Sending vfs7552_is_image_ready 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.020: [vfs7552] QUERY DATA READY entering state 1 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.020: Receiving 64 bytes 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.020: Got 6 bytes out of 64 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.020: [vfs7552] QUERY DATA READY completed successfully 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.020: [vfs7552] CAPTURE_NUM_STATES entering state 1 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.020: [vfs7552] CAPTURE_NUM_STATES entering state 0 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.020: [vfs7552] QUERY DATA READY entering state 0 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.020: Sending vfs7552_is_image_ready 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.021: [vfs7552] QUERY DATA READY entering state 1 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.021: Receiving 64 bytes 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.021: Got 6 bytes out of 64 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.021: [vfs7552] QUERY DATA READY completed successfully 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.021: [vfs7552] CAPTURE_NUM_STATES entering state 1 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.021: [vfs7552] CAPTURE_NUM_STATES entering state 0 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.021: [vfs7552] QUERY DATA READY entering state 0 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.021: Sending vfs7552_is_image_ready 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.022: [vfs7552] QUERY DATA READY entering state 1 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.022: Receiving 64 bytes 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.022: Got 6 bytes out of 64 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.022: [vfs7552] QUERY DATA READY completed successfully 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.022: [vfs7552] CAPTURE_NUM_STATES entering state 1 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.022: [vfs7552] CAPTURE_NUM_STATES entering state 0 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.022: [vfs7552] QUERY DATA READY entering state 0 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.022: Sending vfs7552_is_image_ready 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.023: [vfs7552] QUERY DATA READY entering state 1 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.023: Receiving 64 bytes 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.023: Got 6 bytes out of 64 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.024: [vfs7552] QUERY DATA READY completed successfully 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.024: [vfs7552] CAPTURE_NUM_STATES entering state 1 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.024: [vfs7552] CAPTURE_NUM_STATES entering state 0 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.024: [vfs7552] QUERY DATA READY entering state 0 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.024: Sending vfs7552_is_image_ready 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.024: [vfs7552] QUERY DATA READY entering state 1 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.024: Receiving 64 bytes 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.025: Got 6 bytes out of 64 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.025: [vfs7552] QUERY DATA READY completed successfully 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.025: [vfs7552] CAPTURE_NUM_STATES entering state 1 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.025: [vfs7552] CAPTURE_NUM_STATES entering state 0 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.025: [vfs7552] QUERY DATA READY entering state 0 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.025: Sending vfs7552_is_image_ready 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.025: [vfs7552] QUERY DATA READY entering state 1 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.025: Receiving 64 bytes 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.026: Got 6 bytes out of 64 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.026: [vfs7552] QUERY DATA READY completed successfully 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.026: [vfs7552] CAPTURE_NUM_STATES entering state 1 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.026: [vfs7552] CAPTURE_NUM_STATES entering state 0 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.026: [vfs7552] QUERY DATA READY entering state 0 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.026: Sending vfs7552_is_image_ready 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.026: [vfs7552] QUERY DATA READY entering state 1 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.026: Receiving 64 bytes 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.026: Got 6 bytes out of 64 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.026: [vfs7552] QUERY DATA READY completed successfully 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.027: [vfs7552] CAPTURE_NUM_STATES entering state 1 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.027: [vfs7552] CAPTURE_NUM_STATES entering state 0 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.027: [vfs7552] QUERY DATA READY entering state 0 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.027: Sending vfs7552_is_image_ready 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.027: [vfs7552] QUERY DATA READY entering state 1 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.027: Receiving 64 bytes 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.027: Got 6 bytes out of 64 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.028: [vfs7552] QUERY DATA READY completed successfully 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.028: [vfs7552] CAPTURE_NUM_STATES entering state 1 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.028: [vfs7552] CAPTURE_NUM_STATES entering state 0 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.028: [vfs7552] QUERY DATA READY entering state 0 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.028: Sending vfs7552_is_image_ready 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.028: [vfs7552] QUERY DATA READY entering state 1 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.028: Receiving 64 bytes 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.028: Got 6 bytes out of 64 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.029: [vfs7552] QUERY DATA READY completed successfully 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.029: [vfs7552] CAPTURE_NUM_STATES entering state 1 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.029: [vfs7552] CAPTURE_NUM_STATES entering state 0 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.029: [vfs7552] QUERY DATA READY entering state 0 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.029: Sending vfs7552_is_image_ready 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.029: [vfs7552] QUERY DATA READY entering state 1 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.029: Receiving 64 bytes 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.029: Got 6 bytes out of 64 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.030: [vfs7552] QUERY DATA READY completed successfully 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.030: [vfs7552] CAPTURE_NUM_STATES entering state 1 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.030: [vfs7552] CAPTURE_NUM_STATES entering state 0 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.030: [vfs7552] QUERY DATA READY entering state 0 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.030: Sending vfs7552_is_image_ready 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.030: [vfs7552] QUERY DATA READY entering state 1 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.030: Receiving 64 bytes 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.030: Got 6 bytes out of 64 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.030: [vfs7552] QUERY DATA READY completed successfully 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.030: [vfs7552] CAPTURE_NUM_STATES entering state 1 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.030: [vfs7552] CAPTURE_NUM_STATES entering state 0 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.030: [vfs7552] QUERY DATA READY entering state 0 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.031: Sending vfs7552_is_image_ready 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.031: [vfs7552] QUERY DATA READY entering state 1 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.031: Receiving 64 bytes 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.031: Got 6 bytes out of 64 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.031: [vfs7552] QUERY DATA READY completed successfully 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.031: [vfs7552] CAPTURE_NUM_STATES entering state 1 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.031: [vfs7552] CAPTURE_NUM_STATES entering state 0 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.031: [vfs7552] QUERY DATA READY entering state 0 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.031: Sending vfs7552_is_image_ready 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.032: [vfs7552] QUERY DATA READY entering state 1 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.032: Receiving 64 bytes 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.032: Got 6 bytes out of 64 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.032: [vfs7552] QUERY DATA READY completed successfully 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.032: [vfs7552] CAPTURE_NUM_STATES entering state 1 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.032: [vfs7552] CAPTURE_NUM_STATES entering state 0 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.032: [vfs7552] QUERY DATA READY entering state 0 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.032: Sending vfs7552_is_image_ready 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.033: [vfs7552] QUERY DATA READY entering state 1 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.033: Receiving 64 bytes 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.033: Got 6 bytes out of 64 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.033: [vfs7552] QUERY DATA READY completed successfully 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.033: [vfs7552] CAPTURE_NUM_STATES entering state 1 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.033: [vfs7552] CAPTURE_NUM_STATES entering state 0 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.033: [vfs7552] QUERY DATA READY entering state 0 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.033: Sending vfs7552_is_image_ready 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.034: [vfs7552] QUERY DATA READY entering state 1 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.034: Receiving 64 bytes 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.034: Got 6 bytes out of 64 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.034: [vfs7552] QUERY DATA READY completed successfully 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.034: [vfs7552] CAPTURE_NUM_STATES entering state 1 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.034: [vfs7552] CAPTURE_NUM_STATES entering state 0 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.034: [vfs7552] QUERY DATA READY entering state 0 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.034: Sending vfs7552_is_image_ready 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.035: [vfs7552] QUERY DATA READY entering state 1 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.035: Receiving 64 bytes 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.035: Got 6 bytes out of 64 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.035: [vfs7552] QUERY DATA READY completed successfully 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.035: [vfs7552] CAPTURE_NUM_STATES entering state 1 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.035: [vfs7552] CAPTURE_NUM_STATES entering state 0 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.035: [vfs7552] QUERY DATA READY entering state 0 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.035: Sending vfs7552_is_image_ready 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.035: [vfs7552] QUERY DATA READY entering state 1 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.035: Receiving 64 bytes 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.036: Got 6 bytes out of 64 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.036: [vfs7552] QUERY DATA READY completed successfully 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.036: [vfs7552] CAPTURE_NUM_STATES entering state 1 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.036: [vfs7552] CAPTURE_NUM_STATES entering state 0 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.036: [vfs7552] QUERY DATA READY entering state 0 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.036: Sending vfs7552_is_image_ready 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.036: [vfs7552] QUERY DATA READY entering state 1 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.036: Receiving 64 bytes 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.037: Got 6 bytes out of 64 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.037: [vfs7552] QUERY DATA READY completed successfully 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.037: [vfs7552] CAPTURE_NUM_STATES entering state 1 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.037: [vfs7552] CAPTURE_NUM_STATES entering state 0 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.037: [vfs7552] QUERY DATA READY entering state 0 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.037: Sending vfs7552_is_image_ready 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.037: [vfs7552] QUERY DATA READY entering state 1 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.037: Receiving 64 bytes 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.038: Got 6 bytes out of 64 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.038: [vfs7552] QUERY DATA READY completed successfully 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.038: [vfs7552] CAPTURE_NUM_STATES entering state 1 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.038: [vfs7552] CAPTURE_NUM_STATES entering state 0 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.038: [vfs7552] QUERY DATA READY entering state 0 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.038: Sending vfs7552_is_image_ready 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.038: [vfs7552] QUERY DATA READY entering state 1 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.038: Receiving 64 bytes 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.039: Got 6 bytes out of 64 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.039: [vfs7552] QUERY DATA READY completed successfully 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.039: [vfs7552] CAPTURE_NUM_STATES entering state 1 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.039: [vfs7552] CAPTURE_NUM_STATES entering state 0 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.039: [vfs7552] QUERY DATA READY entering state 0 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.039: Sending vfs7552_is_image_ready 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.039: [vfs7552] QUERY DATA READY entering state 1 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.039: Receiving 64 bytes 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.040: Got 6 bytes out of 64 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.040: [vfs7552] QUERY DATA READY completed successfully 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.040: [vfs7552] CAPTURE_NUM_STATES entering state 1 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.040: [vfs7552] CAPTURE_NUM_STATES entering state 0 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.040: [vfs7552] QUERY DATA READY entering state 0 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.040: Sending vfs7552_is_image_ready 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.040: [vfs7552] QUERY DATA READY entering state 1 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.040: Receiving 64 bytes 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.041: Got 6 bytes out of 64 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.041: [vfs7552] QUERY DATA READY completed successfully 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.041: [vfs7552] CAPTURE_NUM_STATES entering state 1 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.041: [vfs7552] CAPTURE_NUM_STATES entering state 0 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.041: [vfs7552] QUERY DATA READY entering state 0 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.041: Sending vfs7552_is_image_ready 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.041: [vfs7552] QUERY DATA READY entering state 1 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.041: Receiving 64 bytes 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.041: Got 6 bytes out of 64 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.042: [vfs7552] QUERY DATA READY completed successfully 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.042: [vfs7552] CAPTURE_NUM_STATES entering state 1 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.042: [vfs7552] CAPTURE_NUM_STATES entering state 0 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.042: [vfs7552] QUERY DATA READY entering state 0 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.042: Sending vfs7552_is_image_ready 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.042: [vfs7552] QUERY DATA READY entering state 1 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.042: Receiving 64 bytes 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.042: Got 6 bytes out of 64 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.042: [vfs7552] QUERY DATA READY completed successfully 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.042: [vfs7552] CAPTURE_NUM_STATES entering state 1 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.042: [vfs7552] CAPTURE_NUM_STATES entering state 0 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.042: [vfs7552] QUERY DATA READY entering state 0 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.042: Sending vfs7552_is_image_ready 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.043: [vfs7552] QUERY DATA READY entering state 1 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.043: Receiving 64 bytes 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.043: Got 6 bytes out of 64 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.043: [vfs7552] QUERY DATA READY completed successfully 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.043: [vfs7552] CAPTURE_NUM_STATES entering state 1 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.043: [vfs7552] CAPTURE_NUM_STATES entering state 0 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.043: [vfs7552] QUERY DATA READY entering state 0 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.043: Sending vfs7552_is_image_ready 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.044: [vfs7552] QUERY DATA READY entering state 1 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.044: Receiving 64 bytes 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.044: Got 6 bytes out of 64 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.044: [vfs7552] QUERY DATA READY completed successfully 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.044: [vfs7552] CAPTURE_NUM_STATES entering state 1 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.044: [vfs7552] CAPTURE_NUM_STATES entering state 0 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.044: [vfs7552] QUERY DATA READY entering state 0 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.044: Sending vfs7552_is_image_ready 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.045: [vfs7552] QUERY DATA READY entering state 1 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.045: Receiving 64 bytes 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.045: Got 6 bytes out of 64 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.045: [vfs7552] QUERY DATA READY completed successfully 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.045: [vfs7552] CAPTURE_NUM_STATES entering state 1 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.045: [vfs7552] CAPTURE_NUM_STATES entering state 0 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.045: [vfs7552] QUERY DATA READY entering state 0 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.045: Sending vfs7552_is_image_ready 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.046: [vfs7552] QUERY DATA READY entering state 1 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.046: Receiving 64 bytes 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.046: Got 6 bytes out of 64 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.046: [vfs7552] QUERY DATA READY completed successfully 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.046: [vfs7552] CAPTURE_NUM_STATES entering state 1 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.046: [vfs7552] CAPTURE_NUM_STATES entering state 0 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.046: [vfs7552] QUERY DATA READY entering state 0 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.046: Sending vfs7552_is_image_ready 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.047: [vfs7552] QUERY DATA READY entering state 1 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.047: Receiving 64 bytes 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.047: Got 6 bytes out of 64 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.047: [vfs7552] QUERY DATA READY completed successfully 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.047: [vfs7552] CAPTURE_NUM_STATES entering state 1 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.047: [vfs7552] CAPTURE_NUM_STATES entering state 0 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.047: [vfs7552] QUERY DATA READY entering state 0 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.047: Sending vfs7552_is_image_ready 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.048: [vfs7552] QUERY DATA READY entering state 1 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.048: Receiving 64 bytes 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.048: Got 6 bytes out of 64 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.048: [vfs7552] QUERY DATA READY completed successfully 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.048: [vfs7552] CAPTURE_NUM_STATES entering state 1 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.048: [vfs7552] CAPTURE_NUM_STATES entering state 0 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.048: [vfs7552] QUERY DATA READY entering state 0 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.048: Sending vfs7552_is_image_ready 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.048: [vfs7552] QUERY DATA READY entering state 1 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.049: Receiving 64 bytes 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.049: Got 6 bytes out of 64 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.049: [vfs7552] QUERY DATA READY completed successfully 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.049: [vfs7552] CAPTURE_NUM_STATES entering state 1 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.049: [vfs7552] CAPTURE_NUM_STATES entering state 0 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.049: [vfs7552] QUERY DATA READY entering state 0 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.049: Sending vfs7552_is_image_ready 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.049: [vfs7552] QUERY DATA READY entering state 1 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.049: Receiving 64 bytes 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.050: Got 6 bytes out of 64 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.050: [vfs7552] QUERY DATA READY completed successfully 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.050: [vfs7552] CAPTURE_NUM_STATES entering state 1 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.050: [vfs7552] CAPTURE_NUM_STATES entering state 0 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.050: [vfs7552] QUERY DATA READY entering state 0 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.050: Sending vfs7552_is_image_ready 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.050: [vfs7552] QUERY DATA READY entering state 1 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.050: Receiving 64 bytes 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.051: Got 6 bytes out of 64 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.051: [vfs7552] QUERY DATA READY completed successfully 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.051: [vfs7552] CAPTURE_NUM_STATES entering state 1 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.051: [vfs7552] CAPTURE_NUM_STATES entering state 0 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.051: [vfs7552] QUERY DATA READY entering state 0 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.051: Sending vfs7552_is_image_ready 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.051: [vfs7552] QUERY DATA READY entering state 1 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.051: Receiving 64 bytes 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.052: Got 6 bytes out of 64 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.052: [vfs7552] QUERY DATA READY completed successfully 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.052: [vfs7552] CAPTURE_NUM_STATES entering state 1 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.052: [vfs7552] CAPTURE_NUM_STATES entering state 0 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.052: [vfs7552] QUERY DATA READY entering state 0 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.052: Sending vfs7552_is_image_ready 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.052: [vfs7552] QUERY DATA READY entering state 1 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.052: Receiving 64 bytes 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.053: Got 6 bytes out of 64 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.053: [vfs7552] QUERY DATA READY completed successfully 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.053: [vfs7552] CAPTURE_NUM_STATES entering state 1 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.053: [vfs7552] CAPTURE_NUM_STATES entering state 0 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.053: [vfs7552] QUERY DATA READY entering state 0 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.053: Sending vfs7552_is_image_ready 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.053: [vfs7552] QUERY DATA READY entering state 1 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.053: Receiving 64 bytes 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.054: Got 6 bytes out of 64 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.054: [vfs7552] QUERY DATA READY completed successfully 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.054: [vfs7552] CAPTURE_NUM_STATES entering state 1 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.054: [vfs7552] CAPTURE_NUM_STATES entering state 0 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.054: [vfs7552] QUERY DATA READY entering state 0 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.054: Sending vfs7552_is_image_ready 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.054: [vfs7552] QUERY DATA READY entering state 1 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.054: Receiving 64 bytes 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.055: Got 6 bytes out of 64 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.055: [vfs7552] QUERY DATA READY completed successfully 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.055: [vfs7552] CAPTURE_NUM_STATES entering state 1 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.055: [vfs7552] CAPTURE_NUM_STATES entering state 0 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.055: [vfs7552] QUERY DATA READY entering state 0 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.055: Sending vfs7552_is_image_ready 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.055: [vfs7552] QUERY DATA READY entering state 1 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.055: Receiving 64 bytes 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.056: Got 6 bytes out of 64 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.056: [vfs7552] QUERY DATA READY completed successfully 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.056: [vfs7552] CAPTURE_NUM_STATES entering state 1 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.056: [vfs7552] CAPTURE_NUM_STATES entering state 0 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.056: [vfs7552] QUERY DATA READY entering state 0 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.056: Sending vfs7552_is_image_ready 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.056: [vfs7552] QUERY DATA READY entering state 1 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.056: Receiving 64 bytes 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.057: Got 6 bytes out of 64 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.057: [vfs7552] QUERY DATA READY completed successfully 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.057: [vfs7552] CAPTURE_NUM_STATES entering state 1 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.057: [vfs7552] CAPTURE_NUM_STATES entering state 0 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.057: [vfs7552] QUERY DATA READY entering state 0 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.057: Sending vfs7552_is_image_ready 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.057: [vfs7552] QUERY DATA READY entering state 1 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.057: Receiving 64 bytes 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.058: Got 6 bytes out of 64 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.058: [vfs7552] QUERY DATA READY completed successfully 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.058: [vfs7552] CAPTURE_NUM_STATES entering state 1 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.058: [vfs7552] CAPTURE_NUM_STATES entering state 0 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.058: [vfs7552] QUERY DATA READY entering state 0 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.058: Sending vfs7552_is_image_ready 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.058: [vfs7552] QUERY DATA READY entering state 1 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.058: Receiving 64 bytes 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.059: Got 6 bytes out of 64 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.059: [vfs7552] QUERY DATA READY completed successfully 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.059: [vfs7552] CAPTURE_NUM_STATES entering state 1 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.059: [vfs7552] CAPTURE_NUM_STATES entering state 0 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.059: [vfs7552] QUERY DATA READY entering state 0 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.059: Sending vfs7552_is_image_ready 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.059: [vfs7552] QUERY DATA READY entering state 1 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.059: Receiving 64 bytes 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.059: Got 6 bytes out of 64 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.059: [vfs7552] QUERY DATA READY completed successfully 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.059: [vfs7552] CAPTURE_NUM_STATES entering state 1 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.059: [vfs7552] CAPTURE_NUM_STATES entering state 0 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.059: [vfs7552] QUERY DATA READY entering state 0 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.059: Sending vfs7552_is_image_ready 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.060: [vfs7552] QUERY DATA READY entering state 1 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.060: Receiving 64 bytes 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.060: Got 6 bytes out of 64 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.060: [vfs7552] QUERY DATA READY completed successfully 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.061: [vfs7552] CAPTURE_NUM_STATES entering state 1 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.061: [vfs7552] CAPTURE_NUM_STATES entering state 0 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.061: [vfs7552] QUERY DATA READY entering state 0 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.061: Sending vfs7552_is_image_ready 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.061: [vfs7552] QUERY DATA READY entering state 1 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.061: Receiving 64 bytes 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.061: Got 6 bytes out of 64 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.061: [vfs7552] QUERY DATA READY completed successfully 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.061: [vfs7552] CAPTURE_NUM_STATES entering state 1 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.061: [vfs7552] CAPTURE_NUM_STATES entering state 0 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.061: [vfs7552] QUERY DATA READY entering state 0 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.061: Sending vfs7552_is_image_ready 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.062: [vfs7552] QUERY DATA READY entering state 1 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.062: Receiving 64 bytes 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.062: Got 6 bytes out of 64 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.062: [vfs7552] QUERY DATA READY completed successfully 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.062: [vfs7552] CAPTURE_NUM_STATES entering state 1 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.062: [vfs7552] CAPTURE_NUM_STATES entering state 0 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.062: [vfs7552] QUERY DATA READY entering state 0 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.062: Sending vfs7552_is_image_ready 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.063: [vfs7552] QUERY DATA READY entering state 1 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.063: Receiving 64 bytes 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.063: Got 6 bytes out of 64 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.063: [vfs7552] QUERY DATA READY completed successfully 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.063: [vfs7552] CAPTURE_NUM_STATES entering state 1 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.063: [vfs7552] CAPTURE_NUM_STATES entering state 0 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.063: [vfs7552] QUERY DATA READY entering state 0 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.063: Sending vfs7552_is_image_ready 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.064: [vfs7552] QUERY DATA READY entering state 1 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.064: Receiving 64 bytes 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.064: Got 6 bytes out of 64 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.064: [vfs7552] QUERY DATA READY completed successfully 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.064: [vfs7552] CAPTURE_NUM_STATES entering state 1 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.064: [vfs7552] CAPTURE_NUM_STATES entering state 0 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.064: [vfs7552] QUERY DATA READY entering state 0 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.064: Sending vfs7552_is_image_ready 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.065: [vfs7552] QUERY DATA READY entering state 1 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.065: Receiving 64 bytes 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.065: Got 6 bytes out of 64 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.065: [vfs7552] QUERY DATA READY completed successfully 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.065: [vfs7552] CAPTURE_NUM_STATES entering state 1 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.065: [vfs7552] CAPTURE_NUM_STATES entering state 0 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.065: [vfs7552] QUERY DATA READY entering state 0 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.065: Sending vfs7552_is_image_ready 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.066: [vfs7552] QUERY DATA READY entering state 1 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.066: Receiving 64 bytes 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.066: Got 6 bytes out of 64 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.066: [vfs7552] QUERY DATA READY completed successfully 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.066: [vfs7552] CAPTURE_NUM_STATES entering state 1 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.066: [vfs7552] CAPTURE_NUM_STATES entering state 0 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.066: [vfs7552] QUERY DATA READY entering state 0 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.066: Sending vfs7552_is_image_ready 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.067: [vfs7552] QUERY DATA READY entering state 1 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.067: Receiving 64 bytes 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.067: Got 6 bytes out of 64 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.067: [vfs7552] QUERY DATA READY completed successfully 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.067: [vfs7552] CAPTURE_NUM_STATES entering state 1 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.067: [vfs7552] CAPTURE_NUM_STATES entering state 0 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.067: [vfs7552] QUERY DATA READY entering state 0 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.067: Sending vfs7552_is_image_ready 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.067: [vfs7552] QUERY DATA READY entering state 1 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.067: Receiving 64 bytes 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.068: Got 6 bytes out of 64 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.068: [vfs7552] QUERY DATA READY completed successfully 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.068: [vfs7552] CAPTURE_NUM_STATES entering state 1 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.068: [vfs7552] CAPTURE_NUM_STATES entering state 0 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.068: [vfs7552] QUERY DATA READY entering state 0 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.068: Sending vfs7552_is_image_ready 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.068: [vfs7552] QUERY DATA READY entering state 1 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.068: Receiving 64 bytes 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.069: Got 6 bytes out of 64 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.069: [vfs7552] QUERY DATA READY completed successfully 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.069: [vfs7552] CAPTURE_NUM_STATES entering state 1 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.069: [vfs7552] CAPTURE_NUM_STATES entering state 0 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.069: [vfs7552] QUERY DATA READY entering state 0 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.069: Sending vfs7552_is_image_ready 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.069: [vfs7552] QUERY DATA READY entering state 1 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.069: Receiving 64 bytes 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.070: Got 6 bytes out of 64 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.070: [vfs7552] QUERY DATA READY completed successfully 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.070: [vfs7552] CAPTURE_NUM_STATES entering state 1 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.070: [vfs7552] CAPTURE_NUM_STATES entering state 0 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.070: [vfs7552] QUERY DATA READY entering state 0 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.070: Sending vfs7552_is_image_ready 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.070: [vfs7552] QUERY DATA READY entering state 1 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.070: Receiving 64 bytes 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.071: Got 6 bytes out of 64 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.071: [vfs7552] QUERY DATA READY completed successfully 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.071: [vfs7552] CAPTURE_NUM_STATES entering state 1 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.071: [vfs7552] CAPTURE_NUM_STATES entering state 0 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.071: [vfs7552] QUERY DATA READY entering state 0 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.071: Sending vfs7552_is_image_ready 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.071: [vfs7552] QUERY DATA READY entering state 1 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.071: Receiving 64 bytes 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.072: Got 6 bytes out of 64 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.072: [vfs7552] QUERY DATA READY completed successfully 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.072: [vfs7552] CAPTURE_NUM_STATES entering state 1 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.072: [vfs7552] CAPTURE_NUM_STATES entering state 0 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.072: [vfs7552] QUERY DATA READY entering state 0 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.072: Sending vfs7552_is_image_ready 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.072: [vfs7552] QUERY DATA READY entering state 1 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.072: Receiving 64 bytes 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.073: Got 6 bytes out of 64 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.073: [vfs7552] QUERY DATA READY completed successfully 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.073: [vfs7552] CAPTURE_NUM_STATES entering state 1 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.073: [vfs7552] CAPTURE_NUM_STATES entering state 0 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.073: [vfs7552] QUERY DATA READY entering state 0 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.073: Sending vfs7552_is_image_ready 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.073: [vfs7552] QUERY DATA READY entering state 1 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.073: Receiving 64 bytes 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.074: Got 6 bytes out of 64 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.074: [vfs7552] QUERY DATA READY completed successfully 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.074: [vfs7552] CAPTURE_NUM_STATES entering state 1 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.074: [vfs7552] CAPTURE_NUM_STATES entering state 0 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.074: [vfs7552] QUERY DATA READY entering state 0 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.074: Sending vfs7552_is_image_ready 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.074: [vfs7552] QUERY DATA READY entering state 1 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.074: Receiving 64 bytes 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.075: Got 6 bytes out of 64 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.075: [vfs7552] QUERY DATA READY completed successfully 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.075: [vfs7552] CAPTURE_NUM_STATES entering state 1 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.075: [vfs7552] CAPTURE_NUM_STATES entering state 0 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.075: [vfs7552] QUERY DATA READY entering state 0 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.075: Sending vfs7552_is_image_ready 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.075: [vfs7552] QUERY DATA READY entering state 1 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.075: Receiving 64 bytes 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.075: Got 6 bytes out of 64 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.076: [vfs7552] QUERY DATA READY completed successfully 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.076: [vfs7552] CAPTURE_NUM_STATES entering state 1 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.076: [vfs7552] CAPTURE_NUM_STATES entering state 0 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.076: [vfs7552] QUERY DATA READY entering state 0 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.076: Sending vfs7552_is_image_ready 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.076: [vfs7552] QUERY DATA READY entering state 1 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.076: Receiving 64 bytes 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.077: Got 6 bytes out of 64 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.077: [vfs7552] QUERY DATA READY completed successfully 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.077: [vfs7552] CAPTURE_NUM_STATES entering state 1 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.077: [vfs7552] CAPTURE_NUM_STATES entering state 0 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.077: [vfs7552] QUERY DATA READY entering state 0 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.077: Sending vfs7552_is_image_ready 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.077: [vfs7552] QUERY DATA READY entering state 1 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.077: Receiving 64 bytes 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.077: Got 6 bytes out of 64 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.077: [vfs7552] QUERY DATA READY completed successfully 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.077: [vfs7552] CAPTURE_NUM_STATES entering state 1 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.077: [vfs7552] CAPTURE_NUM_STATES entering state 0 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.077: [vfs7552] QUERY DATA READY entering state 0 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.077: Sending vfs7552_is_image_ready 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.078: [vfs7552] QUERY DATA READY entering state 1 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.078: Receiving 64 bytes 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.078: Got 6 bytes out of 64 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.078: [vfs7552] QUERY DATA READY completed successfully 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.078: [vfs7552] CAPTURE_NUM_STATES entering state 1 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.078: [vfs7552] CAPTURE_NUM_STATES entering state 0 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.078: [vfs7552] QUERY DATA READY entering state 0 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.078: Sending vfs7552_is_image_ready 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.079: [vfs7552] QUERY DATA READY entering state 1 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.079: Receiving 64 bytes 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.079: Got 6 bytes out of 64 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.079: [vfs7552] QUERY DATA READY completed successfully 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.079: [vfs7552] CAPTURE_NUM_STATES entering state 1 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.079: [vfs7552] CAPTURE_NUM_STATES entering state 0 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.079: [vfs7552] QUERY DATA READY entering state 0 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.079: Sending vfs7552_is_image_ready 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.080: [vfs7552] QUERY DATA READY entering state 1 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.080: Receiving 64 bytes 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.080: Got 6 bytes out of 64 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.080: [vfs7552] QUERY DATA READY completed successfully 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.080: [vfs7552] CAPTURE_NUM_STATES entering state 1 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.080: [vfs7552] CAPTURE_NUM_STATES entering state 2 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.080: [vfs7552] REQUEST CHUNK entering state 0 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.080: Sending vfs7552_read_image_chunk 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.081: [vfs7552] REQUEST CHUNK completed successfully 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.081: [vfs7552] CAPTURE_NUM_STATES entering state 3 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.081: [vfs7552] CAPTURE_NUM_STATES entering state 2 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.081: [vfs7552] REQUEST CHUNK entering state 0 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.081: Sending vfs7552_read_image_chunk 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.082: [vfs7552] REQUEST CHUNK completed successfully 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.082: [vfs7552] CAPTURE_NUM_STATES entering state 3 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.082: [vfs7552] CAPTURE_NUM_STATES entering state 2 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.082: [vfs7552] REQUEST CHUNK entering state 0 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.082: Sending vfs7552_read_image_chunk 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.083: [vfs7552] REQUEST CHUNK completed successfully 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.083: [vfs7552] CAPTURE_NUM_STATES entering state 3 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.083: [vfs7552] CAPTURE_NUM_STATES entering state 4 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.083: Cleaning image 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.083: variance_after = 1532 184s 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.083: [vfs7552] CAPTURE_NUM_STATES entering state 0 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.083: [vfs7552] QUERY DATA READY entering state 0 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.083: Sending vfs7552_is_image_ready 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.084: [vfs7552] QUERY DATA READY entering state 1 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.084: Receiving 64 bytes 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.084: Got 6 bytes out of 64 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.084: [vfs7552] QUERY DATA READY completed successfully 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.084: [vfs7552] CAPTURE_NUM_STATES entering state 1 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.084: [vfs7552] CAPTURE_NUM_STATES entering state 0 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.084: [vfs7552] QUERY DATA READY entering state 0 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.084: Sending vfs7552_is_image_ready 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.085: [vfs7552] QUERY DATA READY entering state 1 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.085: Receiving 64 bytes 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.085: Got 6 bytes out of 64 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.085: [vfs7552] QUERY DATA READY completed successfully 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.085: [vfs7552] CAPTURE_NUM_STATES entering state 1 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.085: [vfs7552] CAPTURE_NUM_STATES entering state 0 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.085: [vfs7552] QUERY DATA READY entering state 0 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.085: Sending vfs7552_is_image_ready 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.086: [vfs7552] QUERY DATA READY entering state 1 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.086: Receiving 64 bytes 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.086: Got 6 bytes out of 64 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.086: [vfs7552] QUERY DATA READY completed successfully 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.086: [vfs7552] CAPTURE_NUM_STATES entering state 1 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.086: [vfs7552] CAPTURE_NUM_STATES entering state 0 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.086: [vfs7552] QUERY DATA READY entering state 0 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.086: Sending vfs7552_is_image_ready 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.087: [vfs7552] QUERY DATA READY entering state 1 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.087: Receiving 64 bytes 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.087: Got 6 bytes out of 64 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.087: [vfs7552] QUERY DATA READY completed successfully 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.087: [vfs7552] CAPTURE_NUM_STATES entering state 1 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.087: [vfs7552] CAPTURE_NUM_STATES entering state 0 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.087: [vfs7552] QUERY DATA READY entering state 0 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.087: Sending vfs7552_is_image_ready 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.088: [vfs7552] QUERY DATA READY entering state 1 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.088: Receiving 64 bytes 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.088: Got 6 bytes out of 64 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.088: [vfs7552] QUERY DATA READY completed successfully 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.088: [vfs7552] CAPTURE_NUM_STATES entering state 1 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.088: [vfs7552] CAPTURE_NUM_STATES entering state 0 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.088: [vfs7552] QUERY DATA READY entering state 0 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.088: Sending vfs7552_is_image_ready 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.089: [vfs7552] QUERY DATA READY entering state 1 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.089: Receiving 64 bytes 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.089: Got 6 bytes out of 64 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.089: [vfs7552] QUERY DATA READY completed successfully 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.089: [vfs7552] CAPTURE_NUM_STATES entering state 1 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.089: [vfs7552] CAPTURE_NUM_STATES entering state 0 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.089: [vfs7552] QUERY DATA READY entering state 0 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.089: Sending vfs7552_is_image_ready 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.090: [vfs7552] QUERY DATA READY entering state 1 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.090: Receiving 64 bytes 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.090: Got 6 bytes out of 64 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.090: [vfs7552] QUERY DATA READY completed successfully 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.090: [vfs7552] CAPTURE_NUM_STATES entering state 1 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.090: [vfs7552] CAPTURE_NUM_STATES entering state 0 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.090: [vfs7552] QUERY DATA READY entering state 0 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.090: Sending vfs7552_is_image_ready 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.091: [vfs7552] QUERY DATA READY entering state 1 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.091: Receiving 64 bytes 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.091: Got 6 bytes out of 64 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.091: [vfs7552] QUERY DATA READY completed successfully 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.091: [vfs7552] CAPTURE_NUM_STATES entering state 1 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.091: [vfs7552] CAPTURE_NUM_STATES entering state 0 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.091: [vfs7552] QUERY DATA READY entering state 0 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.091: Sending vfs7552_is_image_ready 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.091: [vfs7552] QUERY DATA READY entering state 1 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.092: Receiving 64 bytes 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.092: Got 6 bytes out of 64 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.092: [vfs7552] QUERY DATA READY completed successfully 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.092: [vfs7552] CAPTURE_NUM_STATES entering state 1 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.092: [vfs7552] CAPTURE_NUM_STATES entering state 0 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.092: [vfs7552] QUERY DATA READY entering state 0 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.092: Sending vfs7552_is_image_ready 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.092: [vfs7552] QUERY DATA READY entering state 1 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.093: Receiving 64 bytes 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.093: Got 6 bytes out of 64 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.093: [vfs7552] QUERY DATA READY completed successfully 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.093: [vfs7552] CAPTURE_NUM_STATES entering state 1 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.093: [vfs7552] CAPTURE_NUM_STATES entering state 0 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.093: [vfs7552] QUERY DATA READY entering state 0 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.093: Sending vfs7552_is_image_ready 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.093: [vfs7552] QUERY DATA READY entering state 1 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.093: Receiving 64 bytes 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.094: Got 6 bytes out of 64 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.094: [vfs7552] QUERY DATA READY completed successfully 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.094: [vfs7552] CAPTURE_NUM_STATES entering state 1 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.094: [vfs7552] CAPTURE_NUM_STATES entering state 0 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.094: [vfs7552] QUERY DATA READY entering state 0 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.094: Sending vfs7552_is_image_ready 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.094: [vfs7552] QUERY DATA READY entering state 1 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.094: Receiving 64 bytes 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.095: Got 6 bytes out of 64 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.095: [vfs7552] QUERY DATA READY completed successfully 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.095: [vfs7552] CAPTURE_NUM_STATES entering state 1 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.095: [vfs7552] CAPTURE_NUM_STATES entering state 0 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.095: [vfs7552] QUERY DATA READY entering state 0 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.095: Sending vfs7552_is_image_ready 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.095: [vfs7552] QUERY DATA READY entering state 1 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.095: Receiving 64 bytes 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.096: Got 6 bytes out of 64 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.096: [vfs7552] QUERY DATA READY completed successfully 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.096: [vfs7552] CAPTURE_NUM_STATES entering state 1 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.096: [vfs7552] CAPTURE_NUM_STATES entering state 0 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.096: [vfs7552] QUERY DATA READY entering state 0 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.096: Sending vfs7552_is_image_ready 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.096: [vfs7552] QUERY DATA READY entering state 1 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.096: Receiving 64 bytes 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.097: Got 6 bytes out of 64 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.097: [vfs7552] QUERY DATA READY completed successfully 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.097: [vfs7552] CAPTURE_NUM_STATES entering state 1 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.097: [vfs7552] CAPTURE_NUM_STATES entering state 0 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.097: [vfs7552] QUERY DATA READY entering state 0 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.097: Sending vfs7552_is_image_ready 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.097: [vfs7552] QUERY DATA READY entering state 1 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.097: Receiving 64 bytes 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.098: Got 6 bytes out of 64 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.098: [vfs7552] QUERY DATA READY completed successfully 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.098: [vfs7552] CAPTURE_NUM_STATES entering state 1 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.098: [vfs7552] CAPTURE_NUM_STATES entering state 0 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.098: [vfs7552] QUERY DATA READY entering state 0 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.098: Sending vfs7552_is_image_ready 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.098: [vfs7552] QUERY DATA READY entering state 1 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.098: Receiving 64 bytes 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.099: Got 6 bytes out of 64 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.099: [vfs7552] QUERY DATA READY completed successfully 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.099: [vfs7552] CAPTURE_NUM_STATES entering state 1 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.099: [vfs7552] CAPTURE_NUM_STATES entering state 0 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.099: [vfs7552] QUERY DATA READY entering state 0 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.099: Sending vfs7552_is_image_ready 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.099: [vfs7552] QUERY DATA READY entering state 1 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.099: Receiving 64 bytes 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.100: Got 6 bytes out of 64 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.100: [vfs7552] QUERY DATA READY completed successfully 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.100: [vfs7552] CAPTURE_NUM_STATES entering state 1 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.100: [vfs7552] CAPTURE_NUM_STATES entering state 0 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.100: [vfs7552] QUERY DATA READY entering state 0 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.100: Sending vfs7552_is_image_ready 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.100: [vfs7552] QUERY DATA READY entering state 1 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.100: Receiving 64 bytes 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.101: Got 6 bytes out of 64 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.101: [vfs7552] QUERY DATA READY completed successfully 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.101: [vfs7552] CAPTURE_NUM_STATES entering state 1 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.101: [vfs7552] CAPTURE_NUM_STATES entering state 0 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.101: [vfs7552] QUERY DATA READY entering state 0 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.101: Sending vfs7552_is_image_ready 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.101: [vfs7552] QUERY DATA READY entering state 1 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.101: Receiving 64 bytes 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.102: Got 6 bytes out of 64 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.102: [vfs7552] QUERY DATA READY completed successfully 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.102: [vfs7552] CAPTURE_NUM_STATES entering state 1 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.102: [vfs7552] CAPTURE_NUM_STATES entering state 0 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.102: [vfs7552] QUERY DATA READY entering state 0 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.102: Sending vfs7552_is_image_ready 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.102: [vfs7552] QUERY DATA READY entering state 1 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.102: Receiving 64 bytes 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.103: Got 6 bytes out of 64 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.103: [vfs7552] QUERY DATA READY completed successfully 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.103: [vfs7552] CAPTURE_NUM_STATES entering state 1 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.103: [vfs7552] CAPTURE_NUM_STATES entering state 0 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.103: [vfs7552] QUERY DATA READY entering state 0 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.103: Sending vfs7552_is_image_ready 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.103: [vfs7552] QUERY DATA READY entering state 1 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.103: Receiving 64 bytes 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.104: Got 6 bytes out of 64 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.104: [vfs7552] QUERY DATA READY completed successfully 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.104: [vfs7552] CAPTURE_NUM_STATES entering state 1 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.104: [vfs7552] CAPTURE_NUM_STATES entering state 0 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.104: [vfs7552] QUERY DATA READY entering state 0 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.104: Sending vfs7552_is_image_ready 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.104: [vfs7552] QUERY DATA READY entering state 1 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.104: Receiving 64 bytes 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.105: Got 6 bytes out of 64 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.105: [vfs7552] QUERY DATA READY completed successfully 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.105: [vfs7552] CAPTURE_NUM_STATES entering state 1 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.105: [vfs7552] CAPTURE_NUM_STATES entering state 0 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.105: [vfs7552] QUERY DATA READY entering state 0 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.105: Sending vfs7552_is_image_ready 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.105: [vfs7552] QUERY DATA READY entering state 1 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.105: Receiving 64 bytes 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.106: Got 6 bytes out of 64 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.106: [vfs7552] QUERY DATA READY completed successfully 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.106: [vfs7552] CAPTURE_NUM_STATES entering state 1 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.106: [vfs7552] CAPTURE_NUM_STATES entering state 0 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.106: [vfs7552] QUERY DATA READY entering state 0 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.106: Sending vfs7552_is_image_ready 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.106: [vfs7552] QUERY DATA READY entering state 1 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.106: Receiving 64 bytes 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.107: Got 6 bytes out of 64 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.107: [vfs7552] QUERY DATA READY completed successfully 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.107: [vfs7552] CAPTURE_NUM_STATES entering state 1 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.107: [vfs7552] CAPTURE_NUM_STATES entering state 0 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.107: [vfs7552] QUERY DATA READY entering state 0 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.107: Sending vfs7552_is_image_ready 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.107: [vfs7552] QUERY DATA READY entering state 1 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.107: Receiving 64 bytes 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.107: Got 6 bytes out of 64 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.108: [vfs7552] QUERY DATA READY completed successfully 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.108: [vfs7552] CAPTURE_NUM_STATES entering state 1 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.108: [vfs7552] CAPTURE_NUM_STATES entering state 0 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.108: [vfs7552] QUERY DATA READY entering state 0 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.108: Sending vfs7552_is_image_ready 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.108: [vfs7552] QUERY DATA READY entering state 1 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.108: Receiving 64 bytes 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.108: Got 6 bytes out of 64 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.109: [vfs7552] QUERY DATA READY completed successfully 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.109: [vfs7552] CAPTURE_NUM_STATES entering state 1 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.109: [vfs7552] CAPTURE_NUM_STATES entering state 0 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.109: [vfs7552] QUERY DATA READY entering state 0 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.109: Sending vfs7552_is_image_ready 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.109: [vfs7552] QUERY DATA READY entering state 1 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.109: Receiving 64 bytes 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.110: Got 6 bytes out of 64 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.110: [vfs7552] QUERY DATA READY completed successfully 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.110: [vfs7552] CAPTURE_NUM_STATES entering state 1 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.110: [vfs7552] CAPTURE_NUM_STATES entering state 0 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.110: [vfs7552] QUERY DATA READY entering state 0 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.110: Sending vfs7552_is_image_ready 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.110: [vfs7552] QUERY DATA READY entering state 1 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.110: Receiving 64 bytes 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.110: Got 6 bytes out of 64 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.110: [vfs7552] QUERY DATA READY completed successfully 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.110: [vfs7552] CAPTURE_NUM_STATES entering state 1 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.110: [vfs7552] CAPTURE_NUM_STATES entering state 0 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.110: [vfs7552] QUERY DATA READY entering state 0 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.110: Sending vfs7552_is_image_ready 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.111: [vfs7552] QUERY DATA READY entering state 1 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.111: Receiving 64 bytes 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.111: Got 6 bytes out of 64 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.111: [vfs7552] QUERY DATA READY completed successfully 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.111: [vfs7552] CAPTURE_NUM_STATES entering state 1 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.111: [vfs7552] CAPTURE_NUM_STATES entering state 0 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.111: [vfs7552] QUERY DATA READY entering state 0 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.111: Sending vfs7552_is_image_ready 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.112: [vfs7552] QUERY DATA READY entering state 1 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.112: Receiving 64 bytes 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.112: Got 6 bytes out of 64 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.112: [vfs7552] QUERY DATA READY completed successfully 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.112: [vfs7552] CAPTURE_NUM_STATES entering state 1 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.112: [vfs7552] CAPTURE_NUM_STATES entering state 0 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.112: [vfs7552] QUERY DATA READY entering state 0 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.112: Sending vfs7552_is_image_ready 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.113: [vfs7552] QUERY DATA READY entering state 1 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.113: Receiving 64 bytes 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.113: Got 6 bytes out of 64 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.113: [vfs7552] QUERY DATA READY completed successfully 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.113: [vfs7552] CAPTURE_NUM_STATES entering state 1 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.113: [vfs7552] CAPTURE_NUM_STATES entering state 0 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.113: [vfs7552] QUERY DATA READY entering state 0 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.113: Sending vfs7552_is_image_ready 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.114: [vfs7552] QUERY DATA READY entering state 1 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.114: Receiving 64 bytes 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.114: Got 6 bytes out of 64 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.114: [vfs7552] QUERY DATA READY completed successfully 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.114: [vfs7552] CAPTURE_NUM_STATES entering state 1 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.114: [vfs7552] CAPTURE_NUM_STATES entering state 0 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.114: [vfs7552] QUERY DATA READY entering state 0 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.114: Sending vfs7552_is_image_ready 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.115: [vfs7552] QUERY DATA READY entering state 1 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.115: Receiving 64 bytes 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.115: Got 6 bytes out of 64 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.115: [vfs7552] QUERY DATA READY completed successfully 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.115: [vfs7552] CAPTURE_NUM_STATES entering state 1 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.115: [vfs7552] CAPTURE_NUM_STATES entering state 0 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.115: [vfs7552] QUERY DATA READY entering state 0 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.115: Sending vfs7552_is_image_ready 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.116: [vfs7552] QUERY DATA READY entering state 1 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.116: Receiving 64 bytes 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.116: Got 6 bytes out of 64 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.116: [vfs7552] QUERY DATA READY completed successfully 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.116: [vfs7552] CAPTURE_NUM_STATES entering state 1 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.116: [vfs7552] CAPTURE_NUM_STATES entering state 0 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.116: [vfs7552] QUERY DATA READY entering state 0 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.116: Sending vfs7552_is_image_ready 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.117: [vfs7552] QUERY DATA READY entering state 1 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.117: Receiving 64 bytes 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.117: Got 6 bytes out of 64 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.117: [vfs7552] QUERY DATA READY completed successfully 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.117: [vfs7552] CAPTURE_NUM_STATES entering state 1 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.117: [vfs7552] CAPTURE_NUM_STATES entering state 0 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.117: [vfs7552] QUERY DATA READY entering state 0 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.117: Sending vfs7552_is_image_ready 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.118: [vfs7552] QUERY DATA READY entering state 1 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.118: Receiving 64 bytes 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.118: Got 6 bytes out of 64 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.118: [vfs7552] QUERY DATA READY completed successfully 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.118: [vfs7552] CAPTURE_NUM_STATES entering state 1 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.118: [vfs7552] CAPTURE_NUM_STATES entering state 0 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.118: [vfs7552] QUERY DATA READY entering state 0 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.118: Sending vfs7552_is_image_ready 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.118: [vfs7552] QUERY DATA READY entering state 1 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.119: Receiving 64 bytes 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.119: Got 6 bytes out of 64 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.119: [vfs7552] QUERY DATA READY completed successfully 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.119: [vfs7552] CAPTURE_NUM_STATES entering state 1 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.119: [vfs7552] CAPTURE_NUM_STATES entering state 0 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.119: [vfs7552] QUERY DATA READY entering state 0 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.119: Sending vfs7552_is_image_ready 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.120: [vfs7552] QUERY DATA READY entering state 1 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.120: Receiving 64 bytes 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.120: Got 6 bytes out of 64 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.120: [vfs7552] QUERY DATA READY completed successfully 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.120: [vfs7552] CAPTURE_NUM_STATES entering state 1 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.120: [vfs7552] CAPTURE_NUM_STATES entering state 2 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.120: [vfs7552] REQUEST CHUNK entering state 0 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.120: Sending vfs7552_read_image_chunk 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.121: [vfs7552] REQUEST CHUNK completed successfully 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.121: [vfs7552] CAPTURE_NUM_STATES entering state 3 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.121: [vfs7552] CAPTURE_NUM_STATES entering state 2 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.121: [vfs7552] REQUEST CHUNK entering state 0 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.121: Sending vfs7552_read_image_chunk 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.122: [vfs7552] REQUEST CHUNK completed successfully 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.122: [vfs7552] CAPTURE_NUM_STATES entering state 3 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.122: [vfs7552] CAPTURE_NUM_STATES entering state 2 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.122: [vfs7552] REQUEST CHUNK entering state 0 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.122: Sending vfs7552_read_image_chunk 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.122: [vfs7552] REQUEST CHUNK completed successfully 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.123: [vfs7552] CAPTURE_NUM_STATES entering state 3 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.123: [vfs7552] CAPTURE_NUM_STATES entering state 4 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.123: Cleaning image 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.123: variance_after = 1691 184s 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.123: [vfs7552] CAPTURE_NUM_STATES entering state 0 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.123: [vfs7552] QUERY DATA READY entering state 0 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.123: Sending vfs7552_is_image_ready 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.123: [vfs7552] QUERY DATA READY entering state 1 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.124: Receiving 64 bytes 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.124: Got 6 bytes out of 64 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.124: [vfs7552] QUERY DATA READY completed successfully 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.124: [vfs7552] CAPTURE_NUM_STATES entering state 1 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.124: [vfs7552] CAPTURE_NUM_STATES entering state 0 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.124: [vfs7552] QUERY DATA READY entering state 0 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.124: Sending vfs7552_is_image_ready 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.125: [vfs7552] QUERY DATA READY entering state 1 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.125: Receiving 64 bytes 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.125: Got 6 bytes out of 64 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.125: [vfs7552] QUERY DATA READY completed successfully 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.125: [vfs7552] CAPTURE_NUM_STATES entering state 1 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.125: [vfs7552] CAPTURE_NUM_STATES entering state 0 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.125: [vfs7552] QUERY DATA READY entering state 0 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.125: Sending vfs7552_is_image_ready 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.125: [vfs7552] QUERY DATA READY entering state 1 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.125: Receiving 64 bytes 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.126: Got 6 bytes out of 64 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.126: [vfs7552] QUERY DATA READY completed successfully 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.126: [vfs7552] CAPTURE_NUM_STATES entering state 1 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.126: [vfs7552] CAPTURE_NUM_STATES entering state 0 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.126: [vfs7552] QUERY DATA READY entering state 0 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.126: Sending vfs7552_is_image_ready 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.126: [vfs7552] QUERY DATA READY entering state 1 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.126: Receiving 64 bytes 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.127: Got 6 bytes out of 64 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.127: [vfs7552] QUERY DATA READY completed successfully 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.127: [vfs7552] CAPTURE_NUM_STATES entering state 1 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.127: [vfs7552] CAPTURE_NUM_STATES entering state 0 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.127: [vfs7552] QUERY DATA READY entering state 0 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.127: Sending vfs7552_is_image_ready 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.127: [vfs7552] QUERY DATA READY entering state 1 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.127: Receiving 64 bytes 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.128: Got 6 bytes out of 64 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.128: [vfs7552] QUERY DATA READY completed successfully 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.128: [vfs7552] CAPTURE_NUM_STATES entering state 1 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.128: [vfs7552] CAPTURE_NUM_STATES entering state 0 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.128: [vfs7552] QUERY DATA READY entering state 0 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.128: Sending vfs7552_is_image_ready 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.128: [vfs7552] QUERY DATA READY entering state 1 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.128: Receiving 64 bytes 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.129: Got 6 bytes out of 64 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.129: [vfs7552] QUERY DATA READY completed successfully 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.129: [vfs7552] CAPTURE_NUM_STATES entering state 1 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.129: [vfs7552] CAPTURE_NUM_STATES entering state 0 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.129: [vfs7552] QUERY DATA READY entering state 0 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.129: Sending vfs7552_is_image_ready 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.129: [vfs7552] QUERY DATA READY entering state 1 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.129: Receiving 64 bytes 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.130: Got 6 bytes out of 64 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.130: [vfs7552] QUERY DATA READY completed successfully 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.130: [vfs7552] CAPTURE_NUM_STATES entering state 1 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.130: [vfs7552] CAPTURE_NUM_STATES entering state 0 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.130: [vfs7552] QUERY DATA READY entering state 0 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.130: Sending vfs7552_is_image_ready 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.130: [vfs7552] QUERY DATA READY entering state 1 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.130: Receiving 64 bytes 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.131: Got 6 bytes out of 64 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.131: [vfs7552] QUERY DATA READY completed successfully 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.131: [vfs7552] CAPTURE_NUM_STATES entering state 1 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.131: [vfs7552] CAPTURE_NUM_STATES entering state 0 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.131: [vfs7552] QUERY DATA READY entering state 0 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.131: Sending vfs7552_is_image_ready 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.131: [vfs7552] QUERY DATA READY entering state 1 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.131: Receiving 64 bytes 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.132: Got 6 bytes out of 64 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.132: [vfs7552] QUERY DATA READY completed successfully 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.132: [vfs7552] CAPTURE_NUM_STATES entering state 1 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.132: [vfs7552] CAPTURE_NUM_STATES entering state 0 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.132: [vfs7552] QUERY DATA READY entering state 0 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.132: Sending vfs7552_is_image_ready 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.132: [vfs7552] QUERY DATA READY entering state 1 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.132: Receiving 64 bytes 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.133: Got 6 bytes out of 64 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.133: [vfs7552] QUERY DATA READY completed successfully 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.133: [vfs7552] CAPTURE_NUM_STATES entering state 1 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.133: [vfs7552] CAPTURE_NUM_STATES entering state 0 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.133: [vfs7552] QUERY DATA READY entering state 0 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.133: Sending vfs7552_is_image_ready 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.133: [vfs7552] QUERY DATA READY entering state 1 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.133: Receiving 64 bytes 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.134: Got 6 bytes out of 64 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.134: [vfs7552] QUERY DATA READY completed successfully 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.134: [vfs7552] CAPTURE_NUM_STATES entering state 1 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.134: [vfs7552] CAPTURE_NUM_STATES entering state 0 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.134: [vfs7552] QUERY DATA READY entering state 0 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.134: Sending vfs7552_is_image_ready 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.134: [vfs7552] QUERY DATA READY entering state 1 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.134: Receiving 64 bytes 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.135: Got 6 bytes out of 64 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.135: [vfs7552] QUERY DATA READY completed successfully 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.135: [vfs7552] CAPTURE_NUM_STATES entering state 1 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.135: [vfs7552] CAPTURE_NUM_STATES entering state 0 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.135: [vfs7552] QUERY DATA READY entering state 0 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.135: Sending vfs7552_is_image_ready 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.135: [vfs7552] QUERY DATA READY entering state 1 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.135: Receiving 64 bytes 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.136: Got 6 bytes out of 64 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.136: [vfs7552] QUERY DATA READY completed successfully 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.136: [vfs7552] CAPTURE_NUM_STATES entering state 1 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.136: [vfs7552] CAPTURE_NUM_STATES entering state 0 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.136: [vfs7552] QUERY DATA READY entering state 0 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.136: Sending vfs7552_is_image_ready 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.136: [vfs7552] QUERY DATA READY entering state 1 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.136: Receiving 64 bytes 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.136: Got 6 bytes out of 64 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.137: [vfs7552] QUERY DATA READY completed successfully 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.137: [vfs7552] CAPTURE_NUM_STATES entering state 1 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.137: [vfs7552] CAPTURE_NUM_STATES entering state 0 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.137: [vfs7552] QUERY DATA READY entering state 0 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.137: Sending vfs7552_is_image_ready 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.137: [vfs7552] QUERY DATA READY entering state 1 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.137: Receiving 64 bytes 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.137: Got 6 bytes out of 64 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.137: [vfs7552] QUERY DATA READY completed successfully 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.137: [vfs7552] CAPTURE_NUM_STATES entering state 1 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.137: [vfs7552] CAPTURE_NUM_STATES entering state 0 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.137: [vfs7552] QUERY DATA READY entering state 0 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.137: Sending vfs7552_is_image_ready 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.138: [vfs7552] QUERY DATA READY entering state 1 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.138: Receiving 64 bytes 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.138: Got 6 bytes out of 64 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.138: [vfs7552] QUERY DATA READY completed successfully 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.138: [vfs7552] CAPTURE_NUM_STATES entering state 1 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.138: [vfs7552] CAPTURE_NUM_STATES entering state 0 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.139: [vfs7552] QUERY DATA READY entering state 0 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.139: Sending vfs7552_is_image_ready 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.139: [vfs7552] QUERY DATA READY entering state 1 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.139: Receiving 64 bytes 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.140: Got 6 bytes out of 64 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.140: [vfs7552] QUERY DATA READY completed successfully 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.140: [vfs7552] CAPTURE_NUM_STATES entering state 1 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.140: [vfs7552] CAPTURE_NUM_STATES entering state 0 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.140: [vfs7552] QUERY DATA READY entering state 0 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.140: Sending vfs7552_is_image_ready 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.140: [vfs7552] QUERY DATA READY entering state 1 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.140: Receiving 64 bytes 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.140: Got 6 bytes out of 64 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.140: [vfs7552] QUERY DATA READY completed successfully 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.141: [vfs7552] CAPTURE_NUM_STATES entering state 1 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.141: [vfs7552] CAPTURE_NUM_STATES entering state 0 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.141: [vfs7552] QUERY DATA READY entering state 0 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.141: Sending vfs7552_is_image_ready 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.141: [vfs7552] QUERY DATA READY entering state 1 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.141: Receiving 64 bytes 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.141: Got 6 bytes out of 64 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.141: [vfs7552] QUERY DATA READY completed successfully 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.142: [vfs7552] CAPTURE_NUM_STATES entering state 1 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.142: [vfs7552] CAPTURE_NUM_STATES entering state 0 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.142: [vfs7552] QUERY DATA READY entering state 0 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.142: Sending vfs7552_is_image_ready 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.142: [vfs7552] QUERY DATA READY entering state 1 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.142: Receiving 64 bytes 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.143: Got 6 bytes out of 64 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.143: [vfs7552] QUERY DATA READY completed successfully 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.143: [vfs7552] CAPTURE_NUM_STATES entering state 1 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.143: [vfs7552] CAPTURE_NUM_STATES entering state 0 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.143: [vfs7552] QUERY DATA READY entering state 0 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.143: Sending vfs7552_is_image_ready 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.143: [vfs7552] QUERY DATA READY entering state 1 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.143: Receiving 64 bytes 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.144: Got 6 bytes out of 64 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.144: [vfs7552] QUERY DATA READY completed successfully 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.144: [vfs7552] CAPTURE_NUM_STATES entering state 1 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.144: [vfs7552] CAPTURE_NUM_STATES entering state 0 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.144: [vfs7552] QUERY DATA READY entering state 0 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.144: Sending vfs7552_is_image_ready 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.144: [vfs7552] QUERY DATA READY entering state 1 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.144: Receiving 64 bytes 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.145: Got 6 bytes out of 64 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.145: [vfs7552] QUERY DATA READY completed successfully 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.145: [vfs7552] CAPTURE_NUM_STATES entering state 1 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.145: [vfs7552] CAPTURE_NUM_STATES entering state 0 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.145: [vfs7552] QUERY DATA READY entering state 0 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.145: Sending vfs7552_is_image_ready 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.145: [vfs7552] QUERY DATA READY entering state 1 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.145: Receiving 64 bytes 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.146: Got 6 bytes out of 64 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.146: [vfs7552] QUERY DATA READY completed successfully 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.146: [vfs7552] CAPTURE_NUM_STATES entering state 1 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.146: [vfs7552] CAPTURE_NUM_STATES entering state 0 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.146: [vfs7552] QUERY DATA READY entering state 0 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.146: Sending vfs7552_is_image_ready 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.146: [vfs7552] QUERY DATA READY entering state 1 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.146: Receiving 64 bytes 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.146: Got 6 bytes out of 64 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.147: [vfs7552] QUERY DATA READY completed successfully 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.147: [vfs7552] CAPTURE_NUM_STATES entering state 1 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.147: [vfs7552] CAPTURE_NUM_STATES entering state 0 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.147: [vfs7552] QUERY DATA READY entering state 0 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.147: Sending vfs7552_is_image_ready 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.147: [vfs7552] QUERY DATA READY entering state 1 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.147: Receiving 64 bytes 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.147: Got 6 bytes out of 64 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.148: [vfs7552] QUERY DATA READY completed successfully 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.148: [vfs7552] CAPTURE_NUM_STATES entering state 1 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.148: [vfs7552] CAPTURE_NUM_STATES entering state 0 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.148: [vfs7552] QUERY DATA READY entering state 0 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.148: Sending vfs7552_is_image_ready 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.148: [vfs7552] QUERY DATA READY entering state 1 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.148: Receiving 64 bytes 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.148: Got 6 bytes out of 64 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.148: [vfs7552] QUERY DATA READY completed successfully 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.148: [vfs7552] CAPTURE_NUM_STATES entering state 1 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.149: [vfs7552] CAPTURE_NUM_STATES entering state 0 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.149: [vfs7552] QUERY DATA READY entering state 0 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.149: Sending vfs7552_is_image_ready 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.149: [vfs7552] QUERY DATA READY entering state 1 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.149: Receiving 64 bytes 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.149: Got 6 bytes out of 64 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.150: [vfs7552] QUERY DATA READY completed successfully 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.150: [vfs7552] CAPTURE_NUM_STATES entering state 1 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.150: [vfs7552] CAPTURE_NUM_STATES entering state 0 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.150: [vfs7552] QUERY DATA READY entering state 0 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.150: Sending vfs7552_is_image_ready 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.150: [vfs7552] QUERY DATA READY entering state 1 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.150: Receiving 64 bytes 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.150: Got 6 bytes out of 64 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.151: [vfs7552] QUERY DATA READY completed successfully 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.151: [vfs7552] CAPTURE_NUM_STATES entering state 1 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.151: [vfs7552] CAPTURE_NUM_STATES entering state 0 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.151: [vfs7552] QUERY DATA READY entering state 0 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.151: Sending vfs7552_is_image_ready 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.151: [vfs7552] QUERY DATA READY entering state 1 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.151: Receiving 64 bytes 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.151: Got 6 bytes out of 64 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.151: [vfs7552] QUERY DATA READY completed successfully 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.151: [vfs7552] CAPTURE_NUM_STATES entering state 1 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.151: [vfs7552] CAPTURE_NUM_STATES entering state 0 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.151: [vfs7552] QUERY DATA READY entering state 0 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.151: Sending vfs7552_is_image_ready 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.152: [vfs7552] QUERY DATA READY entering state 1 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.152: Receiving 64 bytes 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.152: Got 6 bytes out of 64 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.152: [vfs7552] QUERY DATA READY completed successfully 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.152: [vfs7552] CAPTURE_NUM_STATES entering state 1 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.152: [vfs7552] CAPTURE_NUM_STATES entering state 0 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.152: [vfs7552] QUERY DATA READY entering state 0 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.152: Sending vfs7552_is_image_ready 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.153: [vfs7552] QUERY DATA READY entering state 1 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.153: Receiving 64 bytes 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.153: Got 6 bytes out of 64 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.153: [vfs7552] QUERY DATA READY completed successfully 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.153: [vfs7552] CAPTURE_NUM_STATES entering state 1 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.153: [vfs7552] CAPTURE_NUM_STATES entering state 0 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.153: [vfs7552] QUERY DATA READY entering state 0 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.153: Sending vfs7552_is_image_ready 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.154: [vfs7552] QUERY DATA READY entering state 1 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.154: Receiving 64 bytes 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.154: Got 6 bytes out of 64 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.154: [vfs7552] QUERY DATA READY completed successfully 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.154: [vfs7552] CAPTURE_NUM_STATES entering state 1 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.154: [vfs7552] CAPTURE_NUM_STATES entering state 0 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.154: [vfs7552] QUERY DATA READY entering state 0 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.154: Sending vfs7552_is_image_ready 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.155: [vfs7552] QUERY DATA READY entering state 1 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.155: Receiving 64 bytes 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.155: Got 6 bytes out of 64 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.155: [vfs7552] QUERY DATA READY completed successfully 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.155: [vfs7552] CAPTURE_NUM_STATES entering state 1 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.155: [vfs7552] CAPTURE_NUM_STATES entering state 0 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.155: [vfs7552] QUERY DATA READY entering state 0 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.155: Sending vfs7552_is_image_ready 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.156: [vfs7552] QUERY DATA READY entering state 1 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.156: Receiving 64 bytes 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.156: Got 6 bytes out of 64 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.156: [vfs7552] QUERY DATA READY completed successfully 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.156: [vfs7552] CAPTURE_NUM_STATES entering state 1 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.156: [vfs7552] CAPTURE_NUM_STATES entering state 0 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.156: [vfs7552] QUERY DATA READY entering state 0 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.156: Sending vfs7552_is_image_ready 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.157: [vfs7552] QUERY DATA READY entering state 1 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.157: Receiving 64 bytes 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.157: Got 6 bytes out of 64 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.157: [vfs7552] QUERY DATA READY completed successfully 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.157: [vfs7552] CAPTURE_NUM_STATES entering state 1 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.157: [vfs7552] CAPTURE_NUM_STATES entering state 0 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.157: [vfs7552] QUERY DATA READY entering state 0 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.157: Sending vfs7552_is_image_ready 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.158: [vfs7552] QUERY DATA READY entering state 1 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.158: Receiving 64 bytes 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.158: Got 6 bytes out of 64 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.158: [vfs7552] QUERY DATA READY completed successfully 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.158: [vfs7552] CAPTURE_NUM_STATES entering state 1 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.158: [vfs7552] CAPTURE_NUM_STATES entering state 0 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.158: [vfs7552] QUERY DATA READY entering state 0 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.158: Sending vfs7552_is_image_ready 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.159: [vfs7552] QUERY DATA READY entering state 1 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.159: Receiving 64 bytes 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.159: Got 6 bytes out of 64 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.159: [vfs7552] QUERY DATA READY completed successfully 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.159: [vfs7552] CAPTURE_NUM_STATES entering state 1 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.159: [vfs7552] CAPTURE_NUM_STATES entering state 0 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.159: [vfs7552] QUERY DATA READY entering state 0 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.159: Sending vfs7552_is_image_ready 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.160: [vfs7552] QUERY DATA READY entering state 1 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.160: Receiving 64 bytes 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.160: Got 6 bytes out of 64 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.160: [vfs7552] QUERY DATA READY completed successfully 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.160: [vfs7552] CAPTURE_NUM_STATES entering state 1 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.160: [vfs7552] CAPTURE_NUM_STATES entering state 0 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.160: [vfs7552] QUERY DATA READY entering state 0 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.160: Sending vfs7552_is_image_ready 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.160: [vfs7552] QUERY DATA READY entering state 1 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.161: Receiving 64 bytes 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.161: Got 6 bytes out of 64 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.161: [vfs7552] QUERY DATA READY completed successfully 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.161: [vfs7552] CAPTURE_NUM_STATES entering state 1 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.161: [vfs7552] CAPTURE_NUM_STATES entering state 0 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.161: [vfs7552] QUERY DATA READY entering state 0 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.161: Sending vfs7552_is_image_ready 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.161: [vfs7552] QUERY DATA READY entering state 1 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.161: Receiving 64 bytes 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.162: Got 6 bytes out of 64 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.162: [vfs7552] QUERY DATA READY completed successfully 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.162: [vfs7552] CAPTURE_NUM_STATES entering state 1 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.162: [vfs7552] CAPTURE_NUM_STATES entering state 2 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.162: [vfs7552] REQUEST CHUNK entering state 0 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.162: Sending vfs7552_read_image_chunk 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.162: [vfs7552] REQUEST CHUNK completed successfully 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.162: [vfs7552] CAPTURE_NUM_STATES entering state 3 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.163: [vfs7552] CAPTURE_NUM_STATES entering state 2 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.163: [vfs7552] REQUEST CHUNK entering state 0 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.163: Sending vfs7552_read_image_chunk 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.163: [vfs7552] REQUEST CHUNK completed successfully 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.163: [vfs7552] CAPTURE_NUM_STATES entering state 3 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.164: [vfs7552] CAPTURE_NUM_STATES entering state 2 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.164: [vfs7552] REQUEST CHUNK entering state 0 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.164: Sending vfs7552_read_image_chunk 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.164: [vfs7552] REQUEST CHUNK completed successfully 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.164: [vfs7552] CAPTURE_NUM_STATES entering state 3 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.165: [vfs7552] CAPTURE_NUM_STATES entering state 4 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.165: Cleaning image 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.165: variance_after = 1845 184s 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.165: [vfs7552] CAPTURE_NUM_STATES entering state 0 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.165: [vfs7552] QUERY DATA READY entering state 0 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.165: Sending vfs7552_is_image_ready 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.165: [vfs7552] QUERY DATA READY entering state 1 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.165: Receiving 64 bytes 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.166: Got 6 bytes out of 64 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.166: [vfs7552] QUERY DATA READY completed successfully 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.166: [vfs7552] CAPTURE_NUM_STATES entering state 1 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.166: [vfs7552] CAPTURE_NUM_STATES entering state 0 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.166: [vfs7552] QUERY DATA READY entering state 0 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.166: Sending vfs7552_is_image_ready 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.166: [vfs7552] QUERY DATA READY entering state 1 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.166: Receiving 64 bytes 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.167: Got 6 bytes out of 64 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.167: [vfs7552] QUERY DATA READY completed successfully 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.167: [vfs7552] CAPTURE_NUM_STATES entering state 1 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.167: [vfs7552] CAPTURE_NUM_STATES entering state 0 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.167: [vfs7552] QUERY DATA READY entering state 0 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.167: Sending vfs7552_is_image_ready 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.167: [vfs7552] QUERY DATA READY entering state 1 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.167: Receiving 64 bytes 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.168: Got 6 bytes out of 64 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.168: [vfs7552] QUERY DATA READY completed successfully 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.168: [vfs7552] CAPTURE_NUM_STATES entering state 1 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.168: [vfs7552] CAPTURE_NUM_STATES entering state 0 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.168: [vfs7552] QUERY DATA READY entering state 0 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.168: Sending vfs7552_is_image_ready 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.168: [vfs7552] QUERY DATA READY entering state 1 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.168: Receiving 64 bytes 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.169: Got 6 bytes out of 64 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.169: [vfs7552] QUERY DATA READY completed successfully 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.169: [vfs7552] CAPTURE_NUM_STATES entering state 1 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.169: [vfs7552] CAPTURE_NUM_STATES entering state 0 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.169: [vfs7552] QUERY DATA READY entering state 0 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.169: Sending vfs7552_is_image_ready 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.169: [vfs7552] QUERY DATA READY entering state 1 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.169: Receiving 64 bytes 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.170: Got 6 bytes out of 64 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.170: [vfs7552] QUERY DATA READY completed successfully 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.170: [vfs7552] CAPTURE_NUM_STATES entering state 1 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.170: [vfs7552] CAPTURE_NUM_STATES entering state 0 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.170: [vfs7552] QUERY DATA READY entering state 0 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.170: Sending vfs7552_is_image_ready 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.170: [vfs7552] QUERY DATA READY entering state 1 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.170: Receiving 64 bytes 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.171: Got 6 bytes out of 64 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.171: [vfs7552] QUERY DATA READY completed successfully 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.171: [vfs7552] CAPTURE_NUM_STATES entering state 1 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.171: [vfs7552] CAPTURE_NUM_STATES entering state 0 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.171: [vfs7552] QUERY DATA READY entering state 0 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.171: Sending vfs7552_is_image_ready 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.171: [vfs7552] QUERY DATA READY entering state 1 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.171: Receiving 64 bytes 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.172: Got 6 bytes out of 64 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.172: [vfs7552] QUERY DATA READY completed successfully 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.172: [vfs7552] CAPTURE_NUM_STATES entering state 1 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.172: [vfs7552] CAPTURE_NUM_STATES entering state 0 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.172: [vfs7552] QUERY DATA READY entering state 0 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.172: Sending vfs7552_is_image_ready 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.172: [vfs7552] QUERY DATA READY entering state 1 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.172: Receiving 64 bytes 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.173: Got 6 bytes out of 64 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.173: [vfs7552] QUERY DATA READY completed successfully 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.173: [vfs7552] CAPTURE_NUM_STATES entering state 1 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.173: [vfs7552] CAPTURE_NUM_STATES entering state 0 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.173: [vfs7552] QUERY DATA READY entering state 0 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.173: Sending vfs7552_is_image_ready 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.173: [vfs7552] QUERY DATA READY entering state 1 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.173: Receiving 64 bytes 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.174: Got 6 bytes out of 64 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.174: [vfs7552] QUERY DATA READY completed successfully 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.174: [vfs7552] CAPTURE_NUM_STATES entering state 1 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.174: [vfs7552] CAPTURE_NUM_STATES entering state 0 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.174: [vfs7552] QUERY DATA READY entering state 0 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.174: Sending vfs7552_is_image_ready 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.174: [vfs7552] QUERY DATA READY entering state 1 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.174: Receiving 64 bytes 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.175: Got 6 bytes out of 64 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.175: [vfs7552] QUERY DATA READY completed successfully 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.175: [vfs7552] CAPTURE_NUM_STATES entering state 1 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.175: [vfs7552] CAPTURE_NUM_STATES entering state 0 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.175: [vfs7552] QUERY DATA READY entering state 0 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.175: Sending vfs7552_is_image_ready 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.175: [vfs7552] QUERY DATA READY entering state 1 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.175: Receiving 64 bytes 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.176: Got 6 bytes out of 64 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.176: [vfs7552] QUERY DATA READY completed successfully 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.176: [vfs7552] CAPTURE_NUM_STATES entering state 1 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.176: [vfs7552] CAPTURE_NUM_STATES entering state 0 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.176: [vfs7552] QUERY DATA READY entering state 0 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.176: Sending vfs7552_is_image_ready 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.176: [vfs7552] QUERY DATA READY entering state 1 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.176: Receiving 64 bytes 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.177: Got 6 bytes out of 64 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.177: [vfs7552] QUERY DATA READY completed successfully 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.177: [vfs7552] CAPTURE_NUM_STATES entering state 1 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.177: [vfs7552] CAPTURE_NUM_STATES entering state 0 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.177: [vfs7552] QUERY DATA READY entering state 0 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.177: Sending vfs7552_is_image_ready 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.177: [vfs7552] QUERY DATA READY entering state 1 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.177: Receiving 64 bytes 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.178: Got 6 bytes out of 64 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.178: [vfs7552] QUERY DATA READY completed successfully 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.178: [vfs7552] CAPTURE_NUM_STATES entering state 1 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.178: [vfs7552] CAPTURE_NUM_STATES entering state 0 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.178: [vfs7552] QUERY DATA READY entering state 0 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.178: Sending vfs7552_is_image_ready 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.178: [vfs7552] QUERY DATA READY entering state 1 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.178: Receiving 64 bytes 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.179: Got 6 bytes out of 64 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.179: [vfs7552] QUERY DATA READY completed successfully 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.179: [vfs7552] CAPTURE_NUM_STATES entering state 1 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.179: [vfs7552] CAPTURE_NUM_STATES entering state 0 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.179: [vfs7552] QUERY DATA READY entering state 0 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.179: Sending vfs7552_is_image_ready 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.179: [vfs7552] QUERY DATA READY entering state 1 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.179: Receiving 64 bytes 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.179: Got 6 bytes out of 64 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.179: [vfs7552] QUERY DATA READY completed successfully 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.180: [vfs7552] CAPTURE_NUM_STATES entering state 1 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.180: [vfs7552] CAPTURE_NUM_STATES entering state 0 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.180: [vfs7552] QUERY DATA READY entering state 0 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.180: Sending vfs7552_is_image_ready 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.180: [vfs7552] QUERY DATA READY entering state 1 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.180: Receiving 64 bytes 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.180: Got 6 bytes out of 64 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.180: [vfs7552] QUERY DATA READY completed successfully 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.180: [vfs7552] CAPTURE_NUM_STATES entering state 1 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.180: [vfs7552] CAPTURE_NUM_STATES entering state 0 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.180: [vfs7552] QUERY DATA READY entering state 0 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.180: Sending vfs7552_is_image_ready 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.181: [vfs7552] QUERY DATA READY entering state 1 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.181: Receiving 64 bytes 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.181: Got 6 bytes out of 64 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.181: [vfs7552] QUERY DATA READY completed successfully 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.181: [vfs7552] CAPTURE_NUM_STATES entering state 1 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.181: [vfs7552] CAPTURE_NUM_STATES entering state 0 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.181: [vfs7552] QUERY DATA READY entering state 0 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.181: Sending vfs7552_is_image_ready 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.182: [vfs7552] QUERY DATA READY entering state 1 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.182: Receiving 64 bytes 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.182: Got 6 bytes out of 64 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.182: [vfs7552] QUERY DATA READY completed successfully 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.182: [vfs7552] CAPTURE_NUM_STATES entering state 1 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.182: [vfs7552] CAPTURE_NUM_STATES entering state 0 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.182: [vfs7552] QUERY DATA READY entering state 0 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.182: Sending vfs7552_is_image_ready 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.183: [vfs7552] QUERY DATA READY entering state 1 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.183: Receiving 64 bytes 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.183: Got 6 bytes out of 64 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.183: [vfs7552] QUERY DATA READY completed successfully 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.183: [vfs7552] CAPTURE_NUM_STATES entering state 1 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.183: [vfs7552] CAPTURE_NUM_STATES entering state 0 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.183: [vfs7552] QUERY DATA READY entering state 0 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.183: Sending vfs7552_is_image_ready 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.184: [vfs7552] QUERY DATA READY entering state 1 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.184: Receiving 64 bytes 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.184: Got 6 bytes out of 64 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.184: [vfs7552] QUERY DATA READY completed successfully 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.184: [vfs7552] CAPTURE_NUM_STATES entering state 1 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.184: [vfs7552] CAPTURE_NUM_STATES entering state 0 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.184: [vfs7552] QUERY DATA READY entering state 0 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.184: Sending vfs7552_is_image_ready 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.185: [vfs7552] QUERY DATA READY entering state 1 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.185: Receiving 64 bytes 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.185: Got 6 bytes out of 64 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.185: [vfs7552] QUERY DATA READY completed successfully 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.185: [vfs7552] CAPTURE_NUM_STATES entering state 1 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.185: [vfs7552] CAPTURE_NUM_STATES entering state 0 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.185: [vfs7552] QUERY DATA READY entering state 0 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.185: Sending vfs7552_is_image_ready 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.186: [vfs7552] QUERY DATA READY entering state 1 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.186: Receiving 64 bytes 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.186: Got 6 bytes out of 64 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.186: [vfs7552] QUERY DATA READY completed successfully 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.186: [vfs7552] CAPTURE_NUM_STATES entering state 1 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.186: [vfs7552] CAPTURE_NUM_STATES entering state 0 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.186: [vfs7552] QUERY DATA READY entering state 0 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.186: Sending vfs7552_is_image_ready 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.187: [vfs7552] QUERY DATA READY entering state 1 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.187: Receiving 64 bytes 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.187: Got 6 bytes out of 64 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.187: [vfs7552] QUERY DATA READY completed successfully 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.187: [vfs7552] CAPTURE_NUM_STATES entering state 1 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.187: [vfs7552] CAPTURE_NUM_STATES entering state 0 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.187: [vfs7552] QUERY DATA READY entering state 0 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.187: Sending vfs7552_is_image_ready 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.187: [vfs7552] QUERY DATA READY entering state 1 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.188: Receiving 64 bytes 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.188: Got 6 bytes out of 64 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.188: [vfs7552] QUERY DATA READY completed successfully 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.188: [vfs7552] CAPTURE_NUM_STATES entering state 1 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.188: [vfs7552] CAPTURE_NUM_STATES entering state 0 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.188: [vfs7552] QUERY DATA READY entering state 0 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.188: Sending vfs7552_is_image_ready 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.188: [vfs7552] QUERY DATA READY entering state 1 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.188: Receiving 64 bytes 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.189: Got 6 bytes out of 64 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.189: [vfs7552] QUERY DATA READY completed successfully 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.189: [vfs7552] CAPTURE_NUM_STATES entering state 1 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.189: [vfs7552] CAPTURE_NUM_STATES entering state 0 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.189: [vfs7552] QUERY DATA READY entering state 0 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.189: Sending vfs7552_is_image_ready 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.189: [vfs7552] QUERY DATA READY entering state 1 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.189: Receiving 64 bytes 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.190: Got 6 bytes out of 64 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.190: [vfs7552] QUERY DATA READY completed successfully 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.190: [vfs7552] CAPTURE_NUM_STATES entering state 1 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.190: [vfs7552] CAPTURE_NUM_STATES entering state 0 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.190: [vfs7552] QUERY DATA READY entering state 0 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.190: Sending vfs7552_is_image_ready 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.190: [vfs7552] QUERY DATA READY entering state 1 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.190: Receiving 64 bytes 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.191: Got 6 bytes out of 64 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.191: [vfs7552] QUERY DATA READY completed successfully 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.191: [vfs7552] CAPTURE_NUM_STATES entering state 1 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.191: [vfs7552] CAPTURE_NUM_STATES entering state 0 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.191: [vfs7552] QUERY DATA READY entering state 0 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.191: Sending vfs7552_is_image_ready 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.191: [vfs7552] QUERY DATA READY entering state 1 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.191: Receiving 64 bytes 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.192: Got 6 bytes out of 64 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.192: [vfs7552] QUERY DATA READY completed successfully 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.192: [vfs7552] CAPTURE_NUM_STATES entering state 1 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.192: [vfs7552] CAPTURE_NUM_STATES entering state 0 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.192: [vfs7552] QUERY DATA READY entering state 0 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.192: Sending vfs7552_is_image_ready 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.192: [vfs7552] QUERY DATA READY entering state 1 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.192: Receiving 64 bytes 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.193: Got 6 bytes out of 64 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.193: [vfs7552] QUERY DATA READY completed successfully 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.193: [vfs7552] CAPTURE_NUM_STATES entering state 1 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.193: [vfs7552] CAPTURE_NUM_STATES entering state 0 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.193: [vfs7552] QUERY DATA READY entering state 0 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.193: Sending vfs7552_is_image_ready 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.193: [vfs7552] QUERY DATA READY entering state 1 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.193: Receiving 64 bytes 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.194: Got 6 bytes out of 64 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.194: [vfs7552] QUERY DATA READY completed successfully 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.194: [vfs7552] CAPTURE_NUM_STATES entering state 1 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.194: [vfs7552] CAPTURE_NUM_STATES entering state 0 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.194: [vfs7552] QUERY DATA READY entering state 0 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.194: Sending vfs7552_is_image_ready 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.194: [vfs7552] QUERY DATA READY entering state 1 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.194: Receiving 64 bytes 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.195: Got 6 bytes out of 64 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.195: [vfs7552] QUERY DATA READY completed successfully 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.195: [vfs7552] CAPTURE_NUM_STATES entering state 1 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.195: [vfs7552] CAPTURE_NUM_STATES entering state 0 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.195: [vfs7552] QUERY DATA READY entering state 0 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.195: Sending vfs7552_is_image_ready 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.195: [vfs7552] QUERY DATA READY entering state 1 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.195: Receiving 64 bytes 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.196: Got 6 bytes out of 64 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.196: [vfs7552] QUERY DATA READY completed successfully 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.196: [vfs7552] CAPTURE_NUM_STATES entering state 1 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.196: [vfs7552] CAPTURE_NUM_STATES entering state 0 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.196: [vfs7552] QUERY DATA READY entering state 0 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.196: Sending vfs7552_is_image_ready 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.196: [vfs7552] QUERY DATA READY entering state 1 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.196: Receiving 64 bytes 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.197: Got 6 bytes out of 64 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.197: [vfs7552] QUERY DATA READY completed successfully 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.197: [vfs7552] CAPTURE_NUM_STATES entering state 1 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.197: [vfs7552] CAPTURE_NUM_STATES entering state 0 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.197: [vfs7552] QUERY DATA READY entering state 0 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.197: Sending vfs7552_is_image_ready 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.197: [vfs7552] QUERY DATA READY entering state 1 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.197: Receiving 64 bytes 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.198: Got 6 bytes out of 64 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.198: [vfs7552] QUERY DATA READY completed successfully 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.198: [vfs7552] CAPTURE_NUM_STATES entering state 1 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.198: [vfs7552] CAPTURE_NUM_STATES entering state 0 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.198: [vfs7552] QUERY DATA READY entering state 0 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.198: Sending vfs7552_is_image_ready 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.198: [vfs7552] QUERY DATA READY entering state 1 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.198: Receiving 64 bytes 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.199: Got 6 bytes out of 64 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.199: [vfs7552] QUERY DATA READY completed successfully 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.199: [vfs7552] CAPTURE_NUM_STATES entering state 1 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.199: [vfs7552] CAPTURE_NUM_STATES entering state 0 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.199: [vfs7552] QUERY DATA READY entering state 0 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.199: Sending vfs7552_is_image_ready 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.199: [vfs7552] QUERY DATA READY entering state 1 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.199: Receiving 64 bytes 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.200: Got 6 bytes out of 64 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.200: [vfs7552] QUERY DATA READY completed successfully 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.200: [vfs7552] CAPTURE_NUM_STATES entering state 1 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.200: [vfs7552] CAPTURE_NUM_STATES entering state 0 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.200: [vfs7552] QUERY DATA READY entering state 0 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.200: Sending vfs7552_is_image_ready 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.200: [vfs7552] QUERY DATA READY entering state 1 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.200: Receiving 64 bytes 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.200: Got 6 bytes out of 64 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.200: [vfs7552] QUERY DATA READY completed successfully 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.200: [vfs7552] CAPTURE_NUM_STATES entering state 1 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.200: [vfs7552] CAPTURE_NUM_STATES entering state 0 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.200: [vfs7552] QUERY DATA READY entering state 0 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.200: Sending vfs7552_is_image_ready 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.201: [vfs7552] QUERY DATA READY entering state 1 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.201: Receiving 64 bytes 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.201: Got 6 bytes out of 64 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.201: [vfs7552] QUERY DATA READY completed successfully 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.201: [vfs7552] CAPTURE_NUM_STATES entering state 1 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.201: [vfs7552] CAPTURE_NUM_STATES entering state 0 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.201: [vfs7552] QUERY DATA READY entering state 0 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.201: Sending vfs7552_is_image_ready 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.202: [vfs7552] QUERY DATA READY entering state 1 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.202: Receiving 64 bytes 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.202: Got 6 bytes out of 64 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.202: [vfs7552] QUERY DATA READY completed successfully 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.202: [vfs7552] CAPTURE_NUM_STATES entering state 1 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.202: [vfs7552] CAPTURE_NUM_STATES entering state 0 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.202: [vfs7552] QUERY DATA READY entering state 0 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.202: Sending vfs7552_is_image_ready 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.203: [vfs7552] QUERY DATA READY entering state 1 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.203: Receiving 64 bytes 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.203: Got 6 bytes out of 64 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.203: [vfs7552] QUERY DATA READY completed successfully 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.203: [vfs7552] CAPTURE_NUM_STATES entering state 1 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.203: [vfs7552] CAPTURE_NUM_STATES entering state 0 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.203: [vfs7552] QUERY DATA READY entering state 0 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.203: Sending vfs7552_is_image_ready 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.204: [vfs7552] QUERY DATA READY entering state 1 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.204: Receiving 64 bytes 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.204: Got 6 bytes out of 64 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.204: [vfs7552] QUERY DATA READY completed successfully 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.204: [vfs7552] CAPTURE_NUM_STATES entering state 1 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.204: [vfs7552] CAPTURE_NUM_STATES entering state 0 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.204: [vfs7552] QUERY DATA READY entering state 0 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.204: Sending vfs7552_is_image_ready 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.205: [vfs7552] QUERY DATA READY entering state 1 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.205: Receiving 64 bytes 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.205: Got 6 bytes out of 64 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.205: [vfs7552] QUERY DATA READY completed successfully 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.205: [vfs7552] CAPTURE_NUM_STATES entering state 1 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.205: [vfs7552] CAPTURE_NUM_STATES entering state 0 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.205: [vfs7552] QUERY DATA READY entering state 0 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.205: Sending vfs7552_is_image_ready 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.206: [vfs7552] QUERY DATA READY entering state 1 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.206: Receiving 64 bytes 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.206: Got 6 bytes out of 64 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.206: [vfs7552] QUERY DATA READY completed successfully 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.206: [vfs7552] CAPTURE_NUM_STATES entering state 1 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.206: [vfs7552] CAPTURE_NUM_STATES entering state 0 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.206: [vfs7552] QUERY DATA READY entering state 0 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.206: Sending vfs7552_is_image_ready 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.207: [vfs7552] QUERY DATA READY entering state 1 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.207: Receiving 64 bytes 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.207: Got 6 bytes out of 64 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.207: [vfs7552] QUERY DATA READY completed successfully 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.207: [vfs7552] CAPTURE_NUM_STATES entering state 1 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.207: [vfs7552] CAPTURE_NUM_STATES entering state 0 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.207: [vfs7552] QUERY DATA READY entering state 0 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.207: Sending vfs7552_is_image_ready 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.207: [vfs7552] QUERY DATA READY entering state 1 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.208: Receiving 64 bytes 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.208: Got 6 bytes out of 64 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.208: [vfs7552] QUERY DATA READY completed successfully 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.208: [vfs7552] CAPTURE_NUM_STATES entering state 1 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.208: [vfs7552] CAPTURE_NUM_STATES entering state 2 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.208: [vfs7552] REQUEST CHUNK entering state 0 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.208: Sending vfs7552_read_image_chunk 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.208: [vfs7552] REQUEST CHUNK completed successfully 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.208: [vfs7552] CAPTURE_NUM_STATES entering state 3 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.209: [vfs7552] CAPTURE_NUM_STATES entering state 2 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.209: [vfs7552] REQUEST CHUNK entering state 0 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.209: Sending vfs7552_read_image_chunk 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.210: [vfs7552] REQUEST CHUNK completed successfully 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.210: [vfs7552] CAPTURE_NUM_STATES entering state 3 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.210: [vfs7552] CAPTURE_NUM_STATES entering state 2 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.210: [vfs7552] REQUEST CHUNK entering state 0 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.210: Sending vfs7552_read_image_chunk 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.210: [vfs7552] REQUEST CHUNK completed successfully 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.210: [vfs7552] CAPTURE_NUM_STATES entering state 3 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.211: [vfs7552] CAPTURE_NUM_STATES entering state 4 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.211: Cleaning image 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.211: variance_after = 2342 184s 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.211: [vfs7552] CAPTURE_NUM_STATES entering state 0 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.211: [vfs7552] QUERY DATA READY entering state 0 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.211: Sending vfs7552_is_image_ready 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.212: [vfs7552] QUERY DATA READY entering state 1 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.212: Receiving 64 bytes 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.212: Got 6 bytes out of 64 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.212: [vfs7552] QUERY DATA READY completed successfully 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.212: [vfs7552] CAPTURE_NUM_STATES entering state 1 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.212: [vfs7552] CAPTURE_NUM_STATES entering state 0 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.212: [vfs7552] QUERY DATA READY entering state 0 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.212: Sending vfs7552_is_image_ready 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.213: [vfs7552] QUERY DATA READY entering state 1 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.213: Receiving 64 bytes 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.213: Got 6 bytes out of 64 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.213: [vfs7552] QUERY DATA READY completed successfully 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.213: [vfs7552] CAPTURE_NUM_STATES entering state 1 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.213: [vfs7552] CAPTURE_NUM_STATES entering state 0 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.213: [vfs7552] QUERY DATA READY entering state 0 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.213: Sending vfs7552_is_image_ready 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.213: [vfs7552] QUERY DATA READY entering state 1 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.213: Receiving 64 bytes 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.214: Got 6 bytes out of 64 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.214: [vfs7552] QUERY DATA READY completed successfully 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.214: [vfs7552] CAPTURE_NUM_STATES entering state 1 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.214: [vfs7552] CAPTURE_NUM_STATES entering state 0 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.214: [vfs7552] QUERY DATA READY entering state 0 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.214: Sending vfs7552_is_image_ready 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.215: [vfs7552] QUERY DATA READY entering state 1 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.215: Receiving 64 bytes 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.215: Got 6 bytes out of 64 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.215: [vfs7552] QUERY DATA READY completed successfully 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.215: [vfs7552] CAPTURE_NUM_STATES entering state 1 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.215: [vfs7552] CAPTURE_NUM_STATES entering state 0 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.215: [vfs7552] QUERY DATA READY entering state 0 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.215: Sending vfs7552_is_image_ready 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.215: [vfs7552] QUERY DATA READY entering state 1 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.215: Receiving 64 bytes 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.216: Got 6 bytes out of 64 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.216: [vfs7552] QUERY DATA READY completed successfully 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.216: [vfs7552] CAPTURE_NUM_STATES entering state 1 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.216: [vfs7552] CAPTURE_NUM_STATES entering state 0 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.216: [vfs7552] QUERY DATA READY entering state 0 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.216: Sending vfs7552_is_image_ready 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.216: [vfs7552] QUERY DATA READY entering state 1 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.216: Receiving 64 bytes 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.217: Got 6 bytes out of 64 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.217: [vfs7552] QUERY DATA READY completed successfully 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.217: [vfs7552] CAPTURE_NUM_STATES entering state 1 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.217: [vfs7552] CAPTURE_NUM_STATES entering state 0 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.217: [vfs7552] QUERY DATA READY entering state 0 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.217: Sending vfs7552_is_image_ready 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.217: [vfs7552] QUERY DATA READY entering state 1 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.217: Receiving 64 bytes 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.218: Got 6 bytes out of 64 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.218: [vfs7552] QUERY DATA READY completed successfully 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.218: [vfs7552] CAPTURE_NUM_STATES entering state 1 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.218: [vfs7552] CAPTURE_NUM_STATES entering state 0 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.218: [vfs7552] QUERY DATA READY entering state 0 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.218: Sending vfs7552_is_image_ready 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.218: [vfs7552] QUERY DATA READY entering state 1 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.218: Receiving 64 bytes 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.219: Got 6 bytes out of 64 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.219: [vfs7552] QUERY DATA READY completed successfully 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.219: [vfs7552] CAPTURE_NUM_STATES entering state 1 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.219: [vfs7552] CAPTURE_NUM_STATES entering state 0 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.219: [vfs7552] QUERY DATA READY entering state 0 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.219: Sending vfs7552_is_image_ready 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.219: [vfs7552] QUERY DATA READY entering state 1 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.219: Receiving 64 bytes 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.220: Got 6 bytes out of 64 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.220: [vfs7552] QUERY DATA READY completed successfully 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.220: [vfs7552] CAPTURE_NUM_STATES entering state 1 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.220: [vfs7552] CAPTURE_NUM_STATES entering state 0 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.220: [vfs7552] QUERY DATA READY entering state 0 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.220: Sending vfs7552_is_image_ready 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.220: [vfs7552] QUERY DATA READY entering state 1 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.220: Receiving 64 bytes 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.221: Got 6 bytes out of 64 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.221: [vfs7552] QUERY DATA READY completed successfully 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.221: [vfs7552] CAPTURE_NUM_STATES entering state 1 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.221: [vfs7552] CAPTURE_NUM_STATES entering state 0 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.221: [vfs7552] QUERY DATA READY entering state 0 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.221: Sending vfs7552_is_image_ready 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.221: [vfs7552] QUERY DATA READY entering state 1 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.221: Receiving 64 bytes 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.222: Got 6 bytes out of 64 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.222: [vfs7552] QUERY DATA READY completed successfully 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.222: [vfs7552] CAPTURE_NUM_STATES entering state 1 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.222: [vfs7552] CAPTURE_NUM_STATES entering state 0 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.222: [vfs7552] QUERY DATA READY entering state 0 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.222: Sending vfs7552_is_image_ready 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.222: [vfs7552] QUERY DATA READY entering state 1 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.222: Receiving 64 bytes 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.223: Got 6 bytes out of 64 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.223: [vfs7552] QUERY DATA READY completed successfully 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.223: [vfs7552] CAPTURE_NUM_STATES entering state 1 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.223: [vfs7552] CAPTURE_NUM_STATES entering state 0 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.223: [vfs7552] QUERY DATA READY entering state 0 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.223: Sending vfs7552_is_image_ready 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.223: [vfs7552] QUERY DATA READY entering state 1 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.223: Receiving 64 bytes 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.224: Got 6 bytes out of 64 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.224: [vfs7552] QUERY DATA READY completed successfully 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.224: [vfs7552] CAPTURE_NUM_STATES entering state 1 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.224: [vfs7552] CAPTURE_NUM_STATES entering state 0 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.224: [vfs7552] QUERY DATA READY entering state 0 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.224: Sending vfs7552_is_image_ready 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.224: [vfs7552] QUERY DATA READY entering state 1 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.224: Receiving 64 bytes 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.225: Got 6 bytes out of 64 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.225: [vfs7552] QUERY DATA READY completed successfully 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.225: [vfs7552] CAPTURE_NUM_STATES entering state 1 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.225: [vfs7552] CAPTURE_NUM_STATES entering state 0 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.225: [vfs7552] QUERY DATA READY entering state 0 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.225: Sending vfs7552_is_image_ready 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.225: [vfs7552] QUERY DATA READY entering state 1 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.226: Receiving 64 bytes 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.226: Got 6 bytes out of 64 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.226: [vfs7552] QUERY DATA READY completed successfully 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.226: [vfs7552] CAPTURE_NUM_STATES entering state 1 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.226: [vfs7552] CAPTURE_NUM_STATES entering state 0 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.226: [vfs7552] QUERY DATA READY entering state 0 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.226: Sending vfs7552_is_image_ready 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.226: [vfs7552] QUERY DATA READY entering state 1 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.226: Receiving 64 bytes 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.227: Got 6 bytes out of 64 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.227: [vfs7552] QUERY DATA READY completed successfully 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.227: [vfs7552] CAPTURE_NUM_STATES entering state 1 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.227: [vfs7552] CAPTURE_NUM_STATES entering state 0 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.227: [vfs7552] QUERY DATA READY entering state 0 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.227: Sending vfs7552_is_image_ready 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.228: [vfs7552] QUERY DATA READY entering state 1 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.228: Receiving 64 bytes 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.228: Got 6 bytes out of 64 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.228: [vfs7552] QUERY DATA READY completed successfully 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.228: [vfs7552] CAPTURE_NUM_STATES entering state 1 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.228: [vfs7552] CAPTURE_NUM_STATES entering state 0 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.228: [vfs7552] QUERY DATA READY entering state 0 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.228: Sending vfs7552_is_image_ready 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.229: [vfs7552] QUERY DATA READY entering state 1 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.229: Receiving 64 bytes 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.229: Got 6 bytes out of 64 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.229: [vfs7552] QUERY DATA READY completed successfully 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.229: [vfs7552] CAPTURE_NUM_STATES entering state 1 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.229: [vfs7552] CAPTURE_NUM_STATES entering state 0 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.229: [vfs7552] QUERY DATA READY entering state 0 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.229: Sending vfs7552_is_image_ready 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.229: [vfs7552] QUERY DATA READY entering state 1 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.229: Receiving 64 bytes 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.230: Got 6 bytes out of 64 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.230: [vfs7552] QUERY DATA READY completed successfully 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.230: [vfs7552] CAPTURE_NUM_STATES entering state 1 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.230: [vfs7552] CAPTURE_NUM_STATES entering state 0 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.230: [vfs7552] QUERY DATA READY entering state 0 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.230: Sending vfs7552_is_image_ready 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.231: [vfs7552] QUERY DATA READY entering state 1 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.231: Receiving 64 bytes 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.231: Got 6 bytes out of 64 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.231: [vfs7552] QUERY DATA READY completed successfully 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.231: [vfs7552] CAPTURE_NUM_STATES entering state 1 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.231: [vfs7552] CAPTURE_NUM_STATES entering state 0 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.231: [vfs7552] QUERY DATA READY entering state 0 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.231: Sending vfs7552_is_image_ready 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.231: [vfs7552] QUERY DATA READY entering state 1 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.232: Receiving 64 bytes 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.232: Got 6 bytes out of 64 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.232: [vfs7552] QUERY DATA READY completed successfully 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.232: [vfs7552] CAPTURE_NUM_STATES entering state 1 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.232: [vfs7552] CAPTURE_NUM_STATES entering state 0 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.232: [vfs7552] QUERY DATA READY entering state 0 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.232: Sending vfs7552_is_image_ready 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.232: [vfs7552] QUERY DATA READY entering state 1 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.232: Receiving 64 bytes 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.233: Got 6 bytes out of 64 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.233: [vfs7552] QUERY DATA READY completed successfully 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.233: [vfs7552] CAPTURE_NUM_STATES entering state 1 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.233: [vfs7552] CAPTURE_NUM_STATES entering state 0 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.233: [vfs7552] QUERY DATA READY entering state 0 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.233: Sending vfs7552_is_image_ready 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.233: [vfs7552] QUERY DATA READY entering state 1 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.233: Receiving 64 bytes 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.234: Got 6 bytes out of 64 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.234: [vfs7552] QUERY DATA READY completed successfully 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.234: [vfs7552] CAPTURE_NUM_STATES entering state 1 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.234: [vfs7552] CAPTURE_NUM_STATES entering state 0 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.234: [vfs7552] QUERY DATA READY entering state 0 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.234: Sending vfs7552_is_image_ready 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.234: [vfs7552] QUERY DATA READY entering state 1 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.234: Receiving 64 bytes 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.235: Got 6 bytes out of 64 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.235: [vfs7552] QUERY DATA READY completed successfully 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.235: [vfs7552] CAPTURE_NUM_STATES entering state 1 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.235: [vfs7552] CAPTURE_NUM_STATES entering state 0 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.235: [vfs7552] QUERY DATA READY entering state 0 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.235: Sending vfs7552_is_image_ready 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.235: [vfs7552] QUERY DATA READY entering state 1 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.235: Receiving 64 bytes 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.236: Got 6 bytes out of 64 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.236: [vfs7552] QUERY DATA READY completed successfully 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.236: [vfs7552] CAPTURE_NUM_STATES entering state 1 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.236: [vfs7552] CAPTURE_NUM_STATES entering state 0 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.236: [vfs7552] QUERY DATA READY entering state 0 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.236: Sending vfs7552_is_image_ready 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.236: [vfs7552] QUERY DATA READY entering state 1 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.236: Receiving 64 bytes 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.237: Got 6 bytes out of 64 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.237: [vfs7552] QUERY DATA READY completed successfully 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.237: [vfs7552] CAPTURE_NUM_STATES entering state 1 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.237: [vfs7552] CAPTURE_NUM_STATES entering state 0 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.237: [vfs7552] QUERY DATA READY entering state 0 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.237: Sending vfs7552_is_image_ready 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.237: [vfs7552] QUERY DATA READY entering state 1 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.237: Receiving 64 bytes 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.238: Got 6 bytes out of 64 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.238: [vfs7552] QUERY DATA READY completed successfully 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.238: [vfs7552] CAPTURE_NUM_STATES entering state 1 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.238: [vfs7552] CAPTURE_NUM_STATES entering state 0 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.238: [vfs7552] QUERY DATA READY entering state 0 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.238: Sending vfs7552_is_image_ready 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.238: [vfs7552] QUERY DATA READY entering state 1 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.238: Receiving 64 bytes 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.238: Got 6 bytes out of 64 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.239: [vfs7552] QUERY DATA READY completed successfully 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.239: [vfs7552] CAPTURE_NUM_STATES entering state 1 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.239: [vfs7552] CAPTURE_NUM_STATES entering state 0 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.239: [vfs7552] QUERY DATA READY entering state 0 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.239: Sending vfs7552_is_image_ready 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.239: [vfs7552] QUERY DATA READY entering state 1 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.239: Receiving 64 bytes 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.239: Got 6 bytes out of 64 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.240: [vfs7552] QUERY DATA READY completed successfully 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.240: [vfs7552] CAPTURE_NUM_STATES entering state 1 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.240: [vfs7552] CAPTURE_NUM_STATES entering state 0 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.240: [vfs7552] QUERY DATA READY entering state 0 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.240: Sending vfs7552_is_image_ready 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.240: [vfs7552] QUERY DATA READY entering state 1 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.240: Receiving 64 bytes 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.240: Got 6 bytes out of 64 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.240: [vfs7552] QUERY DATA READY completed successfully 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.240: [vfs7552] CAPTURE_NUM_STATES entering state 1 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.240: [vfs7552] CAPTURE_NUM_STATES entering state 0 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.240: [vfs7552] QUERY DATA READY entering state 0 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.240: Sending vfs7552_is_image_ready 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.241: [vfs7552] QUERY DATA READY entering state 1 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.241: Receiving 64 bytes 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.241: Got 6 bytes out of 64 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.241: [vfs7552] QUERY DATA READY completed successfully 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.241: [vfs7552] CAPTURE_NUM_STATES entering state 1 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.241: [vfs7552] CAPTURE_NUM_STATES entering state 0 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.241: [vfs7552] QUERY DATA READY entering state 0 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.241: Sending vfs7552_is_image_ready 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.242: [vfs7552] QUERY DATA READY entering state 1 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.242: Receiving 64 bytes 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.242: Got 6 bytes out of 64 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.242: [vfs7552] QUERY DATA READY completed successfully 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.242: [vfs7552] CAPTURE_NUM_STATES entering state 1 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.242: [vfs7552] CAPTURE_NUM_STATES entering state 0 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.242: [vfs7552] QUERY DATA READY entering state 0 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.242: Sending vfs7552_is_image_ready 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.243: [vfs7552] QUERY DATA READY entering state 1 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.243: Receiving 64 bytes 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.243: Got 6 bytes out of 64 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.243: [vfs7552] QUERY DATA READY completed successfully 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.243: [vfs7552] CAPTURE_NUM_STATES entering state 1 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.243: [vfs7552] CAPTURE_NUM_STATES entering state 0 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.243: [vfs7552] QUERY DATA READY entering state 0 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.243: Sending vfs7552_is_image_ready 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.244: [vfs7552] QUERY DATA READY entering state 1 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.244: Receiving 64 bytes 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.244: Got 6 bytes out of 64 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.244: [vfs7552] QUERY DATA READY completed successfully 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.244: [vfs7552] CAPTURE_NUM_STATES entering state 1 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.244: [vfs7552] CAPTURE_NUM_STATES entering state 0 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.244: [vfs7552] QUERY DATA READY entering state 0 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.244: Sending vfs7552_is_image_ready 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.245: [vfs7552] QUERY DATA READY entering state 1 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.245: Receiving 64 bytes 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.245: Got 6 bytes out of 64 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.245: [vfs7552] QUERY DATA READY completed successfully 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.245: [vfs7552] CAPTURE_NUM_STATES entering state 1 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.245: [vfs7552] CAPTURE_NUM_STATES entering state 0 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.245: [vfs7552] QUERY DATA READY entering state 0 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.245: Sending vfs7552_is_image_ready 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.246: [vfs7552] QUERY DATA READY entering state 1 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.246: Receiving 64 bytes 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.246: Got 6 bytes out of 64 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.246: [vfs7552] QUERY DATA READY completed successfully 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.246: [vfs7552] CAPTURE_NUM_STATES entering state 1 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.246: [vfs7552] CAPTURE_NUM_STATES entering state 0 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.246: [vfs7552] QUERY DATA READY entering state 0 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.246: Sending vfs7552_is_image_ready 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.247: [vfs7552] QUERY DATA READY entering state 1 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.247: Receiving 64 bytes 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.247: Got 6 bytes out of 64 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.247: [vfs7552] QUERY DATA READY completed successfully 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.247: [vfs7552] CAPTURE_NUM_STATES entering state 1 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.247: [vfs7552] CAPTURE_NUM_STATES entering state 0 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.247: [vfs7552] QUERY DATA READY entering state 0 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.247: Sending vfs7552_is_image_ready 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.248: [vfs7552] QUERY DATA READY entering state 1 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.248: Receiving 64 bytes 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.248: Got 6 bytes out of 64 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.248: [vfs7552] QUERY DATA READY completed successfully 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.248: [vfs7552] CAPTURE_NUM_STATES entering state 1 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.248: [vfs7552] CAPTURE_NUM_STATES entering state 0 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.248: [vfs7552] QUERY DATA READY entering state 0 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.248: Sending vfs7552_is_image_ready 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.249: [vfs7552] QUERY DATA READY entering state 1 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.249: Receiving 64 bytes 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.249: Got 6 bytes out of 64 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.249: [vfs7552] QUERY DATA READY completed successfully 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.249: [vfs7552] CAPTURE_NUM_STATES entering state 1 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.249: [vfs7552] CAPTURE_NUM_STATES entering state 0 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.249: [vfs7552] QUERY DATA READY entering state 0 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.249: Sending vfs7552_is_image_ready 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.249: [vfs7552] QUERY DATA READY entering state 1 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.249: Receiving 64 bytes 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.250: Got 6 bytes out of 64 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.250: [vfs7552] QUERY DATA READY completed successfully 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.250: [vfs7552] CAPTURE_NUM_STATES entering state 1 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.250: [vfs7552] CAPTURE_NUM_STATES entering state 0 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.250: [vfs7552] QUERY DATA READY entering state 0 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.250: Sending vfs7552_is_image_ready 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.250: [vfs7552] QUERY DATA READY entering state 1 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.250: Receiving 64 bytes 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.251: Got 6 bytes out of 64 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.251: [vfs7552] QUERY DATA READY completed successfully 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.251: [vfs7552] CAPTURE_NUM_STATES entering state 1 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.251: [vfs7552] CAPTURE_NUM_STATES entering state 2 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.251: [vfs7552] REQUEST CHUNK entering state 0 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.251: Sending vfs7552_read_image_chunk 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.251: [vfs7552] REQUEST CHUNK completed successfully 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.251: [vfs7552] CAPTURE_NUM_STATES entering state 3 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.252: [vfs7552] CAPTURE_NUM_STATES entering state 2 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.252: [vfs7552] REQUEST CHUNK entering state 0 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.252: Sending vfs7552_read_image_chunk 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.252: [vfs7552] REQUEST CHUNK completed successfully 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.252: [vfs7552] CAPTURE_NUM_STATES entering state 3 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.253: [vfs7552] CAPTURE_NUM_STATES entering state 2 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.253: [vfs7552] REQUEST CHUNK entering state 0 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.253: Sending vfs7552_read_image_chunk 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.253: [vfs7552] REQUEST CHUNK completed successfully 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.253: [vfs7552] CAPTURE_NUM_STATES entering state 3 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.254: [vfs7552] CAPTURE_NUM_STATES entering state 4 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.254: Cleaning image 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.254: variance_after = 16 184s 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.254: [vfs7552] CAPTURE_NUM_STATES completed successfully 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.254: [vfs7552] DEACTIVATE_NUM_STATES entering state 0 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.264: [vfs7552] DEACTIVATE_NUM_STATES entering state 1 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.264: [vfs7552] STOP CAPTURE entering state 0 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.264: Sending vfs7552_cmd_04 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.265: [vfs7552] STOP CAPTURE entering state 1 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.265: Receiving 64 bytes 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.265: [vfs7552] STOP CAPTURE entering state 2 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.265: Sending vfs7552_cmd_52 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.265: [vfs7552] STOP CAPTURE entering state 3 184s (process:2314): libfprint-vfs7552-DEBUG: 16:48:21.266: Receiving 64 bytes 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.266: [vfs7552] STOP CAPTURE completed successfully 184s (process:2314): libfprint-SSM-DEBUG: 16:48:21.266: [vfs7552] DEACTIVATE_NUM_STATES completed successfully 184s (process:2314): libfprint-device-DEBUG: 16:48:21.266: Device reported finger status change: FP_FINGER_STATUS_NONE 184s (process:2314): libfprint-image_device-DEBUG: 16:48:21.266: Image device reported finger status: off 184s (process:2314): libfprint-image_device-DEBUG: 16:48:21.266: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 184s (process:2314): libfprint-image_device-DEBUG: 16:48:21.266: Deactivating image device 184s (process:2314): libfprint-image_device-DEBUG: 16:48:21.266: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_DEACTIVATING 184s (process:2314): libfprint-image_device-DEBUG: 16:48:21.266: Image device deactivation completed 184s (process:2314): libfprint-image_device-DEBUG: 16:48:21.266: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE 184s (process:2314): libfprint-device-DEBUG: 16:48:21.266: Device reported capture completion 184s (process:2314): libfprint-device-DEBUG: 16:48:21.266: Completing action FPI_DEVICE_ACTION_CAPTURE in idle! 184s (process:2314): libfprint-device-DEBUG: 16:48:21.266: Updated temperature model after 2.72 seconds, ratio 0.27 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 184s (process:2314): libfprint-image_device-DEBUG: 16:48:21.325: Image device close completed 184s (process:2314): libfprint-device-DEBUG: 16:48:21.325: Device reported close completion 184s (process:2314): libfprint-device-DEBUG: 16:48:21.326: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 184s (process:2314): libfprint-device-DEBUG: 16:48:21.326: Updated temperature model after 0.06 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 184s ** (umockdev-run:2310): DEBUG: 16:48:21.433: umockdev.vala:150: Removing test bed /tmp/umockdev.DPB9J2 184s (umockdev-run:2310): GLib-DEBUG: 16:48:21.436: unsetenv() is not thread-safe and should not be used after threads are created 184s Comparing PNGs /tmp/libfprint-umockdev-test-6y7ma0nb/capture.png and /usr/share/installed-tests/libfprint-2/vfs7552/capture.png 184s PASS: libfprint-2/driver-vfs7552.test 184s Running test: libfprint-2/driver-elanspi.test 184s ** (umockdev-run:2323): DEBUG: 16:48:21.533: umockdev.vala:123: Created udev test bed /tmp/umockdev.6YE2J2 184s ** (umockdev-run:2323): DEBUG: 16:48:21.533: umockdev.vala:1297: 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 184s ** (umockdev-run:2323): DEBUG: 16:48:21.533: umockdev.vala:1366: 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) 184s ** (umockdev-run:2323): DEBUG: 16:48:21.537: umockdev.vala:1430: create_node_for_device: creating pty device /tmp/umockdev.6YE2J2/dev/hidraw0: got pty /dev/pts/0 184s ** (umockdev-run:2323): DEBUG: 16:48:21.537: umockdev.vala:1451: create_node_for_device: creating ptymap symlink /tmp/umockdev.6YE2J2/dev/.ptymap/_dev_pts_0 184s ** (umockdev-run:2323): DEBUG: 16:48:21.537: umockdev.vala:1297: parsing device description for /devices/pci0000:00/0000:00:15.1/i2c_designware.1/i2c-1/i2c-ELAN1300:00/0018:04F3:3057.0001 184s ** (umockdev-run:2323): DEBUG: 16:48:21.538: umockdev.vala:1366: creating device /devices/pci0000:00/0000:00:15.1/i2c_designware.1/i2c-1/i2c-ELAN1300:00/0018:04F3:3057.0001 (subsystem hid) 184s ** (umockdev-run:2323): DEBUG: 16:48:21.540: umockdev.vala:1297: parsing device description for /devices/pci0000:00/0000:00:15.1/i2c_designware.1/i2c-1/i2c-ELAN1300:00 184s ** (umockdev-run:2323): DEBUG: 16:48:21.540: umockdev.vala:1366: creating device /devices/pci0000:00/0000:00:15.1/i2c_designware.1/i2c-1/i2c-ELAN1300:00 (subsystem i2c) 184s ** (umockdev-run:2323): DEBUG: 16:48:21.540: umockdev.vala:1297: parsing device description for /devices/pci0000:00/0000:00:15.1/i2c_designware.1/i2c-1 184s ** (umockdev-run:2323): DEBUG: 16:48:21.540: umockdev.vala:1366: creating device /devices/pci0000:00/0000:00:15.1/i2c_designware.1/i2c-1 (subsystem i2c) 184s ** (umockdev-run:2323): DEBUG: 16:48:21.541: umockdev.vala:1297: parsing device description for /devices/pci0000:00/0000:00:15.1/i2c_designware.1 184s ** (umockdev-run:2323): DEBUG: 16:48:21.541: umockdev.vala:1366: creating device /devices/pci0000:00/0000:00:15.1/i2c_designware.1 (subsystem platform) 184s ** (umockdev-run:2323): DEBUG: 16:48:21.541: umockdev.vala:1297: parsing device description for /devices/pci0000:00/0000:00:15.1 184s ** (umockdev-run:2323): DEBUG: 16:48:21.542: umockdev.vala:1366: creating device /devices/pci0000:00/0000:00:15.1 (subsystem pci) 184s ** (umockdev-run:2323): DEBUG: 16:48:21.543: umockdev.vala:1297: parsing device description for /devices/pci0000:00/0000:00:1e.2/pxa2xx-spi.3/spi_master/spi0/spi-ELAN7001:00/spidev/spidev0.0 184s ** (umockdev-run:2323): DEBUG: 16:48:21.543: umockdev.vala:1366: creating device /devices/pci0000:00/0000:00:1e.2/pxa2xx-spi.3/spi_master/spi0/spi-ELAN7001:00/spidev/spidev0.0 (subsystem spidev) 184s ** (umockdev-run:2323): DEBUG: 16:48:21.544: umockdev.vala:1430: create_node_for_device: creating pty device /tmp/umockdev.6YE2J2/dev/spidev0.0: got pty /dev/pts/1 184s ** (umockdev-run:2323): DEBUG: 16:48:21.544: umockdev.vala:1451: create_node_for_device: creating ptymap symlink /tmp/umockdev.6YE2J2/dev/.ptymap/_dev_pts_1 184s ** (umockdev-run:2323): DEBUG: 16:48:21.544: umockdev.vala:1297: parsing device description for /devices/pci0000:00/0000:00:1e.2/pxa2xx-spi.3/spi_master/spi0/spi-ELAN7001:00 184s ** (umockdev-run:2323): DEBUG: 16:48:21.544: umockdev.vala:1366: creating device /devices/pci0000:00/0000:00:1e.2/pxa2xx-spi.3/spi_master/spi0/spi-ELAN7001:00 (subsystem spi) 184s ** (umockdev-run:2323): DEBUG: 16:48:21.546: umockdev.vala:1297: parsing device description for /devices/pci0000:00/0000:00:1e.2/pxa2xx-spi.3/spi_master/spi0 184s ** (umockdev-run:2323): DEBUG: 16:48:21.546: umockdev.vala:1366: creating device /devices/pci0000:00/0000:00:1e.2/pxa2xx-spi.3/spi_master/spi0 (subsystem spi_master) 184s ** (umockdev-run:2323): DEBUG: 16:48:21.547: umockdev.vala:1297: parsing device description for /devices/pci0000:00/0000:00:1e.2/pxa2xx-spi.3 184s ** (umockdev-run:2323): DEBUG: 16:48:21.548: umockdev.vala:1366: creating device /devices/pci0000:00/0000:00:1e.2/pxa2xx-spi.3 (subsystem platform) 184s ** (umockdev-run:2323): DEBUG: 16:48:21.548: umockdev.vala:1297: parsing device description for /devices/pci0000:00/0000:00:1e.2 184s ** (umockdev-run:2323): DEBUG: 16:48:21.548: umockdev.vala:1366: creating device /devices/pci0000:00/0000:00:1e.2 (subsystem pci) 184s (umockdev-run:2323): GLib-GIO-DEBUG: 16:48:21.549: _g_io_module_get_default: Found default implementation local (GLocalVfs) for ?gio-vfs? 184s (process:2327): libfprint-context-DEBUG: 16:48:21.641: Initializing FpContext (libfprint version 1.94.7+tod1) 184s (process:2327): libfprint-tod-DEBUG: 16:48:21.642: Impossible to load the shared drivers dir Error opening directory “/usr/lib/aarch64-linux-gnu/libfprint-2/tod-1”: No such file or directory 184s (process:2327): libfprint-device-DEBUG: 16:48:21.644: Device reported probe completion 184s (process:2327): libfprint-device-DEBUG: 16:48:21.644: Completing action FPI_DEVICE_ACTION_PROBE in idle! 184s (process:2327): libfprint-device-DEBUG: 16:48:21.644: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 184s (process:2327): libfprint-elanspi-DEBUG: 16:48:21.645: 72646244: ../libfprint/drivers/elanspi.c:1562 184s (process:2327): libfprint-image_device-DEBUG: 16:48:21.645: Image device open completed 184s (process:2327): libfprint-device-DEBUG: 16:48:21.645: Device reported open completion 184s (process:2327): libfprint-device-DEBUG: 16:48:21.646: Completing action FPI_DEVICE_ACTION_OPEN in idle! 184s (process:2327): libfprint-device-DEBUG: 16:48:21.646: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 184s (process:2327): libfprint-device-DEBUG: 16:48:21.646: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 184s (process:2327): libfprint-image_device-DEBUG: 16:48:21.646: Activating image device 184s (process:2327): libfprint-image_device-DEBUG: 16:48:21.646: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING 184s (process:2327): libfprint-SSM-DEBUG: 16:48:21.646: [elanspi] ELANSPI_INIT_NSTATES entering state 0 184s libfprint-Message: 16:48:21.646: Failed to read spidev block size, using 4096 184s (process:2327): libfprint-SSM-DEBUG: 16:48:21.647: [elanspi] ELANSPI_INIT_NSTATES entering state 1 184s (process:2327): libfprint-elanspi-DEBUG: 16:48:21.647: got status 81 184s (process:2327): libfprint-elanspi-DEBUG: 16:48:21.647: sync hw reset 184s (process:2327): libfprint-SSM-DEBUG: 16:48:21.647: [elanspi] ELANSPI_INIT_NSTATES entering state 2 184s (process:2327): libfprint-SSM-DEBUG: 16:48:21.651: [elanspi] ELANSPI_INIT_NSTATES entering state 3 184s (process:2327): libfprint-elanspi-DEBUG: 16:48:21.651: sw reset ok 184s (process:2327): libfprint-SSM-DEBUG: 16:48:21.652: [elanspi] ELANSPI_INIT_NSTATES entering state 4 184s (process:2327): libfprint-elanspi-DEBUG: 16:48:21.652: raw height = 96 184s (process:2327): libfprint-SSM-DEBUG: 16:48:21.652: [elanspi] ELANSPI_INIT_NSTATES entering state 5 184s (process:2327): libfprint-elanspi-DEBUG: 16:48:21.652: raw width = 96 184s (process:2327): libfprint-SSM-DEBUG: 16:48:21.653: [elanspi] ELANSPI_INIT_NSTATES entering state 6 184s (process:2327): libfprint-elanspi-DEBUG: 16:48:21.653: raw reg17 = 175 184s (process:2327): libfprint-SSM-DEBUG: 16:48:21.653: [elanspi] ELANSPI_INIT_NSTATES entering state 7 184s (process:2327): libfprint-elanspi-DEBUG: 16:48:21.653: raw version = 09 184s (process:2327): libfprint-elanspi-DEBUG: 16:48:21.653: after hardcoded lookup; 96x96, version 1 184s (process:2327): libfprint-elanspi-DEBUG: 16:48:21.653: found sensor ID 6 => [eFSA96SA] (96 x 96) 184s (process:2327): libfprint-SSM-DEBUG: 16:48:21.653: [elanspi] ELANSPI_INIT_NSTATES entering state 8 184s (process:2327): libfprint-SSM-DEBUG: 16:48:21.657: [elanspi] ELANSPI_INIT_NSTATES entering state 9 184s (process:2327): libfprint-SSM-DEBUG: 16:48:21.658: [elanspi] ELANSPI_INIT_NSTATES entering state 10 184s (process:2327): libfprint-SSM-DEBUG: 16:48:21.658: [elanspi] ELANSPI_INIT_NSTATES entering state 11 184s (process:2327): libfprint-SSM-DEBUG: 16:48:21.658: [elanspi] ELANSPI_INIT_NSTATES entering state 12 184s (process:2327): libfprint-SSM-DEBUG: 16:48:21.658: [elanspi] ELANSPI_INIT_NSTATES entering state 13 184s (process:2327): libfprint-SSM-DEBUG: 16:48:21.659: [elanspi] ELANSPI_INIT_NSTATES entering state 14 184s (process:2327): libfprint-SSM-DEBUG: 16:48:21.659: [elanspi] ELANSPI_INIT_NSTATES entering state 17 184s (process:2327): libfprint-elanspi-DEBUG: 16:48:21.659: got vcm mode = 2 184s (process:2327): libfprint-SSM-DEBUG: 16:48:21.659: [elanspi] ELANSPI_INIT_NSTATES entering state 18 184s (process:2327): libfprint-SSM-DEBUG: 16:48:21.659: [elanspi] ELANSPI_INIT_NSTATES entering state 19 184s (process:2327): libfprint-elanspi-DEBUG: 16:48:21.659: starting calibrate 184s (process:2327): libfprint-SSM-DEBUG: 16:48:21.659: [elanspi] old calibrate entering state 0 184s (process:2327): libfprint-SSM-DEBUG: 16:48:21.661: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0 184s (process:2327): libfprint-SSM-DEBUG: 16:48:21.661: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1 184s (process:2327): libfprint-SSM-DEBUG: 16:48:21.661: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0 184s (process:2327): libfprint-SSM-DEBUG: 16:48:21.661: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1 184s (process:2327): libfprint-SSM-DEBUG: 16:48:21.661: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0 184s (process:2327): libfprint-SSM-DEBUG: 16:48:21.662: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1 184s (process:2327): libfprint-SSM-DEBUG: 16:48:21.662: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0 184s (process:2327): libfprint-SSM-DEBUG: 16:48:21.662: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1 184s (process:2327): libfprint-SSM-DEBUG: 16:48:21.662: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0 184s (process:2327): libfprint-SSM-DEBUG: 16:48:21.662: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1 184s (process:2327): libfprint-SSM-DEBUG: 16:48:21.662: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0 184s (process:2327): libfprint-SSM-DEBUG: 16:48:21.662: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1 184s (process:2327): libfprint-SSM-DEBUG: 16:48:21.662: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0 184s (process:2327): libfprint-SSM-DEBUG: 16:48:21.662: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1 184s (process:2327): libfprint-SSM-DEBUG: 16:48:21.662: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0 184s (process:2327): libfprint-SSM-DEBUG: 16:48:21.663: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1 184s (process:2327): libfprint-SSM-DEBUG: 16:48:21.663: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0 184s (process:2327): libfprint-SSM-DEBUG: 16:48:21.663: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1 184s (process:2327): libfprint-SSM-DEBUG: 16:48:21.663: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0 184s (process:2327): libfprint-SSM-DEBUG: 16:48:21.663: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1 184s (process:2327): libfprint-SSM-DEBUG: 16:48:21.663: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0 184s (process:2327): libfprint-SSM-DEBUG: 16:48:21.663: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1 184s (process:2327): libfprint-SSM-DEBUG: 16:48:21.663: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0 184s (process:2327): libfprint-SSM-DEBUG: 16:48:21.663: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1 184s (process:2327): libfprint-SSM-DEBUG: 16:48:21.663: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0 184s (process:2327): libfprint-SSM-DEBUG: 16:48:21.664: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1 184s (process:2327): libfprint-SSM-DEBUG: 16:48:21.664: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0 184s (process:2327): libfprint-SSM-DEBUG: 16:48:21.664: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1 184s (process:2327): libfprint-SSM-DEBUG: 16:48:21.664: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0 184s (process:2327): libfprint-SSM-DEBUG: 16:48:21.664: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1 184s (process:2327): libfprint-SSM-DEBUG: 16:48:21.664: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0 184s (process:2327): libfprint-SSM-DEBUG: 16:48:21.664: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1 184s (process:2327): libfprint-SSM-DEBUG: 16:48:21.664: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0 184s (process:2327): libfprint-SSM-DEBUG: 16:48:21.664: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1 184s (process:2327): libfprint-SSM-DEBUG: 16:48:21.664: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0 184s (process:2327): libfprint-SSM-DEBUG: 16:48:21.665: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1 184s (process:2327): libfprint-SSM-DEBUG: 16:48:21.665: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0 184s (process:2327): libfprint-SSM-DEBUG: 16:48:21.665: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1 184s (process:2327): libfprint-SSM-DEBUG: 16:48:21.665: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0 184s (process:2327): libfprint-SSM-DEBUG: 16:48:21.665: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1 184s (process:2327): libfprint-SSM-DEBUG: 16:48:21.665: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0 184s (process:2327): libfprint-SSM-DEBUG: 16:48:21.665: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1 184s (process:2327): libfprint-SSM-DEBUG: 16:48:21.665: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0 184s (process:2327): libfprint-SSM-DEBUG: 16:48:21.665: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1 184s (process:2327): libfprint-SSM-DEBUG: 16:48:21.665: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0 184s (process:2327): libfprint-SSM-DEBUG: 16:48:21.666: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1 184s (process:2327): libfprint-SSM-DEBUG: 16:48:21.666: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0 184s (process:2327): libfprint-SSM-DEBUG: 16:48:21.666: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1 184s (process:2327): libfprint-SSM-DEBUG: 16:48:21.666: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0 184s (process:2327): libfprint-SSM-DEBUG: 16:48:21.666: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1 184s (process:2327): libfprint-SSM-DEBUG: 16:48:21.666: [elanspi] ELANSPI_WRTABLE_NSTATES completed successfully 184s (process:2327): libfprint-SSM-DEBUG: 16:48:21.666: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 184s (process:2327): libfprint-SSM-DEBUG: 16:48:21.708: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 184s (process:2327): libfprint-elanspi-DEBUG: 16:48:21.708: dac init is 0x29 184s (process:2327): libfprint-SSM-DEBUG: 16:48:21.709: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 184s (process:2327): libfprint-device-DEBUG: 16:48:21.746: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 184s (process:2327): libfprint-SSM-DEBUG: 16:48:21.752: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 184s (process:2327): libfprint-SSM-DEBUG: 16:48:21.752: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 184s (process:2327): libfprint-SSM-DEBUG: 16:48:21.800: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 184s (process:2327): libfprint-elanspi-DEBUG: 16:48:21.800: calibration ok, saving bg image 184s (process:2327): libfprint-SSM-DEBUG: 16:48:21.800: [elanspi] old calibrate completed successfully 184s (process:2327): libfprint-SSM-DEBUG: 16:48:21.800: [elanspi] ELANSPI_INIT_NSTATES entering state 20 184s (process:2327): libfprint-SSM-DEBUG: 16:48:21.800: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 184s (process:2327): libfprint-SSM-DEBUG: 16:48:21.848: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 184s (process:2327): libfprint-SSM-DEBUG: 16:48:21.848: [elanspi] ELANSPI_INIT_NSTATES entering state 21 184s (process:2327): libfprint-SSM-DEBUG: 16:48:21.848: [elanspi] ELANSPI_INIT_NSTATES completed successfully 184s (process:2327): libfprint-elanspi-DEBUG: 16:48:21.848: 72849469: ../libfprint/drivers/elanspi.c:1596 184s (process:2327): libfprint-image_device-DEBUG: 16:48:21.848: Image device activation completed 184s (process:2327): libfprint-image_device-DEBUG: 16:48:21.848: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE 184s (process:2327): libfprint-image_device-DEBUG: 16:48:21.848: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 184s (process:2327): libfprint-SSM-DEBUG: 16:48:21.848: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 0 184s (process:2327): libfprint-SSM-DEBUG: 16:48:21.848: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 1 184s (process:2327): libfprint-SSM-DEBUG: 16:48:21.848: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 184s (process:2327): libfprint-elanspi-DEBUG: 16:48:21.848: started capturer 184s (process:2327): libfprint-device-DEBUG: 16:48:21.848: Device reported finger status change: FP_FINGER_STATUS_NEEDED 184s (process:2327): libfprint-SSM-DEBUG: 16:48:21.897: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 184s (process:2327): libfprint-SSM-DEBUG: 16:48:21.897: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 2 184s (process:2327): libfprint-elanspi-DEBUG: 16:48:21.898: stddev=933d, ip=40, is_fp=0, is_empty=2 184s (process:2327): libfprint-SSM-DEBUG: 16:48:21.898: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 1 184s (process:2327): libfprint-SSM-DEBUG: 16:48:21.898: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 184s (process:2327): libfprint-SSM-DEBUG: 16:48:21.948: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 184s (process:2327): libfprint-SSM-DEBUG: 16:48:21.948: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 2 184s (process:2327): libfprint-elanspi-DEBUG: 16:48:21.948: stddev=829d, ip=48, is_fp=0, is_empty=2 184s (process:2327): libfprint-SSM-DEBUG: 16:48:21.948: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 1 184s (process:2327): libfprint-SSM-DEBUG: 16:48:21.948: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 185s (process:2327): libfprint-SSM-DEBUG: 16:48:21.997: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 185s (process:2327): libfprint-SSM-DEBUG: 16:48:21.997: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 2 185s (process:2327): libfprint-elanspi-DEBUG: 16:48:21.998: stddev=1307d, ip=37, is_fp=0, is_empty=2 185s (process:2327): libfprint-SSM-DEBUG: 16:48:21.998: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 1 185s (process:2327): libfprint-SSM-DEBUG: 16:48:21.998: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 185s (process:2327): libfprint-SSM-DEBUG: 16:48:22.046: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 185s (process:2327): libfprint-SSM-DEBUG: 16:48:22.046: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 2 185s (process:2327): libfprint-elanspi-DEBUG: 16:48:22.046: stddev=1163d, ip=38, is_fp=0, is_empty=2 185s (process:2327): libfprint-SSM-DEBUG: 16:48:22.046: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 1 185s (process:2327): libfprint-SSM-DEBUG: 16:48:22.046: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 185s (process:2327): libfprint-SSM-DEBUG: 16:48:22.095: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 185s (process:2327): libfprint-SSM-DEBUG: 16:48:22.095: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 2 185s (process:2327): libfprint-elanspi-DEBUG: 16:48:22.096: stddev=960d, ip=43, is_fp=0, is_empty=2 185s (process:2327): libfprint-SSM-DEBUG: 16:48:22.096: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 1 185s (process:2327): libfprint-SSM-DEBUG: 16:48:22.096: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 185s (process:2327): libfprint-SSM-DEBUG: 16:48:22.141: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 185s (process:2327): libfprint-SSM-DEBUG: 16:48:22.141: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 2 185s (process:2327): libfprint-elanspi-DEBUG: 16:48:22.141: stddev=879d, ip=41, is_fp=0, is_empty=2 185s (process:2327): libfprint-SSM-DEBUG: 16:48:22.141: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 1 185s (process:2327): libfprint-SSM-DEBUG: 16:48:22.141: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 185s (process:2327): libfprint-SSM-DEBUG: 16:48:22.185: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 185s (process:2327): libfprint-SSM-DEBUG: 16:48:22.185: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 2 185s (process:2327): libfprint-elanspi-DEBUG: 16:48:22.186: stddev=925d, ip=44, is_fp=0, is_empty=2 185s (process:2327): libfprint-SSM-DEBUG: 16:48:22.186: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 1 185s (process:2327): libfprint-SSM-DEBUG: 16:48:22.186: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 185s (process:2327): libfprint-SSM-DEBUG: 16:48:22.234: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 185s (process:2327): libfprint-SSM-DEBUG: 16:48:22.234: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 2 185s (process:2327): libfprint-elanspi-DEBUG: 16:48:22.234: stddev=1244d, ip=37, is_fp=0, is_empty=2 185s (process:2327): libfprint-SSM-DEBUG: 16:48:22.234: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 1 185s (process:2327): libfprint-SSM-DEBUG: 16:48:22.234: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 185s (process:2327): libfprint-SSM-DEBUG: 16:48:22.283: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 185s (process:2327): libfprint-SSM-DEBUG: 16:48:22.283: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 2 185s (process:2327): libfprint-elanspi-DEBUG: 16:48:22.283: stddev=709d, ip=48, is_fp=0, is_empty=2 185s (process:2327): libfprint-SSM-DEBUG: 16:48:22.283: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 1 185s (process:2327): libfprint-SSM-DEBUG: 16:48:22.283: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 185s (process:2327): libfprint-SSM-DEBUG: 16:48:22.329: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 185s (process:2327): libfprint-SSM-DEBUG: 16:48:22.329: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 2 185s (process:2327): libfprint-elanspi-DEBUG: 16:48:22.329: stddev=553d, ip=54, is_fp=0, is_empty=2 185s (process:2327): libfprint-SSM-DEBUG: 16:48:22.329: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 1 185s (process:2327): libfprint-SSM-DEBUG: 16:48:22.329: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 185s (process:2327): libfprint-SSM-DEBUG: 16:48:22.374: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 185s (process:2327): libfprint-SSM-DEBUG: 16:48:22.374: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 2 185s (process:2327): libfprint-elanspi-DEBUG: 16:48:22.374: stddev=904d, ip=44, is_fp=0, is_empty=2 185s (process:2327): libfprint-SSM-DEBUG: 16:48:22.374: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 1 185s (process:2327): libfprint-SSM-DEBUG: 16:48:22.374: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 185s (process:2327): libfprint-SSM-DEBUG: 16:48:22.420: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 185s (process:2327): libfprint-SSM-DEBUG: 16:48:22.420: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 2 185s (process:2327): libfprint-elanspi-DEBUG: 16:48:22.420: stddev=951d, ip=46, is_fp=0, is_empty=2 185s (process:2327): libfprint-SSM-DEBUG: 16:48:22.420: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 1 185s (process:2327): libfprint-SSM-DEBUG: 16:48:22.420: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 185s (process:2327): libfprint-SSM-DEBUG: 16:48:22.466: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 185s (process:2327): libfprint-SSM-DEBUG: 16:48:22.466: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 2 185s (process:2327): libfprint-elanspi-DEBUG: 16:48:22.466: stddev=795d, ip=44, is_fp=0, is_empty=2 185s (process:2327): libfprint-SSM-DEBUG: 16:48:22.466: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 1 185s (process:2327): libfprint-SSM-DEBUG: 16:48:22.466: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 185s (process:2327): libfprint-SSM-DEBUG: 16:48:22.510: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 185s (process:2327): libfprint-SSM-DEBUG: 16:48:22.510: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 2 185s (process:2327): libfprint-elanspi-DEBUG: 16:48:22.511: stddev=985d, ip=41, is_fp=0, is_empty=2 185s (process:2327): libfprint-SSM-DEBUG: 16:48:22.511: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 1 185s (process:2327): libfprint-SSM-DEBUG: 16:48:22.511: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 185s (process:2327): libfprint-SSM-DEBUG: 16:48:22.557: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 185s (process:2327): libfprint-SSM-DEBUG: 16:48:22.557: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 2 185s (process:2327): libfprint-elanspi-DEBUG: 16:48:22.557: stddev=938d, ip=40, is_fp=0, is_empty=2 185s (process:2327): libfprint-SSM-DEBUG: 16:48:22.557: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 1 185s (process:2327): libfprint-SSM-DEBUG: 16:48:22.557: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 185s (process:2327): libfprint-SSM-DEBUG: 16:48:22.605: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 185s (process:2327): libfprint-SSM-DEBUG: 16:48:22.605: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 2 185s (process:2327): libfprint-elanspi-DEBUG: 16:48:22.605: stddev=846d, ip=40, is_fp=0, is_empty=2 185s (process:2327): libfprint-SSM-DEBUG: 16:48:22.605: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 1 185s (process:2327): libfprint-SSM-DEBUG: 16:48:22.605: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 185s (process:2327): libfprint-SSM-DEBUG: 16:48:22.652: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 185s (process:2327): libfprint-SSM-DEBUG: 16:48:22.652: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 2 185s (process:2327): libfprint-elanspi-DEBUG: 16:48:22.653: stddev=693d, ip=56, is_fp=0, is_empty=2 185s (process:2327): libfprint-SSM-DEBUG: 16:48:22.653: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 1 185s (process:2327): libfprint-SSM-DEBUG: 16:48:22.653: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 185s (process:2327): libfprint-SSM-DEBUG: 16:48:22.700: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 185s (process:2327): libfprint-SSM-DEBUG: 16:48:22.700: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 2 185s (process:2327): libfprint-elanspi-DEBUG: 16:48:22.700: stddev=777d, ip=50, is_fp=0, is_empty=2 185s (process:2327): libfprint-SSM-DEBUG: 16:48:22.700: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 1 185s (process:2327): libfprint-SSM-DEBUG: 16:48:22.700: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 185s (process:2327): libfprint-SSM-DEBUG: 16:48:22.746: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 185s (process:2327): libfprint-SSM-DEBUG: 16:48:22.746: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 2 185s (process:2327): libfprint-elanspi-DEBUG: 16:48:22.747: stddev=824d, ip=45, is_fp=0, is_empty=2 185s (process:2327): libfprint-SSM-DEBUG: 16:48:22.747: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 1 185s (process:2327): libfprint-SSM-DEBUG: 16:48:22.747: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 185s (process:2327): libfprint-SSM-DEBUG: 16:48:22.791: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 185s (process:2327): libfprint-SSM-DEBUG: 16:48:22.791: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 2 185s (process:2327): libfprint-elanspi-DEBUG: 16:48:22.792: stddev=521d, ip=50, is_fp=0, is_empty=2 185s (process:2327): libfprint-SSM-DEBUG: 16:48:22.792: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 1 185s (process:2327): libfprint-SSM-DEBUG: 16:48:22.792: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 185s (process:2327): libfprint-SSM-DEBUG: 16:48:22.837: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 185s (process:2327): libfprint-SSM-DEBUG: 16:48:22.837: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 2 185s (process:2327): libfprint-elanspi-DEBUG: 16:48:22.837: stddev=670d, ip=47, is_fp=0, is_empty=2 185s (process:2327): libfprint-SSM-DEBUG: 16:48:22.837: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 1 185s (process:2327): libfprint-SSM-DEBUG: 16:48:22.837: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 185s (process:2327): libfprint-SSM-DEBUG: 16:48:22.884: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 185s (process:2327): libfprint-SSM-DEBUG: 16:48:22.884: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 2 185s (process:2327): libfprint-elanspi-DEBUG: 16:48:22.885: stddev=1262d, ip=39, is_fp=0, is_empty=2 185s (process:2327): libfprint-SSM-DEBUG: 16:48:22.885: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 1 185s (process:2327): libfprint-SSM-DEBUG: 16:48:22.885: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 185s (process:2327): libfprint-SSM-DEBUG: 16:48:22.932: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 185s (process:2327): libfprint-SSM-DEBUG: 16:48:22.933: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 2 185s (process:2327): libfprint-elanspi-DEBUG: 16:48:22.933: stddev=912d, ip=42, is_fp=0, is_empty=2 185s (process:2327): libfprint-SSM-DEBUG: 16:48:22.933: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 1 185s (process:2327): libfprint-SSM-DEBUG: 16:48:22.933: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 186s (process:2327): libfprint-SSM-DEBUG: 16:48:22.981: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 186s (process:2327): libfprint-SSM-DEBUG: 16:48:22.981: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 2 186s (process:2327): libfprint-elanspi-DEBUG: 16:48:22.981: stddev=1402d, ip=37, is_fp=0, is_empty=2 186s (process:2327): libfprint-SSM-DEBUG: 16:48:22.981: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 1 186s (process:2327): libfprint-SSM-DEBUG: 16:48:22.981: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 186s (process:2327): libfprint-SSM-DEBUG: 16:48:23.028: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 186s (process:2327): libfprint-SSM-DEBUG: 16:48:23.028: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 2 186s (process:2327): libfprint-elanspi-DEBUG: 16:48:23.028: stddev=1530d, ip=32, is_fp=0, is_empty=2 186s (process:2327): libfprint-SSM-DEBUG: 16:48:23.028: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 1 186s (process:2327): libfprint-SSM-DEBUG: 16:48:23.028: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 186s (process:2327): libfprint-SSM-DEBUG: 16:48:23.074: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 186s (process:2327): libfprint-SSM-DEBUG: 16:48:23.074: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 2 186s (process:2327): libfprint-elanspi-DEBUG: 16:48:23.074: stddev=718159d, ip=6, is_fp=1, is_empty=0 186s (process:2327): libfprint-SSM-DEBUG: 16:48:23.074: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 1 186s (process:2327): libfprint-SSM-DEBUG: 16:48:23.074: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 186s (process:2327): libfprint-SSM-DEBUG: 16:48:23.119: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 186s (process:2327): libfprint-SSM-DEBUG: 16:48:23.119: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 2 186s (process:2327): libfprint-elanspi-DEBUG: 16:48:23.120: stddev=400929d, ip=0, is_fp=2, is_empty=0 186s (process:2327): libfprint-device-DEBUG: 16:48:23.120: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 186s (process:2327): libfprint-image_device-DEBUG: 16:48:23.120: Image device reported finger status: on 186s (process:2327): libfprint-image_device-DEBUG: 16:48:23.120: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 186s (process:2327): libfprint-SSM-DEBUG: 16:48:23.120: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 3 186s (process:2327): libfprint-SSM-DEBUG: 16:48:23.120: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 186s (process:2327): libfprint-SSM-DEBUG: 16:48:23.167: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 186s (process:2327): libfprint-SSM-DEBUG: 16:48:23.167: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 4 186s (process:2327): libfprint-elanspi-DEBUG: 16:48:23.167: stddev=346514d, ip=0, is_fp=1, is_empty=0 186s (process:2327): libfprint-SSM-DEBUG: 16:48:23.168: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 3 186s (process:2327): libfprint-SSM-DEBUG: 16:48:23.168: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 186s (process:2327): libfprint-SSM-DEBUG: 16:48:23.214: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 186s (process:2327): libfprint-SSM-DEBUG: 16:48:23.214: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 4 186s (process:2327): libfprint-elanspi-DEBUG: 16:48:23.214: stddev=324160d, ip=0, is_fp=1, is_empty=0 186s (process:2327): libfprint-elanspi-DEBUG: 16:48:23.215: diff = 107344 186s (process:2327): libfprint-SSM-DEBUG: 16:48:23.215: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 3 186s (process:2327): libfprint-SSM-DEBUG: 16:48:23.215: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 186s (process:2327): libfprint-SSM-DEBUG: 16:48:23.261: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 186s (process:2327): libfprint-SSM-DEBUG: 16:48:23.261: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 4 186s (process:2327): libfprint-elanspi-DEBUG: 16:48:23.261: stddev=339430d, ip=0, is_fp=1, is_empty=0 186s (process:2327): libfprint-elanspi-DEBUG: 16:48:23.261: diff = 246471 186s (process:2327): libfprint-SSM-DEBUG: 16:48:23.261: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 3 186s (process:2327): libfprint-SSM-DEBUG: 16:48:23.261: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 186s (process:2327): libfprint-SSM-DEBUG: 16:48:23.306: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 186s (process:2327): libfprint-SSM-DEBUG: 16:48:23.306: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 4 186s (process:2327): libfprint-elanspi-DEBUG: 16:48:23.306: stddev=334711d, ip=0, is_fp=1, is_empty=0 186s (process:2327): libfprint-elanspi-DEBUG: 16:48:23.307: diff = 73010 186s (process:2327): libfprint-SSM-DEBUG: 16:48:23.307: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 3 186s (process:2327): libfprint-SSM-DEBUG: 16:48:23.307: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 186s (process:2327): libfprint-SSM-DEBUG: 16:48:23.352: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 186s (process:2327): libfprint-SSM-DEBUG: 16:48:23.352: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 4 186s (process:2327): libfprint-elanspi-DEBUG: 16:48:23.352: stddev=317574d, ip=0, is_fp=1, is_empty=0 186s (process:2327): libfprint-elanspi-DEBUG: 16:48:23.353: diff = 58831 186s (process:2327): libfprint-elanspi-DEBUG: 16:48:23.353: ignoring b.c. difference is too small 186s (process:2327): libfprint-SSM-DEBUG: 16:48:23.353: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 3 186s (process:2327): libfprint-SSM-DEBUG: 16:48:23.353: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 186s (process:2327): libfprint-SSM-DEBUG: 16:48:23.398: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 186s (process:2327): libfprint-SSM-DEBUG: 16:48:23.398: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 4 186s (process:2327): libfprint-elanspi-DEBUG: 16:48:23.398: stddev=285577d, ip=0, is_fp=1, is_empty=0 186s (process:2327): libfprint-elanspi-DEBUG: 16:48:23.399: diff = 241923 186s (process:2327): libfprint-SSM-DEBUG: 16:48:23.399: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 3 186s (process:2327): libfprint-SSM-DEBUG: 16:48:23.399: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 186s (process:2327): libfprint-SSM-DEBUG: 16:48:23.443: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 186s (process:2327): libfprint-SSM-DEBUG: 16:48:23.443: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 4 186s (process:2327): libfprint-elanspi-DEBUG: 16:48:23.443: stddev=417772d, ip=0, is_fp=2, is_empty=0 186s (process:2327): libfprint-elanspi-DEBUG: 16:48:23.444: diff = 254823 186s (process:2327): libfprint-SSM-DEBUG: 16:48:23.444: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 3 186s (process:2327): libfprint-SSM-DEBUG: 16:48:23.444: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 186s (process:2327): libfprint-SSM-DEBUG: 16:48:23.492: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 186s (process:2327): libfprint-SSM-DEBUG: 16:48:23.492: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 4 186s (process:2327): libfprint-elanspi-DEBUG: 16:48:23.492: stddev=541148d, ip=0, is_fp=2, is_empty=0 186s (process:2327): libfprint-elanspi-DEBUG: 16:48:23.493: diff = 290922 186s (process:2327): libfprint-SSM-DEBUG: 16:48:23.493: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 3 186s (process:2327): libfprint-SSM-DEBUG: 16:48:23.493: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 186s (process:2327): libfprint-SSM-DEBUG: 16:48:23.537: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 186s (process:2327): libfprint-SSM-DEBUG: 16:48:23.537: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 4 186s (process:2327): libfprint-elanspi-DEBUG: 16:48:23.537: stddev=580192d, ip=0, is_fp=2, is_empty=0 186s (process:2327): libfprint-elanspi-DEBUG: 16:48:23.538: diff = 332283 186s (process:2327): libfprint-SSM-DEBUG: 16:48:23.538: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 3 186s (process:2327): libfprint-SSM-DEBUG: 16:48:23.538: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 186s (process:2327): libfprint-SSM-DEBUG: 16:48:23.583: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 186s (process:2327): libfprint-SSM-DEBUG: 16:48:23.583: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 4 186s (process:2327): libfprint-elanspi-DEBUG: 16:48:23.584: stddev=484527d, ip=0, is_fp=2, is_empty=0 186s (process:2327): libfprint-elanspi-DEBUG: 16:48:23.584: diff = 325141 186s (process:2327): libfprint-SSM-DEBUG: 16:48:23.584: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 3 186s (process:2327): libfprint-SSM-DEBUG: 16:48:23.584: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 186s (process:2327): libfprint-SSM-DEBUG: 16:48:23.630: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 186s (process:2327): libfprint-SSM-DEBUG: 16:48:23.630: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 4 186s (process:2327): libfprint-elanspi-DEBUG: 16:48:23.630: stddev=482100d, ip=0, is_fp=2, is_empty=0 186s (process:2327): libfprint-elanspi-DEBUG: 16:48:23.631: diff = 337412 186s (process:2327): libfprint-SSM-DEBUG: 16:48:23.631: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 3 186s (process:2327): libfprint-SSM-DEBUG: 16:48:23.631: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 186s (process:2327): libfprint-SSM-DEBUG: 16:48:23.677: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 186s (process:2327): libfprint-SSM-DEBUG: 16:48:23.677: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 4 186s (process:2327): libfprint-elanspi-DEBUG: 16:48:23.677: stddev=558238d, ip=0, is_fp=2, is_empty=0 186s (process:2327): libfprint-elanspi-DEBUG: 16:48:23.678: diff = 342841 186s (process:2327): libfprint-SSM-DEBUG: 16:48:23.678: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 3 186s (process:2327): libfprint-SSM-DEBUG: 16:48:23.678: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 186s (process:2327): libfprint-SSM-DEBUG: 16:48:23.723: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 186s (process:2327): libfprint-SSM-DEBUG: 16:48:23.723: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 4 186s (process:2327): libfprint-elanspi-DEBUG: 16:48:23.724: stddev=572990d, ip=0, is_fp=2, is_empty=0 186s (process:2327): libfprint-elanspi-DEBUG: 16:48:23.724: diff = 352690 186s (process:2327): libfprint-SSM-DEBUG: 16:48:23.724: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 3 186s (process:2327): libfprint-SSM-DEBUG: 16:48:23.724: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 186s (process:2327): libfprint-SSM-DEBUG: 16:48:23.770: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 186s (process:2327): libfprint-SSM-DEBUG: 16:48:23.770: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 4 186s (process:2327): libfprint-elanspi-DEBUG: 16:48:23.770: stddev=575411d, ip=0, is_fp=2, is_empty=0 186s (process:2327): libfprint-elanspi-DEBUG: 16:48:23.770: diff = 365537 186s (process:2327): libfprint-SSM-DEBUG: 16:48:23.771: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 3 186s (process:2327): libfprint-SSM-DEBUG: 16:48:23.771: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 186s (process:2327): libfprint-SSM-DEBUG: 16:48:23.815: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 186s (process:2327): libfprint-SSM-DEBUG: 16:48:23.815: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 4 186s (process:2327): libfprint-elanspi-DEBUG: 16:48:23.816: stddev=578482d, ip=0, is_fp=2, is_empty=0 186s (process:2327): libfprint-elanspi-DEBUG: 16:48:23.816: diff = 342041 186s (process:2327): libfprint-SSM-DEBUG: 16:48:23.816: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 3 186s (process:2327): libfprint-SSM-DEBUG: 16:48:23.816: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 186s (process:2327): libfprint-SSM-DEBUG: 16:48:23.860: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 186s (process:2327): libfprint-SSM-DEBUG: 16:48:23.860: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 4 186s (process:2327): libfprint-elanspi-DEBUG: 16:48:23.861: stddev=572686d, ip=0, is_fp=2, is_empty=0 186s (process:2327): libfprint-elanspi-DEBUG: 16:48:23.861: diff = 421037 186s (process:2327): libfprint-SSM-DEBUG: 16:48:23.861: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 3 186s (process:2327): libfprint-SSM-DEBUG: 16:48:23.861: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 186s (process:2327): libfprint-SSM-DEBUG: 16:48:23.906: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 186s (process:2327): libfprint-SSM-DEBUG: 16:48:23.906: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 4 186s (process:2327): libfprint-elanspi-DEBUG: 16:48:23.906: stddev=465498d, ip=0, is_fp=2, is_empty=0 186s (process:2327): libfprint-elanspi-DEBUG: 16:48:23.907: diff = 404640 186s (process:2327): libfprint-SSM-DEBUG: 16:48:23.907: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 3 186s (process:2327): libfprint-SSM-DEBUG: 16:48:23.907: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 186s (process:2327): libfprint-SSM-DEBUG: 16:48:23.952: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 186s (process:2327): libfprint-SSM-DEBUG: 16:48:23.952: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 4 186s (process:2327): libfprint-elanspi-DEBUG: 16:48:23.953: stddev=410135d, ip=0, is_fp=2, is_empty=0 186s (process:2327): libfprint-elanspi-DEBUG: 16:48:23.953: diff = 347658 186s (process:2327): libfprint-SSM-DEBUG: 16:48:23.953: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 3 186s (process:2327): libfprint-SSM-DEBUG: 16:48:23.953: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 187s (process:2327): libfprint-SSM-DEBUG: 16:48:23.999: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 187s (process:2327): libfprint-SSM-DEBUG: 16:48:23.999: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 4 187s (process:2327): libfprint-elanspi-DEBUG: 16:48:24.000: stddev=493239d, ip=0, is_fp=2, is_empty=0 187s (process:2327): libfprint-elanspi-DEBUG: 16:48:24.000: diff = 344237 187s (process:2327): libfprint-SSM-DEBUG: 16:48:24.000: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 3 187s (process:2327): libfprint-SSM-DEBUG: 16:48:24.000: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 187s Executing: libfprint-2/driver-elanspi.test 187s (process:2327): libfprint-SSM-DEBUG: 16:48:24.046: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 187s (process:2327): libfprint-SSM-DEBUG: 16:48:24.046: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 4 187s (process:2327): libfprint-elanspi-DEBUG: 16:48:24.046: stddev=553028d, ip=0, is_fp=2, is_empty=0 187s (process:2327): libfprint-elanspi-DEBUG: 16:48:24.047: diff = 419597 187s (process:2327): libfprint-SSM-DEBUG: 16:48:24.047: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 3 187s (process:2327): libfprint-SSM-DEBUG: 16:48:24.047: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 187s (process:2327): libfprint-SSM-DEBUG: 16:48:24.092: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 187s (process:2327): libfprint-SSM-DEBUG: 16:48:24.092: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 4 187s (process:2327): libfprint-elanspi-DEBUG: 16:48:24.093: stddev=574502d, ip=0, is_fp=2, is_empty=0 187s (process:2327): libfprint-elanspi-DEBUG: 16:48:24.093: diff = 408934 187s (process:2327): libfprint-SSM-DEBUG: 16:48:24.093: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 3 187s (process:2327): libfprint-SSM-DEBUG: 16:48:24.093: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 187s (process:2327): libfprint-SSM-DEBUG: 16:48:24.139: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 187s (process:2327): libfprint-SSM-DEBUG: 16:48:24.139: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 4 187s (process:2327): libfprint-elanspi-DEBUG: 16:48:24.139: stddev=645815d, ip=0, is_fp=2, is_empty=0 187s (process:2327): libfprint-elanspi-DEBUG: 16:48:24.139: diff = 409198 187s (process:2327): libfprint-SSM-DEBUG: 16:48:24.139: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 3 187s (process:2327): libfprint-SSM-DEBUG: 16:48:24.139: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 187s (process:2327): libfprint-SSM-DEBUG: 16:48:24.184: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 187s (process:2327): libfprint-SSM-DEBUG: 16:48:24.184: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 4 187s (process:2327): libfprint-elanspi-DEBUG: 16:48:24.185: stddev=677451d, ip=0, is_fp=2, is_empty=0 187s (process:2327): libfprint-elanspi-DEBUG: 16:48:24.185: diff = 429666 187s (process:2327): libfprint-SSM-DEBUG: 16:48:24.185: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 3 187s (process:2327): libfprint-SSM-DEBUG: 16:48:24.185: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 187s (process:2327): libfprint-SSM-DEBUG: 16:48:24.231: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 187s (process:2327): libfprint-SSM-DEBUG: 16:48:24.231: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 4 187s (process:2327): libfprint-elanspi-DEBUG: 16:48:24.231: stddev=634407d, ip=0, is_fp=2, is_empty=0 187s (process:2327): libfprint-elanspi-DEBUG: 16:48:24.231: have enough frames, exiting now 187s (process:2327): libfprint-assembling-DEBUG: 16:48:24.392: calc delta completed in 0.160699 secs 187s (process:2327): libfprint-assembling-DEBUG: 16:48:24.552: calc delta completed in 0.160567 secs 187s (process:2327): libfprint-assembling-DEBUG: 16:48:24.552: errors: 86516 rev: 170625 187s (process:2327): libfprint-assembling-DEBUG: 16:48:24.713: calc delta completed in 0.160909 secs 187s (process:2327): libfprint-assembling-DEBUG: 16:48:24.713: height is 246 187s (process:2327): libfprint-image_device-DEBUG: 16:48:24.715: Image device captured an image 187s (process:2327): libfprint-image_device-DEBUG: 16:48:24.715: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 187s (process:2327): libfprint-device-DEBUG: 16:48:24.715: Device reported finger status change: FP_FINGER_STATUS_PRESENT 187s (process:2327): libfprint-SSM-DEBUG: 16:48:24.715: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 5 187s (process:2327): libfprint-SSM-DEBUG: 16:48:24.715: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 187s (process:2327): libfprint-image-DEBUG: 16:48:24.803: Minutiae scan completed in 0.087443 secs 187s (process:2327): libfprint-SSM-DEBUG: 16:48:24.831: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 187s (process:2327): libfprint-SSM-DEBUG: 16:48:24.831: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 6 187s (process:2327): libfprint-elanspi-DEBUG: 16:48:24.832: stddev=593525d, ip=0, is_fp=2, is_empty=0 187s (process:2327): libfprint-SSM-DEBUG: 16:48:24.832: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 5 187s (process:2327): libfprint-SSM-DEBUG: 16:48:24.832: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 187s (process:2327): libfprint-SSM-DEBUG: 16:48:24.879: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 187s (process:2327): libfprint-SSM-DEBUG: 16:48:24.879: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 6 187s (process:2327): libfprint-elanspi-DEBUG: 16:48:24.879: stddev=610651d, ip=0, is_fp=2, is_empty=0 187s (process:2327): libfprint-SSM-DEBUG: 16:48:24.879: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 5 187s (process:2327): libfprint-SSM-DEBUG: 16:48:24.879: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 187s (process:2327): libfprint-SSM-DEBUG: 16:48:24.926: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 187s (process:2327): libfprint-SSM-DEBUG: 16:48:24.926: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 6 187s (process:2327): libfprint-elanspi-DEBUG: 16:48:24.926: stddev=505673d, ip=0, is_fp=2, is_empty=0 187s (process:2327): libfprint-SSM-DEBUG: 16:48:24.926: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 5 187s (process:2327): libfprint-SSM-DEBUG: 16:48:24.926: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 188s (process:2327): libfprint-SSM-DEBUG: 16:48:24.974: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 188s (process:2327): libfprint-SSM-DEBUG: 16:48:24.974: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 6 188s (process:2327): libfprint-elanspi-DEBUG: 16:48:24.975: stddev=537580d, ip=0, is_fp=2, is_empty=0 188s (process:2327): libfprint-SSM-DEBUG: 16:48:24.975: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 5 188s (process:2327): libfprint-SSM-DEBUG: 16:48:24.975: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 188s (process:2327): libfprint-SSM-DEBUG: 16:48:25.027: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 188s (process:2327): libfprint-SSM-DEBUG: 16:48:25.027: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 6 188s (process:2327): libfprint-elanspi-DEBUG: 16:48:25.027: stddev=520750d, ip=0, is_fp=2, is_empty=0 188s (process:2327): libfprint-SSM-DEBUG: 16:48:25.027: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 5 188s (process:2327): libfprint-SSM-DEBUG: 16:48:25.027: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 188s (process:2327): libfprint-SSM-DEBUG: 16:48:25.076: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 188s (process:2327): libfprint-SSM-DEBUG: 16:48:25.076: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 6 188s (process:2327): libfprint-elanspi-DEBUG: 16:48:25.076: stddev=468008d, ip=0, is_fp=2, is_empty=0 188s (process:2327): libfprint-SSM-DEBUG: 16:48:25.076: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 5 188s (process:2327): libfprint-SSM-DEBUG: 16:48:25.076: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 188s (process:2327): libfprint-SSM-DEBUG: 16:48:25.161: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 188s (process:2327): libfprint-SSM-DEBUG: 16:48:25.161: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 6 188s (process:2327): libfprint-elanspi-DEBUG: 16:48:25.161: stddev=477058d, ip=0, is_fp=2, is_empty=0 188s (process:2327): libfprint-SSM-DEBUG: 16:48:25.161: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 5 188s (process:2327): libfprint-SSM-DEBUG: 16:48:25.161: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 188s (process:2327): libfprint-SSM-DEBUG: 16:48:25.218: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 188s (process:2327): libfprint-SSM-DEBUG: 16:48:25.218: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 6 188s (process:2327): libfprint-elanspi-DEBUG: 16:48:25.218: stddev=460178d, ip=0, is_fp=2, is_empty=0 188s (process:2327): libfprint-SSM-DEBUG: 16:48:25.218: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 5 188s (process:2327): libfprint-SSM-DEBUG: 16:48:25.218: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 188s (process:2327): libfprint-SSM-DEBUG: 16:48:25.264: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 188s (process:2327): libfprint-SSM-DEBUG: 16:48:25.264: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 6 188s (process:2327): libfprint-elanspi-DEBUG: 16:48:25.264: stddev=538508d, ip=0, is_fp=2, is_empty=0 188s (process:2327): libfprint-SSM-DEBUG: 16:48:25.264: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 5 188s (process:2327): libfprint-SSM-DEBUG: 16:48:25.264: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 188s (process:2327): libfprint-SSM-DEBUG: 16:48:25.326: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 188s (process:2327): libfprint-SSM-DEBUG: 16:48:25.326: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 6 188s (process:2327): libfprint-elanspi-DEBUG: 16:48:25.326: stddev=661673d, ip=0, is_fp=2, is_empty=0 188s (process:2327): libfprint-SSM-DEBUG: 16:48:25.326: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 5 188s (process:2327): libfprint-SSM-DEBUG: 16:48:25.326: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 188s (process:2327): libfprint-SSM-DEBUG: 16:48:25.378: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 188s (process:2327): libfprint-SSM-DEBUG: 16:48:25.378: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 6 188s (process:2327): libfprint-elanspi-DEBUG: 16:48:25.378: stddev=764706d, ip=0, is_fp=2, is_empty=0 188s (process:2327): libfprint-SSM-DEBUG: 16:48:25.378: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 5 188s (process:2327): libfprint-SSM-DEBUG: 16:48:25.378: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 188s (process:2327): libfprint-SSM-DEBUG: 16:48:25.425: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 188s (process:2327): libfprint-SSM-DEBUG: 16:48:25.425: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 6 188s (process:2327): libfprint-elanspi-DEBUG: 16:48:25.425: stddev=806415d, ip=0, is_fp=2, is_empty=0 188s (process:2327): libfprint-SSM-DEBUG: 16:48:25.425: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 5 188s (process:2327): libfprint-SSM-DEBUG: 16:48:25.425: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 188s (process:2327): libfprint-SSM-DEBUG: 16:48:25.468: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 188s (process:2327): libfprint-SSM-DEBUG: 16:48:25.468: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 6 188s (process:2327): libfprint-elanspi-DEBUG: 16:48:25.469: stddev=806649d, ip=0, is_fp=2, is_empty=0 188s (process:2327): libfprint-SSM-DEBUG: 16:48:25.469: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 5 188s (process:2327): libfprint-SSM-DEBUG: 16:48:25.469: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 188s (process:2327): libfprint-SSM-DEBUG: 16:48:25.513: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 188s (process:2327): libfprint-SSM-DEBUG: 16:48:25.513: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 6 188s (process:2327): libfprint-elanspi-DEBUG: 16:48:25.513: stddev=822567d, ip=0, is_fp=2, is_empty=0 188s (process:2327): libfprint-SSM-DEBUG: 16:48:25.513: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 5 188s (process:2327): libfprint-SSM-DEBUG: 16:48:25.513: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 188s (process:2327): libfprint-SSM-DEBUG: 16:48:25.556: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 188s (process:2327): libfprint-SSM-DEBUG: 16:48:25.556: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 6 188s (process:2327): libfprint-elanspi-DEBUG: 16:48:25.556: stddev=1017068d, ip=0, is_fp=2, is_empty=0 188s (process:2327): libfprint-SSM-DEBUG: 16:48:25.556: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 5 188s (process:2327): libfprint-SSM-DEBUG: 16:48:25.556: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 188s (process:2327): libfprint-SSM-DEBUG: 16:48:25.599: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 188s (process:2327): libfprint-SSM-DEBUG: 16:48:25.600: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 6 188s (process:2327): libfprint-elanspi-DEBUG: 16:48:25.600: stddev=1004196d, ip=0, is_fp=2, is_empty=0 188s (process:2327): libfprint-SSM-DEBUG: 16:48:25.600: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 5 188s (process:2327): libfprint-SSM-DEBUG: 16:48:25.600: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 188s (process:2327): libfprint-SSM-DEBUG: 16:48:25.643: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 188s (process:2327): libfprint-SSM-DEBUG: 16:48:25.643: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 6 188s (process:2327): libfprint-elanspi-DEBUG: 16:48:25.643: stddev=963655d, ip=0, is_fp=2, is_empty=0 188s (process:2327): libfprint-SSM-DEBUG: 16:48:25.643: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 5 188s (process:2327): libfprint-SSM-DEBUG: 16:48:25.643: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 188s (process:2327): libfprint-SSM-DEBUG: 16:48:25.779: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 188s (process:2327): libfprint-SSM-DEBUG: 16:48:25.779: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 6 188s (process:2327): libfprint-elanspi-DEBUG: 16:48:25.779: stddev=880521d, ip=0, is_fp=2, is_empty=0 188s (process:2327): libfprint-SSM-DEBUG: 16:48:25.779: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 5 188s (process:2327): libfprint-SSM-DEBUG: 16:48:25.779: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 188s (process:2327): libfprint-SSM-DEBUG: 16:48:25.828: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 188s (process:2327): libfprint-SSM-DEBUG: 16:48:25.828: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 6 188s (process:2327): libfprint-elanspi-DEBUG: 16:48:25.829: stddev=1135372d, ip=0, is_fp=2, is_empty=0 188s (process:2327): libfprint-SSM-DEBUG: 16:48:25.829: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 5 188s (process:2327): libfprint-SSM-DEBUG: 16:48:25.829: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 188s (process:2327): libfprint-SSM-DEBUG: 16:48:25.874: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 188s (process:2327): libfprint-SSM-DEBUG: 16:48:25.874: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 6 188s (process:2327): libfprint-elanspi-DEBUG: 16:48:25.874: stddev=1093450d, ip=3, is_fp=1, is_empty=0 188s (process:2327): libfprint-SSM-DEBUG: 16:48:25.874: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 5 188s (process:2327): libfprint-SSM-DEBUG: 16:48:25.874: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 188s (process:2327): libfprint-SSM-DEBUG: 16:48:25.918: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 188s (process:2327): libfprint-SSM-DEBUG: 16:48:25.918: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 6 188s (process:2327): libfprint-elanspi-DEBUG: 16:48:25.918: stddev=41090d, ip=8, is_fp=0, is_empty=2 188s (process:2327): libfprint-SSM-DEBUG: 16:48:25.918: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 5 188s (process:2327): libfprint-SSM-DEBUG: 16:48:25.918: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 189s (process:2327): libfprint-SSM-DEBUG: 16:48:25.964: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 189s (process:2327): libfprint-SSM-DEBUG: 16:48:25.964: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 6 189s (process:2327): libfprint-elanspi-DEBUG: 16:48:25.964: stddev=6836d, ip=13, is_fp=0, is_empty=2 189s (process:2327): libfprint-device-DEBUG: 16:48:25.964: Device reported finger status change: FP_FINGER_STATUS_NONE 189s (process:2327): libfprint-image_device-DEBUG: 16:48:25.964: Image device reported finger status: off 189s (process:2327): libfprint-image_device-DEBUG: 16:48:25.964: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 189s (process:2327): libfprint-image_device-DEBUG: 16:48:25.964: Deactivating image device 189s (process:2327): libfprint-image_device-DEBUG: 16:48:25.964: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_DEACTIVATING 189s (process:2327): libfprint-image_device-DEBUG: 16:48:25.964: Image device deactivation completed 189s (process:2327): libfprint-image_device-DEBUG: 16:48:25.964: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE 189s (process:2327): libfprint-device-DEBUG: 16:48:25.969: Device reported capture completion 189s (process:2327): libfprint-SSM-DEBUG: 16:48:25.969: [elanspi] ELANSPI_FPCAPT_NSTATES completed successfully 189s (process:2327): libfprint-device-DEBUG: 16:48:25.969: Completing action FPI_DEVICE_ACTION_CAPTURE in idle! 189s (process:2327): libfprint-device-DEBUG: 16:48:25.969: Updated temperature model after 4.22 seconds, ratio 0.27 -> 0.29, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 189s (process:2327): libfprint-image_device-DEBUG: 16:48:25.984: Image device close completed 189s (process:2327): libfprint-device-DEBUG: 16:48:25.984: Device reported close completion 189s (process:2327): libfprint-device-DEBUG: 16:48:25.984: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 189s (process:2327): libfprint-device-DEBUG: 16:48:25.984: Updated temperature model after 0.01 seconds, ratio 0.29 -> 0.29, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 189s ** (umockdev-run:2323): DEBUG: 16:48:26.323: umockdev.vala:150: Removing test bed /tmp/umockdev.6YE2J2 189s (umockdev-run:2323): GLib-DEBUG: 16:48:26.333: unsetenv() is not thread-safe and should not be used after threads are created 189s Comparing PNGs /tmp/libfprint-umockdev-test-j72rjjsr/capture.png and /usr/share/installed-tests/libfprint-2/elanspi/capture.png 189s PASS: libfprint-2/driver-elanspi.test 189s Running test: libfprint-2/driver-realtek.test 189s ** (umockdev-run:2338): DEBUG: 16:48:26.584: umockdev.vala:123: Created udev test bed /tmp/umockdev.LDX1J2 189s ** (umockdev-run:2338): DEBUG: 16:48:26.584: umockdev.vala:1297: parsing device description for /devices/pci0000:00/0000:00:14.0/usb1/1-4 189s ** (umockdev-run:2338): DEBUG: 16:48:26.585: umockdev.vala:1366: creating device /devices/pci0000:00/0000:00:14.0/usb1/1-4 (subsystem usb) 189s ** (umockdev-run:2338): DEBUG: 16:48:26.588: umockdev.vala:1411: create_node_for_device: creating file device /tmp/umockdev.LDX1J2/dev/bus/usb/001/005 189s ** (umockdev-run:2338): DEBUG: 16:48:26.588: umockdev.vala:1297: parsing device description for /devices/pci0000:00/0000:00:14.0/usb1 189s ** (umockdev-run:2338): DEBUG: 16:48:26.589: umockdev.vala:1366: creating device /devices/pci0000:00/0000:00:14.0/usb1 (subsystem usb) 189s ** (umockdev-run:2338): DEBUG: 16:48:26.591: umockdev.vala:1411: create_node_for_device: creating file device /tmp/umockdev.LDX1J2/dev/bus/usb/001/001 189s ** (umockdev-run:2338): DEBUG: 16:48:26.592: umockdev.vala:1297: parsing device description for /devices/pci0000:00/0000:00:14.0 189s ** (umockdev-run:2338): DEBUG: 16:48:26.592: umockdev.vala:1366: creating device /devices/pci0000:00/0000:00:14.0 (subsystem pci) 189s (process:2342): libfprint-context-DEBUG: 16:48:26.659: Initializing FpContext (libfprint version 1.94.7+tod1) 189s (process:2342): libfprint-tod-DEBUG: 16:48:26.659: Impossible to load the shared drivers dir Error opening directory “/usr/lib/aarch64-linux-gnu/libfprint-2/tod-1”: No such file or directory 189s (process:2342): libfprint-context-DEBUG: 16:48:26.661: No driver found for USB device 1D6B:0002 189s (process:2342): libfprint-realtek-DEBUG: 16:48:26.662: 77662810: ../libfprint/drivers/realtek/realtek.c:1059 189s (process:2342): libfprint-realtek-DEBUG: 16:48:26.664: Device name: Realtek USB2.0 Finger Print Bridge 189s (process:2342): libfprint-device-DEBUG: 16:48:26.664: Device reported probe completion 189s (process:2342): libfprint-device-DEBUG: 16:48:26.664: Completing action FPI_DEVICE_ACTION_PROBE in idle! 189s (process:2342): libfprint-device-DEBUG: 16:48:26.664: Not updating temperature model, device can run continuously! 189s (process:2342): libfprint-realtek-DEBUG: 16:48:26.665: 77666286: ../libfprint/drivers/realtek/realtek.c:1104 189s (process:2342): libfprint-SSM-DEBUG: 16:48:26.665: [realtek] Init entering state 0 189s (process:2342): libfprint-SSM-DEBUG: 16:48:26.665: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 189s (process:2342): libfprint-SSM-DEBUG: 16:48:26.666: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 189s (process:2342): libfprint-SSM-DEBUG: 16:48:26.666: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 189s (process:2342): libfprint-SSM-DEBUG: 16:48:26.666: [realtek] Init entering state 1 189s (process:2342): libfprint-SSM-DEBUG: 16:48:26.666: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 189s (process:2342): libfprint-SSM-DEBUG: 16:48:26.667: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 189s (process:2342): libfprint-SSM-DEBUG: 16:48:26.667: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 189s (process:2342): libfprint-SSM-DEBUG: 16:48:26.667: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 189s (process:2342): libfprint-SSM-DEBUG: 16:48:26.668: [realtek] Init completed successfully 189s (process:2342): libfprint-realtek-DEBUG: 16:48:26.668: Init complete! 189s (process:2342): libfprint-device-DEBUG: 16:48:26.668: Device reported open completion 189s (process:2342): libfprint-SSM-DEBUG: 16:48:26.668: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 189s (process:2342): libfprint-device-DEBUG: 16:48:26.668: Completing action FPI_DEVICE_ACTION_OPEN in idle! 189s (process:2342): libfprint-device-DEBUG: 16:48:26.668: Not updating temperature model, device can run continuously! 189s (process:2342): libfprint-realtek-DEBUG: 16:48:26.668: 77669036: ../libfprint/drivers/realtek/realtek.c:1167 189s (process:2342): libfprint-SSM-DEBUG: 16:48:26.668: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 189s (process:2342): libfprint-SSM-DEBUG: 16:48:26.668: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 189s (process:2342): libfprint-SSM-DEBUG: 16:48:26.668: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 189s (process:2342): libfprint-realtek-DEBUG: 16:48:26.669: Successfully cleared storage 189s (process:2342): libfprint-device-DEBUG: 16:48:26.669: Device reported deletion completion 189s (process:2342): libfprint-SSM-DEBUG: 16:48:26.669: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 189s (process:2342): libfprint-device-DEBUG: 16:48:26.669: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 189s (process:2342): libfprint-device-DEBUG: 16:48:26.669: Not updating temperature model, device can run continuously! 189s (process:2342): libfprint-device-DEBUG: 16:48:26.675: Not updating temperature model, device can run continuously! 189s (process:2342): libfprint-realtek-DEBUG: 16:48:26.675: 77676137: ../libfprint/drivers/realtek/realtek.c:1036 189s (process:2342): libfprint-SSM-DEBUG: 16:48:26.675: [realtek] Enroll entering state 0 189s (process:2342): libfprint-SSM-DEBUG: 16:48:26.675: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 189s (process:2342): libfprint-SSM-DEBUG: 16:48:26.675: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 189s (process:2342): libfprint-SSM-DEBUG: 16:48:26.676: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 189s (process:2342): libfprint-SSM-DEBUG: 16:48:26.676: [realtek] Enroll entering state 1 189s (process:2342): libfprint-SSM-DEBUG: 16:48:26.676: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 189s (process:2342): libfprint-SSM-DEBUG: 16:48:26.677: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 189s (process:2342): libfprint-SSM-DEBUG: 16:48:26.677: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 189s (process:2342): libfprint-SSM-DEBUG: 16:48:26.677: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 189s (process:2342): libfprint-SSM-DEBUG: 16:48:26.677: [realtek] Enroll entering state 2 189s (process:2342): libfprint-device-DEBUG: 16:48:26.677: Device reported finger status change: FP_FINGER_STATUS_NEEDED 189s (process:2342): libfprint-SSM-DEBUG: 16:48:26.678: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 189s (process:2342): libfprint-SSM-DEBUG: 16:48:26.678: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 189s (process:2342): libfprint-SSM-DEBUG: 16:48:26.678: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 189s (process:2342): libfprint-SSM-DEBUG: 16:48:26.678: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 189s (process:2342): libfprint-SSM-DEBUG: 16:48:26.678: [realtek] Enroll entering state 3 189s (process:2342): libfprint-SSM-DEBUG: 16:48:26.678: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 189s (process:2342): libfprint-SSM-DEBUG: 16:48:26.679: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 189s (process:2342): libfprint-SSM-DEBUG: 16:48:26.679: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 189s (process:2342): libfprint-SSM-DEBUG: 16:48:26.679: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 189s (process:2342): libfprint-device-DEBUG: 16:48:26.680: Device reported finger status change: FP_FINGER_STATUS_PRESENT 189s (process:2342): libfprint-SSM-DEBUG: 16:48:26.680: [realtek] Enroll entering state 4 189s (process:2342): libfprint-SSM-DEBUG: 16:48:26.680: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 189s (process:2342): libfprint-SSM-DEBUG: 16:48:26.680: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 189s (process:2342): libfprint-SSM-DEBUG: 16:48:26.680: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 189s (process:2342): libfprint-SSM-DEBUG: 16:48:26.681: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 189s (process:2342): libfprint-device-DEBUG: 16:48:26.681: Device reported finger status change: FP_FINGER_STATUS_NONE 189s (process:2342): libfprint-device-DEBUG: 16:48:26.681: Device reported enroll progress, reported 1 of 8 have been completed 189s (process:2342): libfprint-SSM-DEBUG: 16:48:26.687: [realtek] Enroll entering state 2 189s (process:2342): libfprint-device-DEBUG: 16:48:26.687: Device reported finger status change: FP_FINGER_STATUS_NEEDED 189s (process:2342): libfprint-SSM-DEBUG: 16:48:26.687: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 189s (process:2342): libfprint-SSM-DEBUG: 16:48:26.687: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 189s (process:2342): libfprint-SSM-DEBUG: 16:48:26.688: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 189s (process:2342): libfprint-SSM-DEBUG: 16:48:26.688: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 189s (process:2342): libfprint-SSM-DEBUG: 16:48:26.688: [realtek] Enroll entering state 3 189s (process:2342): libfprint-SSM-DEBUG: 16:48:26.688: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 189s (process:2342): libfprint-SSM-DEBUG: 16:48:26.688: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 189s (process:2342): libfprint-SSM-DEBUG: 16:48:26.689: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 189s (process:2342): libfprint-SSM-DEBUG: 16:48:26.689: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 189s (process:2342): libfprint-device-DEBUG: 16:48:26.689: Device reported finger status change: FP_FINGER_STATUS_PRESENT 189s (process:2342): libfprint-SSM-DEBUG: 16:48:26.689: [realtek] Enroll entering state 4 189s (process:2342): libfprint-SSM-DEBUG: 16:48:26.689: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 189s (process:2342): libfprint-SSM-DEBUG: 16:48:26.690: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 189s (process:2342): libfprint-SSM-DEBUG: 16:48:26.690: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 189s (process:2342): libfprint-SSM-DEBUG: 16:48:26.690: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 189s (process:2342): libfprint-device-DEBUG: 16:48:26.691: Device reported finger status change: FP_FINGER_STATUS_NONE 189s (process:2342): libfprint-device-DEBUG: 16:48:26.691: Device reported enroll progress, reported 2 of 8 have been completed 189s (process:2342): libfprint-SSM-DEBUG: 16:48:26.691: [realtek] Enroll entering state 2 189s (process:2342): libfprint-device-DEBUG: 16:48:26.691: Device reported finger status change: FP_FINGER_STATUS_NEEDED 189s (process:2342): libfprint-SSM-DEBUG: 16:48:26.691: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 189s (process:2342): libfprint-SSM-DEBUG: 16:48:26.691: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 189s (process:2342): libfprint-SSM-DEBUG: 16:48:26.691: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 189s (process:2342): libfprint-SSM-DEBUG: 16:48:26.691: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 189s (process:2342): libfprint-SSM-DEBUG: 16:48:26.692: [realtek] Enroll entering state 3 189s (process:2342): libfprint-SSM-DEBUG: 16:48:26.692: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 189s (process:2342): libfprint-SSM-DEBUG: 16:48:26.692: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 189s (process:2342): libfprint-SSM-DEBUG: 16:48:26.692: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 189s (process:2342): libfprint-SSM-DEBUG: 16:48:26.693: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 189s (process:2342): libfprint-device-DEBUG: 16:48:26.693: Device reported finger status change: FP_FINGER_STATUS_PRESENT 189s (process:2342): libfprint-SSM-DEBUG: 16:48:26.693: [realtek] Enroll entering state 4 189s (process:2342): libfprint-SSM-DEBUG: 16:48:26.693: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 189s (process:2342): libfprint-SSM-DEBUG: 16:48:26.693: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 189s (process:2342): libfprint-SSM-DEBUG: 16:48:26.693: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 189s (process:2342): libfprint-SSM-DEBUG: 16:48:26.694: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 189s (process:2342): libfprint-device-DEBUG: 16:48:26.694: Device reported finger status change: FP_FINGER_STATUS_NONE 189s (process:2342): libfprint-device-DEBUG: 16:48:26.694: Device reported enroll progress, reported 3 of 8 have been completed 189s (process:2342): libfprint-SSM-DEBUG: 16:48:26.694: [realtek] Enroll entering state 2 189s (process:2342): libfprint-device-DEBUG: 16:48:26.694: Device reported finger status change: FP_FINGER_STATUS_NEEDED 189s (process:2342): libfprint-SSM-DEBUG: 16:48:26.694: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 189s (process:2342): libfprint-SSM-DEBUG: 16:48:26.695: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 189s (process:2342): libfprint-SSM-DEBUG: 16:48:26.695: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 189s (process:2342): libfprint-SSM-DEBUG: 16:48:26.695: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 189s (process:2342): libfprint-SSM-DEBUG: 16:48:26.695: [realtek] Enroll entering state 3 189s (process:2342): libfprint-SSM-DEBUG: 16:48:26.695: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 189s (process:2342): libfprint-SSM-DEBUG: 16:48:26.696: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 189s (process:2342): libfprint-SSM-DEBUG: 16:48:26.696: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 189s (process:2342): libfprint-SSM-DEBUG: 16:48:26.696: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 189s (process:2342): libfprint-device-DEBUG: 16:48:26.697: Device reported finger status change: FP_FINGER_STATUS_PRESENT 189s (process:2342): libfprint-SSM-DEBUG: 16:48:26.697: [realtek] Enroll entering state 4 189s (process:2342): libfprint-SSM-DEBUG: 16:48:26.697: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 189s (process:2342): libfprint-SSM-DEBUG: 16:48:26.697: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 189s (process:2342): libfprint-SSM-DEBUG: 16:48:26.697: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 189s (process:2342): libfprint-SSM-DEBUG: 16:48:26.697: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 189s (process:2342): libfprint-device-DEBUG: 16:48:26.698: Device reported finger status change: FP_FINGER_STATUS_NONE 189s (process:2342): libfprint-device-DEBUG: 16:48:26.698: Device reported enroll progress, reported 4 of 8 have been completed 189s (process:2342): libfprint-SSM-DEBUG: 16:48:26.698: [realtek] Enroll entering state 2 189s (process:2342): libfprint-device-DEBUG: 16:48:26.698: Device reported finger status change: FP_FINGER_STATUS_NEEDED 189s (process:2342): libfprint-SSM-DEBUG: 16:48:26.698: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 189s (process:2342): libfprint-SSM-DEBUG: 16:48:26.698: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 189s (process:2342): libfprint-SSM-DEBUG: 16:48:26.698: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 189s (process:2342): libfprint-SSM-DEBUG: 16:48:26.698: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 189s (process:2342): libfprint-SSM-DEBUG: 16:48:26.699: [realtek] Enroll entering state 3 189s (process:2342): libfprint-SSM-DEBUG: 16:48:26.699: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 189s (process:2342): libfprint-SSM-DEBUG: 16:48:26.699: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 189s (process:2342): libfprint-SSM-DEBUG: 16:48:26.699: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 189s (process:2342): libfprint-SSM-DEBUG: 16:48:26.700: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 189s (process:2342): libfprint-device-DEBUG: 16:48:26.700: Device reported finger status change: FP_FINGER_STATUS_PRESENT 189s (process:2342): libfprint-SSM-DEBUG: 16:48:26.700: [realtek] Enroll entering state 4 189s (process:2342): libfprint-SSM-DEBUG: 16:48:26.700: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 189s (process:2342): libfprint-SSM-DEBUG: 16:48:26.700: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 189s (process:2342): libfprint-SSM-DEBUG: 16:48:26.700: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 189s (process:2342): libfprint-SSM-DEBUG: 16:48:26.701: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 189s (process:2342): libfprint-device-DEBUG: 16:48:26.701: Device reported finger status change: FP_FINGER_STATUS_NONE 189s (process:2342): libfprint-device-DEBUG: 16:48:26.701: Device reported enroll progress, reported 5 of 8 have been completed 189s (process:2342): libfprint-SSM-DEBUG: 16:48:26.701: [realtek] Enroll entering state 2 189s (process:2342): libfprint-device-DEBUG: 16:48:26.701: Device reported finger status change: FP_FINGER_STATUS_NEEDED 189s (process:2342): libfprint-SSM-DEBUG: 16:48:26.701: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 189s (process:2342): libfprint-SSM-DEBUG: 16:48:26.702: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 189s (process:2342): libfprint-SSM-DEBUG: 16:48:26.702: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 189s (process:2342): libfprint-SSM-DEBUG: 16:48:26.702: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 189s (process:2342): libfprint-SSM-DEBUG: 16:48:26.702: [realtek] Enroll entering state 3 189s (process:2342): libfprint-SSM-DEBUG: 16:48:26.702: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 189s (process:2342): libfprint-SSM-DEBUG: 16:48:26.702: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 189s (process:2342): libfprint-SSM-DEBUG: 16:48:26.703: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 189s (process:2342): libfprint-SSM-DEBUG: 16:48:26.703: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 189s (process:2342): libfprint-device-DEBUG: 16:48:26.703: Device reported finger status change: FP_FINGER_STATUS_PRESENT 189s (process:2342): libfprint-SSM-DEBUG: 16:48:26.703: [realtek] Enroll entering state 4 189s (process:2342): libfprint-SSM-DEBUG: 16:48:26.703: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 189s (process:2342): libfprint-SSM-DEBUG: 16:48:26.704: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 189s (process:2342): libfprint-SSM-DEBUG: 16:48:26.704: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 189s (process:2342): libfprint-SSM-DEBUG: 16:48:26.704: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 189s (process:2342): libfprint-device-DEBUG: 16:48:26.705: Device reported finger status change: FP_FINGER_STATUS_NONE 189s (process:2342): libfprint-device-DEBUG: 16:48:26.705: Device reported enroll progress, reported 6 of 8 have been completed 189s (process:2342): libfprint-SSM-DEBUG: 16:48:26.705: [realtek] Enroll entering state 2 189s (process:2342): libfprint-device-DEBUG: 16:48:26.705: Device reported finger status change: FP_FINGER_STATUS_NEEDED 189s (process:2342): libfprint-SSM-DEBUG: 16:48:26.705: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 189s (process:2342): libfprint-SSM-DEBUG: 16:48:26.705: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 189s (process:2342): libfprint-SSM-DEBUG: 16:48:26.705: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 189s (process:2342): libfprint-SSM-DEBUG: 16:48:26.705: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 189s (process:2342): libfprint-SSM-DEBUG: 16:48:26.706: [realtek] Enroll entering state 3 189s (process:2342): libfprint-SSM-DEBUG: 16:48:26.706: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 189s (process:2342): libfprint-SSM-DEBUG: 16:48:26.706: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 189s (process:2342): libfprint-SSM-DEBUG: 16:48:26.706: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 189s (process:2342): libfprint-SSM-DEBUG: 16:48:26.707: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 189s (process:2342): libfprint-device-DEBUG: 16:48:26.707: Device reported finger status change: FP_FINGER_STATUS_PRESENT 189s (process:2342): libfprint-SSM-DEBUG: 16:48:26.707: [realtek] Enroll entering state 4 189s (process:2342): libfprint-SSM-DEBUG: 16:48:26.707: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 189s (process:2342): libfprint-SSM-DEBUG: 16:48:26.707: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 189s (process:2342): libfprint-SSM-DEBUG: 16:48:26.707: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 189s (process:2342): libfprint-SSM-DEBUG: 16:48:26.708: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 189s (process:2342): libfprint-device-DEBUG: 16:48:26.708: Device reported finger status change: FP_FINGER_STATUS_NONE 189s (process:2342): libfprint-device-DEBUG: 16:48:26.708: Device reported enroll progress, reported 7 of 8 have been completed 189s (process:2342): libfprint-SSM-DEBUG: 16:48:26.708: [realtek] Enroll entering state 2 189s (process:2342): libfprint-device-DEBUG: 16:48:26.708: Device reported finger status change: FP_FINGER_STATUS_NEEDED 189s (process:2342): libfprint-SSM-DEBUG: 16:48:26.708: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 189s (process:2342): libfprint-SSM-DEBUG: 16:48:26.709: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 189s (process:2342): libfprint-SSM-DEBUG: 16:48:26.709: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 189s (process:2342): libfprint-SSM-DEBUG: 16:48:26.709: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 189s (process:2342): libfprint-SSM-DEBUG: 16:48:26.709: [realtek] Enroll entering state 3 189s (process:2342): libfprint-SSM-DEBUG: 16:48:26.709: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 189s (process:2342): libfprint-SSM-DEBUG: 16:48:26.710: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 189s (process:2342): libfprint-SSM-DEBUG: 16:48:26.710: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 189s (process:2342): libfprint-SSM-DEBUG: 16:48:26.710: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 189s (process:2342): libfprint-device-DEBUG: 16:48:26.711: Device reported finger status change: FP_FINGER_STATUS_PRESENT 189s (process:2342): libfprint-SSM-DEBUG: 16:48:26.711: [realtek] Enroll entering state 4 189s (process:2342): libfprint-SSM-DEBUG: 16:48:26.711: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 189s (process:2342): libfprint-SSM-DEBUG: 16:48:26.711: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 189s (process:2342): libfprint-SSM-DEBUG: 16:48:26.711: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 189s (process:2342): libfprint-SSM-DEBUG: 16:48:26.711: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 189s (process:2342): libfprint-device-DEBUG: 16:48:26.712: Device reported finger status change: FP_FINGER_STATUS_NONE 189s (process:2342): libfprint-device-DEBUG: 16:48:26.712: Device reported enroll progress, reported 8 of 8 have been completed 189s (process:2342): libfprint-SSM-DEBUG: 16:48:26.712: [realtek] Enroll entering state 2 189s (process:2342): libfprint-device-DEBUG: 16:48:26.712: Device reported finger status change: FP_FINGER_STATUS_NEEDED 189s (process:2342): libfprint-SSM-DEBUG: 16:48:26.712: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 189s (process:2342): libfprint-SSM-DEBUG: 16:48:26.712: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 189s (process:2342): libfprint-SSM-DEBUG: 16:48:26.712: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 189s (process:2342): libfprint-SSM-DEBUG: 16:48:26.712: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 189s (process:2342): libfprint-SSM-DEBUG: 16:48:26.713: [realtek] Enroll entering state 3 189s (process:2342): libfprint-SSM-DEBUG: 16:48:26.713: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 189s (process:2342): libfprint-SSM-DEBUG: 16:48:26.713: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 189s (process:2342): libfprint-SSM-DEBUG: 16:48:26.713: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 189s (process:2342): libfprint-SSM-DEBUG: 16:48:26.714: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 189s (process:2342): libfprint-device-DEBUG: 16:48:26.714: Device reported finger status change: FP_FINGER_STATUS_PRESENT 189s (process:2342): libfprint-SSM-DEBUG: 16:48:26.714: [realtek] Enroll entering state 4 189s (process:2342): libfprint-SSM-DEBUG: 16:48:26.714: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 189s (process:2342): libfprint-SSM-DEBUG: 16:48:26.714: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 189s (process:2342): libfprint-SSM-DEBUG: 16:48:26.715: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 189s (process:2342): libfprint-SSM-DEBUG: 16:48:26.715: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 189s (process:2342): libfprint-device-DEBUG: 16:48:26.715: Device reported finger status change: FP_FINGER_STATUS_NONE 189s (process:2342): libfprint-SSM-DEBUG: 16:48:26.716: [realtek] Enroll entering state 5 189s (process:2342): libfprint-SSM-DEBUG: 16:48:26.716: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 189s (process:2342): libfprint-SSM-DEBUG: 16:48:26.716: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 189s (process:2342): libfprint-SSM-DEBUG: 16:48:26.716: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 189s (process:2342): libfprint-SSM-DEBUG: 16:48:26.716: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 189s (process:2342): libfprint-SSM-DEBUG: 16:48:26.717: [realtek] Enroll entering state 6 189s (process:2342): libfprint-realtek-DEBUG: 16:48:26.717: user_id: FP1-00000000-0-00000000-nobody, finger: 0xff 189s (process:2342): libfprint-SSM-DEBUG: 16:48:26.717: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 189s (process:2342): libfprint-SSM-DEBUG: 16:48:26.717: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 189s (process:2342): libfprint-SSM-DEBUG: 16:48:26.717: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 189s (process:2342): libfprint-SSM-DEBUG: 16:48:26.718: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 189s (process:2342): libfprint-SSM-DEBUG: 16:48:26.718: [realtek] Enroll completed successfully 189s (process:2342): libfprint-realtek-DEBUG: 16:48:26.718: Enrollment complete! 189s (process:2342): libfprint-device-DEBUG: 16:48:26.718: Device reported enroll completion 189s (process:2342): libfprint-device-DEBUG: 16:48:26.718: Print for finger FP_FINGER_UNKNOWN enrolled 189s (process:2342): libfprint-SSM-DEBUG: 16:48:26.718: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 189s (process:2342): libfprint-device-DEBUG: 16:48:26.718: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 189s (process:2342): libfprint-device-DEBUG: 16:48:26.718: Not updating temperature model, device can run continuously! 189s (process:2342): libfprint-realtek-DEBUG: 16:48:26.718: 77719511: ../libfprint/drivers/realtek/realtek.c:1179 189s (process:2342): libfprint-SSM-DEBUG: 16:48:26.718: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 189s (process:2342): libfprint-SSM-DEBUG: 16:48:26.719: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 189s (process:2342): libfprint-SSM-DEBUG: 16:48:26.719: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 189s (process:2342): libfprint-realtek-DEBUG: 16:48:26.720: Query templates complete! 189s (process:2342): libfprint-device-DEBUG: 16:48:26.720: Device reported listing completion 189s (process:2342): libfprint-SSM-DEBUG: 16:48:26.720: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 189s (process:2342): libfprint-device-DEBUG: 16:48:26.720: Completing action FPI_DEVICE_ACTION_LIST in idle! 189s (process:2342): libfprint-device-DEBUG: 16:48:26.720: Not updating temperature model, device can run continuously! 189s (process:2342): libfprint-device-DEBUG: 16:48:26.720: Not updating temperature model, device can run continuously! 189s (process:2342): libfprint-realtek-DEBUG: 16:48:26.720: 77721214: ../libfprint/drivers/realtek/realtek.c:1009 189s (process:2342): libfprint-SSM-DEBUG: 16:48:26.720: [realtek] Verify & Identify entering state 0 189s (process:2342): libfprint-device-DEBUG: 16:48:26.720: Device reported finger status change: FP_FINGER_STATUS_NEEDED 189s (process:2342): libfprint-SSM-DEBUG: 16:48:26.720: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 189s (process:2342): libfprint-SSM-DEBUG: 16:48:26.720: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 189s (process:2342): libfprint-SSM-DEBUG: 16:48:26.721: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 189s (process:2342): libfprint-SSM-DEBUG: 16:48:26.721: [realtek] Verify & Identify entering state 1 189s (process:2342): libfprint-SSM-DEBUG: 16:48:26.721: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 189s (process:2342): libfprint-SSM-DEBUG: 16:48:26.721: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 189s (process:2342): libfprint-SSM-DEBUG: 16:48:26.722: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 189s (process:2342): libfprint-SSM-DEBUG: 16:48:26.722: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 189s (process:2342): libfprint-device-DEBUG: 16:48:26.722: Device reported finger status change: FP_FINGER_STATUS_PRESENT 189s (process:2342): libfprint-SSM-DEBUG: 16:48:26.722: [realtek] Verify & Identify entering state 2 189s (process:2342): libfprint-SSM-DEBUG: 16:48:26.723: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 189s (process:2342): libfprint-SSM-DEBUG: 16:48:26.723: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 189s (process:2342): libfprint-SSM-DEBUG: 16:48:26.723: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 189s (process:2342): libfprint-SSM-DEBUG: 16:48:26.723: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 189s (process:2342): libfprint-device-DEBUG: 16:48:26.724: Device reported finger status change: FP_FINGER_STATUS_NONE 189s (process:2342): libfprint-SSM-DEBUG: 16:48:26.724: [realtek] Verify & Identify entering state 3 189s (process:2342): libfprint-SSM-DEBUG: 16:48:26.724: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 189s (process:2342): libfprint-SSM-DEBUG: 16:48:26.724: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 189s (process:2342): libfprint-SSM-DEBUG: 16:48:26.724: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 189s (process:2342): libfprint-SSM-DEBUG: 16:48:26.725: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 189s (process:2342): libfprint-device-DEBUG: 16:48:26.726: Device reported verify result 189s (process:2342): libfprint-SSM-DEBUG: 16:48:26.726: [realtek] Verify & Identify entering state 4 189s (process:2342): libfprint-SSM-DEBUG: 16:48:26.726: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 189s (process:2342): libfprint-SSM-DEBUG: 16:48:26.726: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 189s (process:2342): libfprint-SSM-DEBUG: 16:48:26.726: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 189s (process:2342): libfprint-SSM-DEBUG: 16:48:26.726: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 189s (process:2342): libfprint-SSM-DEBUG: 16:48:26.727: [realtek] Verify & Identify completed successfully 189s (process:2342): libfprint-realtek-DEBUG: 16:48:26.727: Verify complete! 189s (process:2342): libfprint-device-DEBUG: 16:48:26.727: Device reported verify completion 189s (process:2342): libfprint-SSM-DEBUG: 16:48:26.727: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 189s (process:2342): libfprint-device-DEBUG: 16:48:26.727: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 189s (process:2342): libfprint-device-DEBUG: 16:48:26.727: Not updating temperature model, device can run continuously! 189s (process:2342): libfprint-device-DEBUG: 16:48:26.727: Not updating temperature model, device can run continuously! 189s (process:2342): libfprint-realtek-DEBUG: 16:48:26.727: 77728310: ../libfprint/drivers/realtek/realtek.c:1009 189s (process:2342): libfprint-SSM-DEBUG: 16:48:26.727: [realtek] Verify & Identify entering state 0 189s (process:2342): libfprint-device-DEBUG: 16:48:26.727: Device reported finger status change: FP_FINGER_STATUS_NEEDED 189s (process:2342): libfprint-SSM-DEBUG: 16:48:26.727: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 189s (process:2342): libfprint-SSM-DEBUG: 16:48:26.728: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 189s (process:2342): libfprint-SSM-DEBUG: 16:48:26.728: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 189s (process:2342): libfprint-SSM-DEBUG: 16:48:26.728: [realtek] Verify & Identify entering state 1 189s (process:2342): libfprint-SSM-DEBUG: 16:48:26.728: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 189s (process:2342): libfprint-SSM-DEBUG: 16:48:26.728: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 189s (process:2342): libfprint-SSM-DEBUG: 16:48:26.729: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 189s (process:2342): libfprint-SSM-DEBUG: 16:48:26.729: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 189s (process:2342): libfprint-device-DEBUG: 16:48:26.730: Device reported finger status change: FP_FINGER_STATUS_PRESENT 189s (process:2342): libfprint-SSM-DEBUG: 16:48:26.730: [realtek] Verify & Identify entering state 2 189s (process:2342): libfprint-SSM-DEBUG: 16:48:26.730: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 189s (process:2342): libfprint-SSM-DEBUG: 16:48:26.730: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 189s (process:2342): libfprint-SSM-DEBUG: 16:48:26.730: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 189s (process:2342): libfprint-SSM-DEBUG: 16:48:26.730: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 189s (process:2342): libfprint-device-DEBUG: 16:48:26.731: Device reported finger status change: FP_FINGER_STATUS_NONE 189s (process:2342): libfprint-SSM-DEBUG: 16:48:26.731: [realtek] Verify & Identify entering state 3 189s (process:2342): libfprint-SSM-DEBUG: 16:48:26.731: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 189s (process:2342): libfprint-SSM-DEBUG: 16:48:26.731: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 189s (process:2342): libfprint-SSM-DEBUG: 16:48:26.731: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 189s (process:2342): libfprint-SSM-DEBUG: 16:48:26.732: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 189s (process:2342): libfprint-device-DEBUG: 16:48:26.732: Device reported identify result 189s (process:2342): libfprint-SSM-DEBUG: 16:48:26.732: [realtek] Verify & Identify completed successfully 189s (process:2342): libfprint-realtek-DEBUG: 16:48:26.732: Verify complete! 189s (process:2342): libfprint-device-DEBUG: 16:48:26.732: Device reported identify completion 189s (process:2342): libfprint-SSM-DEBUG: 16:48:26.732: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 189s (process:2342): libfprint-device-DEBUG: 16:48:26.733: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 189s (process:2342): libfprint-device-DEBUG: 16:48:26.733: Not updating temperature model, device can run continuously! 189s (process:2342): libfprint-realtek-DEBUG: 16:48:26.733: 77734118: ../libfprint/drivers/realtek/realtek.c:1148 189s (process:2342): libfprint-SSM-DEBUG: 16:48:26.733: [realtek] Delete print entering state 0 189s (process:2342): libfprint-SSM-DEBUG: 16:48:26.733: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 189s (process:2342): libfprint-SSM-DEBUG: 16:48:26.733: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 189s (process:2342): libfprint-SSM-DEBUG: 16:48:26.734: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 189s (process:2342): libfprint-SSM-DEBUG: 16:48:26.734: [realtek] Delete print entering state 1 189s (process:2342): libfprint-SSM-DEBUG: 16:48:26.734: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 189s (process:2342): libfprint-SSM-DEBUG: 16:48:26.735: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 189s (process:2342): libfprint-SSM-DEBUG: 16:48:26.735: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 189s (process:2342): libfprint-SSM-DEBUG: 16:48:26.735: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 189s (process:2342): libfprint-SSM-DEBUG: 16:48:26.735: [realtek] Delete print completed successfully 189s (process:2342): libfprint-realtek-DEBUG: 16:48:26.735: Delete print complete! 189s (process:2342): libfprint-device-DEBUG: 16:48:26.736: Device reported deletion completion 189s (process:2342): libfprint-SSM-DEBUG: 16:48:26.736: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 189s (process:2342): libfprint-device-DEBUG: 16:48:26.736: Completing action FPI_DEVICE_ACTION_DELETE in idle! 189s (process:2342): libfprint-device-DEBUG: 16:48:26.736: Not updating temperature model, device can run continuously! 189s (process:2342): libfprint-realtek-DEBUG: 16:48:26.736: 77736811: ../libfprint/drivers/realtek/realtek.c:1136 189s (process:2342): libfprint-device-DEBUG: 16:48:26.736: Device reported close completion 189s (process:2342): libfprint-device-DEBUG: 16:48:26.736: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 189s (process:2342): libfprint-device-DEBUG: 16:48:26.736: Not updating temperature model, device can run continuously! 189s enrolling 189s enroll progress: (<__gi__.FpiDeviceRealtek object at 0xe4bb892b38c0 (FpiDeviceRealtek at 0x3718e320)>, 1, None, None, None) 189s enroll progress: (<__gi__.FpiDeviceRealtek object at 0xe4bb892b38c0 (FpiDeviceRealtek at 0x3718e320)>, 2, None, None, None) 189s enroll progress: (<__gi__.FpiDeviceRealtek object at 0xe4bb892b38c0 (FpiDeviceRealtek at 0x3718e320)>, 3, None, None, None) 189s enroll progress: (<__gi__.FpiDeviceRealtek object at 0xe4bb892b38c0 (FpiDeviceRealtek at 0x3718e320)>, 4, None, None, None) 189s enroll progress: (<__gi__.FpiDeviceRealtek object at 0xe4bb892b38c0 (FpiDeviceRealtek at 0x3718e320)>, 5, None, None, None) 189s enroll progress: (<__gi__.FpiDeviceRealtek object at 0xe4bb892b38c0 (FpiDeviceRealtek at 0x3718e320)>, 6, None, None, None) 189s enroll progress: (<__gi__.FpiDeviceRealtek object at 0xe4bb892b38c0 (FpiDeviceRealtek at 0x3718e320)>, 7, None, None, None) 189s enroll progress: (<__gi__.FpiDeviceRealtek object at 0xe4bb892b38c0 (FpiDeviceRealtek at 0x3718e320)>, 8, None, None, None) 189s enroll done 189s listing 189s listing done 189s verifying 189s verify done 189s async identifying 189s indentification_done: 189s deleting 189s delete done 189s ** (umockdev-run:2338): DEBUG: 16:48:26.747: umockdev.vala:150: Removing test bed /tmp/umockdev.LDX1J2 189s (umockdev-run:2338): GLib-DEBUG: 16:48:26.751: unsetenv() is not thread-safe and should not be used after threads are created 189s PASS: libfprint-2/driver-realtek.test 189s Running test: libfprint-2/driver-fpcmoc.test 189s ** (umockdev-run:2350): DEBUG: 16:48:26.797: umockdev.vala:123: Created udev test bed /tmp/umockdev.HNXWJ2 189s ** (umockdev-run:2350): DEBUG: 16:48:26.797: umockdev.vala:1297: parsing device description for /devices/pci0000:00/0000:00:14.0/usb1/1-1 189s ** (umockdev-run:2350): DEBUG: 16:48:26.798: umockdev.vala:1366: creating device /devices/pci0000:00/0000:00:14.0/usb1/1-1 (subsystem usb) 189s ** (umockdev-run:2350): DEBUG: 16:48:26.801: umockdev.vala:1411: create_node_for_device: creating file device /tmp/umockdev.HNXWJ2/dev/bus/usb/001/019 189s ** (umockdev-run:2350): DEBUG: 16:48:26.801: umockdev.vala:1297: parsing device description for /devices/pci0000:00/0000:00:14.0/usb1 189s ** (umockdev-run:2350): DEBUG: 16:48:26.802: umockdev.vala:1366: creating device /devices/pci0000:00/0000:00:14.0/usb1 (subsystem usb) 189s ** (umockdev-run:2350): DEBUG: 16:48:26.804: umockdev.vala:1411: create_node_for_device: creating file device /tmp/umockdev.HNXWJ2/dev/bus/usb/001/001 189s ** (umockdev-run:2350): DEBUG: 16:48:26.804: umockdev.vala:1297: parsing device description for /devices/pci0000:00/0000:00:14.0 189s ** (umockdev-run:2350): DEBUG: 16:48:26.804: umockdev.vala:1366: creating device /devices/pci0000:00/0000:00:14.0 (subsystem pci) 189s (process:2354): libfprint-context-DEBUG: 16:48:26.853: Initializing FpContext (libfprint version 1.94.7+tod1) 189s (process:2354): libfprint-tod-DEBUG: 16:48:26.853: Impossible to load the shared drivers dir Error opening directory “/usr/lib/aarch64-linux-gnu/libfprint-2/tod-1”: No such file or directory 189s (process:2354): libfprint-DEBUG: 16:48:26.855: fpi_device_fpcmoc_init enter --> 189s (process:2354): libfprint-DEBUG: 16:48:26.855: 77855731: ../libfprint/drivers/fpcmoc/fpc.c:1854 189s (process:2354): libfprint-context-DEBUG: 16:48:26.855: No driver found for USB device 1D6B:0002 189s (process:2354): libfprint-DEBUG: 16:48:26.855: fpc_dev_probe enter --> 189s (process:2354): libfprint-DEBUG: 16:48:26.857: Device name: FPC L:0001 FW:127010 189s (process:2354): libfprint-device-DEBUG: 16:48:26.857: Device reported probe completion 189s (process:2354): libfprint-device-DEBUG: 16:48:26.857: Completing action FPI_DEVICE_ACTION_PROBE in idle! 189s (process:2354): libfprint-device-DEBUG: 16:48:26.857: Not updating temperature model, device can run continuously! 189s (process:2354): libfprint-DEBUG: 16:48:26.858: fpc_dev_open enter --> 189s (process:2354): libfprint-SSM-DEBUG: 16:48:26.859: [fpcmoc] FP_INIT_NUM_STATES entering state 0 189s (process:2354): libfprint-SSM-DEBUG: 16:48:26.859: [fpcmoc] FP_CMD_NUM_STATES entering state 0 189s (process:2354): libfprint-DEBUG: 16:48:26.859: fpc_send_ctrl_cmd CMD: 0x1, value: 0x1, index: 0 type: 2 189s (process:2354): libfprint-DEBUG: 16:48:26.859: fpc_cmd_receive_cb current ssm request: 1 state: 0 189s (process:2354): libfprint-SSM-DEBUG: 16:48:26.859: [fpcmoc] FP_CMD_NUM_STATES entering state 1 189s (process:2354): libfprint-DEBUG: 16:48:26.860: fpc_cmd_receive_cb current ssm request: 1 state: 1 189s (process:2354): libfprint-DEBUG: 16:48:26.860: fpc_cmd_receive_cb recv evt data length: 38 189s (process:2354): libfprint-DEBUG: 16:48:26.860: fpc_evt_cb INIT: status=0, Sensor = 1523, HWID = 0x1711, WxH = 96 x 96 189s (process:2354): libfprint-DEBUG: 16:48:26.860: fpc_evt_cb INIT: FW version: 1.27.0.10 189s (process:2354): libfprint-SSM-DEBUG: 16:48:26.860: [fpcmoc] FP_INIT_NUM_STATES entering state 1 189s (process:2354): libfprint-SSM-DEBUG: 16:48:26.860: [fpcmoc] FP_CMD_NUM_STATES entering state 0 189s (process:2354): libfprint-DEBUG: 16:48:26.860: fpc_send_ctrl_cmd CMD: 0x60, value: 0x0, index: 0 type: 3 189s (process:2354): libfprint-SSM-DEBUG: 16:48:26.860: [fpcmoc] FP_CMD_NUM_STATES completed successfully 189s (process:2354): libfprint-DEBUG: 16:48:26.860: fpc_cmd_receive_cb current ssm request: 96 state: 0 189s (process:2354): libfprint-DEBUG: 16:48:26.860: fpc_init_load_db_cb got dbid size: 16 189s (process:2354): libfprint-DEBUG: 16:48:26.860: fpc_init_load_db_cb dbid: 0xa981b581-adfc-e643-a0d0-88c2138092f7 189s (process:2354): libfprint-SSM-DEBUG: 16:48:26.860: [fpcmoc] FP_INIT_NUM_STATES completed successfully 189s (process:2354): libfprint-device-DEBUG: 16:48:26.860: Device reported open completion 189s (process:2354): libfprint-SSM-DEBUG: 16:48:26.860: [fpcmoc] FP_CMD_NUM_STATES completed successfully 189s (process:2354): libfprint-device-DEBUG: 16:48:26.860: Completing action FPI_DEVICE_ACTION_OPEN in idle! 189s (process:2354): libfprint-device-DEBUG: 16:48:26.860: Not updating temperature model, device can run continuously! 189s (process:2354): libfprint-DEBUG: 16:48:26.860: fpc_dev_clear_storage enter --> 189s (process:2354): libfprint-SSM-DEBUG: 16:48:26.860: [fpcmoc] Clear storage entering state 0 189s (process:2354): libfprint-SSM-DEBUG: 16:48:26.860: [fpcmoc] FP_CMD_NUM_STATES entering state 0 189s (process:2354): libfprint-DEBUG: 16:48:26.860: fpc_send_ctrl_cmd CMD: 0x62, value: 0x0, index: 0 type: 1 189s (process:2354): libfprint-DEBUG: 16:48:26.861: fpc_cmd_receive_cb current ssm request: 98 state: 0 189s (process:2354): libfprint-SSM-DEBUG: 16:48:26.861: [fpcmoc] Clear storage entering state 1 189s (process:2354): libfprint-SSM-DEBUG: 16:48:26.861: [fpcmoc] FP_CMD_NUM_STATES entering state 0 189s (process:2354): libfprint-DEBUG: 16:48:26.861: fpc_send_ctrl_cmd CMD: 0x60, value: 0x1, index: 0 type: 1 189s (process:2354): libfprint-SSM-DEBUG: 16:48:26.861: [fpcmoc] FP_CMD_NUM_STATES completed successfully 189s (process:2354): libfprint-DEBUG: 16:48:26.861: fpc_cmd_receive_cb current ssm request: 96 state: 0 189s (process:2354): libfprint-SSM-DEBUG: 16:48:26.861: [fpcmoc] Clear storage completed successfully 189s (process:2354): libfprint-DEBUG: 16:48:26.861: Clear Storage complete! 189s (process:2354): libfprint-device-DEBUG: 16:48:26.861: Device reported deletion completion 189s (process:2354): libfprint-SSM-DEBUG: 16:48:26.861: [fpcmoc] FP_CMD_NUM_STATES completed successfully 189s (process:2354): libfprint-device-DEBUG: 16:48:26.861: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 189s (process:2354): libfprint-device-DEBUG: 16:48:26.861: Not updating temperature model, device can run continuously! 189s (process:2354): libfprint-device-DEBUG: 16:48:26.862: Not updating temperature model, device can run continuously! 189s (process:2354): libfprint-DEBUG: 16:48:26.862: fpc_dev_enroll enter --> 189s (process:2354): libfprint-SSM-DEBUG: 16:48:26.862: [fpcmoc] enroll entering state 0 189s (process:2354): libfprint-SSM-DEBUG: 16:48:26.862: [fpcmoc] FP_CMD_NUM_STATES entering state 0 189s (process:2354): libfprint-DEBUG: 16:48:26.862: fpc_send_ctrl_cmd CMD: 0x70, value: 0x0, index: 0 type: 2 189s (process:2354): libfprint-DEBUG: 16:48:26.863: fpc_cmd_receive_cb current ssm request: 112 state: 0 189s (process:2354): libfprint-SSM-DEBUG: 16:48:26.863: [fpcmoc] FP_CMD_NUM_STATES entering state 1 189s (process:2354): libfprint-DEBUG: 16:48:26.863: fpc_cmd_receive_cb current ssm request: 112 state: 1 189s (process:2354): libfprint-DEBUG: 16:48:26.863: fpc_cmd_receive_cb recv evt data length: 790 189s (process:2354): libfprint-DEBUG: 16:48:26.863: fpc_evt_cb Enum Fids: status = 0, NumFids = 0 189s (process:2354): libfprint-SSM-DEBUG: 16:48:26.863: [fpcmoc] enroll entering state 1 189s (process:2354): libfprint-SSM-DEBUG: 16:48:26.863: [fpcmoc] FP_CMD_NUM_STATES entering state 0 189s (process:2354): libfprint-DEBUG: 16:48:26.863: fpc_send_ctrl_cmd CMD: 0x67, value: 0x0, index: 0 type: 3 189s (process:2354): libfprint-SSM-DEBUG: 16:48:26.864: [fpcmoc] FP_CMD_NUM_STATES completed successfully 189s (process:2354): libfprint-DEBUG: 16:48:26.864: fpc_cmd_receive_cb current ssm request: 103 state: 0 189s (process:2354): libfprint-SSM-DEBUG: 16:48:26.864: [fpcmoc] enroll entering state 2 189s (process:2354): libfprint-device-DEBUG: 16:48:26.864: Device reported finger status change: FP_FINGER_STATUS_NEEDED 189s (process:2354): libfprint-SSM-DEBUG: 16:48:26.864: [fpcmoc] FP_CMD_NUM_STATES entering state 0 189s (process:2354): libfprint-DEBUG: 16:48:26.864: fpc_send_ctrl_cmd CMD: 0x2, value: 0x1, index: 0 type: 2 189s (process:2354): libfprint-SSM-DEBUG: 16:48:26.864: [fpcmoc] FP_CMD_NUM_STATES completed successfully 189s (process:2354): libfprint-DEBUG: 16:48:26.864: fpc_cmd_receive_cb current ssm request: 2 state: 0 189s (process:2354): libfprint-SSM-DEBUG: 16:48:26.864: [fpcmoc] FP_CMD_NUM_STATES entering state 1 189s (process:2354): libfprint-DEBUG: 16:48:26.865: fpc_cmd_receive_cb current ssm request: 2 state: 1 189s (process:2354): libfprint-DEBUG: 16:48:26.865: fpc_cmd_receive_cb recv evt data length: 12 189s (process:2354): libfprint-DEBUG: 16:48:26.865: fpc_evt_cb Got finger down event 189s (process:2354): libfprint-device-DEBUG: 16:48:26.865: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 189s (process:2354): libfprint-SSM-DEBUG: 16:48:26.865: [fpcmoc] enroll entering state 3 189s (process:2354): libfprint-SSM-DEBUG: 16:48:26.865: [fpcmoc] FP_CMD_NUM_STATES entering state 0 189s (process:2354): libfprint-DEBUG: 16:48:26.865: fpc_send_ctrl_cmd CMD: 0x9, value: 0x0, index: 0 type: 2 189s (process:2354): libfprint-SSM-DEBUG: 16:48:26.865: [fpcmoc] FP_CMD_NUM_STATES completed successfully 189s (process:2354): libfprint-DEBUG: 16:48:26.865: fpc_cmd_receive_cb current ssm request: 9 state: 0 189s (process:2354): libfprint-SSM-DEBUG: 16:48:26.865: [fpcmoc] FP_CMD_NUM_STATES entering state 1 189s (process:2354): libfprint-DEBUG: 16:48:26.866: fpc_cmd_receive_cb current ssm request: 9 state: 1 189s (process:2354): libfprint-DEBUG: 16:48:26.866: fpc_cmd_receive_cb recv evt data length: 24 189s (process:2354): libfprint-DEBUG: 16:48:26.866: fpc_evt_cb Got capture event 189s (process:2354): libfprint-device-DEBUG: 16:48:26.866: Device reported finger status change: FP_FINGER_STATUS_NEEDED 189s (process:2354): libfprint-SSM-DEBUG: 16:48:26.866: [fpcmoc] enroll entering state 4 189s (process:2354): libfprint-SSM-DEBUG: 16:48:26.866: [fpcmoc] FP_CMD_NUM_STATES entering state 0 189s (process:2354): libfprint-DEBUG: 16:48:26.866: fpc_send_ctrl_cmd CMD: 0x68, value: 0x0, index: 0 type: 3 189s (process:2354): libfprint-SSM-DEBUG: 16:48:26.866: [fpcmoc] FP_CMD_NUM_STATES completed successfully 189s (process:2354): libfprint-DEBUG: 16:48:26.866: fpc_cmd_receive_cb current ssm request: 104 state: 0 189s (process:2354): libfprint-DEBUG: 16:48:26.866: Enrol Update status: 1, remaining: 11 189s (process:2354): libfprint-device-DEBUG: 16:48:26.866: Device reported enroll progress, reported 1 of 25 have been completed 189s (process:2354): libfprint-SSM-DEBUG: 16:48:26.872: [fpcmoc] enroll entering state 2 189s (process:2354): libfprint-SSM-DEBUG: 16:48:26.872: [fpcmoc] FP_CMD_NUM_STATES entering state 0 189s (process:2354): libfprint-DEBUG: 16:48:26.872: fpc_send_ctrl_cmd CMD: 0x2, value: 0x1, index: 0 type: 2 189s (process:2354): libfprint-SSM-DEBUG: 16:48:26.872: [fpcmoc] FP_CMD_NUM_STATES completed successfully 189s (process:2354): libfprint-DEBUG: 16:48:26.873: fpc_cmd_receive_cb current ssm request: 2 state: 0 189s (process:2354): libfprint-SSM-DEBUG: 16:48:26.873: [fpcmoc] FP_CMD_NUM_STATES entering state 1 189s (process:2354): libfprint-DEBUG: 16:48:26.873: fpc_cmd_receive_cb current ssm request: 2 state: 1 189s (process:2354): libfprint-DEBUG: 16:48:26.873: fpc_cmd_receive_cb recv evt data length: 12 189s (process:2354): libfprint-DEBUG: 16:48:26.873: fpc_evt_cb Got finger down event 189s (process:2354): libfprint-device-DEBUG: 16:48:26.873: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 189s (process:2354): libfprint-SSM-DEBUG: 16:48:26.873: [fpcmoc] enroll entering state 3 189s (process:2354): libfprint-SSM-DEBUG: 16:48:26.873: [fpcmoc] FP_CMD_NUM_STATES entering state 0 189s (process:2354): libfprint-DEBUG: 16:48:26.873: fpc_send_ctrl_cmd CMD: 0x9, value: 0x0, index: 0 type: 2 189s (process:2354): libfprint-SSM-DEBUG: 16:48:26.873: [fpcmoc] FP_CMD_NUM_STATES completed successfully 189s (process:2354): libfprint-DEBUG: 16:48:26.874: fpc_cmd_receive_cb current ssm request: 9 state: 0 189s (process:2354): libfprint-SSM-DEBUG: 16:48:26.874: [fpcmoc] FP_CMD_NUM_STATES entering state 1 189s (process:2354): libfprint-DEBUG: 16:48:26.874: fpc_cmd_receive_cb current ssm request: 9 state: 1 189s (process:2354): libfprint-DEBUG: 16:48:26.874: fpc_cmd_receive_cb recv evt data length: 24 189s (process:2354): libfprint-DEBUG: 16:48:26.874: fpc_evt_cb Got capture event 189s (process:2354): libfprint-device-DEBUG: 16:48:26.874: Device reported finger status change: FP_FINGER_STATUS_NEEDED 189s (process:2354): libfprint-SSM-DEBUG: 16:48:26.874: [fpcmoc] enroll entering state 4 189s (process:2354): libfprint-SSM-DEBUG: 16:48:26.874: [fpcmoc] FP_CMD_NUM_STATES entering state 0 189s (process:2354): libfprint-DEBUG: 16:48:26.874: fpc_send_ctrl_cmd CMD: 0x68, value: 0x0, index: 0 type: 3 189s (process:2354): libfprint-SSM-DEBUG: 16:48:26.875: [fpcmoc] FP_CMD_NUM_STATES completed successfully 189s (process:2354): libfprint-DEBUG: 16:48:26.875: fpc_cmd_receive_cb current ssm request: 104 state: 0 189s (process:2354): libfprint-DEBUG: 16:48:26.875: Enrol Update status: 1, remaining: 10 189s (process:2354): libfprint-device-DEBUG: 16:48:26.875: Device reported enroll progress, reported 2 of 25 have been completed 189s (process:2354): libfprint-SSM-DEBUG: 16:48:26.875: [fpcmoc] enroll entering state 2 189s (process:2354): libfprint-SSM-DEBUG: 16:48:26.875: [fpcmoc] FP_CMD_NUM_STATES entering state 0 189s (process:2354): libfprint-DEBUG: 16:48:26.875: fpc_send_ctrl_cmd CMD: 0x2, value: 0x1, index: 0 type: 2 189s (process:2354): libfprint-SSM-DEBUG: 16:48:26.875: [fpcmoc] FP_CMD_NUM_STATES completed successfully 189s (process:2354): libfprint-DEBUG: 16:48:26.875: fpc_cmd_receive_cb current ssm request: 2 state: 0 189s (process:2354): libfprint-SSM-DEBUG: 16:48:26.875: [fpcmoc] FP_CMD_NUM_STATES entering state 1 189s (process:2354): libfprint-DEBUG: 16:48:26.876: fpc_cmd_receive_cb current ssm request: 2 state: 1 189s (process:2354): libfprint-DEBUG: 16:48:26.876: fpc_cmd_receive_cb recv evt data length: 12 189s (process:2354): libfprint-DEBUG: 16:48:26.876: fpc_evt_cb Got finger down event 189s (process:2354): libfprint-device-DEBUG: 16:48:26.876: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 189s (process:2354): libfprint-SSM-DEBUG: 16:48:26.876: [fpcmoc] enroll entering state 3 189s (process:2354): libfprint-SSM-DEBUG: 16:48:26.876: [fpcmoc] FP_CMD_NUM_STATES entering state 0 189s (process:2354): libfprint-DEBUG: 16:48:26.876: fpc_send_ctrl_cmd CMD: 0x9, value: 0x0, index: 0 type: 2 189s (process:2354): libfprint-SSM-DEBUG: 16:48:26.876: [fpcmoc] FP_CMD_NUM_STATES completed successfully 189s (process:2354): libfprint-DEBUG: 16:48:26.877: fpc_cmd_receive_cb current ssm request: 9 state: 0 189s (process:2354): libfprint-SSM-DEBUG: 16:48:26.877: [fpcmoc] FP_CMD_NUM_STATES entering state 1 189s (process:2354): libfprint-DEBUG: 16:48:26.877: fpc_cmd_receive_cb current ssm request: 9 state: 1 189s (process:2354): libfprint-DEBUG: 16:48:26.877: fpc_cmd_receive_cb recv evt data length: 24 189s (process:2354): libfprint-DEBUG: 16:48:26.877: fpc_evt_cb Got capture event 189s (process:2354): libfprint-device-DEBUG: 16:48:26.877: Device reported finger status change: FP_FINGER_STATUS_NEEDED 189s (process:2354): libfprint-SSM-DEBUG: 16:48:26.877: [fpcmoc] enroll entering state 4 189s (process:2354): libfprint-SSM-DEBUG: 16:48:26.877: [fpcmoc] FP_CMD_NUM_STATES entering state 0 189s (process:2354): libfprint-DEBUG: 16:48:26.877: fpc_send_ctrl_cmd CMD: 0x68, value: 0x0, index: 0 type: 3 189s (process:2354): libfprint-SSM-DEBUG: 16:48:26.877: [fpcmoc] FP_CMD_NUM_STATES completed successfully 189s (process:2354): libfprint-DEBUG: 16:48:26.878: fpc_cmd_receive_cb current ssm request: 104 state: 0 189s (process:2354): libfprint-DEBUG: 16:48:26.878: Enrol Update status: 1, remaining: 9 189s (process:2354): libfprint-device-DEBUG: 16:48:26.878: Device reported enroll progress, reported 3 of 25 have been completed 189s (process:2354): libfprint-SSM-DEBUG: 16:48:26.878: [fpcmoc] enroll entering state 2 189s (process:2354): libfprint-SSM-DEBUG: 16:48:26.878: [fpcmoc] FP_CMD_NUM_STATES entering state 0 189s (process:2354): libfprint-DEBUG: 16:48:26.878: fpc_send_ctrl_cmd CMD: 0x2, value: 0x1, index: 0 type: 2 189s (process:2354): libfprint-SSM-DEBUG: 16:48:26.878: [fpcmoc] FP_CMD_NUM_STATES completed successfully 189s (process:2354): libfprint-DEBUG: 16:48:26.878: fpc_cmd_receive_cb current ssm request: 2 state: 0 189s (process:2354): libfprint-SSM-DEBUG: 16:48:26.878: [fpcmoc] FP_CMD_NUM_STATES entering state 1 189s (process:2354): libfprint-DEBUG: 16:48:26.879: fpc_cmd_receive_cb current ssm request: 2 state: 1 189s (process:2354): libfprint-DEBUG: 16:48:26.879: fpc_cmd_receive_cb recv evt data length: 12 189s (process:2354): libfprint-DEBUG: 16:48:26.879: fpc_evt_cb Got finger down event 189s (process:2354): libfprint-device-DEBUG: 16:48:26.879: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 189s (process:2354): libfprint-SSM-DEBUG: 16:48:26.879: [fpcmoc] enroll entering state 3 189s (process:2354): libfprint-SSM-DEBUG: 16:48:26.879: [fpcmoc] FP_CMD_NUM_STATES entering state 0 189s (process:2354): libfprint-DEBUG: 16:48:26.879: fpc_send_ctrl_cmd CMD: 0x9, value: 0x0, index: 0 type: 2 189s (process:2354): libfprint-SSM-DEBUG: 16:48:26.879: [fpcmoc] FP_CMD_NUM_STATES completed successfully 189s (process:2354): libfprint-DEBUG: 16:48:26.879: fpc_cmd_receive_cb current ssm request: 9 state: 0 189s (process:2354): libfprint-SSM-DEBUG: 16:48:26.879: [fpcmoc] FP_CMD_NUM_STATES entering state 1 189s (process:2354): libfprint-DEBUG: 16:48:26.879: fpc_cmd_receive_cb current ssm request: 9 state: 1 189s (process:2354): libfprint-DEBUG: 16:48:26.879: fpc_cmd_receive_cb recv evt data length: 24 189s (process:2354): libfprint-DEBUG: 16:48:26.879: fpc_evt_cb Got capture event 189s (process:2354): libfprint-device-DEBUG: 16:48:26.879: Device reported finger status change: FP_FINGER_STATUS_NEEDED 189s (process:2354): libfprint-SSM-DEBUG: 16:48:26.879: [fpcmoc] enroll entering state 4 189s (process:2354): libfprint-SSM-DEBUG: 16:48:26.879: [fpcmoc] FP_CMD_NUM_STATES entering state 0 189s (process:2354): libfprint-DEBUG: 16:48:26.879: fpc_send_ctrl_cmd CMD: 0x68, value: 0x0, index: 0 type: 3 189s (process:2354): libfprint-SSM-DEBUG: 16:48:26.880: [fpcmoc] FP_CMD_NUM_STATES completed successfully 189s (process:2354): libfprint-DEBUG: 16:48:26.880: fpc_cmd_receive_cb current ssm request: 104 state: 0 189s (process:2354): libfprint-DEBUG: 16:48:26.880: Enrol Update status: 1, remaining: 8 189s (process:2354): libfprint-device-DEBUG: 16:48:26.880: Device reported enroll progress, reported 4 of 25 have been completed 189s (process:2354): libfprint-SSM-DEBUG: 16:48:26.880: [fpcmoc] enroll entering state 2 189s (process:2354): libfprint-SSM-DEBUG: 16:48:26.880: [fpcmoc] FP_CMD_NUM_STATES entering state 0 189s (process:2354): libfprint-DEBUG: 16:48:26.880: fpc_send_ctrl_cmd CMD: 0x2, value: 0x1, index: 0 type: 2 189s (process:2354): libfprint-SSM-DEBUG: 16:48:26.880: [fpcmoc] FP_CMD_NUM_STATES completed successfully 189s (process:2354): libfprint-DEBUG: 16:48:26.880: fpc_cmd_receive_cb current ssm request: 2 state: 0 189s (process:2354): libfprint-SSM-DEBUG: 16:48:26.880: [fpcmoc] FP_CMD_NUM_STATES entering state 1 189s (process:2354): libfprint-DEBUG: 16:48:26.881: fpc_cmd_receive_cb current ssm request: 2 state: 1 189s (process:2354): libfprint-DEBUG: 16:48:26.881: fpc_cmd_receive_cb recv evt data length: 12 189s (process:2354): libfprint-DEBUG: 16:48:26.881: fpc_evt_cb Got finger down event 189s (process:2354): libfprint-device-DEBUG: 16:48:26.881: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 189s (process:2354): libfprint-SSM-DEBUG: 16:48:26.881: [fpcmoc] enroll entering state 3 189s (process:2354): libfprint-SSM-DEBUG: 16:48:26.881: [fpcmoc] FP_CMD_NUM_STATES entering state 0 189s (process:2354): libfprint-DEBUG: 16:48:26.881: fpc_send_ctrl_cmd CMD: 0x9, value: 0x0, index: 0 type: 2 189s (process:2354): libfprint-SSM-DEBUG: 16:48:26.881: [fpcmoc] FP_CMD_NUM_STATES completed successfully 189s (process:2354): libfprint-DEBUG: 16:48:26.881: fpc_cmd_receive_cb current ssm request: 9 state: 0 189s (process:2354): libfprint-SSM-DEBUG: 16:48:26.881: [fpcmoc] FP_CMD_NUM_STATES entering state 1 189s (process:2354): libfprint-DEBUG: 16:48:26.882: fpc_cmd_receive_cb current ssm request: 9 state: 1 189s (process:2354): libfprint-DEBUG: 16:48:26.882: fpc_cmd_receive_cb recv evt data length: 24 189s (process:2354): libfprint-DEBUG: 16:48:26.882: fpc_evt_cb Got capture event 189s (process:2354): libfprint-device-DEBUG: 16:48:26.882: Device reported finger status change: FP_FINGER_STATUS_NEEDED 189s (process:2354): libfprint-SSM-DEBUG: 16:48:26.882: [fpcmoc] enroll entering state 4 189s (process:2354): libfprint-SSM-DEBUG: 16:48:26.882: [fpcmoc] FP_CMD_NUM_STATES entering state 0 189s (process:2354): libfprint-DEBUG: 16:48:26.882: fpc_send_ctrl_cmd CMD: 0x68, value: 0x0, index: 0 type: 3 189s (process:2354): libfprint-SSM-DEBUG: 16:48:26.882: [fpcmoc] FP_CMD_NUM_STATES completed successfully 189s (process:2354): libfprint-DEBUG: 16:48:26.882: fpc_cmd_receive_cb current ssm request: 104 state: 0 189s (process:2354): libfprint-DEBUG: 16:48:26.882: Enrol Update status: 1, remaining: 7 189s (process:2354): libfprint-device-DEBUG: 16:48:26.882: Device reported enroll progress, reported 5 of 25 have been completed 189s (process:2354): libfprint-SSM-DEBUG: 16:48:26.882: [fpcmoc] enroll entering state 2 189s (process:2354): libfprint-SSM-DEBUG: 16:48:26.882: [fpcmoc] FP_CMD_NUM_STATES entering state 0 189s (process:2354): libfprint-DEBUG: 16:48:26.882: fpc_send_ctrl_cmd CMD: 0x2, value: 0x1, index: 0 type: 2 189s (process:2354): libfprint-SSM-DEBUG: 16:48:26.883: [fpcmoc] FP_CMD_NUM_STATES completed successfully 189s (process:2354): libfprint-DEBUG: 16:48:26.883: fpc_cmd_receive_cb current ssm request: 2 state: 0 189s (process:2354): libfprint-SSM-DEBUG: 16:48:26.883: [fpcmoc] FP_CMD_NUM_STATES entering state 1 189s (process:2354): libfprint-DEBUG: 16:48:26.883: fpc_cmd_receive_cb current ssm request: 2 state: 1 189s (process:2354): libfprint-DEBUG: 16:48:26.883: fpc_cmd_receive_cb recv evt data length: 12 189s (process:2354): libfprint-DEBUG: 16:48:26.883: fpc_evt_cb Got finger down event 189s (process:2354): libfprint-device-DEBUG: 16:48:26.883: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 189s (process:2354): libfprint-SSM-DEBUG: 16:48:26.883: [fpcmoc] enroll entering state 3 189s (process:2354): libfprint-SSM-DEBUG: 16:48:26.883: [fpcmoc] FP_CMD_NUM_STATES entering state 0 189s (process:2354): libfprint-DEBUG: 16:48:26.883: fpc_send_ctrl_cmd CMD: 0x9, value: 0x0, index: 0 type: 2 189s (process:2354): libfprint-SSM-DEBUG: 16:48:26.884: [fpcmoc] FP_CMD_NUM_STATES completed successfully 189s (process:2354): libfprint-DEBUG: 16:48:26.884: fpc_cmd_receive_cb current ssm request: 9 state: 0 189s (process:2354): libfprint-SSM-DEBUG: 16:48:26.884: [fpcmoc] FP_CMD_NUM_STATES entering state 1 189s (process:2354): libfprint-DEBUG: 16:48:26.884: fpc_cmd_receive_cb current ssm request: 9 state: 1 189s (process:2354): libfprint-DEBUG: 16:48:26.884: fpc_cmd_receive_cb recv evt data length: 24 189s (process:2354): libfprint-DEBUG: 16:48:26.884: fpc_evt_cb Got capture event 189s (process:2354): libfprint-device-DEBUG: 16:48:26.884: Device reported finger status change: FP_FINGER_STATUS_NEEDED 189s (process:2354): libfprint-SSM-DEBUG: 16:48:26.884: [fpcmoc] enroll entering state 4 189s (process:2354): libfprint-SSM-DEBUG: 16:48:26.884: [fpcmoc] FP_CMD_NUM_STATES entering state 0 189s (process:2354): libfprint-DEBUG: 16:48:26.884: fpc_send_ctrl_cmd CMD: 0x68, value: 0x0, index: 0 type: 3 189s (process:2354): libfprint-SSM-DEBUG: 16:48:26.884: [fpcmoc] FP_CMD_NUM_STATES completed successfully 189s (process:2354): libfprint-DEBUG: 16:48:26.885: fpc_cmd_receive_cb current ssm request: 104 state: 0 189s (process:2354): libfprint-DEBUG: 16:48:26.885: Enrol Update status: 5, remaining: 7 189s (process:2354): libfprint-DEBUG: 16:48:26.885: Sample overlapping ratio is too High 189s (process:2354): libfprint-device-DEBUG: 16:48:26.885: Device reported enroll progress, reported 5 of 25 have been completed 189s (process:2354): libfprint-SSM-DEBUG: 16:48:26.885: [fpcmoc] enroll entering state 2 189s (process:2354): libfprint-SSM-DEBUG: 16:48:26.885: [fpcmoc] FP_CMD_NUM_STATES entering state 0 189s (process:2354): libfprint-DEBUG: 16:48:26.885: fpc_send_ctrl_cmd CMD: 0x2, value: 0x1, index: 0 type: 2 189s (process:2354): libfprint-SSM-DEBUG: 16:48:26.885: [fpcmoc] FP_CMD_NUM_STATES completed successfully 189s (process:2354): libfprint-DEBUG: 16:48:26.885: fpc_cmd_receive_cb current ssm request: 2 state: 0 189s (process:2354): libfprint-SSM-DEBUG: 16:48:26.885: [fpcmoc] FP_CMD_NUM_STATES entering state 1 189s (process:2354): libfprint-DEBUG: 16:48:26.886: fpc_cmd_receive_cb current ssm request: 2 state: 1 189s (process:2354): libfprint-DEBUG: 16:48:26.886: fpc_cmd_receive_cb recv evt data length: 12 189s (process:2354): libfprint-DEBUG: 16:48:26.886: fpc_evt_cb Got finger down event 189s (process:2354): libfprint-device-DEBUG: 16:48:26.886: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 189s (process:2354): libfprint-SSM-DEBUG: 16:48:26.886: [fpcmoc] enroll entering state 3 189s (process:2354): libfprint-SSM-DEBUG: 16:48:26.886: [fpcmoc] FP_CMD_NUM_STATES entering state 0 189s (process:2354): libfprint-DEBUG: 16:48:26.886: fpc_send_ctrl_cmd CMD: 0x9, value: 0x0, index: 0 type: 2 189s (process:2354): libfprint-SSM-DEBUG: 16:48:26.886: [fpcmoc] FP_CMD_NUM_STATES completed successfully 189s (process:2354): libfprint-DEBUG: 16:48:26.886: fpc_cmd_receive_cb current ssm request: 9 state: 0 189s (process:2354): libfprint-SSM-DEBUG: 16:48:26.886: [fpcmoc] FP_CMD_NUM_STATES entering state 1 189s (process:2354): libfprint-DEBUG: 16:48:26.887: fpc_cmd_receive_cb current ssm request: 9 state: 1 189s (process:2354): libfprint-DEBUG: 16:48:26.887: fpc_cmd_receive_cb recv evt data length: 24 189s (process:2354): libfprint-DEBUG: 16:48:26.887: fpc_evt_cb Got capture event 189s (process:2354): libfprint-device-DEBUG: 16:48:26.887: Device reported finger status change: FP_FINGER_STATUS_NEEDED 189s (process:2354): libfprint-SSM-DEBUG: 16:48:26.887: [fpcmoc] enroll entering state 4 189s (process:2354): libfprint-SSM-DEBUG: 16:48:26.887: [fpcmoc] FP_CMD_NUM_STATES entering state 0 189s (process:2354): libfprint-DEBUG: 16:48:26.887: fpc_send_ctrl_cmd CMD: 0x68, value: 0x0, index: 0 type: 3 189s (process:2354): libfprint-SSM-DEBUG: 16:48:26.887: [fpcmoc] FP_CMD_NUM_STATES completed successfully 189s (process:2354): libfprint-DEBUG: 16:48:26.887: fpc_cmd_receive_cb current ssm request: 104 state: 0 189s (process:2354): libfprint-DEBUG: 16:48:26.887: Enrol Update status: 1, remaining: 6 189s (process:2354): libfprint-device-DEBUG: 16:48:26.887: Device reported enroll progress, reported 6 of 25 have been completed 189s (process:2354): libfprint-SSM-DEBUG: 16:48:26.887: [fpcmoc] enroll entering state 2 189s (process:2354): libfprint-SSM-DEBUG: 16:48:26.887: [fpcmoc] FP_CMD_NUM_STATES entering state 0 189s (process:2354): libfprint-DEBUG: 16:48:26.887: fpc_send_ctrl_cmd CMD: 0x2, value: 0x1, index: 0 type: 2 189s (process:2354): libfprint-SSM-DEBUG: 16:48:26.887: [fpcmoc] FP_CMD_NUM_STATES completed successfully 189s (process:2354): libfprint-DEBUG: 16:48:26.888: fpc_cmd_receive_cb current ssm request: 2 state: 0 189s (process:2354): libfprint-SSM-DEBUG: 16:48:26.888: [fpcmoc] FP_CMD_NUM_STATES entering state 1 189s (process:2354): libfprint-DEBUG: 16:48:26.888: fpc_cmd_receive_cb current ssm request: 2 state: 1 189s (process:2354): libfprint-DEBUG: 16:48:26.888: fpc_cmd_receive_cb recv evt data length: 12 189s (process:2354): libfprint-DEBUG: 16:48:26.888: fpc_evt_cb Got finger down event 189s (process:2354): libfprint-device-DEBUG: 16:48:26.888: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 189s (process:2354): libfprint-SSM-DEBUG: 16:48:26.888: [fpcmoc] enroll entering state 3 189s (process:2354): libfprint-SSM-DEBUG: 16:48:26.888: [fpcmoc] FP_CMD_NUM_STATES entering state 0 189s (process:2354): libfprint-DEBUG: 16:48:26.888: fpc_send_ctrl_cmd CMD: 0x9, value: 0x0, index: 0 type: 2 189s (process:2354): libfprint-SSM-DEBUG: 16:48:26.888: [fpcmoc] FP_CMD_NUM_STATES completed successfully 189s (process:2354): libfprint-DEBUG: 16:48:26.889: fpc_cmd_receive_cb current ssm request: 9 state: 0 189s (process:2354): libfprint-SSM-DEBUG: 16:48:26.889: [fpcmoc] FP_CMD_NUM_STATES entering state 1 189s (process:2354): libfprint-DEBUG: 16:48:26.889: fpc_cmd_receive_cb current ssm request: 9 state: 1 189s (process:2354): libfprint-DEBUG: 16:48:26.889: fpc_cmd_receive_cb recv evt data length: 24 189s (process:2354): libfprint-DEBUG: 16:48:26.889: fpc_evt_cb Got capture event 189s (process:2354): libfprint-device-DEBUG: 16:48:26.889: Device reported finger status change: FP_FINGER_STATUS_NEEDED 189s (process:2354): libfprint-SSM-DEBUG: 16:48:26.889: [fpcmoc] enroll entering state 4 189s (process:2354): libfprint-SSM-DEBUG: 16:48:26.889: [fpcmoc] FP_CMD_NUM_STATES entering state 0 189s (process:2354): libfprint-DEBUG: 16:48:26.889: fpc_send_ctrl_cmd CMD: 0x68, value: 0x0, index: 0 type: 3 189s (process:2354): libfprint-SSM-DEBUG: 16:48:26.889: [fpcmoc] FP_CMD_NUM_STATES completed successfully 189s (process:2354): libfprint-DEBUG: 16:48:26.889: fpc_cmd_receive_cb current ssm request: 104 state: 0 189s (process:2354): libfprint-DEBUG: 16:48:26.889: Enrol Update status: 1, remaining: 5 189s (process:2354): libfprint-device-DEBUG: 16:48:26.889: Device reported enroll progress, reported 7 of 25 have been completed 189s (process:2354): libfprint-SSM-DEBUG: 16:48:26.890: [fpcmoc] enroll entering state 2 189s (process:2354): libfprint-SSM-DEBUG: 16:48:26.890: [fpcmoc] FP_CMD_NUM_STATES entering state 0 189s (process:2354): libfprint-DEBUG: 16:48:26.890: fpc_send_ctrl_cmd CMD: 0x2, value: 0x1, index: 0 type: 2 189s (process:2354): libfprint-SSM-DEBUG: 16:48:26.890: [fpcmoc] FP_CMD_NUM_STATES completed successfully 189s (process:2354): libfprint-DEBUG: 16:48:26.890: fpc_cmd_receive_cb current ssm request: 2 state: 0 189s (process:2354): libfprint-SSM-DEBUG: 16:48:26.890: [fpcmoc] FP_CMD_NUM_STATES entering state 1 189s (process:2354): libfprint-DEBUG: 16:48:26.890: fpc_cmd_receive_cb current ssm request: 2 state: 1 189s (process:2354): libfprint-DEBUG: 16:48:26.890: fpc_cmd_receive_cb recv evt data length: 12 189s (process:2354): libfprint-DEBUG: 16:48:26.890: fpc_evt_cb Got finger down event 189s (process:2354): libfprint-device-DEBUG: 16:48:26.890: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 189s (process:2354): libfprint-SSM-DEBUG: 16:48:26.890: [fpcmoc] enroll entering state 3 189s (process:2354): libfprint-SSM-DEBUG: 16:48:26.890: [fpcmoc] FP_CMD_NUM_STATES entering state 0 189s (process:2354): libfprint-DEBUG: 16:48:26.890: fpc_send_ctrl_cmd CMD: 0x9, value: 0x0, index: 0 type: 2 189s (process:2354): libfprint-SSM-DEBUG: 16:48:26.891: [fpcmoc] FP_CMD_NUM_STATES completed successfully 189s (process:2354): libfprint-DEBUG: 16:48:26.891: fpc_cmd_receive_cb current ssm request: 9 state: 0 189s (process:2354): libfprint-SSM-DEBUG: 16:48:26.891: [fpcmoc] FP_CMD_NUM_STATES entering state 1 189s (process:2354): libfprint-DEBUG: 16:48:26.891: fpc_cmd_receive_cb current ssm request: 9 state: 1 189s (process:2354): libfprint-DEBUG: 16:48:26.891: fpc_cmd_receive_cb recv evt data length: 24 189s (process:2354): libfprint-DEBUG: 16:48:26.891: fpc_evt_cb Got capture event 189s (process:2354): libfprint-device-DEBUG: 16:48:26.891: Device reported finger status change: FP_FINGER_STATUS_NEEDED 189s (process:2354): libfprint-SSM-DEBUG: 16:48:26.891: [fpcmoc] enroll entering state 4 189s (process:2354): libfprint-SSM-DEBUG: 16:48:26.891: [fpcmoc] FP_CMD_NUM_STATES entering state 0 189s (process:2354): libfprint-DEBUG: 16:48:26.891: fpc_send_ctrl_cmd CMD: 0x68, value: 0x0, index: 0 type: 3 189s (process:2354): libfprint-SSM-DEBUG: 16:48:26.892: [fpcmoc] FP_CMD_NUM_STATES completed successfully 189s (process:2354): libfprint-DEBUG: 16:48:26.892: fpc_cmd_receive_cb current ssm request: 104 state: 0 189s (process:2354): libfprint-DEBUG: 16:48:26.892: Enrol Update status: 5, remaining: 5 189s (process:2354): libfprint-DEBUG: 16:48:26.892: Sample overlapping ratio is too High 189s (process:2354): libfprint-device-DEBUG: 16:48:26.892: Device reported enroll progress, reported 7 of 25 have been completed 189s (process:2354): libfprint-SSM-DEBUG: 16:48:26.892: [fpcmoc] enroll entering state 2 189s (process:2354): libfprint-SSM-DEBUG: 16:48:26.892: [fpcmoc] FP_CMD_NUM_STATES entering state 0 189s (process:2354): libfprint-DEBUG: 16:48:26.892: fpc_send_ctrl_cmd CMD: 0x2, value: 0x1, index: 0 type: 2 189s (process:2354): libfprint-SSM-DEBUG: 16:48:26.892: [fpcmoc] FP_CMD_NUM_STATES completed successfully 189s (process:2354): libfprint-DEBUG: 16:48:26.892: fpc_cmd_receive_cb current ssm request: 2 state: 0 189s (process:2354): libfprint-SSM-DEBUG: 16:48:26.892: [fpcmoc] FP_CMD_NUM_STATES entering state 1 189s (process:2354): libfprint-DEBUG: 16:48:26.893: fpc_cmd_receive_cb current ssm request: 2 state: 1 189s (process:2354): libfprint-DEBUG: 16:48:26.893: fpc_cmd_receive_cb recv evt data length: 12 189s (process:2354): libfprint-DEBUG: 16:48:26.893: fpc_evt_cb Got finger down event 189s (process:2354): libfprint-device-DEBUG: 16:48:26.893: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 189s (process:2354): libfprint-SSM-DEBUG: 16:48:26.893: [fpcmoc] enroll entering state 3 189s (process:2354): libfprint-SSM-DEBUG: 16:48:26.893: [fpcmoc] FP_CMD_NUM_STATES entering state 0 189s (process:2354): libfprint-DEBUG: 16:48:26.893: fpc_send_ctrl_cmd CMD: 0x9, value: 0x0, index: 0 type: 2 189s (process:2354): libfprint-SSM-DEBUG: 16:48:26.893: [fpcmoc] FP_CMD_NUM_STATES completed successfully 189s (process:2354): libfprint-DEBUG: 16:48:26.893: fpc_cmd_receive_cb current ssm request: 9 state: 0 189s (process:2354): libfprint-SSM-DEBUG: 16:48:26.893: [fpcmoc] FP_CMD_NUM_STATES entering state 1 189s (process:2354): libfprint-DEBUG: 16:48:26.894: fpc_cmd_receive_cb current ssm request: 9 state: 1 189s (process:2354): libfprint-DEBUG: 16:48:26.894: fpc_cmd_receive_cb recv evt data length: 24 189s (process:2354): libfprint-DEBUG: 16:48:26.894: fpc_evt_cb Got capture event 189s (process:2354): libfprint-device-DEBUG: 16:48:26.894: Device reported finger status change: FP_FINGER_STATUS_NEEDED 189s (process:2354): libfprint-SSM-DEBUG: 16:48:26.894: [fpcmoc] enroll entering state 4 189s (process:2354): libfprint-SSM-DEBUG: 16:48:26.894: [fpcmoc] FP_CMD_NUM_STATES entering state 0 189s (process:2354): libfprint-DEBUG: 16:48:26.894: fpc_send_ctrl_cmd CMD: 0x68, value: 0x0, index: 0 type: 3 189s (process:2354): libfprint-SSM-DEBUG: 16:48:26.894: [fpcmoc] FP_CMD_NUM_STATES completed successfully 189s (process:2354): libfprint-DEBUG: 16:48:26.894: fpc_cmd_receive_cb current ssm request: 104 state: 0 189s (process:2354): libfprint-DEBUG: 16:48:26.894: Enrol Update status: 1, remaining: 4 189s (process:2354): libfprint-device-DEBUG: 16:48:26.894: Device reported enroll progress, reported 8 of 25 have been completed 189s (process:2354): libfprint-SSM-DEBUG: 16:48:26.894: [fpcmoc] enroll entering state 2 189s (process:2354): libfprint-SSM-DEBUG: 16:48:26.894: [fpcmoc] FP_CMD_NUM_STATES entering state 0 189s (process:2354): libfprint-DEBUG: 16:48:26.894: fpc_send_ctrl_cmd CMD: 0x2, value: 0x1, index: 0 type: 2 189s (process:2354): libfprint-SSM-DEBUG: 16:48:26.895: [fpcmoc] FP_CMD_NUM_STATES completed successfully 189s (process:2354): libfprint-DEBUG: 16:48:26.895: fpc_cmd_receive_cb current ssm request: 2 state: 0 189s (process:2354): libfprint-SSM-DEBUG: 16:48:26.895: [fpcmoc] FP_CMD_NUM_STATES entering state 1 189s (process:2354): libfprint-DEBUG: 16:48:26.895: fpc_cmd_receive_cb current ssm request: 2 state: 1 189s (process:2354): libfprint-DEBUG: 16:48:26.895: fpc_cmd_receive_cb recv evt data length: 12 189s (process:2354): libfprint-DEBUG: 16:48:26.895: fpc_evt_cb Got finger down event 189s (process:2354): libfprint-device-DEBUG: 16:48:26.895: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 189s (process:2354): libfprint-SSM-DEBUG: 16:48:26.895: [fpcmoc] enroll entering state 3 189s (process:2354): libfprint-SSM-DEBUG: 16:48:26.895: [fpcmoc] FP_CMD_NUM_STATES entering state 0 189s (process:2354): libfprint-DEBUG: 16:48:26.895: fpc_send_ctrl_cmd CMD: 0x9, value: 0x0, index: 0 type: 2 189s (process:2354): libfprint-SSM-DEBUG: 16:48:26.896: [fpcmoc] FP_CMD_NUM_STATES completed successfully 189s (process:2354): libfprint-DEBUG: 16:48:26.896: fpc_cmd_receive_cb current ssm request: 9 state: 0 189s (process:2354): libfprint-SSM-DEBUG: 16:48:26.896: [fpcmoc] FP_CMD_NUM_STATES entering state 1 189s (process:2354): libfprint-DEBUG: 16:48:26.896: fpc_cmd_receive_cb current ssm request: 9 state: 1 189s (process:2354): libfprint-DEBUG: 16:48:26.896: fpc_cmd_receive_cb recv evt data length: 24 189s (process:2354): libfprint-DEBUG: 16:48:26.896: fpc_evt_cb Got capture event 189s (process:2354): libfprint-device-DEBUG: 16:48:26.896: Device reported finger status change: FP_FINGER_STATUS_NEEDED 189s (process:2354): libfprint-SSM-DEBUG: 16:48:26.896: [fpcmoc] enroll entering state 4 189s (process:2354): libfprint-SSM-DEBUG: 16:48:26.896: [fpcmoc] FP_CMD_NUM_STATES entering state 0 189s (process:2354): libfprint-DEBUG: 16:48:26.896: fpc_send_ctrl_cmd CMD: 0x68, value: 0x0, index: 0 type: 3 189s (process:2354): libfprint-SSM-DEBUG: 16:48:26.897: [fpcmoc] FP_CMD_NUM_STATES completed successfully 189s (process:2354): libfprint-DEBUG: 16:48:26.897: fpc_cmd_receive_cb current ssm request: 104 state: 0 189s (process:2354): libfprint-DEBUG: 16:48:26.897: Enrol Update status: 1, remaining: 3 189s (process:2354): libfprint-device-DEBUG: 16:48:26.897: Device reported enroll progress, reported 9 of 25 have been completed 189s (process:2354): libfprint-SSM-DEBUG: 16:48:26.897: [fpcmoc] enroll entering state 2 189s (process:2354): libfprint-SSM-DEBUG: 16:48:26.897: [fpcmoc] FP_CMD_NUM_STATES entering state 0 189s (process:2354): libfprint-DEBUG: 16:48:26.897: fpc_send_ctrl_cmd CMD: 0x2, value: 0x1, index: 0 type: 2 189s (process:2354): libfprint-SSM-DEBUG: 16:48:26.897: [fpcmoc] FP_CMD_NUM_STATES completed successfully 189s (process:2354): libfprint-DEBUG: 16:48:26.897: fpc_cmd_receive_cb current ssm request: 2 state: 0 189s (process:2354): libfprint-SSM-DEBUG: 16:48:26.897: [fpcmoc] FP_CMD_NUM_STATES entering state 1 189s (process:2354): libfprint-DEBUG: 16:48:26.898: fpc_cmd_receive_cb current ssm request: 2 state: 1 189s (process:2354): libfprint-DEBUG: 16:48:26.898: fpc_cmd_receive_cb recv evt data length: 12 189s (process:2354): libfprint-DEBUG: 16:48:26.898: fpc_evt_cb Got finger down event 189s (process:2354): libfprint-device-DEBUG: 16:48:26.898: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 189s (process:2354): libfprint-SSM-DEBUG: 16:48:26.898: [fpcmoc] enroll entering state 3 189s (process:2354): libfprint-SSM-DEBUG: 16:48:26.898: [fpcmoc] FP_CMD_NUM_STATES entering state 0 189s (process:2354): libfprint-DEBUG: 16:48:26.898: fpc_send_ctrl_cmd CMD: 0x9, value: 0x0, index: 0 type: 2 189s (process:2354): libfprint-SSM-DEBUG: 16:48:26.898: [fpcmoc] FP_CMD_NUM_STATES completed successfully 189s (process:2354): libfprint-DEBUG: 16:48:26.898: fpc_cmd_receive_cb current ssm request: 9 state: 0 189s (process:2354): libfprint-SSM-DEBUG: 16:48:26.898: [fpcmoc] FP_CMD_NUM_STATES entering state 1 189s (process:2354): libfprint-DEBUG: 16:48:26.899: fpc_cmd_receive_cb current ssm request: 9 state: 1 189s (process:2354): libfprint-DEBUG: 16:48:26.899: fpc_cmd_receive_cb recv evt data length: 24 189s (process:2354): libfprint-DEBUG: 16:48:26.899: fpc_evt_cb Got capture event 189s (process:2354): libfprint-device-DEBUG: 16:48:26.899: Device reported finger status change: FP_FINGER_STATUS_NEEDED 189s (process:2354): libfprint-SSM-DEBUG: 16:48:26.899: [fpcmoc] enroll entering state 4 189s (process:2354): libfprint-SSM-DEBUG: 16:48:26.899: [fpcmoc] FP_CMD_NUM_STATES entering state 0 189s (process:2354): libfprint-DEBUG: 16:48:26.899: fpc_send_ctrl_cmd CMD: 0x68, value: 0x0, index: 0 type: 3 189s (process:2354): libfprint-SSM-DEBUG: 16:48:26.899: [fpcmoc] FP_CMD_NUM_STATES completed successfully 189s (process:2354): libfprint-DEBUG: 16:48:26.899: fpc_cmd_receive_cb current ssm request: 104 state: 0 189s (process:2354): libfprint-DEBUG: 16:48:26.899: Enrol Update status: 1, remaining: 2 189s (process:2354): libfprint-device-DEBUG: 16:48:26.899: Device reported enroll progress, reported 10 of 25 have been completed 189s (process:2354): libfprint-SSM-DEBUG: 16:48:26.899: [fpcmoc] enroll entering state 2 189s (process:2354): libfprint-SSM-DEBUG: 16:48:26.899: [fpcmoc] FP_CMD_NUM_STATES entering state 0 189s (process:2354): libfprint-DEBUG: 16:48:26.899: fpc_send_ctrl_cmd CMD: 0x2, value: 0x1, index: 0 type: 2 189s (process:2354): libfprint-SSM-DEBUG: 16:48:26.899: [fpcmoc] FP_CMD_NUM_STATES completed successfully 189s (process:2354): libfprint-DEBUG: 16:48:26.900: fpc_cmd_receive_cb current ssm request: 2 state: 0 189s (process:2354): libfprint-SSM-DEBUG: 16:48:26.900: [fpcmoc] FP_CMD_NUM_STATES entering state 1 189s (process:2354): libfprint-DEBUG: 16:48:26.900: fpc_cmd_receive_cb current ssm request: 2 state: 1 189s (process:2354): libfprint-DEBUG: 16:48:26.900: fpc_cmd_receive_cb recv evt data length: 12 189s (process:2354): libfprint-DEBUG: 16:48:26.900: fpc_evt_cb Got finger down event 189s (process:2354): libfprint-device-DEBUG: 16:48:26.900: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 189s (process:2354): libfprint-SSM-DEBUG: 16:48:26.900: [fpcmoc] enroll entering state 3 189s (process:2354): libfprint-SSM-DEBUG: 16:48:26.900: [fpcmoc] FP_CMD_NUM_STATES entering state 0 189s (process:2354): libfprint-DEBUG: 16:48:26.900: fpc_send_ctrl_cmd CMD: 0x9, value: 0x0, index: 0 type: 2 189s (process:2354): libfprint-SSM-DEBUG: 16:48:26.900: [fpcmoc] FP_CMD_NUM_STATES completed successfully 189s (process:2354): libfprint-DEBUG: 16:48:26.901: fpc_cmd_receive_cb current ssm request: 9 state: 0 189s (process:2354): libfprint-SSM-DEBUG: 16:48:26.901: [fpcmoc] FP_CMD_NUM_STATES entering state 1 189s (process:2354): libfprint-DEBUG: 16:48:26.901: fpc_cmd_receive_cb current ssm request: 9 state: 1 189s (process:2354): libfprint-DEBUG: 16:48:26.901: fpc_cmd_receive_cb recv evt data length: 24 189s (process:2354): libfprint-DEBUG: 16:48:26.901: fpc_evt_cb Got capture event 189s (process:2354): libfprint-device-DEBUG: 16:48:26.901: Device reported finger status change: FP_FINGER_STATUS_NEEDED 189s (process:2354): libfprint-SSM-DEBUG: 16:48:26.901: [fpcmoc] enroll entering state 4 189s (process:2354): libfprint-SSM-DEBUG: 16:48:26.901: [fpcmoc] FP_CMD_NUM_STATES entering state 0 189s (process:2354): libfprint-DEBUG: 16:48:26.901: fpc_send_ctrl_cmd CMD: 0x68, value: 0x0, index: 0 type: 3 189s (process:2354): libfprint-SSM-DEBUG: 16:48:26.901: [fpcmoc] FP_CMD_NUM_STATES completed successfully 189s (process:2354): libfprint-DEBUG: 16:48:26.902: fpc_cmd_receive_cb current ssm request: 104 state: 0 189s (process:2354): libfprint-DEBUG: 16:48:26.902: Enrol Update status: 5, remaining: 2 189s (process:2354): libfprint-DEBUG: 16:48:26.902: Sample overlapping ratio is too High 189s (process:2354): libfprint-device-DEBUG: 16:48:26.902: Device reported enroll progress, reported 10 of 25 have been completed 189s (process:2354): libfprint-SSM-DEBUG: 16:48:26.902: [fpcmoc] enroll entering state 2 189s (process:2354): libfprint-SSM-DEBUG: 16:48:26.902: [fpcmoc] FP_CMD_NUM_STATES entering state 0 189s (process:2354): libfprint-DEBUG: 16:48:26.902: fpc_send_ctrl_cmd CMD: 0x2, value: 0x1, index: 0 type: 2 189s (process:2354): libfprint-SSM-DEBUG: 16:48:26.902: [fpcmoc] FP_CMD_NUM_STATES completed successfully 189s (process:2354): libfprint-DEBUG: 16:48:26.902: fpc_cmd_receive_cb current ssm request: 2 state: 0 189s (process:2354): libfprint-SSM-DEBUG: 16:48:26.902: [fpcmoc] FP_CMD_NUM_STATES entering state 1 189s (process:2354): libfprint-DEBUG: 16:48:26.902: fpc_cmd_receive_cb current ssm request: 2 state: 1 189s (process:2354): libfprint-DEBUG: 16:48:26.902: fpc_cmd_receive_cb recv evt data length: 12 189s (process:2354): libfprint-DEBUG: 16:48:26.903: fpc_evt_cb Got finger down event 189s (process:2354): libfprint-device-DEBUG: 16:48:26.903: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 189s (process:2354): libfprint-SSM-DEBUG: 16:48:26.903: [fpcmoc] enroll entering state 3 189s (process:2354): libfprint-SSM-DEBUG: 16:48:26.903: [fpcmoc] FP_CMD_NUM_STATES entering state 0 189s (process:2354): libfprint-DEBUG: 16:48:26.903: fpc_send_ctrl_cmd CMD: 0x9, value: 0x0, index: 0 type: 2 189s (process:2354): libfprint-SSM-DEBUG: 16:48:26.903: [fpcmoc] FP_CMD_NUM_STATES completed successfully 189s (process:2354): libfprint-DEBUG: 16:48:26.903: fpc_cmd_receive_cb current ssm request: 9 state: 0 189s (process:2354): libfprint-SSM-DEBUG: 16:48:26.903: [fpcmoc] FP_CMD_NUM_STATES entering state 1 189s (process:2354): libfprint-DEBUG: 16:48:26.903: fpc_cmd_receive_cb current ssm request: 9 state: 1 189s (process:2354): libfprint-DEBUG: 16:48:26.903: fpc_cmd_receive_cb recv evt data length: 24 189s (process:2354): libfprint-DEBUG: 16:48:26.903: fpc_evt_cb Got capture event 189s (process:2354): libfprint-device-DEBUG: 16:48:26.903: Device reported finger status change: FP_FINGER_STATUS_NEEDED 189s (process:2354): libfprint-SSM-DEBUG: 16:48:26.903: [fpcmoc] enroll entering state 4 189s (process:2354): libfprint-SSM-DEBUG: 16:48:26.903: [fpcmoc] FP_CMD_NUM_STATES entering state 0 189s (process:2354): libfprint-DEBUG: 16:48:26.903: fpc_send_ctrl_cmd CMD: 0x68, value: 0x0, index: 0 type: 3 189s (process:2354): libfprint-SSM-DEBUG: 16:48:26.904: [fpcmoc] FP_CMD_NUM_STATES completed successfully 189s (process:2354): libfprint-DEBUG: 16:48:26.904: fpc_cmd_receive_cb current ssm request: 104 state: 0 189s (process:2354): libfprint-DEBUG: 16:48:26.904: Enrol Update status: 1, remaining: 1 189s (process:2354): libfprint-device-DEBUG: 16:48:26.904: Device reported enroll progress, reported 11 of 25 have been completed 189s (process:2354): libfprint-SSM-DEBUG: 16:48:26.904: [fpcmoc] enroll entering state 2 189s (process:2354): libfprint-SSM-DEBUG: 16:48:26.904: [fpcmoc] FP_CMD_NUM_STATES entering state 0 189s (process:2354): libfprint-DEBUG: 16:48:26.904: fpc_send_ctrl_cmd CMD: 0x2, value: 0x1, index: 0 type: 2 189s (process:2354): libfprint-SSM-DEBUG: 16:48:26.904: [fpcmoc] FP_CMD_NUM_STATES completed successfully 189s (process:2354): libfprint-DEBUG: 16:48:26.904: fpc_cmd_receive_cb current ssm request: 2 state: 0 189s (process:2354): libfprint-SSM-DEBUG: 16:48:26.904: [fpcmoc] FP_CMD_NUM_STATES entering state 1 189s (process:2354): libfprint-DEBUG: 16:48:26.905: fpc_cmd_receive_cb current ssm request: 2 state: 1 189s (process:2354): libfprint-DEBUG: 16:48:26.905: fpc_cmd_receive_cb recv evt data length: 12 189s (process:2354): libfprint-DEBUG: 16:48:26.905: fpc_evt_cb Got finger down event 189s (process:2354): libfprint-device-DEBUG: 16:48:26.905: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 189s (process:2354): libfprint-SSM-DEBUG: 16:48:26.905: [fpcmoc] enroll entering state 3 189s (process:2354): libfprint-SSM-DEBUG: 16:48:26.905: [fpcmoc] FP_CMD_NUM_STATES entering state 0 189s (process:2354): libfprint-DEBUG: 16:48:26.905: fpc_send_ctrl_cmd CMD: 0x9, value: 0x0, index: 0 type: 2 189s (process:2354): libfprint-SSM-DEBUG: 16:48:26.905: [fpcmoc] FP_CMD_NUM_STATES completed successfully 189s (process:2354): libfprint-DEBUG: 16:48:26.905: fpc_cmd_receive_cb current ssm request: 9 state: 0 189s (process:2354): libfprint-SSM-DEBUG: 16:48:26.905: [fpcmoc] FP_CMD_NUM_STATES entering state 1 189s (process:2354): libfprint-DEBUG: 16:48:26.906: fpc_cmd_receive_cb current ssm request: 9 state: 1 189s (process:2354): libfprint-DEBUG: 16:48:26.906: fpc_cmd_receive_cb recv evt data length: 24 189s (process:2354): libfprint-DEBUG: 16:48:26.906: fpc_evt_cb Got capture event 189s (process:2354): libfprint-device-DEBUG: 16:48:26.906: Device reported finger status change: FP_FINGER_STATUS_NEEDED 189s (process:2354): libfprint-SSM-DEBUG: 16:48:26.906: [fpcmoc] enroll entering state 4 189s (process:2354): libfprint-SSM-DEBUG: 16:48:26.906: [fpcmoc] FP_CMD_NUM_STATES entering state 0 189s (process:2354): libfprint-DEBUG: 16:48:26.906: fpc_send_ctrl_cmd CMD: 0x68, value: 0x0, index: 0 type: 3 189s (process:2354): libfprint-SSM-DEBUG: 16:48:26.906: [fpcmoc] FP_CMD_NUM_STATES completed successfully 189s (process:2354): libfprint-DEBUG: 16:48:26.906: fpc_cmd_receive_cb current ssm request: 104 state: 0 189s (process:2354): libfprint-DEBUG: 16:48:26.906: Enrol Update status: 0, remaining: 0 189s (process:2354): libfprint-device-DEBUG: 16:48:26.906: Device reported enroll progress, reported 12 of 25 have been completed 189s (process:2354): libfprint-SSM-DEBUG: 16:48:26.906: [fpcmoc] enroll entering state 5 189s (process:2354): libfprint-SSM-DEBUG: 16:48:26.906: [fpcmoc] FP_CMD_NUM_STATES entering state 0 189s (process:2354): libfprint-DEBUG: 16:48:26.906: fpc_send_ctrl_cmd CMD: 0x69, value: 0x0, index: 0 type: 3 189s (process:2354): libfprint-SSM-DEBUG: 16:48:26.906: [fpcmoc] FP_CMD_NUM_STATES completed successfully 189s (process:2354): libfprint-DEBUG: 16:48:26.907: fpc_cmd_receive_cb current ssm request: 105 state: 0 189s (process:2354): libfprint-DEBUG: 16:48:26.907: Enrol End status: 0, fid: 0x0 189s (process:2354): libfprint-SSM-DEBUG: 16:48:26.907: [fpcmoc] enroll entering state 6 189s (process:2354): libfprint-SSM-DEBUG: 16:48:26.907: [fpcmoc] FP_CMD_NUM_STATES entering state 0 189s (process:2354): libfprint-DEBUG: 16:48:26.907: fpc_send_ctrl_cmd CMD: 0x6b, value: 0x0, index: 0 type: 3 189s (process:2354): libfprint-SSM-DEBUG: 16:48:26.907: [fpcmoc] FP_CMD_NUM_STATES completed successfully 189s (process:2354): libfprint-DEBUG: 16:48:26.907: fpc_cmd_receive_cb current ssm request: 107 state: 0 189s (process:2354): libfprint-SSM-DEBUG: 16:48:26.907: [fpcmoc] enroll entering state 7 189s (process:2354): libfprint-DEBUG: 16:48:26.907: user_id: FP1-00000000-0-00000000-nobody, finger: 0xf5 189s (process:2354): libfprint-SSM-DEBUG: 16:48:26.907: [fpcmoc] FP_CMD_NUM_STATES entering state 0 189s (process:2354): libfprint-DEBUG: 16:48:26.907: fpc_send_ctrl_cmd CMD: 0x6a, value: 0x0, index: 0 type: 1 189s (process:2354): libfprint-SSM-DEBUG: 16:48:26.907: [fpcmoc] FP_CMD_NUM_STATES completed successfully 189s (process:2354): libfprint-DEBUG: 16:48:26.908: fpc_cmd_receive_cb current ssm request: 106 state: 0 189s (process:2354): libfprint-SSM-DEBUG: 16:48:26.908: [fpcmoc] enroll entering state 8 189s (process:2354): libfprint-SSM-DEBUG: 16:48:26.908: [fpcmoc] FP_CMD_NUM_STATES entering state 0 189s (process:2354): libfprint-DEBUG: 16:48:26.908: fpc_send_ctrl_cmd CMD: 0x61, value: 0x0, index: 0 type: 3 189s (process:2354): libfprint-SSM-DEBUG: 16:48:26.908: [fpcmoc] FP_CMD_NUM_STATES completed successfully 189s (process:2354): libfprint-DEBUG: 16:48:26.908: fpc_cmd_receive_cb current ssm request: 97 state: 0 189s (process:2354): libfprint-SSM-DEBUG: 16:48:26.908: [fpcmoc] enroll entering state 9 189s (process:2354): libfprint-SSM-DEBUG: 16:48:26.908: [fpcmoc] FP_CMD_NUM_STATES entering state 0 189s (process:2354): libfprint-DEBUG: 16:48:26.908: fpc_send_ctrl_cmd CMD: 0x3, value: 0x1, index: 0 type: 1 189s (process:2354): libfprint-SSM-DEBUG: 16:48:26.908: [fpcmoc] FP_CMD_NUM_STATES completed successfully 189s (process:2354): libfprint-DEBUG: 16:48:26.909: fpc_cmd_receive_cb current ssm request: 3 state: 0 189s (process:2354): libfprint-DEBUG: 16:48:26.909: fpc_do_abort_cb Do abort for reasons 189s (process:2354): libfprint-SSM-DEBUG: 16:48:26.909: [fpcmoc] enroll entering state 10 189s (process:2354): libfprint-SSM-DEBUG: 16:48:26.909: [fpcmoc] enroll completed successfully 189s (process:2354): libfprint-DEBUG: 16:48:26.909: Enrollment complete! 189s (process:2354): libfprint-device-DEBUG: 16:48:26.909: Device reported enroll completion 189s (process:2354): libfprint-device-DEBUG: 16:48:26.909: Device reported finger status change: FP_FINGER_STATUS_NONE 189s (process:2354): libfprint-device-DEBUG: 16:48:26.909: Print for finger FP_FINGER_UNKNOWN enrolled 189s (process:2354): libfprint-SSM-DEBUG: 16:48:26.909: [fpcmoc] FP_CMD_NUM_STATES completed successfully 189s (process:2354): libfprint-device-DEBUG: 16:48:26.909: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 189s (process:2354): libfprint-device-DEBUG: 16:48:26.909: Not updating temperature model, device can run continuously! 189s (process:2354): libfprint-DEBUG: 16:48:26.909: fpc_dev_template_list enter --> 189s (process:2354): libfprint-SSM-DEBUG: 16:48:26.909: [fpcmoc] FP_CMD_NUM_STATES entering state 0 189s (process:2354): libfprint-DEBUG: 16:48:26.909: fpc_send_ctrl_cmd CMD: 0x70, value: 0x0, index: 0 type: 2 189s (process:2354): libfprint-DEBUG: 16:48:26.909: fpc_cmd_receive_cb current ssm request: 112 state: 0 189s (process:2354): libfprint-SSM-DEBUG: 16:48:26.909: [fpcmoc] FP_CMD_NUM_STATES entering state 1 189s (process:2354): libfprint-DEBUG: 16:48:26.910: fpc_cmd_receive_cb current ssm request: 112 state: 1 189s (process:2354): libfprint-DEBUG: 16:48:26.910: fpc_cmd_receive_cb recv evt data length: 790 189s (process:2354): libfprint-DEBUG: 16:48:26.910: Query templates complete! 189s (process:2354): libfprint-device-DEBUG: 16:48:26.910: Device reported listing completion 189s (process:2354): libfprint-SSM-DEBUG: 16:48:26.910: [fpcmoc] FP_CMD_NUM_STATES completed successfully 189s (process:2354): libfprint-device-DEBUG: 16:48:26.910: Completing action FPI_DEVICE_ACTION_LIST in idle! 189s (process:2354): libfprint-device-DEBUG: 16:48:26.910: Not updating temperature model, device can run continuously! 189s (process:2354): libfprint-device-DEBUG: 16:48:26.910: Not updating temperature model, device can run continuously! 189s (process:2354): libfprint-DEBUG: 16:48:26.910: fpc_dev_verify_identify enter --> 189s (process:2354): libfprint-SSM-DEBUG: 16:48:26.910: [fpcmoc] verify_identify entering state 0 189s (process:2354): libfprint-device-DEBUG: 16:48:26.910: Device reported finger status change: FP_FINGER_STATUS_NEEDED 189s (process:2354): libfprint-SSM-DEBUG: 16:48:26.910: [fpcmoc] FP_CMD_NUM_STATES entering state 0 189s (process:2354): libfprint-DEBUG: 16:48:26.910: fpc_send_ctrl_cmd CMD: 0x2, value: 0x1, index: 0 type: 2 189s (process:2354): libfprint-DEBUG: 16:48:26.910: fpc_cmd_receive_cb current ssm request: 2 state: 0 189s (process:2354): libfprint-SSM-DEBUG: 16:48:26.910: [fpcmoc] FP_CMD_NUM_STATES entering state 1 189s (process:2354): libfprint-DEBUG: 16:48:26.911: fpc_cmd_receive_cb current ssm request: 2 state: 1 189s (process:2354): libfprint-DEBUG: 16:48:26.911: fpc_cmd_receive_cb recv evt data length: 12 189s (process:2354): libfprint-DEBUG: 16:48:26.911: fpc_evt_cb Got finger down event 189s (process:2354): libfprint-device-DEBUG: 16:48:26.911: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 189s (process:2354): libfprint-SSM-DEBUG: 16:48:26.911: [fpcmoc] verify_identify entering state 1 189s (process:2354): libfprint-SSM-DEBUG: 16:48:26.911: [fpcmoc] FP_CMD_NUM_STATES entering state 0 189s (process:2354): libfprint-DEBUG: 16:48:26.911: fpc_send_ctrl_cmd CMD: 0x9, value: 0x0, index: 0 type: 2 189s (process:2354): libfprint-SSM-DEBUG: 16:48:26.911: [fpcmoc] FP_CMD_NUM_STATES completed successfully 189s (process:2354): libfprint-DEBUG: 16:48:26.911: fpc_cmd_receive_cb current ssm request: 9 state: 0 189s (process:2354): libfprint-SSM-DEBUG: 16:48:26.911: [fpcmoc] FP_CMD_NUM_STATES entering state 1 189s (process:2354): libfprint-DEBUG: 16:48:26.912: fpc_cmd_receive_cb current ssm request: 9 state: 1 189s (process:2354): libfprint-DEBUG: 16:48:26.912: fpc_cmd_receive_cb recv evt data length: 24 189s (process:2354): libfprint-DEBUG: 16:48:26.912: fpc_evt_cb Got capture event 189s (process:2354): libfprint-device-DEBUG: 16:48:26.912: Device reported finger status change: FP_FINGER_STATUS_NEEDED 189s (process:2354): libfprint-SSM-DEBUG: 16:48:26.912: [fpcmoc] verify_identify entering state 2 189s (process:2354): libfprint-SSM-DEBUG: 16:48:26.912: [fpcmoc] FP_CMD_NUM_STATES entering state 0 189s (process:2354): libfprint-DEBUG: 16:48:26.912: fpc_send_ctrl_cmd CMD: 0x6b, value: 0x0, index: 0 type: 3 189s (process:2354): libfprint-SSM-DEBUG: 16:48:26.912: [fpcmoc] FP_CMD_NUM_STATES completed successfully 189s (process:2354): libfprint-DEBUG: 16:48:26.912: fpc_cmd_receive_cb current ssm request: 107 state: 0 189s (process:2354): libfprint-device-DEBUG: 16:48:26.912: Device reported verify result 189s (process:2354): libfprint-SSM-DEBUG: 16:48:26.912: [fpcmoc] verify_identify entering state 3 189s (process:2354): libfprint-SSM-DEBUG: 16:48:26.912: [fpcmoc] FP_CMD_NUM_STATES entering state 0 189s (process:2354): libfprint-DEBUG: 16:48:26.912: fpc_send_ctrl_cmd CMD: 0x3, value: 0x1, index: 0 type: 1 189s (process:2354): libfprint-SSM-DEBUG: 16:48:26.913: [fpcmoc] FP_CMD_NUM_STATES completed successfully 189s (process:2354): libfprint-DEBUG: 16:48:26.913: fpc_cmd_receive_cb current ssm request: 3 state: 0 189s (process:2354): libfprint-DEBUG: 16:48:26.913: fpc_do_abort_cb Do abort for reasons 189s (process:2354): libfprint-SSM-DEBUG: 16:48:26.913: [fpcmoc] verify_identify completed successfully 189s (process:2354): libfprint-DEBUG: 16:48:26.913: Verify_identify complete! 189s (process:2354): libfprint-device-DEBUG: 16:48:26.913: Device reported verify completion 189s (process:2354): libfprint-device-DEBUG: 16:48:26.913: Device reported finger status change: FP_FINGER_STATUS_NONE 189s (process:2354): libfprint-SSM-DEBUG: 16:48:26.913: [fpcmoc] FP_CMD_NUM_STATES completed successfully 189s (process:2354): libfprint-device-DEBUG: 16:48:26.913: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 189s (process:2354): libfprint-device-DEBUG: 16:48:26.913: Not updating temperature model, device can run continuously! 189s (process:2354): libfprint-device-DEBUG: 16:48:26.913: Not updating temperature model, device can run continuously! 189s (process:2354): libfprint-DEBUG: 16:48:26.913: fpc_dev_verify_identify enter --> 189s (process:2354): libfprint-SSM-DEBUG: 16:48:26.913: [fpcmoc] verify_identify entering state 0 189s (process:2354): libfprint-device-DEBUG: 16:48:26.913: Device reported finger status change: FP_FINGER_STATUS_NEEDED 189s (process:2354): libfprint-SSM-DEBUG: 16:48:26.913: [fpcmoc] FP_CMD_NUM_STATES entering state 0 189s (process:2354): libfprint-DEBUG: 16:48:26.913: fpc_send_ctrl_cmd CMD: 0x2, value: 0x1, index: 0 type: 2 189s (process:2354): libfprint-DEBUG: 16:48:26.914: fpc_cmd_receive_cb current ssm request: 2 state: 0 189s (process:2354): libfprint-SSM-DEBUG: 16:48:26.914: [fpcmoc] FP_CMD_NUM_STATES entering state 1 189s (process:2354): libfprint-DEBUG: 16:48:26.914: fpc_cmd_receive_cb current ssm request: 2 state: 1 189s (process:2354): libfprint-DEBUG: 16:48:26.914: fpc_cmd_receive_cb recv evt data length: 12 189s (process:2354): libfprint-DEBUG: 16:48:26.914: fpc_evt_cb Got finger down event 189s (process:2354): libfprint-device-DEBUG: 16:48:26.914: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 189s (process:2354): libfprint-SSM-DEBUG: 16:48:26.914: [fpcmoc] verify_identify entering state 1 189s (process:2354): libfprint-SSM-DEBUG: 16:48:26.914: [fpcmoc] FP_CMD_NUM_STATES entering state 0 189s (process:2354): libfprint-DEBUG: 16:48:26.914: fpc_send_ctrl_cmd CMD: 0x9, value: 0x0, index: 0 type: 2 189s (process:2354): libfprint-SSM-DEBUG: 16:48:26.915: [fpcmoc] FP_CMD_NUM_STATES completed successfully 189s (process:2354): libfprint-DEBUG: 16:48:26.915: fpc_cmd_receive_cb current ssm request: 9 state: 0 189s (process:2354): libfprint-SSM-DEBUG: 16:48:26.915: [fpcmoc] FP_CMD_NUM_STATES entering state 1 189s (process:2354): libfprint-DEBUG: 16:48:26.915: fpc_cmd_receive_cb current ssm request: 9 state: 1 189s (process:2354): libfprint-DEBUG: 16:48:26.915: fpc_cmd_receive_cb recv evt data length: 24 189s (process:2354): libfprint-DEBUG: 16:48:26.915: fpc_evt_cb Got capture event 189s (process:2354): libfprint-device-DEBUG: 16:48:26.915: Device reported finger status change: FP_FINGER_STATUS_NEEDED 189s (process:2354): libfprint-SSM-DEBUG: 16:48:26.915: [fpcmoc] verify_identify entering state 2 189s (process:2354): libfprint-SSM-DEBUG: 16:48:26.915: [fpcmoc] FP_CMD_NUM_STATES entering state 0 189s (process:2354): libfprint-DEBUG: 16:48:26.915: fpc_send_ctrl_cmd CMD: 0x6b, value: 0x0, index: 0 type: 3 189s (process:2354): libfprint-SSM-DEBUG: 16:48:26.916: [fpcmoc] FP_CMD_NUM_STATES completed successfully 189s (process:2354): libfprint-DEBUG: 16:48:26.916: fpc_cmd_receive_cb current ssm request: 107 state: 0 189s (process:2354): libfprint-device-DEBUG: 16:48:26.916: Device reported identify result 189s (process:2354): libfprint-SSM-DEBUG: 16:48:26.916: [fpcmoc] verify_identify entering state 3 189s (process:2354): libfprint-SSM-DEBUG: 16:48:26.916: [fpcmoc] FP_CMD_NUM_STATES entering state 0 189s (process:2354): libfprint-DEBUG: 16:48:26.916: fpc_send_ctrl_cmd CMD: 0x3, value: 0x1, index: 0 type: 1 189s (process:2354): libfprint-SSM-DEBUG: 16:48:26.916: [fpcmoc] FP_CMD_NUM_STATES completed successfully 189s (process:2354): libfprint-DEBUG: 16:48:26.916: fpc_cmd_receive_cb current ssm request: 3 state: 0 189s (process:2354): libfprint-DEBUG: 16:48:26.916: fpc_do_abort_cb Do abort for reasons 189s (process:2354): libfprint-SSM-DEBUG: 16:48:26.916: [fpcmoc] verify_identify completed successfully 189s (process:2354): libfprint-DEBUG: 16:48:26.916: Verify_identify complete! 189s (process:2354): libfprint-device-DEBUG: 16:48:26.916: Device reported identify completion 189s (process:2354): libfprint-device-DEBUG: 16:48:26.916: Device reported finger status change: FP_FINGER_STATUS_NONE 189s (process:2354): libfprint-SSM-DEBUG: 16:48:26.916: [fpcmoc] FP_CMD_NUM_STATES completed successfully 189s (process:2354): libfprint-device-DEBUG: 16:48:26.916: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 189s (process:2354): libfprint-device-DEBUG: 16:48:26.916: Not updating temperature model, device can run continuously! 189s (process:2354): libfprint-DEBUG: 16:48:26.917: fpc_dev_template_delete enter --> 189s (process:2354): libfprint-SSM-DEBUG: 16:48:26.917: [fpcmoc] FP_CMD_NUM_STATES entering state 0 189s (process:2354): libfprint-DEBUG: 16:48:26.917: fpc_send_ctrl_cmd CMD: 0x63, value: 0x0, index: 0 type: 1 189s (process:2354): libfprint-DEBUG: 16:48:26.917: fpc_dev_template_delete exit <-- 189s (process:2354): libfprint-DEBUG: 16:48:26.917: fpc_cmd_receive_cb current ssm request: 99 state: 0 189s (process:2354): libfprint-device-DEBUG: 16:48:26.917: Device reported deletion completion 189s (process:2354): libfprint-SSM-DEBUG: 16:48:26.917: [fpcmoc] FP_CMD_NUM_STATES completed successfully 189s (process:2354): libfprint-device-DEBUG: 16:48:26.917: Completing action FPI_DEVICE_ACTION_DELETE in idle! 189s (process:2354): libfprint-device-DEBUG: 16:48:26.917: Not updating temperature model, device can run continuously! 189s (process:2354): libfprint-DEBUG: 16:48:26.917: fpc_dev_close enter --> 189s (process:2354): libfprint-device-DEBUG: 16:48:26.918: Device reported close completion 189s (process:2354): libfprint-device-DEBUG: 16:48:26.918: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 189s (process:2354): libfprint-device-DEBUG: 16:48:26.918: Not updating temperature model, device can run continuously! 189s Clear 189s Clear done 189s enrolling 189s enroll progress: (<__gi__.FpiDeviceFpcMoc object at 0xee9996a33580 (FpiDeviceFpcMoc at 0x383f1c20)>, 1, None, None, None) 189s enroll progress: (<__gi__.FpiDeviceFpcMoc object at 0xee9996a33580 (FpiDeviceFpcMoc at 0x383f1c20)>, 2, None, None, None) 189s enroll progress: (<__gi__.FpiDeviceFpcMoc object at 0xee9996a33580 (FpiDeviceFpcMoc at 0x383f1c20)>, 3, None, None, None) 189s enroll progress: (<__gi__.FpiDeviceFpcMoc object at 0xee9996a33580 (FpiDeviceFpcMoc at 0x383f1c20)>, 4, None, None, None) 189s enroll progress: (<__gi__.FpiDeviceFpcMoc object at 0xee9996a33580 (FpiDeviceFpcMoc at 0x383f1c20)>, 5, None, None, None) 189s enroll progress: (<__gi__.FpiDeviceFpcMoc object at 0xee9996a33580 (FpiDeviceFpcMoc at 0x383f1c20)>, 5, None, None, GLib.Error('Please try again after removing the finger first.', 'fp - device - retry - quark', 3)) 189s enroll progress: (<__gi__.FpiDeviceFpcMoc object at 0xee9996a33580 (FpiDeviceFpcMoc at 0x383f1c20)>, 6, None, None, None) 189s enroll progress: (<__gi__.FpiDeviceFpcMoc object at 0xee9996a33580 (FpiDeviceFpcMoc at 0x383f1c20)>, 7, None, None, None) 189s enroll progress: (<__gi__.FpiDeviceFpcMoc object at 0xee9996a33580 (FpiDeviceFpcMoc at 0x383f1c20)>, 7, None, None, GLib.Error('Please try again after removing the finger first.', 'fp - device - retry - quark', 3)) 189s enroll progress: (<__gi__.FpiDeviceFpcMoc object at 0xee9996a33580 (FpiDeviceFpcMoc at 0x383f1c20)>, 8, None, None, None) 189s enroll progress: (<__gi__.FpiDeviceFpcMoc object at 0xee9996a33580 (FpiDeviceFpcMoc at 0x383f1c20)>, 9, None, None, None) 189s enroll progress: (<__gi__.FpiDeviceFpcMoc object at 0xee9996a33580 (FpiDeviceFpcMoc at 0x383f1c20)>, 10, None, None, None) 189s enroll progress: (<__gi__.FpiDeviceFpcMoc object at 0xee9996a33580 (FpiDeviceFpcMoc at 0x383f1c20)>, 10, None, None, GLib.Error('Please try again after removing the finger first.', 'fp - device - retry - quark', 3)) 189s enroll progress: (<__gi__.FpiDeviceFpcMoc object at 0xee9996a33580 (FpiDeviceFpcMoc at 0x383f1c20)>, 11, None, None, None) 189s enroll progress: (<__gi__.FpiDeviceFpcMoc object at 0xee9996a33580 (FpiDeviceFpcMoc at 0x383f1c20)>, 12, None, None, None) 189s enroll done 189s listing 189s listing done 189s verifying 189s verify done 189s async identifying 189s indentification_done: 189s deleting 189s delete done 189s ** (umockdev-run:2350): DEBUG: 16:48:26.930: umockdev.vala:150: Removing test bed /tmp/umockdev.HNXWJ2 189s (umockdev-run:2350): GLib-DEBUG: 16:48:26.934: unsetenv() is not thread-safe and should not be used after threads are created 189s PASS: libfprint-2/driver-fpcmoc.test 189s Running test: libfprint-2/fpi-device.test 189s TAP version 13 189s # random seed: R02S98c6c672b8300ed0e2b07ca418fe7eca 189s 1..97 189s # Start of driver tests 189s ok 1 /driver/get_driver 189s ok 2 /driver/get_device_id 189s ok 3 /driver/get_name 189s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 189s # 189s # libfprint-device-DEBUG: Device reported open completion 189s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 189s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 189s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 189s # 189s # libfprint-device-DEBUG: Device reported close completion 189s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 189s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 189s ok 4 /driver/is_open 189s ok 5 /driver/get_nr_enroll_stages 189s ok 6 /driver/set_nr_enroll_stages 189s ok 7 /driver/supports_identify 189s ok 8 /driver/supports_capture 189s ok 9 /driver/has_storage 189s ok 10 /driver/do_not_support_identify 189s ok 11 /driver/do_not_support_capture 189s ok 12 /driver/has_not_storage 189s ok 13 /driver/get_usb_device 189s ok 14 /driver/get_virtual_env 189s ok 15 /driver/get_driver_data 189s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_probe: Device Virtual device for debugging in action FPI_DEVICE_ACTION_PROBE 189s # 189s # libfprint-device-DEBUG: Device reported probe completion 189s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 189s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 189s ok 16 /driver/initial_features 189s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_probe: Device Probed device name in action FPI_DEVICE_ACTION_PROBE 189s # 189s # libfprint-device-DEBUG: Device reported probe completion 189s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 189s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 189s ok 17 /driver/probe 189s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 189s # 189s # libfprint-device-DEBUG: Device reported open completion 189s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 189s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 189s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 189s # 189s # libfprint-device-DEBUG: Device reported close completion 189s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 189s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 189s ok 18 /driver/open 189s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 189s # 189s # libfprint-device-DEBUG: Device reported open completion 189s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 189s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 189s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 189s # 189s # libfprint-device-DEBUG: Device reported close completion 189s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 189s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 189s ok 19 /driver/close 189s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 189s # 189s # libfprint-device-DEBUG: Device reported open completion 189s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 189s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 189s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 189s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_enroll: Device Virtual device for debugging in action FPI_DEVICE_ACTION_ENROLL 189s # 189s # libfprint-device-DEBUG: Device reported enroll completion 189s # libfprint-device-DEBUG: Print for finger FP_FINGER_UNKNOWN enrolled 189s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 189s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 189s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 189s # 189s # libfprint-device-DEBUG: Device reported close completion 189s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 189s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 189s ok 20 /driver/enroll 189s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 189s # 189s # libfprint-device-DEBUG: Device reported open completion 189s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 189s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 189s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 189s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_verify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_VERIFY 189s # 189s # libfprint-device-DEBUG: Device reported verify result 189s # libfprint-device-DEBUG: Device reported verify completion 189s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 189s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 189s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 189s # 189s # libfprint-device-DEBUG: Device reported close completion 189s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 189s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 189s ok 21 /driver/verify 189s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 189s # 189s # libfprint-device-DEBUG: Device reported open completion 189s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 189s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 189s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 189s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_identify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY 189s # 189s # libfprint-device-DEBUG: Device reported identify result 190s # libfprint-device-DEBUG: Device reported identify completion 190s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 190s # libfprint-device-DEBUG: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 190s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 190s # 190s # libfprint-device-DEBUG: Device reported close completion 190s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 190s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 190s ok 22 /driver/identify 190s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 190s # 190s # libfprint-device-DEBUG: Device reported open completion 190s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 190s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 190s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 190s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_capture: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CAPTURE 190s # 190s # libfprint-device-DEBUG: Device reported capture completion 190s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CAPTURE in idle! 190s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 190s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 190s # 190s # libfprint-device-DEBUG: Device reported close completion 190s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 190s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 190s ok 23 /driver/capture 190s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 190s # 190s # libfprint-device-DEBUG: Device reported open completion 190s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 190s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 190s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_list: Device Virtual device for debugging in action FPI_DEVICE_ACTION_LIST 190s # 190s # libfprint-device-DEBUG: Device reported listing completion 190s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_LIST in idle! 190s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 190s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 190s # 190s # libfprint-device-DEBUG: Device reported close completion 190s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 190s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 190s ok 24 /driver/list 190s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 190s # 190s # libfprint-device-DEBUG: Device reported open completion 190s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 190s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 190s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_delete: Device Virtual device for debugging in action FPI_DEVICE_ACTION_DELETE 190s # 190s # libfprint-device-DEBUG: Device reported deletion completion 190s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_DELETE in idle! 190s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 190s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 190s # 190s # libfprint-device-DEBUG: Device reported close completion 190s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 190s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 190s ok 25 /driver/delete 190s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 190s # 190s # libfprint-device-DEBUG: Device reported open completion 190s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 190s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 190s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_clear_storage: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLEAR_STORAGE 190s # 190s # libfprint-device-DEBUG: Device reported deletion completion 190s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 190s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 190s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 190s # 190s # libfprint-device-DEBUG: Device reported close completion 190s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 190s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 190s ok 26 /driver/clear_storage 190s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 190s # 190s # libfprint-device-DEBUG: Device reported open completion 190s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 190s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 190s # libfprint-device-DEBUG: Idle cancelling on ongoing operation! 190s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_cancel: Device Virtual device for debugging in action FPI_DEVICE_ACTION_DELETE 190s # 190s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_delete: Device Virtual device for debugging in action FPI_DEVICE_ACTION_DELETE 190s # 190s # libfprint-device-DEBUG: Device reported deletion completion 190s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_DELETE in idle! 190s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 190s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 190s # 190s # libfprint-device-DEBUG: Device reported close completion 190s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 190s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 190s ok 27 /driver/cancel 190s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 190s # 190s # libfprint-device-DEBUG: Device reported open completion 190s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 190s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 190s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 190s # libfprint-device-DEBUG: Idle cancelling on ongoing operation! 190s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_cancel: Device Virtual device for debugging in action FPI_DEVICE_ACTION_VERIFY 190s # 190s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_suspend: Device Virtual device for debugging in action FPI_DEVICE_ACTION_VERIFY 190s # 190s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_resume: Device Virtual device for debugging in action FPI_DEVICE_ACTION_VERIFY 190s # 190s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_verify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_VERIFY 190s # 190s # libfprint-device-DEBUG: Device reported verify result 190s # libfprint-device-DEBUG: Device reported verify completion 190s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 190s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 190s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 190s # 190s # libfprint-device-DEBUG: Device reported close completion 190s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 190s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 190s ok 28 /driver/critical 190s ok 29 /driver/get_current_action 190s ok 30 /driver/timeout 190s ok 31 /driver/error_types 190s ok 32 /driver/retry_error_types 190s # Start of get_scan_type tests 190s ok 33 /driver/get_scan_type/press 190s ok 34 /driver/get_scan_type/swipe 190s # End of get_scan_type tests 190s # Start of set_scan_type tests 190s ok 35 /driver/set_scan_type/press 190s ok 36 /driver/set_scan_type/swipe 190s # End of set_scan_type tests 190s # Start of finger_status tests 190s ok 37 /driver/finger_status/inactive 190s # libfprint-device-DEBUG: Device reported finger status change: FP_FINGER_STATUS_NEEDED 190s ok 38 /driver/finger_status/waiting 190s # libfprint-device-DEBUG: Device reported finger status change: FP_FINGER_STATUS_PRESENT 190s ok 39 /driver/finger_status/present 190s # libfprint-device-DEBUG: Device reported finger status change: FP_FINGER_STATUS_NEEDED 190s # libfprint-device-DEBUG: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 190s # libfprint-device-DEBUG: Device reported finger status change: FP_FINGER_STATUS_PRESENT 190s # libfprint-device-DEBUG: Device reported finger status change: FP_FINGER_STATUS_NONE 190s ok 40 /driver/finger_status/changes 190s # End of finger_status tests 190s # Start of features tests 190s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_probe: Device Virtual device for debugging in action FPI_DEVICE_ACTION_PROBE 190s # 190s # libfprint-device-DEBUG: Device reported probe completion 190s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 190s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 190s ok 41 /driver/features/probe_updates 190s # End of features tests 190s # Start of initial_features tests 190s ok 42 /driver/initial_features/none 190s ok 43 /driver/initial_features/no_capture 190s ok 44 /driver/initial_features/no_verify 190s ok 45 /driver/initial_features/no_identify 190s ok 46 /driver/initial_features/no_storage 190s ok 47 /driver/initial_features/no_list 190s ok 48 /driver/initial_features/no_delete 190s ok 49 /driver/initial_features/no_clear 190s # End of initial_features tests 190s # Start of probe tests 190s # libfprint-device-DEBUG: Device reported probe completion 190s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 190s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 190s ok 50 /driver/probe/error 190s # libfprint-device-DEBUG: Device reported generic error (The operation is not supported on this device!) during action; action was: FPI_DEVICE_ACTION_PROBE 190s # libfprint-device-DEBUG: Device reported probe completion 190s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 190s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 190s ok 51 /driver/probe/action_error 190s # End of probe tests 190s # Start of open tests 190s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 190s # 190s # libfprint-device-DEBUG: Device reported open completion 190s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 190s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 190s ok 52 /driver/open/error 190s # End of open tests 190s # Start of close tests 190s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 190s # 190s # libfprint-device-DEBUG: Device reported open completion 190s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 190s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 190s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 190s # 190s # libfprint-device-DEBUG: Device reported close completion 190s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 190s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 190s ok 53 /driver/close/error 190s # End of close tests 190s # Start of enroll tests 190s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 190s # 190s # libfprint-device-DEBUG: Device reported open completion 190s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 190s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 190s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 190s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_enroll: Device Virtual device for debugging in action FPI_DEVICE_ACTION_ENROLL 190s # 190s # libfprint-device-DEBUG: Device reported enroll completion 190s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 190s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 190s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 190s # 190s # libfprint-device-DEBUG: Device reported close completion 190s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 190s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 190s ok 54 /driver/enroll/error 190s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 190s # 190s # libfprint-device-DEBUG: Device reported open completion 190s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 190s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 190s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 190s # libfprint-device-DEBUG: Device reported enroll progress, reported 1164526278 of 852152150 have been completed 190s # libfprint-device-DEBUG: Device reported enroll progress, reported 1385470031 of 852152150 have been completed 190s # libfprint-device-DEBUG: Device reported enroll progress, reported 1340301211 of 852152150 have been completed 190s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_enroll: Device Virtual device for debugging in action FPI_DEVICE_ACTION_ENROLL 190s # 190s # libfprint-device-DEBUG: Device reported enroll completion 190s # libfprint-device-DEBUG: Print for finger FP_FINGER_UNKNOWN enrolled 190s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 190s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 190s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 190s # 190s # libfprint-device-DEBUG: Device reported close completion 190s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 190s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 190s ok 55 /driver/enroll/progress 190s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 190s # 190s # libfprint-device-DEBUG: Device reported open completion 190s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 190s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 190s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 190s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_enroll: Device Virtual device for debugging in action FPI_DEVICE_ACTION_ENROLL 190s # 190s # libfprint-device-DEBUG: Device reported enroll completion 190s # libfprint-device-DEBUG: Print for finger FP_FINGER_UNKNOWN enrolled 190s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 190s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 190s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 190s # 190s # libfprint-device-DEBUG: Device reported close completion 190s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 190s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 190s ok 56 /driver/enroll/update_nbis 190s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 190s # 190s # libfprint-device-DEBUG: Device reported open completion 190s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 190s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 190s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 190s # 190s # libfprint-device-DEBUG: Device reported close completion 190s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 190s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 190s ok 57 /driver/enroll/update_nbis_wrong_device 190s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 190s # 190s # libfprint-device-DEBUG: Device reported open completion 190s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 190s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 190s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 190s # 190s # libfprint-device-DEBUG: Device reported close completion 190s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 190s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 190s ok 58 /driver/enroll/update_nbis_wrong_driver 190s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 190s # 190s # libfprint-device-DEBUG: Device reported open completion 190s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 190s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 190s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 190s # 190s # libfprint-device-DEBUG: Device reported close completion 190s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 190s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 190s ok 59 /driver/enroll/update_nbis_missing_feature 190s # Start of error tests 190s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 190s # 190s # libfprint-device-DEBUG: Device reported open completion 190s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 190s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 190s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 190s # libfprint-device-DEBUG: Device reported enroll completion 190s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 190s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 190s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 190s # libfprint-device-DEBUG: Device reported enroll completion 190s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 190s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 190s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 190s # libfprint-device-DEBUG: Device reported enroll completion 190s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 190s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 190s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 190s # 190s # libfprint-device-DEBUG: Device reported close completion 190s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 190s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 190s ok 60 /driver/enroll/error/no_print 190s # End of error tests 190s # End of enroll tests 190s # Start of verify tests 190s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 190s # 190s # libfprint-device-DEBUG: Device reported open completion 190s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 190s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 190s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 190s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_verify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_VERIFY 190s # 190s # libfprint-device-DEBUG: Device reported verify result 190s # libfprint-device-DEBUG: Device reported verify completion 190s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 190s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 190s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 190s # 190s # libfprint-device-DEBUG: Device reported close completion 190s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 190s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 190s ok 61 /driver/verify/fail 190s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 190s # 190s # libfprint-device-DEBUG: Device reported open completion 190s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 190s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 190s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 190s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_verify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_VERIFY 190s # 190s # libfprint-device-DEBUG: Device reported verify result 190s # libfprint-device-DEBUG: Device reported verify completion 190s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 190s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 190s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 190s # 190s # libfprint-device-DEBUG: Device reported close completion 190s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 190s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 190s ok 62 /driver/verify/retry 190s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 190s # 190s # libfprint-device-DEBUG: Device reported open completion 190s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 190s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 190s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 190s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_verify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_VERIFY 190s # 190s # libfprint-device-DEBUG: Device reported verify completion 190s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 190s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 190s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 190s # 190s # libfprint-device-DEBUG: Device reported close completion 190s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 190s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 190s ok 63 /driver/verify/error 190s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 190s # 190s # libfprint-device-DEBUG: Device reported open completion 190s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 190s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 190s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 190s # 190s # libfprint-device-DEBUG: Device reported close completion 190s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 190s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 190s ok 64 /driver/verify/not_supported 190s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 190s # 190s # libfprint-device-DEBUG: Device reported open completion 190s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 190s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 190s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 190s # libfprint-device-DEBUG: Device reported verify result 190s # libfprint-device-DEBUG: Device reported verify completion 190s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 190s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 190s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 190s # 190s # libfprint-device-DEBUG: Device reported close completion 190s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 190s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 190s ok 65 /driver/verify/report_no_cb 190s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 190s # 190s # libfprint-device-DEBUG: Device reported open completion 190s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 190s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 190s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 190s # libfprint-device-DEBUG: Device reported verify completion 190s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 190s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 190s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 190s # 190s # libfprint-device-DEBUG: Device reported close completion 190s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 190s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 190s ok 66 /driver/verify/not_reported 190s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 190s # 190s # libfprint-device-DEBUG: Device reported open completion 190s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 190s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 190s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 190s # libfprint-device-DEBUG: Device reported verify result 190s # libfprint-device-DEBUG: Device reported verify completion 190s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 190s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 190s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 190s # libfprint-device-DEBUG: Device reported verify result 190s # libfprint-device-DEBUG: Device reported verify completion 190s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 190s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 190s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 190s # libfprint-device-DEBUG: Device reported verify result 190s # libfprint-device-DEBUG: Device reported verify completion 190s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 190s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 190s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 190s # libfprint-device-DEBUG: Device reported verify result 190s # libfprint-device-DEBUG: Device reported verify completion 190s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 190s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 190s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 190s # libfprint-device-DEBUG: Device reported verify result 190s # libfprint-device-DEBUG: Device reported verify completion 190s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 190s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 190s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 190s # 190s # libfprint-device-DEBUG: Device reported close completion 190s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 190s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 190s ok 67 /driver/verify/complete_retry 190s # End of verify tests 190s # Start of identify tests 190s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 190s # 190s # libfprint-device-DEBUG: Device reported open completion 190s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 190s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 190s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 190s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_identify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY 190s # 190s # libfprint-device-DEBUG: Device reported identify result 190s # libfprint-device-DEBUG: Device reported identify completion 190s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 190s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 190s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 190s # 190s # libfprint-device-DEBUG: Device reported close completion 190s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 190s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_COLD 190s ok 68 /driver/identify/fail 190s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 190s # 190s # libfprint-device-DEBUG: Device reported open completion 190s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 190s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 190s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 190s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_identify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY 190s # 190s # libfprint-device-DEBUG: Device reported identify result 190s # libfprint-device-DEBUG: Device reported identify completion 190s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 190s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 190s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 190s # 190s # libfprint-device-DEBUG: Device reported close completion 190s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 190s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 190s ok 69 /driver/identify/retry 190s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 190s # 190s # libfprint-device-DEBUG: Device reported open completion 190s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 190s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 190s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 190s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_identify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY 190s # 190s # libfprint-device-DEBUG: Device reported identify completion 190s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 190s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 190s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 190s # 190s # libfprint-device-DEBUG: Device reported close completion 190s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 190s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 190s ok 70 /driver/identify/error 190s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 190s # 190s # libfprint-device-DEBUG: Device reported open completion 190s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 190s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 190s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 190s # libfprint-device-DEBUG: Device reported identify completion 190s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 190s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 190s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 190s # 190s # libfprint-device-DEBUG: Device reported close completion 190s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 190s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 190s ok 71 /driver/identify/not_reported 190s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 190s # 190s # libfprint-device-DEBUG: Device reported open completion 190s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 190s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 190s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 190s # libfprint-device-DEBUG: Device reported identify result 190s # libfprint-device-DEBUG: Device reported identify completion 190s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 190s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 190s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 190s # libfprint-device-DEBUG: Device reported identify result 190s # libfprint-device-DEBUG: Device reported identify completion 190s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 190s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 190s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 190s # libfprint-device-DEBUG: Device reported identify result 190s # libfprint-device-DEBUG: Device reported identify completion 190s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 190s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 190s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 190s # 190s # libfprint-device-DEBUG: Device reported close completion 190s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 190s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 190s ok 72 /driver/identify/complete_retry 190s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 190s # 190s # libfprint-device-DEBUG: Device reported open completion 190s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 190s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 190s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 190s # libfprint-device-DEBUG: Device reported identify result 190s # libfprint-device-DEBUG: Device reported identify completion 190s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 190s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 190s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 190s # 190s # libfprint-device-DEBUG: Device reported close completion 190s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 190s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 190s ok 73 /driver/identify/report_no_cb 190s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 190s # 190s # libfprint-device-DEBUG: Device reported open completion 190s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 190s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 190s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 190s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_suspend: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY 190s # 190s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_resume: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY 190s # 190s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_identify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY 190s # 190s # libfprint-device-DEBUG: Device reported identify result 190s # libfprint-device-DEBUG: Device reported identify completion 190s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 190s # libfprint-device-DEBUG: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 190s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 190s # 190s # libfprint-device-DEBUG: Device reported close completion 190s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 190s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 190s ok 74 /driver/identify/suspend_continues 190s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 190s # 190s # libfprint-device-DEBUG: Device reported open completion 190s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 190s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 190s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 190s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_suspend: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY 190s # 190s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_identify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY 190s # 190s # libfprint-device-DEBUG: Device reported identify result 190s # libfprint-device-DEBUG: Device reported identify completion 190s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 190s # libfprint-device-DEBUG: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 190s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 190s # 190s # libfprint-device-DEBUG: Device reported close completion 190s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 190s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 190s ok 75 /driver/identify/suspend_succeeds 190s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 190s # 190s # libfprint-device-DEBUG: Device reported open completion 190s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 190s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 190s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 190s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_suspend: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY 190s # 190s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_identify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY 190s # 190s # libfprint-device-DEBUG: Device reported identify completion 190s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 190s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 190s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 190s # 190s # libfprint-device-DEBUG: Device reported close completion 190s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 190s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 190s ok 76 /driver/identify/suspend_busy_error 190s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 190s # 190s # libfprint-device-DEBUG: Device reported open completion 190s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 190s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 190s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 190s # 190s # libfprint-device-DEBUG: Device reported close completion 190s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 190s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 190s ok 77 /driver/identify/suspend_while_idle 190s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 190s # 190s # libfprint-device-DEBUG: Device reported open completion 190s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 190s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 190s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 190s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.30, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 192s Executing: libfprint-2/fpi-device.test 192s # libfprint-device-DEBUG: Updated temperature model after 2.00 seconds, ratio 0.30 -> 0.74, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_HOT 192s # libfprint-device-DEBUG: Idle cancelling on ongoing operation! 192s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_cancel: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY 192s # 192s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_identify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY 192s # 192s # libfprint-device-DEBUG: Device reported identify completion 192s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 192s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.74 -> 0.74, active 0 -> 0, FP_TEMPERATURE_HOT -> FP_TEMPERATURE_HOT 192s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.74 -> 0.74, active 1 -> 1, FP_TEMPERATURE_HOT -> FP_TEMPERATURE_HOT 192s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.74 -> 0.74, active 0 -> 0, FP_TEMPERATURE_HOT -> FP_TEMPERATURE_HOT 194s # libfprint-device-DEBUG: Updated temperature model after 2.09 seconds, ratio 0.74 -> 0.49, active 0 -> 0, FP_TEMPERATURE_HOT -> FP_TEMPERATURE_WARM 197s Executing: libfprint-2/fpi-device.test 197s # libfprint-device-DEBUG: Updated temperature model after 3.10 seconds, ratio 0.49 -> 0.26, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_COLD 197s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 197s # 197s # libfprint-device-DEBUG: Device reported close completion 197s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 197s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.26 -> 0.26, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 197s ok 78 /driver/identify/warmup_cooldown 197s # slow test /driver/identify/warmup_cooldown executed in 7.29 secs 197s # End of identify tests 197s # Start of capture tests 197s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 197s # 197s # libfprint-device-DEBUG: Device reported open completion 197s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 197s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 197s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 197s # 197s # libfprint-device-DEBUG: Device reported close completion 197s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 197s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 197s ok 79 /driver/capture/not_supported 197s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 197s # 197s # libfprint-device-DEBUG: Device reported open completion 197s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 197s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 197s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 197s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_capture: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CAPTURE 197s # 197s # libfprint-device-DEBUG: Device reported capture completion 197s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CAPTURE in idle! 197s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 197s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 197s # 197s # libfprint-device-DEBUG: Device reported close completion 197s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 197s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 197s ok 80 /driver/capture/error 197s # End of capture tests 197s # Start of list tests 197s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 197s # 197s # libfprint-device-DEBUG: Device reported open completion 197s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 197s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 197s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_list: Device Virtual device for debugging in action FPI_DEVICE_ACTION_LIST 197s # 197s # libfprint-device-DEBUG: Device reported listing completion 197s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_LIST in idle! 197s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 197s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 197s # 197s # libfprint-device-DEBUG: Device reported close completion 197s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 197s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 197s ok 81 /driver/list/error 197s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 197s # 197s # libfprint-device-DEBUG: Device reported open completion 197s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 197s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 197s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 197s # 197s # libfprint-device-DEBUG: Device reported close completion 197s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 197s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 197s ok 82 /driver/list/no_storage 197s # End of list tests 197s # Start of delete tests 197s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 197s # 197s # libfprint-device-DEBUG: Device reported open completion 197s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 197s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 197s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_delete: Device Virtual device for debugging in action FPI_DEVICE_ACTION_DELETE 197s # 197s # libfprint-device-DEBUG: Device reported deletion completion 197s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_DELETE in idle! 197s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 197s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 197s # 197s # libfprint-device-DEBUG: Device reported close completion 197s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 197s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 197s ok 83 /driver/delete/error 197s # End of delete tests 197s # Start of clear_storage tests 197s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 197s # 197s # libfprint-device-DEBUG: Device reported open completion 197s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 197s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 197s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_clear_storage: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLEAR_STORAGE 197s # 197s # libfprint-device-DEBUG: Device reported deletion completion 197s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 197s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 197s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 197s # 197s # libfprint-device-DEBUG: Device reported close completion 197s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 197s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 197s ok 84 /driver/clear_storage/error 197s # End of clear_storage tests 197s # Start of cancel tests 197s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 197s # 197s # libfprint-device-DEBUG: Device reported open completion 197s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 197s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 197s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_delete: Device Virtual device for debugging in action FPI_DEVICE_ACTION_DELETE 197s # 197s # libfprint-device-DEBUG: Device reported deletion completion 197s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_DELETE in idle! 197s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 197s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 197s # 197s # libfprint-device-DEBUG: Device reported close completion 197s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 197s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 197s ok 85 /driver/cancel/fail 197s # End of cancel tests 197s # Start of get_current_action tests 197s # libfprint-device-DEBUG: Device reported open completion 197s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 197s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 197s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 197s # 197s # libfprint-device-DEBUG: Device reported close completion 197s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 197s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 197s ok 86 /driver/get_current_action/open 197s # End of get_current_action tests 197s # Start of get_cancellable tests 197s ok 87 /driver/get_cancellable/error 197s # libfprint-device-DEBUG: Device reported open completion 197s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 197s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 197s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 197s # 197s # libfprint-device-DEBUG: Device reported close completion 197s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 197s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 197s ok 88 /driver/get_cancellable/open 197s # Start of open tests 197s # libfprint-device-DEBUG: Device reported open completion 197s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 197s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 197s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 197s # 197s # libfprint-device-DEBUG: Device reported close completion 197s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 197s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 197s ok 89 /driver/get_cancellable/open/internal 197s # End of open tests 197s # End of get_cancellable tests 197s # Start of action_is_cancelled tests 197s # libfprint-device-DEBUG: Device reported open completion 197s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 197s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 197s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 197s # 197s # libfprint-device-DEBUG: Device reported close completion 197s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 197s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 197s ok 90 /driver/action_is_cancelled/open 197s ok 91 /driver/action_is_cancelled/error 197s # Start of open tests 197s # libfprint-device-DEBUG: Device reported open completion 197s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 197s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 197s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 197s # 197s # libfprint-device-DEBUG: Device reported close completion 197s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 197s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 197s ok 92 /driver/action_is_cancelled/open/internal 197s # End of open tests 197s # End of action_is_cancelled tests 197s # Start of complete_action tests 197s # Start of all tests 197s ok 93 /driver/complete_action/all/error 197s # End of all tests 197s # End of complete_action tests 197s # Start of action_error tests 197s ok 94 /driver/action_error/error 197s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 197s # 197s # libfprint-device-DEBUG: Device reported generic error (Passed (print) data is not valid.) during action; action was: FPI_DEVICE_ACTION_OPEN 197s # libfprint-device-DEBUG: Device reported open completion 197s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 197s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 197s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 197s # 197s # libfprint-device-DEBUG: Device reported open completion 197s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 197s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 197s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 197s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_enroll: Device Virtual device for debugging in action FPI_DEVICE_ACTION_ENROLL 197s # 197s # libfprint-device-DEBUG: Device reported generic error (Passed (print) data is not valid.) during action; action was: FPI_DEVICE_ACTION_ENROLL 197s # libfprint-device-DEBUG: Device reported enroll completion 197s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 197s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 197s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 197s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_verify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_VERIFY 197s # 197s # libfprint-device-DEBUG: Device reported generic error (Passed (print) data is not valid.) during action; action was: FPI_DEVICE_ACTION_VERIFY 197s # libfprint-device-DEBUG: Device reported verify completion 197s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 197s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 197s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 197s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_identify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY 197s # 197s # libfprint-device-DEBUG: Device reported generic error (Passed (print) data is not valid.) during action; action was: FPI_DEVICE_ACTION_IDENTIFY 197s # libfprint-device-DEBUG: Device reported identify completion 197s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 197s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 197s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 197s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_capture: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CAPTURE 197s # 197s # libfprint-device-DEBUG: Device reported generic error (Passed (print) data is not valid.) during action; action was: FPI_DEVICE_ACTION_CAPTURE 197s # libfprint-device-DEBUG: Device reported capture completion 197s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CAPTURE in idle! 197s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 197s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_list: Device Virtual device for debugging in action FPI_DEVICE_ACTION_LIST 197s # 197s # libfprint-device-DEBUG: Device reported generic error (Passed (print) data is not valid.) during action; action was: FPI_DEVICE_ACTION_LIST 197s # libfprint-device-DEBUG: Device reported listing completion 197s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_LIST in idle! 197s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 197s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_delete: Device Virtual device for debugging in action FPI_DEVICE_ACTION_DELETE 197s # 197s # libfprint-device-DEBUG: Device reported generic error (Passed (print) data is not valid.) during action; action was: FPI_DEVICE_ACTION_DELETE 197s # libfprint-device-DEBUG: Device reported deletion completion 197s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_DELETE in idle! 197s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 197s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_clear_storage: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLEAR_STORAGE 197s # 197s # libfprint-device-DEBUG: Device reported generic error (Passed (print) data is not valid.) during action; action was: FPI_DEVICE_ACTION_CLEAR_STORAGE 197s # libfprint-device-DEBUG: Device reported deletion completion 197s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 197s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 197s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 197s # 197s # libfprint-device-DEBUG: Device reported generic error (Passed (print) data is not valid.) during action; action was: FPI_DEVICE_ACTION_CLOSE 197s # libfprint-device-DEBUG: Device reported close completion 197s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 197s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 197s ok 95 /driver/action_error/all 197s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 197s # 197s # libfprint-device-DEBUG: Device reported open completion 197s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 197s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 197s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 197s # 197s # libfprint-device-DEBUG: Device reported open completion 197s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 197s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 197s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 197s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_enroll: Device Virtual device for debugging in action FPI_DEVICE_ACTION_ENROLL 197s # 197s # libfprint-device-DEBUG: Device reported enroll completion 197s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 197s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 197s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 197s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_verify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_VERIFY 197s # 197s # libfprint-device-DEBUG: Device reported verify completion 197s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 197s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 197s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 197s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_identify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY 197s # 197s # libfprint-device-DEBUG: Device reported identify completion 197s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 197s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 197s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 197s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_capture: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CAPTURE 197s # 197s # libfprint-device-DEBUG: Device reported capture completion 197s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CAPTURE in idle! 197s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 197s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_list: Device Virtual device for debugging in action FPI_DEVICE_ACTION_LIST 197s # 197s # libfprint-device-DEBUG: Device reported listing completion 197s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_LIST in idle! 197s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 197s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_delete: Device Virtual device for debugging in action FPI_DEVICE_ACTION_DELETE 197s # 197s # libfprint-device-DEBUG: Device reported deletion completion 197s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_DELETE in idle! 197s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 197s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_clear_storage: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLEAR_STORAGE 197s # 197s # libfprint-device-DEBUG: Device reported deletion completion 197s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 197s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 197s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 197s # 197s # libfprint-device-DEBUG: Device reported close completion 197s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 197s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 197s ok 96 /driver/action_error/fail 197s # End of action_error tests 197s # Start of timeout tests 197s ok 97 /driver/timeout/cancelled 197s # End of timeout tests 197s # End of driver tests 197s PASS: libfprint-2/fpi-device.test 197s Running test: libfprint-2/driver-synaptics.test 197s ** (umockdev-run:2366): DEBUG: 16:48:34.515: umockdev.vala:123: Created udev test bed /tmp/umockdev.ZWSBK2 197s ** (umockdev-run:2366): DEBUG: 16:48:34.515: umockdev.vala:1297: parsing device description for /devices/pci0000:00/0000:00:14.0/usb1/1-9 197s ** (umockdev-run:2366): DEBUG: 16:48:34.516: umockdev.vala:1366: creating device /devices/pci0000:00/0000:00:14.0/usb1/1-9 (subsystem usb) 197s ** (umockdev-run:2366): DEBUG: 16:48:34.518: umockdev.vala:1411: create_node_for_device: creating file device /tmp/umockdev.ZWSBK2/dev/bus/usb/001/004 197s ** (umockdev-run:2366): DEBUG: 16:48:34.518: umockdev.vala:1297: parsing device description for /devices/pci0000:00/0000:00:14.0/usb1 197s ** (umockdev-run:2366): DEBUG: 16:48:34.519: umockdev.vala:1366: creating device /devices/pci0000:00/0000:00:14.0/usb1 (subsystem usb) 197s ** (umockdev-run:2366): DEBUG: 16:48:34.521: umockdev.vala:1411: create_node_for_device: creating file device /tmp/umockdev.ZWSBK2/dev/bus/usb/001/001 197s ** (umockdev-run:2366): DEBUG: 16:48:34.521: umockdev.vala:1297: parsing device description for /devices/pci0000:00/0000:00:14.0 197s ** (umockdev-run:2366): DEBUG: 16:48:34.521: umockdev.vala:1366: creating device /devices/pci0000:00/0000:00:14.0 (subsystem pci) 197s (process:2370): libfprint-context-DEBUG: 16:48:34.579: Initializing FpContext (libfprint version 1.94.7+tod1) 197s (process:2370): libfprint-tod-DEBUG: 16:48:34.579: Impossible to load the shared drivers dir Error opening directory “/usr/lib/aarch64-linux-gnu/libfprint-2/tod-1”: No such file or directory 197s (process:2370): libfprint-context-DEBUG: 16:48:34.581: No driver found for USB device 1D6B:0002 197s (process:2370): libfprint-synaptics-DEBUG: 16:48:34.581: 85582398: ../libfprint/drivers/synaptics/synaptics.c:1240 197s (process:2370): libfprint-synaptics-DEBUG: 16:48:34.585: Build Time: 1596608839 197s (process:2370): libfprint-synaptics-DEBUG: 16:48:34.585: Build Num: 3273255 197s (process:2370): libfprint-synaptics-DEBUG: 16:48:34.585: Version: 10.1 197s (process:2370): libfprint-synaptics-DEBUG: 16:48:34.585: Target: 1 197s (process:2370): libfprint-synaptics-DEBUG: 16:48:34.585: Product: 65 197s (process:2370): libfprint-synaptics-DEBUG: 16:48:34.585: sequence number is 1 197s (process:2370): libfprint-SSM-DEBUG: 16:48:34.585: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 197s (process:2370): libfprint-SSM-DEBUG: 16:48:34.585: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 197s (process:2370): libfprint-device-DEBUG: 16:48:34.586: Device reported probe completion 197s (process:2370): libfprint-SSM-DEBUG: 16:48:34.586: [synaptics] SYNAPTICS_CMD_NUM_STATES completed successfully 197s (process:2370): libfprint-device-DEBUG: 16:48:34.586: Completing action FPI_DEVICE_ACTION_PROBE in idle! 197s (process:2370): libfprint-device-DEBUG: 16:48:34.586: Not updating temperature model, device can run continuously! 197s (process:2370): libfprint-synaptics-DEBUG: 16:48:34.587: 85588341: ../libfprint/drivers/synaptics/synaptics.c:1400 197s (process:2370): libfprint-synaptics-DEBUG: 16:48:34.587: sequence number is 2 197s (process:2370): libfprint-SSM-DEBUG: 16:48:34.587: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 197s (process:2370): libfprint-SSM-DEBUG: 16:48:34.588: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 197s (process:2370): libfprint-device-DEBUG: 16:48:34.588: Device reported open completion 197s (process:2370): libfprint-SSM-DEBUG: 16:48:34.588: [synaptics] SYNAPTICS_CMD_NUM_STATES completed successfully 197s (process:2370): libfprint-device-DEBUG: 16:48:34.588: Completing action FPI_DEVICE_ACTION_OPEN in idle! 197s (process:2370): libfprint-device-DEBUG: 16:48:34.588: Not updating temperature model, device can run continuously! 197s (process:2370): libfprint-synaptics-DEBUG: 16:48:34.589: clear all prints in database 197s (process:2370): libfprint-synaptics-DEBUG: 16:48:34.589: sequence number is 3 197s (process:2370): libfprint-SSM-DEBUG: 16:48:34.589: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 197s (process:2370): libfprint-SSM-DEBUG: 16:48:34.589: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 197s (process:2370): libfprint-synaptics-DEBUG: 16:48:34.590: Deleting All Enrolled Users is 0% complete 197s (process:2370): libfprint-SSM-DEBUG: 16:48:34.590: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 197s (process:2370): libfprint-synaptics-DEBUG: 16:48:34.590: interrupt transfer done 197s (process:2370): libfprint-SSM-DEBUG: 16:48:34.590: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 197s (process:2370): libfprint-SSM-DEBUG: 16:48:34.591: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 197s (process:2370): libfprint-SSM-DEBUG: 16:48:34.591: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 197s (process:2370): libfprint-SSM-DEBUG: 16:48:34.591: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 197s (process:2370): libfprint-synaptics-DEBUG: 16:48:34.591: Deleting All Enrolled Users is 100% complete 197s (process:2370): libfprint-SSM-DEBUG: 16:48:34.591: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 197s (process:2370): libfprint-synaptics-DEBUG: 16:48:34.592: interrupt transfer done 197s (process:2370): libfprint-SSM-DEBUG: 16:48:34.592: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 197s (process:2370): libfprint-SSM-DEBUG: 16:48:34.592: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 197s (process:2370): libfprint-SSM-DEBUG: 16:48:34.592: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 197s (process:2370): libfprint-SSM-DEBUG: 16:48:34.592: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 197s (process:2370): libfprint-synaptics-DEBUG: 16:48:34.593: Successfully deleted all enrolled user 197s (process:2370): libfprint-device-DEBUG: 16:48:34.593: Device reported deletion completion 197s (process:2370): libfprint-SSM-DEBUG: 16:48:34.593: [synaptics] SYNAPTICS_CMD_NUM_STATES completed successfully 197s (process:2370): libfprint-device-DEBUG: 16:48:34.593: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 197s (process:2370): libfprint-device-DEBUG: 16:48:34.593: Not updating temperature model, device can run continuously! 197s (process:2370): libfprint-device-DEBUG: 16:48:34.593: Not updating temperature model, device can run continuously! 197s (process:2370): libfprint-synaptics-DEBUG: 16:48:34.593: 85594484: ../libfprint/drivers/synaptics/synaptics.c:1011 197s (process:2370): libfprint-synaptics-DEBUG: 16:48:34.593: user_id: FP1-00000000-0-00000000-nobody, finger: 1 197s (process:2370): libfprint-synaptics-DEBUG: 16:48:34.593: sequence number is 4 197s (process:2370): libfprint-SSM-DEBUG: 16:48:34.593: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 197s (process:2370): libfprint-SSM-DEBUG: 16:48:34.594: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 197s (process:2370): libfprint-device-DEBUG: 16:48:34.594: Device reported finger status change: FP_FINGER_STATUS_NEEDED 197s (process:2370): libfprint-synaptics-DEBUG: 16:48:34.594: Place Finger on the Sensor! 197s (process:2370): libfprint-SSM-DEBUG: 16:48:34.594: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 197s (process:2370): libfprint-synaptics-DEBUG: 16:48:34.595: interrupt transfer done 197s (process:2370): libfprint-SSM-DEBUG: 16:48:34.595: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 197s (process:2370): libfprint-SSM-DEBUG: 16:48:34.595: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 197s (process:2370): libfprint-SSM-DEBUG: 16:48:34.596: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 197s (process:2370): libfprint-SSM-DEBUG: 16:48:34.596: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 197s (process:2370): libfprint-device-DEBUG: 16:48:34.596: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 197s (process:2370): libfprint-synaptics-DEBUG: 16:48:34.596: Finger is now on the sensor 197s (process:2370): libfprint-synaptics-DEBUG: 16:48:34.596: Received message with 0 sequence number 0x91, ignoring! 197s (process:2370): libfprint-SSM-DEBUG: 16:48:34.596: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 197s (process:2370): libfprint-synaptics-DEBUG: 16:48:34.597: interrupt transfer done 197s (process:2370): libfprint-SSM-DEBUG: 16:48:34.597: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 197s (process:2370): libfprint-SSM-DEBUG: 16:48:34.597: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 197s (process:2370): libfprint-SSM-DEBUG: 16:48:34.597: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 197s (process:2370): libfprint-SSM-DEBUG: 16:48:34.597: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 197s (process:2370): libfprint-synaptics-DEBUG: 16:48:34.598: Fingerprint image capture complete! 197s (process:2370): libfprint-SSM-DEBUG: 16:48:34.598: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 197s (process:2370): libfprint-synaptics-DEBUG: 16:48:34.598: interrupt transfer done 197s (process:2370): libfprint-SSM-DEBUG: 16:48:34.598: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 197s (process:2370): libfprint-SSM-DEBUG: 16:48:34.599: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 197s (process:2370): libfprint-SSM-DEBUG: 16:48:34.599: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 197s (process:2370): libfprint-SSM-DEBUG: 16:48:34.599: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 197s (process:2370): libfprint-device-DEBUG: 16:48:34.599: Device reported finger status change: FP_FINGER_STATUS_NEEDED 197s (process:2370): libfprint-synaptics-DEBUG: 16:48:34.599: Finger is now off the sensor 197s (process:2370): libfprint-synaptics-DEBUG: 16:48:34.599: Received message with 0 sequence number 0x91, ignoring! 197s (process:2370): libfprint-SSM-DEBUG: 16:48:34.599: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 197s (process:2370): libfprint-synaptics-DEBUG: 16:48:34.600: interrupt transfer done 197s (process:2370): libfprint-SSM-DEBUG: 16:48:34.600: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 197s (process:2370): libfprint-SSM-DEBUG: 16:48:34.600: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 197s (process:2370): libfprint-SSM-DEBUG: 16:48:34.600: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 197s (process:2370): libfprint-SSM-DEBUG: 16:48:34.600: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 197s (process:2370): libfprint-synaptics-DEBUG: 16:48:34.601: Enrollment is 12 % 197s (process:2370): libfprint-device-DEBUG: 16:48:34.601: Device reported enroll progress, reported 1 of 8 have been completed 197s (process:2370): libfprint-SSM-DEBUG: 16:48:34.601: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 197s (process:2370): libfprint-synaptics-DEBUG: 16:48:34.601: interrupt transfer done 197s (process:2370): libfprint-SSM-DEBUG: 16:48:34.601: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 197s (process:2370): libfprint-SSM-DEBUG: 16:48:34.602: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 197s (process:2370): libfprint-SSM-DEBUG: 16:48:34.602: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 197s (process:2370): libfprint-SSM-DEBUG: 16:48:34.602: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 197s (process:2370): libfprint-device-DEBUG: 16:48:34.602: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 197s (process:2370): libfprint-synaptics-DEBUG: 16:48:34.602: Finger is now on the sensor 197s (process:2370): libfprint-synaptics-DEBUG: 16:48:34.602: Received message with 0 sequence number 0x91, ignoring! 197s (process:2370): libfprint-SSM-DEBUG: 16:48:34.602: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 197s (process:2370): libfprint-synaptics-DEBUG: 16:48:34.603: interrupt transfer done 197s (process:2370): libfprint-SSM-DEBUG: 16:48:34.603: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 197s (process:2370): libfprint-SSM-DEBUG: 16:48:34.604: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 197s (process:2370): libfprint-SSM-DEBUG: 16:48:34.604: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 197s (process:2370): libfprint-SSM-DEBUG: 16:48:34.604: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 197s (process:2370): libfprint-synaptics-DEBUG: 16:48:34.604: Fingerprint image capture complete! 197s (process:2370): libfprint-SSM-DEBUG: 16:48:34.604: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 197s (process:2370): libfprint-synaptics-DEBUG: 16:48:34.605: interrupt transfer done 197s (process:2370): libfprint-SSM-DEBUG: 16:48:34.605: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 197s (process:2370): libfprint-SSM-DEBUG: 16:48:34.605: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 197s (process:2370): libfprint-SSM-DEBUG: 16:48:34.605: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 197s (process:2370): libfprint-SSM-DEBUG: 16:48:34.605: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 197s (process:2370): libfprint-device-DEBUG: 16:48:34.606: Device reported finger status change: FP_FINGER_STATUS_NEEDED 197s (process:2370): libfprint-synaptics-DEBUG: 16:48:34.606: Finger is now off the sensor 197s (process:2370): libfprint-synaptics-DEBUG: 16:48:34.606: Received message with 0 sequence number 0x91, ignoring! 197s (process:2370): libfprint-SSM-DEBUG: 16:48:34.606: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 197s (process:2370): libfprint-synaptics-DEBUG: 16:48:34.606: interrupt transfer done 197s (process:2370): libfprint-SSM-DEBUG: 16:48:34.606: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 197s (process:2370): libfprint-SSM-DEBUG: 16:48:34.607: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 197s (process:2370): libfprint-SSM-DEBUG: 16:48:34.607: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 197s (process:2370): libfprint-SSM-DEBUG: 16:48:34.607: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 197s (process:2370): libfprint-synaptics-DEBUG: 16:48:34.607: Enrollment is 25 % 197s (process:2370): libfprint-device-DEBUG: 16:48:34.607: Device reported enroll progress, reported 2 of 8 have been completed 197s (process:2370): libfprint-SSM-DEBUG: 16:48:34.607: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 197s (process:2370): libfprint-synaptics-DEBUG: 16:48:34.608: interrupt transfer done 197s (process:2370): libfprint-SSM-DEBUG: 16:48:34.608: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 197s (process:2370): libfprint-SSM-DEBUG: 16:48:34.608: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 197s (process:2370): libfprint-SSM-DEBUG: 16:48:34.608: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 197s (process:2370): libfprint-SSM-DEBUG: 16:48:34.608: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 197s (process:2370): libfprint-device-DEBUG: 16:48:34.609: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 197s (process:2370): libfprint-synaptics-DEBUG: 16:48:34.609: Finger is now on the sensor 197s (process:2370): libfprint-synaptics-DEBUG: 16:48:34.609: Received message with 0 sequence number 0x91, ignoring! 197s (process:2370): libfprint-SSM-DEBUG: 16:48:34.609: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 197s (process:2370): libfprint-synaptics-DEBUG: 16:48:34.609: interrupt transfer done 197s (process:2370): libfprint-SSM-DEBUG: 16:48:34.609: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 197s (process:2370): libfprint-SSM-DEBUG: 16:48:34.610: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 197s (process:2370): libfprint-SSM-DEBUG: 16:48:34.610: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 197s (process:2370): libfprint-SSM-DEBUG: 16:48:34.610: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 197s (process:2370): libfprint-synaptics-DEBUG: 16:48:34.610: Fingerprint image capture complete! 197s (process:2370): libfprint-SSM-DEBUG: 16:48:34.610: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 197s (process:2370): libfprint-synaptics-DEBUG: 16:48:34.611: interrupt transfer done 197s (process:2370): libfprint-SSM-DEBUG: 16:48:34.611: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 197s (process:2370): libfprint-SSM-DEBUG: 16:48:34.611: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 197s (process:2370): libfprint-SSM-DEBUG: 16:48:34.611: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 197s (process:2370): libfprint-SSM-DEBUG: 16:48:34.611: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 197s (process:2370): libfprint-synaptics-DEBUG: 16:48:34.612: Enrollment is 37 % 197s (process:2370): libfprint-device-DEBUG: 16:48:34.612: Device reported enroll progress, reported 3 of 8 have been completed 197s (process:2370): libfprint-SSM-DEBUG: 16:48:34.612: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 197s (process:2370): libfprint-synaptics-DEBUG: 16:48:34.612: interrupt transfer done 197s (process:2370): libfprint-SSM-DEBUG: 16:48:34.612: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 197s (process:2370): libfprint-SSM-DEBUG: 16:48:34.613: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 197s (process:2370): libfprint-SSM-DEBUG: 16:48:34.613: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 197s (process:2370): libfprint-SSM-DEBUG: 16:48:34.613: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 197s (process:2370): libfprint-device-DEBUG: 16:48:34.613: Device reported finger status change: FP_FINGER_STATUS_NEEDED 197s (process:2370): libfprint-synaptics-DEBUG: 16:48:34.613: Finger is now off the sensor 197s (process:2370): libfprint-synaptics-DEBUG: 16:48:34.613: Received message with 0 sequence number 0x91, ignoring! 197s (process:2370): libfprint-SSM-DEBUG: 16:48:34.613: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 197s (process:2370): libfprint-synaptics-DEBUG: 16:48:34.614: interrupt transfer done 197s (process:2370): libfprint-SSM-DEBUG: 16:48:34.614: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 197s (process:2370): libfprint-SSM-DEBUG: 16:48:34.614: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 197s (process:2370): libfprint-SSM-DEBUG: 16:48:34.614: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 197s (process:2370): libfprint-SSM-DEBUG: 16:48:34.614: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 197s (process:2370): libfprint-device-DEBUG: 16:48:34.615: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 197s (process:2370): libfprint-synaptics-DEBUG: 16:48:34.615: Finger is now on the sensor 197s (process:2370): libfprint-synaptics-DEBUG: 16:48:34.615: Received message with 0 sequence number 0x91, ignoring! 197s (process:2370): libfprint-SSM-DEBUG: 16:48:34.615: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 197s (process:2370): libfprint-synaptics-DEBUG: 16:48:34.615: interrupt transfer done 197s (process:2370): libfprint-SSM-DEBUG: 16:48:34.615: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 197s (process:2370): libfprint-SSM-DEBUG: 16:48:34.616: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 197s (process:2370): libfprint-SSM-DEBUG: 16:48:34.616: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 197s (process:2370): libfprint-SSM-DEBUG: 16:48:34.616: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 197s (process:2370): libfprint-synaptics-DEBUG: 16:48:34.616: Fingerprint image capture complete! 197s (process:2370): libfprint-SSM-DEBUG: 16:48:34.616: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 197s (process:2370): libfprint-synaptics-DEBUG: 16:48:34.617: interrupt transfer done 197s (process:2370): libfprint-SSM-DEBUG: 16:48:34.617: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 197s (process:2370): libfprint-SSM-DEBUG: 16:48:34.617: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 197s (process:2370): libfprint-SSM-DEBUG: 16:48:34.617: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 197s (process:2370): libfprint-SSM-DEBUG: 16:48:34.617: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 197s (process:2370): libfprint-device-DEBUG: 16:48:34.618: Device reported finger status change: FP_FINGER_STATUS_NEEDED 197s (process:2370): libfprint-synaptics-DEBUG: 16:48:34.618: Finger is now off the sensor 197s (process:2370): libfprint-synaptics-DEBUG: 16:48:34.618: Received message with 0 sequence number 0x91, ignoring! 197s (process:2370): libfprint-SSM-DEBUG: 16:48:34.618: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 197s (process:2370): libfprint-synaptics-DEBUG: 16:48:34.618: interrupt transfer done 197s (process:2370): libfprint-SSM-DEBUG: 16:48:34.618: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 197s (process:2370): libfprint-SSM-DEBUG: 16:48:34.619: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 197s (process:2370): libfprint-SSM-DEBUG: 16:48:34.619: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 197s (process:2370): libfprint-SSM-DEBUG: 16:48:34.619: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 197s (process:2370): libfprint-synaptics-DEBUG: 16:48:34.619: Enrollment is 50 % 197s (process:2370): libfprint-device-DEBUG: 16:48:34.619: Device reported enroll progress, reported 4 of 8 have been completed 197s (process:2370): libfprint-SSM-DEBUG: 16:48:34.619: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 197s (process:2370): libfprint-synaptics-DEBUG: 16:48:34.620: interrupt transfer done 197s (process:2370): libfprint-SSM-DEBUG: 16:48:34.620: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 197s (process:2370): libfprint-SSM-DEBUG: 16:48:34.620: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 197s (process:2370): libfprint-SSM-DEBUG: 16:48:34.620: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 197s (process:2370): libfprint-SSM-DEBUG: 16:48:34.620: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 197s (process:2370): libfprint-device-DEBUG: 16:48:34.621: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 197s (process:2370): libfprint-synaptics-DEBUG: 16:48:34.621: Finger is now on the sensor 197s (process:2370): libfprint-synaptics-DEBUG: 16:48:34.621: Received message with 0 sequence number 0x91, ignoring! 197s (process:2370): libfprint-SSM-DEBUG: 16:48:34.621: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 197s (process:2370): libfprint-synaptics-DEBUG: 16:48:34.621: interrupt transfer done 197s (process:2370): libfprint-SSM-DEBUG: 16:48:34.621: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 197s (process:2370): libfprint-SSM-DEBUG: 16:48:34.622: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 197s (process:2370): libfprint-SSM-DEBUG: 16:48:34.622: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 197s (process:2370): libfprint-SSM-DEBUG: 16:48:34.622: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 197s (process:2370): libfprint-synaptics-DEBUG: 16:48:34.622: Fingerprint image capture complete! 197s (process:2370): libfprint-SSM-DEBUG: 16:48:34.622: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 197s (process:2370): libfprint-synaptics-DEBUG: 16:48:34.623: interrupt transfer done 197s (process:2370): libfprint-SSM-DEBUG: 16:48:34.623: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 197s (process:2370): libfprint-SSM-DEBUG: 16:48:34.623: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 197s (process:2370): libfprint-SSM-DEBUG: 16:48:34.623: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 197s (process:2370): libfprint-SSM-DEBUG: 16:48:34.623: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 197s (process:2370): libfprint-device-DEBUG: 16:48:34.624: Device reported finger status change: FP_FINGER_STATUS_NEEDED 197s (process:2370): libfprint-synaptics-DEBUG: 16:48:34.624: Finger is now off the sensor 197s (process:2370): libfprint-synaptics-DEBUG: 16:48:34.624: Received message with 0 sequence number 0x91, ignoring! 197s (process:2370): libfprint-SSM-DEBUG: 16:48:34.624: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 197s (process:2370): libfprint-synaptics-DEBUG: 16:48:34.624: interrupt transfer done 197s (process:2370): libfprint-SSM-DEBUG: 16:48:34.624: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 197s (process:2370): libfprint-SSM-DEBUG: 16:48:34.625: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 197s (process:2370): libfprint-SSM-DEBUG: 16:48:34.625: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 197s (process:2370): libfprint-SSM-DEBUG: 16:48:34.625: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 197s (process:2370): libfprint-synaptics-DEBUG: 16:48:34.625: Enrollment is 62 % 197s (process:2370): libfprint-device-DEBUG: 16:48:34.625: Device reported enroll progress, reported 5 of 8 have been completed 197s (process:2370): libfprint-SSM-DEBUG: 16:48:34.625: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 197s (process:2370): libfprint-synaptics-DEBUG: 16:48:34.626: interrupt transfer done 197s (process:2370): libfprint-SSM-DEBUG: 16:48:34.626: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 197s (process:2370): libfprint-SSM-DEBUG: 16:48:34.626: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 197s (process:2370): libfprint-SSM-DEBUG: 16:48:34.626: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 197s (process:2370): libfprint-SSM-DEBUG: 16:48:34.626: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 197s (process:2370): libfprint-device-DEBUG: 16:48:34.627: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 197s (process:2370): libfprint-synaptics-DEBUG: 16:48:34.627: Finger is now on the sensor 197s (process:2370): libfprint-synaptics-DEBUG: 16:48:34.627: Received message with 0 sequence number 0x91, ignoring! 197s (process:2370): libfprint-SSM-DEBUG: 16:48:34.627: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 197s (process:2370): libfprint-synaptics-DEBUG: 16:48:34.627: interrupt transfer done 197s (process:2370): libfprint-SSM-DEBUG: 16:48:34.627: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 197s (process:2370): libfprint-SSM-DEBUG: 16:48:34.628: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 197s (process:2370): libfprint-SSM-DEBUG: 16:48:34.628: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 197s (process:2370): libfprint-SSM-DEBUG: 16:48:34.628: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 197s (process:2370): libfprint-synaptics-DEBUG: 16:48:34.628: Fingerprint image capture complete! 197s (process:2370): libfprint-SSM-DEBUG: 16:48:34.628: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 197s (process:2370): libfprint-synaptics-DEBUG: 16:48:34.629: interrupt transfer done 197s (process:2370): libfprint-SSM-DEBUG: 16:48:34.629: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 197s (process:2370): libfprint-SSM-DEBUG: 16:48:34.629: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 197s (process:2370): libfprint-SSM-DEBUG: 16:48:34.629: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 197s (process:2370): libfprint-SSM-DEBUG: 16:48:34.629: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 197s (process:2370): libfprint-device-DEBUG: 16:48:34.630: Device reported finger status change: FP_FINGER_STATUS_NEEDED 197s (process:2370): libfprint-synaptics-DEBUG: 16:48:34.630: Finger is now off the sensor 197s (process:2370): libfprint-synaptics-DEBUG: 16:48:34.630: Received message with 0 sequence number 0x91, ignoring! 197s (process:2370): libfprint-SSM-DEBUG: 16:48:34.630: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 197s (process:2370): libfprint-synaptics-DEBUG: 16:48:34.630: interrupt transfer done 197s (process:2370): libfprint-SSM-DEBUG: 16:48:34.630: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 197s (process:2370): libfprint-SSM-DEBUG: 16:48:34.631: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 197s (process:2370): libfprint-SSM-DEBUG: 16:48:34.631: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 197s (process:2370): libfprint-SSM-DEBUG: 16:48:34.631: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 197s (process:2370): libfprint-synaptics-DEBUG: 16:48:34.631: Enrollment is 62 % 197s (process:2370): libfprint-device-DEBUG: 16:48:34.631: Device reported enroll progress, reported 5 of 8 have been completed 197s (process:2370): libfprint-SSM-DEBUG: 16:48:34.631: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 197s (process:2370): libfprint-synaptics-DEBUG: 16:48:34.632: interrupt transfer done 197s (process:2370): libfprint-SSM-DEBUG: 16:48:34.632: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 197s (process:2370): libfprint-SSM-DEBUG: 16:48:34.632: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 197s (process:2370): libfprint-SSM-DEBUG: 16:48:34.632: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 197s (process:2370): libfprint-SSM-DEBUG: 16:48:34.632: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 197s (process:2370): libfprint-device-DEBUG: 16:48:34.633: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 197s (process:2370): libfprint-synaptics-DEBUG: 16:48:34.633: Finger is now on the sensor 197s (process:2370): libfprint-synaptics-DEBUG: 16:48:34.633: Received message with 0 sequence number 0x91, ignoring! 197s (process:2370): libfprint-SSM-DEBUG: 16:48:34.633: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 197s (process:2370): libfprint-synaptics-DEBUG: 16:48:34.633: interrupt transfer done 197s (process:2370): libfprint-SSM-DEBUG: 16:48:34.633: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 197s (process:2370): libfprint-SSM-DEBUG: 16:48:34.634: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 197s (process:2370): libfprint-SSM-DEBUG: 16:48:34.634: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 197s (process:2370): libfprint-SSM-DEBUG: 16:48:34.634: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 197s (process:2370): libfprint-synaptics-DEBUG: 16:48:34.634: Fingerprint image capture complete! 197s (process:2370): libfprint-SSM-DEBUG: 16:48:34.634: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 197s (process:2370): libfprint-synaptics-DEBUG: 16:48:34.635: interrupt transfer done 197s (process:2370): libfprint-SSM-DEBUG: 16:48:34.635: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 197s (process:2370): libfprint-SSM-DEBUG: 16:48:34.635: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 197s (process:2370): libfprint-SSM-DEBUG: 16:48:34.635: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 197s (process:2370): libfprint-SSM-DEBUG: 16:48:34.635: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 197s (process:2370): libfprint-synaptics-DEBUG: 16:48:34.636: Enrollment is 75 % 197s (process:2370): libfprint-device-DEBUG: 16:48:34.636: Device reported enroll progress, reported 6 of 8 have been completed 197s (process:2370): libfprint-SSM-DEBUG: 16:48:34.636: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 197s (process:2370): libfprint-synaptics-DEBUG: 16:48:34.636: interrupt transfer done 197s (process:2370): libfprint-SSM-DEBUG: 16:48:34.636: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 197s (process:2370): libfprint-SSM-DEBUG: 16:48:34.637: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 197s (process:2370): libfprint-SSM-DEBUG: 16:48:34.637: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 197s (process:2370): libfprint-SSM-DEBUG: 16:48:34.637: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 197s (process:2370): libfprint-device-DEBUG: 16:48:34.637: Device reported finger status change: FP_FINGER_STATUS_NEEDED 197s (process:2370): libfprint-synaptics-DEBUG: 16:48:34.637: Finger is now off the sensor 197s (process:2370): libfprint-synaptics-DEBUG: 16:48:34.637: Received message with 0 sequence number 0x91, ignoring! 197s (process:2370): libfprint-SSM-DEBUG: 16:48:34.637: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 197s (process:2370): libfprint-synaptics-DEBUG: 16:48:34.638: interrupt transfer done 197s (process:2370): libfprint-SSM-DEBUG: 16:48:34.638: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 197s (process:2370): libfprint-SSM-DEBUG: 16:48:34.638: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 197s (process:2370): libfprint-SSM-DEBUG: 16:48:34.638: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 197s (process:2370): libfprint-SSM-DEBUG: 16:48:34.638: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 197s (process:2370): libfprint-device-DEBUG: 16:48:34.639: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 197s (process:2370): libfprint-synaptics-DEBUG: 16:48:34.639: Finger is now on the sensor 197s (process:2370): libfprint-synaptics-DEBUG: 16:48:34.639: Received message with 0 sequence number 0x91, ignoring! 197s (process:2370): libfprint-SSM-DEBUG: 16:48:34.639: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 197s (process:2370): libfprint-synaptics-DEBUG: 16:48:34.639: interrupt transfer done 197s (process:2370): libfprint-SSM-DEBUG: 16:48:34.639: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 197s (process:2370): libfprint-SSM-DEBUG: 16:48:34.640: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 197s (process:2370): libfprint-SSM-DEBUG: 16:48:34.640: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 197s (process:2370): libfprint-SSM-DEBUG: 16:48:34.640: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 197s (process:2370): libfprint-synaptics-DEBUG: 16:48:34.641: Fingerprint image capture complete! 197s (process:2370): libfprint-SSM-DEBUG: 16:48:34.641: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 197s (process:2370): libfprint-synaptics-DEBUG: 16:48:34.641: interrupt transfer done 197s (process:2370): libfprint-SSM-DEBUG: 16:48:34.641: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 197s (process:2370): libfprint-SSM-DEBUG: 16:48:34.642: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 197s (process:2370): libfprint-SSM-DEBUG: 16:48:34.642: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 197s (process:2370): libfprint-SSM-DEBUG: 16:48:34.642: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 197s (process:2370): libfprint-device-DEBUG: 16:48:34.642: Device reported finger status change: FP_FINGER_STATUS_NEEDED 197s (process:2370): libfprint-synaptics-DEBUG: 16:48:34.642: Finger is now off the sensor 197s (process:2370): libfprint-synaptics-DEBUG: 16:48:34.642: Received message with 0 sequence number 0x91, ignoring! 197s (process:2370): libfprint-SSM-DEBUG: 16:48:34.642: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 197s (process:2370): libfprint-synaptics-DEBUG: 16:48:34.643: interrupt transfer done 197s (process:2370): libfprint-SSM-DEBUG: 16:48:34.643: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 197s (process:2370): libfprint-SSM-DEBUG: 16:48:34.643: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 197s (process:2370): libfprint-SSM-DEBUG: 16:48:34.643: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 197s (process:2370): libfprint-SSM-DEBUG: 16:48:34.643: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 197s (process:2370): libfprint-synaptics-DEBUG: 16:48:34.644: Enrollment is 87 % 197s (process:2370): libfprint-device-DEBUG: 16:48:34.644: Device reported enroll progress, reported 7 of 8 have been completed 197s (process:2370): libfprint-SSM-DEBUG: 16:48:34.644: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 197s (process:2370): libfprint-synaptics-DEBUG: 16:48:34.644: interrupt transfer done 197s (process:2370): libfprint-SSM-DEBUG: 16:48:34.644: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 197s (process:2370): libfprint-SSM-DEBUG: 16:48:34.645: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 197s (process:2370): libfprint-SSM-DEBUG: 16:48:34.645: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 197s (process:2370): libfprint-SSM-DEBUG: 16:48:34.645: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 197s (process:2370): libfprint-device-DEBUG: 16:48:34.646: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 197s (process:2370): libfprint-synaptics-DEBUG: 16:48:34.646: Finger is now on the sensor 197s (process:2370): libfprint-synaptics-DEBUG: 16:48:34.646: Received message with 0 sequence number 0x91, ignoring! 197s (process:2370): libfprint-SSM-DEBUG: 16:48:34.646: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 197s (process:2370): libfprint-synaptics-DEBUG: 16:48:34.646: interrupt transfer done 197s (process:2370): libfprint-SSM-DEBUG: 16:48:34.646: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 197s (process:2370): libfprint-SSM-DEBUG: 16:48:34.647: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 197s (process:2370): libfprint-SSM-DEBUG: 16:48:34.647: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 197s (process:2370): libfprint-SSM-DEBUG: 16:48:34.647: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 197s (process:2370): libfprint-synaptics-DEBUG: 16:48:34.647: Fingerprint image capture complete! 197s (process:2370): libfprint-SSM-DEBUG: 16:48:34.647: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 197s (process:2370): libfprint-synaptics-DEBUG: 16:48:34.648: interrupt transfer done 197s (process:2370): libfprint-SSM-DEBUG: 16:48:34.648: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 197s (process:2370): libfprint-SSM-DEBUG: 16:48:34.648: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 197s (process:2370): libfprint-SSM-DEBUG: 16:48:34.648: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 197s (process:2370): libfprint-SSM-DEBUG: 16:48:34.648: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 197s (process:2370): libfprint-device-DEBUG: 16:48:34.649: Device reported finger status change: FP_FINGER_STATUS_NEEDED 197s (process:2370): libfprint-synaptics-DEBUG: 16:48:34.649: Finger is now off the sensor 197s (process:2370): libfprint-synaptics-DEBUG: 16:48:34.649: Received message with 0 sequence number 0x91, ignoring! 197s (process:2370): libfprint-SSM-DEBUG: 16:48:34.649: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 197s (process:2370): libfprint-synaptics-DEBUG: 16:48:34.650: interrupt transfer done 197s (process:2370): libfprint-SSM-DEBUG: 16:48:34.650: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 197s (process:2370): libfprint-SSM-DEBUG: 16:48:34.650: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 197s (process:2370): libfprint-SSM-DEBUG: 16:48:34.650: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 197s (process:2370): libfprint-SSM-DEBUG: 16:48:34.650: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 197s (process:2370): libfprint-synaptics-DEBUG: 16:48:34.651: Enrollment is 100 % 197s (process:2370): libfprint-device-DEBUG: 16:48:34.651: Device reported enroll progress, reported 8 of 8 have been completed 197s (process:2370): libfprint-SSM-DEBUG: 16:48:34.651: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 197s (process:2370): libfprint-synaptics-DEBUG: 16:48:34.651: interrupt transfer done 197s (process:2370): libfprint-SSM-DEBUG: 16:48:34.651: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 197s (process:2370): libfprint-SSM-DEBUG: 16:48:34.652: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 197s (process:2370): libfprint-SSM-DEBUG: 16:48:34.652: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 197s (process:2370): libfprint-SSM-DEBUG: 16:48:34.652: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 197s (process:2370): libfprint-device-DEBUG: 16:48:34.652: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 197s (process:2370): libfprint-synaptics-DEBUG: 16:48:34.652: Finger is now on the sensor 197s (process:2370): libfprint-synaptics-DEBUG: 16:48:34.652: Received message with 0 sequence number 0x91, ignoring! 197s (process:2370): libfprint-SSM-DEBUG: 16:48:34.652: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 197s (process:2370): libfprint-synaptics-DEBUG: 16:48:34.653: interrupt transfer done 197s (process:2370): libfprint-SSM-DEBUG: 16:48:34.653: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 197s (process:2370): libfprint-SSM-DEBUG: 16:48:34.653: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 197s (process:2370): libfprint-SSM-DEBUG: 16:48:34.653: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 197s (process:2370): libfprint-SSM-DEBUG: 16:48:34.653: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 197s (process:2370): libfprint-device-DEBUG: 16:48:34.654: Device reported finger status change: FP_FINGER_STATUS_NEEDED 197s (process:2370): libfprint-synaptics-DEBUG: 16:48:34.654: Finger is now off the sensor 197s (process:2370): libfprint-synaptics-DEBUG: 16:48:34.654: Received message with 0 sequence number 0x91, ignoring! 197s (process:2370): libfprint-SSM-DEBUG: 16:48:34.654: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 197s (process:2370): libfprint-synaptics-DEBUG: 16:48:34.654: interrupt transfer done 197s (process:2370): libfprint-SSM-DEBUG: 16:48:34.654: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 197s (process:2370): libfprint-SSM-DEBUG: 16:48:34.655: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 197s (process:2370): libfprint-SSM-DEBUG: 16:48:34.655: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 197s (process:2370): libfprint-SSM-DEBUG: 16:48:34.655: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 197s (process:2370): libfprint-synaptics-DEBUG: 16:48:34.655: Enrollment was successful! 197s (process:2370): libfprint-device-DEBUG: 16:48:34.655: Device reported enroll completion 197s (process:2370): libfprint-device-DEBUG: 16:48:34.655: Device reported finger status change: FP_FINGER_STATUS_NONE 197s (process:2370): libfprint-device-DEBUG: 16:48:34.655: Print for finger FP_FINGER_UNKNOWN enrolled 197s (process:2370): libfprint-SSM-DEBUG: 16:48:34.656: [synaptics] SYNAPTICS_CMD_NUM_STATES completed successfully 197s (process:2370): libfprint-device-DEBUG: 16:48:34.656: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 197s (process:2370): libfprint-device-DEBUG: 16:48:34.656: Not updating temperature model, device can run continuously! 197s (process:2370): libfprint-device-DEBUG: 16:48:34.656: Not updating temperature model, device can run continuously! 197s (process:2370): libfprint-synaptics-DEBUG: 16:48:34.656: data is 0x117e83c0 197s (process:2370): libfprint-synaptics-DEBUG: 16:48:34.656: 85656999: ../libfprint/drivers/synaptics/synaptics.c:643 197s (process:2370): libfprint-synaptics-DEBUG: 16:48:34.656: sequence number is 5 197s (process:2370): libfprint-SSM-DEBUG: 16:48:34.656: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 197s (process:2370): libfprint-SSM-DEBUG: 16:48:34.656: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 197s (process:2370): libfprint-device-DEBUG: 16:48:34.657: Device reported finger status change: FP_FINGER_STATUS_NEEDED 197s (process:2370): libfprint-synaptics-DEBUG: 16:48:34.657: Place Finger on the Sensor! 197s (process:2370): libfprint-SSM-DEBUG: 16:48:34.657: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 197s (process:2370): libfprint-synaptics-DEBUG: 16:48:34.657: got suspend request 197s (process:2370): libfprint-synaptics-DEBUG: 16:48:34.658: interrupt transfer done 197s (process:2370): libfprint-SSM-DEBUG: 16:48:34.658: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 5 197s (process:2370): libfprint-synaptics-DEBUG: 16:48:34.658: got resume request 197s (process:2370): libfprint-SSM-DEBUG: 16:48:34.658: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 6 197s (process:2370): libfprint-SSM-DEBUG: 16:48:34.658: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 197s (process:2370): libfprint-synaptics-DEBUG: 16:48:34.659: interrupt transfer done 197s (process:2370): libfprint-SSM-DEBUG: 16:48:34.659: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 197s (process:2370): libfprint-SSM-DEBUG: 16:48:34.660: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 197s (process:2370): libfprint-SSM-DEBUG: 16:48:34.660: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 197s (process:2370): libfprint-SSM-DEBUG: 16:48:34.660: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 197s (process:2370): libfprint-device-DEBUG: 16:48:34.660: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 197s (process:2370): libfprint-synaptics-DEBUG: 16:48:34.660: Finger is now on the sensor 197s (process:2370): libfprint-synaptics-DEBUG: 16:48:34.660: Received message with 0 sequence number 0x91, ignoring! 197s (process:2370): libfprint-SSM-DEBUG: 16:48:34.660: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 197s (process:2370): libfprint-synaptics-DEBUG: 16:48:34.661: interrupt transfer done 197s (process:2370): libfprint-SSM-DEBUG: 16:48:34.661: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 197s (process:2370): libfprint-SSM-DEBUG: 16:48:34.661: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 197s (process:2370): libfprint-SSM-DEBUG: 16:48:34.661: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 197s (process:2370): libfprint-SSM-DEBUG: 16:48:34.661: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 197s (process:2370): libfprint-synaptics-DEBUG: 16:48:34.662: Fingerprint image capture complete! 197s (process:2370): libfprint-SSM-DEBUG: 16:48:34.662: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 197s (process:2370): libfprint-synaptics-DEBUG: 16:48:34.662: interrupt transfer done 197s (process:2370): libfprint-SSM-DEBUG: 16:48:34.662: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 197s (process:2370): libfprint-SSM-DEBUG: 16:48:34.663: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 197s (process:2370): libfprint-SSM-DEBUG: 16:48:34.663: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 197s (process:2370): libfprint-SSM-DEBUG: 16:48:34.663: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 197s (process:2370): libfprint-device-DEBUG: 16:48:34.663: Device reported finger status change: FP_FINGER_STATUS_NEEDED 197s (process:2370): libfprint-synaptics-DEBUG: 16:48:34.663: Finger is now off the sensor 197s (process:2370): libfprint-synaptics-DEBUG: 16:48:34.663: Received message with 0 sequence number 0x91, ignoring! 197s (process:2370): libfprint-SSM-DEBUG: 16:48:34.663: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 197s (process:2370): libfprint-synaptics-DEBUG: 16:48:34.664: interrupt transfer done 197s (process:2370): libfprint-SSM-DEBUG: 16:48:34.664: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 197s (process:2370): libfprint-SSM-DEBUG: 16:48:34.664: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 197s (process:2370): libfprint-SSM-DEBUG: 16:48:34.664: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 197s (process:2370): libfprint-SSM-DEBUG: 16:48:34.664: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 197s (process:2370): libfprint-synaptics-DEBUG: 16:48:34.665: Verify was successful! for user: FP1-00000000-0-00000000-nobody finger: 1 score: 61.800000 197s (process:2370): libfprint-device-DEBUG: 16:48:34.665: Device reported verify result 197s (process:2370): libfprint-device-DEBUG: 16:48:34.665: Device reported verify completion 197s (process:2370): libfprint-device-DEBUG: 16:48:34.665: Device reported finger status change: FP_FINGER_STATUS_NONE 197s (process:2370): libfprint-SSM-DEBUG: 16:48:34.665: [synaptics] SYNAPTICS_CMD_NUM_STATES completed successfully 197s (process:2370): libfprint-device-DEBUG: 16:48:34.665: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 197s (process:2370): libfprint-device-DEBUG: 16:48:34.665: Not updating temperature model, device can run continuously! 197s (process:2370): libfprint-synaptics-DEBUG: 16:48:34.665: data is 0x117e83c0 197s (process:2370): libfprint-synaptics-DEBUG: 16:48:34.665: 85666280: ../libfprint/drivers/synaptics/synaptics.c:1120 197s (process:2370): libfprint-synaptics-DEBUG: 16:48:34.665: sequence number is 6 197s (process:2370): libfprint-SSM-DEBUG: 16:48:34.665: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 197s (process:2370): libfprint-SSM-DEBUG: 16:48:34.666: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 197s (process:2370): libfprint-synaptics-DEBUG: 16:48:34.666: Successfully deleted enrolled user 197s (process:2370): libfprint-device-DEBUG: 16:48:34.666: Device reported deletion completion 197s (process:2370): libfprint-SSM-DEBUG: 16:48:34.666: [synaptics] SYNAPTICS_CMD_NUM_STATES completed successfully 197s (process:2370): libfprint-device-DEBUG: 16:48:34.666: Completing action FPI_DEVICE_ACTION_DELETE in idle! 197s (process:2370): libfprint-device-DEBUG: 16:48:34.666: Not updating temperature model, device can run continuously! 197s (process:2370): libfprint-synaptics-DEBUG: 16:48:34.666: 85667422: ../libfprint/drivers/synaptics/synaptics.c:1421 197s (process:2370): libfprint-synaptics-DEBUG: 16:48:34.666: sequence number is 7 197s (process:2370): libfprint-SSM-DEBUG: 16:48:34.666: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 197s (process:2370): libfprint-SSM-DEBUG: 16:48:34.667: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 197s (process:2370): libfprint-synaptics-DEBUG: 16:48:34.668: Fingerprint sensor ready to be powered down 197s (process:2370): libfprint-device-DEBUG: 16:48:34.668: Device reported close completion 197s (process:2370): libfprint-SSM-DEBUG: 16:48:34.668: [synaptics] SYNAPTICS_CMD_NUM_STATES completed successfully 197s (process:2370): libfprint-device-DEBUG: 16:48:34.668: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 197s (process:2370): libfprint-device-DEBUG: 16:48:34.668: Not updating temperature model, device can run continuously! 197s libusb: warning [libusb_exit] device 1.1 still referenced 197s enrolling 197s enroll progress: (<__gi__.FpiDeviceSynaptics object at 0xfab17a384440 (FpiDeviceSynaptics at 0x117eb910)>, 1, None, None, None) 197s enroll progress: (<__gi__.FpiDeviceSynaptics object at 0xfab17a384440 (FpiDeviceSynaptics at 0x117eb910)>, 2, None, None, None) 197s enroll progress: (<__gi__.FpiDeviceSynaptics object at 0xfab17a384440 (FpiDeviceSynaptics at 0x117eb910)>, 3, None, None, None) 197s enroll progress: (<__gi__.FpiDeviceSynaptics object at 0xfab17a384440 (FpiDeviceSynaptics at 0x117eb910)>, 4, None, None, None) 197s enroll progress: (<__gi__.FpiDeviceSynaptics object at 0xfab17a384440 (FpiDeviceSynaptics at 0x117eb910)>, 5, None, None, None) 197s enroll progress: (<__gi__.FpiDeviceSynaptics object at 0xfab17a384440 (FpiDeviceSynaptics at 0x117eb910)>, 5, None, None, GLib.Error('Please try again.', 'fp - device - retry - quark', 0)) 197s enroll progress: (<__gi__.FpiDeviceSynaptics object at 0xfab17a384440 (FpiDeviceSynaptics at 0x117eb910)>, 6, None, None, None) 197s enroll progress: (<__gi__.FpiDeviceSynaptics object at 0xfab17a384440 (FpiDeviceSynaptics at 0x117eb910)>, 7, None, None, None) 197s enroll progress: (<__gi__.FpiDeviceSynaptics object at 0xfab17a384440 (FpiDeviceSynaptics at 0x117eb910)>, 8, None, None, None) 197s enroll done 197s verifying 197s verify done 197s deleting 197s delete done 197s ** (umockdev-run:2366): DEBUG: 16:48:34.679: umockdev.vala:150: Removing test bed /tmp/umockdev.ZWSBK2 197s (umockdev-run:2366): GLib-DEBUG: 16:48:34.682: unsetenv() is not thread-safe and should not be used after threads are created 197s PASS: libfprint-2/driver-synaptics.test 197s Running test: libfprint-2/driver-upektc_img.test 197s ** (umockdev-run:2378): DEBUG: 16:48:34.730: umockdev.vala:123: Created udev test bed /tmp/umockdev.RZP6J2 197s ** (umockdev-run:2378): DEBUG: 16:48:34.730: umockdev.vala:1297: parsing device description for /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.3 197s ** (umockdev-run:2378): DEBUG: 16:48:34.731: umockdev.vala:1366: creating device /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.3 (subsystem usb) 197s ** (umockdev-run:2378): DEBUG: 16:48:34.734: umockdev.vala:1411: create_node_for_device: creating file device /tmp/umockdev.RZP6J2/dev/bus/usb/001/003 197s ** (umockdev-run:2378): DEBUG: 16:48:34.734: umockdev.vala:1297: parsing device description for /devices/pci0000:00/0000:00:1a.0/usb1/1-1 197s ** (umockdev-run:2378): DEBUG: 16:48:34.735: umockdev.vala:1366: creating device /devices/pci0000:00/0000:00:1a.0/usb1/1-1 (subsystem usb) 197s ** (umockdev-run:2378): DEBUG: 16:48:34.737: umockdev.vala:1411: create_node_for_device: creating file device /tmp/umockdev.RZP6J2/dev/bus/usb/001/002 197s ** (umockdev-run:2378): DEBUG: 16:48:34.737: umockdev.vala:1297: parsing device description for /devices/pci0000:00/0000:00:1a.0/usb1 197s ** (umockdev-run:2378): DEBUG: 16:48:34.738: umockdev.vala:1366: creating device /devices/pci0000:00/0000:00:1a.0/usb1 (subsystem usb) 197s ** (umockdev-run:2378): DEBUG: 16:48:34.740: umockdev.vala:1411: create_node_for_device: creating file device /tmp/umockdev.RZP6J2/dev/bus/usb/001/001 197s ** (umockdev-run:2378): DEBUG: 16:48:34.740: umockdev.vala:1297: parsing device description for /devices/pci0000:00/0000:00:1a.0 197s ** (umockdev-run:2378): DEBUG: 16:48:34.740: umockdev.vala:1366: creating device /devices/pci0000:00/0000:00:1a.0 (subsystem pci) 197s (process:2382): libfprint-context-DEBUG: 16:48:34.863: Initializing FpContext (libfprint version 1.94.7+tod1) 197s (process:2382): libfprint-tod-DEBUG: 16:48:34.863: Impossible to load the shared drivers dir Error opening directory “/usr/lib/aarch64-linux-gnu/libfprint-2/tod-1”: No such file or directory 197s (process:2382): libfprint-context-DEBUG: 16:48:34.870: No driver found for USB device 8087:0020 197s (process:2382): libfprint-context-DEBUG: 16:48:34.870: No driver found for USB device 1D6B:0002 197s (process:2382): libfprint-device-DEBUG: 16:48:34.870: Device reported probe completion 197s (process:2382): libfprint-device-DEBUG: 16:48:34.870: Completing action FPI_DEVICE_ACTION_PROBE in idle! 197s (process:2382): libfprint-device-DEBUG: 16:48:34.870: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 197s (process:2382): libfprint-image_device-DEBUG: 16:48:34.885: Image device open completed 197s (process:2382): libfprint-device-DEBUG: 16:48:34.885: Device reported open completion 197s (process:2382): libfprint-device-DEBUG: 16:48:34.885: Completing action FPI_DEVICE_ACTION_OPEN in idle! 197s (process:2382): libfprint-device-DEBUG: 16:48:34.885: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 197s (process:2382): libfprint-device-DEBUG: 16:48:34.885: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 197s (process:2382): libfprint-image_device-DEBUG: 16:48:34.885: Activating image device 197s (process:2382): libfprint-image_device-DEBUG: 16:48:34.885: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING 197s (process:2382): libfprint-SSM-DEBUG: 16:48:34.885: [upektc_img] ACTIVATE_NUM_STATES entering state 0 197s (process:2382): libfprint-SSM-DEBUG: 16:48:34.885: [upektc_img] ACTIVATE_NUM_STATES entering state 1 197s (process:2382): libfprint-SSM-DEBUG: 16:48:34.886: [upektc_img] ACTIVATE_NUM_STATES entering state 2 197s (process:2382): libfprint-SSM-DEBUG: 16:48:34.886: [upektc_img] ACTIVATE_NUM_STATES entering state 3 197s (process:2382): libfprint-SSM-DEBUG: 16:48:34.887: [upektc_img] ACTIVATE_NUM_STATES entering state 4 197s (process:2382): libfprint-SSM-DEBUG: 16:48:34.887: [upektc_img] ACTIVATE_NUM_STATES entering state 5 197s (process:2382): libfprint-SSM-DEBUG: 16:48:34.888: [upektc_img] ACTIVATE_NUM_STATES entering state 6 197s (process:2382): libfprint-SSM-DEBUG: 16:48:34.888: [upektc_img] ACTIVATE_NUM_STATES entering state 7 197s (process:2382): libfprint-SSM-DEBUG: 16:48:34.889: [upektc_img] ACTIVATE_NUM_STATES entering state 8 197s (process:2382): libfprint-SSM-DEBUG: 16:48:34.889: [upektc_img] ACTIVATE_NUM_STATES entering state 9 197s (process:2382): libfprint-SSM-DEBUG: 16:48:34.890: [upektc_img] ACTIVATE_NUM_STATES entering state 10 197s (process:2382): libfprint-SSM-DEBUG: 16:48:34.890: [upektc_img] ACTIVATE_NUM_STATES entering state 11 197s (process:2382): libfprint-upektc_img-DEBUG: 16:48:34.891: Sensor type : TCS4x, width x height: 192 x 512 197s (process:2382): libfprint-SSM-DEBUG: 16:48:34.891: [upektc_img] ACTIVATE_NUM_STATES completed successfully 197s (process:2382): libfprint-image_device-DEBUG: 16:48:34.891: Image device activation completed 197s (process:2382): libfprint-image_device-DEBUG: 16:48:34.891: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE 197s (process:2382): libfprint-image_device-DEBUG: 16:48:34.891: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 197s (process:2382): libfprint-device-DEBUG: 16:48:34.891: Device reported finger status change: FP_FINGER_STATUS_NEEDED 197s (process:2382): libfprint-SSM-DEBUG: 16:48:34.891: [upektc_img] CAPTURE_NUM_STATES entering state 0 197s (process:2382): libfprint-SSM-DEBUG: 16:48:34.891: [upektc_img] CAPTURE_NUM_STATES entering state 1 197s (process:2382): libfprint-upektc_img-DEBUG: 16:48:34.892: request completed, len: 0040 197s (process:2382): libfprint-upektc_img-DEBUG: 16:48:34.892: 18th byte is 0c 197s (process:2382): libfprint-SSM-DEBUG: 16:48:34.892: [upektc_img] CAPTURE_NUM_STATES entering state 3 197s (process:2382): libfprint-SSM-DEBUG: 16:48:34.892: [upektc_img] CAPTURE_NUM_STATES entering state 1 197s (process:2382): libfprint-upektc_img-DEBUG: 16:48:34.893: request completed, len: 0040 197s (process:2382): libfprint-SSM-DEBUG: 16:48:34.893: [upektc_img] CAPTURE_NUM_STATES entering state 4 197s (process:2382): libfprint-SSM-DEBUG: 16:48:34.893: [upektc_img] CAPTURE_NUM_STATES entering state 1 197s (process:2382): libfprint-upektc_img-DEBUG: 16:48:34.894: request completed, len: 0040 197s (process:2382): libfprint-upektc_img-DEBUG: 16:48:34.894: 18th byte is 00 197s (process:2382): libfprint-device-DEBUG: 16:48:34.894: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 197s (process:2382): libfprint-SSM-DEBUG: 16:48:34.894: [upektc_img] CAPTURE_NUM_STATES entering state 3 197s (process:2382): libfprint-SSM-DEBUG: 16:48:34.894: [upektc_img] CAPTURE_NUM_STATES entering state 1 197s (process:2382): libfprint-upektc_img-DEBUG: 16:48:34.895: request completed, len: 0040 197s (process:2382): libfprint-upektc_img-DEBUG: 16:48:34.895: response_size is 2052, actual_length is 64 197s (process:2382): libfprint-upektc_img-DEBUG: 16:48:34.895: Waiting for rest of transfer 197s (process:2382): libfprint-SSM-DEBUG: 16:48:34.895: [upektc_img] CAPTURE_NUM_STATES entering state 1 197s (process:2382): libfprint-upektc_img-DEBUG: 16:48:34.895: request completed, len: 07c4 197s (process:2382): libfprint-image_device-DEBUG: 16:48:34.895: Image device reported finger status: on 197s (process:2382): libfprint-image_device-DEBUG: 16:48:34.895: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 197s (process:2382): libfprint-SSM-DEBUG: 16:48:34.895: [upektc_img] CAPTURE_NUM_STATES entering state 5 197s (process:2382): libfprint-SSM-DEBUG: 16:48:34.896: [upektc_img] CAPTURE_NUM_STATES entering state 1 197s (process:2382): libfprint-upektc_img-DEBUG: 16:48:34.896: request completed, len: 0040 197s (process:2382): libfprint-upektc_img-DEBUG: 16:48:34.896: response_size is 2052, actual_length is 64 197s (process:2382): libfprint-upektc_img-DEBUG: 16:48:34.896: Waiting for rest of transfer 197s (process:2382): libfprint-SSM-DEBUG: 16:48:34.896: [upektc_img] CAPTURE_NUM_STATES entering state 1 197s (process:2382): libfprint-upektc_img-DEBUG: 16:48:34.897: request completed, len: 07c4 197s (process:2382): libfprint-SSM-DEBUG: 16:48:34.897: [upektc_img] CAPTURE_NUM_STATES entering state 5 197s (process:2382): libfprint-SSM-DEBUG: 16:48:34.897: [upektc_img] CAPTURE_NUM_STATES entering state 1 197s (process:2382): libfprint-upektc_img-DEBUG: 16:48:34.897: request completed, len: 0040 197s (process:2382): libfprint-upektc_img-DEBUG: 16:48:34.898: response_size is 2052, actual_length is 64 197s (process:2382): libfprint-upektc_img-DEBUG: 16:48:34.898: Waiting for rest of transfer 197s (process:2382): libfprint-SSM-DEBUG: 16:48:34.898: [upektc_img] CAPTURE_NUM_STATES entering state 1 197s (process:2382): libfprint-upektc_img-DEBUG: 16:48:34.898: request completed, len: 07c4 197s (process:2382): libfprint-SSM-DEBUG: 16:48:34.898: [upektc_img] CAPTURE_NUM_STATES entering state 5 197s (process:2382): libfprint-SSM-DEBUG: 16:48:34.898: [upektc_img] CAPTURE_NUM_STATES entering state 1 197s (process:2382): libfprint-upektc_img-DEBUG: 16:48:34.904: request completed, len: 0040 197s (process:2382): libfprint-upektc_img-DEBUG: 16:48:34.904: response_size is 2052, actual_length is 64 197s (process:2382): libfprint-upektc_img-DEBUG: 16:48:34.904: Waiting for rest of transfer 197s (process:2382): libfprint-SSM-DEBUG: 16:48:34.904: [upektc_img] CAPTURE_NUM_STATES entering state 1 197s (process:2382): libfprint-upektc_img-DEBUG: 16:48:34.905: request completed, len: 07c4 197s (process:2382): libfprint-SSM-DEBUG: 16:48:34.905: [upektc_img] CAPTURE_NUM_STATES entering state 5 197s (process:2382): libfprint-SSM-DEBUG: 16:48:34.905: [upektc_img] CAPTURE_NUM_STATES entering state 1 197s (process:2382): libfprint-upektc_img-DEBUG: 16:48:34.906: request completed, len: 0040 197s (process:2382): libfprint-upektc_img-DEBUG: 16:48:34.906: response_size is 2052, actual_length is 64 197s (process:2382): libfprint-upektc_img-DEBUG: 16:48:34.906: Waiting for rest of transfer 197s (process:2382): libfprint-SSM-DEBUG: 16:48:34.906: [upektc_img] CAPTURE_NUM_STATES entering state 1 197s (process:2382): libfprint-upektc_img-DEBUG: 16:48:34.906: request completed, len: 07c4 197s (process:2382): libfprint-SSM-DEBUG: 16:48:34.906: [upektc_img] CAPTURE_NUM_STATES entering state 5 197s (process:2382): libfprint-SSM-DEBUG: 16:48:34.906: [upektc_img] CAPTURE_NUM_STATES entering state 1 197s (process:2382): libfprint-upektc_img-DEBUG: 16:48:34.907: request completed, len: 0040 197s (process:2382): libfprint-upektc_img-DEBUG: 16:48:34.907: response_size is 2052, actual_length is 64 197s (process:2382): libfprint-upektc_img-DEBUG: 16:48:34.907: Waiting for rest of transfer 197s (process:2382): libfprint-SSM-DEBUG: 16:48:34.907: [upektc_img] CAPTURE_NUM_STATES entering state 1 197s (process:2382): libfprint-upektc_img-DEBUG: 16:48:34.907: request completed, len: 07c4 197s (process:2382): libfprint-SSM-DEBUG: 16:48:34.907: [upektc_img] CAPTURE_NUM_STATES entering state 5 197s (process:2382): libfprint-SSM-DEBUG: 16:48:34.908: [upektc_img] CAPTURE_NUM_STATES entering state 1 197s (process:2382): libfprint-upektc_img-DEBUG: 16:48:34.908: request completed, len: 0040 197s (process:2382): libfprint-upektc_img-DEBUG: 16:48:34.908: response_size is 2052, actual_length is 64 197s (process:2382): libfprint-upektc_img-DEBUG: 16:48:34.908: Waiting for rest of transfer 197s (process:2382): libfprint-SSM-DEBUG: 16:48:34.908: [upektc_img] CAPTURE_NUM_STATES entering state 1 197s (process:2382): libfprint-upektc_img-DEBUG: 16:48:34.909: request completed, len: 07c4 197s (process:2382): libfprint-SSM-DEBUG: 16:48:34.909: [upektc_img] CAPTURE_NUM_STATES entering state 5 197s (process:2382): libfprint-SSM-DEBUG: 16:48:34.909: [upektc_img] CAPTURE_NUM_STATES entering state 1 197s (process:2382): libfprint-upektc_img-DEBUG: 16:48:34.910: request completed, len: 0040 197s (process:2382): libfprint-upektc_img-DEBUG: 16:48:34.910: response_size is 2052, actual_length is 64 197s (process:2382): libfprint-upektc_img-DEBUG: 16:48:34.910: Waiting for rest of transfer 197s (process:2382): libfprint-SSM-DEBUG: 16:48:34.910: [upektc_img] CAPTURE_NUM_STATES entering state 1 197s (process:2382): libfprint-upektc_img-DEBUG: 16:48:34.910: request completed, len: 07c4 197s (process:2382): libfprint-SSM-DEBUG: 16:48:34.910: [upektc_img] CAPTURE_NUM_STATES entering state 5 197s (process:2382): libfprint-SSM-DEBUG: 16:48:34.911: [upektc_img] CAPTURE_NUM_STATES entering state 1 197s (process:2382): libfprint-upektc_img-DEBUG: 16:48:34.911: request completed, len: 0040 197s (process:2382): libfprint-upektc_img-DEBUG: 16:48:34.911: response_size is 2052, actual_length is 64 197s (process:2382): libfprint-upektc_img-DEBUG: 16:48:34.911: Waiting for rest of transfer 197s (process:2382): libfprint-SSM-DEBUG: 16:48:34.911: [upektc_img] CAPTURE_NUM_STATES entering state 1 197s (process:2382): libfprint-upektc_img-DEBUG: 16:48:34.912: request completed, len: 07c4 197s (process:2382): libfprint-SSM-DEBUG: 16:48:34.912: [upektc_img] CAPTURE_NUM_STATES entering state 5 197s (process:2382): libfprint-SSM-DEBUG: 16:48:34.912: [upektc_img] CAPTURE_NUM_STATES entering state 1 197s (process:2382): libfprint-upektc_img-DEBUG: 16:48:34.913: request completed, len: 0040 197s (process:2382): libfprint-upektc_img-DEBUG: 16:48:34.913: response_size is 2052, actual_length is 64 197s (process:2382): libfprint-upektc_img-DEBUG: 16:48:34.913: Waiting for rest of transfer 197s (process:2382): libfprint-SSM-DEBUG: 16:48:34.913: [upektc_img] CAPTURE_NUM_STATES entering state 1 197s (process:2382): libfprint-upektc_img-DEBUG: 16:48:34.913: request completed, len: 07c4 197s (process:2382): libfprint-SSM-DEBUG: 16:48:34.913: [upektc_img] CAPTURE_NUM_STATES entering state 5 197s (process:2382): libfprint-SSM-DEBUG: 16:48:34.913: [upektc_img] CAPTURE_NUM_STATES entering state 1 197s (process:2382): libfprint-upektc_img-DEBUG: 16:48:34.914: request completed, len: 0040 197s (process:2382): libfprint-upektc_img-DEBUG: 16:48:34.914: response_size is 2052, actual_length is 64 197s (process:2382): libfprint-upektc_img-DEBUG: 16:48:34.914: Waiting for rest of transfer 197s (process:2382): libfprint-SSM-DEBUG: 16:48:34.914: [upektc_img] CAPTURE_NUM_STATES entering state 1 197s (process:2382): libfprint-upektc_img-DEBUG: 16:48:34.914: request completed, len: 07c4 197s (process:2382): libfprint-SSM-DEBUG: 16:48:34.914: [upektc_img] CAPTURE_NUM_STATES entering state 5 197s (process:2382): libfprint-SSM-DEBUG: 16:48:34.915: [upektc_img] CAPTURE_NUM_STATES entering state 1 197s (process:2382): libfprint-upektc_img-DEBUG: 16:48:34.915: request completed, len: 0040 197s (process:2382): libfprint-upektc_img-DEBUG: 16:48:34.915: response_size is 2052, actual_length is 64 197s (process:2382): libfprint-upektc_img-DEBUG: 16:48:34.915: Waiting for rest of transfer 197s (process:2382): libfprint-SSM-DEBUG: 16:48:34.915: [upektc_img] CAPTURE_NUM_STATES entering state 1 197s (process:2382): libfprint-upektc_img-DEBUG: 16:48:34.916: request completed, len: 07c4 197s (process:2382): libfprint-SSM-DEBUG: 16:48:34.916: [upektc_img] CAPTURE_NUM_STATES entering state 5 197s (process:2382): libfprint-SSM-DEBUG: 16:48:34.916: [upektc_img] CAPTURE_NUM_STATES entering state 1 197s (process:2382): libfprint-upektc_img-DEBUG: 16:48:34.917: request completed, len: 0040 197s (process:2382): libfprint-upektc_img-DEBUG: 16:48:34.917: response_size is 2052, actual_length is 64 197s (process:2382): libfprint-upektc_img-DEBUG: 16:48:34.917: Waiting for rest of transfer 197s (process:2382): libfprint-SSM-DEBUG: 16:48:34.917: [upektc_img] CAPTURE_NUM_STATES entering state 1 197s (process:2382): libfprint-upektc_img-DEBUG: 16:48:34.917: request completed, len: 07c4 197s (process:2382): libfprint-SSM-DEBUG: 16:48:34.917: [upektc_img] CAPTURE_NUM_STATES entering state 5 197s (process:2382): libfprint-SSM-DEBUG: 16:48:34.918: [upektc_img] CAPTURE_NUM_STATES entering state 1 197s (process:2382): libfprint-upektc_img-DEBUG: 16:48:34.918: request completed, len: 0040 197s (process:2382): libfprint-upektc_img-DEBUG: 16:48:34.918: response_size is 2052, actual_length is 64 197s (process:2382): libfprint-upektc_img-DEBUG: 16:48:34.918: Waiting for rest of transfer 197s (process:2382): libfprint-SSM-DEBUG: 16:48:34.918: [upektc_img] CAPTURE_NUM_STATES entering state 1 197s (process:2382): libfprint-upektc_img-DEBUG: 16:48:34.919: request completed, len: 07c4 197s (process:2382): libfprint-SSM-DEBUG: 16:48:34.919: [upektc_img] CAPTURE_NUM_STATES entering state 5 197s (process:2382): libfprint-SSM-DEBUG: 16:48:34.919: [upektc_img] CAPTURE_NUM_STATES entering state 1 197s (process:2382): libfprint-upektc_img-DEBUG: 16:48:34.919: request completed, len: 0040 197s (process:2382): libfprint-upektc_img-DEBUG: 16:48:34.919: response_size is 2052, actual_length is 64 197s (process:2382): libfprint-upektc_img-DEBUG: 16:48:34.919: Waiting for rest of transfer 197s (process:2382): libfprint-SSM-DEBUG: 16:48:34.919: [upektc_img] CAPTURE_NUM_STATES entering state 1 197s (process:2382): libfprint-upektc_img-DEBUG: 16:48:34.920: request completed, len: 07c4 197s (process:2382): libfprint-SSM-DEBUG: 16:48:34.920: [upektc_img] CAPTURE_NUM_STATES entering state 5 197s (process:2382): libfprint-SSM-DEBUG: 16:48:34.920: [upektc_img] CAPTURE_NUM_STATES entering state 1 197s (process:2382): libfprint-upektc_img-DEBUG: 16:48:34.921: request completed, len: 0040 197s (process:2382): libfprint-upektc_img-DEBUG: 16:48:34.921: response_size is 2052, actual_length is 64 197s (process:2382): libfprint-upektc_img-DEBUG: 16:48:34.921: Waiting for rest of transfer 197s (process:2382): libfprint-SSM-DEBUG: 16:48:34.921: [upektc_img] CAPTURE_NUM_STATES entering state 1 197s (process:2382): libfprint-upektc_img-DEBUG: 16:48:34.921: request completed, len: 07c4 197s (process:2382): libfprint-SSM-DEBUG: 16:48:34.921: [upektc_img] CAPTURE_NUM_STATES entering state 5 197s (process:2382): libfprint-SSM-DEBUG: 16:48:34.922: [upektc_img] CAPTURE_NUM_STATES entering state 1 197s (process:2382): libfprint-upektc_img-DEBUG: 16:48:34.922: request completed, len: 0040 197s (process:2382): libfprint-upektc_img-DEBUG: 16:48:34.922: response_size is 2052, actual_length is 64 197s (process:2382): libfprint-upektc_img-DEBUG: 16:48:34.922: Waiting for rest of transfer 197s (process:2382): libfprint-SSM-DEBUG: 16:48:34.922: [upektc_img] CAPTURE_NUM_STATES entering state 1 197s (process:2382): libfprint-upektc_img-DEBUG: 16:48:34.923: request completed, len: 07c4 197s (process:2382): libfprint-SSM-DEBUG: 16:48:34.923: [upektc_img] CAPTURE_NUM_STATES entering state 5 197s (process:2382): libfprint-SSM-DEBUG: 16:48:34.923: [upektc_img] CAPTURE_NUM_STATES entering state 1 197s (process:2382): libfprint-upektc_img-DEBUG: 16:48:34.924: request completed, len: 0040 197s (process:2382): libfprint-upektc_img-DEBUG: 16:48:34.924: response_size is 2052, actual_length is 64 197s (process:2382): libfprint-upektc_img-DEBUG: 16:48:34.924: Waiting for rest of transfer 197s (process:2382): libfprint-SSM-DEBUG: 16:48:34.924: [upektc_img] CAPTURE_NUM_STATES entering state 1 197s (process:2382): libfprint-upektc_img-DEBUG: 16:48:34.924: request completed, len: 07c4 197s (process:2382): libfprint-SSM-DEBUG: 16:48:34.924: [upektc_img] CAPTURE_NUM_STATES entering state 5 197s (process:2382): libfprint-SSM-DEBUG: 16:48:34.924: [upektc_img] CAPTURE_NUM_STATES entering state 1 197s (process:2382): libfprint-upektc_img-DEBUG: 16:48:34.925: request completed, len: 0040 197s (process:2382): libfprint-upektc_img-DEBUG: 16:48:34.925: response_size is 2052, actual_length is 64 197s (process:2382): libfprint-upektc_img-DEBUG: 16:48:34.925: Waiting for rest of transfer 197s (process:2382): libfprint-SSM-DEBUG: 16:48:34.925: [upektc_img] CAPTURE_NUM_STATES entering state 1 197s (process:2382): libfprint-upektc_img-DEBUG: 16:48:34.925: request completed, len: 07c4 197s (process:2382): libfprint-SSM-DEBUG: 16:48:34.925: [upektc_img] CAPTURE_NUM_STATES entering state 5 197s (process:2382): libfprint-SSM-DEBUG: 16:48:34.926: [upektc_img] CAPTURE_NUM_STATES entering state 1 197s (process:2382): libfprint-upektc_img-DEBUG: 16:48:34.926: request completed, len: 0040 197s (process:2382): libfprint-upektc_img-DEBUG: 16:48:34.926: response_size is 2052, actual_length is 64 197s (process:2382): libfprint-upektc_img-DEBUG: 16:48:34.926: Waiting for rest of transfer 197s (process:2382): libfprint-SSM-DEBUG: 16:48:34.926: [upektc_img] CAPTURE_NUM_STATES entering state 1 197s (process:2382): libfprint-upektc_img-DEBUG: 16:48:34.927: request completed, len: 07c4 197s (process:2382): libfprint-SSM-DEBUG: 16:48:34.927: [upektc_img] CAPTURE_NUM_STATES entering state 5 197s (process:2382): libfprint-SSM-DEBUG: 16:48:34.927: [upektc_img] CAPTURE_NUM_STATES entering state 1 197s (process:2382): libfprint-upektc_img-DEBUG: 16:48:34.928: request completed, len: 0040 197s (process:2382): libfprint-upektc_img-DEBUG: 16:48:34.928: response_size is 2052, actual_length is 64 197s (process:2382): libfprint-upektc_img-DEBUG: 16:48:34.928: Waiting for rest of transfer 197s (process:2382): libfprint-SSM-DEBUG: 16:48:34.928: [upektc_img] CAPTURE_NUM_STATES entering state 1 197s (process:2382): libfprint-upektc_img-DEBUG: 16:48:34.928: request completed, len: 07c4 197s (process:2382): libfprint-SSM-DEBUG: 16:48:34.928: [upektc_img] CAPTURE_NUM_STATES entering state 5 197s (process:2382): libfprint-SSM-DEBUG: 16:48:34.929: [upektc_img] CAPTURE_NUM_STATES entering state 1 197s (process:2382): libfprint-upektc_img-DEBUG: 16:48:34.929: request completed, len: 0040 197s (process:2382): libfprint-upektc_img-DEBUG: 16:48:34.929: response_size is 2052, actual_length is 64 197s (process:2382): libfprint-upektc_img-DEBUG: 16:48:34.929: Waiting for rest of transfer 197s (process:2382): libfprint-SSM-DEBUG: 16:48:34.929: [upektc_img] CAPTURE_NUM_STATES entering state 1 197s (process:2382): libfprint-upektc_img-DEBUG: 16:48:34.930: request completed, len: 07c4 197s (process:2382): libfprint-SSM-DEBUG: 16:48:34.930: [upektc_img] CAPTURE_NUM_STATES entering state 5 197s (process:2382): libfprint-SSM-DEBUG: 16:48:34.930: [upektc_img] CAPTURE_NUM_STATES entering state 1 197s (process:2382): libfprint-upektc_img-DEBUG: 16:48:34.931: request completed, len: 0040 197s (process:2382): libfprint-upektc_img-DEBUG: 16:48:34.931: response_size is 2052, actual_length is 64 197s (process:2382): libfprint-upektc_img-DEBUG: 16:48:34.931: Waiting for rest of transfer 197s (process:2382): libfprint-SSM-DEBUG: 16:48:34.931: [upektc_img] CAPTURE_NUM_STATES entering state 1 197s (process:2382): libfprint-upektc_img-DEBUG: 16:48:34.931: request completed, len: 07c4 197s (process:2382): libfprint-SSM-DEBUG: 16:48:34.931: [upektc_img] CAPTURE_NUM_STATES entering state 5 197s (process:2382): libfprint-SSM-DEBUG: 16:48:34.931: [upektc_img] CAPTURE_NUM_STATES entering state 1 197s (process:2382): libfprint-upektc_img-DEBUG: 16:48:34.932: request completed, len: 0040 197s (process:2382): libfprint-upektc_img-DEBUG: 16:48:34.932: response_size is 2052, actual_length is 64 197s (process:2382): libfprint-upektc_img-DEBUG: 16:48:34.932: Waiting for rest of transfer 197s (process:2382): libfprint-SSM-DEBUG: 16:48:34.932: [upektc_img] CAPTURE_NUM_STATES entering state 1 197s (process:2382): libfprint-upektc_img-DEBUG: 16:48:34.932: request completed, len: 07c4 197s (process:2382): libfprint-SSM-DEBUG: 16:48:34.932: [upektc_img] CAPTURE_NUM_STATES entering state 5 197s (process:2382): libfprint-SSM-DEBUG: 16:48:34.933: [upektc_img] CAPTURE_NUM_STATES entering state 1 197s (process:2382): libfprint-upektc_img-DEBUG: 16:48:34.933: request completed, len: 0040 197s (process:2382): libfprint-upektc_img-DEBUG: 16:48:34.933: response_size is 2052, actual_length is 64 197s (process:2382): libfprint-upektc_img-DEBUG: 16:48:34.933: Waiting for rest of transfer 197s (process:2382): libfprint-SSM-DEBUG: 16:48:34.933: [upektc_img] CAPTURE_NUM_STATES entering state 1 197s (process:2382): libfprint-upektc_img-DEBUG: 16:48:34.934: request completed, len: 07c4 197s (process:2382): libfprint-SSM-DEBUG: 16:48:34.934: [upektc_img] CAPTURE_NUM_STATES entering state 5 197s (process:2382): libfprint-SSM-DEBUG: 16:48:34.934: [upektc_img] CAPTURE_NUM_STATES entering state 1 197s (process:2382): libfprint-upektc_img-DEBUG: 16:48:34.935: request completed, len: 0040 197s (process:2382): libfprint-upektc_img-DEBUG: 16:48:34.935: response_size is 2052, actual_length is 64 197s (process:2382): libfprint-upektc_img-DEBUG: 16:48:34.935: Waiting for rest of transfer 197s (process:2382): libfprint-SSM-DEBUG: 16:48:34.935: [upektc_img] CAPTURE_NUM_STATES entering state 1 197s (process:2382): libfprint-upektc_img-DEBUG: 16:48:34.935: request completed, len: 07c4 197s (process:2382): libfprint-SSM-DEBUG: 16:48:34.935: [upektc_img] CAPTURE_NUM_STATES entering state 5 197s (process:2382): libfprint-SSM-DEBUG: 16:48:34.936: [upektc_img] CAPTURE_NUM_STATES entering state 1 197s (process:2382): libfprint-upektc_img-DEBUG: 16:48:34.936: request completed, len: 0040 197s (process:2382): libfprint-upektc_img-DEBUG: 16:48:34.936: response_size is 2052, actual_length is 64 197s (process:2382): libfprint-upektc_img-DEBUG: 16:48:34.936: Waiting for rest of transfer 197s (process:2382): libfprint-SSM-DEBUG: 16:48:34.936: [upektc_img] CAPTURE_NUM_STATES entering state 1 197s (process:2382): libfprint-upektc_img-DEBUG: 16:48:34.936: request completed, len: 07c4 197s (process:2382): libfprint-SSM-DEBUG: 16:48:34.936: [upektc_img] CAPTURE_NUM_STATES entering state 5 197s (process:2382): libfprint-SSM-DEBUG: 16:48:34.937: [upektc_img] CAPTURE_NUM_STATES entering state 1 197s (process:2382): libfprint-upektc_img-DEBUG: 16:48:34.937: request completed, len: 0040 197s (process:2382): libfprint-upektc_img-DEBUG: 16:48:34.937: response_size is 186, actual_length is 64 197s (process:2382): libfprint-upektc_img-DEBUG: 16:48:34.937: Waiting for rest of transfer 197s (process:2382): libfprint-SSM-DEBUG: 16:48:34.937: [upektc_img] CAPTURE_NUM_STATES entering state 1 197s (process:2382): libfprint-upektc_img-DEBUG: 16:48:34.938: request completed, len: 007a 197s (process:2382): libfprint-upektc_img-DEBUG: 16:48:34.938: Image size is 55296 197s (process:2382): libfprint-image_device-DEBUG: 16:48:34.938: Image device captured an image 197s (process:2382): libfprint-image_device-DEBUG: 16:48:34.938: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 197s (process:2382): libfprint-device-DEBUG: 16:48:34.938: Device reported finger status change: FP_FINGER_STATUS_PRESENT 197s (process:2382): libfprint-device-DEBUG: 16:48:34.938: Device reported finger status change: FP_FINGER_STATUS_NONE 197s (process:2382): libfprint-image_device-DEBUG: 16:48:34.938: Image device reported finger status: off 197s (process:2382): libfprint-image_device-DEBUG: 16:48:34.938: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 197s (process:2382): libfprint-image_device-DEBUG: 16:48:34.938: Deactivating image device 197s (process:2382): libfprint-image_device-DEBUG: 16:48:34.938: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_DEACTIVATING 197s (process:2382): libfprint-SSM-DEBUG: 16:48:34.938: [upektc_img] CAPTURE_NUM_STATES completed successfully 197s (process:2382): libfprint-SSM-DEBUG: 16:48:34.938: [upektc_img] DEACTIVATE_NUM_STATES entering state 0 197s (process:2382): libfprint-SSM-DEBUG: 16:48:34.939: [upektc_img] DEACTIVATE_NUM_STATES entering state 1 197s (process:2382): libfprint-SSM-DEBUG: 16:48:34.940: [upektc_img] DEACTIVATE_NUM_STATES completed successfully 197s (process:2382): libfprint-upektc_img-DEBUG: 16:48:34.940: Deactivate completed 197s (process:2382): libfprint-image_device-DEBUG: 16:48:34.940: Image device deactivation completed 197s (process:2382): libfprint-image_device-DEBUG: 16:48:34.940: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE 197s (process:2382): libfprint-image-DEBUG: 16:48:34.948: Minutiae scan completed in 0.010152 secs 197s (process:2382): libfprint-device-DEBUG: 16:48:34.948: Device reported capture completion 197s (process:2382): libfprint-device-DEBUG: 16:48:34.948: Completing action FPI_DEVICE_ACTION_CAPTURE in idle! 197s (process:2382): libfprint-device-DEBUG: 16:48:34.948: Updated temperature model after 0.06 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 197s (process:2382): libfprint-image_device-DEBUG: 16:48:34.949: Image device close completed 197s (process:2382): libfprint-device-DEBUG: 16:48:34.949: Device reported close completion 197s (process:2382): libfprint-device-DEBUG: 16:48:34.949: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 197s (process:2382): libfprint-device-DEBUG: 16:48:34.949: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 198s ** (umockdev-run:2378): DEBUG: 16:48:35.042: umockdev.vala:150: Removing test bed /tmp/umockdev.RZP6J2 198s (umockdev-run:2378): GLib-DEBUG: 16:48:35.047: unsetenv() is not thread-safe and should not be used after threads are created 198s Comparing PNGs /tmp/libfprint-umockdev-test-3s1fbs5x/capture.png and /usr/share/installed-tests/libfprint-2/upektc_img/capture.png 198s PASS: libfprint-2/driver-upektc_img.test 198s Running test: libfprint-2/driver-egis0570.test 198s ** (umockdev-run:2391): DEBUG: 16:48:35.149: umockdev.vala:123: Created udev test bed /tmp/umockdev.OZQGK2 198s ** (umockdev-run:2391): DEBUG: 16:48:35.149: umockdev.vala:1297: parsing device description for /devices/pci0000:00/0000:00:14.0/usb1/1-9 198s ** (umockdev-run:2391): DEBUG: 16:48:35.150: umockdev.vala:1366: creating device /devices/pci0000:00/0000:00:14.0/usb1/1-9 (subsystem usb) 198s ** (umockdev-run:2391): DEBUG: 16:48:35.153: umockdev.vala:1411: create_node_for_device: creating file device /tmp/umockdev.OZQGK2/dev/bus/usb/001/005 198s ** (umockdev-run:2391): DEBUG: 16:48:35.153: umockdev.vala:1297: parsing device description for /devices/pci0000:00/0000:00:14.0/usb1 198s ** (umockdev-run:2391): DEBUG: 16:48:35.153: umockdev.vala:1366: creating device /devices/pci0000:00/0000:00:14.0/usb1 (subsystem usb) 198s ** (umockdev-run:2391): DEBUG: 16:48:35.155: umockdev.vala:1411: create_node_for_device: creating file device /tmp/umockdev.OZQGK2/dev/bus/usb/001/001 198s ** (umockdev-run:2391): DEBUG: 16:48:35.155: umockdev.vala:1297: parsing device description for /devices/pci0000:00/0000:00:14.0 198s ** (umockdev-run:2391): DEBUG: 16:48:35.156: umockdev.vala:1366: creating device /devices/pci0000:00/0000:00:14.0 (subsystem pci) 198s (process:2395): libfprint-context-DEBUG: 16:48:35.230: Initializing FpContext (libfprint version 1.94.7+tod1) 198s (process:2395): libfprint-tod-DEBUG: 16:48:35.230: Impossible to load the shared drivers dir Error opening directory “/usr/lib/aarch64-linux-gnu/libfprint-2/tod-1”: No such file or directory 198s (process:2395): libfprint-context-DEBUG: 16:48:35.232: No driver found for USB device 1D6B:0002 198s (process:2395): libfprint-device-DEBUG: 16:48:35.232: Device reported probe completion 198s (process:2395): libfprint-device-DEBUG: 16:48:35.233: Completing action FPI_DEVICE_ACTION_PROBE in idle! 198s (process:2395): libfprint-device-DEBUG: 16:48:35.233: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 198s (process:2395): libfprint-image_device-DEBUG: 16:48:35.235: Image device open completed 198s (process:2395): libfprint-device-DEBUG: 16:48:35.235: Device reported open completion 198s (process:2395): libfprint-device-DEBUG: 16:48:35.235: Completing action FPI_DEVICE_ACTION_OPEN in idle! 198s (process:2395): libfprint-device-DEBUG: 16:48:35.235: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 198s (process:2395): libfprint-device-DEBUG: 16:48:35.235: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 198s (process:2395): libfprint-image_device-DEBUG: 16:48:35.235: Activating image device 198s (process:2395): libfprint-image_device-DEBUG: 16:48:35.235: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.235: [egis0570] SM_STATES_NUM entering state 0 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.235: [egis0570] SM_STATES_NUM entering state 1 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.235: [egis0570] SM_STATES_NUM entering state 2 198s (process:2395): libfprint-image_device-DEBUG: 16:48:35.236: Image device activation completed 198s (process:2395): libfprint-image_device-DEBUG: 16:48:35.236: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE 198s (process:2395): libfprint-image_device-DEBUG: 16:48:35.236: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 198s (process:2395): libfprint-device-DEBUG: 16:48:35.236: Device reported finger status change: FP_FINGER_STATUS_NEEDED 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.236: [egis0570] SM_STATES_NUM entering state 3 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.236: [egis0570] SM_STATES_NUM entering state 2 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.237: [egis0570] SM_STATES_NUM entering state 3 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.237: [egis0570] SM_STATES_NUM entering state 2 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.238: [egis0570] SM_STATES_NUM entering state 3 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.238: [egis0570] SM_STATES_NUM entering state 2 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.239: [egis0570] SM_STATES_NUM entering state 3 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.239: [egis0570] SM_STATES_NUM entering state 2 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.240: [egis0570] SM_STATES_NUM entering state 3 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.240: [egis0570] SM_STATES_NUM entering state 2 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.241: [egis0570] SM_STATES_NUM entering state 3 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.241: [egis0570] SM_STATES_NUM entering state 2 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.242: [egis0570] SM_STATES_NUM entering state 3 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.242: [egis0570] SM_STATES_NUM entering state 2 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.242: [egis0570] SM_STATES_NUM entering state 3 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.243: [egis0570] SM_STATES_NUM entering state 2 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.243: [egis0570] SM_STATES_NUM entering state 3 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.244: [egis0570] SM_STATES_NUM entering state 2 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.244: [egis0570] SM_STATES_NUM entering state 3 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.244: [egis0570] SM_STATES_NUM entering state 2 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.245: [egis0570] SM_STATES_NUM entering state 3 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.245: [egis0570] SM_STATES_NUM entering state 2 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.246: [egis0570] SM_STATES_NUM entering state 3 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.246: [egis0570] SM_STATES_NUM entering state 2 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.247: [egis0570] SM_STATES_NUM entering state 3 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.247: [egis0570] SM_STATES_NUM entering state 2 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.248: [egis0570] SM_STATES_NUM entering state 3 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.248: [egis0570] SM_STATES_NUM entering state 2 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.249: [egis0570] SM_STATES_NUM entering state 3 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.249: [egis0570] SM_STATES_NUM entering state 2 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.249: [egis0570] SM_STATES_NUM entering state 3 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.250: [egis0570] SM_STATES_NUM entering state 2 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.250: [egis0570] SM_STATES_NUM entering state 3 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.251: [egis0570] SM_STATES_NUM entering state 2 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.251: [egis0570] SM_STATES_NUM entering state 3 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.251: [egis0570] SM_STATES_NUM entering state 2 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.252: [egis0570] SM_STATES_NUM entering state 3 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.252: [egis0570] SM_STATES_NUM entering state 2 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.253: [egis0570] SM_STATES_NUM entering state 3 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.253: [egis0570] SM_STATES_NUM entering state 2 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.254: [egis0570] SM_STATES_NUM entering state 3 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.254: [egis0570] SM_STATES_NUM entering state 2 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.255: [egis0570] SM_STATES_NUM entering state 3 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.255: [egis0570] SM_STATES_NUM entering state 2 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.256: [egis0570] SM_STATES_NUM entering state 3 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.256: [egis0570] SM_STATES_NUM entering state 4 198s (process:2395): libfprint-image_device-DEBUG: 16:48:35.256: Image device reported finger status: off 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.256: [egis0570] SM_STATES_NUM entering state 5 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.257: [egis0570] SM_STATES_NUM entering state 1 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.257: [egis0570] SM_STATES_NUM entering state 2 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.257: [egis0570] SM_STATES_NUM entering state 3 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.257: [egis0570] SM_STATES_NUM entering state 2 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.258: [egis0570] SM_STATES_NUM entering state 3 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.258: [egis0570] SM_STATES_NUM entering state 2 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.259: [egis0570] SM_STATES_NUM entering state 3 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.259: [egis0570] SM_STATES_NUM entering state 2 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.260: [egis0570] SM_STATES_NUM entering state 3 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.260: [egis0570] SM_STATES_NUM entering state 4 198s (process:2395): libfprint-egis0570-DEBUG: 16:48:35.260: Finger status (picture number, mean) : 0 , 0 198s (process:2395): libfprint-egis0570-DEBUG: 16:48:35.260: Finger status (picture number, mean) : 1 , 0 198s (process:2395): libfprint-egis0570-DEBUG: 16:48:35.260: Finger status (picture number, mean) : 2 , 0 198s (process:2395): libfprint-egis0570-DEBUG: 16:48:35.260: Finger status (picture number, mean) : 3 , 0 198s (process:2395): libfprint-egis0570-DEBUG: 16:48:35.260: Finger status (picture number, mean) : 4 , 0 198s (process:2395): libfprint-image_device-DEBUG: 16:48:35.260: Image device reported finger status: off 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.260: [egis0570] SM_STATES_NUM entering state 5 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.260: [egis0570] SM_STATES_NUM entering state 1 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.260: [egis0570] SM_STATES_NUM entering state 2 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.260: [egis0570] SM_STATES_NUM entering state 3 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.261: [egis0570] SM_STATES_NUM entering state 2 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.261: [egis0570] SM_STATES_NUM entering state 3 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.262: [egis0570] SM_STATES_NUM entering state 2 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.262: [egis0570] SM_STATES_NUM entering state 3 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.262: [egis0570] SM_STATES_NUM entering state 2 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.263: [egis0570] SM_STATES_NUM entering state 3 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.263: [egis0570] SM_STATES_NUM entering state 4 198s (process:2395): libfprint-egis0570-DEBUG: 16:48:35.264: Finger status (picture number, mean) : 0 , 0 198s (process:2395): libfprint-egis0570-DEBUG: 16:48:35.264: Finger status (picture number, mean) : 1 , 0 198s (process:2395): libfprint-egis0570-DEBUG: 16:48:35.264: Finger status (picture number, mean) : 2 , 0 198s (process:2395): libfprint-egis0570-DEBUG: 16:48:35.264: Finger status (picture number, mean) : 3 , 0 198s (process:2395): libfprint-egis0570-DEBUG: 16:48:35.264: Finger status (picture number, mean) : 4 , 0 198s (process:2395): libfprint-image_device-DEBUG: 16:48:35.264: Image device reported finger status: off 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.264: [egis0570] SM_STATES_NUM entering state 5 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.264: [egis0570] SM_STATES_NUM entering state 1 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.264: [egis0570] SM_STATES_NUM entering state 2 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.264: [egis0570] SM_STATES_NUM entering state 3 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.264: [egis0570] SM_STATES_NUM entering state 2 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.265: [egis0570] SM_STATES_NUM entering state 3 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.265: [egis0570] SM_STATES_NUM entering state 2 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.266: [egis0570] SM_STATES_NUM entering state 3 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.266: [egis0570] SM_STATES_NUM entering state 2 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.267: [egis0570] SM_STATES_NUM entering state 3 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.267: [egis0570] SM_STATES_NUM entering state 4 198s (process:2395): libfprint-egis0570-DEBUG: 16:48:35.267: Finger status (picture number, mean) : 0 , 0 198s (process:2395): libfprint-egis0570-DEBUG: 16:48:35.267: Finger status (picture number, mean) : 1 , 0 198s (process:2395): libfprint-egis0570-DEBUG: 16:48:35.267: Finger status (picture number, mean) : 2 , 0 198s (process:2395): libfprint-egis0570-DEBUG: 16:48:35.267: Finger status (picture number, mean) : 3 , 0 198s (process:2395): libfprint-egis0570-DEBUG: 16:48:35.267: Finger status (picture number, mean) : 4 , 0 198s (process:2395): libfprint-image_device-DEBUG: 16:48:35.267: Image device reported finger status: off 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.267: [egis0570] SM_STATES_NUM entering state 5 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.267: [egis0570] SM_STATES_NUM entering state 1 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.267: [egis0570] SM_STATES_NUM entering state 2 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.268: [egis0570] SM_STATES_NUM entering state 3 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.268: [egis0570] SM_STATES_NUM entering state 2 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.269: [egis0570] SM_STATES_NUM entering state 3 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.269: [egis0570] SM_STATES_NUM entering state 2 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.269: [egis0570] SM_STATES_NUM entering state 3 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.270: [egis0570] SM_STATES_NUM entering state 2 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.270: [egis0570] SM_STATES_NUM entering state 3 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.270: [egis0570] SM_STATES_NUM entering state 4 198s (process:2395): libfprint-egis0570-DEBUG: 16:48:35.271: Finger status (picture number, mean) : 0 , 0 198s (process:2395): libfprint-egis0570-DEBUG: 16:48:35.271: Finger status (picture number, mean) : 1 , 0 198s (process:2395): libfprint-egis0570-DEBUG: 16:48:35.271: Finger status (picture number, mean) : 2 , 0 198s (process:2395): libfprint-egis0570-DEBUG: 16:48:35.271: Finger status (picture number, mean) : 3 , 0 198s (process:2395): libfprint-egis0570-DEBUG: 16:48:35.271: Finger status (picture number, mean) : 4 , 0 198s (process:2395): libfprint-image_device-DEBUG: 16:48:35.271: Image device reported finger status: off 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.271: [egis0570] SM_STATES_NUM entering state 5 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.271: [egis0570] SM_STATES_NUM entering state 1 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.271: [egis0570] SM_STATES_NUM entering state 2 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.271: [egis0570] SM_STATES_NUM entering state 3 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.272: [egis0570] SM_STATES_NUM entering state 2 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.272: [egis0570] SM_STATES_NUM entering state 3 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.272: [egis0570] SM_STATES_NUM entering state 2 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.273: [egis0570] SM_STATES_NUM entering state 3 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.273: [egis0570] SM_STATES_NUM entering state 2 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.274: [egis0570] SM_STATES_NUM entering state 3 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.274: [egis0570] SM_STATES_NUM entering state 4 198s (process:2395): libfprint-egis0570-DEBUG: 16:48:35.274: Finger status (picture number, mean) : 0 , 0 198s (process:2395): libfprint-egis0570-DEBUG: 16:48:35.275: Finger status (picture number, mean) : 1 , 0 198s (process:2395): libfprint-egis0570-DEBUG: 16:48:35.275: Finger status (picture number, mean) : 2 , 0 198s (process:2395): libfprint-egis0570-DEBUG: 16:48:35.275: Finger status (picture number, mean) : 3 , 0 198s (process:2395): libfprint-egis0570-DEBUG: 16:48:35.275: Finger status (picture number, mean) : 4 , 0 198s (process:2395): libfprint-image_device-DEBUG: 16:48:35.275: Image device reported finger status: off 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.275: [egis0570] SM_STATES_NUM entering state 5 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.275: [egis0570] SM_STATES_NUM entering state 1 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.275: [egis0570] SM_STATES_NUM entering state 2 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.275: [egis0570] SM_STATES_NUM entering state 3 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.275: [egis0570] SM_STATES_NUM entering state 2 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.276: [egis0570] SM_STATES_NUM entering state 3 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.276: [egis0570] SM_STATES_NUM entering state 2 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.277: [egis0570] SM_STATES_NUM entering state 3 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.277: [egis0570] SM_STATES_NUM entering state 2 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.278: [egis0570] SM_STATES_NUM entering state 3 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.278: [egis0570] SM_STATES_NUM entering state 4 198s (process:2395): libfprint-egis0570-DEBUG: 16:48:35.278: Finger status (picture number, mean) : 0 , 0 198s (process:2395): libfprint-egis0570-DEBUG: 16:48:35.278: Finger status (picture number, mean) : 1 , 0 198s (process:2395): libfprint-egis0570-DEBUG: 16:48:35.278: Finger status (picture number, mean) : 2 , 0 198s (process:2395): libfprint-egis0570-DEBUG: 16:48:35.278: Finger status (picture number, mean) : 3 , 0 198s (process:2395): libfprint-egis0570-DEBUG: 16:48:35.278: Finger status (picture number, mean) : 4 , 0 198s (process:2395): libfprint-image_device-DEBUG: 16:48:35.278: Image device reported finger status: off 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.278: [egis0570] SM_STATES_NUM entering state 5 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.278: [egis0570] SM_STATES_NUM entering state 1 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.278: [egis0570] SM_STATES_NUM entering state 2 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.279: [egis0570] SM_STATES_NUM entering state 3 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.279: [egis0570] SM_STATES_NUM entering state 2 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.279: [egis0570] SM_STATES_NUM entering state 3 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.280: [egis0570] SM_STATES_NUM entering state 2 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.280: [egis0570] SM_STATES_NUM entering state 3 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.281: [egis0570] SM_STATES_NUM entering state 2 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.281: [egis0570] SM_STATES_NUM entering state 3 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.281: [egis0570] SM_STATES_NUM entering state 4 198s (process:2395): libfprint-egis0570-DEBUG: 16:48:35.282: Finger status (picture number, mean) : 0 , 0 198s (process:2395): libfprint-egis0570-DEBUG: 16:48:35.282: Finger status (picture number, mean) : 1 , 0 198s (process:2395): libfprint-egis0570-DEBUG: 16:48:35.282: Finger status (picture number, mean) : 2 , 0 198s (process:2395): libfprint-egis0570-DEBUG: 16:48:35.282: Finger status (picture number, mean) : 3 , 0 198s (process:2395): libfprint-egis0570-DEBUG: 16:48:35.282: Finger status (picture number, mean) : 4 , 0 198s (process:2395): libfprint-image_device-DEBUG: 16:48:35.282: Image device reported finger status: off 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.282: [egis0570] SM_STATES_NUM entering state 5 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.282: [egis0570] SM_STATES_NUM entering state 1 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.282: [egis0570] SM_STATES_NUM entering state 2 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.282: [egis0570] SM_STATES_NUM entering state 3 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.282: [egis0570] SM_STATES_NUM entering state 2 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.283: [egis0570] SM_STATES_NUM entering state 3 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.283: [egis0570] SM_STATES_NUM entering state 2 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.284: [egis0570] SM_STATES_NUM entering state 3 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.284: [egis0570] SM_STATES_NUM entering state 2 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.285: [egis0570] SM_STATES_NUM entering state 3 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.285: [egis0570] SM_STATES_NUM entering state 4 198s (process:2395): libfprint-egis0570-DEBUG: 16:48:35.285: Finger status (picture number, mean) : 0 , 0 198s (process:2395): libfprint-egis0570-DEBUG: 16:48:35.285: Finger status (picture number, mean) : 1 , 0 198s (process:2395): libfprint-egis0570-DEBUG: 16:48:35.285: Finger status (picture number, mean) : 2 , 0 198s (process:2395): libfprint-egis0570-DEBUG: 16:48:35.285: Finger status (picture number, mean) : 3 , 0 198s (process:2395): libfprint-egis0570-DEBUG: 16:48:35.285: Finger status (picture number, mean) : 4 , 0 198s (process:2395): libfprint-image_device-DEBUG: 16:48:35.285: Image device reported finger status: off 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.285: [egis0570] SM_STATES_NUM entering state 5 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.285: [egis0570] SM_STATES_NUM entering state 1 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.285: [egis0570] SM_STATES_NUM entering state 2 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.286: [egis0570] SM_STATES_NUM entering state 3 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.286: [egis0570] SM_STATES_NUM entering state 2 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.287: [egis0570] SM_STATES_NUM entering state 3 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.287: [egis0570] SM_STATES_NUM entering state 2 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.288: [egis0570] SM_STATES_NUM entering state 3 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.288: [egis0570] SM_STATES_NUM entering state 2 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.289: [egis0570] SM_STATES_NUM entering state 3 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.289: [egis0570] SM_STATES_NUM entering state 4 198s (process:2395): libfprint-egis0570-DEBUG: 16:48:35.289: Finger status (picture number, mean) : 0 , 0 198s (process:2395): libfprint-egis0570-DEBUG: 16:48:35.289: Finger status (picture number, mean) : 1 , 0 198s (process:2395): libfprint-egis0570-DEBUG: 16:48:35.289: Finger status (picture number, mean) : 2 , 0 198s (process:2395): libfprint-egis0570-DEBUG: 16:48:35.289: Finger status (picture number, mean) : 3 , 0 198s (process:2395): libfprint-egis0570-DEBUG: 16:48:35.289: Finger status (picture number, mean) : 4 , 0 198s (process:2395): libfprint-image_device-DEBUG: 16:48:35.289: Image device reported finger status: off 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.289: [egis0570] SM_STATES_NUM entering state 5 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.289: [egis0570] SM_STATES_NUM entering state 1 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.289: [egis0570] SM_STATES_NUM entering state 2 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.290: [egis0570] SM_STATES_NUM entering state 3 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.290: [egis0570] SM_STATES_NUM entering state 2 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.291: [egis0570] SM_STATES_NUM entering state 3 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.291: [egis0570] SM_STATES_NUM entering state 2 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.291: [egis0570] SM_STATES_NUM entering state 3 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.292: [egis0570] SM_STATES_NUM entering state 2 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.292: [egis0570] SM_STATES_NUM entering state 3 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.292: [egis0570] SM_STATES_NUM entering state 4 198s (process:2395): libfprint-egis0570-DEBUG: 16:48:35.293: Finger status (picture number, mean) : 0 , 0 198s (process:2395): libfprint-egis0570-DEBUG: 16:48:35.293: Finger status (picture number, mean) : 1 , 0 198s (process:2395): libfprint-egis0570-DEBUG: 16:48:35.293: Finger status (picture number, mean) : 2 , 0 198s (process:2395): libfprint-egis0570-DEBUG: 16:48:35.293: Finger status (picture number, mean) : 3 , 0 198s (process:2395): libfprint-egis0570-DEBUG: 16:48:35.293: Finger status (picture number, mean) : 4 , 0 198s (process:2395): libfprint-image_device-DEBUG: 16:48:35.293: Image device reported finger status: off 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.293: [egis0570] SM_STATES_NUM entering state 5 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.293: [egis0570] SM_STATES_NUM entering state 1 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.293: [egis0570] SM_STATES_NUM entering state 2 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.293: [egis0570] SM_STATES_NUM entering state 3 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.294: [egis0570] SM_STATES_NUM entering state 2 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.294: [egis0570] SM_STATES_NUM entering state 3 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.294: [egis0570] SM_STATES_NUM entering state 2 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.295: [egis0570] SM_STATES_NUM entering state 3 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.295: [egis0570] SM_STATES_NUM entering state 2 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.296: [egis0570] SM_STATES_NUM entering state 3 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.296: [egis0570] SM_STATES_NUM entering state 4 198s (process:2395): libfprint-egis0570-DEBUG: 16:48:35.297: Finger status (picture number, mean) : 0 , 0 198s (process:2395): libfprint-egis0570-DEBUG: 16:48:35.297: Finger status (picture number, mean) : 1 , 0 198s (process:2395): libfprint-egis0570-DEBUG: 16:48:35.297: Finger status (picture number, mean) : 2 , 0 198s (process:2395): libfprint-egis0570-DEBUG: 16:48:35.297: Finger status (picture number, mean) : 3 , 0 198s (process:2395): libfprint-egis0570-DEBUG: 16:48:35.297: Finger status (picture number, mean) : 4 , 0 198s (process:2395): libfprint-image_device-DEBUG: 16:48:35.297: Image device reported finger status: off 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.297: [egis0570] SM_STATES_NUM entering state 5 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.297: [egis0570] SM_STATES_NUM entering state 1 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.297: [egis0570] SM_STATES_NUM entering state 2 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.297: [egis0570] SM_STATES_NUM entering state 3 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.297: [egis0570] SM_STATES_NUM entering state 2 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.298: [egis0570] SM_STATES_NUM entering state 3 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.298: [egis0570] SM_STATES_NUM entering state 2 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.299: [egis0570] SM_STATES_NUM entering state 3 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.299: [egis0570] SM_STATES_NUM entering state 2 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.300: [egis0570] SM_STATES_NUM entering state 3 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.300: [egis0570] SM_STATES_NUM entering state 4 198s (process:2395): libfprint-egis0570-DEBUG: 16:48:35.300: Finger status (picture number, mean) : 0 , 0 198s (process:2395): libfprint-egis0570-DEBUG: 16:48:35.300: Finger status (picture number, mean) : 1 , 0 198s (process:2395): libfprint-egis0570-DEBUG: 16:48:35.300: Finger status (picture number, mean) : 2 , 0 198s (process:2395): libfprint-egis0570-DEBUG: 16:48:35.300: Finger status (picture number, mean) : 3 , 0 198s (process:2395): libfprint-egis0570-DEBUG: 16:48:35.300: Finger status (picture number, mean) : 4 , 0 198s (process:2395): libfprint-image_device-DEBUG: 16:48:35.300: Image device reported finger status: off 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.300: [egis0570] SM_STATES_NUM entering state 5 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.300: [egis0570] SM_STATES_NUM entering state 1 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.300: [egis0570] SM_STATES_NUM entering state 2 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.301: [egis0570] SM_STATES_NUM entering state 3 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.301: [egis0570] SM_STATES_NUM entering state 2 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.302: [egis0570] SM_STATES_NUM entering state 3 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.302: [egis0570] SM_STATES_NUM entering state 2 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.302: [egis0570] SM_STATES_NUM entering state 3 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.303: [egis0570] SM_STATES_NUM entering state 2 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.303: [egis0570] SM_STATES_NUM entering state 3 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.303: [egis0570] SM_STATES_NUM entering state 4 198s (process:2395): libfprint-egis0570-DEBUG: 16:48:35.304: Finger status (picture number, mean) : 0 , 0 198s (process:2395): libfprint-egis0570-DEBUG: 16:48:35.304: Finger status (picture number, mean) : 1 , 0 198s (process:2395): libfprint-egis0570-DEBUG: 16:48:35.304: Finger status (picture number, mean) : 2 , 0 198s (process:2395): libfprint-egis0570-DEBUG: 16:48:35.304: Finger status (picture number, mean) : 3 , 0 198s (process:2395): libfprint-egis0570-DEBUG: 16:48:35.304: Finger status (picture number, mean) : 4 , 0 198s (process:2395): libfprint-image_device-DEBUG: 16:48:35.304: Image device reported finger status: off 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.304: [egis0570] SM_STATES_NUM entering state 5 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.304: [egis0570] SM_STATES_NUM entering state 1 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.304: [egis0570] SM_STATES_NUM entering state 2 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.305: [egis0570] SM_STATES_NUM entering state 3 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.305: [egis0570] SM_STATES_NUM entering state 2 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.305: [egis0570] SM_STATES_NUM entering state 3 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.306: [egis0570] SM_STATES_NUM entering state 2 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.306: [egis0570] SM_STATES_NUM entering state 3 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.307: [egis0570] SM_STATES_NUM entering state 2 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.307: [egis0570] SM_STATES_NUM entering state 3 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.307: [egis0570] SM_STATES_NUM entering state 4 198s (process:2395): libfprint-egis0570-DEBUG: 16:48:35.308: Finger status (picture number, mean) : 0 , 0 198s (process:2395): libfprint-egis0570-DEBUG: 16:48:35.308: Finger status (picture number, mean) : 1 , 0 198s (process:2395): libfprint-egis0570-DEBUG: 16:48:35.308: Finger status (picture number, mean) : 2 , 0 198s (process:2395): libfprint-egis0570-DEBUG: 16:48:35.308: Finger status (picture number, mean) : 3 , 0 198s (process:2395): libfprint-egis0570-DEBUG: 16:48:35.308: Finger status (picture number, mean) : 4 , 0 198s (process:2395): libfprint-image_device-DEBUG: 16:48:35.308: Image device reported finger status: off 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.308: [egis0570] SM_STATES_NUM entering state 5 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.308: [egis0570] SM_STATES_NUM entering state 1 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.308: [egis0570] SM_STATES_NUM entering state 2 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.308: [egis0570] SM_STATES_NUM entering state 3 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.309: [egis0570] SM_STATES_NUM entering state 2 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.309: [egis0570] SM_STATES_NUM entering state 3 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.309: [egis0570] SM_STATES_NUM entering state 2 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.310: [egis0570] SM_STATES_NUM entering state 3 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.310: [egis0570] SM_STATES_NUM entering state 2 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.311: [egis0570] SM_STATES_NUM entering state 3 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.311: [egis0570] SM_STATES_NUM entering state 4 198s (process:2395): libfprint-egis0570-DEBUG: 16:48:35.312: Finger status (picture number, mean) : 0 , 0 198s (process:2395): libfprint-egis0570-DEBUG: 16:48:35.312: Finger status (picture number, mean) : 1 , 0 198s (process:2395): libfprint-egis0570-DEBUG: 16:48:35.312: Finger status (picture number, mean) : 2 , 0 198s (process:2395): libfprint-egis0570-DEBUG: 16:48:35.312: Finger status (picture number, mean) : 3 , 0 198s (process:2395): libfprint-egis0570-DEBUG: 16:48:35.312: Finger status (picture number, mean) : 4 , 0 198s (process:2395): libfprint-image_device-DEBUG: 16:48:35.312: Image device reported finger status: off 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.312: [egis0570] SM_STATES_NUM entering state 5 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.312: [egis0570] SM_STATES_NUM entering state 1 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.312: [egis0570] SM_STATES_NUM entering state 2 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.312: [egis0570] SM_STATES_NUM entering state 3 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.312: [egis0570] SM_STATES_NUM entering state 2 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.313: [egis0570] SM_STATES_NUM entering state 3 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.313: [egis0570] SM_STATES_NUM entering state 2 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.314: [egis0570] SM_STATES_NUM entering state 3 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.314: [egis0570] SM_STATES_NUM entering state 2 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.315: [egis0570] SM_STATES_NUM entering state 3 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.315: [egis0570] SM_STATES_NUM entering state 4 198s (process:2395): libfprint-egis0570-DEBUG: 16:48:35.316: Finger status (picture number, mean) : 0 , 0 198s (process:2395): libfprint-egis0570-DEBUG: 16:48:35.316: Finger status (picture number, mean) : 1 , 0 198s (process:2395): libfprint-egis0570-DEBUG: 16:48:35.316: Finger status (picture number, mean) : 2 , 0 198s (process:2395): libfprint-egis0570-DEBUG: 16:48:35.316: Finger status (picture number, mean) : 3 , 0 198s (process:2395): libfprint-egis0570-DEBUG: 16:48:35.316: Finger status (picture number, mean) : 4 , 0 198s (process:2395): libfprint-image_device-DEBUG: 16:48:35.316: Image device reported finger status: off 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.316: [egis0570] SM_STATES_NUM entering state 5 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.316: [egis0570] SM_STATES_NUM entering state 1 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.316: [egis0570] SM_STATES_NUM entering state 2 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.316: [egis0570] SM_STATES_NUM entering state 3 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.316: [egis0570] SM_STATES_NUM entering state 2 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.317: [egis0570] SM_STATES_NUM entering state 3 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.317: [egis0570] SM_STATES_NUM entering state 2 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.318: [egis0570] SM_STATES_NUM entering state 3 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.318: [egis0570] SM_STATES_NUM entering state 2 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.319: [egis0570] SM_STATES_NUM entering state 3 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.319: [egis0570] SM_STATES_NUM entering state 4 198s (process:2395): libfprint-egis0570-DEBUG: 16:48:35.320: Finger status (picture number, mean) : 0 , 0 198s (process:2395): libfprint-egis0570-DEBUG: 16:48:35.320: Finger status (picture number, mean) : 1 , 0 198s (process:2395): libfprint-egis0570-DEBUG: 16:48:35.320: Finger status (picture number, mean) : 2 , 0 198s (process:2395): libfprint-egis0570-DEBUG: 16:48:35.320: Finger status (picture number, mean) : 3 , 0 198s (process:2395): libfprint-egis0570-DEBUG: 16:48:35.320: Finger status (picture number, mean) : 4 , 0 198s (process:2395): libfprint-image_device-DEBUG: 16:48:35.320: Image device reported finger status: off 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.320: [egis0570] SM_STATES_NUM entering state 5 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.320: [egis0570] SM_STATES_NUM entering state 1 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.320: [egis0570] SM_STATES_NUM entering state 2 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.320: [egis0570] SM_STATES_NUM entering state 3 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.320: [egis0570] SM_STATES_NUM entering state 2 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.321: [egis0570] SM_STATES_NUM entering state 3 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.321: [egis0570] SM_STATES_NUM entering state 2 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.322: [egis0570] SM_STATES_NUM entering state 3 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.322: [egis0570] SM_STATES_NUM entering state 2 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.323: [egis0570] SM_STATES_NUM entering state 3 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.323: [egis0570] SM_STATES_NUM entering state 4 198s (process:2395): libfprint-egis0570-DEBUG: 16:48:35.323: Finger status (picture number, mean) : 0 , 0 198s (process:2395): libfprint-egis0570-DEBUG: 16:48:35.323: Finger status (picture number, mean) : 1 , 0 198s (process:2395): libfprint-egis0570-DEBUG: 16:48:35.323: Finger status (picture number, mean) : 2 , 0 198s (process:2395): libfprint-egis0570-DEBUG: 16:48:35.323: Finger status (picture number, mean) : 3 , 0 198s (process:2395): libfprint-egis0570-DEBUG: 16:48:35.323: Finger status (picture number, mean) : 4 , 0 198s (process:2395): libfprint-image_device-DEBUG: 16:48:35.323: Image device reported finger status: off 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.323: [egis0570] SM_STATES_NUM entering state 5 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.323: [egis0570] SM_STATES_NUM entering state 1 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.323: [egis0570] SM_STATES_NUM entering state 2 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.324: [egis0570] SM_STATES_NUM entering state 3 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.324: [egis0570] SM_STATES_NUM entering state 2 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.325: [egis0570] SM_STATES_NUM entering state 3 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.325: [egis0570] SM_STATES_NUM entering state 2 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.326: [egis0570] SM_STATES_NUM entering state 3 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.326: [egis0570] SM_STATES_NUM entering state 2 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.327: [egis0570] SM_STATES_NUM entering state 3 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.327: [egis0570] SM_STATES_NUM entering state 4 198s (process:2395): libfprint-egis0570-DEBUG: 16:48:35.327: Finger status (picture number, mean) : 0 , 0 198s (process:2395): libfprint-egis0570-DEBUG: 16:48:35.327: Finger status (picture number, mean) : 1 , 0 198s (process:2395): libfprint-egis0570-DEBUG: 16:48:35.327: Finger status (picture number, mean) : 2 , 0 198s (process:2395): libfprint-egis0570-DEBUG: 16:48:35.327: Finger status (picture number, mean) : 3 , 0 198s (process:2395): libfprint-egis0570-DEBUG: 16:48:35.327: Finger status (picture number, mean) : 4 , 0 198s (process:2395): libfprint-image_device-DEBUG: 16:48:35.327: Image device reported finger status: off 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.328: [egis0570] SM_STATES_NUM entering state 5 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.328: [egis0570] SM_STATES_NUM entering state 1 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.328: [egis0570] SM_STATES_NUM entering state 2 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.328: [egis0570] SM_STATES_NUM entering state 3 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.328: [egis0570] SM_STATES_NUM entering state 2 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.329: [egis0570] SM_STATES_NUM entering state 3 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.329: [egis0570] SM_STATES_NUM entering state 2 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.330: [egis0570] SM_STATES_NUM entering state 3 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.330: [egis0570] SM_STATES_NUM entering state 2 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.331: [egis0570] SM_STATES_NUM entering state 3 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.331: [egis0570] SM_STATES_NUM entering state 4 198s (process:2395): libfprint-egis0570-DEBUG: 16:48:35.331: Finger status (picture number, mean) : 0 , 0 198s (process:2395): libfprint-egis0570-DEBUG: 16:48:35.331: Finger status (picture number, mean) : 1 , 0 198s (process:2395): libfprint-egis0570-DEBUG: 16:48:35.331: Finger status (picture number, mean) : 2 , 0 198s (process:2395): libfprint-egis0570-DEBUG: 16:48:35.331: Finger status (picture number, mean) : 3 , 0 198s (process:2395): libfprint-egis0570-DEBUG: 16:48:35.331: Finger status (picture number, mean) : 4 , 0 198s (process:2395): libfprint-image_device-DEBUG: 16:48:35.331: Image device reported finger status: off 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.331: [egis0570] SM_STATES_NUM entering state 5 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.331: [egis0570] SM_STATES_NUM entering state 1 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.331: [egis0570] SM_STATES_NUM entering state 2 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.332: [egis0570] SM_STATES_NUM entering state 3 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.332: [egis0570] SM_STATES_NUM entering state 2 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.333: [egis0570] SM_STATES_NUM entering state 3 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.333: [egis0570] SM_STATES_NUM entering state 2 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.334: [egis0570] SM_STATES_NUM entering state 3 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.334: [egis0570] SM_STATES_NUM entering state 2 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.335: [egis0570] SM_STATES_NUM entering state 3 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.335: [egis0570] SM_STATES_NUM entering state 4 198s (process:2395): libfprint-device-DEBUG: 16:48:35.335: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 198s (process:2395): libfprint-egis0570-DEBUG: 16:48:35.335: Finger status (picture number, mean) : 0 , 0 198s (process:2395): libfprint-egis0570-DEBUG: 16:48:35.335: Finger status (picture number, mean) : 1 , 0 198s (process:2395): libfprint-egis0570-DEBUG: 16:48:35.335: Finger status (picture number, mean) : 2 , 0 198s (process:2395): libfprint-egis0570-DEBUG: 16:48:35.336: Finger status (picture number, mean) : 3 , 0 198s (process:2395): libfprint-egis0570-DEBUG: 16:48:35.336: Finger status (picture number, mean) : 4 , 0 198s (process:2395): libfprint-image_device-DEBUG: 16:48:35.336: Image device reported finger status: off 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.336: [egis0570] SM_STATES_NUM entering state 5 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.336: [egis0570] SM_STATES_NUM entering state 1 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.336: [egis0570] SM_STATES_NUM entering state 2 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.336: [egis0570] SM_STATES_NUM entering state 3 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.336: [egis0570] SM_STATES_NUM entering state 2 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.337: [egis0570] SM_STATES_NUM entering state 3 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.337: [egis0570] SM_STATES_NUM entering state 2 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.338: [egis0570] SM_STATES_NUM entering state 3 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.338: [egis0570] SM_STATES_NUM entering state 2 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.339: [egis0570] SM_STATES_NUM entering state 3 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.339: [egis0570] SM_STATES_NUM entering state 4 198s (process:2395): libfprint-egis0570-DEBUG: 16:48:35.339: Finger status (picture number, mean) : 0 , 0 198s (process:2395): libfprint-egis0570-DEBUG: 16:48:35.339: Finger status (picture number, mean) : 1 , 0 198s (process:2395): libfprint-egis0570-DEBUG: 16:48:35.339: Finger status (picture number, mean) : 2 , 0 198s (process:2395): libfprint-egis0570-DEBUG: 16:48:35.339: Finger status (picture number, mean) : 3 , 0 198s (process:2395): libfprint-egis0570-DEBUG: 16:48:35.339: Finger status (picture number, mean) : 4 , 0 198s (process:2395): libfprint-image_device-DEBUG: 16:48:35.339: Image device reported finger status: off 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.339: [egis0570] SM_STATES_NUM entering state 5 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.339: [egis0570] SM_STATES_NUM entering state 1 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.339: [egis0570] SM_STATES_NUM entering state 2 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.340: [egis0570] SM_STATES_NUM entering state 3 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.340: [egis0570] SM_STATES_NUM entering state 2 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.341: [egis0570] SM_STATES_NUM entering state 3 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.341: [egis0570] SM_STATES_NUM entering state 2 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.342: [egis0570] SM_STATES_NUM entering state 3 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.342: [egis0570] SM_STATES_NUM entering state 2 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.343: [egis0570] SM_STATES_NUM entering state 3 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.343: [egis0570] SM_STATES_NUM entering state 4 198s (process:2395): libfprint-egis0570-DEBUG: 16:48:35.343: Finger status (picture number, mean) : 0 , 0 198s (process:2395): libfprint-egis0570-DEBUG: 16:48:35.343: Finger status (picture number, mean) : 1 , 0 198s (process:2395): libfprint-egis0570-DEBUG: 16:48:35.343: Finger status (picture number, mean) : 2 , 0 198s (process:2395): libfprint-egis0570-DEBUG: 16:48:35.343: Finger status (picture number, mean) : 3 , 0 198s (process:2395): libfprint-egis0570-DEBUG: 16:48:35.343: Finger status (picture number, mean) : 4 , 0 198s (process:2395): libfprint-image_device-DEBUG: 16:48:35.343: Image device reported finger status: off 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.343: [egis0570] SM_STATES_NUM entering state 5 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.343: [egis0570] SM_STATES_NUM entering state 1 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.343: [egis0570] SM_STATES_NUM entering state 2 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.344: [egis0570] SM_STATES_NUM entering state 3 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.344: [egis0570] SM_STATES_NUM entering state 2 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.345: [egis0570] SM_STATES_NUM entering state 3 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.345: [egis0570] SM_STATES_NUM entering state 2 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.345: [egis0570] SM_STATES_NUM entering state 3 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.346: [egis0570] SM_STATES_NUM entering state 2 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.346: [egis0570] SM_STATES_NUM entering state 3 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.346: [egis0570] SM_STATES_NUM entering state 4 198s (process:2395): libfprint-egis0570-DEBUG: 16:48:35.347: Finger status (picture number, mean) : 0 , 0 198s (process:2395): libfprint-egis0570-DEBUG: 16:48:35.347: Finger status (picture number, mean) : 1 , 0 198s (process:2395): libfprint-egis0570-DEBUG: 16:48:35.347: Finger status (picture number, mean) : 2 , 0 198s (process:2395): libfprint-egis0570-DEBUG: 16:48:35.347: Finger status (picture number, mean) : 3 , 0 198s (process:2395): libfprint-egis0570-DEBUG: 16:48:35.347: Finger status (picture number, mean) : 4 , 0 198s (process:2395): libfprint-image_device-DEBUG: 16:48:35.347: Image device reported finger status: off 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.347: [egis0570] SM_STATES_NUM entering state 5 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.347: [egis0570] SM_STATES_NUM entering state 1 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.347: [egis0570] SM_STATES_NUM entering state 2 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.348: [egis0570] SM_STATES_NUM entering state 3 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.348: [egis0570] SM_STATES_NUM entering state 2 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.348: [egis0570] SM_STATES_NUM entering state 3 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.348: [egis0570] SM_STATES_NUM entering state 2 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.349: [egis0570] SM_STATES_NUM entering state 3 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.349: [egis0570] SM_STATES_NUM entering state 2 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.350: [egis0570] SM_STATES_NUM entering state 3 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.350: [egis0570] SM_STATES_NUM entering state 4 198s (process:2395): libfprint-egis0570-DEBUG: 16:48:35.351: Finger status (picture number, mean) : 0 , 0 198s (process:2395): libfprint-egis0570-DEBUG: 16:48:35.351: Finger status (picture number, mean) : 1 , 0 198s (process:2395): libfprint-egis0570-DEBUG: 16:48:35.351: Finger status (picture number, mean) : 2 , 0 198s (process:2395): libfprint-egis0570-DEBUG: 16:48:35.351: Finger status (picture number, mean) : 3 , 0 198s (process:2395): libfprint-egis0570-DEBUG: 16:48:35.351: Finger status (picture number, mean) : 4 , 0 198s (process:2395): libfprint-image_device-DEBUG: 16:48:35.351: Image device reported finger status: off 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.351: [egis0570] SM_STATES_NUM entering state 5 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.351: [egis0570] SM_STATES_NUM entering state 1 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.351: [egis0570] SM_STATES_NUM entering state 2 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.351: [egis0570] SM_STATES_NUM entering state 3 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.351: [egis0570] SM_STATES_NUM entering state 2 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.352: [egis0570] SM_STATES_NUM entering state 3 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.352: [egis0570] SM_STATES_NUM entering state 2 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.353: [egis0570] SM_STATES_NUM entering state 3 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.353: [egis0570] SM_STATES_NUM entering state 2 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.354: [egis0570] SM_STATES_NUM entering state 3 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.354: [egis0570] SM_STATES_NUM entering state 4 198s (process:2395): libfprint-egis0570-DEBUG: 16:48:35.355: Finger status (picture number, mean) : 0 , 0 198s (process:2395): libfprint-egis0570-DEBUG: 16:48:35.355: Finger status (picture number, mean) : 1 , 0 198s (process:2395): libfprint-egis0570-DEBUG: 16:48:35.355: Finger status (picture number, mean) : 2 , 0 198s (process:2395): libfprint-egis0570-DEBUG: 16:48:35.355: Finger status (picture number, mean) : 3 , 0 198s (process:2395): libfprint-egis0570-DEBUG: 16:48:35.355: Finger status (picture number, mean) : 4 , 0 198s (process:2395): libfprint-image_device-DEBUG: 16:48:35.355: Image device reported finger status: off 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.355: [egis0570] SM_STATES_NUM entering state 5 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.355: [egis0570] SM_STATES_NUM entering state 1 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.355: [egis0570] SM_STATES_NUM entering state 2 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.355: [egis0570] SM_STATES_NUM entering state 3 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.355: [egis0570] SM_STATES_NUM entering state 2 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.356: [egis0570] SM_STATES_NUM entering state 3 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.356: [egis0570] SM_STATES_NUM entering state 2 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.357: [egis0570] SM_STATES_NUM entering state 3 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.357: [egis0570] SM_STATES_NUM entering state 2 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.358: [egis0570] SM_STATES_NUM entering state 3 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.358: [egis0570] SM_STATES_NUM entering state 4 198s (process:2395): libfprint-egis0570-DEBUG: 16:48:35.358: Finger status (picture number, mean) : 0 , 0 198s (process:2395): libfprint-egis0570-DEBUG: 16:48:35.358: Finger status (picture number, mean) : 1 , 0 198s (process:2395): libfprint-egis0570-DEBUG: 16:48:35.358: Finger status (picture number, mean) : 2 , 0 198s (process:2395): libfprint-egis0570-DEBUG: 16:48:35.358: Finger status (picture number, mean) : 3 , 0 198s (process:2395): libfprint-egis0570-DEBUG: 16:48:35.358: Finger status (picture number, mean) : 4 , 0 198s (process:2395): libfprint-image_device-DEBUG: 16:48:35.358: Image device reported finger status: off 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.358: [egis0570] SM_STATES_NUM entering state 5 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.358: [egis0570] SM_STATES_NUM entering state 1 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.358: [egis0570] SM_STATES_NUM entering state 2 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.359: [egis0570] SM_STATES_NUM entering state 3 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.359: [egis0570] SM_STATES_NUM entering state 2 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.360: [egis0570] SM_STATES_NUM entering state 3 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.360: [egis0570] SM_STATES_NUM entering state 2 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.361: [egis0570] SM_STATES_NUM entering state 3 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.361: [egis0570] SM_STATES_NUM entering state 2 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.361: [egis0570] SM_STATES_NUM entering state 3 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.362: [egis0570] SM_STATES_NUM entering state 4 198s (process:2395): libfprint-egis0570-DEBUG: 16:48:35.362: Finger status (picture number, mean) : 0 , 0 198s (process:2395): libfprint-egis0570-DEBUG: 16:48:35.362: Finger status (picture number, mean) : 1 , 0 198s (process:2395): libfprint-egis0570-DEBUG: 16:48:35.362: Finger status (picture number, mean) : 2 , 0 198s (process:2395): libfprint-egis0570-DEBUG: 16:48:35.362: Finger status (picture number, mean) : 3 , 0 198s (process:2395): libfprint-egis0570-DEBUG: 16:48:35.362: Finger status (picture number, mean) : 4 , 0 198s (process:2395): libfprint-image_device-DEBUG: 16:48:35.362: Image device reported finger status: off 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.362: [egis0570] SM_STATES_NUM entering state 5 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.362: [egis0570] SM_STATES_NUM entering state 1 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.362: [egis0570] SM_STATES_NUM entering state 2 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.362: [egis0570] SM_STATES_NUM entering state 3 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.363: [egis0570] SM_STATES_NUM entering state 2 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.363: [egis0570] SM_STATES_NUM entering state 3 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.364: [egis0570] SM_STATES_NUM entering state 2 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.364: [egis0570] SM_STATES_NUM entering state 3 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.365: [egis0570] SM_STATES_NUM entering state 2 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.365: [egis0570] SM_STATES_NUM entering state 3 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.365: [egis0570] SM_STATES_NUM entering state 4 198s (process:2395): libfprint-egis0570-DEBUG: 16:48:35.366: Finger status (picture number, mean) : 0 , 0 198s (process:2395): libfprint-egis0570-DEBUG: 16:48:35.366: Finger status (picture number, mean) : 1 , 0 198s (process:2395): libfprint-egis0570-DEBUG: 16:48:35.366: Finger status (picture number, mean) : 2 , 0 198s (process:2395): libfprint-egis0570-DEBUG: 16:48:35.366: Finger status (picture number, mean) : 3 , 0 198s (process:2395): libfprint-egis0570-DEBUG: 16:48:35.366: Finger status (picture number, mean) : 4 , 0 198s (process:2395): libfprint-image_device-DEBUG: 16:48:35.366: Image device reported finger status: off 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.366: [egis0570] SM_STATES_NUM entering state 5 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.366: [egis0570] SM_STATES_NUM entering state 1 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.366: [egis0570] SM_STATES_NUM entering state 2 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.366: [egis0570] SM_STATES_NUM entering state 3 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.367: [egis0570] SM_STATES_NUM entering state 2 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.367: [egis0570] SM_STATES_NUM entering state 3 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.368: [egis0570] SM_STATES_NUM entering state 2 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.368: [egis0570] SM_STATES_NUM entering state 3 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.368: [egis0570] SM_STATES_NUM entering state 2 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.369: [egis0570] SM_STATES_NUM entering state 3 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.369: [egis0570] SM_STATES_NUM entering state 4 198s (process:2395): libfprint-egis0570-DEBUG: 16:48:35.370: Finger status (picture number, mean) : 0 , 0 198s (process:2395): libfprint-egis0570-DEBUG: 16:48:35.370: Finger status (picture number, mean) : 1 , 0 198s (process:2395): libfprint-egis0570-DEBUG: 16:48:35.370: Finger status (picture number, mean) : 2 , 0 198s (process:2395): libfprint-egis0570-DEBUG: 16:48:35.370: Finger status (picture number, mean) : 3 , 0 198s (process:2395): libfprint-egis0570-DEBUG: 16:48:35.370: Finger status (picture number, mean) : 4 , 0 198s (process:2395): libfprint-image_device-DEBUG: 16:48:35.370: Image device reported finger status: off 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.370: [egis0570] SM_STATES_NUM entering state 5 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.370: [egis0570] SM_STATES_NUM entering state 1 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.370: [egis0570] SM_STATES_NUM entering state 2 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.370: [egis0570] SM_STATES_NUM entering state 3 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.370: [egis0570] SM_STATES_NUM entering state 2 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.371: [egis0570] SM_STATES_NUM entering state 3 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.371: [egis0570] SM_STATES_NUM entering state 2 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.372: [egis0570] SM_STATES_NUM entering state 3 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.372: [egis0570] SM_STATES_NUM entering state 2 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.373: [egis0570] SM_STATES_NUM entering state 3 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.373: [egis0570] SM_STATES_NUM entering state 4 198s (process:2395): libfprint-egis0570-DEBUG: 16:48:35.373: Finger status (picture number, mean) : 0 , 0 198s (process:2395): libfprint-egis0570-DEBUG: 16:48:35.374: Finger status (picture number, mean) : 1 , 0 198s (process:2395): libfprint-egis0570-DEBUG: 16:48:35.374: Finger status (picture number, mean) : 2 , 0 198s (process:2395): libfprint-egis0570-DEBUG: 16:48:35.374: Finger status (picture number, mean) : 3 , 0 198s (process:2395): libfprint-egis0570-DEBUG: 16:48:35.374: Finger status (picture number, mean) : 4 , 0 198s (process:2395): libfprint-image_device-DEBUG: 16:48:35.374: Image device reported finger status: off 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.374: [egis0570] SM_STATES_NUM entering state 5 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.374: [egis0570] SM_STATES_NUM entering state 1 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.374: [egis0570] SM_STATES_NUM entering state 2 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.374: [egis0570] SM_STATES_NUM entering state 3 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.374: [egis0570] SM_STATES_NUM entering state 2 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.375: [egis0570] SM_STATES_NUM entering state 3 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.375: [egis0570] SM_STATES_NUM entering state 2 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.376: [egis0570] SM_STATES_NUM entering state 3 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.376: [egis0570] SM_STATES_NUM entering state 2 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.377: [egis0570] SM_STATES_NUM entering state 3 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.377: [egis0570] SM_STATES_NUM entering state 4 198s (process:2395): libfprint-egis0570-DEBUG: 16:48:35.377: Finger status (picture number, mean) : 0 , 0 198s (process:2395): libfprint-egis0570-DEBUG: 16:48:35.377: Finger status (picture number, mean) : 1 , 0 198s (process:2395): libfprint-egis0570-DEBUG: 16:48:35.377: Finger status (picture number, mean) : 2 , 0 198s (process:2395): libfprint-egis0570-DEBUG: 16:48:35.377: Finger status (picture number, mean) : 3 , 0 198s (process:2395): libfprint-egis0570-DEBUG: 16:48:35.377: Finger status (picture number, mean) : 4 , 0 198s (process:2395): libfprint-image_device-DEBUG: 16:48:35.377: Image device reported finger status: off 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.377: [egis0570] SM_STATES_NUM entering state 5 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.377: [egis0570] SM_STATES_NUM entering state 1 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.377: [egis0570] SM_STATES_NUM entering state 2 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.378: [egis0570] SM_STATES_NUM entering state 3 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.378: [egis0570] SM_STATES_NUM entering state 2 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.379: [egis0570] SM_STATES_NUM entering state 3 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.379: [egis0570] SM_STATES_NUM entering state 2 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.380: [egis0570] SM_STATES_NUM entering state 3 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.380: [egis0570] SM_STATES_NUM entering state 2 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.381: [egis0570] SM_STATES_NUM entering state 3 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.381: [egis0570] SM_STATES_NUM entering state 4 198s (process:2395): libfprint-egis0570-DEBUG: 16:48:35.381: Finger status (picture number, mean) : 0 , 0 198s (process:2395): libfprint-egis0570-DEBUG: 16:48:35.381: Finger status (picture number, mean) : 1 , 0 198s (process:2395): libfprint-egis0570-DEBUG: 16:48:35.381: Finger status (picture number, mean) : 2 , 0 198s (process:2395): libfprint-egis0570-DEBUG: 16:48:35.381: Finger status (picture number, mean) : 3 , 0 198s (process:2395): libfprint-egis0570-DEBUG: 16:48:35.381: Finger status (picture number, mean) : 4 , 0 198s (process:2395): libfprint-image_device-DEBUG: 16:48:35.381: Image device reported finger status: off 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.381: [egis0570] SM_STATES_NUM entering state 5 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.381: [egis0570] SM_STATES_NUM entering state 1 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.381: [egis0570] SM_STATES_NUM entering state 2 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.382: [egis0570] SM_STATES_NUM entering state 3 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.382: [egis0570] SM_STATES_NUM entering state 2 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.382: [egis0570] SM_STATES_NUM entering state 3 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.383: [egis0570] SM_STATES_NUM entering state 2 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.383: [egis0570] SM_STATES_NUM entering state 3 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.384: [egis0570] SM_STATES_NUM entering state 2 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.384: [egis0570] SM_STATES_NUM entering state 3 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.384: [egis0570] SM_STATES_NUM entering state 4 198s (process:2395): libfprint-egis0570-DEBUG: 16:48:35.385: Finger status (picture number, mean) : 0 , 0 198s (process:2395): libfprint-egis0570-DEBUG: 16:48:35.385: Finger status (picture number, mean) : 1 , 0 198s (process:2395): libfprint-egis0570-DEBUG: 16:48:35.385: Finger status (picture number, mean) : 2 , 0 198s (process:2395): libfprint-egis0570-DEBUG: 16:48:35.385: Finger status (picture number, mean) : 3 , 0 198s (process:2395): libfprint-egis0570-DEBUG: 16:48:35.385: Finger status (picture number, mean) : 4 , 0 198s (process:2395): libfprint-image_device-DEBUG: 16:48:35.385: Image device reported finger status: off 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.385: [egis0570] SM_STATES_NUM entering state 5 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.385: [egis0570] SM_STATES_NUM entering state 1 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.385: [egis0570] SM_STATES_NUM entering state 2 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.385: [egis0570] SM_STATES_NUM entering state 3 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.385: [egis0570] SM_STATES_NUM entering state 2 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.386: [egis0570] SM_STATES_NUM entering state 3 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.386: [egis0570] SM_STATES_NUM entering state 2 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.387: [egis0570] SM_STATES_NUM entering state 3 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.387: [egis0570] SM_STATES_NUM entering state 2 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.388: [egis0570] SM_STATES_NUM entering state 3 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.388: [egis0570] SM_STATES_NUM entering state 4 198s (process:2395): libfprint-egis0570-DEBUG: 16:48:35.389: Finger status (picture number, mean) : 0 , 0 198s (process:2395): libfprint-egis0570-DEBUG: 16:48:35.389: Finger status (picture number, mean) : 1 , 0 198s (process:2395): libfprint-egis0570-DEBUG: 16:48:35.389: Finger status (picture number, mean) : 2 , 0 198s (process:2395): libfprint-egis0570-DEBUG: 16:48:35.389: Finger status (picture number, mean) : 3 , 0 198s (process:2395): libfprint-egis0570-DEBUG: 16:48:35.389: Finger status (picture number, mean) : 4 , 0 198s (process:2395): libfprint-image_device-DEBUG: 16:48:35.389: Image device reported finger status: off 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.389: [egis0570] SM_STATES_NUM entering state 5 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.389: [egis0570] SM_STATES_NUM entering state 1 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.389: [egis0570] SM_STATES_NUM entering state 2 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.389: [egis0570] SM_STATES_NUM entering state 3 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.389: [egis0570] SM_STATES_NUM entering state 2 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.390: [egis0570] SM_STATES_NUM entering state 3 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.390: [egis0570] SM_STATES_NUM entering state 2 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.391: [egis0570] SM_STATES_NUM entering state 3 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.391: [egis0570] SM_STATES_NUM entering state 2 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.392: [egis0570] SM_STATES_NUM entering state 3 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.392: [egis0570] SM_STATES_NUM entering state 4 198s (process:2395): libfprint-egis0570-DEBUG: 16:48:35.393: Finger status (picture number, mean) : 0 , 0 198s (process:2395): libfprint-egis0570-DEBUG: 16:48:35.393: Finger status (picture number, mean) : 1 , 0 198s (process:2395): libfprint-egis0570-DEBUG: 16:48:35.393: Finger status (picture number, mean) : 2 , 0 198s (process:2395): libfprint-egis0570-DEBUG: 16:48:35.393: Finger status (picture number, mean) : 3 , 0 198s (process:2395): libfprint-egis0570-DEBUG: 16:48:35.393: Finger status (picture number, mean) : 4 , 0 198s (process:2395): libfprint-image_device-DEBUG: 16:48:35.393: Image device reported finger status: off 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.393: [egis0570] SM_STATES_NUM entering state 5 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.393: [egis0570] SM_STATES_NUM entering state 1 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.393: [egis0570] SM_STATES_NUM entering state 2 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.393: [egis0570] SM_STATES_NUM entering state 3 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.393: [egis0570] SM_STATES_NUM entering state 2 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.394: [egis0570] SM_STATES_NUM entering state 3 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.394: [egis0570] SM_STATES_NUM entering state 2 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.395: [egis0570] SM_STATES_NUM entering state 3 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.395: [egis0570] SM_STATES_NUM entering state 2 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.396: [egis0570] SM_STATES_NUM entering state 3 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.396: [egis0570] SM_STATES_NUM entering state 4 198s (process:2395): libfprint-egis0570-DEBUG: 16:48:35.397: Finger status (picture number, mean) : 0 , 0 198s (process:2395): libfprint-egis0570-DEBUG: 16:48:35.397: Finger status (picture number, mean) : 1 , 1 198s (process:2395): libfprint-egis0570-DEBUG: 16:48:35.397: Finger status (picture number, mean) : 2 , 2 198s (process:2395): libfprint-egis0570-DEBUG: 16:48:35.397: Finger status (picture number, mean) : 3 , 3 198s (process:2395): libfprint-egis0570-DEBUG: 16:48:35.397: Finger status (picture number, mean) : 4 , 6 198s (process:2395): libfprint-image_device-DEBUG: 16:48:35.397: Image device reported finger status: off 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.397: [egis0570] SM_STATES_NUM entering state 5 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.397: [egis0570] SM_STATES_NUM entering state 1 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.397: [egis0570] SM_STATES_NUM entering state 2 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.397: [egis0570] SM_STATES_NUM entering state 3 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.397: [egis0570] SM_STATES_NUM entering state 2 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.398: [egis0570] SM_STATES_NUM entering state 3 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.398: [egis0570] SM_STATES_NUM entering state 2 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.399: [egis0570] SM_STATES_NUM entering state 3 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.399: [egis0570] SM_STATES_NUM entering state 2 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.400: [egis0570] SM_STATES_NUM entering state 3 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.400: [egis0570] SM_STATES_NUM entering state 4 198s (process:2395): libfprint-egis0570-DEBUG: 16:48:35.401: Finger status (picture number, mean) : 0 , 11 198s (process:2395): libfprint-egis0570-DEBUG: 16:48:35.401: Finger status (picture number, mean) : 1 , 16 198s (process:2395): libfprint-egis0570-DEBUG: 16:48:35.401: Finger status (picture number, mean) : 2 , 23 198s (process:2395): libfprint-egis0570-DEBUG: 16:48:35.401: Finger status (picture number, mean) : 3 , 28 198s (process:2395): libfprint-egis0570-DEBUG: 16:48:35.401: Finger status (picture number, mean) : 4 , 32 198s (process:2395): libfprint-device-DEBUG: 16:48:35.401: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 198s (process:2395): libfprint-image_device-DEBUG: 16:48:35.401: Image device reported finger status: on 198s (process:2395): libfprint-image_device-DEBUG: 16:48:35.401: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 198s (process:2395): libfprint-device-DEBUG: 16:48:35.401: Device reported finger status change: FP_FINGER_STATUS_NEEDED 198s (process:2395): libfprint-image_device-DEBUG: 16:48:35.401: Image device reported finger status: off 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.401: [egis0570] SM_STATES_NUM entering state 5 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.401: [egis0570] SM_STATES_NUM entering state 1 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.401: [egis0570] SM_STATES_NUM entering state 2 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.401: [egis0570] SM_STATES_NUM entering state 3 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.402: [egis0570] SM_STATES_NUM entering state 2 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.402: [egis0570] SM_STATES_NUM entering state 3 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.403: [egis0570] SM_STATES_NUM entering state 2 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.403: [egis0570] SM_STATES_NUM entering state 3 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.404: [egis0570] SM_STATES_NUM entering state 2 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.404: [egis0570] SM_STATES_NUM entering state 3 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.404: [egis0570] SM_STATES_NUM entering state 4 198s (process:2395): libfprint-egis0570-DEBUG: 16:48:35.405: Finger status (picture number, mean) : 0 , 38 198s (process:2395): libfprint-egis0570-DEBUG: 16:48:35.405: Finger status (picture number, mean) : 1 , 43 198s (process:2395): libfprint-egis0570-DEBUG: 16:48:35.405: Finger status (picture number, mean) : 2 , 48 198s (process:2395): libfprint-egis0570-DEBUG: 16:48:35.405: Finger status (picture number, mean) : 3 , 54 198s (process:2395): libfprint-egis0570-DEBUG: 16:48:35.405: Finger status (picture number, mean) : 4 , 58 198s (process:2395): libfprint-device-DEBUG: 16:48:35.405: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 198s (process:2395): libfprint-image_device-DEBUG: 16:48:35.405: Image device reported finger status: on 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.405: [egis0570] SM_STATES_NUM entering state 5 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.405: [egis0570] SM_STATES_NUM entering state 1 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.405: [egis0570] SM_STATES_NUM entering state 2 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.405: [egis0570] SM_STATES_NUM entering state 3 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.406: [egis0570] SM_STATES_NUM entering state 2 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.406: [egis0570] SM_STATES_NUM entering state 3 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.407: [egis0570] SM_STATES_NUM entering state 2 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.407: [egis0570] SM_STATES_NUM entering state 3 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.408: [egis0570] SM_STATES_NUM entering state 2 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.408: [egis0570] SM_STATES_NUM entering state 3 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.408: [egis0570] SM_STATES_NUM entering state 4 198s (process:2395): libfprint-egis0570-DEBUG: 16:48:35.409: Finger status (picture number, mean) : 0 , 62 198s (process:2395): libfprint-egis0570-DEBUG: 16:48:35.409: Finger status (picture number, mean) : 1 , 68 198s (process:2395): libfprint-egis0570-DEBUG: 16:48:35.409: Finger status (picture number, mean) : 2 , 71 198s (process:2395): libfprint-egis0570-DEBUG: 16:48:35.409: Finger status (picture number, mean) : 3 , 73 198s (process:2395): libfprint-egis0570-DEBUG: 16:48:35.409: Finger status (picture number, mean) : 4 , 77 198s (process:2395): libfprint-image_device-DEBUG: 16:48:35.409: Image device reported finger status: on 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.409: [egis0570] SM_STATES_NUM entering state 5 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.409: [egis0570] SM_STATES_NUM entering state 1 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.409: [egis0570] SM_STATES_NUM entering state 2 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.409: [egis0570] SM_STATES_NUM entering state 3 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.410: [egis0570] SM_STATES_NUM entering state 2 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.410: [egis0570] SM_STATES_NUM entering state 3 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.411: [egis0570] SM_STATES_NUM entering state 2 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.411: [egis0570] SM_STATES_NUM entering state 3 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.412: [egis0570] SM_STATES_NUM entering state 2 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.412: [egis0570] SM_STATES_NUM entering state 3 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.412: [egis0570] SM_STATES_NUM entering state 4 198s (process:2395): libfprint-egis0570-DEBUG: 16:48:35.413: Finger status (picture number, mean) : 0 , 79 198s (process:2395): libfprint-egis0570-DEBUG: 16:48:35.413: Finger status (picture number, mean) : 1 , 79 198s (process:2395): libfprint-egis0570-DEBUG: 16:48:35.413: Finger status (picture number, mean) : 2 , 82 198s (process:2395): libfprint-egis0570-DEBUG: 16:48:35.413: Finger status (picture number, mean) : 3 , 84 198s (process:2395): libfprint-egis0570-DEBUG: 16:48:35.413: Finger status (picture number, mean) : 4 , 85 198s (process:2395): libfprint-image_device-DEBUG: 16:48:35.413: Image device reported finger status: on 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.413: [egis0570] SM_STATES_NUM entering state 5 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.413: [egis0570] SM_STATES_NUM entering state 1 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.413: [egis0570] SM_STATES_NUM entering state 2 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.413: [egis0570] SM_STATES_NUM entering state 3 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.414: [egis0570] SM_STATES_NUM entering state 2 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.414: [egis0570] SM_STATES_NUM entering state 3 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.415: [egis0570] SM_STATES_NUM entering state 2 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.415: [egis0570] SM_STATES_NUM entering state 3 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.416: [egis0570] SM_STATES_NUM entering state 2 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.416: [egis0570] SM_STATES_NUM entering state 3 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.416: [egis0570] SM_STATES_NUM entering state 4 198s (process:2395): libfprint-egis0570-DEBUG: 16:48:35.417: Finger status (picture number, mean) : 0 , 88 198s (process:2395): libfprint-egis0570-DEBUG: 16:48:35.417: Finger status (picture number, mean) : 1 , 89 198s (process:2395): libfprint-egis0570-DEBUG: 16:48:35.417: Finger status (picture number, mean) : 2 , 90 198s (process:2395): libfprint-egis0570-DEBUG: 16:48:35.417: Finger status (picture number, mean) : 3 , 92 198s (process:2395): libfprint-egis0570-DEBUG: 16:48:35.417: Finger status (picture number, mean) : 4 , 92 198s (process:2395): libfprint-image_device-DEBUG: 16:48:35.417: Image device reported finger status: on 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.417: [egis0570] SM_STATES_NUM entering state 5 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.417: [egis0570] SM_STATES_NUM entering state 1 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.417: [egis0570] SM_STATES_NUM entering state 2 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.417: [egis0570] SM_STATES_NUM entering state 3 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.417: [egis0570] SM_STATES_NUM entering state 2 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.418: [egis0570] SM_STATES_NUM entering state 3 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.418: [egis0570] SM_STATES_NUM entering state 2 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.419: [egis0570] SM_STATES_NUM entering state 3 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.419: [egis0570] SM_STATES_NUM entering state 2 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.420: [egis0570] SM_STATES_NUM entering state 3 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.420: [egis0570] SM_STATES_NUM entering state 4 198s (process:2395): libfprint-egis0570-DEBUG: 16:48:35.420: Finger status (picture number, mean) : 0 , 93 198s (process:2395): libfprint-egis0570-DEBUG: 16:48:35.420: Finger status (picture number, mean) : 1 , 94 198s (process:2395): libfprint-egis0570-DEBUG: 16:48:35.420: Finger status (picture number, mean) : 2 , 95 198s (process:2395): libfprint-egis0570-DEBUG: 16:48:35.420: Finger status (picture number, mean) : 3 , 96 198s (process:2395): libfprint-egis0570-DEBUG: 16:48:35.420: Finger status (picture number, mean) : 4 , 97 198s (process:2395): libfprint-image_device-DEBUG: 16:48:35.420: Image device reported finger status: on 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.421: [egis0570] SM_STATES_NUM entering state 5 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.421: [egis0570] SM_STATES_NUM entering state 1 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.421: [egis0570] SM_STATES_NUM entering state 2 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.421: [egis0570] SM_STATES_NUM entering state 3 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.421: [egis0570] SM_STATES_NUM entering state 2 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.422: [egis0570] SM_STATES_NUM entering state 3 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.422: [egis0570] SM_STATES_NUM entering state 2 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.423: [egis0570] SM_STATES_NUM entering state 3 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.423: [egis0570] SM_STATES_NUM entering state 2 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.424: [egis0570] SM_STATES_NUM entering state 3 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.424: [egis0570] SM_STATES_NUM entering state 4 198s (process:2395): libfprint-egis0570-DEBUG: 16:48:35.424: Finger status (picture number, mean) : 0 , 97 198s (process:2395): libfprint-egis0570-DEBUG: 16:48:35.424: Finger status (picture number, mean) : 1 , 95 198s (process:2395): libfprint-egis0570-DEBUG: 16:48:35.424: Finger status (picture number, mean) : 2 , 95 198s (process:2395): libfprint-egis0570-DEBUG: 16:48:35.424: Finger status (picture number, mean) : 3 , 96 198s (process:2395): libfprint-egis0570-DEBUG: 16:48:35.424: Finger status (picture number, mean) : 4 , 97 198s (process:2395): libfprint-image_device-DEBUG: 16:48:35.425: Image device reported finger status: on 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.425: [egis0570] SM_STATES_NUM entering state 5 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.425: [egis0570] SM_STATES_NUM entering state 1 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.425: [egis0570] SM_STATES_NUM entering state 2 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.425: [egis0570] SM_STATES_NUM entering state 3 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.425: [egis0570] SM_STATES_NUM entering state 2 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.426: [egis0570] SM_STATES_NUM entering state 3 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.426: [egis0570] SM_STATES_NUM entering state 2 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.427: [egis0570] SM_STATES_NUM entering state 3 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.427: [egis0570] SM_STATES_NUM entering state 2 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.428: [egis0570] SM_STATES_NUM entering state 3 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.428: [egis0570] SM_STATES_NUM entering state 4 198s (process:2395): libfprint-egis0570-DEBUG: 16:48:35.429: Finger status (picture number, mean) : 0 , 96 198s (process:2395): libfprint-egis0570-DEBUG: 16:48:35.429: Finger status (picture number, mean) : 1 , 97 198s (process:2395): libfprint-egis0570-DEBUG: 16:48:35.429: Finger status (picture number, mean) : 2 , 98 198s (process:2395): libfprint-egis0570-DEBUG: 16:48:35.429: Finger status (picture number, mean) : 3 , 98 198s (process:2395): libfprint-egis0570-DEBUG: 16:48:35.429: Finger status (picture number, mean) : 4 , 98 198s (process:2395): libfprint-image_device-DEBUG: 16:48:35.429: Image device reported finger status: on 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.429: [egis0570] SM_STATES_NUM entering state 5 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.429: [egis0570] SM_STATES_NUM entering state 1 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.429: [egis0570] SM_STATES_NUM entering state 2 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.429: [egis0570] SM_STATES_NUM entering state 3 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.429: [egis0570] SM_STATES_NUM entering state 2 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.430: [egis0570] SM_STATES_NUM entering state 3 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.430: [egis0570] SM_STATES_NUM entering state 2 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.431: [egis0570] SM_STATES_NUM entering state 3 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.431: [egis0570] SM_STATES_NUM entering state 2 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.432: [egis0570] SM_STATES_NUM entering state 3 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.432: [egis0570] SM_STATES_NUM entering state 4 198s (process:2395): libfprint-egis0570-DEBUG: 16:48:35.433: Finger status (picture number, mean) : 0 , 98 198s (process:2395): libfprint-egis0570-DEBUG: 16:48:35.433: Finger status (picture number, mean) : 1 , 99 198s (process:2395): libfprint-egis0570-DEBUG: 16:48:35.433: Finger status (picture number, mean) : 2 , 100 198s (process:2395): libfprint-egis0570-DEBUG: 16:48:35.433: Finger status (picture number, mean) : 3 , 99 198s (process:2395): libfprint-egis0570-DEBUG: 16:48:35.433: Finger status (picture number, mean) : 4 , 97 198s (process:2395): libfprint-image_device-DEBUG: 16:48:35.433: Image device reported finger status: on 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.433: [egis0570] SM_STATES_NUM entering state 5 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.433: [egis0570] SM_STATES_NUM entering state 1 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.433: [egis0570] SM_STATES_NUM entering state 2 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.433: [egis0570] SM_STATES_NUM entering state 3 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.433: [egis0570] SM_STATES_NUM entering state 2 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.434: [egis0570] SM_STATES_NUM entering state 3 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.434: [egis0570] SM_STATES_NUM entering state 2 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.435: [egis0570] SM_STATES_NUM entering state 3 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.435: [egis0570] SM_STATES_NUM entering state 2 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.436: [egis0570] SM_STATES_NUM entering state 3 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.436: [egis0570] SM_STATES_NUM entering state 4 198s (process:2395): libfprint-egis0570-DEBUG: 16:48:35.436: Finger status (picture number, mean) : 0 , 98 198s (process:2395): libfprint-egis0570-DEBUG: 16:48:35.436: Finger status (picture number, mean) : 1 , 98 198s (process:2395): libfprint-egis0570-DEBUG: 16:48:35.437: Finger status (picture number, mean) : 2 , 98 198s (process:2395): libfprint-egis0570-DEBUG: 16:48:35.437: Finger status (picture number, mean) : 3 , 95 198s (process:2395): libfprint-egis0570-DEBUG: 16:48:35.437: Finger status (picture number, mean) : 4 , 91 198s (process:2395): libfprint-image_device-DEBUG: 16:48:35.437: Image device reported finger status: on 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.437: [egis0570] SM_STATES_NUM entering state 5 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.437: [egis0570] SM_STATES_NUM entering state 1 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.437: [egis0570] SM_STATES_NUM entering state 2 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.437: [egis0570] SM_STATES_NUM entering state 3 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.437: [egis0570] SM_STATES_NUM entering state 2 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.438: [egis0570] SM_STATES_NUM entering state 3 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.438: [egis0570] SM_STATES_NUM entering state 2 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.439: [egis0570] SM_STATES_NUM entering state 3 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.439: [egis0570] SM_STATES_NUM entering state 2 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.440: [egis0570] SM_STATES_NUM entering state 3 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.440: [egis0570] SM_STATES_NUM entering state 4 198s (process:2395): libfprint-egis0570-DEBUG: 16:48:35.441: Finger status (picture number, mean) : 0 , 88 198s (process:2395): libfprint-egis0570-DEBUG: 16:48:35.441: Finger status (picture number, mean) : 1 , 88 198s (process:2395): libfprint-egis0570-DEBUG: 16:48:35.441: Finger status (picture number, mean) : 2 , 88 198s (process:2395): libfprint-egis0570-DEBUG: 16:48:35.441: Finger status (picture number, mean) : 3 , 87 198s (process:2395): libfprint-egis0570-DEBUG: 16:48:35.441: Finger status (picture number, mean) : 4 , 89 198s (process:2395): libfprint-image_device-DEBUG: 16:48:35.441: Image device reported finger status: on 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.441: [egis0570] SM_STATES_NUM entering state 5 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.441: [egis0570] SM_STATES_NUM entering state 1 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.441: [egis0570] SM_STATES_NUM entering state 2 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.441: [egis0570] SM_STATES_NUM entering state 3 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.441: [egis0570] SM_STATES_NUM entering state 2 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.442: [egis0570] SM_STATES_NUM entering state 3 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.442: [egis0570] SM_STATES_NUM entering state 2 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.443: [egis0570] SM_STATES_NUM entering state 3 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.443: [egis0570] SM_STATES_NUM entering state 2 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.444: [egis0570] SM_STATES_NUM entering state 3 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.444: [egis0570] SM_STATES_NUM entering state 4 198s (process:2395): libfprint-egis0570-DEBUG: 16:48:35.445: Finger status (picture number, mean) : 0 , 88 198s (process:2395): libfprint-egis0570-DEBUG: 16:48:35.445: Finger status (picture number, mean) : 1 , 89 198s (process:2395): libfprint-egis0570-DEBUG: 16:48:35.445: Finger status (picture number, mean) : 2 , 90 198s (process:2395): libfprint-egis0570-DEBUG: 16:48:35.445: Finger status (picture number, mean) : 3 , 91 198s (process:2395): libfprint-egis0570-DEBUG: 16:48:35.445: Finger status (picture number, mean) : 4 , 89 198s (process:2395): libfprint-image_device-DEBUG: 16:48:35.445: Image device reported finger status: on 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.445: [egis0570] SM_STATES_NUM entering state 5 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.445: [egis0570] SM_STATES_NUM entering state 1 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.445: [egis0570] SM_STATES_NUM entering state 2 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.445: [egis0570] SM_STATES_NUM entering state 3 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.445: [egis0570] SM_STATES_NUM entering state 2 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.446: [egis0570] SM_STATES_NUM entering state 3 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.446: [egis0570] SM_STATES_NUM entering state 2 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.447: [egis0570] SM_STATES_NUM entering state 3 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.447: [egis0570] SM_STATES_NUM entering state 2 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.448: [egis0570] SM_STATES_NUM entering state 3 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.448: [egis0570] SM_STATES_NUM entering state 4 198s (process:2395): libfprint-egis0570-DEBUG: 16:48:35.448: Finger status (picture number, mean) : 0 , 90 198s (process:2395): libfprint-egis0570-DEBUG: 16:48:35.448: Finger status (picture number, mean) : 1 , 89 198s (process:2395): libfprint-egis0570-DEBUG: 16:48:35.448: Finger status (picture number, mean) : 2 , 85 198s (process:2395): libfprint-egis0570-DEBUG: 16:48:35.448: Finger status (picture number, mean) : 3 , 75 198s (process:2395): libfprint-egis0570-DEBUG: 16:48:35.448: Finger status (picture number, mean) : 4 , 46 198s (process:2395): libfprint-image_device-DEBUG: 16:48:35.448: Image device reported finger status: on 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.448: [egis0570] SM_STATES_NUM entering state 5 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.448: [egis0570] SM_STATES_NUM entering state 1 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.448: [egis0570] SM_STATES_NUM entering state 2 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.449: [egis0570] SM_STATES_NUM entering state 3 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.449: [egis0570] SM_STATES_NUM entering state 2 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.450: [egis0570] SM_STATES_NUM entering state 3 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.450: [egis0570] SM_STATES_NUM entering state 2 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.451: [egis0570] SM_STATES_NUM entering state 3 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.451: [egis0570] SM_STATES_NUM entering state 2 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.452: [egis0570] SM_STATES_NUM entering state 3 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.452: [egis0570] SM_STATES_NUM entering state 4 198s (process:2395): libfprint-egis0570-DEBUG: 16:48:35.452: Finger status (picture number, mean) : 0 , 17 198s (process:2395): libfprint-egis0570-DEBUG: 16:48:35.452: Finger status (picture number, mean) : 1 , 14 198s (process:2395): libfprint-egis0570-DEBUG: 16:48:35.452: Finger status (picture number, mean) : 2 , 15 198s (process:2395): libfprint-egis0570-DEBUG: 16:48:35.452: Finger status (picture number, mean) : 3 , 15 198s (process:2395): libfprint-egis0570-DEBUG: 16:48:35.452: Finger status (picture number, mean) : 4 , 15 198s (process:2395): libfprint-assembling-DEBUG: 16:48:35.533: calc delta completed in 0.080804 secs 198s (process:2395): libfprint-assembling-DEBUG: 16:48:35.614: calc delta completed in 0.080628 secs 198s (process:2395): libfprint-assembling-DEBUG: 16:48:35.614: errors: 10243 rev: 29954 198s (process:2395): libfprint-assembling-DEBUG: 16:48:35.695: calc delta completed in 0.080706 secs 198s (process:2395): libfprint-assembling-DEBUG: 16:48:35.695: height is 292 198s (process:2395): libfprint-image_device-DEBUG: 16:48:35.697: Image device captured an image 198s (process:2395): libfprint-image_device-DEBUG: 16:48:35.698: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 198s (process:2395): libfprint-device-DEBUG: 16:48:35.698: Device reported finger status change: FP_FINGER_STATUS_PRESENT 198s (process:2395): libfprint-device-DEBUG: 16:48:35.703: Device reported finger status change: FP_FINGER_STATUS_NONE 198s (process:2395): libfprint-image_device-DEBUG: 16:48:35.703: Image device reported finger status: off 198s (process:2395): libfprint-image_device-DEBUG: 16:48:35.703: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 198s (process:2395): libfprint-image_device-DEBUG: 16:48:35.703: Deactivating image device 198s (process:2395): libfprint-image_device-DEBUG: 16:48:35.703: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_DEACTIVATING 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.703: [egis0570] SM_STATES_NUM entering state 5 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.703: [egis0570] SM_STATES_NUM entering state 1 198s (process:2395): libfprint-egis0570-DEBUG: 16:48:35.703: deactivating, marking completed 198s (process:2395): libfprint-SSM-DEBUG: 16:48:35.703: [egis0570] SM_STATES_NUM completed successfully 198s (process:2395): libfprint-image_device-DEBUG: 16:48:35.703: Image device deactivation completed 198s (process:2395): libfprint-image_device-DEBUG: 16:48:35.703: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE 198s (process:2395): libfprint-image-DEBUG: 16:48:35.743: Minutiae scan completed in 0.044356 secs 198s (process:2395): libfprint-device-DEBUG: 16:48:35.743: Device reported capture completion 198s (process:2395): libfprint-device-DEBUG: 16:48:35.743: Completing action FPI_DEVICE_ACTION_CAPTURE in idle! 198s (process:2395): libfprint-device-DEBUG: 16:48:35.743: Updated temperature model after 0.41 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 198s (process:2395): libfprint-image_device-DEBUG: 16:48:35.743: Image device close completed 198s (process:2395): libfprint-device-DEBUG: 16:48:35.743: Device reported close completion 198s (process:2395): libfprint-device-DEBUG: 16:48:35.744: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 198s (process:2395): libfprint-device-DEBUG: 16:48:35.744: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 198s ** (umockdev-run:2391): DEBUG: 16:48:35.964: umockdev.vala:150: Removing test bed /tmp/umockdev.OZQGK2 199s (umockdev-run:2391): GLib-DEBUG: 16:48:35.967: unsetenv() is not thread-safe and should not be used after threads are created 199s Comparing PNGs /tmp/libfprint-umockdev-test-bzht2aox/capture.png and /usr/share/installed-tests/libfprint-2/egis0570/capture.png 199s PASS: libfprint-2/driver-egis0570.test 199s Running test: libfprint-2/virtual-device.test 199s (process:2402): libfprint-context-DEBUG: 16:48:36.113: Initializing FpContext (libfprint version 1.94.7+tod1) 199s (process:2402): libfprint-tod-DEBUG: 16:48:36.113: Impossible to load the shared drivers dir Error opening directory “/usr/lib/aarch64-linux-gnu/libfprint-2/tod-1”: No such file or directory 199s (process:2402): libfprint-context-DEBUG: 16:48:36.115: No driver found for USB device 1D6B:0003 199s (process:2402): libfprint-context-DEBUG: 16:48:36.115: No driver found for USB device 0627:0001 199s (process:2402): libfprint-context-DEBUG: 16:48:36.115: No driver found for USB device 1D6B:0002 199s (process:2402): libfprint-context-DEBUG: 16:48:36.115: Found virtual environment device: FP_VIRTUAL_DEVICE, /tmp/libfprint-5klh53a1/virtual-device.socket 199s (process:2402): libfprint-context-DEBUG: 16:48:36.116: created 199s (process:2402): libfprint-device-DEBUG: 16:48:36.116: Device reported probe completion 199s (process:2402): libfprint-device-DEBUG: 16:48:36.116: Completing action FPI_DEVICE_ACTION_PROBE in idle! 199s (process:2402): libfprint-device-DEBUG: 16:48:36.116: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 199s test_capture_unsupported (__main__.VirtualDevice.test_capture_unsupported) ... (process:2402): libfprint-virtual_device-DEBUG: 16:48:36.117: 87118102: ../libfprint/drivers/virtual-device.c:387 199s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:36.117: 87118232: ../libfprint/drivers/virtual-device-listener.c:153 199s (process:2402): libfprint-device-DEBUG: 16:48:36.117: Device reported open completion 199s (process:2402): libfprint-device-DEBUG: 16:48:36.117: Completing action FPI_DEVICE_ACTION_OPEN in idle! 199s (process:2402): libfprint-device-DEBUG: 16:48:36.117: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 199s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:36.119: Got a new connection! 199s (process:2402): libfprint-virtual_device-DEBUG: 16:48:36.119: Got instructions of length 16 199s (process:2402): libfprint-virtual_device-DEBUG: 16:48:36.119: Received command SET_KEEP_ALIVE 0 199s (process:2402): libfprint-virtual_device-DEBUG: 16:48:36.119: Keep alive toggled: 0 199s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:36.120: Got a new connection! 199s (process:2402): libfprint-virtual_device-DEBUG: 16:48:36.120: Got instructions of length 19 199s (process:2402): libfprint-virtual_device-DEBUG: 16:48:36.120: Received command SET_ENROLL_STAGES 5 199s (process:2402): libfprint-device-DEBUG: 16:48:36.120: Device reported close completion 199s (process:2402): libfprint-device-DEBUG: 16:48:36.120: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 199s (process:2402): libfprint-device-DEBUG: 16:48:36.120: 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_change_enroll_stages (__main__.VirtualDevice.test_change_enroll_stages) ... (process:2402): libfprint-virtual_device-DEBUG: 16:48:36.120: 87121423: ../libfprint/drivers/virtual-device.c:387 199s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:36.120: 87121442: ../libfprint/drivers/virtual-device-listener.c:153 199s (process:2402): libfprint-device-DEBUG: 16:48:36.120: Device reported open completion 199s (process:2402): libfprint-device-DEBUG: 16:48:36.120: Completing action FPI_DEVICE_ACTION_OPEN in idle! 199s (process:2402): libfprint-device-DEBUG: 16:48:36.121: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 199s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:36.127: Got a new connection! 199s (process:2402): libfprint-virtual_device-DEBUG: 16:48:36.128: Got instructions of length 20 199s (process:2402): libfprint-virtual_device-DEBUG: 16:48:36.128: Received command SET_ENROLL_STAGES 20 199s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:36.128: Got a new connection! 199s (process:2402): libfprint-virtual_device-DEBUG: 16:48:36.128: Got instructions of length 19 199s (process:2402): libfprint-virtual_device-DEBUG: 16:48:36.128: Received command SET_ENROLL_STAGES 1 199s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:36.128: Got a new connection! 199s (process:2402): libfprint-virtual_device-DEBUG: 16:48:36.128: Got instructions of length 19 199s (process:2402): libfprint-virtual_device-DEBUG: 16:48:36.128: Received command SET_ENROLL_STAGES 0 199s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:36.132: Got a new connection! 199s (process:2402): libfprint-virtual_device-DEBUG: 16:48:36.133: Got instructions of length 16 199s (process:2402): libfprint-virtual_device-DEBUG: 16:48:36.133: Received command SET_KEEP_ALIVE 0 199s (process:2402): libfprint-virtual_device-DEBUG: 16:48:36.133: Keep alive toggled: 0 199s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:36.133: Got a new connection! 199s (process:2402): libfprint-virtual_device-DEBUG: 16:48:36.133: Got instructions of length 19 199s (process:2402): libfprint-virtual_device-DEBUG: 16:48:36.133: Received command SET_ENROLL_STAGES 5 199s (process:2402): libfprint-device-DEBUG: 16:48:36.133: Device reported close completion 199s (process:2402): libfprint-device-DEBUG: 16:48:36.133: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 199s (process:2402): libfprint-device-DEBUG: 16:48:36.133: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 199s ok 199s test_change_scan_type (__main__.VirtualDevice.test_change_scan_type) ... (process:2402): libfprint-virtual_device-DEBUG: 16:48:36.133: 87133973: ../libfprint/drivers/virtual-device.c:387 199s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:36.133: 87133981: ../libfprint/drivers/virtual-device-listener.c:153 199s (process:2402): libfprint-device-DEBUG: 16:48:36.133: Device reported open completion 199s (process:2402): libfprint-device-DEBUG: 16:48:36.133: Completing action FPI_DEVICE_ACTION_OPEN in idle! 199s (process:2402): libfprint-device-DEBUG: 16:48:36.133: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 199s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:36.133: Got a new connection! 199s (process:2402): libfprint-virtual_device-DEBUG: 16:48:36.133: Got instructions of length 19 199s (process:2402): libfprint-virtual_device-DEBUG: 16:48:36.133: Received command SET_SCAN_TYPE press 199s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:36.133: Got a new connection! 199s (process:2402): libfprint-virtual_device-DEBUG: 16:48:36.133: Got instructions of length 19 199s (process:2402): libfprint-virtual_device-DEBUG: 16:48:36.133: Received command SET_SCAN_TYPE swipe 199s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:36.133: Got a new connection! 199s (process:2402): libfprint-virtual_device-DEBUG: 16:48:36.133: Got instructions of length 25 199s (process:2402): libfprint-virtual_device-DEBUG: 16:48:36.133: Received command SET_SCAN_TYPE eye-contact 199s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:36.134: Got a new connection! 199s (process:2402): libfprint-virtual_device-DEBUG: 16:48:36.134: Got instructions of length 16 199s (process:2402): libfprint-virtual_device-DEBUG: 16:48:36.134: Received command SET_KEEP_ALIVE 0 199s (process:2402): libfprint-virtual_device-DEBUG: 16:48:36.134: Keep alive toggled: 0 199s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:36.134: Got a new connection! 199s (process:2402): libfprint-virtual_device-DEBUG: 16:48:36.134: Got instructions of length 19 199s (process:2402): libfprint-virtual_device-DEBUG: 16:48:36.134: Received command SET_ENROLL_STAGES 5 199s (process:2402): libfprint-device-DEBUG: 16:48:36.134: Device reported close completion 199s (process:2402): libfprint-device-DEBUG: 16:48:36.134: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 199s (process:2402): libfprint-device-DEBUG: 16:48:36.134: 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_close_error (__main__.VirtualDevice.test_close_error) ... (process:2402): libfprint-virtual_device-DEBUG: 16:48:36.134: 87135097: ../libfprint/drivers/virtual-device.c:387 199s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:36.134: 87135105: ../libfprint/drivers/virtual-device-listener.c:153 199s (process:2402): libfprint-device-DEBUG: 16:48:36.134: Device reported open completion 199s (process:2402): libfprint-device-DEBUG: 16:48:36.134: Completing action FPI_DEVICE_ACTION_OPEN in idle! 199s (process:2402): libfprint-device-DEBUG: 16:48:36.134: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 199s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:36.134: Got a new connection! 199s (process:2402): libfprint-virtual_device-DEBUG: 16:48:36.134: Got instructions of length 9 199s (process:2402): libfprint-virtual_device-DEBUG: 16:48:36.134: Received command SLEEP 100 199s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:36.134: Got a new connection! 199s (process:2402): libfprint-virtual_device-DEBUG: 16:48:36.134: Got instructions of length 7 199s (process:2402): libfprint-virtual_device-DEBUG: 16:48:36.134: Received command ERROR 4 199s (process:2402): libfprint-virtual_device-DEBUG: 16:48:36.135: Processing command SLEEP 100 199s (process:2402): libfprint-virtual_device-DEBUG: 16:48:36.135: Sleeping 100ms 199s (process:2402): libfprint-virtual_device-DEBUG: 16:48:36.235: Sleeping completed 199s (process:2402): libfprint-virtual_device-DEBUG: 16:48:36.235: Processing command ERROR 4 199s (process:2402): libfprint-device-DEBUG: 16:48:36.235: Device reported close completion 199s (process:2402): libfprint-device-DEBUG: 16:48:36.235: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 199s (process:2402): libfprint-device-DEBUG: 16:48:36.235: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 199s ok 199s test_close_while_opening (__main__.VirtualDevice.test_close_while_opening) ... (process:2402): libfprint-virtual_device-DEBUG: 16:48:36.236: 87236828: ../libfprint/drivers/virtual-device.c:387 199s (process:2402): libfprint-device-DEBUG: 16:48:36.236: Device reported open completion 199s (process:2402): libfprint-device-DEBUG: 16:48:36.236: Completing action FPI_DEVICE_ACTION_OPEN in idle! 199s (process:2402): libfprint-device-DEBUG: 16:48:36.236: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 199s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:36.236: Got a new connection! 199s (process:2402): libfprint-virtual_device-DEBUG: 16:48:36.236: Got instructions of length 16 199s (process:2402): libfprint-virtual_device-DEBUG: 16:48:36.236: Received command SET_KEEP_ALIVE 1 199s (process:2402): libfprint-virtual_device-DEBUG: 16:48:36.236: Keep alive toggled: 1 199s (process:2402): libfprint-device-DEBUG: 16:48:36.236: Device reported close completion 199s (process:2402): libfprint-device-DEBUG: 16:48:36.236: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 199s (process:2402): libfprint-device-DEBUG: 16:48:36.236: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 199s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:36.236: Got a new connection! 199s (process:2402): libfprint-virtual_device-DEBUG: 16:48:36.236: Got instructions of length 9 199s (process:2402): libfprint-virtual_device-DEBUG: 16:48:36.236: Received command SLEEP 500 199s (process:2402): libfprint-virtual_device-DEBUG: 16:48:36.236: 87237644: ../libfprint/drivers/virtual-device.c:387 199s (process:2402): libfprint-virtual_device-DEBUG: 16:48:36.236: Processing command SLEEP 500 199s (process:2402): libfprint-virtual_device-DEBUG: 16:48:36.237: Sleeping 500ms 199s (process:2402): libfprint-virtual_device-DEBUG: 16:48:36.737: Sleeping completed 199s (process:2402): libfprint-virtual_device-DEBUG: 16:48:36.737: 87738448: ../libfprint/drivers/virtual-device.c:387 199s (process:2402): libfprint-device-DEBUG: 16:48:36.737: Device reported open completion 199s (process:2402): libfprint-device-DEBUG: 16:48:36.737: Completing action FPI_DEVICE_ACTION_OPEN in idle! 199s (process:2402): libfprint-device-DEBUG: 16:48:36.737: Updated temperature model after 0.50 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 199s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:36.738: Got a new connection! 199s (process:2402): libfprint-virtual_device-DEBUG: 16:48:36.738: Got instructions of length 16 199s (process:2402): libfprint-virtual_device-DEBUG: 16:48:36.738: Received command SET_KEEP_ALIVE 0 199s (process:2402): libfprint-virtual_device-DEBUG: 16:48:36.738: Keep alive toggled: 0 199s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:36.738: Got a new connection! 199s (process:2402): libfprint-virtual_device-DEBUG: 16:48:36.738: Got instructions of length 19 199s (process:2402): libfprint-virtual_device-DEBUG: 16:48:36.738: Received command SET_ENROLL_STAGES 5 199s (process:2402): libfprint-device-DEBUG: 16:48:36.738: Device reported close completion 199s (process:2402): libfprint-device-DEBUG: 16:48:36.738: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 199s (process:2402): libfprint-device-DEBUG: 16:48:36.738: 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_delayed_open (__main__.VirtualDevice.test_delayed_open) ... (process:2402): libfprint-virtual_device-DEBUG: 16:48:36.738: 87739441: ../libfprint/drivers/virtual-device.c:387 199s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:36.738: 87739471: ../libfprint/drivers/virtual-device-listener.c:153 199s (process:2402): libfprint-device-DEBUG: 16:48:36.738: Device reported open completion 199s (process:2402): libfprint-device-DEBUG: 16:48:36.738: Completing action FPI_DEVICE_ACTION_OPEN in idle! 199s (process:2402): libfprint-device-DEBUG: 16:48:36.738: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 199s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:36.739: Got a new connection! 199s (process:2402): libfprint-virtual_device-DEBUG: 16:48:36.739: Got instructions of length 16 199s (process:2402): libfprint-virtual_device-DEBUG: 16:48:36.739: Received command IGNORED_COMMAND 199s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:36.739: Got a new connection! 199s (process:2402): libfprint-virtual_device-DEBUG: 16:48:36.739: Got instructions of length 9 199s (process:2402): libfprint-virtual_device-DEBUG: 16:48:36.739: Received command SLEEP 500 199s (process:2402): libfprint-virtual_device-DEBUG: 16:48:36.739: Processing command IGNORED_COMMAND 199s (process:2402): libfprint-device-DEBUG: 16:48:36.739: Device reported close completion 199s (process:2402): libfprint-device-DEBUG: 16:48:36.739: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 199s (process:2402): libfprint-device-DEBUG: 16:48:36.739: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 199s (process:2402): libfprint-virtual_device-DEBUG: 16:48:36.739: 87740464: ../libfprint/drivers/virtual-device.c:387 199s (process:2402): libfprint-virtual_device-DEBUG: 16:48:36.739: Processing command SLEEP 500 199s (process:2402): libfprint-virtual_device-DEBUG: 16:48:36.739: Sleeping 500ms 200s (process:2402): libfprint-virtual_device-DEBUG: 16:48:37.240: Sleeping completed 200s (process:2402): libfprint-virtual_device-DEBUG: 16:48:37.240: 88241381: ../libfprint/drivers/virtual-device.c:387 200s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:37.240: 88241406: ../libfprint/drivers/virtual-device-listener.c:153 200s (process:2402): libfprint-device-DEBUG: 16:48:37.240: Device reported open completion 200s (process:2402): libfprint-device-DEBUG: 16:48:37.240: Completing action FPI_DEVICE_ACTION_OPEN in idle! 200s (process:2402): libfprint-device-DEBUG: 16:48:37.240: Updated temperature model after 0.50 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 200s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:37.241: Got a new connection! 200s (process:2402): libfprint-virtual_device-DEBUG: 16:48:37.241: Got instructions of length 16 200s (process:2402): libfprint-virtual_device-DEBUG: 16:48:37.241: Received command SET_KEEP_ALIVE 0 200s (process:2402): libfprint-virtual_device-DEBUG: 16:48:37.241: Keep alive toggled: 0 200s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:37.241: Got a new connection! 200s (process:2402): libfprint-virtual_device-DEBUG: 16:48:37.241: Got instructions of length 19 200s (process:2402): libfprint-virtual_device-DEBUG: 16:48:37.241: Received command SET_ENROLL_STAGES 5 200s (process:2402): libfprint-device-DEBUG: 16:48:37.241: Device reported close completion 200s (process:2402): libfprint-device-DEBUG: 16:48:37.241: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 200s (process:2402): libfprint-device-DEBUG: 16:48:37.241: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 200s ok 200s test_delayed_open_with_keep_alive (__main__.VirtualDevice.test_delayed_open_with_keep_alive) ... (process:2402): libfprint-virtual_device-DEBUG: 16:48:37.241: 88242444: ../libfprint/drivers/virtual-device.c:387 200s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:37.241: 88242472: ../libfprint/drivers/virtual-device-listener.c:153 200s (process:2402): libfprint-device-DEBUG: 16:48:37.241: Device reported open completion 200s (process:2402): libfprint-device-DEBUG: 16:48:37.241: Completing action FPI_DEVICE_ACTION_OPEN in idle! 200s (process:2402): libfprint-device-DEBUG: 16:48:37.241: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 200s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:37.242: Got a new connection! 200s (process:2402): libfprint-virtual_device-DEBUG: 16:48:37.242: Got instructions of length 16 200s (process:2402): libfprint-virtual_device-DEBUG: 16:48:37.242: Received command SET_KEEP_ALIVE 1 200s (process:2402): libfprint-virtual_device-DEBUG: 16:48:37.242: Keep alive toggled: 1 200s (process:2402): libfprint-device-DEBUG: 16:48:37.242: Device reported close completion 200s (process:2402): libfprint-device-DEBUG: 16:48:37.242: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 200s (process:2402): libfprint-device-DEBUG: 16:48:37.242: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 200s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:37.242: Got a new connection! 200s (process:2402): libfprint-virtual_device-DEBUG: 16:48:37.242: Got instructions of length 9 200s (process:2402): libfprint-virtual_device-DEBUG: 16:48:37.242: Received command SLEEP 500 200s (process:2402): libfprint-virtual_device-DEBUG: 16:48:37.242: 88243227: ../libfprint/drivers/virtual-device.c:387 200s (process:2402): libfprint-virtual_device-DEBUG: 16:48:37.242: Processing command SLEEP 500 200s (process:2402): libfprint-virtual_device-DEBUG: 16:48:37.242: Sleeping 500ms 200s (process:2402): libfprint-virtual_device-DEBUG: 16:48:37.743: Sleeping completed 200s (process:2402): libfprint-virtual_device-DEBUG: 16:48:37.743: 88743977: ../libfprint/drivers/virtual-device.c:387 200s (process:2402): libfprint-device-DEBUG: 16:48:37.743: Device reported open completion 200s (process:2402): libfprint-device-DEBUG: 16:48:37.743: Completing action FPI_DEVICE_ACTION_OPEN in idle! 200s (process:2402): libfprint-device-DEBUG: 16:48:37.743: Updated temperature model after 0.50 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 200s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:37.743: Got a new connection! 200s (process:2402): libfprint-virtual_device-DEBUG: 16:48:37.743: Got instructions of length 16 200s (process:2402): libfprint-virtual_device-DEBUG: 16:48:37.743: Received command SET_KEEP_ALIVE 0 200s (process:2402): libfprint-virtual_device-DEBUG: 16:48:37.743: Keep alive toggled: 0 200s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:37.743: Got a new connection! 200s (process:2402): libfprint-virtual_device-DEBUG: 16:48:37.743: Got instructions of length 19 200s (process:2402): libfprint-virtual_device-DEBUG: 16:48:37.743: Received command SET_ENROLL_STAGES 5 200s (process:2402): libfprint-device-DEBUG: 16:48:37.744: Device reported close completion 200s (process:2402): libfprint-device-DEBUG: 16:48:37.744: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 200s (process:2402): libfprint-device-DEBUG: 16:48:37.744: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 200s ok 200s test_device_features (__main__.VirtualDevice.test_device_features) ... (process:2402): libfprint-virtual_device-DEBUG: 16:48:37.744: 88744974: ../libfprint/drivers/virtual-device.c:387 200s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:37.744: 88745003: ../libfprint/drivers/virtual-device-listener.c:153 200s (process:2402): libfprint-device-DEBUG: 16:48:37.744: Device reported open completion 200s (process:2402): libfprint-device-DEBUG: 16:48:37.744: Completing action FPI_DEVICE_ACTION_OPEN in idle! 200s (process:2402): libfprint-device-DEBUG: 16:48:37.744: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 200s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:37.744: Got a new connection! 200s (process:2402): libfprint-virtual_device-DEBUG: 16:48:37.744: Got instructions of length 16 200s (process:2402): libfprint-virtual_device-DEBUG: 16:48:37.744: Received command SET_KEEP_ALIVE 0 200s (process:2402): libfprint-virtual_device-DEBUG: 16:48:37.744: Keep alive toggled: 0 200s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:37.745: Got a new connection! 200s (process:2402): libfprint-virtual_device-DEBUG: 16:48:37.745: Got instructions of length 19 200s (process:2402): libfprint-virtual_device-DEBUG: 16:48:37.745: Received command SET_ENROLL_STAGES 5 200s (process:2402): libfprint-device-DEBUG: 16:48:37.745: Device reported close completion 200s (process:2402): libfprint-device-DEBUG: 16:48:37.745: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 200s (process:2402): libfprint-device-DEBUG: 16:48:37.745: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 200s ok 200s test_device_properties (__main__.VirtualDevice.test_device_properties) ... (process:2402): libfprint-virtual_device-DEBUG: 16:48:37.745: 88746040: ../libfprint/drivers/virtual-device.c:387 200s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:37.745: 88746067: ../libfprint/drivers/virtual-device-listener.c:153 200s (process:2402): libfprint-device-DEBUG: 16:48:37.745: Device reported open completion 200s (process:2402): libfprint-device-DEBUG: 16:48:37.745: Completing action FPI_DEVICE_ACTION_OPEN in idle! 200s (process:2402): libfprint-device-DEBUG: 16:48:37.745: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 200s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:37.745: Got a new connection! 200s (process:2402): libfprint-virtual_device-DEBUG: 16:48:37.745: Got instructions of length 16 200s /usr/libexec/installed-tests/libfprint-2/virtual-device.py:463: DeprecationWarning: FPrint.Device.supports_identify is deprecated 200s self.assertFalse(self.dev.supports_identify()) 200s /usr/libexec/installed-tests/libfprint-2/virtual-device.py:464: DeprecationWarning: FPrint.Device.supports_capture is deprecated 200s self.assertFalse(self.dev.supports_capture()) 200s /usr/libexec/installed-tests/libfprint-2/virtual-device.py:465: DeprecationWarning: FPrint.Device.has_storage is deprecated 200s self.assertFalse(self.dev.has_storage()) 200s (process:2402): libfprint-virtual_device-DEBUG: 16:48:37.745: Received command SET_KEEP_ALIVE 0 200s (process:2402): libfprint-virtual_device-DEBUG: 16:48:37.745: Keep alive toggled: 0 200s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:37.746: Got a new connection! 200s (process:2402): libfprint-virtual_device-DEBUG: 16:48:37.746: Got instructions of length 19 200s (process:2402): libfprint-virtual_device-DEBUG: 16:48:37.746: Received command SET_ENROLL_STAGES 5 200s (process:2402): libfprint-device-DEBUG: 16:48:37.746: Device reported close completion 200s (process:2402): libfprint-device-DEBUG: 16:48:37.746: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 200s (process:2402): libfprint-device-DEBUG: 16:48:37.746: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 200s ok 200s test_device_sleep (__main__.VirtualDevice.test_device_sleep) ... (process:2402): libfprint-virtual_device-DEBUG: 16:48:37.746: 88747128: ../libfprint/drivers/virtual-device.c:387 200s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:37.746: 88747155: ../libfprint/drivers/virtual-device-listener.c:153 200s (process:2402): libfprint-device-DEBUG: 16:48:37.746: Device reported open completion 200s (process:2402): libfprint-device-DEBUG: 16:48:37.746: Completing action FPI_DEVICE_ACTION_OPEN in idle! 200s (process:2402): libfprint-device-DEBUG: 16:48:37.746: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 200s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:37.746: Got a new connection! 200s (process:2402): libfprint-virtual_device-DEBUG: 16:48:37.746: Got instructions of length 10 200s (process:2402): libfprint-virtual_device-DEBUG: 16:48:37.746: Received command SLEEP 1500 200s (process:2402): libfprint-device-DEBUG: 16:48:37.747: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 200s (process:2402): libfprint-virtual_device-DEBUG: 16:48:37.747: Processing command SLEEP 1500 200s (process:2402): libfprint-virtual_device-DEBUG: 16:48:37.747: Sleeping 1500ms 201s (process:2402): libfprint-device-DEBUG: 16:48:38.046: Updated temperature model after 0.30 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 201s (process:2402): libfprint-device-DEBUG: 16:48:38.047: Idle cancelling on ongoing operation! 201s (process:2402): libfprint-virtual_device-DEBUG: 16:48:38.047: Got cancellation! 201s (process:2402): libfprint-device-DEBUG: 16:48:38.047: Device reported finger status change: FP_FINGER_STATUS_NEEDED 201s (process:2402): libfprint-virtual_device-DEBUG: 16:48:38.047: Virtual device scan failed with error: Operation was cancelled 201s (process:2402): libfprint-device-DEBUG: 16:48:38.047: Device reported verify completion 201s (process:2402): libfprint-device-DEBUG: 16:48:38.047: Device reported finger status change: FP_FINGER_STATUS_NONE 201s (process:2402): libfprint-device-DEBUG: 16:48:38.047: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 201s (process:2402): libfprint-device-DEBUG: 16:48:38.047: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 201s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:38.247: Got a new connection! 201s (process:2402): libfprint-virtual_device-DEBUG: 16:48:38.248: Got instructions of length 16 201s (process:2402): libfprint-virtual_device-DEBUG: 16:48:38.248: Received command SET_KEEP_ALIVE 0 201s (process:2402): libfprint-virtual_device-DEBUG: 16:48:38.248: Keep alive toggled: 0 201s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:38.248: Got a new connection! 201s (process:2402): libfprint-virtual_device-DEBUG: 16:48:38.248: Got instructions of length 19 201s (process:2402): libfprint-virtual_device-DEBUG: 16:48:38.248: Received command SET_ENROLL_STAGES 5 201s (process:2402): libfprint-device-DEBUG: 16:48:38.248: Device reported close completion 201s (process:2402): libfprint-device-DEBUG: 16:48:38.248: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 201s (process:2402): libfprint-device-DEBUG: 16:48:38.248: Updated temperature model after 0.20 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 201s ok 201s test_device_sleep_before_completing_verify (__main__.VirtualDevice.test_device_sleep_before_completing_verify) ... (process:2402): libfprint-virtual_device-DEBUG: 16:48:38.248: 89249311: ../libfprint/drivers/virtual-device.c:387 201s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:38.248: 89249340: ../libfprint/drivers/virtual-device-listener.c:153 201s (process:2402): libfprint-device-DEBUG: 16:48:38.248: Device reported open completion 201s (process:2402): libfprint-device-DEBUG: 16:48:38.248: Completing action FPI_DEVICE_ACTION_OPEN in idle! 201s (process:2402): libfprint-device-DEBUG: 16:48:38.248: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 201s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:38.249: Got a new connection! 201s (process:2402): libfprint-virtual_device-DEBUG: 16:48:38.249: Got instructions of length 14 201s (process:2402): libfprint-virtual_device-DEBUG: 16:48:38.249: Received command SCAN foo-print 201s (process:2402): libfprint-device-DEBUG: 16:48:38.249: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 201s (process:2402): libfprint-virtual_device-DEBUG: 16:48:38.249: Processing command SCAN foo-print 201s (process:2402): libfprint-device-DEBUG: 16:48:38.249: Device reported finger status change: FP_FINGER_STATUS_NEEDED 201s (process:2402): libfprint-device-DEBUG: 16:48:38.249: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 201s (process:2402): libfprint-device-DEBUG: 16:48:38.249: Device reported finger status change: FP_FINGER_STATUS_NEEDED 201s (process:2402): libfprint-device-DEBUG: 16:48:38.249: Device reported enroll progress, reported 1 of 5 have been completed 201s (process:2402): libfprint-virtual_device-DEBUG: 16:48:38.249: Sleeping completed 201s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:38.249: Got a new connection! 201s (process:2402): libfprint-virtual_device-DEBUG: 16:48:38.249: Got instructions of length 14 201s (process:2402): libfprint-virtual_device-DEBUG: 16:48:38.249: Received command SCAN foo-print 201s (process:2402): libfprint-virtual_device-DEBUG: 16:48:38.249: Processing command SCAN foo-print 201s (process:2402): libfprint-device-DEBUG: 16:48:38.249: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 201s (process:2402): libfprint-device-DEBUG: 16:48:38.249: Device reported finger status change: FP_FINGER_STATUS_NEEDED 201s (process:2402): libfprint-device-DEBUG: 16:48:38.249: Device reported enroll progress, reported 2 of 5 have been completed 201s (process:2402): libfprint-virtual_device-DEBUG: 16:48:38.249: Sleeping completed 201s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:38.250: Got a new connection! 201s (process:2402): libfprint-virtual_device-DEBUG: 16:48:38.250: Got instructions of length 14 201s (process:2402): libfprint-virtual_device-DEBUG: 16:48:38.250: Received command SCAN foo-print 201s (process:2402): libfprint-virtual_device-DEBUG: 16:48:38.250: Processing command SCAN foo-print 201s (process:2402): libfprint-device-DEBUG: 16:48:38.250: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 201s (process:2402): libfprint-device-DEBUG: 16:48:38.250: Device reported finger status change: FP_FINGER_STATUS_NEEDED 201s (process:2402): libfprint-device-DEBUG: 16:48:38.250: Device reported enroll progress, reported 3 of 5 have been completed 201s (process:2402): libfprint-virtual_device-DEBUG: 16:48:38.250: Sleeping completed 201s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:38.250: Got a new connection! 201s (process:2402): libfprint-virtual_device-DEBUG: 16:48:38.250: Got instructions of length 14 201s (process:2402): libfprint-virtual_device-DEBUG: 16:48:38.250: Received command SCAN foo-print 201s (process:2402): libfprint-virtual_device-DEBUG: 16:48:38.250: Processing command SCAN foo-print 201s (process:2402): libfprint-device-DEBUG: 16:48:38.250: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 201s (process:2402): libfprint-device-DEBUG: 16:48:38.250: Device reported finger status change: FP_FINGER_STATUS_NEEDED 201s (process:2402): libfprint-device-DEBUG: 16:48:38.250: Device reported enroll progress, reported 4 of 5 have been completed 201s (process:2402): libfprint-virtual_device-DEBUG: 16:48:38.250: Sleeping completed 201s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:38.250: Got a new connection! 201s (process:2402): libfprint-virtual_device-DEBUG: 16:48:38.250: Got instructions of length 14 201s (process:2402): libfprint-virtual_device-DEBUG: 16:48:38.250: Received command SCAN foo-print 201s (process:2402): libfprint-virtual_device-DEBUG: 16:48:38.250: Processing command SCAN foo-print 201s (process:2402): libfprint-device-DEBUG: 16:48:38.250: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 201s (process:2402): libfprint-device-DEBUG: 16:48:38.250: Device reported finger status change: FP_FINGER_STATUS_NEEDED 201s (process:2402): libfprint-device-DEBUG: 16:48:38.250: Device reported enroll progress, reported 5 of 5 have been completed 201s (process:2402): libfprint-device-DEBUG: 16:48:38.250: Device reported enroll completion 201s (process:2402): libfprint-device-DEBUG: 16:48:38.250: Device reported finger status change: FP_FINGER_STATUS_NONE 201s (process:2402): libfprint-device-DEBUG: 16:48:38.251: Print for finger FP_FINGER_LEFT_RING enrolled 201s (process:2402): libfprint-device-DEBUG: 16:48:38.251: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 201s (process:2402): libfprint-device-DEBUG: 16:48:38.251: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 201s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:38.251: Got a new connection! 201s (process:2402): libfprint-virtual_device-DEBUG: 16:48:38.251: Got instructions of length 9 201s (process:2402): libfprint-virtual_device-DEBUG: 16:48:38.251: Received command SLEEP 100 201s (process:2402): libfprint-device-DEBUG: 16:48:38.251: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 201s (process:2402): libfprint-virtual_device-DEBUG: 16:48:38.251: Processing command SLEEP 100 201s (process:2402): libfprint-virtual_device-DEBUG: 16:48:38.251: Sleeping 100ms 201s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:38.251: Got a new connection! 201s (process:2402): libfprint-virtual_device-DEBUG: 16:48:38.251: Got instructions of length 14 201s (process:2402): libfprint-virtual_device-DEBUG: 16:48:38.251: Received command SCAN bar-print 201s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:38.251: Got a new connection! 201s (process:2402): libfprint-virtual_device-DEBUG: 16:48:38.252: Got instructions of length 9 201s (process:2402): libfprint-virtual_device-DEBUG: 16:48:38.252: Received command SLEEP 800 201s (process:2402): libfprint-virtual_device-DEBUG: 16:48:38.351: Sleeping completed 201s (process:2402): libfprint-virtual_device-DEBUG: 16:48:38.351: Processing command SCAN bar-print 201s (process:2402): libfprint-device-DEBUG: 16:48:38.351: Device reported finger status change: FP_FINGER_STATUS_NEEDED 201s (process:2402): libfprint-device-DEBUG: 16:48:38.351: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 201s (process:2402): libfprint-virtual_device-DEBUG: 16:48:38.351: Virtual device scanned print bar-print 201s (process:2402): libfprint-device-DEBUG: 16:48:38.351: Device reported verify result 201s (process:2402): libfprint-device-DEBUG: 16:48:38.351: Device reported finger status change: FP_FINGER_STATUS_NEEDED 201s (process:2402): libfprint-virtual_device-DEBUG: 16:48:38.351: Processing command SLEEP 800 201s (process:2402): libfprint-virtual_device-DEBUG: 16:48:38.352: Sleeping 800ms 201s (process:2402): libfprint-virtual_device-DEBUG: 16:48:38.352: Sleeping now, command queued for later: SCAN bar-print 202s Executing: libfprint-2/virtual-device.test 202s (process:2402): libfprint-virtual_device-DEBUG: 16:48:39.152: Sleeping completed 202s (process:2402): libfprint-virtual_device-DEBUG: 16:48:39.153: Processing command SCAN bar-print 202s (process:2402): libfprint-device-DEBUG: 16:48:39.153: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 202s (process:2402): libfprint-virtual_device-DEBUG: 16:48:39.153: Virtual device scanned print bar-print 202s (process:2402): libfprint-device-DEBUG: 16:48:39.153: Device reported finger status change: FP_FINGER_STATUS_NEEDED 202s (process:2402): libfprint-device-DEBUG: 16:48:39.153: Device reported verify completion 202s (process:2402): libfprint-device-DEBUG: 16:48:39.153: Device reported finger status change: FP_FINGER_STATUS_NONE 202s (process:2402): libfprint-device-DEBUG: 16:48:39.153: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 202s (process:2402): libfprint-device-DEBUG: 16:48:39.153: Updated temperature model after 0.90 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 202s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:39.153: Got a new connection! 202s (process:2402): libfprint-virtual_device-DEBUG: 16:48:39.153: Got instructions of length 16 202s (process:2402): libfprint-virtual_device-DEBUG: 16:48:39.153: Received command SET_KEEP_ALIVE 0 202s (process:2402): libfprint-virtual_device-DEBUG: 16:48:39.153: Keep alive toggled: 0 202s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:39.154: Got a new connection! 202s (process:2402): libfprint-virtual_device-DEBUG: 16:48:39.154: Got instructions of length 19 202s (process:2402): libfprint-virtual_device-DEBUG: 16:48:39.154: Received command SET_ENROLL_STAGES 5 202s (process:2402): libfprint-device-DEBUG: 16:48:39.154: Device reported close completion 202s (process:2402): libfprint-device-DEBUG: 16:48:39.154: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 202s (process:2402): libfprint-device-DEBUG: 16:48:39.154: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 202s Enroll done 202s ok 202s test_device_sleep_on_cancellation (__main__.VirtualDevice.test_device_sleep_on_cancellation) ... (process:2402): libfprint-virtual_device-DEBUG: 16:48:39.154: 90155584: ../libfprint/drivers/virtual-device.c:387 202s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:39.154: 90155681: ../libfprint/drivers/virtual-device-listener.c:153 202s (process:2402): libfprint-device-DEBUG: 16:48:39.155: Device reported open completion 202s (process:2402): libfprint-device-DEBUG: 16:48:39.155: Completing action FPI_DEVICE_ACTION_OPEN in idle! 202s (process:2402): libfprint-device-DEBUG: 16:48:39.155: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 202s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:39.155: Got a new connection! 202s (process:2402): libfprint-virtual_device-DEBUG: 16:48:39.155: Got instructions of length 26 202s (process:2402): libfprint-virtual_device-DEBUG: 16:48:39.155: Received command SET_CANCELLATION_ENABLED 0 202s (process:2402): libfprint-virtual_device-DEBUG: 16:48:39.155: Cancellation support toggled: 0 202s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:39.155: Got a new connection! 202s (process:2402): libfprint-virtual_device-DEBUG: 16:48:39.156: Got instructions of length 10 202s (process:2402): libfprint-virtual_device-DEBUG: 16:48:39.156: Received command SLEEP 1500 202s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:39.156: Got a new connection! 202s (process:2402): libfprint-virtual_device-DEBUG: 16:48:39.156: Got instructions of length 14 202s (process:2402): libfprint-virtual_device-DEBUG: 16:48:39.156: Received command SCAN foo-print 202s (process:2402): libfprint-device-DEBUG: 16:48:39.156: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 202s (process:2402): libfprint-virtual_device-DEBUG: 16:48:39.156: Processing command SLEEP 1500 202s (process:2402): libfprint-virtual_device-DEBUG: 16:48:39.156: Sleeping 1500ms 202s (process:2402): libfprint-device-DEBUG: 16:48:39.456: Idle cancelling on ongoing operation! 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.657: Sleeping completed 203s (process:2402): libfprint-device-DEBUG: 16:48:40.657: Device reported finger status change: FP_FINGER_STATUS_NEEDED 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.658: Virtual device scan failed with error: Operation was cancelled 203s (process:2402): libfprint-device-DEBUG: 16:48:40.658: Device reported verify completion 203s (process:2402): libfprint-device-DEBUG: 16:48:40.658: Device reported finger status change: FP_FINGER_STATUS_NONE 203s (process:2402): libfprint-device-DEBUG: 16:48:40.658: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 203s (process:2402): libfprint-device-DEBUG: 16:48:40.658: Updated temperature model after 1.50 seconds, ratio 0.27 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.658: Processing command SCAN foo-print 203s (process:2402): libfprint-device-DEBUG: 16:48:40.658: Device reported close completion 203s (process:2402): libfprint-device-DEBUG: 16:48:40.658: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 203s (process:2402): libfprint-device-DEBUG: 16:48:40.658: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 203s ok 203s test_enroll (__main__.VirtualDevice.test_enroll) ... (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.659: 91659772: ../libfprint/drivers/virtual-device.c:387 203s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:40.659: 91659824: ../libfprint/drivers/virtual-device-listener.c:153 203s (process:2402): libfprint-device-DEBUG: 16:48:40.659: Device reported open completion 203s (process:2402): libfprint-device-DEBUG: 16:48:40.659: Completing action FPI_DEVICE_ACTION_OPEN in idle! 203s (process:2402): libfprint-device-DEBUG: 16:48:40.659: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 203s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:40.659: Got a new connection! 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.659: Got instructions of length 14 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.659: Received command SCAN testprint 203s (process:2402): libfprint-device-DEBUG: 16:48:40.659: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.659: Processing command SCAN testprint 203s (process:2402): libfprint-device-DEBUG: 16:48:40.659: Device reported finger status change: FP_FINGER_STATUS_NEEDED 203s (process:2402): libfprint-device-DEBUG: 16:48:40.659: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 203s (process:2402): libfprint-device-DEBUG: 16:48:40.659: Device reported finger status change: FP_FINGER_STATUS_NEEDED 203s (process:2402): libfprint-device-DEBUG: 16:48:40.659: Device reported enroll progress, reported 1 of 5 have been completed 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.659: Sleeping completed 203s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:40.659: Got a new connection! 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.659: Got instructions of length 14 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.659: Received command SCAN testprint 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.659: Processing command SCAN testprint 203s (process:2402): libfprint-device-DEBUG: 16:48:40.659: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 203s (process:2402): libfprint-device-DEBUG: 16:48:40.659: Device reported finger status change: FP_FINGER_STATUS_NEEDED 203s (process:2402): libfprint-device-DEBUG: 16:48:40.659: Device reported enroll progress, reported 2 of 5 have been completed 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.659: Sleeping completed 203s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:40.659: Got a new connection! 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.659: Got instructions of length 14 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.659: Received command SCAN testprint 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.659: Processing command SCAN testprint 203s (process:2402): libfprint-device-DEBUG: 16:48:40.659: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 203s (process:2402): libfprint-device-DEBUG: 16:48:40.660: Device reported finger status change: FP_FINGER_STATUS_NEEDED 203s (process:2402): libfprint-device-DEBUG: 16:48:40.660: Device reported enroll progress, reported 3 of 5 have been completed 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.660: Sleeping completed 203s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:40.660: Got a new connection! 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.660: Got instructions of length 14 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.660: Received command SCAN testprint 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.660: Processing command SCAN testprint 203s (process:2402): libfprint-device-DEBUG: 16:48:40.660: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 203s (process:2402): libfprint-device-DEBUG: 16:48:40.660: Device reported finger status change: FP_FINGER_STATUS_NEEDED 203s (process:2402): libfprint-device-DEBUG: 16:48:40.660: Device reported enroll progress, reported 4 of 5 have been completed 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.660: Sleeping completed 203s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:40.660: Got a new connection! 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.660: Got instructions of length 14 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.660: Received command SCAN testprint 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.660: Processing command SCAN testprint 203s (process:2402): libfprint-device-DEBUG: 16:48:40.660: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 203s (process:2402): libfprint-device-DEBUG: 16:48:40.660: Device reported finger status change: FP_FINGER_STATUS_NEEDED 203s (process:2402): libfprint-device-DEBUG: 16:48:40.660: Device reported enroll progress, reported 5 of 5 have been completed 203s (process:2402): libfprint-device-DEBUG: 16:48:40.660: Device reported enroll completion 203s (process:2402): libfprint-device-DEBUG: 16:48:40.660: Device reported finger status change: FP_FINGER_STATUS_NONE 203s (process:2402): libfprint-device-DEBUG: 16:48:40.660: Print for finger FP_FINGER_LEFT_LITTLE enrolled 203s (process:2402): libfprint-device-DEBUG: 16:48:40.660: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 203s (process:2402): libfprint-device-DEBUG: 16:48:40.660: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 203s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:40.660: Got a new connection! 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.660: Got instructions of length 16 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.660: Received command SET_KEEP_ALIVE 0 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.660: Keep alive toggled: 0 203s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:40.660: Got a new connection! 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.660: Got instructions of length 19 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.660: Received command SET_ENROLL_STAGES 5 203s (process:2402): libfprint-device-DEBUG: 16:48:40.660: Device reported close completion 203s (process:2402): libfprint-device-DEBUG: 16:48:40.660: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 203s (process:2402): libfprint-device-DEBUG: 16:48:40.660: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 203s Enroll done 203s ok 203s test_enroll_script (__main__.VirtualDevice.test_enroll_script) ... (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.660: 91661595: ../libfprint/drivers/virtual-device.c:387 203s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:40.660: 91661604: ../libfprint/drivers/virtual-device-listener.c:153 203s (process:2402): libfprint-device-DEBUG: 16:48:40.660: Device reported open completion 203s (process:2402): libfprint-device-DEBUG: 16:48:40.660: Completing action FPI_DEVICE_ACTION_OPEN in idle! 203s (process:2402): libfprint-device-DEBUG: 16:48:40.661: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 203s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:40.661: Got a new connection! 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.661: Got instructions of length 19 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.661: Received command SET_ENROLL_STAGES 8 203s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:40.661: Got a new connection! 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.661: Got instructions of length 13 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.661: Received command SCAN print-id 203s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:40.661: Got a new connection! 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.661: Got instructions of length 13 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.661: Received command SCAN print-id 203s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:40.661: Got a new connection! 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.661: Got instructions of length 7 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.661: Received command RETRY 1 203s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:40.661: Got a new connection! 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.661: Got instructions of length 13 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.661: Received command SCAN print-id 203s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:40.661: Got a new connection! 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.661: Got instructions of length 7 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.661: Received command RETRY 3 203s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:40.661: Got a new connection! 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.661: Got instructions of length 13 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.661: Received command SCAN print-id 203s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:40.661: Got a new connection! 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.661: Got instructions of length 7 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.661: Received command RETRY 2 203s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:40.661: Got a new connection! 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.661: Got instructions of length 13 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.661: Received command SCAN print-id 203s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:40.661: Got a new connection! 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.661: Got instructions of length 8 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.661: Received command SLEEP 10 203s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:40.662: Got a new connection! 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.662: Got instructions of length 8 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.662: Received command SLEEP 20 203s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:40.662: Got a new connection! 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.662: Got instructions of length 7 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.662: Received command RETRY 0 203s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:40.662: Got a new connection! 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.662: Got instructions of length 7 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.662: Received command RETRY 3 203s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:40.662: Got a new connection! 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.662: Got instructions of length 13 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.662: Received command SCAN print-id 203s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:40.662: Got a new connection! 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.662: Got instructions of length 15 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.662: Received command SCAN another-id 203s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:40.662: Got a new connection! 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.662: Got instructions of length 13 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.662: Received command SCAN print-id 203s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:40.662: Got a new connection! 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.662: Got instructions of length 13 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.662: Received command SCAN print-id 203s (process:2402): libfprint-device-DEBUG: 16:48:40.662: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.662: Processing command SCAN print-id 203s (process:2402): libfprint-device-DEBUG: 16:48:40.662: Device reported finger status change: FP_FINGER_STATUS_NEEDED 203s (process:2402): libfprint-device-DEBUG: 16:48:40.662: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 203s (process:2402): libfprint-device-DEBUG: 16:48:40.662: Device reported finger status change: FP_FINGER_STATUS_NEEDED 203s (process:2402): libfprint-device-DEBUG: 16:48:40.662: Device reported enroll progress, reported 1 of 8 have been completed 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.662: Sleeping completed 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.662: Processing command SCAN print-id 203s (process:2402): libfprint-device-DEBUG: 16:48:40.662: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 203s (process:2402): libfprint-device-DEBUG: 16:48:40.662: Device reported finger status change: FP_FINGER_STATUS_NEEDED 203s (process:2402): libfprint-device-DEBUG: 16:48:40.662: Device reported enroll progress, reported 2 of 8 have been completed 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.662: Sleeping completed 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.662: Processing command RETRY 1 203s (process:2402): libfprint-device-DEBUG: 16:48:40.662: Device reported enroll progress, reported 2 of 8 have been completed 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.662: Sleeping completed 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.662: Processing command SCAN print-id 203s (process:2402): libfprint-device-DEBUG: 16:48:40.662: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 203s (process:2402): libfprint-device-DEBUG: 16:48:40.662: Device reported finger status change: FP_FINGER_STATUS_NEEDED 203s (process:2402): libfprint-device-DEBUG: 16:48:40.662: Device reported enroll progress, reported 3 of 8 have been completed 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.662: Sleeping completed 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.662: Processing command RETRY 3 203s (process:2402): libfprint-device-DEBUG: 16:48:40.662: Device reported enroll progress, reported 3 of 8 have been completed 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.662: Sleeping completed 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.662: Processing command SCAN print-id 203s (process:2402): libfprint-device-DEBUG: 16:48:40.662: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 203s (process:2402): libfprint-device-DEBUG: 16:48:40.662: Device reported finger status change: FP_FINGER_STATUS_NEEDED 203s (process:2402): libfprint-device-DEBUG: 16:48:40.662: Device reported enroll progress, reported 4 of 8 have been completed 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.662: Sleeping completed 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.662: Processing command RETRY 2 203s (process:2402): libfprint-device-DEBUG: 16:48:40.662: Device reported enroll progress, reported 4 of 8 have been completed 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.662: Sleeping completed 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.662: Processing command SCAN print-id 203s (process:2402): libfprint-device-DEBUG: 16:48:40.662: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 203s (process:2402): libfprint-device-DEBUG: 16:48:40.662: Device reported finger status change: FP_FINGER_STATUS_NEEDED 203s (process:2402): libfprint-device-DEBUG: 16:48:40.662: Device reported enroll progress, reported 5 of 8 have been completed 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.662: Processing command SLEEP 10 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.662: Sleeping 10ms 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.672: Sleeping completed 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.672: Processing command SLEEP 20 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.672: Sleeping 20ms 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.693: Sleeping completed 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.693: Processing command RETRY 0 203s (process:2402): libfprint-device-DEBUG: 16:48:40.693: Device reported enroll progress, reported 5 of 8 have been completed 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.693: Sleeping completed 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.693: Processing command RETRY 3 203s (process:2402): libfprint-device-DEBUG: 16:48:40.693: Device reported enroll progress, reported 5 of 8 have been completed 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.693: Sleeping completed 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.693: Processing command SCAN print-id 203s (process:2402): libfprint-device-DEBUG: 16:48:40.693: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 203s (process:2402): libfprint-device-DEBUG: 16:48:40.693: Device reported finger status change: FP_FINGER_STATUS_NEEDED 203s (process:2402): libfprint-device-DEBUG: 16:48:40.693: Device reported enroll progress, reported 6 of 8 have been completed 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.693: Sleeping completed 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.693: Processing command SCAN another-id 203s (process:2402): libfprint-device-DEBUG: 16:48:40.693: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 203s (process:2402): libfprint-device-DEBUG: 16:48:40.693: Device reported enroll progress, reported 6 of 8 have been completed 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.693: Sleeping completed 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.693: Processing command SCAN print-id 203s (process:2402): libfprint-device-DEBUG: 16:48:40.693: Device reported finger status change: FP_FINGER_STATUS_NEEDED 203s (process:2402): libfprint-device-DEBUG: 16:48:40.693: Device reported enroll progress, reported 7 of 8 have been completed 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.693: Sleeping completed 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.693: Processing command SCAN print-id 203s (process:2402): libfprint-device-DEBUG: 16:48:40.693: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 203s (process:2402): libfprint-device-DEBUG: 16:48:40.693: Device reported finger status change: FP_FINGER_STATUS_NEEDED 203s (process:2402): libfprint-device-DEBUG: 16:48:40.693: Device reported enroll progress, reported 8 of 8 have been completed 203s (process:2402): libfprint-device-DEBUG: 16:48:40.693: Device reported enroll completion 203s (process:2402): libfprint-device-DEBUG: 16:48:40.693: Device reported finger status change: FP_FINGER_STATUS_NONE 203s (process:2402): libfprint-device-DEBUG: 16:48:40.693: Print for finger FP_FINGER_UNKNOWN enrolled 203s (process:2402): libfprint-device-DEBUG: 16:48:40.693: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 203s (process:2402): libfprint-device-DEBUG: 16:48:40.693: Updated temperature model after 0.03 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 203s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:40.693: Got a new connection! 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.693: Got instructions of length 16 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.693: Received command SET_KEEP_ALIVE 0 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.693: Keep alive toggled: 0 203s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:40.693: Got a new connection! 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.693: Got instructions of length 19 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.693: Received command SET_ENROLL_STAGES 5 203s (process:2402): libfprint-device-DEBUG: 16:48:40.693: Device reported close completion 203s (process:2402): libfprint-device-DEBUG: 16:48:40.693: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 203s (process:2402): libfprint-device-DEBUG: 16:48:40.693: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 203s ok 203s test_enroll_script_interactive (__main__.VirtualDevice.test_enroll_script_interactive) ... (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.693: 91694619: ../libfprint/drivers/virtual-device.c:387 203s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:40.693: 91694628: ../libfprint/drivers/virtual-device-listener.c:153 203s (process:2402): libfprint-device-DEBUG: 16:48:40.694: Device reported open completion 203s (process:2402): libfprint-device-DEBUG: 16:48:40.694: Completing action FPI_DEVICE_ACTION_OPEN in idle! 203s (process:2402): libfprint-device-DEBUG: 16:48:40.694: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 203s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:40.694: Got a new connection! 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.694: Got instructions of length 8 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.694: Received command SLEEP 50 203s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:40.694: Got a new connection! 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.694: Got instructions of length 13 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.694: Received command SCAN print-id 203s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:40.694: Got a new connection! 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.694: Got instructions of length 13 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.694: Received command SCAN print-id 203s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:40.694: Got a new connection! 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.694: Got instructions of length 7 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.694: Received command RETRY 1 203s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:40.694: Got a new connection! 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.694: Got instructions of length 13 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.694: Received command SCAN print-id 203s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:40.694: Got a new connection! 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.694: Got instructions of length 8 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.694: Received command SLEEP 50 203s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:40.694: Got a new connection! 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.694: Got instructions of length 13 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.694: Received command SCAN print-id 203s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:40.694: Got a new connection! 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.694: Got instructions of length 7 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.694: Received command RETRY 2 203s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:40.694: Got a new connection! 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.694: Got instructions of length 15 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.694: Received command SCAN another-id 203s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:40.694: Got a new connection! 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.694: Got instructions of length 13 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.694: Received command SCAN print-id 203s (process:2402): libfprint-device-DEBUG: 16:48:40.695: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.695: Processing command SLEEP 50 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.695: Sleeping 50ms 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.745: Sleeping completed 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.745: Processing command SCAN print-id 203s (process:2402): libfprint-device-DEBUG: 16:48:40.745: Device reported finger status change: FP_FINGER_STATUS_NEEDED 203s (process:2402): libfprint-device-DEBUG: 16:48:40.745: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 203s (process:2402): libfprint-device-DEBUG: 16:48:40.745: Device reported finger status change: FP_FINGER_STATUS_NEEDED 203s (process:2402): libfprint-device-DEBUG: 16:48:40.745: Device reported enroll progress, reported 1 of 5 have been completed 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.745: Sleeping completed 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.745: Processing command SCAN print-id 203s (process:2402): libfprint-device-DEBUG: 16:48:40.745: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 203s (process:2402): libfprint-device-DEBUG: 16:48:40.745: Device reported finger status change: FP_FINGER_STATUS_NEEDED 203s (process:2402): libfprint-device-DEBUG: 16:48:40.745: Device reported enroll progress, reported 2 of 5 have been completed 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.745: Sleeping completed 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.745: Processing command RETRY 1 203s (process:2402): libfprint-device-DEBUG: 16:48:40.745: Device reported enroll progress, reported 2 of 5 have been completed 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.745: Sleeping completed 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.745: Processing command SCAN print-id 203s (process:2402): libfprint-device-DEBUG: 16:48:40.745: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 203s (process:2402): libfprint-device-DEBUG: 16:48:40.745: Device reported finger status change: FP_FINGER_STATUS_NEEDED 203s (process:2402): libfprint-device-DEBUG: 16:48:40.745: Device reported enroll progress, reported 3 of 5 have been completed 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.745: Processing command SLEEP 50 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.745: Sleeping 50ms 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.795: Sleeping completed 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.795: Processing command SCAN print-id 203s (process:2402): libfprint-device-DEBUG: 16:48:40.795: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 203s (process:2402): libfprint-device-DEBUG: 16:48:40.795: Device reported finger status change: FP_FINGER_STATUS_NEEDED 203s (process:2402): libfprint-device-DEBUG: 16:48:40.795: Device reported enroll progress, reported 4 of 5 have been completed 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.795: Sleeping completed 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.795: Processing command RETRY 2 203s (process:2402): libfprint-device-DEBUG: 16:48:40.795: Device reported enroll progress, reported 4 of 5 have been completed 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.795: Sleeping completed 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.795: Processing command SCAN another-id 203s (process:2402): libfprint-device-DEBUG: 16:48:40.795: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 203s (process:2402): libfprint-device-DEBUG: 16:48:40.795: Device reported enroll progress, reported 4 of 5 have been completed 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.795: Sleeping completed 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.795: Processing command SCAN print-id 203s (process:2402): libfprint-device-DEBUG: 16:48:40.795: Device reported finger status change: FP_FINGER_STATUS_NEEDED 203s (process:2402): libfprint-device-DEBUG: 16:48:40.795: Device reported enroll progress, reported 5 of 5 have been completed 203s (process:2402): libfprint-device-DEBUG: 16:48:40.795: Device reported enroll completion 203s (process:2402): libfprint-device-DEBUG: 16:48:40.795: Device reported finger status change: FP_FINGER_STATUS_NONE 203s (process:2402): libfprint-device-DEBUG: 16:48:40.795: Print for finger FP_FINGER_UNKNOWN enrolled 203s (process:2402): libfprint-device-DEBUG: 16:48:40.795: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 203s (process:2402): libfprint-device-DEBUG: 16:48:40.795: Updated temperature model after 0.10 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 203s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:40.796: Got a new connection! 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.796: Got instructions of length 16 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.796: Received command SET_KEEP_ALIVE 0 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.796: Keep alive toggled: 0 203s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:40.796: Got a new connection! 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.796: Got instructions of length 19 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.796: Received command SET_ENROLL_STAGES 5 203s (process:2402): libfprint-device-DEBUG: 16:48:40.796: Device reported close completion 203s (process:2402): libfprint-device-DEBUG: 16:48:40.796: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 203s (process:2402): libfprint-device-DEBUG: 16:48:40.796: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 203s ok 203s test_enroll_verify_error (__main__.VirtualDevice.test_enroll_verify_error) ... (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.796: 91797121: ../libfprint/drivers/virtual-device.c:387 203s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:40.796: 91797130: ../libfprint/drivers/virtual-device-listener.c:153 203s (process:2402): libfprint-device-DEBUG: 16:48:40.796: Device reported open completion 203s (process:2402): libfprint-device-DEBUG: 16:48:40.796: Completing action FPI_DEVICE_ACTION_OPEN in idle! 203s (process:2402): libfprint-device-DEBUG: 16:48:40.796: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 203s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:40.796: Got a new connection! 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.796: Got instructions of length 14 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.796: Received command SCAN testprint 203s (process:2402): libfprint-device-DEBUG: 16:48:40.796: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.796: Processing command SCAN testprint 203s (process:2402): libfprint-device-DEBUG: 16:48:40.796: Device reported finger status change: FP_FINGER_STATUS_NEEDED 203s (process:2402): libfprint-device-DEBUG: 16:48:40.796: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 203s (process:2402): libfprint-device-DEBUG: 16:48:40.796: Device reported finger status change: FP_FINGER_STATUS_NEEDED 203s (process:2402): libfprint-device-DEBUG: 16:48:40.796: Device reported enroll progress, reported 1 of 5 have been completed 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.796: Sleeping completed 203s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:40.796: Got a new connection! 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.796: Got instructions of length 14 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.796: Received command SCAN testprint 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.796: Processing command SCAN testprint 203s (process:2402): libfprint-device-DEBUG: 16:48:40.796: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 203s (process:2402): libfprint-device-DEBUG: 16:48:40.796: Device reported finger status change: FP_FINGER_STATUS_NEEDED 203s (process:2402): libfprint-device-DEBUG: 16:48:40.796: Device reported enroll progress, reported 2 of 5 have been completed 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.796: Sleeping completed 203s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:40.797: Got a new connection! 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.797: Got instructions of length 14 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.797: Received command SCAN testprint 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.797: Processing command SCAN testprint 203s (process:2402): libfprint-device-DEBUG: 16:48:40.797: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 203s (process:2402): libfprint-device-DEBUG: 16:48:40.797: Device reported finger status change: FP_FINGER_STATUS_NEEDED 203s (process:2402): libfprint-device-DEBUG: 16:48:40.797: Device reported enroll progress, reported 3 of 5 have been completed 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.797: Sleeping completed 203s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:40.797: Got a new connection! 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.797: Got instructions of length 14 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.797: Received command SCAN testprint 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.797: Processing command SCAN testprint 203s (process:2402): libfprint-device-DEBUG: 16:48:40.797: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 203s (process:2402): libfprint-device-DEBUG: 16:48:40.797: Device reported finger status change: FP_FINGER_STATUS_NEEDED 203s (process:2402): libfprint-device-DEBUG: 16:48:40.797: Device reported enroll progress, reported 4 of 5 have been completed 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.797: Sleeping completed 203s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:40.797: Got a new connection! 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.797: Got instructions of length 14 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.797: Received command SCAN testprint 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.797: Processing command SCAN testprint 203s (process:2402): libfprint-device-DEBUG: 16:48:40.797: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 203s (process:2402): libfprint-device-DEBUG: 16:48:40.797: Device reported finger status change: FP_FINGER_STATUS_NEEDED 203s (process:2402): libfprint-device-DEBUG: 16:48:40.797: Device reported enroll progress, reported 5 of 5 have been completed 203s (process:2402): libfprint-device-DEBUG: 16:48:40.797: Device reported enroll completion 203s (process:2402): libfprint-device-DEBUG: 16:48:40.797: Device reported finger status change: FP_FINGER_STATUS_NONE 203s (process:2402): libfprint-device-DEBUG: 16:48:40.797: Print for finger FP_FINGER_LEFT_RING enrolled 203s (process:2402): libfprint-device-DEBUG: 16:48:40.797: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 203s (process:2402): libfprint-device-DEBUG: 16:48:40.797: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 203s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:40.797: Got a new connection! 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.797: Got instructions of length 7 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.797: Received command ERROR 0 203s (process:2402): libfprint-device-DEBUG: 16:48:40.797: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.797: Processing command ERROR 0 203s (process:2402): libfprint-device-DEBUG: 16:48:40.797: Device reported finger status change: FP_FINGER_STATUS_NEEDED 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.797: Virtual device scan failed with error: An unspecified error occurred! 203s (process:2402): libfprint-device-DEBUG: 16:48:40.797: Device reported verify completion 203s (process:2402): libfprint-device-DEBUG: 16:48:40.797: Device reported finger status change: FP_FINGER_STATUS_NONE 203s (process:2402): libfprint-device-DEBUG: 16:48:40.797: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 203s (process:2402): libfprint-device-DEBUG: 16:48:40.797: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 203s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:40.797: Got a new connection! 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.797: Got instructions of length 16 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.797: Received command SET_KEEP_ALIVE 0 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.797: Keep alive toggled: 0 203s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:40.797: Got a new connection! 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.797: Got instructions of length 19 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.797: Received command SET_ENROLL_STAGES 5 203s (process:2402): libfprint-device-DEBUG: 16:48:40.798: Device reported close completion 203s (process:2402): libfprint-device-DEBUG: 16:48:40.798: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 203s (process:2402): libfprint-device-DEBUG: 16:48:40.798: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 203s Enroll done 203s ok 203s test_enroll_verify_match (__main__.VirtualDevice.test_enroll_verify_match) ... (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.798: 91798817: ../libfprint/drivers/virtual-device.c:387 203s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:40.798: 91798826: ../libfprint/drivers/virtual-device-listener.c:153 203s (process:2402): libfprint-device-DEBUG: 16:48:40.798: Device reported open completion 203s (process:2402): libfprint-device-DEBUG: 16:48:40.798: Completing action FPI_DEVICE_ACTION_OPEN in idle! 203s (process:2402): libfprint-device-DEBUG: 16:48:40.798: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 203s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:40.798: Got a new connection! 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.798: Got instructions of length 14 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.798: Received command SCAN testprint 203s (process:2402): libfprint-device-DEBUG: 16:48:40.798: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.798: Processing command SCAN testprint 203s (process:2402): libfprint-device-DEBUG: 16:48:40.798: Device reported finger status change: FP_FINGER_STATUS_NEEDED 203s (process:2402): libfprint-device-DEBUG: 16:48:40.798: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 203s (process:2402): libfprint-device-DEBUG: 16:48:40.798: Device reported finger status change: FP_FINGER_STATUS_NEEDED 203s (process:2402): libfprint-device-DEBUG: 16:48:40.798: Device reported enroll progress, reported 1 of 5 have been completed 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.798: Sleeping completed 203s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:40.798: Got a new connection! 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.798: Got instructions of length 14 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.798: Received command SCAN testprint 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.798: Processing command SCAN testprint 203s (process:2402): libfprint-device-DEBUG: 16:48:40.798: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 203s (process:2402): libfprint-device-DEBUG: 16:48:40.798: Device reported finger status change: FP_FINGER_STATUS_NEEDED 203s (process:2402): libfprint-device-DEBUG: 16:48:40.798: Device reported enroll progress, reported 2 of 5 have been completed 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.798: Sleeping completed 203s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:40.798: Got a new connection! 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.798: Got instructions of length 14 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.798: Received command SCAN testprint 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.798: Processing command SCAN testprint 203s (process:2402): libfprint-device-DEBUG: 16:48:40.798: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 203s (process:2402): libfprint-device-DEBUG: 16:48:40.798: Device reported finger status change: FP_FINGER_STATUS_NEEDED 203s (process:2402): libfprint-device-DEBUG: 16:48:40.798: Device reported enroll progress, reported 3 of 5 have been completed 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.798: Sleeping completed 203s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:40.798: Got a new connection! 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.798: Got instructions of length 14 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.798: Received command SCAN testprint 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.798: Processing command SCAN testprint 203s (process:2402): libfprint-device-DEBUG: 16:48:40.798: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 203s (process:2402): libfprint-device-DEBUG: 16:48:40.798: Device reported finger status change: FP_FINGER_STATUS_NEEDED 203s (process:2402): libfprint-device-DEBUG: 16:48:40.798: Device reported enroll progress, reported 4 of 5 have been completed 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.798: Sleeping completed 203s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:40.798: Got a new connection! 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.799: Got instructions of length 14 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.799: Received command SCAN testprint 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.799: Processing command SCAN testprint 203s (process:2402): libfprint-device-DEBUG: 16:48:40.799: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 203s (process:2402): libfprint-device-DEBUG: 16:48:40.799: Device reported finger status change: FP_FINGER_STATUS_NEEDED 203s (process:2402): libfprint-device-DEBUG: 16:48:40.799: Device reported enroll progress, reported 5 of 5 have been completed 203s (process:2402): libfprint-device-DEBUG: 16:48:40.799: Device reported enroll completion 203s (process:2402): libfprint-device-DEBUG: 16:48:40.799: Device reported finger status change: FP_FINGER_STATUS_NONE 203s (process:2402): libfprint-device-DEBUG: 16:48:40.799: Print for finger FP_FINGER_LEFT_THUMB enrolled 203s (process:2402): libfprint-device-DEBUG: 16:48:40.799: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 203s (process:2402): libfprint-device-DEBUG: 16:48:40.799: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 203s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:40.799: Got a new connection! 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.799: Got instructions of length 14 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.799: Received command SCAN testprint 203s (process:2402): libfprint-device-DEBUG: 16:48:40.799: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.799: Processing command SCAN testprint 203s (process:2402): libfprint-device-DEBUG: 16:48:40.799: Device reported finger status change: FP_FINGER_STATUS_NEEDED 203s (process:2402): libfprint-device-DEBUG: 16:48:40.799: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.799: Virtual device scanned print testprint 203s (process:2402): libfprint-device-DEBUG: 16:48:40.799: Device reported verify result 203s (process:2402): libfprint-device-DEBUG: 16:48:40.799: Device reported finger status change: FP_FINGER_STATUS_NEEDED 203s (process:2402): libfprint-device-DEBUG: 16:48:40.799: Device reported verify completion 203s (process:2402): libfprint-device-DEBUG: 16:48:40.799: Device reported finger status change: FP_FINGER_STATUS_NONE 203s (process:2402): libfprint-device-DEBUG: 16:48:40.799: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 203s (process:2402): libfprint-device-DEBUG: 16:48:40.799: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 203s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:40.799: Got a new connection! 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.799: Got instructions of length 16 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.800: Received command SET_KEEP_ALIVE 0 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.800: Keep alive toggled: 0 203s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:40.800: Got a new connection! 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.800: Got instructions of length 19 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.800: Received command SET_ENROLL_STAGES 5 203s (process:2402): libfprint-device-DEBUG: 16:48:40.800: Device reported close completion 203s (process:2402): libfprint-device-DEBUG: 16:48:40.800: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 203s (process:2402): libfprint-device-DEBUG: 16:48:40.800: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 203s Enroll done 203s ok 203s test_enroll_verify_no_match (__main__.VirtualDevice.test_enroll_verify_no_match) ... (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.800: 91801158: ../libfprint/drivers/virtual-device.c:387 203s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:40.800: 91801186: ../libfprint/drivers/virtual-device-listener.c:153 203s (process:2402): libfprint-device-DEBUG: 16:48:40.800: Device reported open completion 203s (process:2402): libfprint-device-DEBUG: 16:48:40.800: Completing action FPI_DEVICE_ACTION_OPEN in idle! 203s (process:2402): libfprint-device-DEBUG: 16:48:40.800: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 203s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:40.800: Got a new connection! 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.800: Got instructions of length 14 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.800: Received command SCAN testprint 203s (process:2402): libfprint-device-DEBUG: 16:48:40.800: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.800: Processing command SCAN testprint 203s (process:2402): libfprint-device-DEBUG: 16:48:40.800: Device reported finger status change: FP_FINGER_STATUS_NEEDED 203s (process:2402): libfprint-device-DEBUG: 16:48:40.801: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 203s (process:2402): libfprint-device-DEBUG: 16:48:40.801: Device reported finger status change: FP_FINGER_STATUS_NEEDED 203s (process:2402): libfprint-device-DEBUG: 16:48:40.801: Device reported enroll progress, reported 1 of 5 have been completed 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.801: Sleeping completed 203s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:40.801: Got a new connection! 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.801: Got instructions of length 14 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.801: Received command SCAN testprint 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.801: Processing command SCAN testprint 203s (process:2402): libfprint-device-DEBUG: 16:48:40.801: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 203s (process:2402): libfprint-device-DEBUG: 16:48:40.801: Device reported finger status change: FP_FINGER_STATUS_NEEDED 203s (process:2402): libfprint-device-DEBUG: 16:48:40.801: Device reported enroll progress, reported 2 of 5 have been completed 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.801: Sleeping completed 203s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:40.801: Got a new connection! 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.801: Got instructions of length 14 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.801: Received command SCAN testprint 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.801: Processing command SCAN testprint 203s (process:2402): libfprint-device-DEBUG: 16:48:40.801: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 203s (process:2402): libfprint-device-DEBUG: 16:48:40.801: Device reported finger status change: FP_FINGER_STATUS_NEEDED 203s (process:2402): libfprint-device-DEBUG: 16:48:40.801: Device reported enroll progress, reported 3 of 5 have been completed 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.801: Sleeping completed 203s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:40.801: Got a new connection! 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.802: Got instructions of length 14 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.802: Received command SCAN testprint 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.802: Processing command SCAN testprint 203s (process:2402): libfprint-device-DEBUG: 16:48:40.802: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 203s (process:2402): libfprint-device-DEBUG: 16:48:40.802: Device reported finger status change: FP_FINGER_STATUS_NEEDED 203s (process:2402): libfprint-device-DEBUG: 16:48:40.802: Device reported enroll progress, reported 4 of 5 have been completed 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.802: Sleeping completed 203s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:40.802: Got a new connection! 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.802: Got instructions of length 14 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.802: Received command SCAN testprint 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.802: Processing command SCAN testprint 203s (process:2402): libfprint-device-DEBUG: 16:48:40.802: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 203s (process:2402): libfprint-device-DEBUG: 16:48:40.802: Device reported finger status change: FP_FINGER_STATUS_NEEDED 203s (process:2402): libfprint-device-DEBUG: 16:48:40.802: Device reported enroll progress, reported 5 of 5 have been completed 203s (process:2402): libfprint-device-DEBUG: 16:48:40.802: Device reported enroll completion 203s (process:2402): libfprint-device-DEBUG: 16:48:40.802: Device reported finger status change: FP_FINGER_STATUS_NONE 203s (process:2402): libfprint-device-DEBUG: 16:48:40.802: Print for finger FP_FINGER_LEFT_RING enrolled 203s (process:2402): libfprint-device-DEBUG: 16:48:40.802: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 203s (process:2402): libfprint-device-DEBUG: 16:48:40.802: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 203s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:40.802: Got a new connection! 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.802: Got instructions of length 18 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.802: Received command SCAN not-testprint 203s (process:2402): libfprint-device-DEBUG: 16:48:40.803: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.803: Processing command SCAN not-testprint 203s (process:2402): libfprint-device-DEBUG: 16:48:40.803: Device reported finger status change: FP_FINGER_STATUS_NEEDED 203s (process:2402): libfprint-device-DEBUG: 16:48:40.803: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.803: Virtual device scanned print not-testprint 203s (process:2402): libfprint-device-DEBUG: 16:48:40.803: Device reported verify result 203s (process:2402): libfprint-device-DEBUG: 16:48:40.803: Device reported finger status change: FP_FINGER_STATUS_NEEDED 203s (process:2402): libfprint-device-DEBUG: 16:48:40.803: Device reported verify completion 203s (process:2402): libfprint-device-DEBUG: 16:48:40.803: Device reported finger status change: FP_FINGER_STATUS_NONE 203s (process:2402): libfprint-device-DEBUG: 16:48:40.803: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 203s (process:2402): libfprint-device-DEBUG: 16:48:40.803: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 203s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:40.803: Got a new connection! 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.803: Got instructions of length 16 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.803: Received command SET_KEEP_ALIVE 0 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.803: Keep alive toggled: 0 203s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:40.803: Got a new connection! 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.803: Got instructions of length 19 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.803: Received command SET_ENROLL_STAGES 5 203s (process:2402): libfprint-device-DEBUG: 16:48:40.803: Device reported close completion 203s (process:2402): libfprint-device-DEBUG: 16:48:40.803: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 203s (process:2402): libfprint-device-DEBUG: 16:48:40.803: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 203s Enroll done 203s ok 203s test_enroll_verify_retry (__main__.VirtualDevice.test_enroll_verify_retry) ... (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.804: 91804769: ../libfprint/drivers/virtual-device.c:387 203s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:40.804: 91804798: ../libfprint/drivers/virtual-device-listener.c:153 203s (process:2402): libfprint-device-DEBUG: 16:48:40.804: Device reported open completion 203s (process:2402): libfprint-device-DEBUG: 16:48:40.804: Completing action FPI_DEVICE_ACTION_OPEN in idle! 203s (process:2402): libfprint-device-DEBUG: 16:48:40.804: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 203s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:40.804: Got a new connection! 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.804: Got instructions of length 7 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.804: Received command RETRY 1 203s (process:2402): libfprint-device-DEBUG: 16:48:40.804: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.804: Processing command RETRY 1 203s (process:2402): libfprint-device-DEBUG: 16:48:40.804: Device reported finger status change: FP_FINGER_STATUS_NEEDED 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.804: Virtual device scan failed with error: The swipe was too short, please try again. 203s (process:2402): libfprint-device-DEBUG: 16:48:40.804: Device reported verify result 203s (process:2402): libfprint-device-DEBUG: 16:48:40.804: Device reported verify completion 203s (process:2402): libfprint-device-DEBUG: 16:48:40.804: Device reported finger status change: FP_FINGER_STATUS_NONE 203s (process:2402): libfprint-device-DEBUG: 16:48:40.804: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 203s (process:2402): libfprint-device-DEBUG: 16:48:40.804: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 203s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:40.804: Got a new connection! 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.805: Got instructions of length 16 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.805: Received command SET_KEEP_ALIVE 0 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.805: Keep alive toggled: 0 203s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:40.805: Got a new connection! 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.805: Got instructions of length 19 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.805: Received command SET_ENROLL_STAGES 5 203s (process:2402): libfprint-device-DEBUG: 16:48:40.805: Device reported close completion 203s (process:2402): libfprint-device-DEBUG: 16:48:40.805: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 203s (process:2402): libfprint-device-DEBUG: 16:48:40.805: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 203s ok 203s test_enroll_verify_script (__main__.VirtualDevice.test_enroll_verify_script) ... (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.805: 91806201: ../libfprint/drivers/virtual-device.c:387 203s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:40.805: 91806229: ../libfprint/drivers/virtual-device-listener.c:153 203s (process:2402): libfprint-device-DEBUG: 16:48:40.805: Device reported open completion 203s (process:2402): libfprint-device-DEBUG: 16:48:40.805: Completing action FPI_DEVICE_ACTION_OPEN in idle! 203s (process:2402): libfprint-device-DEBUG: 16:48:40.805: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 203s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:40.805: Got a new connection! 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.805: Got instructions of length 19 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.805: Received command SET_ENROLL_STAGES 8 203s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:40.806: Got a new connection! 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.806: Got instructions of length 13 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.806: Received command SCAN print-id 203s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:40.806: Got a new connection! 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.806: Got instructions of length 13 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.806: Received command SCAN print-id 203s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:40.806: Got a new connection! 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.806: Got instructions of length 7 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.806: Received command RETRY 1 203s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:40.806: Got a new connection! 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.806: Got instructions of length 13 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.806: Received command SCAN print-id 203s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:40.806: Got a new connection! 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.806: Got instructions of length 7 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.806: Received command RETRY 3 203s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:40.806: Got a new connection! 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.806: Got instructions of length 13 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.807: Received command SCAN print-id 203s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:40.807: Got a new connection! 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.807: Got instructions of length 7 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.807: Received command RETRY 2 203s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:40.807: Got a new connection! 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.807: Got instructions of length 13 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.807: Received command SCAN print-id 203s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:40.807: Got a new connection! 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.807: Got instructions of length 8 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.807: Received command SLEEP 10 203s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:40.807: Got a new connection! 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.807: Got instructions of length 8 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.807: Received command SLEEP 20 203s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:40.807: Got a new connection! 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.807: Got instructions of length 7 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.807: Received command RETRY 0 203s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:40.808: Got a new connection! 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.808: Got instructions of length 7 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.808: Received command RETRY 3 203s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:40.808: Got a new connection! 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.808: Got instructions of length 13 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.808: Received command SCAN print-id 203s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:40.808: Got a new connection! 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.808: Got instructions of length 15 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.808: Received command SCAN another-id 203s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:40.808: Got a new connection! 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.808: Got instructions of length 13 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.808: Received command SCAN print-id 203s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:40.808: Got a new connection! 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.808: Got instructions of length 13 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.808: Received command SCAN print-id 203s (process:2402): libfprint-device-DEBUG: 16:48:40.808: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.808: Processing command SCAN print-id 203s (process:2402): libfprint-device-DEBUG: 16:48:40.808: Device reported finger status change: FP_FINGER_STATUS_NEEDED 203s (process:2402): libfprint-device-DEBUG: 16:48:40.808: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 203s (process:2402): libfprint-device-DEBUG: 16:48:40.808: Device reported finger status change: FP_FINGER_STATUS_NEEDED 203s (process:2402): libfprint-device-DEBUG: 16:48:40.808: Device reported enroll progress, reported 1 of 8 have been completed 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.809: Sleeping completed 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.809: Processing command SCAN print-id 203s (process:2402): libfprint-device-DEBUG: 16:48:40.809: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 203s (process:2402): libfprint-device-DEBUG: 16:48:40.809: Device reported finger status change: FP_FINGER_STATUS_NEEDED 203s (process:2402): libfprint-device-DEBUG: 16:48:40.809: Device reported enroll progress, reported 2 of 8 have been completed 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.809: Sleeping completed 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.809: Processing command RETRY 1 203s (process:2402): libfprint-device-DEBUG: 16:48:40.809: Device reported enroll progress, reported 2 of 8 have been completed 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.809: Sleeping completed 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.809: Processing command SCAN print-id 203s (process:2402): libfprint-device-DEBUG: 16:48:40.809: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 203s (process:2402): libfprint-device-DEBUG: 16:48:40.809: Device reported finger status change: FP_FINGER_STATUS_NEEDED 203s (process:2402): libfprint-device-DEBUG: 16:48:40.809: Device reported enroll progress, reported 3 of 8 have been completed 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.809: Sleeping completed 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.809: Processing command RETRY 3 203s (process:2402): libfprint-device-DEBUG: 16:48:40.809: Device reported enroll progress, reported 3 of 8 have been completed 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.809: Sleeping completed 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.809: Processing command SCAN print-id 203s (process:2402): libfprint-device-DEBUG: 16:48:40.809: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 203s (process:2402): libfprint-device-DEBUG: 16:48:40.809: Device reported finger status change: FP_FINGER_STATUS_NEEDED 203s (process:2402): libfprint-device-DEBUG: 16:48:40.809: Device reported enroll progress, reported 4 of 8 have been completed 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.809: Sleeping completed 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.809: Processing command RETRY 2 203s (process:2402): libfprint-device-DEBUG: 16:48:40.809: Device reported enroll progress, reported 4 of 8 have been completed 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.809: Sleeping completed 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.809: Processing command SCAN print-id 203s (process:2402): libfprint-device-DEBUG: 16:48:40.809: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 203s (process:2402): libfprint-device-DEBUG: 16:48:40.809: Device reported finger status change: FP_FINGER_STATUS_NEEDED 203s (process:2402): libfprint-device-DEBUG: 16:48:40.809: Device reported enroll progress, reported 5 of 8 have been completed 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.809: Processing command SLEEP 10 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.809: Sleeping 10ms 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.819: Sleeping completed 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.819: Processing command SLEEP 20 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.819: Sleeping 20ms 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.840: Sleeping completed 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.840: Processing command RETRY 0 203s (process:2402): libfprint-device-DEBUG: 16:48:40.840: Device reported enroll progress, reported 5 of 8 have been completed 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.840: Sleeping completed 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.840: Processing command RETRY 3 203s (process:2402): libfprint-device-DEBUG: 16:48:40.840: Device reported enroll progress, reported 5 of 8 have been completed 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.840: Sleeping completed 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.840: Processing command SCAN print-id 203s (process:2402): libfprint-device-DEBUG: 16:48:40.840: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 203s (process:2402): libfprint-device-DEBUG: 16:48:40.840: Device reported finger status change: FP_FINGER_STATUS_NEEDED 203s (process:2402): libfprint-device-DEBUG: 16:48:40.840: Device reported enroll progress, reported 6 of 8 have been completed 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.840: Sleeping completed 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.840: Processing command SCAN another-id 203s (process:2402): libfprint-device-DEBUG: 16:48:40.840: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 203s (process:2402): libfprint-device-DEBUG: 16:48:40.840: Device reported enroll progress, reported 6 of 8 have been completed 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.840: Sleeping completed 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.840: Processing command SCAN print-id 203s (process:2402): libfprint-device-DEBUG: 16:48:40.840: Device reported finger status change: FP_FINGER_STATUS_NEEDED 203s (process:2402): libfprint-device-DEBUG: 16:48:40.840: Device reported enroll progress, reported 7 of 8 have been completed 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.840: Sleeping completed 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.840: Processing command SCAN print-id 203s (process:2402): libfprint-device-DEBUG: 16:48:40.840: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 203s (process:2402): libfprint-device-DEBUG: 16:48:40.840: Device reported finger status change: FP_FINGER_STATUS_NEEDED 203s (process:2402): libfprint-device-DEBUG: 16:48:40.840: Device reported enroll progress, reported 8 of 8 have been completed 203s (process:2402): libfprint-device-DEBUG: 16:48:40.840: Device reported enroll completion 203s (process:2402): libfprint-device-DEBUG: 16:48:40.840: Device reported finger status change: FP_FINGER_STATUS_NONE 203s (process:2402): libfprint-device-DEBUG: 16:48:40.840: Print for finger FP_FINGER_UNKNOWN enrolled 203s (process:2402): libfprint-device-DEBUG: 16:48:40.840: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 203s (process:2402): libfprint-device-DEBUG: 16:48:40.840: Updated temperature model after 0.03 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 203s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:40.841: Got a new connection! 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.841: Got instructions of length 7 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.841: Received command RETRY 2 203s (process:2402): libfprint-device-DEBUG: 16:48:40.841: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.841: Processing command RETRY 2 203s (process:2402): libfprint-device-DEBUG: 16:48:40.841: Device reported finger status change: FP_FINGER_STATUS_NEEDED 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.841: Virtual device scan failed with error: The finger was not centered properly, please try again. 203s (process:2402): libfprint-device-DEBUG: 16:48:40.841: Device reported verify result 203s (process:2402): libfprint-device-DEBUG: 16:48:40.841: Device reported verify completion 203s (process:2402): libfprint-device-DEBUG: 16:48:40.841: Device reported finger status change: FP_FINGER_STATUS_NONE 203s (process:2402): libfprint-device-DEBUG: 16:48:40.841: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 203s (process:2402): libfprint-device-DEBUG: 16:48:40.841: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 203s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:40.841: Got a new connection! 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.841: Got instructions of length 8 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.841: Received command SLEEP 50 203s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:40.841: Got a new connection! 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.841: Got instructions of length 7 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.841: Received command RETRY 1 203s (process:2402): libfprint-device-DEBUG: 16:48:40.841: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.841: Processing command SLEEP 50 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.841: Sleeping 50ms 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.891: Sleeping completed 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.891: Processing command RETRY 1 203s (process:2402): libfprint-device-DEBUG: 16:48:40.891: Device reported finger status change: FP_FINGER_STATUS_NEEDED 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.891: Virtual device scan failed with error: The swipe was too short, please try again. 203s (process:2402): libfprint-device-DEBUG: 16:48:40.891: Device reported verify result 203s (process:2402): libfprint-device-DEBUG: 16:48:40.891: Device reported verify completion 203s (process:2402): libfprint-device-DEBUG: 16:48:40.891: Device reported finger status change: FP_FINGER_STATUS_NONE 203s (process:2402): libfprint-device-DEBUG: 16:48:40.891: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 203s (process:2402): libfprint-device-DEBUG: 16:48:40.891: Updated temperature model after 0.05 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 203s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:40.892: Got a new connection! 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.892: Got instructions of length 15 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.892: Received command SCAN another-id 203s (process:2402): libfprint-device-DEBUG: 16:48:40.892: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.892: Processing command SCAN another-id 203s (process:2402): libfprint-device-DEBUG: 16:48:40.892: Device reported finger status change: FP_FINGER_STATUS_NEEDED 203s (process:2402): libfprint-device-DEBUG: 16:48:40.892: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.892: Virtual device scanned print another-id 203s (process:2402): libfprint-device-DEBUG: 16:48:40.892: Device reported verify result 203s (process:2402): libfprint-device-DEBUG: 16:48:40.892: Device reported finger status change: FP_FINGER_STATUS_NEEDED 203s (process:2402): libfprint-device-DEBUG: 16:48:40.892: Device reported verify completion 203s (process:2402): libfprint-device-DEBUG: 16:48:40.892: Device reported finger status change: FP_FINGER_STATUS_NONE 203s (process:2402): libfprint-device-DEBUG: 16:48:40.892: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 203s (process:2402): libfprint-device-DEBUG: 16:48:40.892: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 203s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:40.892: Got a new connection! 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.892: Got instructions of length 13 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.892: Received command SCAN print-id 203s (process:2402): libfprint-device-DEBUG: 16:48:40.892: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.892: Processing command SCAN print-id 203s (process:2402): libfprint-device-DEBUG: 16:48:40.892: Device reported finger status change: FP_FINGER_STATUS_NEEDED 203s (process:2402): libfprint-device-DEBUG: 16:48:40.892: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.892: Virtual device scanned print print-id 203s (process:2402): libfprint-device-DEBUG: 16:48:40.892: Device reported verify result 203s (process:2402): libfprint-device-DEBUG: 16:48:40.892: Device reported finger status change: FP_FINGER_STATUS_NEEDED 203s (process:2402): libfprint-device-DEBUG: 16:48:40.892: Device reported verify completion 203s (process:2402): libfprint-device-DEBUG: 16:48:40.892: Device reported finger status change: FP_FINGER_STATUS_NONE 203s (process:2402): libfprint-device-DEBUG: 16:48:40.892: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 203s (process:2402): libfprint-device-DEBUG: 16:48:40.892: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 203s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:40.892: Got a new connection! 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.892: Got instructions of length 16 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.892: Received command SET_KEEP_ALIVE 0 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.892: Keep alive toggled: 0 203s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:40.892: Got a new connection! 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.892: Got instructions of length 19 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.892: Received command SET_ENROLL_STAGES 5 203s (process:2402): libfprint-device-DEBUG: 16:48:40.892: Device reported close completion 203s (process:2402): libfprint-device-DEBUG: 16:48:40.892: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 203s (process:2402): libfprint-device-DEBUG: 16:48:40.892: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 203s ok 203s test_enroll_with_retry (__main__.VirtualDevice.test_enroll_with_retry) ... (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.892: 91893529: ../libfprint/drivers/virtual-device.c:387 203s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:40.892: 91893538: ../libfprint/drivers/virtual-device-listener.c:153 203s (process:2402): libfprint-device-DEBUG: 16:48:40.892: Device reported open completion 203s (process:2402): libfprint-device-DEBUG: 16:48:40.892: Completing action FPI_DEVICE_ACTION_OPEN in idle! 203s (process:2402): libfprint-device-DEBUG: 16:48:40.892: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 203s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:40.893: Got a new connection! 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.893: Got instructions of length 14 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.893: Received command SCAN testprint 203s (process:2402): libfprint-device-DEBUG: 16:48:40.893: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.893: Processing command SCAN testprint 203s (process:2402): libfprint-device-DEBUG: 16:48:40.893: Device reported finger status change: FP_FINGER_STATUS_NEEDED 203s (process:2402): libfprint-device-DEBUG: 16:48:40.893: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 203s (process:2402): libfprint-device-DEBUG: 16:48:40.893: Device reported finger status change: FP_FINGER_STATUS_NEEDED 203s (process:2402): libfprint-device-DEBUG: 16:48:40.893: Device reported enroll progress, reported 1 of 5 have been completed 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.893: Sleeping completed 203s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:40.893: Got a new connection! 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.893: Got instructions of length 14 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.893: Received command SCAN testprint 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.893: Processing command SCAN testprint 203s (process:2402): libfprint-device-DEBUG: 16:48:40.893: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 203s (process:2402): libfprint-device-DEBUG: 16:48:40.893: Device reported finger status change: FP_FINGER_STATUS_NEEDED 203s (process:2402): libfprint-device-DEBUG: 16:48:40.893: Device reported enroll progress, reported 2 of 5 have been completed 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.893: Sleeping completed 203s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:40.893: Got a new connection! 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.893: Got instructions of length 7 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.893: Received command RETRY 1 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.893: Processing command RETRY 1 203s (process:2402): libfprint-device-DEBUG: 16:48:40.893: Device reported enroll progress, reported 2 of 5 have been completed 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.893: Sleeping completed 203s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:40.893: Got a new connection! 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.893: Got instructions of length 14 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.893: Received command SCAN testprint 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.893: Processing command SCAN testprint 203s (process:2402): libfprint-device-DEBUG: 16:48:40.893: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 203s (process:2402): libfprint-device-DEBUG: 16:48:40.893: Device reported finger status change: FP_FINGER_STATUS_NEEDED 203s (process:2402): libfprint-device-DEBUG: 16:48:40.893: Device reported enroll progress, reported 3 of 5 have been completed 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.893: Sleeping completed 203s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:40.893: Got a new connection! 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.893: Got instructions of length 14 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.893: Received command SCAN testprint 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.893: Processing command SCAN testprint 203s (process:2402): libfprint-device-DEBUG: 16:48:40.893: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 203s (process:2402): libfprint-device-DEBUG: 16:48:40.893: Device reported finger status change: FP_FINGER_STATUS_NEEDED 203s (process:2402): libfprint-device-DEBUG: 16:48:40.893: Device reported enroll progress, reported 4 of 5 have been completed 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.893: Sleeping completed 203s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:40.893: Got a new connection! 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.893: Got instructions of length 14 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.893: Received command SCAN testprint 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.893: Processing command SCAN testprint 203s (process:2402): libfprint-device-DEBUG: 16:48:40.893: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 203s (process:2402): libfprint-device-DEBUG: 16:48:40.893: Device reported finger status change: FP_FINGER_STATUS_NEEDED 203s (process:2402): libfprint-device-DEBUG: 16:48:40.893: Device reported enroll progress, reported 5 of 5 have been completed 203s (process:2402): libfprint-device-DEBUG: 16:48:40.893: Device reported enroll completion 203s (process:2402): libfprint-device-DEBUG: 16:48:40.893: Device reported finger status change: FP_FINGER_STATUS_NONE 203s (process:2402): libfprint-device-DEBUG: 16:48:40.893: Print for finger FP_FINGER_LEFT_LITTLE enrolled 203s (process:2402): libfprint-device-DEBUG: 16:48:40.894: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 203s (process:2402): libfprint-device-DEBUG: 16:48:40.894: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 203s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:40.894: Got a new connection! 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.894: Got instructions of length 16 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.894: Received command SET_KEEP_ALIVE 0 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.894: Keep alive toggled: 0 203s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:40.894: Got a new connection! 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.894: Got instructions of length 19 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.894: Received command SET_ENROLL_STAGES 5 203s (process:2402): libfprint-device-DEBUG: 16:48:40.894: Device reported close completion 203s (process:2402): libfprint-device-DEBUG: 16:48:40.894: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 203s (process:2402): libfprint-device-DEBUG: 16:48:40.894: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 203s Enroll done 203s ok 203s test_finger_status (__main__.VirtualDevice.test_finger_status) ... (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.894: 91895163: ../libfprint/drivers/virtual-device.c:387 203s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:40.894: 91895171: ../libfprint/drivers/virtual-device-listener.c:153 203s (process:2402): libfprint-device-DEBUG: 16:48:40.894: Device reported open completion 203s (process:2402): libfprint-device-DEBUG: 16:48:40.894: Completing action FPI_DEVICE_ACTION_OPEN in idle! 203s (process:2402): libfprint-device-DEBUG: 16:48:40.894: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 203s (process:2402): libfprint-device-DEBUG: 16:48:40.894: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 203s (process:2402): libfprint-device-DEBUG: 16:48:40.894: Device reported finger status change: FP_FINGER_STATUS_NEEDED 203s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:40.894: Got a new connection! 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.894: Got instructions of length 8 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.894: Received command FINGER 1 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.894: Processing command FINGER 1 203s (process:2402): libfprint-device-DEBUG: 16:48:40.894: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 203s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:40.894: Got a new connection! 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.894: Got instructions of length 8 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.894: Received command FINGER 0 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.894: Processing command FINGER 0 203s (process:2402): libfprint-device-DEBUG: 16:48:40.894: Device reported finger status change: FP_FINGER_STATUS_NEEDED 203s (process:2402): libfprint-device-DEBUG: 16:48:40.894: Idle cancelling on ongoing operation! 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.894: Got cancellation! 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.894: Virtual device scan failed with error: Operation was cancelled 203s (process:2402): libfprint-device-DEBUG: 16:48:40.894: Device reported verify completion 203s (process:2402): libfprint-device-DEBUG: 16:48:40.894: Device reported finger status change: FP_FINGER_STATUS_NONE 203s (process:2402): libfprint-device-DEBUG: 16:48:40.894: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 203s (process:2402): libfprint-device-DEBUG: 16:48:40.894: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 203s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:40.895: Got a new connection! 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.895: Got instructions of length 16 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.895: Received command SET_KEEP_ALIVE 0 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.895: Keep alive toggled: 0 203s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:40.895: Got a new connection! 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.895: Got instructions of length 19 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.895: Received command SET_ENROLL_STAGES 5 203s (process:2402): libfprint-device-DEBUG: 16:48:40.895: Device reported close completion 203s (process:2402): libfprint-device-DEBUG: 16:48:40.895: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 203s (process:2402): libfprint-device-DEBUG: 16:48:40.895: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 203s ok 203s test_finger_status_after_sleep (__main__.VirtualDevice.test_finger_status_after_sleep) ... (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.895: 91895992: ../libfprint/drivers/virtual-device.c:387 203s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:40.895: 91896240: ../libfprint/drivers/virtual-device-listener.c:153 203s (process:2402): libfprint-device-DEBUG: 16:48:40.895: Device reported open completion 203s (process:2402): libfprint-device-DEBUG: 16:48:40.895: Completing action FPI_DEVICE_ACTION_OPEN in idle! 203s (process:2402): libfprint-device-DEBUG: 16:48:40.895: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 203s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:40.896: Got a new connection! 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.896: Got instructions of length 8 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.896: Received command SLEEP 10 203s (process:2402): libfprint-device-DEBUG: 16:48:40.896: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.896: Processing command SLEEP 10 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.896: Sleeping 10ms 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.906: Sleeping completed 203s (process:2402): libfprint-device-DEBUG: 16:48:40.906: Device reported finger status change: FP_FINGER_STATUS_NEEDED 203s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:40.906: Got a new connection! 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.907: Got instructions of length 8 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.907: Received command FINGER 1 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.907: Processing command FINGER 1 203s (process:2402): libfprint-device-DEBUG: 16:48:40.907: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 203s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:40.907: Got a new connection! 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.907: Got instructions of length 8 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.907: Received command FINGER 0 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.907: Processing command FINGER 0 203s (process:2402): libfprint-device-DEBUG: 16:48:40.907: Device reported finger status change: FP_FINGER_STATUS_NEEDED 203s (process:2402): libfprint-device-DEBUG: 16:48:40.907: Idle cancelling on ongoing operation! 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.907: Got cancellation! 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.908: Virtual device scan failed with error: Operation was cancelled 203s (process:2402): libfprint-device-DEBUG: 16:48:40.908: Device reported verify completion 203s (process:2402): libfprint-device-DEBUG: 16:48:40.908: Device reported finger status change: FP_FINGER_STATUS_NONE 203s (process:2402): libfprint-device-DEBUG: 16:48:40.908: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 203s (process:2402): libfprint-device-DEBUG: 16:48:40.908: Updated temperature model after 0.01 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 203s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:40.908: Got a new connection! 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.908: Got instructions of length 16 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.908: Received command SET_KEEP_ALIVE 0 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.908: Keep alive toggled: 0 203s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:40.908: Got a new connection! 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.908: Got instructions of length 19 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.908: Received command SET_ENROLL_STAGES 5 203s (process:2402): libfprint-device-DEBUG: 16:48:40.909: Device reported close completion 203s (process:2402): libfprint-device-DEBUG: 16:48:40.909: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 203s (process:2402): libfprint-device-DEBUG: 16:48:40.909: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 203s ok 203s test_identify_unsupported (__main__.VirtualDevice.test_identify_unsupported) ... (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.909: 91910168: ../libfprint/drivers/virtual-device.c:387 203s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:40.909: 91910234: ../libfprint/drivers/virtual-device-listener.c:153 203s (process:2402): libfprint-device-DEBUG: 16:48:40.909: Device reported open completion 203s (process:2402): libfprint-device-DEBUG: 16:48:40.909: Completing action FPI_DEVICE_ACTION_OPEN in idle! 203s (process:2402): libfprint-device-DEBUG: 16:48:40.909: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 203s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:40.910: Got a new connection! 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.910: Got instructions of length 16 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.910: Received command SET_KEEP_ALIVE 0 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.910: Keep alive toggled: 0 203s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:40.910: Got a new connection! 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.910: Got instructions of length 19 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.910: Received command SET_ENROLL_STAGES 5 203s (process:2402): libfprint-device-DEBUG: 16:48:40.910: Device reported close completion 203s (process:2402): libfprint-device-DEBUG: 16:48:40.910: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 203s (process:2402): libfprint-device-DEBUG: 16:48:40.910: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 203s ok 203s test_open_error (__main__.VirtualDevice.test_open_error) ... (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.910: 91911684: ../libfprint/drivers/virtual-device.c:387 203s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:40.911: 91911729: ../libfprint/drivers/virtual-device-listener.c:153 203s (process:2402): libfprint-device-DEBUG: 16:48:40.911: Device reported open completion 203s (process:2402): libfprint-device-DEBUG: 16:48:40.911: Completing action FPI_DEVICE_ACTION_OPEN in idle! 203s (process:2402): libfprint-device-DEBUG: 16:48:40.911: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 203s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:40.911: Got a new connection! 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.911: Got instructions of length 16 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.911: Received command IGNORED_COMMAND 203s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:40.911: Got a new connection! 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.911: Got instructions of length 7 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.911: Received command ERROR 5 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.911: Processing command IGNORED_COMMAND 203s (process:2402): libfprint-device-DEBUG: 16:48:40.911: Device reported close completion 203s (process:2402): libfprint-device-DEBUG: 16:48:40.912: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 203s (process:2402): libfprint-device-DEBUG: 16:48:40.912: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.912: 91912941: ../libfprint/drivers/virtual-device.c:387 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.912: Processing command ERROR 5 203s (process:2402): libfprint-device-DEBUG: 16:48:40.912: Device reported open completion 203s (process:2402): libfprint-device-DEBUG: 16:48:40.912: Completing action FPI_DEVICE_ACTION_OPEN in idle! 203s (process:2402): libfprint-device-DEBUG: 16:48:40.912: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 203s ok 203s test_open_error_with_keep_alive (__main__.VirtualDevice.test_open_error_with_keep_alive) ... (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.912: 91913336: ../libfprint/drivers/virtual-device.c:387 203s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:40.912: 91913382: ../libfprint/drivers/virtual-device-listener.c:153 203s (process:2402): libfprint-device-DEBUG: 16:48:40.912: Device reported open completion 203s (process:2402): libfprint-device-DEBUG: 16:48:40.912: Completing action FPI_DEVICE_ACTION_OPEN in idle! 203s (process:2402): libfprint-device-DEBUG: 16:48:40.912: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 203s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:40.913: Got a new connection! 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.913: Got instructions of length 16 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.913: Received command SET_KEEP_ALIVE 1 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.913: Keep alive toggled: 1 203s (process:2402): libfprint-device-DEBUG: 16:48:40.913: Device reported close completion 203s (process:2402): libfprint-device-DEBUG: 16:48:40.913: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 203s (process:2402): libfprint-device-DEBUG: 16:48:40.913: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 203s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:40.913: Got a new connection! 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.913: Got instructions of length 7 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.913: Received command ERROR 5 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.913: 91914069: ../libfprint/drivers/virtual-device.c:387 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.913: Processing command ERROR 5 203s (process:2402): libfprint-device-DEBUG: 16:48:40.913: Device reported open completion 203s (process:2402): libfprint-device-DEBUG: 16:48:40.913: Completing action FPI_DEVICE_ACTION_OPEN in idle! 203s (process:2402): libfprint-device-DEBUG: 16:48:40.913: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 203s ok 203s test_quick_enroll (__main__.VirtualDevice.test_quick_enroll) ... (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.913: 91914173: ../libfprint/drivers/virtual-device.c:387 203s (process:2402): libfprint-device-DEBUG: 16:48:40.913: Device reported open completion 203s (process:2402): libfprint-device-DEBUG: 16:48:40.913: Completing action FPI_DEVICE_ACTION_OPEN in idle! 203s (process:2402): libfprint-device-DEBUG: 16:48:40.913: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 203s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:40.913: Got a new connection! 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.913: Got instructions of length 19 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.913: Received command SET_ENROLL_STAGES 1 203s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:40.913: Got a new connection! 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.913: Got instructions of length 14 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.913: Received command SCAN testprint 203s (process:2402): libfprint-device-DEBUG: 16:48:40.913: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.913: Processing command SCAN testprint 203s (process:2402): libfprint-device-DEBUG: 16:48:40.913: Device reported finger status change: FP_FINGER_STATUS_NEEDED 203s (process:2402): libfprint-device-DEBUG: 16:48:40.913: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 203s (process:2402): libfprint-device-DEBUG: 16:48:40.913: Device reported finger status change: FP_FINGER_STATUS_NEEDED 203s (process:2402): libfprint-device-DEBUG: 16:48:40.913: Device reported enroll progress, reported 1 of 1 have been completed 203s (process:2402): libfprint-device-DEBUG: 16:48:40.913: Device reported enroll completion 203s (process:2402): libfprint-device-DEBUG: 16:48:40.913: Device reported finger status change: FP_FINGER_STATUS_NONE 203s (process:2402): libfprint-device-DEBUG: 16:48:40.913: Print for finger FP_FINGER_LEFT_LITTLE enrolled 203s (process:2402): libfprint-device-DEBUG: 16:48:40.913: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 203s (process:2402): libfprint-device-DEBUG: 16:48:40.913: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 203s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:40.914: Got a new connection! 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.914: Got instructions of length 16 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.914: Received command SET_KEEP_ALIVE 0 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.914: Keep alive toggled: 0 203s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:40.914: Got a new connection! 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.914: Got instructions of length 19 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.914: Received command SET_ENROLL_STAGES 5 203s (process:2402): libfprint-device-DEBUG: 16:48:40.914: Device reported close completion 203s (process:2402): libfprint-device-DEBUG: 16:48:40.914: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 203s (process:2402): libfprint-device-DEBUG: 16:48:40.914: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 203s Enroll done 203s ok 203s (process:2402): libfprint-context-DEBUG: 16:48:40.930: Initializing FpContext (libfprint version 1.94.7+tod1) 203s (process:2402): libfprint-tod-DEBUG: 16:48:40.930: Impossible to load the shared drivers dir Error opening directory “/usr/lib/aarch64-linux-gnu/libfprint-2/tod-1”: No such file or directory 203s (process:2402): libfprint-context-DEBUG: 16:48:40.932: No driver found for USB device 1D6B:0003 203s (process:2402): libfprint-context-DEBUG: 16:48:40.932: No driver found for USB device 0627:0001 203s (process:2402): libfprint-context-DEBUG: 16:48:40.932: No driver found for USB device 1D6B:0002 203s (process:2402): libfprint-context-DEBUG: 16:48:40.932: Found virtual environment device: FP_VIRTUAL_DEVICE, /tmp/libfprint-3bji9p41/virtual-device.socket 203s (process:2402): libfprint-context-DEBUG: 16:48:40.932: created 203s (process:2402): libfprint-device-DEBUG: 16:48:40.932: Device reported probe completion 203s (process:2402): libfprint-device-DEBUG: 16:48:40.932: Completing action FPI_DEVICE_ACTION_PROBE in idle! 203s (process:2402): libfprint-device-DEBUG: 16:48:40.932: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 203s test_capture (__main__.VirtualDeviceBusyDeviceOperations.test_capture) ... (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.933: 91933773: ../libfprint/drivers/virtual-device.c:387 203s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:40.933: 91933782: ../libfprint/drivers/virtual-device-listener.c:153 203s (process:2402): libfprint-device-DEBUG: 16:48:40.933: Device reported open completion 203s (process:2402): libfprint-device-DEBUG: 16:48:40.933: Completing action FPI_DEVICE_ACTION_OPEN in idle! 203s (process:2402): libfprint-device-DEBUG: 16:48:40.933: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 203s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:40.933: Got a new connection! 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.933: Got instructions of length 9 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.933: Received command SLEEP 200 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.933: Processing command SLEEP 200 203s (process:2402): libfprint-virtual_device-DEBUG: 16:48:40.933: Sleeping 200ms 204s (process:2402): libfprint-virtual_device-DEBUG: 16:48:41.133: Sleeping completed 204s (process:2402): libfprint-device-DEBUG: 16:48:41.133: Device reported close completion 204s (process:2402): libfprint-device-DEBUG: 16:48:41.133: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 204s (process:2402): libfprint-device-DEBUG: 16:48:41.133: Updated temperature model after 0.20 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 204s ok 204s test_close (__main__.VirtualDeviceBusyDeviceOperations.test_close) ... (process:2402): libfprint-virtual_device-DEBUG: 16:48:41.133: 92134643: ../libfprint/drivers/virtual-device.c:387 204s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:41.133: 92134654: ../libfprint/drivers/virtual-device-listener.c:153 204s (process:2402): libfprint-device-DEBUG: 16:48:41.134: Device reported open completion 204s (process:2402): libfprint-device-DEBUG: 16:48:41.134: Completing action FPI_DEVICE_ACTION_OPEN in idle! 204s (process:2402): libfprint-device-DEBUG: 16:48:41.134: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 204s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:41.134: Got a new connection! 204s (process:2402): libfprint-virtual_device-DEBUG: 16:48:41.134: Got instructions of length 9 204s (process:2402): libfprint-virtual_device-DEBUG: 16:48:41.134: Received command SLEEP 200 204s (process:2402): libfprint-virtual_device-DEBUG: 16:48:41.134: Processing command SLEEP 200 204s (process:2402): libfprint-virtual_device-DEBUG: 16:48:41.134: Sleeping 200ms 204s (process:2402): libfprint-virtual_device-DEBUG: 16:48:41.334: Sleeping completed 204s (process:2402): libfprint-device-DEBUG: 16:48:41.334: Device reported close completion 204s (process:2402): libfprint-device-DEBUG: 16:48:41.334: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 204s (process:2402): libfprint-device-DEBUG: 16:48:41.334: Updated temperature model after 0.20 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 204s ok 204s test_delete_print (__main__.VirtualDeviceBusyDeviceOperations.test_delete_print) ... (process:2402): libfprint-virtual_device-DEBUG: 16:48:41.334: 92335611: ../libfprint/drivers/virtual-device.c:387 204s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:41.334: 92335621: ../libfprint/drivers/virtual-device-listener.c:153 204s (process:2402): libfprint-device-DEBUG: 16:48:41.335: Device reported open completion 204s (process:2402): libfprint-device-DEBUG: 16:48:41.335: Completing action FPI_DEVICE_ACTION_OPEN in idle! 204s (process:2402): libfprint-device-DEBUG: 16:48:41.335: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 204s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:41.335: Got a new connection! 204s (process:2402): libfprint-virtual_device-DEBUG: 16:48:41.335: Got instructions of length 9 204s (process:2402): libfprint-virtual_device-DEBUG: 16:48:41.335: Received command SLEEP 200 204s (process:2402): libfprint-virtual_device-DEBUG: 16:48:41.335: Processing command SLEEP 200 204s (process:2402): libfprint-virtual_device-DEBUG: 16:48:41.335: Sleeping 200ms 204s (process:2402): libfprint-virtual_device-DEBUG: 16:48:41.535: Sleeping completed 204s (process:2402): libfprint-device-DEBUG: 16:48:41.535: Device reported close completion 204s (process:2402): libfprint-device-DEBUG: 16:48:41.535: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 204s (process:2402): libfprint-device-DEBUG: 16:48:41.535: Updated temperature model after 0.20 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 204s ok 204s test_enroll (__main__.VirtualDeviceBusyDeviceOperations.test_enroll) ... (process:2402): libfprint-virtual_device-DEBUG: 16:48:41.536: 92536714: ../libfprint/drivers/virtual-device.c:387 204s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:41.536: 92536725: ../libfprint/drivers/virtual-device-listener.c:153 204s (process:2402): libfprint-device-DEBUG: 16:48:41.536: Device reported open completion 204s (process:2402): libfprint-device-DEBUG: 16:48:41.536: Completing action FPI_DEVICE_ACTION_OPEN in idle! 204s (process:2402): libfprint-device-DEBUG: 16:48:41.536: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 204s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:41.536: Got a new connection! 204s (process:2402): libfprint-virtual_device-DEBUG: 16:48:41.536: Got instructions of length 9 204s (process:2402): libfprint-virtual_device-DEBUG: 16:48:41.536: Received command SLEEP 200 204s (process:2402): libfprint-virtual_device-DEBUG: 16:48:41.536: Processing command SLEEP 200 204s (process:2402): libfprint-virtual_device-DEBUG: 16:48:41.536: Sleeping 200ms 204s (process:2402): libfprint-virtual_device-DEBUG: 16:48:41.736: Sleeping completed 204s (process:2402): libfprint-device-DEBUG: 16:48:41.736: Device reported close completion 204s (process:2402): libfprint-device-DEBUG: 16:48:41.736: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 204s (process:2402): libfprint-device-DEBUG: 16:48:41.736: Updated temperature model after 0.20 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 204s ok 204s test_identify (__main__.VirtualDeviceBusyDeviceOperations.test_identify) ... (process:2402): libfprint-virtual_device-DEBUG: 16:48:41.737: 92737694: ../libfprint/drivers/virtual-device.c:387 204s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:41.737: 92737705: ../libfprint/drivers/virtual-device-listener.c:153 204s (process:2402): libfprint-device-DEBUG: 16:48:41.737: Device reported open completion 204s (process:2402): libfprint-device-DEBUG: 16:48:41.737: Completing action FPI_DEVICE_ACTION_OPEN in idle! 204s (process:2402): libfprint-device-DEBUG: 16:48:41.737: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 204s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:41.737: Got a new connection! 204s (process:2402): libfprint-virtual_device-DEBUG: 16:48:41.737: Got instructions of length 9 204s (process:2402): libfprint-virtual_device-DEBUG: 16:48:41.737: Received command SLEEP 200 204s (process:2402): libfprint-virtual_device-DEBUG: 16:48:41.737: Processing command SLEEP 200 204s (process:2402): libfprint-virtual_device-DEBUG: 16:48:41.737: Sleeping 200ms 204s (process:2402): libfprint-virtual_device-DEBUG: 16:48:41.937: Sleeping completed 204s (process:2402): libfprint-device-DEBUG: 16:48:41.937: Device reported close completion 204s (process:2402): libfprint-device-DEBUG: 16:48:41.937: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 204s (process:2402): libfprint-device-DEBUG: 16:48:41.937: Updated temperature model after 0.20 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 204s ok 204s test_list_prints (__main__.VirtualDeviceBusyDeviceOperations.test_list_prints) ... (process:2402): libfprint-virtual_device-DEBUG: 16:48:41.938: 92938714: ../libfprint/drivers/virtual-device.c:387 204s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:41.938: 92938724: ../libfprint/drivers/virtual-device-listener.c:153 204s (process:2402): libfprint-device-DEBUG: 16:48:41.938: Device reported open completion 204s (process:2402): libfprint-device-DEBUG: 16:48:41.938: Completing action FPI_DEVICE_ACTION_OPEN in idle! 204s (process:2402): libfprint-device-DEBUG: 16:48:41.938: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 204s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:41.938: Got a new connection! 204s (process:2402): libfprint-virtual_device-DEBUG: 16:48:41.938: Got instructions of length 9 204s (process:2402): libfprint-virtual_device-DEBUG: 16:48:41.938: Received command SLEEP 200 204s (process:2402): libfprint-virtual_device-DEBUG: 16:48:41.938: Processing command SLEEP 200 204s (process:2402): libfprint-virtual_device-DEBUG: 16:48:41.938: Sleeping 200ms 205s (process:2402): libfprint-virtual_device-DEBUG: 16:48:42.138: Sleeping completed 205s (process:2402): libfprint-device-DEBUG: 16:48:42.138: Device reported close completion 205s (process:2402): libfprint-device-DEBUG: 16:48:42.138: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 205s (process:2402): libfprint-device-DEBUG: 16:48:42.138: Updated temperature model after 0.20 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 205s ok 205s test_open (__main__.VirtualDeviceBusyDeviceOperations.test_open) ... (process:2402): libfprint-virtual_device-DEBUG: 16:48:42.139: 93139758: ../libfprint/drivers/virtual-device.c:387 205s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:42.139: 93139768: ../libfprint/drivers/virtual-device-listener.c:153 205s (process:2402): libfprint-device-DEBUG: 16:48:42.139: Device reported open completion 205s (process:2402): libfprint-device-DEBUG: 16:48:42.139: Completing action FPI_DEVICE_ACTION_OPEN in idle! 205s (process:2402): libfprint-device-DEBUG: 16:48:42.139: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 205s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:42.139: Got a new connection! 205s (process:2402): libfprint-virtual_device-DEBUG: 16:48:42.139: Got instructions of length 9 205s (process:2402): libfprint-virtual_device-DEBUG: 16:48:42.139: Received command SLEEP 200 205s (process:2402): libfprint-virtual_device-DEBUG: 16:48:42.139: Processing command SLEEP 200 205s (process:2402): libfprint-virtual_device-DEBUG: 16:48:42.139: Sleeping 200ms 205s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:42.139: Got a new connection! 205s (process:2402): libfprint-virtual_device-DEBUG: 16:48:42.240: Got instructions of length 16 205s (process:2402): libfprint-virtual_device-DEBUG: 16:48:42.240: Received command SET_KEEP_ALIVE 1 205s (process:2402): libfprint-virtual_device-DEBUG: 16:48:42.240: Keep alive toggled: 1 205s (process:2402): libfprint-virtual_device-DEBUG: 16:48:42.340: Sleeping completed 205s (process:2402): libfprint-device-DEBUG: 16:48:42.340: Device reported close completion 205s (process:2402): libfprint-device-DEBUG: 16:48:42.340: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 205s (process:2402): libfprint-device-DEBUG: 16:48:42.340: Updated temperature model after 0.20 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 205s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:42.340: Got a new connection! 205s (process:2402): libfprint-virtual_device-DEBUG: 16:48:42.341: Got instructions of length 9 205s (process:2402): libfprint-virtual_device-DEBUG: 16:48:42.341: Received command SLEEP 100 205s (process:2402): libfprint-virtual_device-DEBUG: 16:48:42.341: 93341762: ../libfprint/drivers/virtual-device.c:387 205s (process:2402): libfprint-virtual_device-DEBUG: 16:48:42.341: Processing command SLEEP 100 205s (process:2402): libfprint-virtual_device-DEBUG: 16:48:42.341: Sleeping 100ms 205s (process:2402): libfprint-virtual_device-DEBUG: 16:48:42.441: Sleeping completed 205s (process:2402): libfprint-virtual_device-DEBUG: 16:48:42.441: 93442138: ../libfprint/drivers/virtual-device.c:387 205s (process:2402): libfprint-device-DEBUG: 16:48:42.441: Device reported open completion 205s (process:2402): libfprint-device-DEBUG: 16:48:42.441: Completing action FPI_DEVICE_ACTION_OPEN in idle! 205s (process:2402): libfprint-device-DEBUG: 16:48:42.441: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 205s (process:2402): libfprint-device-DEBUG: 16:48:42.441: Device reported close completion 205s (process:2402): libfprint-device-DEBUG: 16:48:42.441: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 205s (process:2402): libfprint-device-DEBUG: 16:48:42.441: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 205s ok 205s test_verify (__main__.VirtualDeviceBusyDeviceOperations.test_verify) ... (process:2402): libfprint-virtual_device-DEBUG: 16:48:42.441: 93442519: ../libfprint/drivers/virtual-device.c:387 205s (process:2402): libfprint-device-DEBUG: 16:48:42.441: Device reported open completion 205s (process:2402): libfprint-device-DEBUG: 16:48:42.441: Completing action FPI_DEVICE_ACTION_OPEN in idle! 205s (process:2402): libfprint-device-DEBUG: 16:48:42.441: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 205s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:42.442: Got a new connection! 205s (process:2402): libfprint-virtual_device-DEBUG: 16:48:42.442: Got instructions of length 9 205s (process:2402): libfprint-virtual_device-DEBUG: 16:48:42.442: Received command SLEEP 200 205s (process:2402): libfprint-virtual_device-DEBUG: 16:48:42.442: Processing command SLEEP 200 205s (process:2402): libfprint-virtual_device-DEBUG: 16:48:42.442: Sleeping 200ms 205s (process:2402): libfprint-virtual_device-DEBUG: 16:48:42.642: Sleeping completed 205s (process:2402): libfprint-device-DEBUG: 16:48:42.642: Device reported close completion 205s (process:2402): libfprint-device-DEBUG: 16:48:42.642: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 205s (process:2402): libfprint-device-DEBUG: 16:48:42.642: Updated temperature model after 0.20 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 205s ok 205s (process:2402): libfprint-virtual_device-DEBUG: 16:48:42.643: 93643964: ../libfprint/drivers/virtual-device.c:752 205s (process:2402): libfprint-context-DEBUG: 16:48:42.643: Initializing FpContext (libfprint version 1.94.7+tod1) 205s (process:2402): libfprint-tod-DEBUG: 16:48:42.643: Impossible to load the shared drivers dir Error opening directory “/usr/lib/aarch64-linux-gnu/libfprint-2/tod-1”: No such file or directory 205s (process:2402): libfprint-context-DEBUG: 16:48:42.645: No driver found for USB device 1D6B:0003 205s (process:2402): libfprint-context-DEBUG: 16:48:42.645: No driver found for USB device 0627:0001 205s (process:2402): libfprint-context-DEBUG: 16:48:42.645: No driver found for USB device 1D6B:0002 205s (process:2402): libfprint-context-DEBUG: 16:48:42.645: Found virtual environment device: FP_VIRTUAL_DEVICE, /tmp/libfprint-jsf89zdj/virtual-device.socket 205s (process:2402): libfprint-context-DEBUG: 16:48:42.645: created 205s (process:2402): libfprint-device-DEBUG: 16:48:42.646: Device reported probe completion 205s (process:2402): libfprint-device-DEBUG: 16:48:42.646: Completing action FPI_DEVICE_ACTION_PROBE in idle! 205s (process:2402): libfprint-device-DEBUG: 16:48:42.646: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 205s test_capture (__main__.VirtualDeviceClosed.test_capture) ... (process:2402): libfprint-virtual_device-DEBUG: 16:48:42.646: 93647528: ../libfprint/drivers/virtual-device.c:387 205s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:42.646: 93647595: ../libfprint/drivers/virtual-device-listener.c:153 205s (process:2402): libfprint-device-DEBUG: 16:48:42.647: Device reported open completion 205s (process:2402): libfprint-device-DEBUG: 16:48:42.647: Completing action FPI_DEVICE_ACTION_OPEN in idle! 205s (process:2402): libfprint-device-DEBUG: 16:48:42.647: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 205s (process:2402): libfprint-device-DEBUG: 16:48:42.647: Device reported close completion 205s (process:2402): libfprint-device-DEBUG: 16:48:42.647: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 205s (process:2402): libfprint-device-DEBUG: 16:48:42.647: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 205s ok 205s test_close (__main__.VirtualDeviceClosed.test_close) ... (process:2402): libfprint-virtual_device-DEBUG: 16:48:42.647: 93648452: ../libfprint/drivers/virtual-device.c:387 205s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:42.647: 93648517: ../libfprint/drivers/virtual-device-listener.c:153 205s (process:2402): libfprint-device-DEBUG: 16:48:42.647: Device reported open completion 205s (process:2402): libfprint-device-DEBUG: 16:48:42.648: Completing action FPI_DEVICE_ACTION_OPEN in idle! 205s (process:2402): libfprint-device-DEBUG: 16:48:42.648: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 205s (process:2402): libfprint-device-DEBUG: 16:48:42.648: Device reported close completion 205s (process:2402): libfprint-device-DEBUG: 16:48:42.648: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 205s (process:2402): libfprint-device-DEBUG: 16:48:42.648: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 205s ok 205s test_delete_print (__main__.VirtualDeviceClosed.test_delete_print) ... (process:2402): libfprint-virtual_device-DEBUG: 16:48:42.648: 93649292: ../libfprint/drivers/virtual-device.c:387 205s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:42.648: 93649355: ../libfprint/drivers/virtual-device-listener.c:153 205s (process:2402): libfprint-device-DEBUG: 16:48:42.648: Device reported open completion 205s (process:2402): libfprint-device-DEBUG: 16:48:42.648: Completing action FPI_DEVICE_ACTION_OPEN in idle! 205s (process:2402): libfprint-device-DEBUG: 16:48:42.648: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 205s (process:2402): libfprint-device-DEBUG: 16:48:42.648: Device reported close completion 205s (process:2402): libfprint-device-DEBUG: 16:48:42.649: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 205s (process:2402): libfprint-device-DEBUG: 16:48:42.649: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 205s ok 205s test_enroll (__main__.VirtualDeviceClosed.test_enroll) ... (process:2402): libfprint-virtual_device-DEBUG: 16:48:42.649: 93650130: ../libfprint/drivers/virtual-device.c:387 205s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:42.649: 93650195: ../libfprint/drivers/virtual-device-listener.c:153 205s (process:2402): libfprint-device-DEBUG: 16:48:42.649: Device reported open completion 205s (process:2402): libfprint-device-DEBUG: 16:48:42.649: Completing action FPI_DEVICE_ACTION_OPEN in idle! 205s (process:2402): libfprint-device-DEBUG: 16:48:42.649: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 205s (process:2402): libfprint-device-DEBUG: 16:48:42.649: Device reported close completion 205s (process:2402): libfprint-device-DEBUG: 16:48:42.649: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 205s (process:2402): libfprint-device-DEBUG: 16:48:42.649: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 205s ok 205s test_identify (__main__.VirtualDeviceClosed.test_identify) ... (process:2402): libfprint-virtual_device-DEBUG: 16:48:42.650: 93650976: ../libfprint/drivers/virtual-device.c:387 205s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:42.650: 93651041: ../libfprint/drivers/virtual-device-listener.c:153 205s (process:2402): libfprint-device-DEBUG: 16:48:42.650: Device reported open completion 205s (process:2402): libfprint-device-DEBUG: 16:48:42.650: Completing action FPI_DEVICE_ACTION_OPEN in idle! 205s (process:2402): libfprint-device-DEBUG: 16:48:42.650: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 205s (process:2402): libfprint-device-DEBUG: 16:48:42.650: Device reported close completion 205s (process:2402): libfprint-device-DEBUG: 16:48:42.650: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 205s (process:2402): libfprint-device-DEBUG: 16:48:42.650: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 205s ok 205s test_list_prints (__main__.VirtualDeviceClosed.test_list_prints) ... (process:2402): libfprint-virtual_device-DEBUG: 16:48:42.651: 93651815: ../libfprint/drivers/virtual-device.c:387 205s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:42.651: 93651880: ../libfprint/drivers/virtual-device-listener.c:153 205s (process:2402): libfprint-device-DEBUG: 16:48:42.651: Device reported open completion 205s (process:2402): libfprint-device-DEBUG: 16:48:42.651: Completing action FPI_DEVICE_ACTION_OPEN in idle! 205s (process:2402): libfprint-device-DEBUG: 16:48:42.651: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 205s (process:2402): libfprint-device-DEBUG: 16:48:42.651: Device reported close completion 205s (process:2402): libfprint-device-DEBUG: 16:48:42.651: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 205s (process:2402): libfprint-device-DEBUG: 16:48:42.651: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 205s ok 205s test_verify (__main__.VirtualDeviceClosed.test_verify) ... (process:2402): libfprint-virtual_device-DEBUG: 16:48:42.652: 93652729: ../libfprint/drivers/virtual-device.c:387 205s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:42.652: 93652793: ../libfprint/drivers/virtual-device-listener.c:153 205s (process:2402): libfprint-device-DEBUG: 16:48:42.652: Device reported open completion 205s (process:2402): libfprint-device-DEBUG: 16:48:42.652: Completing action FPI_DEVICE_ACTION_OPEN in idle! 205s (process:2402): libfprint-device-DEBUG: 16:48:42.652: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 205s (process:2402): libfprint-device-DEBUG: 16:48:42.652: Device reported close completion 205s (process:2402): libfprint-device-DEBUG: 16:48:42.652: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 205s (process:2402): libfprint-device-DEBUG: 16:48:42.652: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 205s ok 205s (process:2402): libfprint-virtual_device-DEBUG: 16:48:42.652: 93653620: ../libfprint/drivers/virtual-device.c:752 205s (process:2402): libfprint-context-DEBUG: 16:48:42.653: Initializing FpContext (libfprint version 1.94.7+tod1) 205s (process:2402): libfprint-tod-DEBUG: 16:48:42.653: Impossible to load the shared drivers dir Error opening directory “/usr/lib/aarch64-linux-gnu/libfprint-2/tod-1”: No such file or directory 205s (process:2402): libfprint-context-DEBUG: 16:48:42.654: No driver found for USB device 1D6B:0003 205s (process:2402): libfprint-context-DEBUG: 16:48:42.654: No driver found for USB device 0627:0001 205s (process:2402): libfprint-context-DEBUG: 16:48:42.655: No driver found for USB device 1D6B:0002 205s (process:2402): libfprint-context-DEBUG: 16:48:42.655: Found virtual environment device: FP_VIRTUAL_DEVICE, /tmp/libfprint-jsf89zdj/virtual-device.socket 205s (process:2402): libfprint-context-DEBUG: 16:48:42.655: created 205s (process:2402): libfprint-context-DEBUG: 16:48:42.655: Found virtual environment device: FP_VIRTUAL_DEVICE_STORAGE, /tmp/libfprint-nkl_bng_/virtual-device-storage.socket 205s (process:2402): libfprint-context-DEBUG: 16:48:42.655: created 205s (process:2402): libfprint-device-DEBUG: 16:48:42.655: Device reported probe completion 205s (process:2402): libfprint-device-DEBUG: 16:48:42.655: Device reported probe completion 205s (process:2402): libfprint-device-DEBUG: 16:48:42.656: Completing action FPI_DEVICE_ACTION_PROBE in idle! 205s (process:2402): libfprint-device-DEBUG: 16:48:42.656: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 205s (process:2402): libfprint-device-DEBUG: 16:48:42.656: Completing action FPI_DEVICE_ACTION_PROBE in idle! 205s (process:2402): libfprint-device-DEBUG: 16:48:42.656: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 205s test_capture_unsupported (__main__.VirtualDeviceStorage.test_capture_unsupported) ... (process:2402): libfprint-virtual_device-DEBUG: 16:48:42.656: 93657225: ../libfprint/drivers/virtual-device.c:387 205s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:42.656: 93657295: ../libfprint/drivers/virtual-device-listener.c:153 205s (process:2402): libfprint-device-DEBUG: 16:48:42.656: Device reported open completion 205s (process:2402): libfprint-device-DEBUG: 16:48:42.656: Completing action FPI_DEVICE_ACTION_OPEN in idle! 205s (process:2402): libfprint-device-DEBUG: 16:48:42.656: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 205s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:42.657: Got a new connection! 205s (process:2402): libfprint-virtual_device-DEBUG: 16:48:42.657: Got instructions of length 5 205s (process:2402): libfprint-virtual_device-DEBUG: 16:48:42.657: Received command CONT 205s (process:2402): libfprint-virtual_device-DEBUG: 16:48:42.657: Processing command CONT 205s (process:2402): libfprint-device-DEBUG: 16:48:42.657: Device reported deletion completion 205s (process:2402): libfprint-device-DEBUG: 16:48:42.657: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 205s (process:2402): libfprint-device-DEBUG: 16:48:42.657: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 205s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:42.657: Got a new connection! 205s (process:2402): libfprint-virtual_device-DEBUG: 16:48:42.657: Got instructions of length 16 205s (process:2402): libfprint-virtual_device-DEBUG: 16:48:42.657: Received command SET_KEEP_ALIVE 0 205s (process:2402): libfprint-virtual_device-DEBUG: 16:48:42.657: Keep alive toggled: 0 205s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:42.658: Got a new connection! 205s (process:2402): libfprint-virtual_device-DEBUG: 16:48:42.658: Got instructions of length 19 205s (process:2402): libfprint-virtual_device-DEBUG: 16:48:42.658: Received command SET_ENROLL_STAGES 5 205s (process:2402): libfprint-device-DEBUG: 16:48:42.658: Device reported close completion 205s (process:2402): libfprint-device-DEBUG: 16:48:42.658: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 205s (process:2402): libfprint-device-DEBUG: 16:48:42.658: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 205s ok 205s test_change_enroll_stages (__main__.VirtualDeviceStorage.test_change_enroll_stages) ... (process:2402): libfprint-virtual_device-DEBUG: 16:48:42.658: 93659434: ../libfprint/drivers/virtual-device.c:387 205s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:42.658: 93659499: ../libfprint/drivers/virtual-device-listener.c:153 205s (process:2402): libfprint-device-DEBUG: 16:48:42.658: Device reported open completion 205s (process:2402): libfprint-device-DEBUG: 16:48:42.659: Completing action FPI_DEVICE_ACTION_OPEN in idle! 205s (process:2402): libfprint-device-DEBUG: 16:48:42.659: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 205s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:42.659: Got a new connection! 205s (process:2402): libfprint-virtual_device-DEBUG: 16:48:42.659: Got instructions of length 20 205s (process:2402): libfprint-virtual_device-DEBUG: 16:48:42.659: Received command SET_ENROLL_STAGES 20 205s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:42.659: Got a new connection! 205s (process:2402): libfprint-virtual_device-DEBUG: 16:48:42.659: Got instructions of length 19 205s (process:2402): libfprint-virtual_device-DEBUG: 16:48:42.659: Received command SET_ENROLL_STAGES 1 205s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:42.660: Got a new connection! 205s (process:2402): libfprint-virtual_device-DEBUG: 16:48:42.660: Got instructions of length 19 205s (process:2402): libfprint-virtual_device-DEBUG: 16:48:42.660: Received command SET_ENROLL_STAGES 0 205s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:42.660: Got a new connection! 205s (process:2402): libfprint-virtual_device-DEBUG: 16:48:42.660: Got instructions of length 5 205s (process:2402): libfprint-virtual_device-DEBUG: 16:48:42.660: Received command CONT 205s (process:2402): libfprint-virtual_device-DEBUG: 16:48:42.660: Processing command CONT 205s (process:2402): libfprint-device-DEBUG: 16:48:42.660: Device reported deletion completion 205s (process:2402): libfprint-device-DEBUG: 16:48:42.660: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 205s (process:2402): libfprint-device-DEBUG: 16:48:42.660: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 205s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:42.661: Got a new connection! 205s (process:2402): libfprint-virtual_device-DEBUG: 16:48:42.661: Got instructions of length 16 205s (process:2402): libfprint-virtual_device-DEBUG: 16:48:42.661: Received command SET_KEEP_ALIVE 0 205s (process:2402): libfprint-virtual_device-DEBUG: 16:48:42.661: Keep alive toggled: 0 205s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:42.661: Got a new connection! 205s (process:2402): libfprint-virtual_device-DEBUG: 16:48:42.661: Got instructions of length 19 205s (process:2402): libfprint-virtual_device-DEBUG: 16:48:42.661: Received command SET_ENROLL_STAGES 5 205s (process:2402): libfprint-device-DEBUG: 16:48:42.661: Device reported close completion 205s (process:2402): libfprint-device-DEBUG: 16:48:42.661: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 205s (process:2402): libfprint-device-DEBUG: 16:48:42.661: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 205s ok 205s test_change_scan_type (__main__.VirtualDeviceStorage.test_change_scan_type) ... (process:2402): libfprint-virtual_device-DEBUG: 16:48:42.662: 93662831: ../libfprint/drivers/virtual-device.c:387 205s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:42.662: 93662896: ../libfprint/drivers/virtual-device-listener.c:153 205s (process:2402): libfprint-device-DEBUG: 16:48:42.662: Device reported open completion 205s (process:2402): libfprint-device-DEBUG: 16:48:42.662: Completing action FPI_DEVICE_ACTION_OPEN in idle! 205s (process:2402): libfprint-device-DEBUG: 16:48:42.662: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 205s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:42.662: Got a new connection! 205s (process:2402): libfprint-virtual_device-DEBUG: 16:48:42.662: Got instructions of length 19 205s (process:2402): libfprint-virtual_device-DEBUG: 16:48:42.662: Received command SET_SCAN_TYPE press 205s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:42.663: Got a new connection! 205s (process:2402): libfprint-virtual_device-DEBUG: 16:48:42.663: Got instructions of length 19 205s (process:2402): libfprint-virtual_device-DEBUG: 16:48:42.663: Received command SET_SCAN_TYPE swipe 205s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:42.663: Got a new connection! 205s (process:2402): libfprint-virtual_device-DEBUG: 16:48:42.663: Got instructions of length 25 205s (process:2402): libfprint-virtual_device-DEBUG: 16:48:42.663: Received command SET_SCAN_TYPE eye-contact 205s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:42.663: Got a new connection! 205s (process:2402): libfprint-virtual_device-DEBUG: 16:48:42.663: Got instructions of length 5 205s (process:2402): libfprint-virtual_device-DEBUG: 16:48:42.663: Received command CONT 205s (process:2402): libfprint-virtual_device-DEBUG: 16:48:42.663: Processing command CONT 205s (process:2402): libfprint-device-DEBUG: 16:48:42.663: Device reported deletion completion 205s (process:2402): libfprint-device-DEBUG: 16:48:42.663: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 205s (process:2402): libfprint-device-DEBUG: 16:48:42.663: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 205s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:42.663: Got a new connection! 205s (process:2402): libfprint-virtual_device-DEBUG: 16:48:42.664: Got instructions of length 16 205s (process:2402): libfprint-virtual_device-DEBUG: 16:48:42.664: Received command SET_KEEP_ALIVE 0 205s (process:2402): libfprint-virtual_device-DEBUG: 16:48:42.664: Keep alive toggled: 0 205s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:42.664: Got a new connection! 205s (process:2402): libfprint-virtual_device-DEBUG: 16:48:42.664: Got instructions of length 19 205s (process:2402): libfprint-virtual_device-DEBUG: 16:48:42.664: Received command SET_ENROLL_STAGES 5 205s (process:2402): libfprint-device-DEBUG: 16:48:42.664: Device reported close completion 205s (process:2402): libfprint-device-DEBUG: 16:48:42.664: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 205s (process:2402): libfprint-device-DEBUG: 16:48:42.664: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 205s ok 205s test_clear_storage (__main__.VirtualDeviceStorage.test_clear_storage) ... (process:2402): libfprint-virtual_device-DEBUG: 16:48:42.664: 93664921: ../libfprint/drivers/virtual-device.c:387 205s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:42.664: 93664929: ../libfprint/drivers/virtual-device-listener.c:153 205s (process:2402): libfprint-device-DEBUG: 16:48:42.664: Device reported open completion 205s (process:2402): libfprint-device-DEBUG: 16:48:42.664: Completing action FPI_DEVICE_ACTION_OPEN in idle! 205s (process:2402): libfprint-device-DEBUG: 16:48:42.664: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 205s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:42.664: Got a new connection! 205s (process:2402): libfprint-virtual_device-DEBUG: 16:48:42.664: Got instructions of length 9 205s (process:2402): libfprint-virtual_device-DEBUG: 16:48:42.664: Received command INSERT p1 205s (process:2402): libfprint-virtual_device-DEBUG: 16:48:42.664: Processing command INSERT p1 206s (process:2402): libfprint-device-DEBUG: 16:48:43.165: Device reported listing completion 206s (process:2402): libfprint-device-DEBUG: 16:48:43.165: Completing action FPI_DEVICE_ACTION_LIST in idle! 206s (process:2402): libfprint-device-DEBUG: 16:48:43.165: Updated temperature model after 0.50 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 206s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:43.165: Got a new connection! 206s (process:2402): libfprint-virtual_device-DEBUG: 16:48:43.165: Got instructions of length 5 206s (process:2402): libfprint-virtual_device-DEBUG: 16:48:43.165: Received command CONT 206s (process:2402): libfprint-virtual_device-DEBUG: 16:48:43.165: Processing command CONT 206s (process:2402): libfprint-device-DEBUG: 16:48:43.165: Device reported deletion completion 206s (process:2402): libfprint-device-DEBUG: 16:48:43.165: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 206s (process:2402): libfprint-device-DEBUG: 16:48:43.165: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 206s (process:2402): libfprint-device-DEBUG: 16:48:43.666: Device reported listing completion 206s (process:2402): libfprint-device-DEBUG: 16:48:43.666: Completing action FPI_DEVICE_ACTION_LIST in idle! 206s (process:2402): libfprint-device-DEBUG: 16:48:43.666: Updated temperature model after 0.50 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 206s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:43.666: Got a new connection! 206s (process:2402): libfprint-virtual_device-DEBUG: 16:48:43.666: Got instructions of length 5 206s (process:2402): libfprint-virtual_device-DEBUG: 16:48:43.666: Received command CONT 206s (process:2402): libfprint-virtual_device-DEBUG: 16:48:43.666: Processing command CONT 206s (process:2402): libfprint-device-DEBUG: 16:48:43.666: Device reported deletion completion 206s (process:2402): libfprint-device-DEBUG: 16:48:43.666: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 206s (process:2402): libfprint-device-DEBUG: 16:48:43.666: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 206s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:43.666: Got a new connection! 206s (process:2402): libfprint-virtual_device-DEBUG: 16:48:43.666: Got instructions of length 16 206s (process:2402): libfprint-virtual_device-DEBUG: 16:48:43.666: Received command SET_KEEP_ALIVE 0 206s (process:2402): libfprint-virtual_device-DEBUG: 16:48:43.666: Keep alive toggled: 0 206s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:43.667: Got a new connection! 206s (process:2402): libfprint-virtual_device-DEBUG: 16:48:43.667: Got instructions of length 19 206s (process:2402): libfprint-virtual_device-DEBUG: 16:48:43.667: Received command SET_ENROLL_STAGES 5 206s (process:2402): libfprint-device-DEBUG: 16:48:43.667: Device reported close completion 206s (process:2402): libfprint-device-DEBUG: 16:48:43.667: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 206s (process:2402): libfprint-device-DEBUG: 16:48:43.667: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 206s 206s ok 206s test_clear_storage_error (__main__.VirtualDeviceStorage.test_clear_storage_error) ... (process:2402): libfprint-virtual_device-DEBUG: 16:48:43.667: 94667963: ../libfprint/drivers/virtual-device.c:387 206s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:43.667: 94667973: ../libfprint/drivers/virtual-device-listener.c:153 206s (process:2402): libfprint-device-DEBUG: 16:48:43.667: Device reported open completion 206s (process:2402): libfprint-device-DEBUG: 16:48:43.667: Completing action FPI_DEVICE_ACTION_OPEN in idle! 206s (process:2402): libfprint-device-DEBUG: 16:48:43.667: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 206s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:43.667: Got a new connection! 206s (process:2402): libfprint-virtual_device-DEBUG: 16:48:43.667: Got instructions of length 9 206s (process:2402): libfprint-virtual_device-DEBUG: 16:48:43.667: Received command INSERT p1 206s (process:2402): libfprint-virtual_device-DEBUG: 16:48:43.667: Processing command INSERT p1 207s Executing: libfprint-2/virtual-device.test 207s (process:2402): libfprint-device-DEBUG: 16:48:44.168: Device reported listing completion 207s (process:2402): libfprint-device-DEBUG: 16:48:44.168: Completing action FPI_DEVICE_ACTION_LIST in idle! 207s (process:2402): libfprint-device-DEBUG: 16:48:44.168: Updated temperature model after 0.50 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 207s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:44.168: Got a new connection! 207s (process:2402): libfprint-virtual_device-DEBUG: 16:48:44.168: Got instructions of length 7 207s (process:2402): libfprint-virtual_device-DEBUG: 16:48:44.168: Received command ERROR 5 207s (process:2402): libfprint-virtual_device-DEBUG: 16:48:44.168: Processing command ERROR 5 207s (process:2402): libfprint-device-DEBUG: 16:48:44.168: Device reported deletion completion 207s (process:2402): libfprint-device-DEBUG: 16:48:44.168: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 207s (process:2402): libfprint-device-DEBUG: 16:48:44.168: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 207s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:44.168: Got a new connection! 207s (process:2402): libfprint-virtual_device-DEBUG: 16:48:44.168: Got instructions of length 5 207s (process:2402): libfprint-virtual_device-DEBUG: 16:48:44.168: Received command CONT 207s (process:2402): libfprint-virtual_device-DEBUG: 16:48:44.168: Processing command CONT 207s (process:2402): libfprint-device-DEBUG: 16:48:44.168: Device reported deletion completion 207s (process:2402): libfprint-device-DEBUG: 16:48:44.168: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 207s (process:2402): libfprint-device-DEBUG: 16:48:44.168: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 207s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:44.169: Got a new connection! 207s (process:2402): libfprint-virtual_device-DEBUG: 16:48:44.169: Got instructions of length 16 207s (process:2402): libfprint-virtual_device-DEBUG: 16:48:44.169: Received command SET_KEEP_ALIVE 0 207s (process:2402): libfprint-virtual_device-DEBUG: 16:48:44.169: Keep alive toggled: 0 207s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:44.169: Got a new connection! 207s (process:2402): libfprint-virtual_device-DEBUG: 16:48:44.169: Got instructions of length 19 207s (process:2402): libfprint-virtual_device-DEBUG: 16:48:44.169: Received command SET_ENROLL_STAGES 5 207s (process:2402): libfprint-device-DEBUG: 16:48:44.169: Device reported close completion 207s (process:2402): libfprint-device-DEBUG: 16:48:44.169: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 207s (process:2402): libfprint-device-DEBUG: 16:48:44.169: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 207s 207s ok 207s test_close_error (__main__.VirtualDeviceStorage.test_close_error) ... (process:2402): libfprint-virtual_device-DEBUG: 16:48:44.169: 95170016: ../libfprint/drivers/virtual-device.c:387 207s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:44.169: 95170025: ../libfprint/drivers/virtual-device-listener.c:153 207s (process:2402): libfprint-device-DEBUG: 16:48:44.169: Device reported open completion 207s (process:2402): libfprint-device-DEBUG: 16:48:44.169: Completing action FPI_DEVICE_ACTION_OPEN in idle! 207s (process:2402): libfprint-device-DEBUG: 16:48:44.169: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 207s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:44.169: Got a new connection! 207s (process:2402): libfprint-virtual_device-DEBUG: 16:48:44.169: Got instructions of length 9 207s (process:2402): libfprint-virtual_device-DEBUG: 16:48:44.169: Received command SLEEP 100 207s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:44.169: Got a new connection! 207s (process:2402): libfprint-virtual_device-DEBUG: 16:48:44.169: Got instructions of length 7 207s (process:2402): libfprint-virtual_device-DEBUG: 16:48:44.169: Received command ERROR 4 207s (process:2402): libfprint-virtual_device-DEBUG: 16:48:44.169: Processing command SLEEP 100 207s (process:2402): libfprint-virtual_device-DEBUG: 16:48:44.169: Sleeping 100ms 207s (process:2402): libfprint-virtual_device-DEBUG: 16:48:44.269: Sleeping completed 207s (process:2402): libfprint-virtual_device-DEBUG: 16:48:44.270: Processing command ERROR 4 207s (process:2402): libfprint-device-DEBUG: 16:48:44.270: Device reported close completion 207s (process:2402): libfprint-device-DEBUG: 16:48:44.270: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 207s (process:2402): libfprint-device-DEBUG: 16:48:44.270: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 207s ok 207s test_close_while_opening (__main__.VirtualDeviceStorage.test_close_while_opening) ... (process:2402): libfprint-virtual_device-DEBUG: 16:48:44.270: 95271056: ../libfprint/drivers/virtual-device.c:387 207s (process:2402): libfprint-device-DEBUG: 16:48:44.270: Device reported open completion 207s (process:2402): libfprint-device-DEBUG: 16:48:44.270: Completing action FPI_DEVICE_ACTION_OPEN in idle! 207s (process:2402): libfprint-device-DEBUG: 16:48:44.270: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 207s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:44.270: Got a new connection! 207s (process:2402): libfprint-virtual_device-DEBUG: 16:48:44.270: Got instructions of length 16 207s (process:2402): libfprint-virtual_device-DEBUG: 16:48:44.270: Received command SET_KEEP_ALIVE 1 207s (process:2402): libfprint-virtual_device-DEBUG: 16:48:44.270: Keep alive toggled: 1 207s (process:2402): libfprint-device-DEBUG: 16:48:44.270: Device reported close completion 207s (process:2402): libfprint-device-DEBUG: 16:48:44.270: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 207s (process:2402): libfprint-device-DEBUG: 16:48:44.270: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 207s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:44.270: Got a new connection! 207s (process:2402): libfprint-virtual_device-DEBUG: 16:48:44.270: Got instructions of length 9 207s (process:2402): libfprint-virtual_device-DEBUG: 16:48:44.271: Received command SLEEP 500 207s (process:2402): libfprint-virtual_device-DEBUG: 16:48:44.271: 95271796: ../libfprint/drivers/virtual-device.c:387 207s (process:2402): libfprint-virtual_device-DEBUG: 16:48:44.271: Processing command SLEEP 500 207s (process:2402): libfprint-virtual_device-DEBUG: 16:48:44.271: Sleeping 500ms 207s (process:2402): libfprint-virtual_device-DEBUG: 16:48:44.771: Sleeping completed 207s (process:2402): libfprint-virtual_device-DEBUG: 16:48:44.771: 95772601: ../libfprint/drivers/virtual-device.c:387 207s (process:2402): libfprint-device-DEBUG: 16:48:44.771: Device reported open completion 207s (process:2402): libfprint-device-DEBUG: 16:48:44.771: Completing action FPI_DEVICE_ACTION_OPEN in idle! 207s (process:2402): libfprint-device-DEBUG: 16:48:44.772: Updated temperature model after 0.50 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 207s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:44.772: Got a new connection! 207s (process:2402): libfprint-virtual_device-DEBUG: 16:48:44.772: Got instructions of length 5 207s (process:2402): libfprint-virtual_device-DEBUG: 16:48:44.772: Received command CONT 207s (process:2402): libfprint-virtual_device-DEBUG: 16:48:44.772: Processing command CONT 207s (process:2402): libfprint-device-DEBUG: 16:48:44.772: Device reported deletion completion 207s (process:2402): libfprint-device-DEBUG: 16:48:44.772: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 207s (process:2402): libfprint-device-DEBUG: 16:48:44.772: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 207s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:44.772: Got a new connection! 207s (process:2402): libfprint-virtual_device-DEBUG: 16:48:44.772: Got instructions of length 16 207s (process:2402): libfprint-virtual_device-DEBUG: 16:48:44.772: Received command SET_KEEP_ALIVE 0 207s (process:2402): libfprint-virtual_device-DEBUG: 16:48:44.772: Keep alive toggled: 0 207s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:44.772: Got a new connection! 207s (process:2402): libfprint-virtual_device-DEBUG: 16:48:44.772: Got instructions of length 19 207s (process:2402): libfprint-virtual_device-DEBUG: 16:48:44.772: Received command SET_ENROLL_STAGES 5 207s (process:2402): libfprint-device-DEBUG: 16:48:44.772: Device reported close completion 207s (process:2402): libfprint-device-DEBUG: 16:48:44.772: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 207s (process:2402): libfprint-device-DEBUG: 16:48:44.772: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 207s ok 207s test_delayed_open (__main__.VirtualDeviceStorage.test_delayed_open) ... (process:2402): libfprint-virtual_device-DEBUG: 16:48:44.773: 95773743: ../libfprint/drivers/virtual-device.c:387 207s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:44.773: 95773767: ../libfprint/drivers/virtual-device-listener.c:153 207s (process:2402): libfprint-device-DEBUG: 16:48:44.773: Device reported open completion 207s (process:2402): libfprint-device-DEBUG: 16:48:44.773: Completing action FPI_DEVICE_ACTION_OPEN in idle! 207s (process:2402): libfprint-device-DEBUG: 16:48:44.773: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 207s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:44.773: Got a new connection! 207s (process:2402): libfprint-virtual_device-DEBUG: 16:48:44.773: Got instructions of length 16 207s (process:2402): libfprint-virtual_device-DEBUG: 16:48:44.773: Received command IGNORED_COMMAND 207s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:44.773: Got a new connection! 207s (process:2402): libfprint-virtual_device-DEBUG: 16:48:44.773: Got instructions of length 9 207s (process:2402): libfprint-virtual_device-DEBUG: 16:48:44.773: Received command SLEEP 500 207s (process:2402): libfprint-virtual_device-DEBUG: 16:48:44.773: Processing command IGNORED_COMMAND 207s (process:2402): libfprint-device-DEBUG: 16:48:44.773: Device reported close completion 207s (process:2402): libfprint-device-DEBUG: 16:48:44.773: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 207s (process:2402): libfprint-device-DEBUG: 16:48:44.773: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 207s (process:2402): libfprint-virtual_device-DEBUG: 16:48:44.774: 95774696: ../libfprint/drivers/virtual-device.c:387 207s (process:2402): libfprint-virtual_device-DEBUG: 16:48:44.774: Processing command SLEEP 500 207s (process:2402): libfprint-virtual_device-DEBUG: 16:48:44.774: Sleeping 500ms 208s (process:2402): libfprint-virtual_device-DEBUG: 16:48:45.274: Sleeping completed 208s (process:2402): libfprint-virtual_device-DEBUG: 16:48:45.274: 96275448: ../libfprint/drivers/virtual-device.c:387 208s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:45.274: 96275473: ../libfprint/drivers/virtual-device-listener.c:153 208s (process:2402): libfprint-device-DEBUG: 16:48:45.274: Device reported open completion 208s (process:2402): libfprint-device-DEBUG: 16:48:45.274: Completing action FPI_DEVICE_ACTION_OPEN in idle! 208s (process:2402): libfprint-device-DEBUG: 16:48:45.275: Updated temperature model after 0.50 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 208s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:45.275: Got a new connection! 208s (process:2402): libfprint-virtual_device-DEBUG: 16:48:45.275: Got instructions of length 5 208s (process:2402): libfprint-virtual_device-DEBUG: 16:48:45.275: Received command CONT 208s (process:2402): libfprint-virtual_device-DEBUG: 16:48:45.275: Processing command CONT 208s (process:2402): libfprint-device-DEBUG: 16:48:45.275: Device reported deletion completion 208s (process:2402): libfprint-device-DEBUG: 16:48:45.275: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 208s (process:2402): libfprint-device-DEBUG: 16:48:45.275: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 208s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:45.275: Got a new connection! 208s (process:2402): libfprint-virtual_device-DEBUG: 16:48:45.275: Got instructions of length 16 208s (process:2402): libfprint-virtual_device-DEBUG: 16:48:45.275: Received command SET_KEEP_ALIVE 0 208s (process:2402): libfprint-virtual_device-DEBUG: 16:48:45.275: Keep alive toggled: 0 208s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:45.275: Got a new connection! 208s (process:2402): libfprint-virtual_device-DEBUG: 16:48:45.275: Got instructions of length 19 208s (process:2402): libfprint-virtual_device-DEBUG: 16:48:45.275: Received command SET_ENROLL_STAGES 5 208s (process:2402): libfprint-device-DEBUG: 16:48:45.275: Device reported close completion 208s (process:2402): libfprint-device-DEBUG: 16:48:45.275: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 208s (process:2402): libfprint-device-DEBUG: 16:48:45.275: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 208s ok 208s test_delayed_open_with_keep_alive (__main__.VirtualDeviceStorage.test_delayed_open_with_keep_alive) ... (process:2402): libfprint-virtual_device-DEBUG: 16:48:45.276: 96276820: ../libfprint/drivers/virtual-device.c:387 208s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:45.276: 96276854: ../libfprint/drivers/virtual-device-listener.c:153 208s (process:2402): libfprint-device-DEBUG: 16:48:45.276: Device reported open completion 208s (process:2402): libfprint-device-DEBUG: 16:48:45.276: Completing action FPI_DEVICE_ACTION_OPEN in idle! 208s (process:2402): libfprint-device-DEBUG: 16:48:45.276: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 208s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:45.276: Got a new connection! 208s (process:2402): libfprint-virtual_device-DEBUG: 16:48:45.276: Got instructions of length 16 208s (process:2402): libfprint-virtual_device-DEBUG: 16:48:45.276: Received command SET_KEEP_ALIVE 1 208s (process:2402): libfprint-virtual_device-DEBUG: 16:48:45.276: Keep alive toggled: 1 208s (process:2402): libfprint-device-DEBUG: 16:48:45.276: Device reported close completion 208s (process:2402): libfprint-device-DEBUG: 16:48:45.276: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 208s (process:2402): libfprint-device-DEBUG: 16:48:45.276: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 208s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:45.276: Got a new connection! 208s (process:2402): libfprint-virtual_device-DEBUG: 16:48:45.276: Got instructions of length 9 208s (process:2402): libfprint-virtual_device-DEBUG: 16:48:45.276: Received command SLEEP 500 208s (process:2402): libfprint-virtual_device-DEBUG: 16:48:45.276: 96277577: ../libfprint/drivers/virtual-device.c:387 208s (process:2402): libfprint-virtual_device-DEBUG: 16:48:45.276: Processing command SLEEP 500 208s (process:2402): libfprint-virtual_device-DEBUG: 16:48:45.276: Sleeping 500ms 208s (process:2402): libfprint-virtual_device-DEBUG: 16:48:45.777: Sleeping completed 208s (process:2402): libfprint-virtual_device-DEBUG: 16:48:45.777: 96778421: ../libfprint/drivers/virtual-device.c:387 208s (process:2402): libfprint-device-DEBUG: 16:48:45.777: Device reported open completion 208s (process:2402): libfprint-device-DEBUG: 16:48:45.777: Completing action FPI_DEVICE_ACTION_OPEN in idle! 208s (process:2402): libfprint-device-DEBUG: 16:48:45.777: Updated temperature model after 0.50 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 208s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:45.778: Got a new connection! 208s (process:2402): libfprint-virtual_device-DEBUG: 16:48:45.778: Got instructions of length 5 208s (process:2402): libfprint-virtual_device-DEBUG: 16:48:45.778: Received command CONT 208s (process:2402): libfprint-virtual_device-DEBUG: 16:48:45.778: Processing command CONT 208s (process:2402): libfprint-device-DEBUG: 16:48:45.778: Device reported deletion completion 208s (process:2402): libfprint-device-DEBUG: 16:48:45.778: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 208s (process:2402): libfprint-device-DEBUG: 16:48:45.778: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 208s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:45.778: Got a new connection! 208s (process:2402): libfprint-virtual_device-DEBUG: 16:48:45.778: Got instructions of length 16 208s (process:2402): libfprint-virtual_device-DEBUG: 16:48:45.778: Received command SET_KEEP_ALIVE 0 208s (process:2402): libfprint-virtual_device-DEBUG: 16:48:45.778: Keep alive toggled: 0 208s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:45.778: Got a new connection! 208s (process:2402): libfprint-virtual_device-DEBUG: 16:48:45.778: Got instructions of length 19 208s (process:2402): libfprint-virtual_device-DEBUG: 16:48:45.778: Received command SET_ENROLL_STAGES 5 208s (process:2402): libfprint-device-DEBUG: 16:48:45.778: Device reported close completion 208s (process:2402): libfprint-device-DEBUG: 16:48:45.778: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 208s (process:2402): libfprint-device-DEBUG: 16:48:45.778: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 208s ok 208s test_delete_error (__main__.VirtualDeviceStorage.test_delete_error) ... (process:2402): libfprint-virtual_device-DEBUG: 16:48:45.779: 96779734: ../libfprint/drivers/virtual-device.c:387 208s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:45.779: 96779755: ../libfprint/drivers/virtual-device-listener.c:153 208s (process:2402): libfprint-device-DEBUG: 16:48:45.779: Device reported open completion 208s (process:2402): libfprint-device-DEBUG: 16:48:45.779: Completing action FPI_DEVICE_ACTION_OPEN in idle! 208s (process:2402): libfprint-device-DEBUG: 16:48:45.779: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 208s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:45.779: Got a new connection! 208s (process:2402): libfprint-virtual_device-DEBUG: 16:48:45.779: Got instructions of length 9 208s (process:2402): libfprint-virtual_device-DEBUG: 16:48:45.779: Received command SLEEP 100 208s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:45.779: Got a new connection! 208s (process:2402): libfprint-virtual_device-DEBUG: 16:48:45.779: Got instructions of length 7 208s (process:2402): libfprint-virtual_device-DEBUG: 16:48:45.779: Received command ERROR 7 208s (process:2402): libfprint-virtual_device-DEBUG: 16:48:45.779: Processing command SLEEP 100 208s (process:2402): libfprint-virtual_device-DEBUG: 16:48:45.779: Sleeping 100ms 208s (process:2402): libfprint-virtual_device-DEBUG: 16:48:45.880: Sleeping completed 208s (process:2402): libfprint-virtual_device-DEBUG: 16:48:45.880: Processing command ERROR 7 208s (process:2402): libfprint-device-DEBUG: 16:48:45.880: Device reported deletion completion 208s (process:2402): libfprint-device-DEBUG: 16:48:45.880: Completing action FPI_DEVICE_ACTION_DELETE in idle! 208s (process:2402): libfprint-device-DEBUG: 16:48:45.880: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 208s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:45.880: Got a new connection! 208s (process:2402): libfprint-virtual_device-DEBUG: 16:48:45.880: Got instructions of length 5 208s (process:2402): libfprint-virtual_device-DEBUG: 16:48:45.880: Received command CONT 208s (process:2402): libfprint-virtual_device-DEBUG: 16:48:45.880: Processing command CONT 208s (process:2402): libfprint-device-DEBUG: 16:48:45.880: Device reported deletion completion 208s (process:2402): libfprint-device-DEBUG: 16:48:45.880: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 208s (process:2402): libfprint-device-DEBUG: 16:48:45.880: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 208s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:45.880: Got a new connection! 208s (process:2402): libfprint-virtual_device-DEBUG: 16:48:45.880: Got instructions of length 16 208s (process:2402): libfprint-virtual_device-DEBUG: 16:48:45.880: Received command SET_KEEP_ALIVE 0 208s (process:2402): libfprint-virtual_device-DEBUG: 16:48:45.880: Keep alive toggled: 0 208s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:45.880: Got a new connection! 208s (process:2402): libfprint-virtual_device-DEBUG: 16:48:45.881: Got instructions of length 19 208s (process:2402): libfprint-virtual_device-DEBUG: 16:48:45.881: Received command SET_ENROLL_STAGES 5 208s (process:2402): libfprint-device-DEBUG: 16:48:45.881: Device reported close completion 208s (process:2402): libfprint-device-DEBUG: 16:48:45.881: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 208s (process:2402): libfprint-device-DEBUG: 16:48:45.881: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 208s ok 208s test_delete_multiple_times (__main__.VirtualDeviceStorage.test_delete_multiple_times) ... (process:2402): libfprint-virtual_device-DEBUG: 16:48:45.881: 96881991: ../libfprint/drivers/virtual-device.c:387 208s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:45.881: 96882012: ../libfprint/drivers/virtual-device-listener.c:153 208s (process:2402): libfprint-device-DEBUG: 16:48:45.881: Device reported open completion 208s (process:2402): libfprint-device-DEBUG: 16:48:45.881: Completing action FPI_DEVICE_ACTION_OPEN in idle! 208s (process:2402): libfprint-device-DEBUG: 16:48:45.881: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 208s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:45.881: Got a new connection! 208s (process:2402): libfprint-virtual_device-DEBUG: 16:48:45.881: Got instructions of length 16 208s (process:2402): libfprint-virtual_device-DEBUG: 16:48:45.881: Received command SCAN right-thumb 208s (process:2402): libfprint-device-DEBUG: 16:48:45.881: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 208s (process:2402): libfprint-virtual_device-DEBUG: 16:48:45.881: Processing command SCAN right-thumb 208s (process:2402): libfprint-device-DEBUG: 16:48:45.881: Device reported finger status change: FP_FINGER_STATUS_NEEDED 208s (process:2402): libfprint-device-DEBUG: 16:48:45.881: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 208s (process:2402): libfprint-device-DEBUG: 16:48:45.881: Device reported finger status change: FP_FINGER_STATUS_NEEDED 208s (process:2402): libfprint-device-DEBUG: 16:48:45.881: Device reported enroll progress, reported 1 of 5 have been completed 208s (process:2402): libfprint-virtual_device-DEBUG: 16:48:45.881: Sleeping completed 208s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:45.882: Got a new connection! 208s (process:2402): libfprint-virtual_device-DEBUG: 16:48:45.882: Got instructions of length 16 208s (process:2402): libfprint-virtual_device-DEBUG: 16:48:45.882: Received command SCAN right-thumb 208s (process:2402): libfprint-virtual_device-DEBUG: 16:48:45.882: Processing command SCAN right-thumb 208s (process:2402): libfprint-device-DEBUG: 16:48:45.882: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 208s (process:2402): libfprint-device-DEBUG: 16:48:45.882: Device reported finger status change: FP_FINGER_STATUS_NEEDED 208s (process:2402): libfprint-device-DEBUG: 16:48:45.882: Device reported enroll progress, reported 2 of 5 have been completed 208s (process:2402): libfprint-virtual_device-DEBUG: 16:48:45.882: Sleeping completed 208s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:45.882: Got a new connection! 208s (process:2402): libfprint-virtual_device-DEBUG: 16:48:45.882: Got instructions of length 16 208s (process:2402): libfprint-virtual_device-DEBUG: 16:48:45.882: Received command SCAN right-thumb 208s (process:2402): libfprint-virtual_device-DEBUG: 16:48:45.882: Processing command SCAN right-thumb 208s (process:2402): libfprint-device-DEBUG: 16:48:45.882: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 208s (process:2402): libfprint-device-DEBUG: 16:48:45.882: Device reported finger status change: FP_FINGER_STATUS_NEEDED 208s (process:2402): libfprint-device-DEBUG: 16:48:45.882: Device reported enroll progress, reported 3 of 5 have been completed 208s (process:2402): libfprint-virtual_device-DEBUG: 16:48:45.882: Sleeping completed 208s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:45.882: Got a new connection! 208s (process:2402): libfprint-virtual_device-DEBUG: 16:48:45.882: Got instructions of length 16 208s (process:2402): libfprint-virtual_device-DEBUG: 16:48:45.882: Received command SCAN right-thumb 208s (process:2402): libfprint-virtual_device-DEBUG: 16:48:45.882: Processing command SCAN right-thumb 208s (process:2402): libfprint-device-DEBUG: 16:48:45.882: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 208s (process:2402): libfprint-device-DEBUG: 16:48:45.882: Device reported finger status change: FP_FINGER_STATUS_NEEDED 208s (process:2402): libfprint-device-DEBUG: 16:48:45.882: Device reported enroll progress, reported 4 of 5 have been completed 208s (process:2402): libfprint-virtual_device-DEBUG: 16:48:45.882: Sleeping completed 208s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:45.882: Got a new connection! 208s (process:2402): libfprint-virtual_device-DEBUG: 16:48:45.883: Got instructions of length 16 208s (process:2402): libfprint-virtual_device-DEBUG: 16:48:45.883: Received command SCAN right-thumb 208s (process:2402): libfprint-virtual_device-DEBUG: 16:48:45.883: Processing command SCAN right-thumb 208s (process:2402): libfprint-device-DEBUG: 16:48:45.883: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 208s (process:2402): libfprint-device-DEBUG: 16:48:45.883: Device reported finger status change: FP_FINGER_STATUS_NEEDED 208s (process:2402): libfprint-device-DEBUG: 16:48:45.883: Device reported enroll progress, reported 5 of 5 have been completed 208s (process:2402): libfprint-device-DEBUG: 16:48:45.883: Device reported enroll completion 208s (process:2402): libfprint-device-DEBUG: 16:48:45.883: Device reported finger status change: FP_FINGER_STATUS_NONE 208s (process:2402): libfprint-device-DEBUG: 16:48:45.883: Print for finger FP_FINGER_RIGHT_THUMB enrolled 208s (process:2402): libfprint-device-DEBUG: 16:48:45.883: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 208s (process:2402): libfprint-device-DEBUG: 16:48:45.883: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 209s (process:2402): libfprint-virtual_device_storage-DEBUG: 16:48:46.384: Deleting print right-thumb for user testuser 209s (process:2402): libfprint-device-DEBUG: 16:48:46.384: Device reported deletion completion 209s (process:2402): libfprint-device-DEBUG: 16:48:46.384: Completing action FPI_DEVICE_ACTION_DELETE in idle! 209s (process:2402): libfprint-device-DEBUG: 16:48:46.384: Updated temperature model after 0.50 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 209s (process:2402): libfprint-virtual_device_storage-DEBUG: 16:48:46.884: Deleting print right-thumb for user testuser 209s (process:2402): libfprint-device-DEBUG: 16:48:46.885: Device reported deletion completion 209s (process:2402): libfprint-device-DEBUG: 16:48:46.885: Completing action FPI_DEVICE_ACTION_DELETE in idle! 209s (process:2402): libfprint-device-DEBUG: 16:48:46.885: Updated temperature model after 0.50 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 209s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:46.885: Got a new connection! 209s (process:2402): libfprint-virtual_device-DEBUG: 16:48:46.885: Got instructions of length 5 209s (process:2402): libfprint-virtual_device-DEBUG: 16:48:46.885: Received command CONT 209s (process:2402): libfprint-virtual_device-DEBUG: 16:48:46.885: Processing command CONT 209s (process:2402): libfprint-device-DEBUG: 16:48:46.885: Device reported deletion completion 209s (process:2402): libfprint-device-DEBUG: 16:48:46.885: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 209s (process:2402): libfprint-device-DEBUG: 16:48:46.885: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 209s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:46.885: Got a new connection! 209s (process:2402): libfprint-virtual_device-DEBUG: 16:48:46.885: Got instructions of length 16 209s (process:2402): libfprint-virtual_device-DEBUG: 16:48:46.885: Received command SET_KEEP_ALIVE 0 209s (process:2402): libfprint-virtual_device-DEBUG: 16:48:46.885: Keep alive toggled: 0 209s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:46.885: Got a new connection! 209s (process:2402): libfprint-virtual_device-DEBUG: 16:48:46.885: Got instructions of length 19 209s (process:2402): libfprint-virtual_device-DEBUG: 16:48:46.885: Received command SET_ENROLL_STAGES 5 209s (process:2402): libfprint-device-DEBUG: 16:48:46.886: Device reported close completion 209s (process:2402): libfprint-device-DEBUG: 16:48:46.886: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 209s (process:2402): libfprint-device-DEBUG: 16:48:46.886: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 209s Enroll done 209s ok 209s test_device_features (__main__.VirtualDeviceStorage.test_device_features) ... (process:2402): libfprint-virtual_device-DEBUG: 16:48:46.886: 97886835: ../libfprint/drivers/virtual-device.c:387 209s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:46.886: 97886844: ../libfprint/drivers/virtual-device-listener.c:153 209s (process:2402): libfprint-device-DEBUG: 16:48:46.886: Device reported open completion 209s (process:2402): libfprint-device-DEBUG: 16:48:46.886: Completing action FPI_DEVICE_ACTION_OPEN in idle! 209s (process:2402): libfprint-device-DEBUG: 16:48:46.886: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 209s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:46.886: Got a new connection! 209s (process:2402): libfprint-virtual_device-DEBUG: 16:48:46.886: Got instructions of length 5 209s (process:2402): libfprint-virtual_device-DEBUG: 16:48:46.886: Received command CONT 209s (process:2402): libfprint-virtual_device-DEBUG: 16:48:46.886: Processing command CONT 209s (process:2402): libfprint-device-DEBUG: 16:48:46.886: Device reported deletion completion 209s (process:2402): libfprint-device-DEBUG: 16:48:46.886: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 209s (process:2402): libfprint-device-DEBUG: 16:48:46.886: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 209s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:46.886: Got a new connection! 209s (process:2402): libfprint-virtual_device-DEBUG: 16:48:46.886: Got instructions of length 16 209s (process:2402): libfprint-virtual_device-DEBUG: 16:48:46.886: Received command SET_KEEP_ALIVE 0 209s (process:2402): libfprint-virtual_device-DEBUG: 16:48:46.886: Keep alive toggled: 0 209s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:46.886: Got a new connection! 209s (process:2402): libfprint-virtual_device-DEBUG: 16:48:46.886: Got instructions of length 19 209s (process:2402): libfprint-virtual_device-DEBUG: 16:48:46.886: Received command SET_ENROLL_STAGES 5 209s (process:2402): libfprint-device-DEBUG: 16:48:46.886: Device reported close completion 209s (process:2402): libfprint-device-DEBUG: 16:48:46.886: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 209s (process:2402): libfprint-device-DEBUG: 16:48:46.886: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 209s ok 209s test_device_properties (__main__.VirtualDeviceStorage.test_device_properties) ... (process:2402): libfprint-virtual_device-DEBUG: 16:48:46.886: 97887435: ../libfprint/drivers/virtual-device.c:387 209s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:46.886: 97887442: ../libfprint/drivers/virtual-device-listener.c:153 209s (process:2402): libfprint-device-DEBUG: 16:48:46.886: Device reported open completion 209s (process:2402): libfprint-device-DEBUG: 16:48:46.886: Completing action FPI_DEVICE_ACTION_OPEN in idle! 209s (process:2402): libfprint-device-DEBUG: 16:48:46.886: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 209s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:46.886: Got a new connection! 209s (process:2402): libfprint-virtual_device-DEBUG: 16:48:46.886: Got instructions of length 5 209s (process:2402): libfprint-virtual_device-DEBUG: 16:48:46.886: Received command CONT 209s (process:2402): libfprint-virtual_device-DEBUG: 16:48:46.887: Processing command CONT 209s (process:2402): libfprint-device-DEBUG: 16:48:46.887: Device reported deletion completion 209s (process:2402): libfprint-device-DEBUG: 16:48:46.887: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 209s (process:2402): libfprint-device-DEBUG: 16:48:46.887: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 209s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:46.887: Got a new connection! 209s (process:2402): libfprint-virtual_device-DEBUG: 16:48:46.887: Got instructions of length 16 209s (process:2402): libfprint-virtual_device-DEBUG: 16:48:46.887: Received command SET_KEEP_ALIVE 0 209s (process:2402): libfprint-virtual_device-DEBUG: 16:48:46.887: Keep alive toggled: 0 209s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:46.887: Got a new connection! 209s (process:2402): libfprint-virtual_device-DEBUG: 16:48:46.887: Got instructions of length 19 209s (process:2402): libfprint-virtual_device-DEBUG: 16:48:46.887: Received command SET_ENROLL_STAGES 5 209s (process:2402): libfprint-device-DEBUG: 16:48:46.887: Device reported close completion 209s (process:2402): libfprint-device-DEBUG: 16:48:46.887: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 209s (process:2402): libfprint-device-DEBUG: 16:48:46.887: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 209s ok 209s test_device_sleep (__main__.VirtualDeviceStorage.test_device_sleep) ... (process:2402): libfprint-virtual_device-DEBUG: 16:48:46.887: 97888100: ../libfprint/drivers/virtual-device.c:387 209s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:46.887: 97888147: ../libfprint/drivers/virtual-device-listener.c:153 209s (process:2402): libfprint-device-DEBUG: 16:48:46.887: Device reported open completion 209s (process:2402): libfprint-device-DEBUG: 16:48:46.887: Completing action FPI_DEVICE_ACTION_OPEN in idle! 209s (process:2402): libfprint-device-DEBUG: 16:48:46.887: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 209s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:46.887: Got a new connection! 209s (process:2402): libfprint-virtual_device-DEBUG: 16:48:46.887: Got instructions of length 10 209s (process:2402): libfprint-virtual_device-DEBUG: 16:48:46.887: Received command SLEEP 1500 209s (process:2402): libfprint-device-DEBUG: 16:48:46.888: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 209s (process:2402): libfprint-virtual_device-DEBUG: 16:48:46.888: Processing command SLEEP 1500 209s (process:2402): libfprint-virtual_device-DEBUG: 16:48:46.888: Sleeping 1500ms 210s (process:2402): libfprint-device-DEBUG: 16:48:47.188: Idle cancelling on ongoing operation! 210s (process:2402): libfprint-virtual_device-DEBUG: 16:48:47.188: Got cancellation! 210s (process:2402): libfprint-device-DEBUG: 16:48:47.188: Device reported finger status change: FP_FINGER_STATUS_NEEDED 210s (process:2402): libfprint-device-DEBUG: 16:48:47.188: Device reported identify completion 210s (process:2402): libfprint-device-DEBUG: 16:48:47.188: Device reported finger status change: FP_FINGER_STATUS_NONE 210s (process:2402): libfprint-device-DEBUG: 16:48:47.188: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 210s (process:2402): libfprint-device-DEBUG: 16:48:47.188: Updated temperature model after 0.30 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 210s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:47.388: Got a new connection! 210s (process:2402): libfprint-virtual_device-DEBUG: 16:48:47.388: Got instructions of length 5 210s (process:2402): libfprint-virtual_device-DEBUG: 16:48:47.388: Received command CONT 210s (process:2402): libfprint-virtual_device-DEBUG: 16:48:47.388: Processing command CONT 210s (process:2402): libfprint-device-DEBUG: 16:48:47.388: Device reported deletion completion 210s (process:2402): libfprint-device-DEBUG: 16:48:47.388: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 210s (process:2402): libfprint-device-DEBUG: 16:48:47.388: Updated temperature model after 0.20 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 210s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:47.388: Got a new connection! 210s (process:2402): libfprint-virtual_device-DEBUG: 16:48:47.388: Got instructions of length 16 210s (process:2402): libfprint-virtual_device-DEBUG: 16:48:47.388: Received command SET_KEEP_ALIVE 0 210s (process:2402): libfprint-virtual_device-DEBUG: 16:48:47.388: Keep alive toggled: 0 210s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:47.388: Got a new connection! 210s (process:2402): libfprint-virtual_device-DEBUG: 16:48:47.388: Got instructions of length 19 210s (process:2402): libfprint-virtual_device-DEBUG: 16:48:47.388: Received command SET_ENROLL_STAGES 5 210s (process:2402): libfprint-device-DEBUG: 16:48:47.389: Device reported close completion 210s (process:2402): libfprint-device-DEBUG: 16:48:47.389: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 210s (process:2402): libfprint-device-DEBUG: 16:48:47.389: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 210s ok 210s test_device_sleep_before_completing_verify (__main__.VirtualDeviceStorage.test_device_sleep_before_completing_verify) ... (process:2402): libfprint-virtual_device-DEBUG: 16:48:47.389: 98389906: ../libfprint/drivers/virtual-device.c:387 210s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:47.389: 98389942: ../libfprint/drivers/virtual-device-listener.c:153 210s (process:2402): libfprint-device-DEBUG: 16:48:47.389: Device reported open completion 210s (process:2402): libfprint-device-DEBUG: 16:48:47.389: Completing action FPI_DEVICE_ACTION_OPEN in idle! 210s (process:2402): libfprint-device-DEBUG: 16:48:47.389: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 210s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:47.389: Got a new connection! 210s (process:2402): libfprint-virtual_device-DEBUG: 16:48:47.389: Got instructions of length 14 210s (process:2402): libfprint-virtual_device-DEBUG: 16:48:47.389: Received command SCAN foo-print 210s (process:2402): libfprint-device-DEBUG: 16:48:47.389: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 210s (process:2402): libfprint-virtual_device-DEBUG: 16:48:47.389: Processing command SCAN foo-print 210s (process:2402): libfprint-device-DEBUG: 16:48:47.389: Device reported finger status change: FP_FINGER_STATUS_NEEDED 210s (process:2402): libfprint-device-DEBUG: 16:48:47.389: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 210s (process:2402): libfprint-device-DEBUG: 16:48:47.389: Device reported finger status change: FP_FINGER_STATUS_NEEDED 210s (process:2402): libfprint-device-DEBUG: 16:48:47.389: Device reported enroll progress, reported 1 of 5 have been completed 210s (process:2402): libfprint-virtual_device-DEBUG: 16:48:47.389: Sleeping completed 210s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:47.389: Got a new connection! 210s (process:2402): libfprint-virtual_device-DEBUG: 16:48:47.390: Got instructions of length 14 210s (process:2402): libfprint-virtual_device-DEBUG: 16:48:47.390: Received command SCAN foo-print 210s (process:2402): libfprint-virtual_device-DEBUG: 16:48:47.390: Processing command SCAN foo-print 210s (process:2402): libfprint-device-DEBUG: 16:48:47.390: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 210s (process:2402): libfprint-device-DEBUG: 16:48:47.390: Device reported finger status change: FP_FINGER_STATUS_NEEDED 210s (process:2402): libfprint-device-DEBUG: 16:48:47.390: Device reported enroll progress, reported 2 of 5 have been completed 210s (process:2402): libfprint-virtual_device-DEBUG: 16:48:47.390: Sleeping completed 210s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:47.390: Got a new connection! 210s (process:2402): libfprint-virtual_device-DEBUG: 16:48:47.390: Got instructions of length 14 210s (process:2402): libfprint-virtual_device-DEBUG: 16:48:47.390: Received command SCAN foo-print 210s (process:2402): libfprint-virtual_device-DEBUG: 16:48:47.390: Processing command SCAN foo-print 210s (process:2402): libfprint-device-DEBUG: 16:48:47.390: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 210s (process:2402): libfprint-device-DEBUG: 16:48:47.390: Device reported finger status change: FP_FINGER_STATUS_NEEDED 210s (process:2402): libfprint-device-DEBUG: 16:48:47.390: Device reported enroll progress, reported 3 of 5 have been completed 210s (process:2402): libfprint-virtual_device-DEBUG: 16:48:47.390: Sleeping completed 210s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:47.390: Got a new connection! 210s (process:2402): libfprint-virtual_device-DEBUG: 16:48:47.390: Got instructions of length 14 210s (process:2402): libfprint-virtual_device-DEBUG: 16:48:47.390: Received command SCAN foo-print 210s (process:2402): libfprint-virtual_device-DEBUG: 16:48:47.390: Processing command SCAN foo-print 210s (process:2402): libfprint-device-DEBUG: 16:48:47.390: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 210s (process:2402): libfprint-device-DEBUG: 16:48:47.390: Device reported finger status change: FP_FINGER_STATUS_NEEDED 210s (process:2402): libfprint-device-DEBUG: 16:48:47.390: Device reported enroll progress, reported 4 of 5 have been completed 210s (process:2402): libfprint-virtual_device-DEBUG: 16:48:47.390: Sleeping completed 210s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:47.390: Got a new connection! 210s (process:2402): libfprint-virtual_device-DEBUG: 16:48:47.391: Got instructions of length 14 210s (process:2402): libfprint-virtual_device-DEBUG: 16:48:47.391: Received command SCAN foo-print 210s (process:2402): libfprint-virtual_device-DEBUG: 16:48:47.391: Processing command SCAN foo-print 210s (process:2402): libfprint-device-DEBUG: 16:48:47.391: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 210s (process:2402): libfprint-device-DEBUG: 16:48:47.391: Device reported finger status change: FP_FINGER_STATUS_NEEDED 210s (process:2402): libfprint-device-DEBUG: 16:48:47.391: Device reported enroll progress, reported 5 of 5 have been completed 210s (process:2402): libfprint-device-DEBUG: 16:48:47.391: Device reported enroll completion 210s (process:2402): libfprint-device-DEBUG: 16:48:47.391: Device reported finger status change: FP_FINGER_STATUS_NONE 210s (process:2402): libfprint-device-DEBUG: 16:48:47.391: Print for finger FP_FINGER_LEFT_RING enrolled 210s (process:2402): libfprint-device-DEBUG: 16:48:47.391: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 210s (process:2402): libfprint-device-DEBUG: 16:48:47.391: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 210s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:47.391: Got a new connection! 210s (process:2402): libfprint-virtual_device-DEBUG: 16:48:47.391: Got instructions of length 9 210s (process:2402): libfprint-virtual_device-DEBUG: 16:48:47.391: Received command SLEEP 100 210s (process:2402): libfprint-device-DEBUG: 16:48:47.391: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 210s (process:2402): libfprint-virtual_device-DEBUG: 16:48:47.391: Processing command SLEEP 100 210s (process:2402): libfprint-virtual_device-DEBUG: 16:48:47.391: Sleeping 100ms 210s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:47.391: Got a new connection! 210s (process:2402): libfprint-virtual_device-DEBUG: 16:48:47.392: Got instructions of length 14 210s (process:2402): libfprint-virtual_device-DEBUG: 16:48:47.392: Received command SCAN bar-print 210s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:47.392: Got a new connection! 210s (process:2402): libfprint-virtual_device-DEBUG: 16:48:47.392: Got instructions of length 9 210s (process:2402): libfprint-virtual_device-DEBUG: 16:48:47.392: Received command SLEEP 800 210s (process:2402): libfprint-virtual_device-DEBUG: 16:48:47.491: Sleeping completed 210s (process:2402): libfprint-virtual_device-DEBUG: 16:48:47.491: Processing command SCAN bar-print 210s (process:2402): libfprint-device-DEBUG: 16:48:47.491: Device reported finger status change: FP_FINGER_STATUS_NEEDED 210s (process:2402): libfprint-device-DEBUG: 16:48:47.492: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 210s (process:2402): libfprint-virtual_device_storage-DEBUG: 16:48:47.492: Trying to identify print 'bar-print' against a gallery of 1 prints 210s (process:2402): libfprint-device-DEBUG: 16:48:47.492: Device reported identify result 210s (process:2402): libfprint-device-DEBUG: 16:48:47.492: Device reported finger status change: FP_FINGER_STATUS_NEEDED 210s (process:2402): libfprint-virtual_device-DEBUG: 16:48:47.492: Processing command SLEEP 800 210s (process:2402): libfprint-virtual_device-DEBUG: 16:48:47.492: Sleeping 800ms 210s (process:2402): libfprint-virtual_device-DEBUG: 16:48:47.492: Sleeping now, command queued for later: SCAN bar-print 210s (process:2402): libfprint-device-DEBUG: 16:48:47.729: Updated temperature model after 0.34 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 211s (process:2402): libfprint-virtual_device-DEBUG: 16:48:48.293: Sleeping completed 211s (process:2402): libfprint-virtual_device-DEBUG: 16:48:48.293: Processing command SCAN bar-print 211s (process:2402): libfprint-device-DEBUG: 16:48:48.293: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 211s (process:2402): libfprint-virtual_device_storage-DEBUG: 16:48:48.293: Trying to identify print 'bar-print' against a gallery of 1 prints 211s (process:2402): libfprint-device-DEBUG: 16:48:48.293: Device reported finger status change: FP_FINGER_STATUS_NEEDED 211s (process:2402): libfprint-device-DEBUG: 16:48:48.293: Device reported identify completion 211s (process:2402): libfprint-device-DEBUG: 16:48:48.293: Device reported finger status change: FP_FINGER_STATUS_NONE 211s (process:2402): libfprint-device-DEBUG: 16:48:48.293: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 211s (process:2402): libfprint-device-DEBUG: 16:48:48.293: Updated temperature model after 0.56 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 211s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:48.294: Got a new connection! 211s (process:2402): libfprint-virtual_device-DEBUG: 16:48:48.294: Got instructions of length 5 211s (process:2402): libfprint-virtual_device-DEBUG: 16:48:48.294: Received command CONT 211s (process:2402): libfprint-virtual_device-DEBUG: 16:48:48.294: Processing command CONT 211s (process:2402): libfprint-device-DEBUG: 16:48:48.294: Device reported deletion completion 211s (process:2402): libfprint-device-DEBUG: 16:48:48.294: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 211s (process:2402): libfprint-device-DEBUG: 16:48:48.294: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 211s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:48.294: Got a new connection! 211s (process:2402): libfprint-virtual_device-DEBUG: 16:48:48.294: Got instructions of length 16 211s (process:2402): libfprint-virtual_device-DEBUG: 16:48:48.294: Received command SET_KEEP_ALIVE 0 211s (process:2402): libfprint-virtual_device-DEBUG: 16:48:48.294: Keep alive toggled: 0 211s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:48.294: Got a new connection! 211s (process:2402): libfprint-virtual_device-DEBUG: 16:48:48.294: Got instructions of length 19 211s (process:2402): libfprint-virtual_device-DEBUG: 16:48:48.294: Received command SET_ENROLL_STAGES 5 211s (process:2402): libfprint-device-DEBUG: 16:48:48.294: Device reported close completion 211s (process:2402): libfprint-device-DEBUG: 16:48:48.294: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 211s (process:2402): libfprint-device-DEBUG: 16:48:48.294: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 211s Enroll done 211s ok 211s test_device_sleep_on_cancellation (__main__.VirtualDeviceStorage.test_device_sleep_on_cancellation) ... (process:2402): libfprint-virtual_device-DEBUG: 16:48:48.294: 99295145: ../libfprint/drivers/virtual-device.c:387 211s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:48.294: 99295154: ../libfprint/drivers/virtual-device-listener.c:153 211s (process:2402): libfprint-device-DEBUG: 16:48:48.294: Device reported open completion 211s (process:2402): libfprint-device-DEBUG: 16:48:48.294: Completing action FPI_DEVICE_ACTION_OPEN in idle! 211s (process:2402): libfprint-device-DEBUG: 16:48:48.294: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 211s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:48.294: Got a new connection! 211s (process:2402): libfprint-virtual_device-DEBUG: 16:48:48.294: Got instructions of length 26 211s (process:2402): libfprint-virtual_device-DEBUG: 16:48:48.294: Received command SET_CANCELLATION_ENABLED 0 211s (process:2402): libfprint-virtual_device-DEBUG: 16:48:48.294: Cancellation support toggled: 0 211s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:48.294: Got a new connection! 211s (process:2402): libfprint-virtual_device-DEBUG: 16:48:48.294: Got instructions of length 10 211s (process:2402): libfprint-virtual_device-DEBUG: 16:48:48.294: Received command SLEEP 1500 211s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:48.294: Got a new connection! 211s (process:2402): libfprint-virtual_device-DEBUG: 16:48:48.294: Got instructions of length 14 211s (process:2402): libfprint-virtual_device-DEBUG: 16:48:48.294: Received command SCAN foo-print 211s (process:2402): libfprint-device-DEBUG: 16:48:48.294: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 211s (process:2402): libfprint-virtual_device-DEBUG: 16:48:48.294: Processing command SLEEP 1500 211s (process:2402): libfprint-virtual_device-DEBUG: 16:48:48.294: Sleeping 1500ms 211s (process:2402): libfprint-device-DEBUG: 16:48:48.595: Idle cancelling on ongoing operation! 212s Executing: libfprint-2/virtual-device.test 212s (process:2402): libfprint-virtual_device-DEBUG: 16:48:49.805: Sleeping completed 212s (process:2402): libfprint-device-DEBUG: 16:48:49.815: Device reported finger status change: FP_FINGER_STATUS_NEEDED 212s (process:2402): libfprint-device-DEBUG: 16:48:49.819: Device reported identify completion 212s (process:2402): libfprint-device-DEBUG: 16:48:49.819: Device reported finger status change: FP_FINGER_STATUS_NONE 212s (process:2402): libfprint-device-DEBUG: 16:48:49.840: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 212s (process:2402): libfprint-device-DEBUG: 16:48:49.840: Updated temperature model after 1.55 seconds, ratio 0.27 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 212s (process:2402): libfprint-virtual_device-DEBUG: 16:48:49.849: Processing command SCAN foo-print 212s (process:2402): libfprint-device-DEBUG: 16:48:49.849: Device reported close completion 212s (process:2402): libfprint-device-DEBUG: 16:48:49.849: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 212s (process:2402): libfprint-device-DEBUG: 16:48:49.849: Updated temperature model after 0.01 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 212s ok 212s test_duplicate_enroll (__main__.VirtualDeviceStorage.test_duplicate_enroll) ... (process:2402): libfprint-virtual_device-DEBUG: 16:48:49.850: 100850868: ../libfprint/drivers/virtual-device.c:387 212s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:49.850: 100850915: ../libfprint/drivers/virtual-device-listener.c:153 212s (process:2402): libfprint-device-DEBUG: 16:48:49.850: Device reported open completion 212s (process:2402): libfprint-device-DEBUG: 16:48:49.850: Completing action FPI_DEVICE_ACTION_OPEN in idle! 212s (process:2402): libfprint-device-DEBUG: 16:48:49.850: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 212s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:49.859: Got a new connection! 212s (process:2402): libfprint-virtual_device-DEBUG: 16:48:49.859: Got instructions of length 14 212s (process:2402): libfprint-virtual_device-DEBUG: 16:48:49.859: Received command SCAN testprint 212s (process:2402): libfprint-device-DEBUG: 16:48:49.864: Updated temperature model after 0.01 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 212s (process:2402): libfprint-virtual_device-DEBUG: 16:48:49.864: Processing command SCAN testprint 212s (process:2402): libfprint-device-DEBUG: 16:48:49.864: Device reported finger status change: FP_FINGER_STATUS_NEEDED 212s (process:2402): libfprint-device-DEBUG: 16:48:49.864: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 212s (process:2402): libfprint-device-DEBUG: 16:48:49.864: Device reported finger status change: FP_FINGER_STATUS_NEEDED 212s (process:2402): libfprint-device-DEBUG: 16:48:49.864: Device reported enroll progress, reported 1 of 5 have been completed 212s (process:2402): libfprint-virtual_device-DEBUG: 16:48:49.864: Sleeping completed 212s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:49.864: Got a new connection! 212s (process:2402): libfprint-virtual_device-DEBUG: 16:48:49.865: Got instructions of length 14 212s (process:2402): libfprint-virtual_device-DEBUG: 16:48:49.865: Received command SCAN testprint 212s (process:2402): libfprint-virtual_device-DEBUG: 16:48:49.865: Processing command SCAN testprint 212s (process:2402): libfprint-device-DEBUG: 16:48:49.865: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 212s (process:2402): libfprint-device-DEBUG: 16:48:49.865: Device reported finger status change: FP_FINGER_STATUS_NEEDED 212s (process:2402): libfprint-device-DEBUG: 16:48:49.865: Device reported enroll progress, reported 2 of 5 have been completed 212s (process:2402): libfprint-virtual_device-DEBUG: 16:48:49.865: Sleeping completed 212s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:49.865: Got a new connection! 212s (process:2402): libfprint-virtual_device-DEBUG: 16:48:49.865: Got instructions of length 14 212s (process:2402): libfprint-virtual_device-DEBUG: 16:48:49.865: Received command SCAN testprint 212s (process:2402): libfprint-virtual_device-DEBUG: 16:48:49.865: Processing command SCAN testprint 212s (process:2402): libfprint-device-DEBUG: 16:48:49.865: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 212s (process:2402): libfprint-device-DEBUG: 16:48:49.865: Device reported finger status change: FP_FINGER_STATUS_NEEDED 212s (process:2402): libfprint-device-DEBUG: 16:48:49.865: Device reported enroll progress, reported 3 of 5 have been completed 212s (process:2402): libfprint-virtual_device-DEBUG: 16:48:49.865: Sleeping completed 212s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:49.865: Got a new connection! 212s (process:2402): libfprint-virtual_device-DEBUG: 16:48:49.865: Got instructions of length 14 212s (process:2402): libfprint-virtual_device-DEBUG: 16:48:49.866: Received command SCAN testprint 212s (process:2402): libfprint-virtual_device-DEBUG: 16:48:49.866: Processing command SCAN testprint 212s (process:2402): libfprint-device-DEBUG: 16:48:49.866: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 212s (process:2402): libfprint-device-DEBUG: 16:48:49.866: Device reported finger status change: FP_FINGER_STATUS_NEEDED 212s (process:2402): libfprint-device-DEBUG: 16:48:49.866: Device reported enroll progress, reported 4 of 5 have been completed 212s (process:2402): libfprint-virtual_device-DEBUG: 16:48:49.866: Sleeping completed 212s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:49.866: Got a new connection! 212s (process:2402): libfprint-virtual_device-DEBUG: 16:48:49.866: Got instructions of length 14 212s (process:2402): libfprint-virtual_device-DEBUG: 16:48:49.866: Received command SCAN testprint 212s (process:2402): libfprint-virtual_device-DEBUG: 16:48:49.866: Processing command SCAN testprint 212s (process:2402): libfprint-device-DEBUG: 16:48:49.866: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 212s (process:2402): libfprint-device-DEBUG: 16:48:49.866: Device reported finger status change: FP_FINGER_STATUS_NEEDED 212s (process:2402): libfprint-device-DEBUG: 16:48:49.866: Device reported enroll progress, reported 5 of 5 have been completed 212s (process:2402): libfprint-device-DEBUG: 16:48:49.866: Device reported enroll completion 212s (process:2402): libfprint-device-DEBUG: 16:48:49.866: Device reported finger status change: FP_FINGER_STATUS_NONE 212s (process:2402): libfprint-device-DEBUG: 16:48:49.866: Print for finger FP_FINGER_LEFT_LITTLE enrolled 212s (process:2402): libfprint-device-DEBUG: 16:48:49.866: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 212s (process:2402): libfprint-device-DEBUG: 16:48:49.866: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 212s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:49.871: Got a new connection! 212s (process:2402): libfprint-virtual_device-DEBUG: 16:48:49.872: Got instructions of length 14 212s (process:2402): libfprint-virtual_device-DEBUG: 16:48:49.872: Received command SCAN testprint 212s (process:2402): libfprint-device-DEBUG: 16:48:49.872: Updated temperature model after 0.01 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 212s (process:2402): libfprint-virtual_device-DEBUG: 16:48:49.872: Processing command SCAN testprint 212s (process:2402): libfprint-device-DEBUG: 16:48:49.872: Device reported finger status change: FP_FINGER_STATUS_NEEDED 212s (process:2402): libfprint-device-DEBUG: 16:48:49.872: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 212s (process:2402): libfprint-device-DEBUG: 16:48:49.872: Device reported enroll completion 212s (process:2402): libfprint-device-DEBUG: 16:48:49.872: Device reported finger status change: FP_FINGER_STATUS_NONE 212s (process:2402): libfprint-device-DEBUG: 16:48:49.872: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 212s (process:2402): libfprint-device-DEBUG: 16:48:49.872: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 212s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:49.877: Got a new connection! 212s (process:2402): libfprint-virtual_device-DEBUG: 16:48:49.877: Got instructions of length 5 212s (process:2402): libfprint-virtual_device-DEBUG: 16:48:49.877: Received command CONT 212s (process:2402): libfprint-virtual_device-DEBUG: 16:48:49.877: Processing command CONT 212s (process:2402): libfprint-device-DEBUG: 16:48:49.877: Device reported deletion completion 212s (process:2402): libfprint-device-DEBUG: 16:48:49.877: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 212s (process:2402): libfprint-device-DEBUG: 16:48:49.877: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 212s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:49.877: Got a new connection! 212s (process:2402): libfprint-virtual_device-DEBUG: 16:48:49.877: Got instructions of length 16 212s (process:2402): libfprint-virtual_device-DEBUG: 16:48:49.877: Received command SET_KEEP_ALIVE 0 212s (process:2402): libfprint-virtual_device-DEBUG: 16:48:49.877: Keep alive toggled: 0 212s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:49.877: Got a new connection! 212s (process:2402): libfprint-virtual_device-DEBUG: 16:48:49.877: Got instructions of length 19 212s (process:2402): libfprint-virtual_device-DEBUG: 16:48:49.877: Received command SET_ENROLL_STAGES 5 212s (process:2402): libfprint-device-DEBUG: 16:48:49.878: Device reported close completion 212s (process:2402): libfprint-device-DEBUG: 16:48:49.878: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 212s (process:2402): libfprint-device-DEBUG: 16:48:49.878: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 212s Enroll done 212s Enroll done 212s ok 212s test_enroll (__main__.VirtualDeviceStorage.test_enroll) ... (process:2402): libfprint-virtual_device-DEBUG: 16:48:49.878: 100879044: ../libfprint/drivers/virtual-device.c:387 212s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:49.878: 100879090: ../libfprint/drivers/virtual-device-listener.c:153 212s (process:2402): libfprint-device-DEBUG: 16:48:49.878: Device reported open completion 212s (process:2402): libfprint-device-DEBUG: 16:48:49.878: Completing action FPI_DEVICE_ACTION_OPEN in idle! 212s (process:2402): libfprint-device-DEBUG: 16:48:49.878: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 212s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:49.878: Got a new connection! 212s (process:2402): libfprint-virtual_device-DEBUG: 16:48:49.878: Got instructions of length 14 212s (process:2402): libfprint-virtual_device-DEBUG: 16:48:49.878: Received command SCAN testprint 212s (process:2402): libfprint-device-DEBUG: 16:48:49.878: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 212s (process:2402): libfprint-virtual_device-DEBUG: 16:48:49.879: Processing command SCAN testprint 212s (process:2402): libfprint-device-DEBUG: 16:48:49.879: Device reported finger status change: FP_FINGER_STATUS_NEEDED 212s (process:2402): libfprint-device-DEBUG: 16:48:49.879: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 212s (process:2402): libfprint-device-DEBUG: 16:48:49.879: Device reported finger status change: FP_FINGER_STATUS_NEEDED 212s (process:2402): libfprint-device-DEBUG: 16:48:49.879: Device reported enroll progress, reported 1 of 5 have been completed 212s (process:2402): libfprint-virtual_device-DEBUG: 16:48:49.879: Sleeping completed 212s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:49.879: Got a new connection! 212s (process:2402): libfprint-virtual_device-DEBUG: 16:48:49.879: Got instructions of length 14 212s (process:2402): libfprint-virtual_device-DEBUG: 16:48:49.879: Received command SCAN testprint 212s (process:2402): libfprint-virtual_device-DEBUG: 16:48:49.879: Processing command SCAN testprint 212s (process:2402): libfprint-device-DEBUG: 16:48:49.879: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 212s (process:2402): libfprint-device-DEBUG: 16:48:49.879: Device reported finger status change: FP_FINGER_STATUS_NEEDED 212s (process:2402): libfprint-device-DEBUG: 16:48:49.879: Device reported enroll progress, reported 2 of 5 have been completed 212s (process:2402): libfprint-virtual_device-DEBUG: 16:48:49.879: Sleeping completed 212s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:49.879: Got a new connection! 212s (process:2402): libfprint-virtual_device-DEBUG: 16:48:49.879: Got instructions of length 14 212s (process:2402): libfprint-virtual_device-DEBUG: 16:48:49.879: Received command SCAN testprint 212s (process:2402): libfprint-virtual_device-DEBUG: 16:48:49.879: Processing command SCAN testprint 212s (process:2402): libfprint-device-DEBUG: 16:48:49.879: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 212s (process:2402): libfprint-device-DEBUG: 16:48:49.879: Device reported finger status change: FP_FINGER_STATUS_NEEDED 212s (process:2402): libfprint-device-DEBUG: 16:48:49.879: Device reported enroll progress, reported 3 of 5 have been completed 212s (process:2402): libfprint-virtual_device-DEBUG: 16:48:49.879: Sleeping completed 212s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:49.879: Got a new connection! 212s (process:2402): libfprint-virtual_device-DEBUG: 16:48:49.879: Got instructions of length 14 212s (process:2402): libfprint-virtual_device-DEBUG: 16:48:49.879: Received command SCAN testprint 212s (process:2402): libfprint-virtual_device-DEBUG: 16:48:49.879: Processing command SCAN testprint 212s (process:2402): libfprint-device-DEBUG: 16:48:49.879: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 212s (process:2402): libfprint-device-DEBUG: 16:48:49.879: Device reported finger status change: FP_FINGER_STATUS_NEEDED 212s (process:2402): libfprint-device-DEBUG: 16:48:49.879: Device reported enroll progress, reported 4 of 5 have been completed 212s (process:2402): libfprint-virtual_device-DEBUG: 16:48:49.879: Sleeping completed 212s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:49.879: Got a new connection! 212s (process:2402): libfprint-virtual_device-DEBUG: 16:48:49.880: Got instructions of length 14 212s (process:2402): libfprint-virtual_device-DEBUG: 16:48:49.880: Received command SCAN testprint 212s (process:2402): libfprint-virtual_device-DEBUG: 16:48:49.880: Processing command SCAN testprint 212s (process:2402): libfprint-device-DEBUG: 16:48:49.880: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 212s (process:2402): libfprint-device-DEBUG: 16:48:49.880: Device reported finger status change: FP_FINGER_STATUS_NEEDED 212s (process:2402): libfprint-device-DEBUG: 16:48:49.880: Device reported enroll progress, reported 5 of 5 have been completed 212s (process:2402): libfprint-device-DEBUG: 16:48:49.880: Device reported enroll completion 212s (process:2402): libfprint-device-DEBUG: 16:48:49.880: Device reported finger status change: FP_FINGER_STATUS_NONE 212s (process:2402): libfprint-device-DEBUG: 16:48:49.880: Print for finger FP_FINGER_LEFT_LITTLE enrolled 212s (process:2402): libfprint-device-DEBUG: 16:48:49.880: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 212s (process:2402): libfprint-device-DEBUG: 16:48:49.880: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 212s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:49.880: Got a new connection! 212s (process:2402): libfprint-virtual_device-DEBUG: 16:48:49.880: Got instructions of length 5 212s (process:2402): libfprint-virtual_device-DEBUG: 16:48:49.880: Received command CONT 212s (process:2402): libfprint-virtual_device-DEBUG: 16:48:49.880: Processing command CONT 212s (process:2402): libfprint-device-DEBUG: 16:48:49.880: Device reported deletion completion 212s (process:2402): libfprint-device-DEBUG: 16:48:49.880: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 212s (process:2402): libfprint-device-DEBUG: 16:48:49.880: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 212s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:49.880: Got a new connection! 212s (process:2402): libfprint-virtual_device-DEBUG: 16:48:49.880: Got instructions of length 16 212s (process:2402): libfprint-virtual_device-DEBUG: 16:48:49.880: Received command SET_KEEP_ALIVE 0 212s (process:2402): libfprint-virtual_device-DEBUG: 16:48:49.880: Keep alive toggled: 0 212s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:49.880: Got a new connection! 212s (process:2402): libfprint-virtual_device-DEBUG: 16:48:49.880: Got instructions of length 19 212s (process:2402): libfprint-virtual_device-DEBUG: 16:48:49.880: Received command SET_ENROLL_STAGES 5 212s (process:2402): libfprint-device-DEBUG: 16:48:49.880: Device reported close completion 212s (process:2402): libfprint-device-DEBUG: 16:48:49.880: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 212s (process:2402): libfprint-device-DEBUG: 16:48:49.880: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 212s Enroll done 212s ok 212s test_enroll_script (__main__.VirtualDeviceStorage.test_enroll_script) ... (process:2402): libfprint-virtual_device-DEBUG: 16:48:49.880: 100881353: ../libfprint/drivers/virtual-device.c:387 212s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:49.880: 100881362: ../libfprint/drivers/virtual-device-listener.c:153 212s (process:2402): libfprint-device-DEBUG: 16:48:49.880: Device reported open completion 212s (process:2402): libfprint-device-DEBUG: 16:48:49.880: Completing action FPI_DEVICE_ACTION_OPEN in idle! 212s (process:2402): libfprint-device-DEBUG: 16:48:49.880: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 212s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:49.880: Got a new connection! 212s (process:2402): libfprint-virtual_device-DEBUG: 16:48:49.880: Got instructions of length 19 212s (process:2402): libfprint-virtual_device-DEBUG: 16:48:49.880: Received command SET_ENROLL_STAGES 8 212s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:49.880: Got a new connection! 212s (process:2402): libfprint-virtual_device-DEBUG: 16:48:49.880: Got instructions of length 13 212s (process:2402): libfprint-virtual_device-DEBUG: 16:48:49.880: Received command SCAN print-id 212s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:49.881: Got a new connection! 212s (process:2402): libfprint-virtual_device-DEBUG: 16:48:49.881: Got instructions of length 13 212s (process:2402): libfprint-virtual_device-DEBUG: 16:48:49.881: Received command SCAN print-id 212s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:49.881: Got a new connection! 212s (process:2402): libfprint-virtual_device-DEBUG: 16:48:49.881: Got instructions of length 7 212s (process:2402): libfprint-virtual_device-DEBUG: 16:48:49.881: Received command RETRY 1 212s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:49.881: Got a new connection! 212s (process:2402): libfprint-virtual_device-DEBUG: 16:48:49.881: Got instructions of length 13 212s (process:2402): libfprint-virtual_device-DEBUG: 16:48:49.881: Received command SCAN print-id 212s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:49.881: Got a new connection! 212s (process:2402): libfprint-virtual_device-DEBUG: 16:48:49.881: Got instructions of length 7 212s (process:2402): libfprint-virtual_device-DEBUG: 16:48:49.881: Received command RETRY 3 212s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:49.881: Got a new connection! 212s (process:2402): libfprint-virtual_device-DEBUG: 16:48:49.881: Got instructions of length 13 212s (process:2402): libfprint-virtual_device-DEBUG: 16:48:49.881: Received command SCAN print-id 212s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:49.881: Got a new connection! 212s (process:2402): libfprint-virtual_device-DEBUG: 16:48:49.881: Got instructions of length 7 212s (process:2402): libfprint-virtual_device-DEBUG: 16:48:49.881: Received command RETRY 2 212s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:49.881: Got a new connection! 212s (process:2402): libfprint-virtual_device-DEBUG: 16:48:49.881: Got instructions of length 13 212s (process:2402): libfprint-virtual_device-DEBUG: 16:48:49.881: Received command SCAN print-id 212s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:49.881: Got a new connection! 212s (process:2402): libfprint-virtual_device-DEBUG: 16:48:49.881: Got instructions of length 8 212s (process:2402): libfprint-virtual_device-DEBUG: 16:48:49.881: Received command SLEEP 10 212s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:49.881: Got a new connection! 212s (process:2402): libfprint-virtual_device-DEBUG: 16:48:49.881: Got instructions of length 8 212s (process:2402): libfprint-virtual_device-DEBUG: 16:48:49.881: Received command SLEEP 20 212s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:49.881: Got a new connection! 212s (process:2402): libfprint-virtual_device-DEBUG: 16:48:49.881: Got instructions of length 7 212s (process:2402): libfprint-virtual_device-DEBUG: 16:48:49.881: Received command RETRY 0 212s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:49.881: Got a new connection! 212s (process:2402): libfprint-virtual_device-DEBUG: 16:48:49.881: Got instructions of length 7 212s (process:2402): libfprint-virtual_device-DEBUG: 16:48:49.881: Received command RETRY 3 212s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:49.881: Got a new connection! 212s (process:2402): libfprint-virtual_device-DEBUG: 16:48:49.882: Got instructions of length 13 212s (process:2402): libfprint-virtual_device-DEBUG: 16:48:49.882: Received command SCAN print-id 212s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:49.882: Got a new connection! 212s (process:2402): libfprint-virtual_device-DEBUG: 16:48:49.882: Got instructions of length 15 212s (process:2402): libfprint-virtual_device-DEBUG: 16:48:49.882: Received command SCAN another-id 212s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:49.882: Got a new connection! 212s (process:2402): libfprint-virtual_device-DEBUG: 16:48:49.882: Got instructions of length 13 212s (process:2402): libfprint-virtual_device-DEBUG: 16:48:49.882: Received command SCAN print-id 212s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:49.882: Got a new connection! 212s (process:2402): libfprint-virtual_device-DEBUG: 16:48:49.882: Got instructions of length 13 212s (process:2402): libfprint-virtual_device-DEBUG: 16:48:49.882: Received command SCAN print-id 212s (process:2402): libfprint-device-DEBUG: 16:48:49.882: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 212s (process:2402): libfprint-virtual_device-DEBUG: 16:48:49.882: Processing command SCAN print-id 212s (process:2402): libfprint-device-DEBUG: 16:48:49.882: Device reported finger status change: FP_FINGER_STATUS_NEEDED 212s (process:2402): libfprint-device-DEBUG: 16:48:49.882: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 212s (process:2402): libfprint-device-DEBUG: 16:48:49.882: Device reported finger status change: FP_FINGER_STATUS_NEEDED 212s (process:2402): libfprint-device-DEBUG: 16:48:49.882: Device reported enroll progress, reported 1 of 8 have been completed 212s (process:2402): libfprint-virtual_device-DEBUG: 16:48:49.882: Sleeping completed 212s (process:2402): libfprint-virtual_device-DEBUG: 16:48:49.882: Processing command SCAN print-id 212s (process:2402): libfprint-device-DEBUG: 16:48:49.882: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 212s (process:2402): libfprint-device-DEBUG: 16:48:49.882: Device reported finger status change: FP_FINGER_STATUS_NEEDED 212s (process:2402): libfprint-device-DEBUG: 16:48:49.882: Device reported enroll progress, reported 2 of 8 have been completed 212s (process:2402): libfprint-virtual_device-DEBUG: 16:48:49.882: Sleeping completed 212s (process:2402): libfprint-virtual_device-DEBUG: 16:48:49.882: Processing command RETRY 1 212s (process:2402): libfprint-device-DEBUG: 16:48:49.882: Device reported enroll progress, reported 2 of 8 have been completed 212s (process:2402): libfprint-virtual_device-DEBUG: 16:48:49.882: Sleeping completed 212s (process:2402): libfprint-virtual_device-DEBUG: 16:48:49.882: Processing command SCAN print-id 212s (process:2402): libfprint-device-DEBUG: 16:48:49.882: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 212s (process:2402): libfprint-device-DEBUG: 16:48:49.882: Device reported finger status change: FP_FINGER_STATUS_NEEDED 212s (process:2402): libfprint-device-DEBUG: 16:48:49.882: Device reported enroll progress, reported 3 of 8 have been completed 212s (process:2402): libfprint-virtual_device-DEBUG: 16:48:49.882: Sleeping completed 212s (process:2402): libfprint-virtual_device-DEBUG: 16:48:49.882: Processing command RETRY 3 212s (process:2402): libfprint-device-DEBUG: 16:48:49.882: Device reported enroll progress, reported 3 of 8 have been completed 212s (process:2402): libfprint-virtual_device-DEBUG: 16:48:49.882: Sleeping completed 212s (process:2402): libfprint-virtual_device-DEBUG: 16:48:49.882: Processing command SCAN print-id 212s (process:2402): libfprint-device-DEBUG: 16:48:49.882: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 212s (process:2402): libfprint-device-DEBUG: 16:48:49.882: Device reported finger status change: FP_FINGER_STATUS_NEEDED 212s (process:2402): libfprint-device-DEBUG: 16:48:49.882: Device reported enroll progress, reported 4 of 8 have been completed 212s (process:2402): libfprint-virtual_device-DEBUG: 16:48:49.882: Sleeping completed 212s (process:2402): libfprint-virtual_device-DEBUG: 16:48:49.882: Processing command RETRY 2 212s (process:2402): libfprint-device-DEBUG: 16:48:49.882: Device reported enroll progress, reported 4 of 8 have been completed 212s (process:2402): libfprint-virtual_device-DEBUG: 16:48:49.882: Sleeping completed 212s (process:2402): libfprint-virtual_device-DEBUG: 16:48:49.882: Processing command SCAN print-id 212s (process:2402): libfprint-device-DEBUG: 16:48:49.882: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 212s (process:2402): libfprint-device-DEBUG: 16:48:49.882: Device reported finger status change: FP_FINGER_STATUS_NEEDED 212s (process:2402): libfprint-device-DEBUG: 16:48:49.882: Device reported enroll progress, reported 5 of 8 have been completed 212s (process:2402): libfprint-virtual_device-DEBUG: 16:48:49.882: Processing command SLEEP 10 212s (process:2402): libfprint-virtual_device-DEBUG: 16:48:49.882: Sleeping 10ms 212s (process:2402): libfprint-virtual_device-DEBUG: 16:48:49.892: Sleeping completed 212s (process:2402): libfprint-virtual_device-DEBUG: 16:48:49.892: Processing command SLEEP 20 212s (process:2402): libfprint-virtual_device-DEBUG: 16:48:49.892: Sleeping 20ms 212s (process:2402): libfprint-virtual_device-DEBUG: 16:48:49.912: Sleeping completed 212s (process:2402): libfprint-virtual_device-DEBUG: 16:48:49.912: Processing command RETRY 0 212s (process:2402): libfprint-device-DEBUG: 16:48:49.912: Device reported enroll progress, reported 5 of 8 have been completed 212s (process:2402): libfprint-virtual_device-DEBUG: 16:48:49.912: Sleeping completed 212s (process:2402): libfprint-virtual_device-DEBUG: 16:48:49.912: Processing command RETRY 3 212s (process:2402): libfprint-device-DEBUG: 16:48:49.912: Device reported enroll progress, reported 5 of 8 have been completed 212s (process:2402): libfprint-virtual_device-DEBUG: 16:48:49.912: Sleeping completed 212s (process:2402): libfprint-virtual_device-DEBUG: 16:48:49.912: Processing command SCAN print-id 212s (process:2402): libfprint-device-DEBUG: 16:48:49.912: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 212s (process:2402): libfprint-device-DEBUG: 16:48:49.912: Device reported finger status change: FP_FINGER_STATUS_NEEDED 212s (process:2402): libfprint-device-DEBUG: 16:48:49.912: Device reported enroll progress, reported 6 of 8 have been completed 212s (process:2402): libfprint-virtual_device-DEBUG: 16:48:49.912: Sleeping completed 212s (process:2402): libfprint-virtual_device-DEBUG: 16:48:49.912: Processing command SCAN another-id 212s (process:2402): libfprint-device-DEBUG: 16:48:49.912: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 212s (process:2402): libfprint-device-DEBUG: 16:48:49.912: Device reported enroll progress, reported 6 of 8 have been completed 212s (process:2402): libfprint-virtual_device-DEBUG: 16:48:49.912: Sleeping completed 212s (process:2402): libfprint-virtual_device-DEBUG: 16:48:49.912: Processing command SCAN print-id 212s (process:2402): libfprint-device-DEBUG: 16:48:49.912: Device reported finger status change: FP_FINGER_STATUS_NEEDED 212s (process:2402): libfprint-device-DEBUG: 16:48:49.912: Device reported enroll progress, reported 7 of 8 have been completed 212s (process:2402): libfprint-virtual_device-DEBUG: 16:48:49.912: Sleeping completed 212s (process:2402): libfprint-virtual_device-DEBUG: 16:48:49.912: Processing command SCAN print-id 212s (process:2402): libfprint-device-DEBUG: 16:48:49.912: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 212s (process:2402): libfprint-device-DEBUG: 16:48:49.912: Device reported finger status change: FP_FINGER_STATUS_NEEDED 212s (process:2402): libfprint-device-DEBUG: 16:48:49.912: Device reported enroll progress, reported 8 of 8 have been completed 212s (process:2402): libfprint-device-DEBUG: 16:48:49.912: Device reported enroll completion 212s (process:2402): libfprint-device-DEBUG: 16:48:49.912: Device reported finger status change: FP_FINGER_STATUS_NONE 212s (process:2402): libfprint-device-DEBUG: 16:48:49.912: Print for finger FP_FINGER_UNKNOWN enrolled 212s (process:2402): libfprint-device-DEBUG: 16:48:49.912: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 212s (process:2402): libfprint-device-DEBUG: 16:48:49.912: Updated temperature model after 0.03 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 212s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:49.913: Got a new connection! 212s (process:2402): libfprint-virtual_device-DEBUG: 16:48:49.913: Got instructions of length 5 212s (process:2402): libfprint-virtual_device-DEBUG: 16:48:49.913: Received command CONT 212s (process:2402): libfprint-virtual_device-DEBUG: 16:48:49.913: Processing command CONT 212s (process:2402): libfprint-device-DEBUG: 16:48:49.913: Device reported deletion completion 212s (process:2402): libfprint-device-DEBUG: 16:48:49.913: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 212s (process:2402): libfprint-device-DEBUG: 16:48:49.913: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 212s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:49.913: Got a new connection! 212s (process:2402): libfprint-virtual_device-DEBUG: 16:48:49.913: Got instructions of length 16 212s (process:2402): libfprint-virtual_device-DEBUG: 16:48:49.913: Received command SET_KEEP_ALIVE 0 212s (process:2402): libfprint-virtual_device-DEBUG: 16:48:49.913: Keep alive toggled: 0 212s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:49.913: Got a new connection! 212s (process:2402): libfprint-virtual_device-DEBUG: 16:48:49.913: Got instructions of length 19 212s (process:2402): libfprint-virtual_device-DEBUG: 16:48:49.913: Received command SET_ENROLL_STAGES 5 212s (process:2402): libfprint-device-DEBUG: 16:48:49.913: Device reported close completion 212s (process:2402): libfprint-device-DEBUG: 16:48:49.913: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 212s (process:2402): libfprint-device-DEBUG: 16:48:49.913: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 212s ok 212s test_enroll_script_interactive (__main__.VirtualDeviceStorage.test_enroll_script_interactive) ... (process:2402): libfprint-virtual_device-DEBUG: 16:48:49.913: 100914437: ../libfprint/drivers/virtual-device.c:387 212s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:49.913: 100914446: ../libfprint/drivers/virtual-device-listener.c:153 212s (process:2402): libfprint-device-DEBUG: 16:48:49.913: Device reported open completion 212s (process:2402): libfprint-device-DEBUG: 16:48:49.913: Completing action FPI_DEVICE_ACTION_OPEN in idle! 212s (process:2402): libfprint-device-DEBUG: 16:48:49.913: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 212s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:49.913: Got a new connection! 212s (process:2402): libfprint-virtual_device-DEBUG: 16:48:49.913: Got instructions of length 8 212s (process:2402): libfprint-virtual_device-DEBUG: 16:48:49.913: Received command SLEEP 50 212s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:49.914: Got a new connection! 212s (process:2402): libfprint-virtual_device-DEBUG: 16:48:49.914: Got instructions of length 13 212s (process:2402): libfprint-virtual_device-DEBUG: 16:48:49.914: Received command SCAN print-id 212s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:49.914: Got a new connection! 212s (process:2402): libfprint-virtual_device-DEBUG: 16:48:49.914: Got instructions of length 13 212s (process:2402): libfprint-virtual_device-DEBUG: 16:48:49.914: Received command SCAN print-id 212s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:49.914: Got a new connection! 212s (process:2402): libfprint-virtual_device-DEBUG: 16:48:49.914: Got instructions of length 7 212s (process:2402): libfprint-virtual_device-DEBUG: 16:48:49.914: Received command RETRY 1 212s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:49.914: Got a new connection! 212s (process:2402): libfprint-virtual_device-DEBUG: 16:48:49.914: Got instructions of length 13 212s (process:2402): libfprint-virtual_device-DEBUG: 16:48:49.914: Received command SCAN print-id 212s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:49.914: Got a new connection! 212s (process:2402): libfprint-virtual_device-DEBUG: 16:48:49.914: Got instructions of length 8 212s (process:2402): libfprint-virtual_device-DEBUG: 16:48:49.914: Received command SLEEP 50 212s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:49.914: Got a new connection! 212s (process:2402): libfprint-virtual_device-DEBUG: 16:48:49.914: Got instructions of length 13 212s (process:2402): libfprint-virtual_device-DEBUG: 16:48:49.914: Received command SCAN print-id 212s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:49.914: Got a new connection! 212s (process:2402): libfprint-virtual_device-DEBUG: 16:48:49.914: Got instructions of length 7 212s (process:2402): libfprint-virtual_device-DEBUG: 16:48:49.914: Received command RETRY 2 212s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:49.914: Got a new connection! 212s (process:2402): libfprint-virtual_device-DEBUG: 16:48:49.914: Got instructions of length 15 212s (process:2402): libfprint-virtual_device-DEBUG: 16:48:49.914: Received command SCAN another-id 212s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:49.914: Got a new connection! 212s (process:2402): libfprint-virtual_device-DEBUG: 16:48:49.914: Got instructions of length 13 212s (process:2402): libfprint-virtual_device-DEBUG: 16:48:49.914: Received command SCAN print-id 212s (process:2402): libfprint-device-DEBUG: 16:48:49.914: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 212s (process:2402): libfprint-virtual_device-DEBUG: 16:48:49.914: Processing command SLEEP 50 212s (process:2402): libfprint-virtual_device-DEBUG: 16:48:49.914: Sleeping 50ms 212s (process:2402): libfprint-virtual_device-DEBUG: 16:48:49.965: Sleeping completed 212s (process:2402): libfprint-virtual_device-DEBUG: 16:48:49.965: Processing command SCAN print-id 212s (process:2402): libfprint-device-DEBUG: 16:48:49.965: Device reported finger status change: FP_FINGER_STATUS_NEEDED 212s (process:2402): libfprint-device-DEBUG: 16:48:49.965: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 212s (process:2402): libfprint-device-DEBUG: 16:48:49.965: Device reported finger status change: FP_FINGER_STATUS_NEEDED 212s (process:2402): libfprint-device-DEBUG: 16:48:49.965: Device reported enroll progress, reported 1 of 5 have been completed 212s (process:2402): libfprint-virtual_device-DEBUG: 16:48:49.965: Sleeping completed 212s (process:2402): libfprint-virtual_device-DEBUG: 16:48:49.965: Processing command SCAN print-id 212s (process:2402): libfprint-device-DEBUG: 16:48:49.965: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 212s (process:2402): libfprint-device-DEBUG: 16:48:49.965: Device reported finger status change: FP_FINGER_STATUS_NEEDED 212s (process:2402): libfprint-device-DEBUG: 16:48:49.965: Device reported enroll progress, reported 2 of 5 have been completed 212s (process:2402): libfprint-virtual_device-DEBUG: 16:48:49.965: Sleeping completed 212s (process:2402): libfprint-virtual_device-DEBUG: 16:48:49.965: Processing command RETRY 1 212s (process:2402): libfprint-device-DEBUG: 16:48:49.965: Device reported enroll progress, reported 2 of 5 have been completed 212s (process:2402): libfprint-virtual_device-DEBUG: 16:48:49.965: Sleeping completed 212s (process:2402): libfprint-virtual_device-DEBUG: 16:48:49.965: Processing command SCAN print-id 212s (process:2402): libfprint-device-DEBUG: 16:48:49.965: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 212s (process:2402): libfprint-device-DEBUG: 16:48:49.965: Device reported finger status change: FP_FINGER_STATUS_NEEDED 212s (process:2402): libfprint-device-DEBUG: 16:48:49.965: Device reported enroll progress, reported 3 of 5 have been completed 212s (process:2402): libfprint-virtual_device-DEBUG: 16:48:49.965: Processing command SLEEP 50 212s (process:2402): libfprint-virtual_device-DEBUG: 16:48:49.965: Sleeping 50ms 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.015: Sleeping completed 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.015: Processing command SCAN print-id 213s (process:2402): libfprint-device-DEBUG: 16:48:50.015: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 213s (process:2402): libfprint-device-DEBUG: 16:48:50.015: Device reported finger status change: FP_FINGER_STATUS_NEEDED 213s (process:2402): libfprint-device-DEBUG: 16:48:50.015: Device reported enroll progress, reported 4 of 5 have been completed 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.015: Sleeping completed 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.015: Processing command RETRY 2 213s (process:2402): libfprint-device-DEBUG: 16:48:50.015: Device reported enroll progress, reported 4 of 5 have been completed 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.015: Sleeping completed 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.015: Processing command SCAN another-id 213s (process:2402): libfprint-device-DEBUG: 16:48:50.015: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 213s (process:2402): libfprint-device-DEBUG: 16:48:50.015: Device reported enroll progress, reported 4 of 5 have been completed 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.015: Sleeping completed 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.015: Processing command SCAN print-id 213s (process:2402): libfprint-device-DEBUG: 16:48:50.015: Device reported finger status change: FP_FINGER_STATUS_NEEDED 213s (process:2402): libfprint-device-DEBUG: 16:48:50.015: Device reported enroll progress, reported 5 of 5 have been completed 213s (process:2402): libfprint-device-DEBUG: 16:48:50.015: Device reported enroll completion 213s (process:2402): libfprint-device-DEBUG: 16:48:50.015: Device reported finger status change: FP_FINGER_STATUS_NONE 213s (process:2402): libfprint-device-DEBUG: 16:48:50.015: Print for finger FP_FINGER_UNKNOWN enrolled 213s (process:2402): libfprint-device-DEBUG: 16:48:50.015: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 213s (process:2402): libfprint-device-DEBUG: 16:48:50.015: Updated temperature model after 0.10 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 213s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:50.016: Got a new connection! 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.016: Got instructions of length 5 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.016: Received command CONT 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.016: Processing command CONT 213s (process:2402): libfprint-device-DEBUG: 16:48:50.016: Device reported deletion completion 213s (process:2402): libfprint-device-DEBUG: 16:48:50.016: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 213s (process:2402): libfprint-device-DEBUG: 16:48:50.016: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 213s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:50.016: Got a new connection! 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.016: Got instructions of length 16 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.016: Received command SET_KEEP_ALIVE 0 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.016: Keep alive toggled: 0 213s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:50.016: Got a new connection! 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.016: Got instructions of length 19 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.016: Received command SET_ENROLL_STAGES 5 213s (process:2402): libfprint-device-DEBUG: 16:48:50.016: Device reported close completion 213s (process:2402): libfprint-device-DEBUG: 16:48:50.016: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 213s (process:2402): libfprint-device-DEBUG: 16:48:50.016: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 213s ok 213s test_enroll_verify_error (__main__.VirtualDeviceStorage.test_enroll_verify_error) ... (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.016: 101017211: ../libfprint/drivers/virtual-device.c:387 213s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:50.016: 101017219: ../libfprint/drivers/virtual-device-listener.c:153 213s (process:2402): libfprint-device-DEBUG: 16:48:50.016: Device reported open completion 213s (process:2402): libfprint-device-DEBUG: 16:48:50.016: Completing action FPI_DEVICE_ACTION_OPEN in idle! 213s (process:2402): libfprint-device-DEBUG: 16:48:50.016: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 213s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:50.016: Got a new connection! 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.016: Got instructions of length 14 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.016: Received command SCAN testprint 213s (process:2402): libfprint-device-DEBUG: 16:48:50.016: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.016: Processing command SCAN testprint 213s (process:2402): libfprint-device-DEBUG: 16:48:50.016: Device reported finger status change: FP_FINGER_STATUS_NEEDED 213s (process:2402): libfprint-device-DEBUG: 16:48:50.016: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 213s (process:2402): libfprint-device-DEBUG: 16:48:50.016: Device reported finger status change: FP_FINGER_STATUS_NEEDED 213s (process:2402): libfprint-device-DEBUG: 16:48:50.016: Device reported enroll progress, reported 1 of 5 have been completed 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.016: Sleeping completed 213s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:50.016: Got a new connection! 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.017: Got instructions of length 14 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.017: Received command SCAN testprint 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.017: Processing command SCAN testprint 213s (process:2402): libfprint-device-DEBUG: 16:48:50.017: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 213s (process:2402): libfprint-device-DEBUG: 16:48:50.017: Device reported finger status change: FP_FINGER_STATUS_NEEDED 213s (process:2402): libfprint-device-DEBUG: 16:48:50.017: Device reported enroll progress, reported 2 of 5 have been completed 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.017: Sleeping completed 213s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:50.017: Got a new connection! 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.017: Got instructions of length 14 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.017: Received command SCAN testprint 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.017: Processing command SCAN testprint 213s (process:2402): libfprint-device-DEBUG: 16:48:50.017: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 213s (process:2402): libfprint-device-DEBUG: 16:48:50.017: Device reported finger status change: FP_FINGER_STATUS_NEEDED 213s (process:2402): libfprint-device-DEBUG: 16:48:50.017: Device reported enroll progress, reported 3 of 5 have been completed 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.017: Sleeping completed 213s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:50.017: Got a new connection! 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.017: Got instructions of length 14 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.017: Received command SCAN testprint 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.017: Processing command SCAN testprint 213s (process:2402): libfprint-device-DEBUG: 16:48:50.017: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 213s (process:2402): libfprint-device-DEBUG: 16:48:50.017: Device reported finger status change: FP_FINGER_STATUS_NEEDED 213s (process:2402): libfprint-device-DEBUG: 16:48:50.017: Device reported enroll progress, reported 4 of 5 have been completed 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.017: Sleeping completed 213s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:50.017: Got a new connection! 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.017: Got instructions of length 14 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.017: Received command SCAN testprint 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.017: Processing command SCAN testprint 213s (process:2402): libfprint-device-DEBUG: 16:48:50.017: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 213s (process:2402): libfprint-device-DEBUG: 16:48:50.017: Device reported finger status change: FP_FINGER_STATUS_NEEDED 213s (process:2402): libfprint-device-DEBUG: 16:48:50.017: Device reported enroll progress, reported 5 of 5 have been completed 213s (process:2402): libfprint-device-DEBUG: 16:48:50.017: Device reported enroll completion 213s (process:2402): libfprint-device-DEBUG: 16:48:50.017: Device reported finger status change: FP_FINGER_STATUS_NONE 213s (process:2402): libfprint-device-DEBUG: 16:48:50.017: Print for finger FP_FINGER_LEFT_RING enrolled 213s (process:2402): libfprint-device-DEBUG: 16:48:50.017: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 213s (process:2402): libfprint-device-DEBUG: 16:48:50.017: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 213s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:50.017: Got a new connection! 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.017: Got instructions of length 7 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.017: Received command ERROR 0 213s (process:2402): libfprint-device-DEBUG: 16:48:50.017: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.017: Processing command ERROR 0 213s (process:2402): libfprint-device-DEBUG: 16:48:50.017: Device reported finger status change: FP_FINGER_STATUS_NEEDED 213s (process:2402): libfprint-device-DEBUG: 16:48:50.017: Device reported identify completion 213s (process:2402): libfprint-device-DEBUG: 16:48:50.017: Device reported finger status change: FP_FINGER_STATUS_NONE 213s (process:2402): libfprint-device-DEBUG: 16:48:50.017: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 213s (process:2402): libfprint-device-DEBUG: 16:48:50.017: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 213s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:50.017: Got a new connection! 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.017: Got instructions of length 5 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.018: Received command CONT 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.018: Processing command CONT 213s (process:2402): libfprint-device-DEBUG: 16:48:50.018: Device reported deletion completion 213s (process:2402): libfprint-device-DEBUG: 16:48:50.018: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 213s (process:2402): libfprint-device-DEBUG: 16:48:50.018: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 213s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:50.018: Got a new connection! 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.018: Got instructions of length 16 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.018: Received command SET_KEEP_ALIVE 0 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.018: Keep alive toggled: 0 213s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:50.018: Got a new connection! 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.018: Got instructions of length 19 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.018: Received command SET_ENROLL_STAGES 5 213s (process:2402): libfprint-device-DEBUG: 16:48:50.018: Device reported close completion 213s (process:2402): libfprint-device-DEBUG: 16:48:50.018: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 213s (process:2402): libfprint-device-DEBUG: 16:48:50.018: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 213s Enroll done 213s ok 213s test_enroll_verify_match (__main__.VirtualDeviceStorage.test_enroll_verify_match) ... (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.018: 101019059: ../libfprint/drivers/virtual-device.c:387 213s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:50.018: 101019067: ../libfprint/drivers/virtual-device-listener.c:153 213s (process:2402): libfprint-device-DEBUG: 16:48:50.018: Device reported open completion 213s (process:2402): libfprint-device-DEBUG: 16:48:50.018: Completing action FPI_DEVICE_ACTION_OPEN in idle! 213s (process:2402): libfprint-device-DEBUG: 16:48:50.018: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 213s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:50.018: Got a new connection! 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.018: Got instructions of length 14 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.018: Received command SCAN testprint 213s (process:2402): libfprint-device-DEBUG: 16:48:50.018: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.018: Processing command SCAN testprint 213s (process:2402): libfprint-device-DEBUG: 16:48:50.018: Device reported finger status change: FP_FINGER_STATUS_NEEDED 213s (process:2402): libfprint-device-DEBUG: 16:48:50.018: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 213s (process:2402): libfprint-device-DEBUG: 16:48:50.018: Device reported finger status change: FP_FINGER_STATUS_NEEDED 213s (process:2402): libfprint-device-DEBUG: 16:48:50.018: Device reported enroll progress, reported 1 of 5 have been completed 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.018: Sleeping completed 213s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:50.018: Got a new connection! 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.018: Got instructions of length 14 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.018: Received command SCAN testprint 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.018: Processing command SCAN testprint 213s (process:2402): libfprint-device-DEBUG: 16:48:50.018: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 213s (process:2402): libfprint-device-DEBUG: 16:48:50.018: Device reported finger status change: FP_FINGER_STATUS_NEEDED 213s (process:2402): libfprint-device-DEBUG: 16:48:50.018: Device reported enroll progress, reported 2 of 5 have been completed 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.018: Sleeping completed 213s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:50.018: Got a new connection! 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.018: Got instructions of length 14 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.018: Received command SCAN testprint 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.018: Processing command SCAN testprint 213s (process:2402): libfprint-device-DEBUG: 16:48:50.018: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 213s (process:2402): libfprint-device-DEBUG: 16:48:50.018: Device reported finger status change: FP_FINGER_STATUS_NEEDED 213s (process:2402): libfprint-device-DEBUG: 16:48:50.018: Device reported enroll progress, reported 3 of 5 have been completed 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.018: Sleeping completed 213s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:50.019: Got a new connection! 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.019: Got instructions of length 14 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.019: Received command SCAN testprint 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.019: Processing command SCAN testprint 213s (process:2402): libfprint-device-DEBUG: 16:48:50.019: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 213s (process:2402): libfprint-device-DEBUG: 16:48:50.019: Device reported finger status change: FP_FINGER_STATUS_NEEDED 213s (process:2402): libfprint-device-DEBUG: 16:48:50.019: Device reported enroll progress, reported 4 of 5 have been completed 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.019: Sleeping completed 213s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:50.019: Got a new connection! 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.019: Got instructions of length 14 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.019: Received command SCAN testprint 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.019: Processing command SCAN testprint 213s (process:2402): libfprint-device-DEBUG: 16:48:50.019: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 213s (process:2402): libfprint-device-DEBUG: 16:48:50.019: Device reported finger status change: FP_FINGER_STATUS_NEEDED 213s (process:2402): libfprint-device-DEBUG: 16:48:50.019: Device reported enroll progress, reported 5 of 5 have been completed 213s (process:2402): libfprint-device-DEBUG: 16:48:50.019: Device reported enroll completion 213s (process:2402): libfprint-device-DEBUG: 16:48:50.019: Device reported finger status change: FP_FINGER_STATUS_NONE 213s (process:2402): libfprint-device-DEBUG: 16:48:50.019: Print for finger FP_FINGER_LEFT_THUMB enrolled 213s (process:2402): libfprint-device-DEBUG: 16:48:50.019: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 213s (process:2402): libfprint-device-DEBUG: 16:48:50.019: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 213s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:50.019: Got a new connection! 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.020: Got instructions of length 14 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.020: Received command SCAN testprint 213s (process:2402): libfprint-device-DEBUG: 16:48:50.020: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.020: Processing command SCAN testprint 213s (process:2402): libfprint-device-DEBUG: 16:48:50.020: Device reported finger status change: FP_FINGER_STATUS_NEEDED 213s (process:2402): libfprint-device-DEBUG: 16:48:50.020: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 213s (process:2402): libfprint-virtual_device_storage-DEBUG: 16:48:50.020: Trying to identify print 'testprint' against a gallery of 1 prints 213s (process:2402): libfprint-device-DEBUG: 16:48:50.020: Device reported identify result 213s (process:2402): libfprint-device-DEBUG: 16:48:50.020: Device reported finger status change: FP_FINGER_STATUS_NEEDED 213s (process:2402): libfprint-device-DEBUG: 16:48:50.020: Device reported identify completion 213s (process:2402): libfprint-device-DEBUG: 16:48:50.020: Device reported finger status change: FP_FINGER_STATUS_NONE 213s (process:2402): libfprint-device-DEBUG: 16:48:50.020: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 213s (process:2402): libfprint-device-DEBUG: 16:48:50.020: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 213s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:50.020: Got a new connection! 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.021: Got instructions of length 5 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.021: Received command CONT 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.021: Processing command CONT 213s (process:2402): libfprint-device-DEBUG: 16:48:50.021: Device reported deletion completion 213s (process:2402): libfprint-device-DEBUG: 16:48:50.021: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 213s (process:2402): libfprint-device-DEBUG: 16:48:50.021: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 213s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:50.021: Got a new connection! 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.021: Got instructions of length 16 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.021: Received command SET_KEEP_ALIVE 0 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.021: Keep alive toggled: 0 213s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:50.021: Got a new connection! 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.021: Got instructions of length 19 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.021: Received command SET_ENROLL_STAGES 5 213s (process:2402): libfprint-device-DEBUG: 16:48:50.022: Device reported close completion 213s (process:2402): libfprint-device-DEBUG: 16:48:50.022: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 213s (process:2402): libfprint-device-DEBUG: 16:48:50.022: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 213s Enroll done 213s ok 213s test_enroll_verify_no_match (__main__.VirtualDeviceStorage.test_enroll_verify_no_match) ... (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.022: 101023152: ../libfprint/drivers/virtual-device.c:387 213s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:50.022: 101023199: ../libfprint/drivers/virtual-device-listener.c:153 213s (process:2402): libfprint-device-DEBUG: 16:48:50.022: Device reported open completion 213s (process:2402): libfprint-device-DEBUG: 16:48:50.022: Completing action FPI_DEVICE_ACTION_OPEN in idle! 213s (process:2402): libfprint-device-DEBUG: 16:48:50.022: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 213s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:50.022: Got a new connection! 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.022: Got instructions of length 14 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.022: Received command SCAN testprint 213s (process:2402): libfprint-device-DEBUG: 16:48:50.023: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.023: Processing command SCAN testprint 213s (process:2402): libfprint-device-DEBUG: 16:48:50.023: Device reported finger status change: FP_FINGER_STATUS_NEEDED 213s (process:2402): libfprint-device-DEBUG: 16:48:50.023: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 213s (process:2402): libfprint-device-DEBUG: 16:48:50.023: Device reported finger status change: FP_FINGER_STATUS_NEEDED 213s (process:2402): libfprint-device-DEBUG: 16:48:50.023: Device reported enroll progress, reported 1 of 5 have been completed 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.023: Sleeping completed 213s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:50.023: Got a new connection! 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.023: Got instructions of length 14 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.023: Received command SCAN testprint 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.023: Processing command SCAN testprint 213s (process:2402): libfprint-device-DEBUG: 16:48:50.023: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 213s (process:2402): libfprint-device-DEBUG: 16:48:50.023: Device reported finger status change: FP_FINGER_STATUS_NEEDED 213s (process:2402): libfprint-device-DEBUG: 16:48:50.023: Device reported enroll progress, reported 2 of 5 have been completed 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.023: Sleeping completed 213s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:50.024: Got a new connection! 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.024: Got instructions of length 14 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.024: Received command SCAN testprint 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.024: Processing command SCAN testprint 213s (process:2402): libfprint-device-DEBUG: 16:48:50.024: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 213s (process:2402): libfprint-device-DEBUG: 16:48:50.024: Device reported finger status change: FP_FINGER_STATUS_NEEDED 213s (process:2402): libfprint-device-DEBUG: 16:48:50.024: Device reported enroll progress, reported 3 of 5 have been completed 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.024: Sleeping completed 213s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:50.024: Got a new connection! 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.024: Got instructions of length 14 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.024: Received command SCAN testprint 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.024: Processing command SCAN testprint 213s (process:2402): libfprint-device-DEBUG: 16:48:50.024: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 213s (process:2402): libfprint-device-DEBUG: 16:48:50.024: Device reported finger status change: FP_FINGER_STATUS_NEEDED 213s (process:2402): libfprint-device-DEBUG: 16:48:50.024: Device reported enroll progress, reported 4 of 5 have been completed 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.024: Sleeping completed 213s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:50.024: Got a new connection! 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.025: Got instructions of length 14 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.025: Received command SCAN testprint 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.025: Processing command SCAN testprint 213s (process:2402): libfprint-device-DEBUG: 16:48:50.025: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 213s (process:2402): libfprint-device-DEBUG: 16:48:50.025: Device reported finger status change: FP_FINGER_STATUS_NEEDED 213s (process:2402): libfprint-device-DEBUG: 16:48:50.025: Device reported enroll progress, reported 5 of 5 have been completed 213s (process:2402): libfprint-device-DEBUG: 16:48:50.025: Device reported enroll completion 213s (process:2402): libfprint-device-DEBUG: 16:48:50.025: Device reported finger status change: FP_FINGER_STATUS_NONE 213s (process:2402): libfprint-device-DEBUG: 16:48:50.025: Print for finger FP_FINGER_LEFT_RING enrolled 213s (process:2402): libfprint-device-DEBUG: 16:48:50.025: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 213s (process:2402): libfprint-device-DEBUG: 16:48:50.025: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 213s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:50.025: Got a new connection! 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.025: Got instructions of length 18 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.025: Received command SCAN not-testprint 213s (process:2402): libfprint-device-DEBUG: 16:48:50.025: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.025: Processing command SCAN not-testprint 213s (process:2402): libfprint-device-DEBUG: 16:48:50.025: Device reported finger status change: FP_FINGER_STATUS_NEEDED 213s (process:2402): libfprint-device-DEBUG: 16:48:50.026: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 213s (process:2402): libfprint-virtual_device_storage-DEBUG: 16:48:50.026: Trying to identify print 'not-testprint' against a gallery of 1 prints 213s (process:2402): libfprint-device-DEBUG: 16:48:50.026: Device reported identify result 213s (process:2402): libfprint-device-DEBUG: 16:48:50.026: Device reported finger status change: FP_FINGER_STATUS_NEEDED 213s (process:2402): libfprint-device-DEBUG: 16:48:50.026: Device reported identify completion 213s (process:2402): libfprint-device-DEBUG: 16:48:50.026: Device reported finger status change: FP_FINGER_STATUS_NONE 213s (process:2402): libfprint-device-DEBUG: 16:48:50.026: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 213s (process:2402): libfprint-device-DEBUG: 16:48:50.026: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 213s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:50.026: Got a new connection! 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.026: Got instructions of length 5 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.026: Received command CONT 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.026: Processing command CONT 213s (process:2402): libfprint-device-DEBUG: 16:48:50.026: Device reported deletion completion 213s (process:2402): libfprint-device-DEBUG: 16:48:50.026: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 213s (process:2402): libfprint-device-DEBUG: 16:48:50.026: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 213s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:50.026: Got a new connection! 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.026: Got instructions of length 16 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.026: Received command SET_KEEP_ALIVE 0 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.026: Keep alive toggled: 0 213s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:50.027: Got a new connection! 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.027: Got instructions of length 19 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.027: Received command SET_ENROLL_STAGES 5 213s (process:2402): libfprint-device-DEBUG: 16:48:50.027: Device reported close completion 213s (process:2402): libfprint-device-DEBUG: 16:48:50.027: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 213s (process:2402): libfprint-device-DEBUG: 16:48:50.027: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 213s Enroll done 213s ok 213s test_enroll_verify_retry (__main__.VirtualDeviceStorage.test_enroll_verify_retry) ... (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.027: 101027902: ../libfprint/drivers/virtual-device.c:387 213s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:50.027: 101027910: ../libfprint/drivers/virtual-device-listener.c:153 213s (process:2402): libfprint-device-DEBUG: 16:48:50.027: Device reported open completion 213s (process:2402): libfprint-device-DEBUG: 16:48:50.027: Completing action FPI_DEVICE_ACTION_OPEN in idle! 213s (process:2402): libfprint-device-DEBUG: 16:48:50.027: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 213s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:50.027: Got a new connection! 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.027: Got instructions of length 7 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.027: Received command RETRY 1 213s (process:2402): libfprint-device-DEBUG: 16:48:50.027: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.027: Processing command RETRY 1 213s (process:2402): libfprint-device-DEBUG: 16:48:50.027: Device reported finger status change: FP_FINGER_STATUS_NEEDED 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.027: Virtual device scan failed with error: The swipe was too short, please try again. 213s (process:2402): libfprint-device-DEBUG: 16:48:50.027: Device reported verify result 213s (process:2402): libfprint-device-DEBUG: 16:48:50.027: Device reported verify completion 213s (process:2402): libfprint-device-DEBUG: 16:48:50.027: Device reported finger status change: FP_FINGER_STATUS_NONE 213s (process:2402): libfprint-device-DEBUG: 16:48:50.027: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 213s (process:2402): libfprint-device-DEBUG: 16:48:50.027: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 213s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:50.027: Got a new connection! 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.027: Got instructions of length 5 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.027: Received command CONT 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.027: Processing command CONT 213s (process:2402): libfprint-device-DEBUG: 16:48:50.027: Device reported deletion completion 213s (process:2402): libfprint-device-DEBUG: 16:48:50.027: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 213s (process:2402): libfprint-device-DEBUG: 16:48:50.027: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 213s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:50.027: Got a new connection! 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.027: Got instructions of length 16 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.027: Received command SET_KEEP_ALIVE 0 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.027: Keep alive toggled: 0 213s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:50.028: Got a new connection! 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.028: Got instructions of length 19 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.028: Received command SET_ENROLL_STAGES 5 213s (process:2402): libfprint-device-DEBUG: 16:48:50.028: Device reported close completion 213s (process:2402): libfprint-device-DEBUG: 16:48:50.028: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 213s (process:2402): libfprint-device-DEBUG: 16:48:50.028: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 213s ok 213s test_enroll_verify_script (__main__.VirtualDeviceStorage.test_enroll_verify_script) ... (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.028: 101028854: ../libfprint/drivers/virtual-device.c:387 213s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:50.028: 101028862: ../libfprint/drivers/virtual-device-listener.c:153 213s (process:2402): libfprint-device-DEBUG: 16:48:50.028: Device reported open completion 213s (process:2402): libfprint-device-DEBUG: 16:48:50.028: Completing action FPI_DEVICE_ACTION_OPEN in idle! 213s (process:2402): libfprint-device-DEBUG: 16:48:50.028: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 213s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:50.028: Got a new connection! 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.028: Got instructions of length 19 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.028: Received command SET_ENROLL_STAGES 8 213s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:50.028: Got a new connection! 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.028: Got instructions of length 13 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.028: Received command SCAN print-id 213s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:50.028: Got a new connection! 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.028: Got instructions of length 13 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.028: Received command SCAN print-id 213s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:50.028: Got a new connection! 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.028: Got instructions of length 7 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.028: Received command RETRY 1 213s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:50.028: Got a new connection! 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.028: Got instructions of length 13 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.028: Received command SCAN print-id 213s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:50.028: Got a new connection! 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.028: Got instructions of length 7 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.028: Received command RETRY 3 213s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:50.028: Got a new connection! 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.028: Got instructions of length 13 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.028: Received command SCAN print-id 213s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:50.028: Got a new connection! 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.028: Got instructions of length 7 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.028: Received command RETRY 2 213s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:50.029: Got a new connection! 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.029: Got instructions of length 13 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.029: Received command SCAN print-id 213s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:50.029: Got a new connection! 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.029: Got instructions of length 8 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.029: Received command SLEEP 10 213s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:50.029: Got a new connection! 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.029: Got instructions of length 8 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.029: Received command SLEEP 20 213s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:50.029: Got a new connection! 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.029: Got instructions of length 7 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.029: Received command RETRY 0 213s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:50.029: Got a new connection! 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.029: Got instructions of length 7 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.029: Received command RETRY 3 213s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:50.029: Got a new connection! 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.029: Got instructions of length 13 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.029: Received command SCAN print-id 213s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:50.029: Got a new connection! 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.029: Got instructions of length 15 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.029: Received command SCAN another-id 213s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:50.029: Got a new connection! 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.029: Got instructions of length 13 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.029: Received command SCAN print-id 213s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:50.029: Got a new connection! 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.029: Got instructions of length 13 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.029: Received command SCAN print-id 213s (process:2402): libfprint-device-DEBUG: 16:48:50.029: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.029: Processing command SCAN print-id 213s (process:2402): libfprint-device-DEBUG: 16:48:50.029: Device reported finger status change: FP_FINGER_STATUS_NEEDED 213s (process:2402): libfprint-device-DEBUG: 16:48:50.029: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 213s (process:2402): libfprint-device-DEBUG: 16:48:50.029: Device reported finger status change: FP_FINGER_STATUS_NEEDED 213s (process:2402): libfprint-device-DEBUG: 16:48:50.029: Device reported enroll progress, reported 1 of 8 have been completed 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.029: Sleeping completed 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.029: Processing command SCAN print-id 213s (process:2402): libfprint-device-DEBUG: 16:48:50.029: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 213s (process:2402): libfprint-device-DEBUG: 16:48:50.029: Device reported finger status change: FP_FINGER_STATUS_NEEDED 213s (process:2402): libfprint-device-DEBUG: 16:48:50.029: Device reported enroll progress, reported 2 of 8 have been completed 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.029: Sleeping completed 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.029: Processing command RETRY 1 213s (process:2402): libfprint-device-DEBUG: 16:48:50.029: Device reported enroll progress, reported 2 of 8 have been completed 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.029: Sleeping completed 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.029: Processing command SCAN print-id 213s (process:2402): libfprint-device-DEBUG: 16:48:50.029: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 213s (process:2402): libfprint-device-DEBUG: 16:48:50.029: Device reported finger status change: FP_FINGER_STATUS_NEEDED 213s (process:2402): libfprint-device-DEBUG: 16:48:50.029: Device reported enroll progress, reported 3 of 8 have been completed 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.029: Sleeping completed 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.029: Processing command RETRY 3 213s (process:2402): libfprint-device-DEBUG: 16:48:50.029: Device reported enroll progress, reported 3 of 8 have been completed 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.029: Sleeping completed 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.030: Processing command SCAN print-id 213s (process:2402): libfprint-device-DEBUG: 16:48:50.030: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 213s (process:2402): libfprint-device-DEBUG: 16:48:50.030: Device reported finger status change: FP_FINGER_STATUS_NEEDED 213s (process:2402): libfprint-device-DEBUG: 16:48:50.030: Device reported enroll progress, reported 4 of 8 have been completed 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.030: Sleeping completed 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.030: Processing command RETRY 2 213s (process:2402): libfprint-device-DEBUG: 16:48:50.030: Device reported enroll progress, reported 4 of 8 have been completed 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.030: Sleeping completed 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.030: Processing command SCAN print-id 213s (process:2402): libfprint-device-DEBUG: 16:48:50.030: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 213s (process:2402): libfprint-device-DEBUG: 16:48:50.030: Device reported finger status change: FP_FINGER_STATUS_NEEDED 213s (process:2402): libfprint-device-DEBUG: 16:48:50.030: Device reported enroll progress, reported 5 of 8 have been completed 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.030: Processing command SLEEP 10 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.030: Sleeping 10ms 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.040: Sleeping completed 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.040: Processing command SLEEP 20 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.040: Sleeping 20ms 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.060: Sleeping completed 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.060: Processing command RETRY 0 213s (process:2402): libfprint-device-DEBUG: 16:48:50.060: Device reported enroll progress, reported 5 of 8 have been completed 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.060: Sleeping completed 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.060: Processing command RETRY 3 213s (process:2402): libfprint-device-DEBUG: 16:48:50.060: Device reported enroll progress, reported 5 of 8 have been completed 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.060: Sleeping completed 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.060: Processing command SCAN print-id 213s (process:2402): libfprint-device-DEBUG: 16:48:50.060: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 213s (process:2402): libfprint-device-DEBUG: 16:48:50.060: Device reported finger status change: FP_FINGER_STATUS_NEEDED 213s (process:2402): libfprint-device-DEBUG: 16:48:50.060: Device reported enroll progress, reported 6 of 8 have been completed 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.060: Sleeping completed 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.060: Processing command SCAN another-id 213s (process:2402): libfprint-device-DEBUG: 16:48:50.060: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 213s (process:2402): libfprint-device-DEBUG: 16:48:50.060: Device reported enroll progress, reported 6 of 8 have been completed 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.060: Sleeping completed 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.060: Processing command SCAN print-id 213s (process:2402): libfprint-device-DEBUG: 16:48:50.060: Device reported finger status change: FP_FINGER_STATUS_NEEDED 213s (process:2402): libfprint-device-DEBUG: 16:48:50.060: Device reported enroll progress, reported 7 of 8 have been completed 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.060: Sleeping completed 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.060: Processing command SCAN print-id 213s (process:2402): libfprint-device-DEBUG: 16:48:50.060: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 213s (process:2402): libfprint-device-DEBUG: 16:48:50.060: Device reported finger status change: FP_FINGER_STATUS_NEEDED 213s (process:2402): libfprint-device-DEBUG: 16:48:50.060: Device reported enroll progress, reported 8 of 8 have been completed 213s (process:2402): libfprint-device-DEBUG: 16:48:50.060: Device reported enroll completion 213s (process:2402): libfprint-device-DEBUG: 16:48:50.060: Device reported finger status change: FP_FINGER_STATUS_NONE 213s (process:2402): libfprint-device-DEBUG: 16:48:50.060: Print for finger FP_FINGER_UNKNOWN enrolled 213s (process:2402): libfprint-device-DEBUG: 16:48:50.060: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 213s (process:2402): libfprint-device-DEBUG: 16:48:50.060: Updated temperature model after 0.03 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 213s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:50.060: Got a new connection! 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.060: Got instructions of length 7 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.060: Received command RETRY 2 213s (process:2402): libfprint-device-DEBUG: 16:48:50.060: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.060: Processing command RETRY 2 213s (process:2402): libfprint-device-DEBUG: 16:48:50.060: Device reported finger status change: FP_FINGER_STATUS_NEEDED 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.060: Virtual device scan failed with error: The finger was not centered properly, please try again. 213s (process:2402): libfprint-device-DEBUG: 16:48:50.060: Device reported verify result 213s (process:2402): libfprint-device-DEBUG: 16:48:50.060: Device reported verify completion 213s (process:2402): libfprint-device-DEBUG: 16:48:50.060: Device reported finger status change: FP_FINGER_STATUS_NONE 213s (process:2402): libfprint-device-DEBUG: 16:48:50.060: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 213s (process:2402): libfprint-device-DEBUG: 16:48:50.060: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 213s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:50.060: Got a new connection! 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.060: Got instructions of length 8 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.060: Received command SLEEP 50 213s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:50.061: Got a new connection! 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.061: Got instructions of length 7 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.061: Received command RETRY 1 213s (process:2402): libfprint-device-DEBUG: 16:48:50.061: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.061: Processing command SLEEP 50 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.061: Sleeping 50ms 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.111: Sleeping completed 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.111: Processing command RETRY 1 213s (process:2402): libfprint-device-DEBUG: 16:48:50.111: Device reported finger status change: FP_FINGER_STATUS_NEEDED 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.111: Virtual device scan failed with error: The swipe was too short, please try again. 213s (process:2402): libfprint-device-DEBUG: 16:48:50.111: Device reported verify result 213s (process:2402): libfprint-device-DEBUG: 16:48:50.111: Device reported verify completion 213s (process:2402): libfprint-device-DEBUG: 16:48:50.111: Device reported finger status change: FP_FINGER_STATUS_NONE 213s (process:2402): libfprint-device-DEBUG: 16:48:50.111: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 213s (process:2402): libfprint-device-DEBUG: 16:48:50.111: Updated temperature model after 0.05 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 213s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:50.111: Got a new connection! 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.111: Got instructions of length 15 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.111: Received command SCAN another-id 213s (process:2402): libfprint-device-DEBUG: 16:48:50.111: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.111: Processing command SCAN another-id 213s (process:2402): libfprint-device-DEBUG: 16:48:50.111: Device reported finger status change: FP_FINGER_STATUS_NEEDED 213s (process:2402): libfprint-device-DEBUG: 16:48:50.111: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.111: Virtual device scanned print another-id 213s (process:2402): libfprint-device-DEBUG: 16:48:50.111: Device reported verify result 213s (process:2402): libfprint-device-DEBUG: 16:48:50.111: Device reported finger status change: FP_FINGER_STATUS_NEEDED 213s (process:2402): libfprint-device-DEBUG: 16:48:50.111: Device reported verify completion 213s (process:2402): libfprint-device-DEBUG: 16:48:50.111: Device reported finger status change: FP_FINGER_STATUS_NONE 213s (process:2402): libfprint-device-DEBUG: 16:48:50.111: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 213s (process:2402): libfprint-device-DEBUG: 16:48:50.111: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 213s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:50.112: Got a new connection! 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.112: Got instructions of length 13 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.112: Received command SCAN print-id 213s (process:2402): libfprint-device-DEBUG: 16:48:50.112: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.112: Processing command SCAN print-id 213s (process:2402): libfprint-device-DEBUG: 16:48:50.112: Device reported finger status change: FP_FINGER_STATUS_NEEDED 213s (process:2402): libfprint-device-DEBUG: 16:48:50.112: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.112: Virtual device scanned print print-id 213s (process:2402): libfprint-device-DEBUG: 16:48:50.112: Device reported verify result 213s (process:2402): libfprint-device-DEBUG: 16:48:50.112: Device reported finger status change: FP_FINGER_STATUS_NEEDED 213s (process:2402): libfprint-device-DEBUG: 16:48:50.112: Device reported verify completion 213s (process:2402): libfprint-device-DEBUG: 16:48:50.112: Device reported finger status change: FP_FINGER_STATUS_NONE 213s (process:2402): libfprint-device-DEBUG: 16:48:50.112: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 213s (process:2402): libfprint-device-DEBUG: 16:48:50.112: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 213s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:50.112: Got a new connection! 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.112: Got instructions of length 5 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.112: Received command CONT 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.112: Processing command CONT 213s (process:2402): libfprint-device-DEBUG: 16:48:50.112: Device reported deletion completion 213s (process:2402): libfprint-device-DEBUG: 16:48:50.112: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 213s (process:2402): libfprint-device-DEBUG: 16:48:50.112: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 213s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:50.112: Got a new connection! 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.112: Got instructions of length 16 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.112: Received command SET_KEEP_ALIVE 0 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.112: Keep alive toggled: 0 213s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:50.112: Got a new connection! 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.112: Got instructions of length 19 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.112: Received command SET_ENROLL_STAGES 5 213s (process:2402): libfprint-device-DEBUG: 16:48:50.112: Device reported close completion 213s (process:2402): libfprint-device-DEBUG: 16:48:50.112: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 213s (process:2402): libfprint-device-DEBUG: 16:48:50.112: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 213s ok 213s test_enroll_with_retry (__main__.VirtualDeviceStorage.test_enroll_with_retry) ... (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.112: 101113462: ../libfprint/drivers/virtual-device.c:387 213s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:50.112: 101113470: ../libfprint/drivers/virtual-device-listener.c:153 213s (process:2402): libfprint-device-DEBUG: 16:48:50.112: Device reported open completion 213s (process:2402): libfprint-device-DEBUG: 16:48:50.112: Completing action FPI_DEVICE_ACTION_OPEN in idle! 213s (process:2402): libfprint-device-DEBUG: 16:48:50.112: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 213s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:50.112: Got a new connection! 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.113: Got instructions of length 14 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.113: Received command SCAN testprint 213s (process:2402): libfprint-device-DEBUG: 16:48:50.113: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.113: Processing command SCAN testprint 213s (process:2402): libfprint-device-DEBUG: 16:48:50.113: Device reported finger status change: FP_FINGER_STATUS_NEEDED 213s (process:2402): libfprint-device-DEBUG: 16:48:50.113: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 213s (process:2402): libfprint-device-DEBUG: 16:48:50.113: Device reported finger status change: FP_FINGER_STATUS_NEEDED 213s (process:2402): libfprint-device-DEBUG: 16:48:50.113: Device reported enroll progress, reported 1 of 5 have been completed 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.113: Sleeping completed 213s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:50.113: Got a new connection! 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.113: Got instructions of length 14 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.113: Received command SCAN testprint 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.113: Processing command SCAN testprint 213s (process:2402): libfprint-device-DEBUG: 16:48:50.113: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 213s (process:2402): libfprint-device-DEBUG: 16:48:50.113: Device reported finger status change: FP_FINGER_STATUS_NEEDED 213s (process:2402): libfprint-device-DEBUG: 16:48:50.113: Device reported enroll progress, reported 2 of 5 have been completed 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.113: Sleeping completed 213s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:50.113: Got a new connection! 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.113: Got instructions of length 7 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.113: Received command RETRY 1 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.113: Processing command RETRY 1 213s (process:2402): libfprint-device-DEBUG: 16:48:50.113: Device reported enroll progress, reported 2 of 5 have been completed 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.113: Sleeping completed 213s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:50.113: Got a new connection! 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.113: Got instructions of length 14 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.113: Received command SCAN testprint 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.113: Processing command SCAN testprint 213s (process:2402): libfprint-device-DEBUG: 16:48:50.113: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 213s (process:2402): libfprint-device-DEBUG: 16:48:50.113: Device reported finger status change: FP_FINGER_STATUS_NEEDED 213s (process:2402): libfprint-device-DEBUG: 16:48:50.113: Device reported enroll progress, reported 3 of 5 have been completed 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.113: Sleeping completed 213s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:50.113: Got a new connection! 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.113: Got instructions of length 14 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.113: Received command SCAN testprint 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.113: Processing command SCAN testprint 213s (process:2402): libfprint-device-DEBUG: 16:48:50.113: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 213s (process:2402): libfprint-device-DEBUG: 16:48:50.113: Device reported finger status change: FP_FINGER_STATUS_NEEDED 213s (process:2402): libfprint-device-DEBUG: 16:48:50.113: Device reported enroll progress, reported 4 of 5 have been completed 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.113: Sleeping completed 213s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:50.113: Got a new connection! 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.113: Got instructions of length 14 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.113: Received command SCAN testprint 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.113: Processing command SCAN testprint 213s (process:2402): libfprint-device-DEBUG: 16:48:50.113: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 213s (process:2402): libfprint-device-DEBUG: 16:48:50.113: Device reported finger status change: FP_FINGER_STATUS_NEEDED 213s (process:2402): libfprint-device-DEBUG: 16:48:50.113: Device reported enroll progress, reported 5 of 5 have been completed 213s (process:2402): libfprint-device-DEBUG: 16:48:50.113: Device reported enroll completion 213s (process:2402): libfprint-device-DEBUG: 16:48:50.113: Device reported finger status change: FP_FINGER_STATUS_NONE 213s (process:2402): libfprint-device-DEBUG: 16:48:50.113: Print for finger FP_FINGER_LEFT_LITTLE enrolled 213s (process:2402): libfprint-device-DEBUG: 16:48:50.113: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 213s (process:2402): libfprint-device-DEBUG: 16:48:50.113: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 213s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:50.114: Got a new connection! 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.114: Got instructions of length 5 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.114: Received command CONT 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.114: Processing command CONT 213s (process:2402): libfprint-device-DEBUG: 16:48:50.114: Device reported deletion completion 213s (process:2402): libfprint-device-DEBUG: 16:48:50.114: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 213s (process:2402): libfprint-device-DEBUG: 16:48:50.114: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 213s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:50.114: Got a new connection! 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.114: Got instructions of length 16 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.114: Received command SET_KEEP_ALIVE 0 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.114: Keep alive toggled: 0 213s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:50.114: Got a new connection! 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.114: Got instructions of length 19 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.114: Received command SET_ENROLL_STAGES 5 213s (process:2402): libfprint-device-DEBUG: 16:48:50.114: Device reported close completion 213s (process:2402): libfprint-device-DEBUG: 16:48:50.114: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 213s (process:2402): libfprint-device-DEBUG: 16:48:50.114: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 213s Enroll done 213s ok 213s test_finger_status (__main__.VirtualDeviceStorage.test_finger_status) ... (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.114: 101115201: ../libfprint/drivers/virtual-device.c:387 213s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:50.114: 101115209: ../libfprint/drivers/virtual-device-listener.c:153 213s (process:2402): libfprint-device-DEBUG: 16:48:50.114: Device reported open completion 213s (process:2402): libfprint-device-DEBUG: 16:48:50.114: Completing action FPI_DEVICE_ACTION_OPEN in idle! 213s (process:2402): libfprint-device-DEBUG: 16:48:50.114: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 213s (process:2402): libfprint-device-DEBUG: 16:48:50.114: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 213s (process:2402): libfprint-device-DEBUG: 16:48:50.114: Device reported finger status change: FP_FINGER_STATUS_NEEDED 213s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:50.114: Got a new connection! 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.114: Got instructions of length 8 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.114: Received command FINGER 1 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.114: Processing command FINGER 1 213s (process:2402): libfprint-device-DEBUG: 16:48:50.114: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 213s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:50.114: Got a new connection! 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.114: Got instructions of length 8 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.114: Received command FINGER 0 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.114: Processing command FINGER 0 213s (process:2402): libfprint-device-DEBUG: 16:48:50.114: Device reported finger status change: FP_FINGER_STATUS_NEEDED 213s (process:2402): libfprint-device-DEBUG: 16:48:50.114: Idle cancelling on ongoing operation! 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.114: Got cancellation! 213s (process:2402): libfprint-device-DEBUG: 16:48:50.114: Device reported identify completion 213s (process:2402): libfprint-device-DEBUG: 16:48:50.114: Device reported finger status change: FP_FINGER_STATUS_NONE 213s (process:2402): libfprint-device-DEBUG: 16:48:50.114: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 213s (process:2402): libfprint-device-DEBUG: 16:48:50.115: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 213s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:50.115: Got a new connection! 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.115: Got instructions of length 5 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.115: Received command CONT 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.115: Processing command CONT 213s (process:2402): libfprint-device-DEBUG: 16:48:50.115: Device reported deletion completion 213s (process:2402): libfprint-device-DEBUG: 16:48:50.115: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 213s (process:2402): libfprint-device-DEBUG: 16:48:50.115: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 213s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:50.115: Got a new connection! 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.115: Got instructions of length 16 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.115: Received command SET_KEEP_ALIVE 0 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.115: Keep alive toggled: 0 213s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:50.115: Got a new connection! 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.115: Got instructions of length 19 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.115: Received command SET_ENROLL_STAGES 5 213s (process:2402): libfprint-device-DEBUG: 16:48:50.115: Device reported close completion 213s (process:2402): libfprint-device-DEBUG: 16:48:50.115: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 213s (process:2402): libfprint-device-DEBUG: 16:48:50.115: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 213s ok 213s test_finger_status_after_sleep (__main__.VirtualDeviceStorage.test_finger_status_after_sleep) ... (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.115: 101116497: ../libfprint/drivers/virtual-device.c:387 213s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:50.115: 101116523: ../libfprint/drivers/virtual-device-listener.c:153 213s (process:2402): libfprint-device-DEBUG: 16:48:50.115: Device reported open completion 213s (process:2402): libfprint-device-DEBUG: 16:48:50.115: Completing action FPI_DEVICE_ACTION_OPEN in idle! 213s (process:2402): libfprint-device-DEBUG: 16:48:50.115: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 213s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:50.116: Got a new connection! 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.116: Got instructions of length 8 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.116: Received command SLEEP 10 213s (process:2402): libfprint-device-DEBUG: 16:48:50.116: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.116: Processing command SLEEP 10 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.116: Sleeping 10ms 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.126: Sleeping completed 213s (process:2402): libfprint-device-DEBUG: 16:48:50.126: Device reported finger status change: FP_FINGER_STATUS_NEEDED 213s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:50.126: Got a new connection! 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.126: Got instructions of length 8 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.126: Received command FINGER 1 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.127: Processing command FINGER 1 213s (process:2402): libfprint-device-DEBUG: 16:48:50.127: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 213s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:50.127: Got a new connection! 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.127: Got instructions of length 8 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.127: Received command FINGER 0 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.127: Processing command FINGER 0 213s (process:2402): libfprint-device-DEBUG: 16:48:50.127: Device reported finger status change: FP_FINGER_STATUS_NEEDED 213s (process:2402): libfprint-device-DEBUG: 16:48:50.127: Idle cancelling on ongoing operation! 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.127: Got cancellation! 213s (process:2402): libfprint-device-DEBUG: 16:48:50.127: Device reported identify completion 213s (process:2402): libfprint-device-DEBUG: 16:48:50.127: Device reported finger status change: FP_FINGER_STATUS_NONE 213s (process:2402): libfprint-device-DEBUG: 16:48:50.127: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 213s (process:2402): libfprint-device-DEBUG: 16:48:50.127: Updated temperature model after 0.01 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 213s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:50.258: Got a new connection! 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.259: Got instructions of length 5 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.259: Received command CONT 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.259: Processing command CONT 213s (process:2402): libfprint-device-DEBUG: 16:48:50.259: Device reported deletion completion 213s (process:2402): libfprint-device-DEBUG: 16:48:50.259: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 213s (process:2402): libfprint-device-DEBUG: 16:48:50.259: Updated temperature model after 0.13 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 213s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:50.259: Got a new connection! 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.259: Got instructions of length 16 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.259: Received command SET_KEEP_ALIVE 0 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.259: Keep alive toggled: 0 213s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:50.259: Got a new connection! 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.259: Got instructions of length 19 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.259: Received command SET_ENROLL_STAGES 5 213s (process:2402): libfprint-device-DEBUG: 16:48:50.259: Device reported close completion 213s (process:2402): libfprint-device-DEBUG: 16:48:50.259: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 213s (process:2402): libfprint-device-DEBUG: 16:48:50.259: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 213s ok 213s test_identify_match (__main__.VirtualDeviceStorage.test_identify_match) ... (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.260: 101260715: ../libfprint/drivers/virtual-device.c:387 213s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:50.260: 101260743: ../libfprint/drivers/virtual-device-listener.c:153 213s (process:2402): libfprint-device-DEBUG: 16:48:50.260: Device reported open completion 213s (process:2402): libfprint-device-DEBUG: 16:48:50.260: Completing action FPI_DEVICE_ACTION_OPEN in idle! 213s (process:2402): libfprint-device-DEBUG: 16:48:50.260: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 213s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:50.260: Got a new connection! 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.260: Got instructions of length 16 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.260: Received command SCAN right-thumb 213s (process:2402): libfprint-device-DEBUG: 16:48:50.260: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.260: Processing command SCAN right-thumb 213s (process:2402): libfprint-device-DEBUG: 16:48:50.260: Device reported finger status change: FP_FINGER_STATUS_NEEDED 213s (process:2402): libfprint-device-DEBUG: 16:48:50.260: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 213s (process:2402): libfprint-device-DEBUG: 16:48:50.260: Device reported finger status change: FP_FINGER_STATUS_NEEDED 213s (process:2402): libfprint-device-DEBUG: 16:48:50.260: Device reported enroll progress, reported 1 of 5 have been completed 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.260: Sleeping completed 213s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:50.260: Got a new connection! 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.260: Got instructions of length 16 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.260: Received command SCAN right-thumb 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.260: Processing command SCAN right-thumb 213s (process:2402): libfprint-device-DEBUG: 16:48:50.260: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 213s (process:2402): libfprint-device-DEBUG: 16:48:50.260: Device reported finger status change: FP_FINGER_STATUS_NEEDED 213s (process:2402): libfprint-device-DEBUG: 16:48:50.261: Device reported enroll progress, reported 2 of 5 have been completed 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.261: Sleeping completed 213s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:50.261: Got a new connection! 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.261: Got instructions of length 16 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.261: Received command SCAN right-thumb 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.261: Processing command SCAN right-thumb 213s (process:2402): libfprint-device-DEBUG: 16:48:50.261: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 213s (process:2402): libfprint-device-DEBUG: 16:48:50.261: Device reported finger status change: FP_FINGER_STATUS_NEEDED 213s (process:2402): libfprint-device-DEBUG: 16:48:50.261: Device reported enroll progress, reported 3 of 5 have been completed 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.261: Sleeping completed 213s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:50.261: Got a new connection! 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.261: Got instructions of length 16 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.261: Received command SCAN right-thumb 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.261: Processing command SCAN right-thumb 213s (process:2402): libfprint-device-DEBUG: 16:48:50.261: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 213s (process:2402): libfprint-device-DEBUG: 16:48:50.261: Device reported finger status change: FP_FINGER_STATUS_NEEDED 213s (process:2402): libfprint-device-DEBUG: 16:48:50.261: Device reported enroll progress, reported 4 of 5 have been completed 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.261: Sleeping completed 213s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:50.261: Got a new connection! 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.261: Got instructions of length 16 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.261: Received command SCAN right-thumb 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.261: Processing command SCAN right-thumb 213s (process:2402): libfprint-device-DEBUG: 16:48:50.261: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 213s (process:2402): libfprint-device-DEBUG: 16:48:50.261: Device reported finger status change: FP_FINGER_STATUS_NEEDED 213s (process:2402): libfprint-device-DEBUG: 16:48:50.262: Device reported enroll progress, reported 5 of 5 have been completed 213s (process:2402): libfprint-device-DEBUG: 16:48:50.262: Device reported enroll completion 213s (process:2402): libfprint-device-DEBUG: 16:48:50.262: Device reported finger status change: FP_FINGER_STATUS_NONE 213s (process:2402): libfprint-device-DEBUG: 16:48:50.262: Print for finger FP_FINGER_RIGHT_THUMB enrolled 213s (process:2402): libfprint-device-DEBUG: 16:48:50.262: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 213s (process:2402): libfprint-device-DEBUG: 16:48:50.262: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 213s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:50.262: Got a new connection! 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.262: Got instructions of length 15 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.262: Received command SCAN left-thumb 213s (process:2402): libfprint-device-DEBUG: 16:48:50.262: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.262: Processing command SCAN left-thumb 213s (process:2402): libfprint-device-DEBUG: 16:48:50.262: Device reported finger status change: FP_FINGER_STATUS_NEEDED 213s (process:2402): libfprint-device-DEBUG: 16:48:50.262: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 213s (process:2402): libfprint-device-DEBUG: 16:48:50.262: Device reported finger status change: FP_FINGER_STATUS_NEEDED 213s (process:2402): libfprint-device-DEBUG: 16:48:50.262: Device reported enroll progress, reported 1 of 5 have been completed 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.262: Sleeping completed 213s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:50.262: Got a new connection! 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.262: Got instructions of length 15 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.262: Received command SCAN left-thumb 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.262: Processing command SCAN left-thumb 213s (process:2402): libfprint-device-DEBUG: 16:48:50.262: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 213s (process:2402): libfprint-device-DEBUG: 16:48:50.262: Device reported finger status change: FP_FINGER_STATUS_NEEDED 213s (process:2402): libfprint-device-DEBUG: 16:48:50.262: Device reported enroll progress, reported 2 of 5 have been completed 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.263: Sleeping completed 213s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:50.263: Got a new connection! 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.263: Got instructions of length 15 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.263: Received command SCAN left-thumb 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.263: Processing command SCAN left-thumb 213s (process:2402): libfprint-device-DEBUG: 16:48:50.263: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 213s (process:2402): libfprint-device-DEBUG: 16:48:50.263: Device reported finger status change: FP_FINGER_STATUS_NEEDED 213s (process:2402): libfprint-device-DEBUG: 16:48:50.263: Device reported enroll progress, reported 3 of 5 have been completed 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.263: Sleeping completed 213s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:50.263: Got a new connection! 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.263: Got instructions of length 15 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.263: Received command SCAN left-thumb 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.263: Processing command SCAN left-thumb 213s (process:2402): libfprint-device-DEBUG: 16:48:50.263: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 213s (process:2402): libfprint-device-DEBUG: 16:48:50.263: Device reported finger status change: FP_FINGER_STATUS_NEEDED 213s (process:2402): libfprint-device-DEBUG: 16:48:50.263: Device reported enroll progress, reported 4 of 5 have been completed 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.263: Sleeping completed 213s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:50.263: Got a new connection! 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.263: Got instructions of length 15 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.263: Received command SCAN left-thumb 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.263: Processing command SCAN left-thumb 213s (process:2402): libfprint-device-DEBUG: 16:48:50.263: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 213s (process:2402): libfprint-device-DEBUG: 16:48:50.263: Device reported finger status change: FP_FINGER_STATUS_NEEDED 213s (process:2402): libfprint-device-DEBUG: 16:48:50.263: Device reported enroll progress, reported 5 of 5 have been completed 213s (process:2402): libfprint-device-DEBUG: 16:48:50.264: Device reported enroll completion 213s (process:2402): libfprint-device-DEBUG: 16:48:50.264: Device reported finger status change: FP_FINGER_STATUS_NONE 213s (process:2402): libfprint-device-DEBUG: 16:48:50.264: Print for finger FP_FINGER_LEFT_THUMB enrolled 213s (process:2402): libfprint-device-DEBUG: 16:48:50.264: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 213s (process:2402): libfprint-device-DEBUG: 16:48:50.264: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 213s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:50.264: Got a new connection! 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.264: Got instructions of length 16 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.264: Received command SCAN right-thumb 213s (process:2402): libfprint-device-DEBUG: 16:48:50.264: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.264: Processing command SCAN right-thumb 213s (process:2402): libfprint-device-DEBUG: 16:48:50.264: Device reported finger status change: FP_FINGER_STATUS_NEEDED 213s (process:2402): libfprint-device-DEBUG: 16:48:50.264: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 213s (process:2402): libfprint-virtual_device_storage-DEBUG: 16:48:50.264: Trying to identify print 'right-thumb' against a gallery of 2 prints 213s (process:2402): libfprint-device-DEBUG: 16:48:50.264: Device reported identify result 213s (process:2402): libfprint-device-DEBUG: 16:48:50.264: Device reported finger status change: FP_FINGER_STATUS_NEEDED 213s (process:2402): libfprint-device-DEBUG: 16:48:50.264: Device reported identify completion 213s (process:2402): libfprint-device-DEBUG: 16:48:50.264: Device reported finger status change: FP_FINGER_STATUS_NONE 213s (process:2402): libfprint-device-DEBUG: 16:48:50.264: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 213s (process:2402): libfprint-device-DEBUG: 16:48:50.264: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 213s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:50.264: Got a new connection! 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.264: Got instructions of length 15 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.264: Received command SCAN left-thumb 213s (process:2402): libfprint-device-DEBUG: 16:48:50.265: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.265: Processing command SCAN left-thumb 213s (process:2402): libfprint-device-DEBUG: 16:48:50.265: Device reported finger status change: FP_FINGER_STATUS_NEEDED 213s (process:2402): libfprint-device-DEBUG: 16:48:50.265: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 213s (process:2402): libfprint-virtual_device_storage-DEBUG: 16:48:50.265: Trying to identify print 'left-thumb' against a gallery of 2 prints 213s (process:2402): libfprint-device-DEBUG: 16:48:50.265: Device reported identify result 213s (process:2402): libfprint-device-DEBUG: 16:48:50.265: Device reported finger status change: FP_FINGER_STATUS_NEEDED 213s (process:2402): libfprint-device-DEBUG: 16:48:50.265: Device reported identify completion 213s (process:2402): libfprint-device-DEBUG: 16:48:50.265: Device reported finger status change: FP_FINGER_STATUS_NONE 213s (process:2402): libfprint-device-DEBUG: 16:48:50.265: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 213s (process:2402): libfprint-device-DEBUG: 16:48:50.265: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 213s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:50.265: Got a new connection! 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.265: Got instructions of length 5 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.265: Received command CONT 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.265: Processing command CONT 213s (process:2402): libfprint-device-DEBUG: 16:48:50.265: Device reported deletion completion 213s (process:2402): libfprint-device-DEBUG: 16:48:50.265: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 213s (process:2402): libfprint-device-DEBUG: 16:48:50.265: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 213s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:50.265: Got a new connection! 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.265: Got instructions of length 16 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.265: Received command SET_KEEP_ALIVE 0 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.265: Keep alive toggled: 0 213s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:50.265: Got a new connection! 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.266: Got instructions of length 19 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.266: Received command SET_ENROLL_STAGES 5 213s (process:2402): libfprint-device-DEBUG: 16:48:50.266: Device reported close completion 213s (process:2402): libfprint-device-DEBUG: 16:48:50.266: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 213s (process:2402): libfprint-device-DEBUG: 16:48:50.266: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 213s Enroll done 213s Enroll done 213s ok 213s test_identify_missing_print (__main__.VirtualDeviceStorage.test_identify_missing_print) ... (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.266: 101267057: ../libfprint/drivers/virtual-device.c:387 213s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:50.266: 101267086: ../libfprint/drivers/virtual-device-listener.c:153 213s (process:2402): libfprint-device-DEBUG: 16:48:50.266: Device reported open completion 213s (process:2402): libfprint-device-DEBUG: 16:48:50.266: Completing action FPI_DEVICE_ACTION_OPEN in idle! 213s (process:2402): libfprint-device-DEBUG: 16:48:50.266: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 213s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:50.266: Got a new connection! 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.266: Got instructions of length 23 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.266: Received command SCAN not-existing-print 213s (process:2402): libfprint-device-DEBUG: 16:48:50.266: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.266: Processing command SCAN not-existing-print 213s (process:2402): libfprint-device-DEBUG: 16:48:50.266: Device reported finger status change: FP_FINGER_STATUS_NEEDED 213s (process:2402): libfprint-device-DEBUG: 16:48:50.266: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 213s (process:2402): libfprint-virtual_device_storage-DEBUG: 16:48:50.266: Trying to identify print 'not-existing-print' against a gallery of 1 prints 213s (process:2402): libfprint-device-DEBUG: 16:48:50.267: Device reported identify result 213s (process:2402): libfprint-device-DEBUG: 16:48:50.267: Device reported finger status change: FP_FINGER_STATUS_NEEDED 213s (process:2402): libfprint-device-DEBUG: 16:48:50.267: Device reported identify completion 213s (process:2402): libfprint-device-DEBUG: 16:48:50.267: Device reported finger status change: FP_FINGER_STATUS_NONE 213s (process:2402): libfprint-device-DEBUG: 16:48:50.267: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 213s (process:2402): libfprint-device-DEBUG: 16:48:50.267: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 213s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:50.267: Got a new connection! 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.267: Got instructions of length 5 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.267: Received command CONT 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.267: Processing command CONT 213s (process:2402): libfprint-device-DEBUG: 16:48:50.267: Device reported deletion completion 213s (process:2402): libfprint-device-DEBUG: 16:48:50.267: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 213s (process:2402): libfprint-device-DEBUG: 16:48:50.267: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 213s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:50.267: Got a new connection! 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.267: Got instructions of length 16 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.267: Received command SET_KEEP_ALIVE 0 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.267: Keep alive toggled: 0 213s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:50.267: Got a new connection! 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.267: Got instructions of length 19 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.267: Received command SET_ENROLL_STAGES 5 213s (process:2402): libfprint-device-DEBUG: 16:48:50.267: Device reported close completion 213s (process:2402): libfprint-device-DEBUG: 16:48:50.268: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 213s (process:2402): libfprint-device-DEBUG: 16:48:50.268: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 213s ok 213s test_identify_no_match (__main__.VirtualDeviceStorage.test_identify_no_match) ... (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.268: 101268893: ../libfprint/drivers/virtual-device.c:387 213s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:50.268: 101268920: ../libfprint/drivers/virtual-device-listener.c:153 213s (process:2402): libfprint-device-DEBUG: 16:48:50.268: Device reported open completion 213s (process:2402): libfprint-device-DEBUG: 16:48:50.268: Completing action FPI_DEVICE_ACTION_OPEN in idle! 213s (process:2402): libfprint-device-DEBUG: 16:48:50.268: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 213s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:50.268: Got a new connection! 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.268: Got instructions of length 16 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.268: Received command SCAN right-thumb 213s (process:2402): libfprint-device-DEBUG: 16:48:50.268: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.268: Processing command SCAN right-thumb 213s (process:2402): libfprint-device-DEBUG: 16:48:50.268: Device reported finger status change: FP_FINGER_STATUS_NEEDED 213s (process:2402): libfprint-device-DEBUG: 16:48:50.268: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 213s (process:2402): libfprint-device-DEBUG: 16:48:50.268: Device reported finger status change: FP_FINGER_STATUS_NEEDED 213s (process:2402): libfprint-device-DEBUG: 16:48:50.268: Device reported enroll progress, reported 1 of 5 have been completed 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.268: Sleeping completed 213s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:50.268: Got a new connection! 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.268: Got instructions of length 16 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.268: Received command SCAN right-thumb 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.268: Processing command SCAN right-thumb 213s (process:2402): libfprint-device-DEBUG: 16:48:50.268: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 213s (process:2402): libfprint-device-DEBUG: 16:48:50.268: Device reported finger status change: FP_FINGER_STATUS_NEEDED 213s (process:2402): libfprint-device-DEBUG: 16:48:50.269: Device reported enroll progress, reported 2 of 5 have been completed 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.269: Sleeping completed 213s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:50.269: Got a new connection! 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.269: Got instructions of length 16 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.269: Received command SCAN right-thumb 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.269: Processing command SCAN right-thumb 213s (process:2402): libfprint-device-DEBUG: 16:48:50.269: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 213s (process:2402): libfprint-device-DEBUG: 16:48:50.269: Device reported finger status change: FP_FINGER_STATUS_NEEDED 213s (process:2402): libfprint-device-DEBUG: 16:48:50.269: Device reported enroll progress, reported 3 of 5 have been completed 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.269: Sleeping completed 213s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:50.269: Got a new connection! 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.269: Got instructions of length 16 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.269: Received command SCAN right-thumb 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.269: Processing command SCAN right-thumb 213s (process:2402): libfprint-device-DEBUG: 16:48:50.269: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 213s (process:2402): libfprint-device-DEBUG: 16:48:50.269: Device reported finger status change: FP_FINGER_STATUS_NEEDED 213s (process:2402): libfprint-device-DEBUG: 16:48:50.269: Device reported enroll progress, reported 4 of 5 have been completed 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.269: Sleeping completed 213s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:50.269: Got a new connection! 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.269: Got instructions of length 16 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.269: Received command SCAN right-thumb 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.269: Processing command SCAN right-thumb 213s (process:2402): libfprint-device-DEBUG: 16:48:50.269: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 213s (process:2402): libfprint-device-DEBUG: 16:48:50.269: Device reported finger status change: FP_FINGER_STATUS_NEEDED 213s (process:2402): libfprint-device-DEBUG: 16:48:50.269: Device reported enroll progress, reported 5 of 5 have been completed 213s (process:2402): libfprint-device-DEBUG: 16:48:50.269: Device reported enroll completion 213s (process:2402): libfprint-device-DEBUG: 16:48:50.269: Device reported finger status change: FP_FINGER_STATUS_NONE 213s (process:2402): libfprint-device-DEBUG: 16:48:50.269: Print for finger FP_FINGER_RIGHT_THUMB enrolled 213s (process:2402): libfprint-device-DEBUG: 16:48:50.269: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 213s (process:2402): libfprint-device-DEBUG: 16:48:50.269: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 213s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:50.269: Got a new connection! 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.269: Got instructions of length 15 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.269: Received command SCAN left-thumb 213s (process:2402): libfprint-device-DEBUG: 16:48:50.269: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.269: Processing command SCAN left-thumb 213s (process:2402): libfprint-device-DEBUG: 16:48:50.269: Device reported finger status change: FP_FINGER_STATUS_NEEDED 213s (process:2402): libfprint-device-DEBUG: 16:48:50.269: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 213s (process:2402): libfprint-device-DEBUG: 16:48:50.269: Device reported finger status change: FP_FINGER_STATUS_NEEDED 213s (process:2402): libfprint-device-DEBUG: 16:48:50.269: Device reported enroll progress, reported 1 of 5 have been completed 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.269: Sleeping completed 213s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:50.269: Got a new connection! 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.269: Got instructions of length 15 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.269: Received command SCAN left-thumb 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.269: Processing command SCAN left-thumb 213s (process:2402): libfprint-device-DEBUG: 16:48:50.269: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 213s (process:2402): libfprint-device-DEBUG: 16:48:50.269: Device reported finger status change: FP_FINGER_STATUS_NEEDED 213s (process:2402): libfprint-device-DEBUG: 16:48:50.269: Device reported enroll progress, reported 2 of 5 have been completed 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.269: Sleeping completed 213s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:50.270: Got a new connection! 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.270: Got instructions of length 15 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.270: Received command SCAN left-thumb 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.270: Processing command SCAN left-thumb 213s (process:2402): libfprint-device-DEBUG: 16:48:50.270: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 213s (process:2402): libfprint-device-DEBUG: 16:48:50.270: Device reported finger status change: FP_FINGER_STATUS_NEEDED 213s (process:2402): libfprint-device-DEBUG: 16:48:50.270: Device reported enroll progress, reported 3 of 5 have been completed 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.270: Sleeping completed 213s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:50.270: Got a new connection! 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.270: Got instructions of length 15 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.270: Received command SCAN left-thumb 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.270: Processing command SCAN left-thumb 213s (process:2402): libfprint-device-DEBUG: 16:48:50.270: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 213s (process:2402): libfprint-device-DEBUG: 16:48:50.270: Device reported finger status change: FP_FINGER_STATUS_NEEDED 213s (process:2402): libfprint-device-DEBUG: 16:48:50.270: Device reported enroll progress, reported 4 of 5 have been completed 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.270: Sleeping completed 213s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:50.270: Got a new connection! 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.270: Got instructions of length 15 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.270: Received command SCAN left-thumb 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.270: Processing command SCAN left-thumb 213s (process:2402): libfprint-device-DEBUG: 16:48:50.270: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 213s (process:2402): libfprint-device-DEBUG: 16:48:50.270: Device reported finger status change: FP_FINGER_STATUS_NEEDED 213s (process:2402): libfprint-device-DEBUG: 16:48:50.270: Device reported enroll progress, reported 5 of 5 have been completed 213s (process:2402): libfprint-device-DEBUG: 16:48:50.270: Device reported enroll completion 213s (process:2402): libfprint-device-DEBUG: 16:48:50.270: Device reported finger status change: FP_FINGER_STATUS_NONE 213s (process:2402): libfprint-device-DEBUG: 16:48:50.270: Print for finger FP_FINGER_LEFT_THUMB enrolled 213s (process:2402): libfprint-device-DEBUG: 16:48:50.270: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 213s (process:2402): libfprint-device-DEBUG: 16:48:50.270: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 213s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:50.270: Got a new connection! 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.270: Got instructions of length 16 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.270: Received command SCAN right-thumb 213s (process:2402): libfprint-device-DEBUG: 16:48:50.270: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.270: Processing command SCAN right-thumb 213s (process:2402): libfprint-device-DEBUG: 16:48:50.270: Device reported finger status change: FP_FINGER_STATUS_NEEDED 213s (process:2402): libfprint-device-DEBUG: 16:48:50.270: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 213s (process:2402): libfprint-virtual_device_storage-DEBUG: 16:48:50.270: Trying to identify print 'right-thumb' against a gallery of 1 prints 213s (process:2402): libfprint-device-DEBUG: 16:48:50.270: Device reported identify result 213s (process:2402): libfprint-device-DEBUG: 16:48:50.270: Device reported finger status change: FP_FINGER_STATUS_NEEDED 213s (process:2402): libfprint-device-DEBUG: 16:48:50.270: Device reported identify completion 213s (process:2402): libfprint-device-DEBUG: 16:48:50.270: Device reported finger status change: FP_FINGER_STATUS_NONE 213s (process:2402): libfprint-device-DEBUG: 16:48:50.270: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 213s (process:2402): libfprint-device-DEBUG: 16:48:50.270: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 213s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:50.270: Got a new connection! 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.270: Got instructions of length 15 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.270: Received command SCAN left-thumb 213s (process:2402): libfprint-device-DEBUG: 16:48:50.270: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.270: Processing command SCAN left-thumb 213s (process:2402): libfprint-device-DEBUG: 16:48:50.270: Device reported finger status change: FP_FINGER_STATUS_NEEDED 213s (process:2402): libfprint-device-DEBUG: 16:48:50.270: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 213s (process:2402): libfprint-virtual_device_storage-DEBUG: 16:48:50.270: Trying to identify print 'left-thumb' against a gallery of 1 prints 213s (process:2402): libfprint-device-DEBUG: 16:48:50.270: Device reported identify result 213s (process:2402): libfprint-device-DEBUG: 16:48:50.270: Device reported finger status change: FP_FINGER_STATUS_NEEDED 213s (process:2402): libfprint-device-DEBUG: 16:48:50.270: Device reported identify completion 213s (process:2402): libfprint-device-DEBUG: 16:48:50.270: Device reported finger status change: FP_FINGER_STATUS_NONE 213s (process:2402): libfprint-device-DEBUG: 16:48:50.270: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 213s (process:2402): libfprint-device-DEBUG: 16:48:50.270: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 213s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:50.271: Got a new connection! 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.271: Got instructions of length 5 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.271: Received command CONT 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.271: Processing command CONT 213s (process:2402): libfprint-device-DEBUG: 16:48:50.271: Device reported deletion completion 213s (process:2402): libfprint-device-DEBUG: 16:48:50.271: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 213s (process:2402): libfprint-device-DEBUG: 16:48:50.271: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 213s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:50.271: Got a new connection! 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.271: Got instructions of length 16 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.271: Received command SET_KEEP_ALIVE 0 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.271: Keep alive toggled: 0 213s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:50.271: Got a new connection! 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.271: Got instructions of length 19 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.271: Received command SET_ENROLL_STAGES 5 213s (process:2402): libfprint-device-DEBUG: 16:48:50.271: Device reported close completion 213s (process:2402): libfprint-device-DEBUG: 16:48:50.271: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 213s (process:2402): libfprint-device-DEBUG: 16:48:50.271: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 213s Enroll done 213s Enroll done 213s ok 213s test_identify_retry (__main__.VirtualDeviceStorage.test_identify_retry) ... (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.271: 101272361: ../libfprint/drivers/virtual-device.c:387 213s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:50.271: 101272390: ../libfprint/drivers/virtual-device-listener.c:153 213s (process:2402): libfprint-device-DEBUG: 16:48:50.271: Device reported open completion 213s (process:2402): libfprint-device-DEBUG: 16:48:50.271: Completing action FPI_DEVICE_ACTION_OPEN in idle! 213s (process:2402): libfprint-device-DEBUG: 16:48:50.271: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 213s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:50.271: Got a new connection! 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.272: Got instructions of length 7 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.272: Received command RETRY 1 213s (process:2402): libfprint-device-DEBUG: 16:48:50.272: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.272: Processing command RETRY 1 213s (process:2402): libfprint-device-DEBUG: 16:48:50.272: Device reported finger status change: FP_FINGER_STATUS_NEEDED 213s (process:2402): libfprint-device-DEBUG: 16:48:50.272: Device reported identify result 213s (process:2402): libfprint-device-DEBUG: 16:48:50.272: Device reported identify completion 213s (process:2402): libfprint-device-DEBUG: 16:48:50.272: Device reported finger status change: FP_FINGER_STATUS_NONE 213s (process:2402): libfprint-device-DEBUG: 16:48:50.272: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 213s (process:2402): libfprint-device-DEBUG: 16:48:50.272: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 213s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:50.272: Got a new connection! 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.272: Got instructions of length 5 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.272: Received command CONT 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.272: Processing command CONT 213s (process:2402): libfprint-device-DEBUG: 16:48:50.272: Device reported deletion completion 213s (process:2402): libfprint-device-DEBUG: 16:48:50.272: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 213s (process:2402): libfprint-device-DEBUG: 16:48:50.272: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 213s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:50.272: Got a new connection! 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.272: Got instructions of length 16 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.272: Received command SET_KEEP_ALIVE 0 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.272: Keep alive toggled: 0 213s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:50.273: Got a new connection! 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.273: Got instructions of length 19 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.273: Received command SET_ENROLL_STAGES 5 213s (process:2402): libfprint-device-DEBUG: 16:48:50.273: Device reported close completion 213s (process:2402): libfprint-device-DEBUG: 16:48:50.273: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 213s (process:2402): libfprint-device-DEBUG: 16:48:50.273: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 213s ok 213s test_identify_unsupported (__main__.VirtualDeviceStorage.test_identify_unsupported) ... (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.273: 101274120: ../libfprint/drivers/virtual-device.c:387 213s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:50.273: 101274150: ../libfprint/drivers/virtual-device-listener.c:153 213s (process:2402): libfprint-device-DEBUG: 16:48:50.273: Device reported open completion 213s (process:2402): libfprint-device-DEBUG: 16:48:50.273: Completing action FPI_DEVICE_ACTION_OPEN in idle! 213s (process:2402): libfprint-device-DEBUG: 16:48:50.273: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 213s skipped 'Device supports identification' 213s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:50.273: Got a new connection! 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.273: Got instructions of length 5 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.273: Received command CONT 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.273: Processing command CONT 213s (process:2402): libfprint-device-DEBUG: 16:48:50.273: Device reported deletion completion 213s (process:2402): libfprint-device-DEBUG: 16:48:50.273: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 213s (process:2402): libfprint-device-DEBUG: 16:48:50.273: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 213s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:50.274: Got a new connection! 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.274: Got instructions of length 16 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.274: Received command SET_KEEP_ALIVE 0 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.274: Keep alive toggled: 0 213s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:50.274: Got a new connection! 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.274: Got instructions of length 19 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.274: Received command SET_ENROLL_STAGES 5 213s (process:2402): libfprint-device-DEBUG: 16:48:50.274: Device reported close completion 213s (process:2402): libfprint-device-DEBUG: 16:48:50.274: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 213s (process:2402): libfprint-device-DEBUG: 16:48:50.274: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 213s test_list_delete (__main__.VirtualDeviceStorage.test_list_delete) ... (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.274: 101275289: ../libfprint/drivers/virtual-device.c:387 213s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:50.274: 101275317: ../libfprint/drivers/virtual-device-listener.c:153 213s (process:2402): libfprint-device-DEBUG: 16:48:50.274: Device reported open completion 213s (process:2402): libfprint-device-DEBUG: 16:48:50.274: Completing action FPI_DEVICE_ACTION_OPEN in idle! 213s (process:2402): libfprint-device-DEBUG: 16:48:50.274: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 213s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:50.274: Got a new connection! 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.274: Got instructions of length 14 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.275: Received command SCAN testprint 213s (process:2402): libfprint-device-DEBUG: 16:48:50.275: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.275: Processing command SCAN testprint 213s (process:2402): libfprint-device-DEBUG: 16:48:50.275: Device reported finger status change: FP_FINGER_STATUS_NEEDED 213s (process:2402): libfprint-device-DEBUG: 16:48:50.275: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 213s (process:2402): libfprint-device-DEBUG: 16:48:50.275: Device reported finger status change: FP_FINGER_STATUS_NEEDED 213s (process:2402): libfprint-device-DEBUG: 16:48:50.275: Device reported enroll progress, reported 1 of 5 have been completed 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.275: Sleeping completed 213s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:50.275: Got a new connection! 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.275: Got instructions of length 14 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.275: Received command SCAN testprint 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.275: Processing command SCAN testprint 213s (process:2402): libfprint-device-DEBUG: 16:48:50.275: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 213s (process:2402): libfprint-device-DEBUG: 16:48:50.275: Device reported finger status change: FP_FINGER_STATUS_NEEDED 213s (process:2402): libfprint-device-DEBUG: 16:48:50.275: Device reported enroll progress, reported 2 of 5 have been completed 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.275: Sleeping completed 213s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:50.275: Got a new connection! 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.275: Got instructions of length 14 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.275: Received command SCAN testprint 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.275: Processing command SCAN testprint 213s (process:2402): libfprint-device-DEBUG: 16:48:50.275: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 213s (process:2402): libfprint-device-DEBUG: 16:48:50.275: Device reported finger status change: FP_FINGER_STATUS_NEEDED 213s (process:2402): libfprint-device-DEBUG: 16:48:50.275: Device reported enroll progress, reported 3 of 5 have been completed 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.276: Sleeping completed 213s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:50.276: Got a new connection! 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.276: Got instructions of length 14 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.276: Received command SCAN testprint 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.276: Processing command SCAN testprint 213s (process:2402): libfprint-device-DEBUG: 16:48:50.276: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 213s (process:2402): libfprint-device-DEBUG: 16:48:50.276: Device reported finger status change: FP_FINGER_STATUS_NEEDED 213s (process:2402): libfprint-device-DEBUG: 16:48:50.276: Device reported enroll progress, reported 4 of 5 have been completed 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.276: Sleeping completed 213s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:50.276: Got a new connection! 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.276: Got instructions of length 14 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.276: Received command SCAN testprint 213s (process:2402): libfprint-virtual_device-DEBUG: 16:48:50.276: Processing command SCAN testprint 213s (process:2402): libfprint-device-DEBUG: 16:48:50.276: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 213s (process:2402): libfprint-device-DEBUG: 16:48:50.276: Device reported finger status change: FP_FINGER_STATUS_NEEDED 213s (process:2402): libfprint-device-DEBUG: 16:48:50.276: Device reported enroll progress, reported 5 of 5 have been completed 213s (process:2402): libfprint-device-DEBUG: 16:48:50.276: Device reported enroll completion 213s (process:2402): libfprint-device-DEBUG: 16:48:50.276: Device reported finger status change: FP_FINGER_STATUS_NONE 213s (process:2402): libfprint-device-DEBUG: 16:48:50.276: Print for finger FP_FINGER_RIGHT_THUMB enrolled 213s (process:2402): libfprint-device-DEBUG: 16:48:50.276: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 213s (process:2402): libfprint-device-DEBUG: 16:48:50.276: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 213s (process:2402): libfprint-device-DEBUG: 16:48:50.777: Device reported listing completion 213s (process:2402): libfprint-device-DEBUG: 16:48:50.777: Completing action FPI_DEVICE_ACTION_LIST in idle! 213s (process:2402): libfprint-device-DEBUG: 16:48:50.777: Updated temperature model after 0.50 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 214s (process:2402): libfprint-virtual_device_storage-DEBUG: 16:48:51.291: Deleting print testprint for user testuser 214s (process:2402): libfprint-device-DEBUG: 16:48:51.292: Device reported deletion completion 214s (process:2402): libfprint-device-DEBUG: 16:48:51.292: Completing action FPI_DEVICE_ACTION_DELETE in idle! 214s (process:2402): libfprint-device-DEBUG: 16:48:51.292: Updated temperature model after 0.51 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 214s (process:2402): libfprint-device-DEBUG: 16:48:51.792: Device reported listing completion 214s (process:2402): libfprint-device-DEBUG: 16:48:51.792: Completing action FPI_DEVICE_ACTION_LIST in idle! 214s (process:2402): libfprint-device-DEBUG: 16:48:51.792: Updated temperature model after 0.50 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 214s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:51.793: Got a new connection! 214s (process:2402): libfprint-virtual_device-DEBUG: 16:48:51.793: Got instructions of length 5 214s (process:2402): libfprint-virtual_device-DEBUG: 16:48:51.793: Received command CONT 214s (process:2402): libfprint-virtual_device-DEBUG: 16:48:51.793: Processing command CONT 214s (process:2402): libfprint-device-DEBUG: 16:48:51.793: Device reported deletion completion 214s (process:2402): libfprint-device-DEBUG: 16:48:51.793: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 214s (process:2402): libfprint-device-DEBUG: 16:48:51.793: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 214s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:51.793: Got a new connection! 214s (process:2402): libfprint-virtual_device-DEBUG: 16:48:51.793: Got instructions of length 16 214s (process:2402): libfprint-virtual_device-DEBUG: 16:48:51.793: Received command SET_KEEP_ALIVE 0 214s (process:2402): libfprint-virtual_device-DEBUG: 16:48:51.793: Keep alive toggled: 0 214s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:51.793: Got a new connection! 214s (process:2402): libfprint-virtual_device-DEBUG: 16:48:51.793: Got instructions of length 19 214s (process:2402): libfprint-virtual_device-DEBUG: 16:48:51.793: Received command SET_ENROLL_STAGES 5 214s (process:2402): libfprint-device-DEBUG: 16:48:51.793: Device reported close completion 214s (process:2402): libfprint-device-DEBUG: 16:48:51.793: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 214s (process:2402): libfprint-device-DEBUG: 16:48:51.793: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 214s Enroll done 214s 214s blub 'testprint' 214s ok 214s test_list_delete_missing (__main__.VirtualDeviceStorage.test_list_delete_missing) ... (process:2402): libfprint-virtual_device-DEBUG: 16:48:51.793: 102794619: ../libfprint/drivers/virtual-device.c:387 214s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:51.793: 102794643: ../libfprint/drivers/virtual-device-listener.c:153 214s (process:2402): libfprint-device-DEBUG: 16:48:51.794: Device reported open completion 214s (process:2402): libfprint-device-DEBUG: 16:48:51.794: Completing action FPI_DEVICE_ACTION_OPEN in idle! 214s (process:2402): libfprint-device-DEBUG: 16:48:51.794: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 214s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:51.794: Got a new connection! 214s (process:2402): libfprint-virtual_device-DEBUG: 16:48:51.794: Got instructions of length 14 214s (process:2402): libfprint-virtual_device-DEBUG: 16:48:51.794: Received command SCAN testprint 214s (process:2402): libfprint-device-DEBUG: 16:48:51.794: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 214s (process:2402): libfprint-virtual_device-DEBUG: 16:48:51.794: Processing command SCAN testprint 214s (process:2402): libfprint-device-DEBUG: 16:48:51.794: Device reported finger status change: FP_FINGER_STATUS_NEEDED 214s (process:2402): libfprint-device-DEBUG: 16:48:51.794: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 214s (process:2402): libfprint-device-DEBUG: 16:48:51.794: Device reported finger status change: FP_FINGER_STATUS_NEEDED 214s (process:2402): libfprint-device-DEBUG: 16:48:51.794: Device reported enroll progress, reported 1 of 5 have been completed 214s (process:2402): libfprint-virtual_device-DEBUG: 16:48:51.794: Sleeping completed 214s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:51.794: Got a new connection! 214s (process:2402): libfprint-virtual_device-DEBUG: 16:48:51.794: Got instructions of length 14 214s (process:2402): libfprint-virtual_device-DEBUG: 16:48:51.794: Received command SCAN testprint 214s (process:2402): libfprint-virtual_device-DEBUG: 16:48:51.794: Processing command SCAN testprint 214s (process:2402): libfprint-device-DEBUG: 16:48:51.794: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 214s (process:2402): libfprint-device-DEBUG: 16:48:51.794: Device reported finger status change: FP_FINGER_STATUS_NEEDED 214s (process:2402): libfprint-device-DEBUG: 16:48:51.794: Device reported enroll progress, reported 2 of 5 have been completed 214s (process:2402): libfprint-virtual_device-DEBUG: 16:48:51.794: Sleeping completed 214s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:51.795: Got a new connection! 214s (process:2402): libfprint-virtual_device-DEBUG: 16:48:51.795: Got instructions of length 14 214s (process:2402): libfprint-virtual_device-DEBUG: 16:48:51.795: Received command SCAN testprint 214s (process:2402): libfprint-virtual_device-DEBUG: 16:48:51.795: Processing command SCAN testprint 214s (process:2402): libfprint-device-DEBUG: 16:48:51.795: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 214s (process:2402): libfprint-device-DEBUG: 16:48:51.795: Device reported finger status change: FP_FINGER_STATUS_NEEDED 214s (process:2402): libfprint-device-DEBUG: 16:48:51.795: Device reported enroll progress, reported 3 of 5 have been completed 214s (process:2402): libfprint-virtual_device-DEBUG: 16:48:51.795: Sleeping completed 214s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:51.795: Got a new connection! 214s (process:2402): libfprint-virtual_device-DEBUG: 16:48:51.795: Got instructions of length 14 214s (process:2402): libfprint-virtual_device-DEBUG: 16:48:51.795: Received command SCAN testprint 214s (process:2402): libfprint-virtual_device-DEBUG: 16:48:51.795: Processing command SCAN testprint 214s (process:2402): libfprint-device-DEBUG: 16:48:51.795: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 214s (process:2402): libfprint-device-DEBUG: 16:48:51.795: Device reported finger status change: FP_FINGER_STATUS_NEEDED 214s (process:2402): libfprint-device-DEBUG: 16:48:51.795: Device reported enroll progress, reported 4 of 5 have been completed 214s (process:2402): libfprint-virtual_device-DEBUG: 16:48:51.795: Sleeping completed 214s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:51.795: Got a new connection! 214s (process:2402): libfprint-virtual_device-DEBUG: 16:48:51.795: Got instructions of length 14 214s (process:2402): libfprint-virtual_device-DEBUG: 16:48:51.795: Received command SCAN testprint 214s (process:2402): libfprint-virtual_device-DEBUG: 16:48:51.795: Processing command SCAN testprint 214s (process:2402): libfprint-device-DEBUG: 16:48:51.795: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 214s (process:2402): libfprint-device-DEBUG: 16:48:51.795: Device reported finger status change: FP_FINGER_STATUS_NEEDED 214s (process:2402): libfprint-device-DEBUG: 16:48:51.795: Device reported enroll progress, reported 5 of 5 have been completed 214s (process:2402): libfprint-device-DEBUG: 16:48:51.795: Device reported enroll completion 214s (process:2402): libfprint-device-DEBUG: 16:48:51.795: Device reported finger status change: FP_FINGER_STATUS_NONE 214s (process:2402): libfprint-device-DEBUG: 16:48:51.795: Print for finger FP_FINGER_RIGHT_THUMB enrolled 214s (process:2402): libfprint-device-DEBUG: 16:48:51.795: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 214s (process:2402): libfprint-device-DEBUG: 16:48:51.795: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 214s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:51.795: Got a new connection! 214s (process:2402): libfprint-virtual_device-DEBUG: 16:48:51.796: Got instructions of length 16 214s (process:2402): libfprint-virtual_device-DEBUG: 16:48:51.796: Received command REMOVE testprint 214s (process:2402): libfprint-virtual_device-DEBUG: 16:48:51.796: Processing command REMOVE testprint 215s (process:2402): libfprint-virtual_device_storage-DEBUG: 16:48:52.296: Deleting print testprint for user testuser 215s (process:2402): libfprint-device-DEBUG: 16:48:52.296: Device reported deletion completion 215s (process:2402): libfprint-device-DEBUG: 16:48:52.296: Completing action FPI_DEVICE_ACTION_DELETE in idle! 215s (process:2402): libfprint-device-DEBUG: 16:48:52.296: Updated temperature model after 0.50 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 215s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:52.296: Got a new connection! 215s (process:2402): libfprint-virtual_device-DEBUG: 16:48:52.296: Got instructions of length 5 215s (process:2402): libfprint-virtual_device-DEBUG: 16:48:52.296: Received command CONT 215s (process:2402): libfprint-virtual_device-DEBUG: 16:48:52.297: Processing command CONT 215s (process:2402): libfprint-device-DEBUG: 16:48:52.297: Device reported deletion completion 215s (process:2402): libfprint-device-DEBUG: 16:48:52.297: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 215s (process:2402): libfprint-device-DEBUG: 16:48:52.297: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 215s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:52.297: Got a new connection! 215s (process:2402): libfprint-virtual_device-DEBUG: 16:48:52.297: Got instructions of length 16 215s (process:2402): libfprint-virtual_device-DEBUG: 16:48:52.297: Received command SET_KEEP_ALIVE 0 215s (process:2402): libfprint-virtual_device-DEBUG: 16:48:52.297: Keep alive toggled: 0 215s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:52.297: Got a new connection! 215s (process:2402): libfprint-virtual_device-DEBUG: 16:48:52.297: Got instructions of length 19 215s (process:2402): libfprint-virtual_device-DEBUG: 16:48:52.297: Received command SET_ENROLL_STAGES 5 215s (process:2402): libfprint-device-DEBUG: 16:48:52.297: Device reported close completion 215s (process:2402): libfprint-device-DEBUG: 16:48:52.297: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 215s (process:2402): libfprint-device-DEBUG: 16:48:52.297: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 215s Enroll done 215s ok 215s test_list_empty (__main__.VirtualDeviceStorage.test_list_empty) ... (process:2402): libfprint-virtual_device-DEBUG: 16:48:52.297: 103298090: ../libfprint/drivers/virtual-device.c:387 215s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:52.297: 103298100: ../libfprint/drivers/virtual-device-listener.c:153 215s (process:2402): libfprint-device-DEBUG: 16:48:52.297: Device reported open completion 215s (process:2402): libfprint-device-DEBUG: 16:48:52.297: Completing action FPI_DEVICE_ACTION_OPEN in idle! 215s (process:2402): libfprint-device-DEBUG: 16:48:52.297: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 215s (process:2402): libfprint-device-DEBUG: 16:48:52.798: Device reported listing completion 215s (process:2402): libfprint-device-DEBUG: 16:48:52.798: Completing action FPI_DEVICE_ACTION_LIST in idle! 215s (process:2402): libfprint-device-DEBUG: 16:48:52.798: Updated temperature model after 0.50 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 215s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:52.798: Got a new connection! 215s (process:2402): libfprint-virtual_device-DEBUG: 16:48:52.798: Got instructions of length 5 215s (process:2402): libfprint-virtual_device-DEBUG: 16:48:52.798: Received command CONT 215s (process:2402): libfprint-virtual_device-DEBUG: 16:48:52.798: Processing command CONT 215s (process:2402): libfprint-device-DEBUG: 16:48:52.798: Device reported deletion completion 215s (process:2402): libfprint-device-DEBUG: 16:48:52.798: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 215s (process:2402): libfprint-device-DEBUG: 16:48:52.798: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 215s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:52.798: Got a new connection! 215s (process:2402): libfprint-virtual_device-DEBUG: 16:48:52.798: Got instructions of length 16 215s (process:2402): libfprint-virtual_device-DEBUG: 16:48:52.798: Received command SET_KEEP_ALIVE 0 215s (process:2402): libfprint-virtual_device-DEBUG: 16:48:52.798: Keep alive toggled: 0 215s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:52.798: Got a new connection! 215s (process:2402): libfprint-virtual_device-DEBUG: 16:48:52.798: Got instructions of length 19 215s (process:2402): libfprint-virtual_device-DEBUG: 16:48:52.798: Received command SET_ENROLL_STAGES 5 215s (process:2402): libfprint-device-DEBUG: 16:48:52.798: Device reported close completion 215s (process:2402): libfprint-device-DEBUG: 16:48:52.798: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 215s (process:2402): libfprint-device-DEBUG: 16:48:52.798: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 215s ok 215s test_list_error (__main__.VirtualDeviceStorage.test_list_error) ... (process:2402): libfprint-virtual_device-DEBUG: 16:48:52.798: 103799562: ../libfprint/drivers/virtual-device.c:387 215s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:52.798: 103799571: ../libfprint/drivers/virtual-device-listener.c:153 215s (process:2402): libfprint-device-DEBUG: 16:48:52.798: Device reported open completion 215s (process:2402): libfprint-device-DEBUG: 16:48:52.798: Completing action FPI_DEVICE_ACTION_OPEN in idle! 215s (process:2402): libfprint-device-DEBUG: 16:48:52.798: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 215s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:52.799: Got a new connection! 215s (process:2402): libfprint-virtual_device-DEBUG: 16:48:52.799: Got instructions of length 9 215s (process:2402): libfprint-virtual_device-DEBUG: 16:48:52.799: Received command SLEEP 100 215s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:52.799: Got a new connection! 215s (process:2402): libfprint-virtual_device-DEBUG: 16:48:52.799: Got instructions of length 7 215s (process:2402): libfprint-virtual_device-DEBUG: 16:48:52.799: Received command ERROR 4 215s (process:2402): libfprint-virtual_device-DEBUG: 16:48:52.799: Processing command SLEEP 100 215s (process:2402): libfprint-virtual_device-DEBUG: 16:48:52.799: Sleeping 100ms 215s (process:2402): libfprint-virtual_device-DEBUG: 16:48:52.899: Sleeping completed 215s (process:2402): libfprint-virtual_device-DEBUG: 16:48:52.899: Processing command ERROR 4 215s (process:2402): libfprint-device-DEBUG: 16:48:52.899: Device reported listing completion 215s (process:2402): libfprint-device-DEBUG: 16:48:52.899: Completing action FPI_DEVICE_ACTION_LIST in idle! 215s (process:2402): libfprint-device-DEBUG: 16:48:52.899: Updated temperature model after 0.10 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 215s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:52.900: Got a new connection! 215s (process:2402): libfprint-virtual_device-DEBUG: 16:48:52.900: Got instructions of length 5 215s (process:2402): libfprint-virtual_device-DEBUG: 16:48:52.900: Received command CONT 215s (process:2402): libfprint-virtual_device-DEBUG: 16:48:52.900: Processing command CONT 215s (process:2402): libfprint-device-DEBUG: 16:48:52.900: Device reported deletion completion 215s (process:2402): libfprint-device-DEBUG: 16:48:52.900: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 215s (process:2402): libfprint-device-DEBUG: 16:48:52.900: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 215s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:52.900: Got a new connection! 215s (process:2402): libfprint-virtual_device-DEBUG: 16:48:52.900: Got instructions of length 16 215s (process:2402): libfprint-virtual_device-DEBUG: 16:48:52.900: Received command SET_KEEP_ALIVE 0 215s (process:2402): libfprint-virtual_device-DEBUG: 16:48:52.900: Keep alive toggled: 0 215s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:52.900: Got a new connection! 215s (process:2402): libfprint-virtual_device-DEBUG: 16:48:52.900: Got instructions of length 19 215s (process:2402): libfprint-virtual_device-DEBUG: 16:48:52.900: Received command SET_ENROLL_STAGES 5 215s (process:2402): libfprint-device-DEBUG: 16:48:52.900: Device reported close completion 215s (process:2402): libfprint-device-DEBUG: 16:48:52.900: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 215s (process:2402): libfprint-device-DEBUG: 16:48:52.900: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 215s ok 215s test_list_populated (__main__.VirtualDeviceStorage.test_list_populated) ... (process:2402): libfprint-virtual_device-DEBUG: 16:48:52.900: 103901324: ../libfprint/drivers/virtual-device.c:387 215s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:52.900: 103901332: ../libfprint/drivers/virtual-device-listener.c:153 215s (process:2402): libfprint-device-DEBUG: 16:48:52.900: Device reported open completion 215s (process:2402): libfprint-device-DEBUG: 16:48:52.900: Completing action FPI_DEVICE_ACTION_OPEN in idle! 215s (process:2402): libfprint-device-DEBUG: 16:48:52.900: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 215s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:52.900: Got a new connection! 215s (process:2402): libfprint-virtual_device-DEBUG: 16:48:52.900: Got instructions of length 9 215s (process:2402): libfprint-virtual_device-DEBUG: 16:48:52.900: Received command INSERT p1 215s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:52.900: Got a new connection! 215s (process:2402): libfprint-virtual_device-DEBUG: 16:48:52.900: Got instructions of length 7 215s (process:2402): libfprint-virtual_device-DEBUG: 16:48:52.900: Received command SCAN p2 215s (process:2402): libfprint-device-DEBUG: 16:48:52.901: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 215s (process:2402): libfprint-virtual_device-DEBUG: 16:48:52.901: Processing command INSERT p1 215s (process:2402): libfprint-virtual_device-DEBUG: 16:48:52.901: Processing command SCAN p2 215s (process:2402): libfprint-device-DEBUG: 16:48:52.901: Device reported finger status change: FP_FINGER_STATUS_NEEDED 215s (process:2402): libfprint-device-DEBUG: 16:48:52.901: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 215s (process:2402): libfprint-device-DEBUG: 16:48:52.901: Device reported finger status change: FP_FINGER_STATUS_NEEDED 215s (process:2402): libfprint-device-DEBUG: 16:48:52.901: Device reported enroll progress, reported 1 of 5 have been completed 215s (process:2402): libfprint-virtual_device-DEBUG: 16:48:52.901: Sleeping completed 215s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:52.901: Got a new connection! 215s (process:2402): libfprint-virtual_device-DEBUG: 16:48:52.901: Got instructions of length 7 215s (process:2402): libfprint-virtual_device-DEBUG: 16:48:52.901: Received command SCAN p2 215s (process:2402): libfprint-virtual_device-DEBUG: 16:48:52.901: Processing command SCAN p2 215s (process:2402): libfprint-device-DEBUG: 16:48:52.901: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 215s (process:2402): libfprint-device-DEBUG: 16:48:52.901: Device reported finger status change: FP_FINGER_STATUS_NEEDED 215s (process:2402): libfprint-device-DEBUG: 16:48:52.901: Device reported enroll progress, reported 2 of 5 have been completed 215s (process:2402): libfprint-virtual_device-DEBUG: 16:48:52.901: Sleeping completed 215s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:52.901: Got a new connection! 215s (process:2402): libfprint-virtual_device-DEBUG: 16:48:52.901: Got instructions of length 7 215s (process:2402): libfprint-virtual_device-DEBUG: 16:48:52.901: Received command SCAN p2 215s (process:2402): libfprint-virtual_device-DEBUG: 16:48:52.901: Processing command SCAN p2 215s (process:2402): libfprint-device-DEBUG: 16:48:52.901: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 215s (process:2402): libfprint-device-DEBUG: 16:48:52.901: Device reported finger status change: FP_FINGER_STATUS_NEEDED 215s (process:2402): libfprint-device-DEBUG: 16:48:52.901: Device reported enroll progress, reported 3 of 5 have been completed 215s (process:2402): libfprint-virtual_device-DEBUG: 16:48:52.901: Sleeping completed 215s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:52.901: Got a new connection! 215s (process:2402): libfprint-virtual_device-DEBUG: 16:48:52.901: Got instructions of length 7 215s (process:2402): libfprint-virtual_device-DEBUG: 16:48:52.901: Received command SCAN p2 215s (process:2402): libfprint-virtual_device-DEBUG: 16:48:52.901: Processing command SCAN p2 215s (process:2402): libfprint-device-DEBUG: 16:48:52.901: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 215s (process:2402): libfprint-device-DEBUG: 16:48:52.901: Device reported finger status change: FP_FINGER_STATUS_NEEDED 215s (process:2402): libfprint-device-DEBUG: 16:48:52.901: Device reported enroll progress, reported 4 of 5 have been completed 215s (process:2402): libfprint-virtual_device-DEBUG: 16:48:52.901: Sleeping completed 215s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:52.901: Got a new connection! 215s (process:2402): libfprint-virtual_device-DEBUG: 16:48:52.901: Got instructions of length 7 215s (process:2402): libfprint-virtual_device-DEBUG: 16:48:52.901: Received command SCAN p2 215s (process:2402): libfprint-virtual_device-DEBUG: 16:48:52.901: Processing command SCAN p2 215s (process:2402): libfprint-device-DEBUG: 16:48:52.901: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 215s (process:2402): libfprint-device-DEBUG: 16:48:52.901: Device reported finger status change: FP_FINGER_STATUS_NEEDED 215s (process:2402): libfprint-device-DEBUG: 16:48:52.901: Device reported enroll progress, reported 5 of 5 have been completed 215s (process:2402): libfprint-device-DEBUG: 16:48:52.901: Device reported enroll completion 215s (process:2402): libfprint-device-DEBUG: 16:48:52.901: Device reported finger status change: FP_FINGER_STATUS_NONE 215s (process:2402): libfprint-device-DEBUG: 16:48:52.901: Print for finger FP_FINGER_LEFT_LITTLE enrolled 215s (process:2402): libfprint-device-DEBUG: 16:48:52.901: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 215s (process:2402): libfprint-device-DEBUG: 16:48:52.901: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 216s (process:2402): libfprint-device-DEBUG: 16:48:53.402: Device reported listing completion 216s (process:2402): libfprint-device-DEBUG: 16:48:53.402: Completing action FPI_DEVICE_ACTION_LIST in idle! 216s (process:2402): libfprint-device-DEBUG: 16:48:53.402: Updated temperature model after 0.50 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 216s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:53.402: Got a new connection! 216s (process:2402): libfprint-virtual_device-DEBUG: 16:48:53.402: Got instructions of length 5 216s (process:2402): libfprint-virtual_device-DEBUG: 16:48:53.402: Received command CONT 216s (process:2402): libfprint-virtual_device-DEBUG: 16:48:53.402: Processing command CONT 216s (process:2402): libfprint-device-DEBUG: 16:48:53.402: Device reported deletion completion 216s (process:2402): libfprint-device-DEBUG: 16:48:53.402: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 216s (process:2402): libfprint-device-DEBUG: 16:48:53.402: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 216s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:53.403: Got a new connection! 216s (process:2402): libfprint-virtual_device-DEBUG: 16:48:53.403: Got instructions of length 16 216s (process:2402): libfprint-virtual_device-DEBUG: 16:48:53.403: Received command SET_KEEP_ALIVE 0 216s (process:2402): libfprint-virtual_device-DEBUG: 16:48:53.403: Keep alive toggled: 0 216s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:53.403: Got a new connection! 216s (process:2402): libfprint-virtual_device-DEBUG: 16:48:53.403: Got instructions of length 19 216s (process:2402): libfprint-virtual_device-DEBUG: 16:48:53.403: Received command SET_ENROLL_STAGES 5 216s (process:2402): libfprint-device-DEBUG: 16:48:53.403: Device reported close completion 216s (process:2402): libfprint-device-DEBUG: 16:48:53.403: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 216s (process:2402): libfprint-device-DEBUG: 16:48:53.403: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 216s Enroll done 216s ok 216s test_open_error (__main__.VirtualDeviceStorage.test_open_error) ... (process:2402): libfprint-virtual_device-DEBUG: 16:48:53.403: 104404189: ../libfprint/drivers/virtual-device.c:387 216s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:53.403: 104404201: ../libfprint/drivers/virtual-device-listener.c:153 216s (process:2402): libfprint-device-DEBUG: 16:48:53.403: Device reported open completion 216s (process:2402): libfprint-device-DEBUG: 16:48:53.403: Completing action FPI_DEVICE_ACTION_OPEN in idle! 216s (process:2402): libfprint-device-DEBUG: 16:48:53.403: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 216s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:53.403: Got a new connection! 216s (process:2402): libfprint-virtual_device-DEBUG: 16:48:53.403: Got instructions of length 16 216s (process:2402): libfprint-virtual_device-DEBUG: 16:48:53.403: Received command IGNORED_COMMAND 216s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:53.403: Got a new connection! 216s (process:2402): libfprint-virtual_device-DEBUG: 16:48:53.403: Got instructions of length 7 216s (process:2402): libfprint-virtual_device-DEBUG: 16:48:53.403: Received command ERROR 5 216s (process:2402): libfprint-virtual_device-DEBUG: 16:48:53.403: Processing command IGNORED_COMMAND 216s (process:2402): libfprint-device-DEBUG: 16:48:53.403: Device reported close completion 216s (process:2402): libfprint-device-DEBUG: 16:48:53.403: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 216s (process:2402): libfprint-device-DEBUG: 16:48:53.404: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 216s (process:2402): libfprint-virtual_device-DEBUG: 16:48:53.404: 104404848: ../libfprint/drivers/virtual-device.c:387 216s (process:2402): libfprint-virtual_device-DEBUG: 16:48:53.404: Processing command ERROR 5 216s (process:2402): libfprint-device-DEBUG: 16:48:53.404: Device reported open completion 216s (process:2402): libfprint-device-DEBUG: 16:48:53.404: Completing action FPI_DEVICE_ACTION_OPEN in idle! 216s (process:2402): libfprint-device-DEBUG: 16:48:53.404: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 216s ok 216s test_open_error_with_keep_alive (__main__.VirtualDeviceStorage.test_open_error_with_keep_alive) ... (process:2402): libfprint-virtual_device-DEBUG: 16:48:53.404: 104404970: ../libfprint/drivers/virtual-device.c:387 216s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:53.404: 104404978: ../libfprint/drivers/virtual-device-listener.c:153 216s (process:2402): libfprint-device-DEBUG: 16:48:53.404: Device reported open completion 216s (process:2402): libfprint-device-DEBUG: 16:48:53.404: Completing action FPI_DEVICE_ACTION_OPEN in idle! 216s (process:2402): libfprint-device-DEBUG: 16:48:53.404: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 216s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:53.404: Got a new connection! 216s (process:2402): libfprint-virtual_device-DEBUG: 16:48:53.404: Got instructions of length 16 216s (process:2402): libfprint-virtual_device-DEBUG: 16:48:53.404: Received command SET_KEEP_ALIVE 1 216s (process:2402): libfprint-virtual_device-DEBUG: 16:48:53.404: Keep alive toggled: 1 216s (process:2402): libfprint-device-DEBUG: 16:48:53.404: Device reported close completion 216s (process:2402): libfprint-device-DEBUG: 16:48:53.404: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 216s (process:2402): libfprint-device-DEBUG: 16:48:53.404: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 216s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:53.404: Got a new connection! 216s (process:2402): libfprint-virtual_device-DEBUG: 16:48:53.404: Got instructions of length 7 216s (process:2402): libfprint-virtual_device-DEBUG: 16:48:53.404: Received command ERROR 5 216s (process:2402): libfprint-virtual_device-DEBUG: 16:48:53.404: 104405347: ../libfprint/drivers/virtual-device.c:387 216s (process:2402): libfprint-virtual_device-DEBUG: 16:48:53.404: Processing command ERROR 5 216s (process:2402): libfprint-device-DEBUG: 16:48:53.404: Device reported open completion 216s (process:2402): libfprint-device-DEBUG: 16:48:53.404: Completing action FPI_DEVICE_ACTION_OPEN in idle! 216s (process:2402): libfprint-device-DEBUG: 16:48:53.404: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 216s ok 216s test_quick_enroll (__main__.VirtualDeviceStorage.test_quick_enroll) ... (process:2402): libfprint-virtual_device-DEBUG: 16:48:53.404: 104405447: ../libfprint/drivers/virtual-device.c:387 216s (process:2402): libfprint-device-DEBUG: 16:48:53.404: Device reported open completion 216s (process:2402): libfprint-device-DEBUG: 16:48:53.404: Completing action FPI_DEVICE_ACTION_OPEN in idle! 216s (process:2402): libfprint-device-DEBUG: 16:48:53.404: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 216s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:53.404: Got a new connection! 216s (process:2402): libfprint-virtual_device-DEBUG: 16:48:53.404: Got instructions of length 19 216s (process:2402): libfprint-virtual_device-DEBUG: 16:48:53.404: Received command SET_ENROLL_STAGES 1 216s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:53.404: Got a new connection! 216s (process:2402): libfprint-virtual_device-DEBUG: 16:48:53.405: Got instructions of length 14 216s (process:2402): libfprint-virtual_device-DEBUG: 16:48:53.405: Received command SCAN testprint 216s (process:2402): libfprint-device-DEBUG: 16:48:53.405: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 216s (process:2402): libfprint-virtual_device-DEBUG: 16:48:53.405: Processing command SCAN testprint 216s (process:2402): libfprint-device-DEBUG: 16:48:53.405: Device reported finger status change: FP_FINGER_STATUS_NEEDED 216s (process:2402): libfprint-device-DEBUG: 16:48:53.405: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 216s (process:2402): libfprint-device-DEBUG: 16:48:53.405: Device reported finger status change: FP_FINGER_STATUS_NEEDED 216s (process:2402): libfprint-device-DEBUG: 16:48:53.405: Device reported enroll progress, reported 1 of 1 have been completed 216s (process:2402): libfprint-device-DEBUG: 16:48:53.405: Device reported enroll completion 216s (process:2402): libfprint-device-DEBUG: 16:48:53.405: Device reported finger status change: FP_FINGER_STATUS_NONE 216s (process:2402): libfprint-device-DEBUG: 16:48:53.405: Print for finger FP_FINGER_LEFT_LITTLE enrolled 216s (process:2402): libfprint-device-DEBUG: 16:48:53.405: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 216s (process:2402): libfprint-device-DEBUG: 16:48:53.405: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 216s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:53.405: Got a new connection! 216s (process:2402): libfprint-virtual_device-DEBUG: 16:48:53.405: Got instructions of length 5 216s (process:2402): libfprint-virtual_device-DEBUG: 16:48:53.405: Received command CONT 216s (process:2402): libfprint-virtual_device-DEBUG: 16:48:53.405: Processing command CONT 216s (process:2402): libfprint-device-DEBUG: 16:48:53.405: Device reported deletion completion 216s (process:2402): libfprint-device-DEBUG: 16:48:53.405: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 216s (process:2402): libfprint-device-DEBUG: 16:48:53.405: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 216s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:53.405: Got a new connection! 216s (process:2402): libfprint-virtual_device-DEBUG: 16:48:53.405: Got instructions of length 16 216s (process:2402): libfprint-virtual_device-DEBUG: 16:48:53.405: Received command SET_KEEP_ALIVE 0 216s (process:2402): libfprint-virtual_device-DEBUG: 16:48:53.405: Keep alive toggled: 0 216s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:53.405: Got a new connection! 216s (process:2402): libfprint-virtual_device-DEBUG: 16:48:53.405: Got instructions of length 19 216s (process:2402): libfprint-virtual_device-DEBUG: 16:48:53.405: Received command SET_ENROLL_STAGES 5 216s (process:2402): libfprint-device-DEBUG: 16:48:53.405: Device reported close completion 216s (process:2402): libfprint-device-DEBUG: 16:48:53.405: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 216s (process:2402): libfprint-device-DEBUG: 16:48:53.405: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 216s Enroll done 216s ok 216s test_verify_missing_print (__main__.VirtualDeviceStorage.test_verify_missing_print) ... (process:2402): libfprint-virtual_device-DEBUG: 16:48:53.405: 104406406: ../libfprint/drivers/virtual-device.c:387 216s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:53.405: 104406413: ../libfprint/drivers/virtual-device-listener.c:153 216s (process:2402): libfprint-device-DEBUG: 16:48:53.405: Device reported open completion 216s (process:2402): libfprint-device-DEBUG: 16:48:53.405: Completing action FPI_DEVICE_ACTION_OPEN in idle! 216s (process:2402): libfprint-device-DEBUG: 16:48:53.405: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 216s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:53.405: Got a new connection! 216s (process:2402): libfprint-virtual_device-DEBUG: 16:48:53.405: Got instructions of length 23 216s (process:2402): libfprint-virtual_device-DEBUG: 16:48:53.405: Received command SCAN not-existing-print 216s (process:2402): libfprint-device-DEBUG: 16:48:53.405: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 216s (process:2402): libfprint-virtual_device-DEBUG: 16:48:53.406: Processing command SCAN not-existing-print 216s (process:2402): libfprint-device-DEBUG: 16:48:53.406: Device reported finger status change: FP_FINGER_STATUS_NEEDED 216s (process:2402): libfprint-device-DEBUG: 16:48:53.406: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 216s (process:2402): libfprint-virtual_device-DEBUG: 16:48:53.406: Virtual device scanned print not-existing-print 216s (process:2402): libfprint-device-DEBUG: 16:48:53.406: Device reported verify result 216s (process:2402): libfprint-device-DEBUG: 16:48:53.406: Device reported finger status change: FP_FINGER_STATUS_NEEDED 216s (process:2402): libfprint-device-DEBUG: 16:48:53.406: Device reported verify completion 216s (process:2402): libfprint-device-DEBUG: 16:48:53.406: Device reported finger status change: FP_FINGER_STATUS_NONE 216s (process:2402): libfprint-device-DEBUG: 16:48:53.406: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 216s (process:2402): libfprint-device-DEBUG: 16:48:53.406: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 216s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:53.406: Got a new connection! 216s (process:2402): libfprint-virtual_device-DEBUG: 16:48:53.406: Got instructions of length 5 216s (process:2402): libfprint-virtual_device-DEBUG: 16:48:53.406: Received command CONT 216s (process:2402): libfprint-virtual_device-DEBUG: 16:48:53.406: Processing command CONT 216s (process:2402): libfprint-device-DEBUG: 16:48:53.406: Device reported deletion completion 216s (process:2402): libfprint-device-DEBUG: 16:48:53.406: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 216s (process:2402): libfprint-device-DEBUG: 16:48:53.406: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 216s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:53.406: Got a new connection! 216s (process:2402): libfprint-virtual_device-DEBUG: 16:48:53.406: Got instructions of length 16 216s (process:2402): libfprint-virtual_device-DEBUG: 16:48:53.406: Received command SET_KEEP_ALIVE 0 216s (process:2402): libfprint-virtual_device-DEBUG: 16:48:53.406: Keep alive toggled: 0 216s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:53.406: Got a new connection! 216s (process:2402): libfprint-virtual_device-DEBUG: 16:48:53.406: Got instructions of length 19 216s (process:2402): libfprint-virtual_device-DEBUG: 16:48:53.406: Received command SET_ENROLL_STAGES 5 216s (process:2402): libfprint-device-DEBUG: 16:48:53.406: Device reported close completion 216s (process:2402): libfprint-device-DEBUG: 16:48:53.406: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 216s (process:2402): libfprint-device-DEBUG: 16:48:53.406: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 216s ok 216s (process:2402): libfprint-virtual_device-DEBUG: 16:48:53.406: 104407346: ../libfprint/drivers/virtual-device.c:752 216s test_device_unplug (__main__.VirtualDeviceUnplugging.test_device_unplug) ... (process:2402): libfprint-context-DEBUG: 16:48:53.422: Initializing FpContext (libfprint version 1.94.7+tod1) 216s (process:2402): libfprint-tod-DEBUG: 16:48:53.422: Impossible to load the shared drivers dir Error opening directory “/usr/lib/aarch64-linux-gnu/libfprint-2/tod-1”: No such file or directory 216s (process:2402): libfprint-context-DEBUG: 16:48:53.429: No driver found for USB device 1D6B:0003 216s (process:2402): libfprint-context-DEBUG: 16:48:53.429: No driver found for USB device 0627:0001 216s (process:2402): libfprint-context-DEBUG: 16:48:53.429: No driver found for USB device 1D6B:0002 216s (process:2402): libfprint-context-DEBUG: 16:48:53.429: Found virtual environment device: FP_VIRTUAL_DEVICE, /tmp/libfprint-irruegle/virtual-device.socket 216s (process:2402): libfprint-context-DEBUG: 16:48:53.429: created 216s (process:2402): libfprint-context-DEBUG: 16:48:53.429: Found virtual environment device: FP_VIRTUAL_DEVICE_STORAGE, /tmp/libfprint-nkl_bng_/virtual-device-storage.socket 216s (process:2402): libfprint-context-DEBUG: 16:48:53.429: created 216s (process:2402): libfprint-device-DEBUG: 16:48:53.430: Device reported probe completion 216s (process:2402): libfprint-device-DEBUG: 16:48:53.430: Device reported probe completion 216s (process:2402): libfprint-device-DEBUG: 16:48:53.430: Completing action FPI_DEVICE_ACTION_PROBE in idle! 216s (process:2402): libfprint-device-DEBUG: 16:48:53.430: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 216s (process:2402): libfprint-device-DEBUG: 16:48:53.430: Completing action FPI_DEVICE_ACTION_PROBE in idle! 216s (process:2402): libfprint-device-DEBUG: 16:48:53.430: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 216s (process:2402): libfprint-virtual_device-DEBUG: 16:48:53.430: 104430815: ../libfprint/drivers/virtual-device.c:387 216s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:53.430: 104430823: ../libfprint/drivers/virtual-device-listener.c:153 216s (process:2402): libfprint-device-DEBUG: 16:48:53.430: Device reported open completion 216s (process:2402): libfprint-device-DEBUG: 16:48:53.430: Completing action FPI_DEVICE_ACTION_OPEN in idle! 216s (process:2402): libfprint-device-DEBUG: 16:48:53.430: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 216s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:53.435: Got a new connection! 216s (process:2402): libfprint-virtual_device-DEBUG: 16:48:53.435: Got instructions of length 7 216s (process:2402): libfprint-virtual_device-DEBUG: 16:48:53.435: Received command UNPLUG 216s (process:2402): libfprint-device-DEBUG: 16:48:53.435: Device reported close completion 216s (process:2402): libfprint-device-DEBUG: 16:48:53.435: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 216s (process:2402): libfprint-device-DEBUG: 16:48:53.435: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 216s (process:2402): libfprint-virtual_device-DEBUG: 16:48:53.435: 104436687: ../libfprint/drivers/virtual-device.c:752 216s (process:2402): libfprint-virtual_device_storage-DEBUG: 16:48:53.436: 104436702: ../libfprint/drivers/virtual-device-storage.c:253 216s (process:2402): libfprint-virtual_device-DEBUG: 16:48:53.436: 104436709: ../libfprint/drivers/virtual-device.c:752 216s ok 216s test_device_unplug_during_verify (__main__.VirtualDeviceUnplugging.test_device_unplug_during_verify) ... (process:2402): libfprint-context-DEBUG: 16:48:53.436: Initializing FpContext (libfprint version 1.94.7+tod1) 216s (process:2402): libfprint-tod-DEBUG: 16:48:53.436: Impossible to load the shared drivers dir Error opening directory “/usr/lib/aarch64-linux-gnu/libfprint-2/tod-1”: No such file or directory 216s (process:2402): libfprint-context-DEBUG: 16:48:53.437: No driver found for USB device 1D6B:0003 216s (process:2402): libfprint-context-DEBUG: 16:48:53.437: No driver found for USB device 0627:0001 216s (process:2402): libfprint-context-DEBUG: 16:48:53.437: No driver found for USB device 1D6B:0002 216s (process:2402): libfprint-context-DEBUG: 16:48:53.438: Found virtual environment device: FP_VIRTUAL_DEVICE, /tmp/libfprint-irruegle/virtual-device.socket 216s (process:2402): libfprint-context-DEBUG: 16:48:53.438: created 216s (process:2402): libfprint-context-DEBUG: 16:48:53.438: Found virtual environment device: FP_VIRTUAL_DEVICE_STORAGE, /tmp/libfprint-nkl_bng_/virtual-device-storage.socket 216s (process:2402): libfprint-context-DEBUG: 16:48:53.438: created 216s (process:2402): libfprint-device-DEBUG: 16:48:53.438: Device reported probe completion 216s (process:2402): libfprint-device-DEBUG: 16:48:53.438: Device reported probe completion 216s (process:2402): libfprint-device-DEBUG: 16:48:53.438: Completing action FPI_DEVICE_ACTION_PROBE in idle! 216s (process:2402): libfprint-device-DEBUG: 16:48:53.438: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 216s (process:2402): libfprint-device-DEBUG: 16:48:53.438: Completing action FPI_DEVICE_ACTION_PROBE in idle! 216s (process:2402): libfprint-device-DEBUG: 16:48:53.438: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 216s (process:2402): libfprint-virtual_device-DEBUG: 16:48:53.438: 104439577: ../libfprint/drivers/virtual-device.c:387 216s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:53.438: 104439588: ../libfprint/drivers/virtual-device-listener.c:153 216s (process:2402): libfprint-device-DEBUG: 16:48:53.438: Device reported open completion 216s (process:2402): libfprint-device-DEBUG: 16:48:53.438: Completing action FPI_DEVICE_ACTION_OPEN in idle! 216s (process:2402): libfprint-device-DEBUG: 16:48:53.438: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 216s (process:2402): libfprint-device-DEBUG: 16:48:53.439: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 216s (process:2402): libfprint-device-DEBUG: 16:48:53.439: Device reported finger status change: FP_FINGER_STATUS_NEEDED 216s (process:2402): libfprint-virtual_device_connection-DEBUG: 16:48:53.439: Got a new connection! 216s (process:2402): libfprint-virtual_device-DEBUG: 16:48:53.439: Got instructions of length 7 216s (process:2402): libfprint-virtual_device-DEBUG: 16:48:53.439: Received command UNPLUG 216s (process:2402): libfprint-device-DEBUG: 16:48:53.539: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 216s (process:2402): libfprint-device-DEBUG: 16:48:53.940: Device reported generic error (No commands arrived in time to run!) during action; action was: FPI_DEVICE_ACTION_VERIFY 216s (process:2402): libfprint-device-DEBUG: 16:48:53.940: Device reported verify completion 216s (process:2402): libfprint-device-DEBUG: 16:48:53.940: Device reported finger status change: FP_FINGER_STATUS_NONE 216s (process:2402): libfprint-device-DEBUG: 16:48:53.940: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 216s (process:2402): libfprint-device-DEBUG: 16:48:53.940: Updated temperature model after 0.40 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 216s (process:2402): libfprint-device-DEBUG: 16:48:53.940: Device reported close completion 216s (process:2402): libfprint-device-DEBUG: 16:48:53.940: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 216s (process:2402): libfprint-device-DEBUG: 16:48:53.940: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 216s (process:2402): libfprint-virtual_device-DEBUG: 16:48:53.940: 104941261: ../libfprint/drivers/virtual-device.c:752 216s (process:2402): libfprint-virtual_device_storage-DEBUG: 16:48:53.940: 104941281: ../libfprint/drivers/virtual-device-storage.c:253 216s (process:2402): libfprint-virtual_device-DEBUG: 16:48:53.940: 104941287: ../libfprint/drivers/virtual-device.c:752 216s ok 216s 216s ---------------------------------------------------------------------- 216s Ran 86 tests in 17.830s 216s 216s OK (skipped=1) 217s Executing: libfprint-2/virtual-device.test 217s PASS: libfprint-2/virtual-device.test 217s Running test: libfprint-2/fpi-assembling.test 217s TAP version 13 217s # random seed: R02Sc69acaaac0ec6e526e6d1c1759e0f90f 217s 1..1 217s # Start of assembling tests 217s # libfprint-assembling-DEBUG: calc delta completed in 0.098591 secs 217s # libfprint-assembling-DEBUG: calc delta completed in 0.098454 secs 217s # libfprint-assembling-DEBUG: errors: 0 rev: 130848 217s # libfprint-assembling-DEBUG: calc delta completed in 0.099025 secs 217s # libfprint-assembling-DEBUG: height is 310 217s ok 1 /assembling/frames 217s # End of assembling tests 217s PASS: libfprint-2/fpi-assembling.test 217s Running test: libfprint-2/virtual-image.test 217s (process:2420): libfprint-context-DEBUG: 16:48:54.483: Initializing FpContext (libfprint version 1.94.7+tod1) 217s (process:2420): libfprint-tod-DEBUG: 16:48:54.483: Impossible to load the shared drivers dir Error opening directory “/usr/lib/aarch64-linux-gnu/libfprint-2/tod-1”: No such file or directory 217s (process:2420): libfprint-context-DEBUG: 16:48:54.485: No driver found for USB device 1D6B:0003 217s (process:2420): libfprint-context-DEBUG: 16:48:54.485: No driver found for USB device 0627:0001 217s (process:2420): libfprint-context-DEBUG: 16:48:54.485: No driver found for USB device 1D6B:0002 217s (process:2420): libfprint-context-DEBUG: 16:48:54.485: Found virtual environment device: FP_VIRTUAL_IMAGE, /tmp/libfprint-hgc8_5ax/virtual-image.socket 217s (process:2420): libfprint-context-DEBUG: 16:48:54.486: created 217s (process:2420): libfprint-device-DEBUG: 16:48:54.486: Device reported probe completion 217s (process:2420): libfprint-device-DEBUG: 16:48:54.486: Completing action FPI_DEVICE_ACTION_PROBE in idle! 217s (process:2420): libfprint-device-DEBUG: 16:48:54.486: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 217s test_capture_prevents_close (__main__.VirtualImage.test_capture_prevents_close) ... (process:2420): libfprint-virtual_image-DEBUG: 16:48:54.519: 105519898: ../libfprint/drivers/virtual-image.c:216 217s (process:2420): libfprint-virtual_device_connection-DEBUG: 16:48:54.519: 105519985: ../libfprint/drivers/virtual-device-listener.c:153 217s (process:2420): libfprint-image_device-DEBUG: 16:48:54.619: Image device open completed 217s (process:2420): libfprint-device-DEBUG: 16:48:54.619: Device reported open completion 217s (process:2420): libfprint-device-DEBUG: 16:48:54.619: Completing action FPI_DEVICE_ACTION_OPEN in idle! 217s (process:2420): libfprint-device-DEBUG: 16:48:54.619: Updated temperature model after 0.13 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 217s (process:2420): libfprint-device-DEBUG: 16:48:54.630: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 217s (process:2420): libfprint-image_device-DEBUG: 16:48:54.630: Activating image device 217s (process:2420): libfprint-image_device-DEBUG: 16:48:54.630: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING 217s (process:2420): libfprint-image_device-DEBUG: 16:48:54.630: Image device activation completed 217s (process:2420): libfprint-image_device-DEBUG: 16:48:54.630: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE 217s (process:2420): libfprint-image_device-DEBUG: 16:48:54.630: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 217s (process:2420): libfprint-device-DEBUG: 16:48:54.630: Device reported finger status change: FP_FINGER_STATUS_NEEDED 217s (process:2420): libfprint-virtual_device_connection-DEBUG: 16:48:54.631: Got a new connection! 217s (process:2420): libfprint-device-DEBUG: 16:48:54.631: Idle cancelling on ongoing operation! 217s (process:2420): libfprint-image_device-DEBUG: 16:48:54.631: Deactivating image device 217s (process:2420): libfprint-image_device-DEBUG: 16:48:54.631: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_DEACTIVATING 217s (process:2420): libfprint-image_device-DEBUG: 16:48:54.631: Image device deactivation completed 217s (process:2420): libfprint-image_device-DEBUG: 16:48:54.631: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE 217s (process:2420): libfprint-device-DEBUG: 16:48:54.631: Device reported generic error (Operation was cancelled) during action; action was: FPI_DEVICE_ACTION_CAPTURE 217s (process:2420): libfprint-device-DEBUG: 16:48:54.631: Device reported capture completion 217s (process:2420): libfprint-device-DEBUG: 16:48:54.631: Device reported finger status change: FP_FINGER_STATUS_NONE 217s (process:2420): libfprint-device-DEBUG: 16:48:54.631: Completing action FPI_DEVICE_ACTION_CAPTURE in idle! 217s (process:2420): libfprint-device-DEBUG: 16:48:54.631: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 217s (process:2420): libfprint-virtual_image-DEBUG: 16:48:54.642: 105643462: ../libfprint/drivers/virtual-image.c:244 217s (process:2420): libfprint-image_device-DEBUG: 16:48:54.743: Image device close completed 217s (process:2420): libfprint-device-DEBUG: 16:48:54.743: Device reported close completion 217s (process:2420): libfprint-device-DEBUG: 16:48:54.743: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 217s (process:2420): libfprint-device-DEBUG: 16:48:54.743: Updated temperature model after 0.11 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 217s Capture operation finished 217s Capture cancelled as expected 217s ok 217s test_enroll_verify (__main__.VirtualImage.test_enroll_verify) ... (process:2420): libfprint-virtual_image-DEBUG: 16:48:54.743: 105744158: ../libfprint/drivers/virtual-image.c:216 217s (process:2420): libfprint-virtual_device_connection-DEBUG: 16:48:54.743: 105744190: ../libfprint/drivers/virtual-device-listener.c:153 217s (process:2420): libfprint-image_device-DEBUG: 16:48:54.843: Image device open completed 217s (process:2420): libfprint-device-DEBUG: 16:48:54.843: Device reported open completion 217s (process:2420): libfprint-device-DEBUG: 16:48:54.843: Completing action FPI_DEVICE_ACTION_OPEN in idle! 217s (process:2420): libfprint-device-DEBUG: 16:48:54.843: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 217s (process:2420): libfprint-device-DEBUG: 16:48:54.845: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 217s (process:2420): libfprint-image_device-DEBUG: 16:48:54.845: Activating image device 217s (process:2420): libfprint-image_device-DEBUG: 16:48:54.845: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING 217s (process:2420): libfprint-image_device-DEBUG: 16:48:54.845: Image device activation completed 217s (process:2420): libfprint-image_device-DEBUG: 16:48:54.845: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE 217s (process:2420): libfprint-image_device-DEBUG: 16:48:54.845: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 217s (process:2420): libfprint-device-DEBUG: 16:48:54.845: Device reported finger status change: FP_FINGER_STATUS_NEEDED 217s (process:2420): libfprint-virtual_device_connection-DEBUG: 16:48:54.845: Got a new connection! 217s (process:2420): libfprint-virtual_image-DEBUG: 16:48:54.845: image data: 0xfa3fe20 217s (process:2420): libfprint-device-DEBUG: 16:48:54.845: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 217s (process:2420): libfprint-image_device-DEBUG: 16:48:54.845: Image device reported finger status: on 217s (process:2420): libfprint-image_device-DEBUG: 16:48:54.845: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 217s (process:2420): libfprint-image_device-DEBUG: 16:48:54.845: Image device captured an image 217s (process:2420): libfprint-image_device-DEBUG: 16:48:54.845: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 217s (process:2420): libfprint-device-DEBUG: 16:48:54.846: Device reported finger status change: FP_FINGER_STATUS_PRESENT 217s (process:2420): libfprint-device-DEBUG: 16:48:54.846: Device reported finger status change: FP_FINGER_STATUS_NONE 217s (process:2420): libfprint-image_device-DEBUG: 16:48:54.846: Image device reported finger status: off 217s (process:2420): libfprint-image_device-DEBUG: 16:48:54.846: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 217s (process:2420): libfprint-image-DEBUG: 16:48:54.869: Minutiae scan completed in 0.023614 secs 217s (process:2420): libfprint-device-DEBUG: 16:48:54.869: Device reported enroll progress, reported 1 of 5 have been completed 217s (process:2420): libfprint-image_device-DEBUG: 16:48:54.869: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 217s (process:2420): libfprint-device-DEBUG: 16:48:54.869: Device reported finger status change: FP_FINGER_STATUS_NEEDED 217s (process:2420): libfprint-device-DEBUG: 16:48:54.870: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 217s (process:2420): libfprint-image_device-DEBUG: 16:48:54.870: Image device reported finger status: on 217s (process:2420): libfprint-image_device-DEBUG: 16:48:54.870: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 217s (process:2420): libfprint-virtual_image-DEBUG: 16:48:54.870: image data: 0xfa3fe20 217s (process:2420): libfprint-image_device-DEBUG: 16:48:54.870: Image device captured an image 217s (process:2420): libfprint-image_device-DEBUG: 16:48:54.870: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 217s (process:2420): libfprint-device-DEBUG: 16:48:54.870: Device reported finger status change: FP_FINGER_STATUS_PRESENT 217s (process:2420): libfprint-image-DEBUG: 16:48:54.893: Minutiae scan completed in 0.022910 secs 217s (process:2420): libfprint-device-DEBUG: 16:48:54.893: Device reported enroll progress, reported 2 of 5 have been completed 217s (process:2420): libfprint-device-DEBUG: 16:48:54.893: Device reported finger status change: FP_FINGER_STATUS_NONE 217s (process:2420): libfprint-image_device-DEBUG: 16:48:54.893: Image device reported finger status: off 217s (process:2420): libfprint-image_device-DEBUG: 16:48:54.893: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 217s (process:2420): libfprint-image_device-DEBUG: 16:48:54.893: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 217s (process:2420): libfprint-device-DEBUG: 16:48:54.893: Device reported finger status change: FP_FINGER_STATUS_NEEDED 217s (process:2420): libfprint-virtual_image-DEBUG: 16:48:54.894: image data: 0xfa3fe20 217s (process:2420): libfprint-device-DEBUG: 16:48:54.894: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 217s (process:2420): libfprint-image_device-DEBUG: 16:48:54.894: Image device reported finger status: on 217s (process:2420): libfprint-image_device-DEBUG: 16:48:54.894: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 217s (process:2420): libfprint-image_device-DEBUG: 16:48:54.894: Image device captured an image 217s (process:2420): libfprint-image_device-DEBUG: 16:48:54.894: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 217s (process:2420): libfprint-device-DEBUG: 16:48:54.894: Device reported finger status change: FP_FINGER_STATUS_PRESENT 217s (process:2420): libfprint-device-DEBUG: 16:48:54.894: Device reported finger status change: FP_FINGER_STATUS_NONE 217s (process:2420): libfprint-image_device-DEBUG: 16:48:54.894: Image device reported finger status: off 217s (process:2420): libfprint-image_device-DEBUG: 16:48:54.894: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 217s (process:2420): libfprint-image-DEBUG: 16:48:54.917: Minutiae scan completed in 0.023089 secs 217s (process:2420): libfprint-device-DEBUG: 16:48:54.917: Device reported enroll progress, reported 3 of 5 have been completed 217s (process:2420): libfprint-image_device-DEBUG: 16:48:54.917: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 217s (process:2420): libfprint-device-DEBUG: 16:48:54.917: Device reported finger status change: FP_FINGER_STATUS_NEEDED 217s (process:2420): libfprint-virtual_image-DEBUG: 16:48:54.917: image data: 0xfa3fe20 217s (process:2420): libfprint-device-DEBUG: 16:48:54.917: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 217s (process:2420): libfprint-image_device-DEBUG: 16:48:54.917: Image device reported finger status: on 217s (process:2420): libfprint-image_device-DEBUG: 16:48:54.917: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 217s (process:2420): libfprint-image_device-DEBUG: 16:48:54.917: Image device captured an image 217s (process:2420): libfprint-image_device-DEBUG: 16:48:54.917: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 217s (process:2420): libfprint-device-DEBUG: 16:48:54.917: Device reported finger status change: FP_FINGER_STATUS_PRESENT 217s (process:2420): libfprint-device-DEBUG: 16:48:54.917: Device reported finger status change: FP_FINGER_STATUS_NONE 217s (process:2420): libfprint-image_device-DEBUG: 16:48:54.918: Image device reported finger status: off 217s (process:2420): libfprint-image_device-DEBUG: 16:48:54.918: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 217s (process:2420): libfprint-image-DEBUG: 16:48:54.941: Minutiae scan completed in 0.023376 secs 217s (process:2420): libfprint-device-DEBUG: 16:48:54.941: Device reported enroll progress, reported 4 of 5 have been completed 217s (process:2420): libfprint-image_device-DEBUG: 16:48:54.941: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 217s (process:2420): libfprint-device-DEBUG: 16:48:54.941: Device reported finger status change: FP_FINGER_STATUS_NEEDED 217s (process:2420): libfprint-virtual_image-DEBUG: 16:48:54.941: image data: 0xfa3fe20 217s (process:2420): libfprint-device-DEBUG: 16:48:54.941: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 217s (process:2420): libfprint-image_device-DEBUG: 16:48:54.941: Image device reported finger status: on 217s (process:2420): libfprint-image_device-DEBUG: 16:48:54.942: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 217s (process:2420): libfprint-image_device-DEBUG: 16:48:54.942: Image device captured an image 217s (process:2420): libfprint-image_device-DEBUG: 16:48:54.942: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 217s (process:2420): libfprint-device-DEBUG: 16:48:54.942: Device reported finger status change: FP_FINGER_STATUS_PRESENT 217s (process:2420): libfprint-device-DEBUG: 16:48:54.942: Device reported finger status change: FP_FINGER_STATUS_NONE 217s (process:2420): libfprint-image_device-DEBUG: 16:48:54.942: Image device reported finger status: off 217s (process:2420): libfprint-image_device-DEBUG: 16:48:54.942: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 217s (process:2420): libfprint-image-DEBUG: 16:48:54.965: Minutiae scan completed in 0.022971 secs 217s (process:2420): libfprint-device-DEBUG: 16:48:54.965: Device reported enroll progress, reported 5 of 5 have been completed 217s (process:2420): libfprint-image_device-DEBUG: 16:48:54.965: Deactivating image device 217s (process:2420): libfprint-image_device-DEBUG: 16:48:54.965: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_DEACTIVATING 217s (process:2420): libfprint-image_device-DEBUG: 16:48:54.965: Image device deactivation completed 217s (process:2420): libfprint-image_device-DEBUG: 16:48:54.965: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE 217s (process:2420): libfprint-device-DEBUG: 16:48:54.965: Device reported enroll completion 217s (process:2420): libfprint-device-DEBUG: 16:48:54.965: Print for finger FP_FINGER_LEFT_THUMB enrolled 217s (process:2420): libfprint-device-DEBUG: 16:48:54.965: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 217s (process:2420): libfprint-device-DEBUG: 16:48:54.965: Updated temperature model after 0.12 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 217s (process:2420): libfprint-device-DEBUG: 16:48:54.965: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 217s (process:2420): libfprint-image_device-DEBUG: 16:48:54.965: Activating image device 217s (process:2420): libfprint-image_device-DEBUG: 16:48:54.965: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING 217s (process:2420): libfprint-image_device-DEBUG: 16:48:54.965: Image device activation completed 217s (process:2420): libfprint-image_device-DEBUG: 16:48:54.965: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE 217s (process:2420): libfprint-image_device-DEBUG: 16:48:54.965: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 217s (process:2420): libfprint-device-DEBUG: 16:48:54.965: Device reported finger status change: FP_FINGER_STATUS_NEEDED 217s (process:2420): libfprint-virtual_image-DEBUG: 16:48:54.965: image data: 0xfa4e6b0 217s (process:2420): libfprint-device-DEBUG: 16:48:54.965: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 217s (process:2420): libfprint-image_device-DEBUG: 16:48:54.966: Image device reported finger status: on 217s (process:2420): libfprint-image_device-DEBUG: 16:48:54.966: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 217s (process:2420): libfprint-image_device-DEBUG: 16:48:54.966: Image device captured an image 217s (process:2420): libfprint-image_device-DEBUG: 16:48:54.966: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 217s (process:2420): libfprint-device-DEBUG: 16:48:54.966: Device reported finger status change: FP_FINGER_STATUS_PRESENT 217s (process:2420): libfprint-device-DEBUG: 16:48:54.966: Device reported finger status change: FP_FINGER_STATUS_NONE 217s (process:2420): libfprint-image_device-DEBUG: 16:48:54.966: Image device reported finger status: off 217s (process:2420): libfprint-image_device-DEBUG: 16:48:54.966: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 217s (process:2420): libfprint-image_device-DEBUG: 16:48:54.966: Deactivating image device 217s (process:2420): libfprint-image_device-DEBUG: 16:48:54.966: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_DEACTIVATING 217s (process:2420): libfprint-image_device-DEBUG: 16:48:54.966: Image device deactivation completed 217s (process:2420): libfprint-image_device-DEBUG: 16:48:54.966: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE 218s (process:2420): libfprint-image-DEBUG: 16:48:54.989: Minutiae scan completed in 0.022930 secs 219s (process:2420): libfprint-print-DEBUG: 16:48:56.105: score 1093/40 219s (process:2420): libfprint-device-DEBUG: 16:48:56.132: Device reported verify result 219s (process:2420): libfprint-device-DEBUG: 16:48:56.145: Device reported verify completion 219s (process:2420): libfprint-device-DEBUG: 16:48:56.177: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 219s (process:2420): libfprint-device-DEBUG: 16:48:56.178: Updated temperature model after 1.21 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 219s (process:2420): libfprint-device-DEBUG: 16:48:56.207: Updated temperature model after 0.03 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 219s (process:2420): libfprint-image_device-DEBUG: 16:48:56.207: Activating image device 219s (process:2420): libfprint-image_device-DEBUG: 16:48:56.207: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING 219s (process:2420): libfprint-image_device-DEBUG: 16:48:56.207: Image device activation completed 219s (process:2420): libfprint-image_device-DEBUG: 16:48:56.207: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE 219s (process:2420): libfprint-image_device-DEBUG: 16:48:56.207: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 219s (process:2420): libfprint-device-DEBUG: 16:48:56.207: Device reported finger status change: FP_FINGER_STATUS_NEEDED 219s (process:2420): libfprint-virtual_image-DEBUG: 16:48:56.224: image data: 0xfa5de90 219s (process:2420): libfprint-device-DEBUG: 16:48:56.224: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 219s (process:2420): libfprint-image_device-DEBUG: 16:48:56.224: Image device reported finger status: on 219s (process:2420): libfprint-image_device-DEBUG: 16:48:56.224: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 219s (process:2420): libfprint-image_device-DEBUG: 16:48:56.224: Image device captured an image 219s (process:2420): libfprint-image_device-DEBUG: 16:48:56.224: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 219s (process:2420): libfprint-device-DEBUG: 16:48:56.224: Device reported finger status change: FP_FINGER_STATUS_PRESENT 219s (process:2420): libfprint-device-DEBUG: 16:48:56.224: Device reported finger status change: FP_FINGER_STATUS_NONE 219s (process:2420): libfprint-image_device-DEBUG: 16:48:56.224: Image device reported finger status: off 219s (process:2420): libfprint-image_device-DEBUG: 16:48:56.224: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 219s (process:2420): libfprint-image_device-DEBUG: 16:48:56.224: Deactivating image device 219s (process:2420): libfprint-image_device-DEBUG: 16:48:56.224: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_DEACTIVATING 219s (process:2420): libfprint-image_device-DEBUG: 16:48:56.224: Image device deactivation completed 219s (process:2420): libfprint-image_device-DEBUG: 16:48:56.224: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE 219s (process:2420): libfprint-image-DEBUG: 16:48:56.250: Minutiae scan completed in 0.026194 secs 219s (process:2420): libfprint-print-DEBUG: 16:48:56.257: score 10/40 219s (process:2420): libfprint-print-DEBUG: 16:48:56.262: score 10/40 219s (process:2420): libfprint-print-DEBUG: 16:48:56.268: score 10/40 219s (process:2420): libfprint-print-DEBUG: 16:48:56.273: score 10/40 219s (process:2420): libfprint-print-DEBUG: 16:48:56.279: score 10/40 219s (process:2420): libfprint-device-DEBUG: 16:48:56.279: Device reported verify result 219s (process:2420): libfprint-device-DEBUG: 16:48:56.279: Device reported verify completion 219s (process:2420): libfprint-device-DEBUG: 16:48:56.279: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 219s (process:2420): libfprint-device-DEBUG: 16:48:56.279: Updated temperature model after 0.07 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 219s (process:2420): libfprint-device-DEBUG: 16:48:56.279: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 219s (process:2420): libfprint-image_device-DEBUG: 16:48:56.280: Activating image device 219s (process:2420): libfprint-image_device-DEBUG: 16:48:56.280: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING 219s (process:2420): libfprint-image_device-DEBUG: 16:48:56.280: Image device activation completed 219s (process:2420): libfprint-image_device-DEBUG: 16:48:56.280: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE 219s (process:2420): libfprint-image_device-DEBUG: 16:48:56.280: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 219s (process:2420): libfprint-device-DEBUG: 16:48:56.280: Device reported finger status change: FP_FINGER_STATUS_NEEDED 219s (process:2420): libfprint-virtual_image-DEBUG: 16:48:56.280: image data: 0xfa6cea0 219s (process:2420): libfprint-device-DEBUG: 16:48:56.280: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 219s (process:2420): libfprint-image_device-DEBUG: 16:48:56.280: Image device reported finger status: on 219s (process:2420): libfprint-image_device-DEBUG: 16:48:56.280: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 219s (process:2420): libfprint-image_device-DEBUG: 16:48:56.280: Image device captured an image 219s (process:2420): libfprint-image_device-DEBUG: 16:48:56.280: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 219s (process:2420): libfprint-device-DEBUG: 16:48:56.280: Device reported finger status change: FP_FINGER_STATUS_PRESENT 219s (process:2420): libfprint-device-DEBUG: 16:48:56.280: Device reported finger status change: FP_FINGER_STATUS_NONE 219s (process:2420): libfprint-image_device-DEBUG: 16:48:56.280: Image device reported finger status: off 219s (process:2420): libfprint-image_device-DEBUG: 16:48:56.280: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 219s (process:2420): libfprint-image-DEBUG: 16:48:56.300: Minutiae scan completed in 0.020377 secs 219s (process:2420): libfprint-device-DEBUG: 16:48:56.301: Device reported enroll progress, reported 1 of 5 have been completed 219s (process:2420): libfprint-image_device-DEBUG: 16:48:56.301: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 219s (process:2420): libfprint-device-DEBUG: 16:48:56.301: Device reported finger status change: FP_FINGER_STATUS_NEEDED 219s (process:2420): libfprint-device-DEBUG: 16:48:56.301: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 219s (process:2420): libfprint-image_device-DEBUG: 16:48:56.301: Image device reported finger status: on 219s (process:2420): libfprint-image_device-DEBUG: 16:48:56.301: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 219s (process:2420): libfprint-virtual_image-DEBUG: 16:48:56.301: image data: 0xfa6cea0 219s (process:2420): libfprint-image_device-DEBUG: 16:48:56.301: Image device captured an image 219s (process:2420): libfprint-image_device-DEBUG: 16:48:56.301: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 219s (process:2420): libfprint-device-DEBUG: 16:48:56.301: Device reported finger status change: FP_FINGER_STATUS_PRESENT 219s (process:2420): libfprint-image-DEBUG: 16:48:56.321: Minutiae scan completed in 0.020397 secs 219s (process:2420): libfprint-device-DEBUG: 16:48:56.322: Device reported enroll progress, reported 2 of 5 have been completed 219s (process:2420): libfprint-device-DEBUG: 16:48:56.322: Device reported finger status change: FP_FINGER_STATUS_NONE 219s (process:2420): libfprint-image_device-DEBUG: 16:48:56.322: Image device reported finger status: off 219s (process:2420): libfprint-image_device-DEBUG: 16:48:56.322: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 219s (process:2420): libfprint-image_device-DEBUG: 16:48:56.322: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 219s (process:2420): libfprint-device-DEBUG: 16:48:56.322: Device reported finger status change: FP_FINGER_STATUS_NEEDED 219s (process:2420): libfprint-virtual_image-DEBUG: 16:48:56.322: image data: 0xfa6cea0 219s (process:2420): libfprint-device-DEBUG: 16:48:56.322: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 219s (process:2420): libfprint-image_device-DEBUG: 16:48:56.322: Image device reported finger status: on 219s (process:2420): libfprint-image_device-DEBUG: 16:48:56.322: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 219s (process:2420): libfprint-image_device-DEBUG: 16:48:56.322: Image device captured an image 219s (process:2420): libfprint-image_device-DEBUG: 16:48:56.322: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 219s (process:2420): libfprint-device-DEBUG: 16:48:56.322: Device reported finger status change: FP_FINGER_STATUS_PRESENT 219s (process:2420): libfprint-device-DEBUG: 16:48:56.322: Device reported finger status change: FP_FINGER_STATUS_NONE 219s (process:2420): libfprint-image_device-DEBUG: 16:48:56.322: Image device reported finger status: off 219s (process:2420): libfprint-image_device-DEBUG: 16:48:56.322: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 219s (process:2420): libfprint-image-DEBUG: 16:48:56.342: Minutiae scan completed in 0.020352 secs 219s (process:2420): libfprint-device-DEBUG: 16:48:56.343: Device reported enroll progress, reported 3 of 5 have been completed 219s (process:2420): libfprint-image_device-DEBUG: 16:48:56.343: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 219s (process:2420): libfprint-device-DEBUG: 16:48:56.343: Device reported finger status change: FP_FINGER_STATUS_NEEDED 219s (process:2420): libfprint-virtual_image-DEBUG: 16:48:56.343: image data: 0xfa6cea0 219s (process:2420): libfprint-device-DEBUG: 16:48:56.343: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 219s (process:2420): libfprint-image_device-DEBUG: 16:48:56.343: Image device reported finger status: on 219s (process:2420): libfprint-image_device-DEBUG: 16:48:56.343: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 219s (process:2420): libfprint-image_device-DEBUG: 16:48:56.343: Image device captured an image 219s (process:2420): libfprint-image_device-DEBUG: 16:48:56.343: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 219s (process:2420): libfprint-device-DEBUG: 16:48:56.343: Device reported finger status change: FP_FINGER_STATUS_PRESENT 219s (process:2420): libfprint-device-DEBUG: 16:48:56.343: Device reported finger status change: FP_FINGER_STATUS_NONE 219s (process:2420): libfprint-image_device-DEBUG: 16:48:56.343: Image device reported finger status: off 219s (process:2420): libfprint-image_device-DEBUG: 16:48:56.343: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 219s (process:2420): libfprint-image-DEBUG: 16:48:56.364: Minutiae scan completed in 0.020735 secs 219s (process:2420): libfprint-device-DEBUG: 16:48:56.364: Device reported enroll progress, reported 4 of 5 have been completed 219s (process:2420): libfprint-image_device-DEBUG: 16:48:56.364: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 219s (process:2420): libfprint-device-DEBUG: 16:48:56.364: Device reported finger status change: FP_FINGER_STATUS_NEEDED 219s (process:2420): libfprint-virtual_image-DEBUG: 16:48:56.364: image data: 0xfa6cea0 219s (process:2420): libfprint-device-DEBUG: 16:48:56.364: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 219s (process:2420): libfprint-image_device-DEBUG: 16:48:56.364: Image device reported finger status: on 219s (process:2420): libfprint-image_device-DEBUG: 16:48:56.364: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 219s (process:2420): libfprint-image_device-DEBUG: 16:48:56.364: Image device captured an image 219s (process:2420): libfprint-image_device-DEBUG: 16:48:56.364: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 219s (process:2420): libfprint-device-DEBUG: 16:48:56.364: Device reported finger status change: FP_FINGER_STATUS_PRESENT 219s (process:2420): libfprint-device-DEBUG: 16:48:56.364: Device reported finger status change: FP_FINGER_STATUS_NONE 219s (process:2420): libfprint-image_device-DEBUG: 16:48:56.364: Image device reported finger status: off 219s (process:2420): libfprint-image_device-DEBUG: 16:48:56.364: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 219s (process:2420): libfprint-image-DEBUG: 16:48:56.385: Minutiae scan completed in 0.020583 secs 219s (process:2420): libfprint-device-DEBUG: 16:48:56.385: Device reported enroll progress, reported 5 of 5 have been completed 219s (process:2420): libfprint-image_device-DEBUG: 16:48:56.385: Deactivating image device 219s (process:2420): libfprint-image_device-DEBUG: 16:48:56.385: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_DEACTIVATING 219s (process:2420): libfprint-image_device-DEBUG: 16:48:56.385: Image device deactivation completed 219s (process:2420): libfprint-image_device-DEBUG: 16:48:56.385: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE 219s (process:2420): libfprint-device-DEBUG: 16:48:56.385: Device reported enroll completion 219s (process:2420): libfprint-device-DEBUG: 16:48:56.385: Print for finger FP_FINGER_LEFT_THUMB enrolled 219s (process:2420): libfprint-device-DEBUG: 16:48:56.385: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 219s (process:2420): libfprint-device-DEBUG: 16:48:56.385: Updated temperature model after 0.11 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 219s (process:2420): libfprint-device-DEBUG: 16:48:56.385: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 219s (process:2420): libfprint-image_device-DEBUG: 16:48:56.385: Activating image device 219s (process:2420): libfprint-image_device-DEBUG: 16:48:56.385: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING 219s (process:2420): libfprint-image_device-DEBUG: 16:48:56.385: Image device activation completed 219s (process:2420): libfprint-image_device-DEBUG: 16:48:56.385: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE 219s (process:2420): libfprint-image_device-DEBUG: 16:48:56.385: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 219s (process:2420): libfprint-device-DEBUG: 16:48:56.385: Device reported finger status change: FP_FINGER_STATUS_NEEDED 219s (process:2420): libfprint-virtual_image-DEBUG: 16:48:56.385: image data: 0xfa4e6b0 219s (process:2420): libfprint-device-DEBUG: 16:48:56.385: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 219s (process:2420): libfprint-image_device-DEBUG: 16:48:56.385: Image device reported finger status: on 219s (process:2420): libfprint-image_device-DEBUG: 16:48:56.385: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 219s (process:2420): libfprint-image_device-DEBUG: 16:48:56.385: Image device captured an image 219s (process:2420): libfprint-image_device-DEBUG: 16:48:56.385: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 219s (process:2420): libfprint-device-DEBUG: 16:48:56.385: Device reported finger status change: FP_FINGER_STATUS_PRESENT 219s (process:2420): libfprint-device-DEBUG: 16:48:56.385: Device reported finger status change: FP_FINGER_STATUS_NONE 219s (process:2420): libfprint-image_device-DEBUG: 16:48:56.385: Image device reported finger status: off 219s (process:2420): libfprint-image_device-DEBUG: 16:48:56.385: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 219s (process:2420): libfprint-image_device-DEBUG: 16:48:56.385: Deactivating image device 219s (process:2420): libfprint-image_device-DEBUG: 16:48:56.385: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_DEACTIVATING 219s (process:2420): libfprint-image_device-DEBUG: 16:48:56.385: Image device deactivation completed 219s (process:2420): libfprint-image_device-DEBUG: 16:48:56.385: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE 219s (process:2420): libfprint-image-DEBUG: 16:48:56.408: Minutiae scan completed in 0.022912 secs 220s (process:2420): libfprint-print-DEBUG: 16:48:57.412: score 1093/40 220s (process:2420): libfprint-device-DEBUG: 16:48:57.429: Device reported verify result 220s (process:2420): libfprint-device-DEBUG: 16:48:57.429: Device reported verify completion 220s (process:2420): libfprint-device-DEBUG: 16:48:57.498: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 220s (process:2420): libfprint-device-DEBUG: 16:48:57.498: Updated temperature model after 1.11 seconds, ratio 0.27 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 220s (process:2420): libfprint-device-DEBUG: 16:48:57.551: Updated temperature model after 0.05 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 220s (process:2420): libfprint-image_device-DEBUG: 16:48:57.551: Activating image device 220s (process:2420): libfprint-image_device-DEBUG: 16:48:57.551: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING 220s (process:2420): libfprint-image_device-DEBUG: 16:48:57.552: Image device activation completed 220s (process:2420): libfprint-image_device-DEBUG: 16:48:57.552: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE 220s (process:2420): libfprint-image_device-DEBUG: 16:48:57.552: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 220s (process:2420): libfprint-device-DEBUG: 16:48:57.552: Device reported finger status change: FP_FINGER_STATUS_NEEDED 220s (process:2420): libfprint-virtual_image-DEBUG: 16:48:57.552: image data: 0xfa5de90 220s (process:2420): libfprint-device-DEBUG: 16:48:57.552: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 220s (process:2420): libfprint-image_device-DEBUG: 16:48:57.552: Image device reported finger status: on 220s (process:2420): libfprint-image_device-DEBUG: 16:48:57.552: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 220s (process:2420): libfprint-image_device-DEBUG: 16:48:57.552: Image device captured an image 220s (process:2420): libfprint-image_device-DEBUG: 16:48:57.552: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 220s (process:2420): libfprint-device-DEBUG: 16:48:57.552: Device reported finger status change: FP_FINGER_STATUS_PRESENT 220s (process:2420): libfprint-device-DEBUG: 16:48:57.552: Device reported finger status change: FP_FINGER_STATUS_NONE 220s (process:2420): libfprint-image_device-DEBUG: 16:48:57.552: Image device reported finger status: off 220s (process:2420): libfprint-image_device-DEBUG: 16:48:57.552: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 220s (process:2420): libfprint-image_device-DEBUG: 16:48:57.552: Deactivating image device 220s (process:2420): libfprint-image_device-DEBUG: 16:48:57.552: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_DEACTIVATING 220s (process:2420): libfprint-image_device-DEBUG: 16:48:57.552: Image device deactivation completed 220s (process:2420): libfprint-image_device-DEBUG: 16:48:57.552: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE 220s (process:2420): libfprint-image-DEBUG: 16:48:57.573: Minutiae scan completed in 0.020705 secs 220s (process:2420): libfprint-print-DEBUG: 16:48:57.579: score 10/40 220s (process:2420): libfprint-print-DEBUG: 16:48:57.584: score 10/40 220s (process:2420): libfprint-print-DEBUG: 16:48:57.590: score 10/40 220s (process:2420): libfprint-print-DEBUG: 16:48:57.595: score 10/40 220s (process:2420): libfprint-print-DEBUG: 16:48:57.600: score 10/40 220s (process:2420): libfprint-print-DEBUG: 16:48:57.821: score 855/40 220s (process:2420): libfprint-device-DEBUG: 16:48:57.821: Device reported verify result 220s (process:2420): libfprint-device-DEBUG: 16:48:57.821: Device reported verify completion 220s (process:2420): libfprint-device-DEBUG: 16:48:57.821: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 220s (process:2420): libfprint-device-DEBUG: 16:48:57.821: Updated temperature model after 0.27 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 220s (process:2420): libfprint-device-DEBUG: 16:48:57.821: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 220s (process:2420): libfprint-image_device-DEBUG: 16:48:57.821: Activating image device 220s (process:2420): libfprint-image_device-DEBUG: 16:48:57.821: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING 220s (process:2420): libfprint-image_device-DEBUG: 16:48:57.821: Image device activation completed 220s (process:2420): libfprint-image_device-DEBUG: 16:48:57.821: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE 220s (process:2420): libfprint-image_device-DEBUG: 16:48:57.821: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 220s (process:2420): libfprint-device-DEBUG: 16:48:57.821: Device reported finger status change: FP_FINGER_STATUS_NEEDED 220s (process:2420): libfprint-device-DEBUG: 16:48:57.822: Device reported verify result 220s (process:2420): libfprint-image_device-DEBUG: 16:48:57.822: Deactivating image device 220s (process:2420): libfprint-image_device-DEBUG: 16:48:57.822: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_DEACTIVATING 220s (process:2420): libfprint-image_device-DEBUG: 16:48:57.822: Image device deactivation completed 220s (process:2420): libfprint-image_device-DEBUG: 16:48:57.822: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE 220s (process:2420): libfprint-device-DEBUG: 16:48:57.822: Device reported verify completion 220s (process:2420): libfprint-device-DEBUG: 16:48:57.822: Device reported finger status change: FP_FINGER_STATUS_NONE 220s (process:2420): libfprint-device-DEBUG: 16:48:57.822: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 220s (process:2420): libfprint-device-DEBUG: 16:48:57.822: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 220s (process:2420): libfprint-device-DEBUG: 16:48:57.834: Updated temperature model after 0.01 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 220s (process:2420): libfprint-image_device-DEBUG: 16:48:57.834: Activating image device 220s (process:2420): libfprint-image_device-DEBUG: 16:48:57.834: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING 220s (process:2420): libfprint-image_device-DEBUG: 16:48:57.834: Image device activation completed 220s (process:2420): libfprint-image_device-DEBUG: 16:48:57.834: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE 220s (process:2420): libfprint-image_device-DEBUG: 16:48:57.834: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 220s (process:2420): libfprint-device-DEBUG: 16:48:57.834: Device reported finger status change: FP_FINGER_STATUS_NEEDED 220s (process:2420): libfprint-image_device-DEBUG: 16:48:57.834: Deactivating image device 220s (process:2420): libfprint-image_device-DEBUG: 16:48:57.834: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_DEACTIVATING 220s (process:2420): libfprint-image_device-DEBUG: 16:48:57.834: Image device deactivation completed 220s (process:2420): libfprint-image_device-DEBUG: 16:48:57.834: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE 220s (process:2420): libfprint-device-DEBUG: 16:48:57.834: Device reported generic error (An unspecified error occurred!) during action; action was: FPI_DEVICE_ACTION_VERIFY 220s (process:2420): libfprint-device-DEBUG: 16:48:57.834: Device reported verify completion 220s (process:2420): libfprint-device-DEBUG: 16:48:57.834: Device reported finger status change: FP_FINGER_STATUS_NONE 220s (process:2420): libfprint-device-DEBUG: 16:48:57.834: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 220s (process:2420): libfprint-device-DEBUG: 16:48:57.834: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 220s (process:2420): libfprint-virtual_image-DEBUG: 16:48:57.835: 108835704: ../libfprint/drivers/virtual-image.c:244 220s (process:2420): libfprint-image_device-DEBUG: 16:48:57.935: Image device close completed 220s (process:2420): libfprint-device-DEBUG: 16:48:57.935: Device reported close completion 220s (process:2420): libfprint-device-DEBUG: 16:48:57.935: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 220s (process:2420): libfprint-device-DEBUG: 16:48:57.935: Updated temperature model after 0.10 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 220s Print was processed, continuing 220s Print was processed, continuing 220s Print was processed, continuing 220s Print was processed, continuing 220s Print was processed, continuing 220s Enroll done 220s Print was processed, continuing 220s Print was processed, continuing 220s Print was processed, continuing 220s Print was processed, continuing 220s Print was processed, continuing 220s Enroll done 220s fp - device - error - quark: An unspecified error occurred! (0) 220s ok 220s test_features (__main__.VirtualImage.test_features) ... (process:2420): libfprint-virtual_image-DEBUG: 16:48:57.935: 108936358: ../libfprint/drivers/virtual-image.c:216 220s (process:2420): libfprint-virtual_device_connection-DEBUG: 16:48:57.935: 108936390: ../libfprint/drivers/virtual-device-listener.c:153 221s (process:2420): libfprint-image_device-DEBUG: 16:48:58.036: Image device open completed 221s (process:2420): libfprint-device-DEBUG: 16:48:58.036: Device reported open completion 221s (process:2420): libfprint-device-DEBUG: 16:48:58.036: Completing action FPI_DEVICE_ACTION_OPEN in idle! 221s (process:2420): libfprint-device-DEBUG: 16:48:58.036: Updated temperature model after 0.10 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 221s (process:2420): libfprint-virtual_image-DEBUG: 16:48:58.036: 109037400: ../libfprint/drivers/virtual-image.c:244 221s (process:2420): libfprint-image_device-DEBUG: 16:48:58.136: Image device close completed 221s (process:2420): libfprint-device-DEBUG: 16:48:58.136: Device reported close completion 221s (process:2420): libfprint-device-DEBUG: 16:48:58.137: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 221s (process:2420): libfprint-device-DEBUG: 16:48:58.137: Updated temperature model after 0.10 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 221s ok 221s test_identify (__main__.VirtualImage.test_identify) ... (process:2420): libfprint-virtual_image-DEBUG: 16:48:58.137: 109137912: ../libfprint/drivers/virtual-image.c:216 221s (process:2420): libfprint-virtual_device_connection-DEBUG: 16:48:58.137: 109137945: ../libfprint/drivers/virtual-device-listener.c:153 221s (process:2420): libfprint-image_device-DEBUG: 16:48:58.237: Image device open completed 221s (process:2420): libfprint-device-DEBUG: 16:48:58.237: Device reported open completion 221s (process:2420): libfprint-device-DEBUG: 16:48:58.237: Completing action FPI_DEVICE_ACTION_OPEN in idle! 221s (process:2420): libfprint-device-DEBUG: 16:48:58.237: Updated temperature model after 0.10 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 221s (process:2420): libfprint-device-DEBUG: 16:48:58.238: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 221s (process:2420): libfprint-image_device-DEBUG: 16:48:58.238: Activating image device 221s (process:2420): libfprint-image_device-DEBUG: 16:48:58.238: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING 221s (process:2420): libfprint-image_device-DEBUG: 16:48:58.238: Image device activation completed 221s (process:2420): libfprint-image_device-DEBUG: 16:48:58.238: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE 221s (process:2420): libfprint-image_device-DEBUG: 16:48:58.238: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 221s (process:2420): libfprint-device-DEBUG: 16:48:58.238: Device reported finger status change: FP_FINGER_STATUS_NEEDED 221s (process:2420): libfprint-virtual_device_connection-DEBUG: 16:48:58.238: Got a new connection! 221s (process:2420): libfprint-virtual_image-DEBUG: 16:48:58.238: image data: 0xfa4e6b0 221s (process:2420): libfprint-device-DEBUG: 16:48:58.238: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 221s (process:2420): libfprint-image_device-DEBUG: 16:48:58.238: Image device reported finger status: on 221s (process:2420): libfprint-image_device-DEBUG: 16:48:58.238: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 221s (process:2420): libfprint-image_device-DEBUG: 16:48:58.238: Image device captured an image 221s (process:2420): libfprint-image_device-DEBUG: 16:48:58.238: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 221s (process:2420): libfprint-device-DEBUG: 16:48:58.238: Device reported finger status change: FP_FINGER_STATUS_PRESENT 221s (process:2420): libfprint-device-DEBUG: 16:48:58.238: Device reported finger status change: FP_FINGER_STATUS_NONE 221s (process:2420): libfprint-image_device-DEBUG: 16:48:58.238: Image device reported finger status: off 221s (process:2420): libfprint-image_device-DEBUG: 16:48:58.238: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 221s (process:2420): libfprint-image-DEBUG: 16:48:58.262: Minutiae scan completed in 0.023339 secs 221s (process:2420): libfprint-device-DEBUG: 16:48:58.262: Device reported enroll progress, reported 1 of 5 have been completed 221s (process:2420): libfprint-image_device-DEBUG: 16:48:58.262: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 221s (process:2420): libfprint-device-DEBUG: 16:48:58.262: Device reported finger status change: FP_FINGER_STATUS_NEEDED 221s (process:2420): libfprint-device-DEBUG: 16:48:58.262: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 221s (process:2420): libfprint-image_device-DEBUG: 16:48:58.262: Image device reported finger status: on 221s (process:2420): libfprint-image_device-DEBUG: 16:48:58.262: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 221s (process:2420): libfprint-virtual_image-DEBUG: 16:48:58.262: image data: 0xfa4e6b0 221s (process:2420): libfprint-image_device-DEBUG: 16:48:58.262: Image device captured an image 221s (process:2420): libfprint-image_device-DEBUG: 16:48:58.262: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 221s (process:2420): libfprint-device-DEBUG: 16:48:58.262: Device reported finger status change: FP_FINGER_STATUS_PRESENT 221s (process:2420): libfprint-image-DEBUG: 16:48:58.286: Minutiae scan completed in 0.023108 secs 221s (process:2420): libfprint-device-DEBUG: 16:48:58.286: Device reported enroll progress, reported 2 of 5 have been completed 221s (process:2420): libfprint-device-DEBUG: 16:48:58.286: Device reported finger status change: FP_FINGER_STATUS_NONE 221s (process:2420): libfprint-image_device-DEBUG: 16:48:58.286: Image device reported finger status: off 221s (process:2420): libfprint-image_device-DEBUG: 16:48:58.286: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 221s (process:2420): libfprint-image_device-DEBUG: 16:48:58.286: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 221s (process:2420): libfprint-device-DEBUG: 16:48:58.286: Device reported finger status change: FP_FINGER_STATUS_NEEDED 221s (process:2420): libfprint-virtual_image-DEBUG: 16:48:58.286: image data: 0xfa4e6b0 221s (process:2420): libfprint-device-DEBUG: 16:48:58.286: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 221s (process:2420): libfprint-image_device-DEBUG: 16:48:58.286: Image device reported finger status: on 221s (process:2420): libfprint-image_device-DEBUG: 16:48:58.286: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 221s (process:2420): libfprint-image_device-DEBUG: 16:48:58.286: Image device captured an image 221s (process:2420): libfprint-image_device-DEBUG: 16:48:58.286: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 221s (process:2420): libfprint-device-DEBUG: 16:48:58.286: Device reported finger status change: FP_FINGER_STATUS_PRESENT 221s (process:2420): libfprint-device-DEBUG: 16:48:58.286: Device reported finger status change: FP_FINGER_STATUS_NONE 221s (process:2420): libfprint-image_device-DEBUG: 16:48:58.286: Image device reported finger status: off 221s (process:2420): libfprint-image_device-DEBUG: 16:48:58.286: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 221s (process:2420): libfprint-image-DEBUG: 16:48:58.310: Minutiae scan completed in 0.023350 secs 221s (process:2420): libfprint-device-DEBUG: 16:48:58.310: Device reported enroll progress, reported 3 of 5 have been completed 221s (process:2420): libfprint-image_device-DEBUG: 16:48:58.310: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 221s (process:2420): libfprint-device-DEBUG: 16:48:58.310: Device reported finger status change: FP_FINGER_STATUS_NEEDED 221s (process:2420): libfprint-virtual_image-DEBUG: 16:48:58.310: image data: 0xfa4e6b0 221s (process:2420): libfprint-device-DEBUG: 16:48:58.310: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 221s (process:2420): libfprint-image_device-DEBUG: 16:48:58.310: Image device reported finger status: on 221s (process:2420): libfprint-image_device-DEBUG: 16:48:58.310: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 221s (process:2420): libfprint-image_device-DEBUG: 16:48:58.310: Image device captured an image 221s (process:2420): libfprint-image_device-DEBUG: 16:48:58.310: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 221s (process:2420): libfprint-device-DEBUG: 16:48:58.310: Device reported finger status change: FP_FINGER_STATUS_PRESENT 221s (process:2420): libfprint-device-DEBUG: 16:48:58.310: Device reported finger status change: FP_FINGER_STATUS_NONE 221s (process:2420): libfprint-image_device-DEBUG: 16:48:58.310: Image device reported finger status: off 221s (process:2420): libfprint-image_device-DEBUG: 16:48:58.310: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 221s (process:2420): libfprint-image-DEBUG: 16:48:58.333: Minutiae scan completed in 0.023000 secs 221s (process:2420): libfprint-device-DEBUG: 16:48:58.334: Device reported enroll progress, reported 4 of 5 have been completed 221s (process:2420): libfprint-image_device-DEBUG: 16:48:58.334: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 221s (process:2420): libfprint-device-DEBUG: 16:48:58.334: Device reported finger status change: FP_FINGER_STATUS_NEEDED 221s (process:2420): libfprint-virtual_image-DEBUG: 16:48:58.334: image data: 0xfa4e6b0 221s (process:2420): libfprint-device-DEBUG: 16:48:58.334: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 221s (process:2420): libfprint-image_device-DEBUG: 16:48:58.334: Image device reported finger status: on 221s (process:2420): libfprint-image_device-DEBUG: 16:48:58.334: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 221s (process:2420): libfprint-image_device-DEBUG: 16:48:58.334: Image device captured an image 221s (process:2420): libfprint-image_device-DEBUG: 16:48:58.334: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 221s (process:2420): libfprint-device-DEBUG: 16:48:58.334: Device reported finger status change: FP_FINGER_STATUS_PRESENT 221s (process:2420): libfprint-device-DEBUG: 16:48:58.334: Device reported finger status change: FP_FINGER_STATUS_NONE 221s (process:2420): libfprint-image_device-DEBUG: 16:48:58.334: Image device reported finger status: off 221s (process:2420): libfprint-image_device-DEBUG: 16:48:58.334: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 221s (process:2420): libfprint-image-DEBUG: 16:48:58.357: Minutiae scan completed in 0.023139 secs 221s (process:2420): libfprint-device-DEBUG: 16:48:58.358: Device reported enroll progress, reported 5 of 5 have been completed 221s (process:2420): libfprint-image_device-DEBUG: 16:48:58.358: Deactivating image device 221s (process:2420): libfprint-image_device-DEBUG: 16:48:58.358: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_DEACTIVATING 221s (process:2420): libfprint-image_device-DEBUG: 16:48:58.358: Image device deactivation completed 221s (process:2420): libfprint-image_device-DEBUG: 16:48:58.358: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE 221s (process:2420): libfprint-device-DEBUG: 16:48:58.358: Device reported enroll completion 221s (process:2420): libfprint-device-DEBUG: 16:48:58.358: Print for finger FP_FINGER_LEFT_THUMB enrolled 221s (process:2420): libfprint-device-DEBUG: 16:48:58.358: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 221s (process:2420): libfprint-device-DEBUG: 16:48:58.358: Updated temperature model after 0.12 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 221s (process:2420): libfprint-device-DEBUG: 16:48:58.358: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 221s (process:2420): libfprint-image_device-DEBUG: 16:48:58.358: Activating image device 221s (process:2420): libfprint-image_device-DEBUG: 16:48:58.358: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING 221s (process:2420): libfprint-image_device-DEBUG: 16:48:58.358: Image device activation completed 221s (process:2420): libfprint-image_device-DEBUG: 16:48:58.358: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE 221s (process:2420): libfprint-image_device-DEBUG: 16:48:58.358: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 221s (process:2420): libfprint-device-DEBUG: 16:48:58.358: Device reported finger status change: FP_FINGER_STATUS_NEEDED 221s (process:2420): libfprint-virtual_image-DEBUG: 16:48:58.359: image data: 0xfa5de90 221s (process:2420): libfprint-device-DEBUG: 16:48:58.359: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 221s (process:2420): libfprint-image_device-DEBUG: 16:48:58.359: Image device reported finger status: on 221s (process:2420): libfprint-image_device-DEBUG: 16:48:58.359: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 221s (process:2420): libfprint-image_device-DEBUG: 16:48:58.359: Image device captured an image 221s (process:2420): libfprint-image_device-DEBUG: 16:48:58.359: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 221s (process:2420): libfprint-device-DEBUG: 16:48:58.363: Device reported finger status change: FP_FINGER_STATUS_PRESENT 221s (process:2420): libfprint-device-DEBUG: 16:48:58.363: Device reported finger status change: FP_FINGER_STATUS_NONE 221s (process:2420): libfprint-image_device-DEBUG: 16:48:58.363: Image device reported finger status: off 221s (process:2420): libfprint-image_device-DEBUG: 16:48:58.363: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 221s (process:2420): libfprint-image-DEBUG: 16:48:58.380: Minutiae scan completed in 0.020956 secs 221s (process:2420): libfprint-device-DEBUG: 16:48:58.380: Device reported enroll progress, reported 1 of 5 have been completed 221s (process:2420): libfprint-image_device-DEBUG: 16:48:58.380: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 221s (process:2420): libfprint-device-DEBUG: 16:48:58.380: Device reported finger status change: FP_FINGER_STATUS_NEEDED 221s (process:2420): libfprint-device-DEBUG: 16:48:58.380: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 221s (process:2420): libfprint-image_device-DEBUG: 16:48:58.380: Image device reported finger status: on 221s (process:2420): libfprint-image_device-DEBUG: 16:48:58.380: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 221s (process:2420): libfprint-virtual_image-DEBUG: 16:48:58.380: image data: 0xfa6cea0 221s (process:2420): libfprint-image_device-DEBUG: 16:48:58.380: Image device captured an image 221s (process:2420): libfprint-image_device-DEBUG: 16:48:58.380: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 221s (process:2420): libfprint-device-DEBUG: 16:48:58.380: Device reported finger status change: FP_FINGER_STATUS_PRESENT 221s (process:2420): libfprint-image-DEBUG: 16:48:58.401: Minutiae scan completed in 0.020773 secs 221s (process:2420): libfprint-device-DEBUG: 16:48:58.401: Device reported enroll progress, reported 2 of 5 have been completed 221s (process:2420): libfprint-device-DEBUG: 16:48:58.402: Device reported finger status change: FP_FINGER_STATUS_NONE 221s (process:2420): libfprint-image_device-DEBUG: 16:48:58.402: Image device reported finger status: off 221s (process:2420): libfprint-image_device-DEBUG: 16:48:58.402: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 221s (process:2420): libfprint-image_device-DEBUG: 16:48:58.402: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 221s (process:2420): libfprint-device-DEBUG: 16:48:58.402: Device reported finger status change: FP_FINGER_STATUS_NEEDED 221s (process:2420): libfprint-virtual_image-DEBUG: 16:48:58.402: image data: 0xfa5de90 221s (process:2420): libfprint-device-DEBUG: 16:48:58.402: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 221s (process:2420): libfprint-image_device-DEBUG: 16:48:58.402: Image device reported finger status: on 221s (process:2420): libfprint-image_device-DEBUG: 16:48:58.402: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 221s (process:2420): libfprint-image_device-DEBUG: 16:48:58.402: Image device captured an image 221s (process:2420): libfprint-image_device-DEBUG: 16:48:58.402: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 221s (process:2420): libfprint-device-DEBUG: 16:48:58.402: Device reported finger status change: FP_FINGER_STATUS_PRESENT 221s (process:2420): libfprint-device-DEBUG: 16:48:58.402: Device reported finger status change: FP_FINGER_STATUS_NONE 221s (process:2420): libfprint-image_device-DEBUG: 16:48:58.402: Image device reported finger status: off 221s (process:2420): libfprint-image_device-DEBUG: 16:48:58.402: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 221s (process:2420): libfprint-image-DEBUG: 16:48:58.423: Minutiae scan completed in 0.021291 secs 221s (process:2420): libfprint-device-DEBUG: 16:48:58.423: Device reported enroll progress, reported 3 of 5 have been completed 221s (process:2420): libfprint-image_device-DEBUG: 16:48:58.423: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 221s (process:2420): libfprint-device-DEBUG: 16:48:58.423: Device reported finger status change: FP_FINGER_STATUS_NEEDED 221s (process:2420): libfprint-virtual_image-DEBUG: 16:48:58.423: image data: 0xfa5de90 221s (process:2420): libfprint-device-DEBUG: 16:48:58.424: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 221s (process:2420): libfprint-image_device-DEBUG: 16:48:58.424: Image device reported finger status: on 221s (process:2420): libfprint-image_device-DEBUG: 16:48:58.424: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 221s (process:2420): libfprint-image_device-DEBUG: 16:48:58.424: Image device captured an image 221s (process:2420): libfprint-image_device-DEBUG: 16:48:58.424: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 221s (process:2420): libfprint-device-DEBUG: 16:48:58.424: Device reported finger status change: FP_FINGER_STATUS_PRESENT 221s (process:2420): libfprint-device-DEBUG: 16:48:58.424: Device reported finger status change: FP_FINGER_STATUS_NONE 221s (process:2420): libfprint-image_device-DEBUG: 16:48:58.424: Image device reported finger status: off 221s (process:2420): libfprint-image_device-DEBUG: 16:48:58.424: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 221s (process:2420): libfprint-image-DEBUG: 16:48:58.445: Minutiae scan completed in 0.020946 secs 221s (process:2420): libfprint-device-DEBUG: 16:48:58.445: Device reported enroll progress, reported 4 of 5 have been completed 221s (process:2420): libfprint-image_device-DEBUG: 16:48:58.445: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 221s (process:2420): libfprint-device-DEBUG: 16:48:58.445: Device reported finger status change: FP_FINGER_STATUS_NEEDED 221s (process:2420): libfprint-virtual_image-DEBUG: 16:48:58.445: image data: 0xfa5de90 221s (process:2420): libfprint-device-DEBUG: 16:48:58.445: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 221s (process:2420): libfprint-image_device-DEBUG: 16:48:58.445: Image device reported finger status: on 221s (process:2420): libfprint-image_device-DEBUG: 16:48:58.445: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 221s (process:2420): libfprint-image_device-DEBUG: 16:48:58.445: Image device captured an image 221s (process:2420): libfprint-image_device-DEBUG: 16:48:58.445: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 221s (process:2420): libfprint-device-DEBUG: 16:48:58.445: Device reported finger status change: FP_FINGER_STATUS_PRESENT 221s (process:2420): libfprint-device-DEBUG: 16:48:58.445: Device reported finger status change: FP_FINGER_STATUS_NONE 221s (process:2420): libfprint-image_device-DEBUG: 16:48:58.445: Image device reported finger status: off 221s (process:2420): libfprint-image_device-DEBUG: 16:48:58.445: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 221s (process:2420): libfprint-image-DEBUG: 16:48:58.466: Minutiae scan completed in 0.020884 secs 221s (process:2420): libfprint-device-DEBUG: 16:48:58.466: Device reported enroll progress, reported 5 of 5 have been completed 221s (process:2420): libfprint-image_device-DEBUG: 16:48:58.466: Deactivating image device 221s (process:2420): libfprint-image_device-DEBUG: 16:48:58.466: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_DEACTIVATING 221s (process:2420): libfprint-image_device-DEBUG: 16:48:58.466: Image device deactivation completed 221s (process:2420): libfprint-image_device-DEBUG: 16:48:58.466: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE 221s (process:2420): libfprint-device-DEBUG: 16:48:58.466: Device reported enroll completion 221s (process:2420): libfprint-device-DEBUG: 16:48:58.466: Print for finger FP_FINGER_LEFT_THUMB enrolled 221s (process:2420): libfprint-device-DEBUG: 16:48:58.467: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 221s (process:2420): libfprint-device-DEBUG: 16:48:58.467: Updated temperature model after 0.11 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 221s (process:2420): libfprint-device-DEBUG: 16:48:58.467: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 221s (process:2420): libfprint-image_device-DEBUG: 16:48:58.467: Activating image device 221s (process:2420): libfprint-image_device-DEBUG: 16:48:58.467: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING 221s (process:2420): libfprint-image_device-DEBUG: 16:48:58.467: Image device activation completed 221s (process:2420): libfprint-image_device-DEBUG: 16:48:58.467: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE 221s (process:2420): libfprint-image_device-DEBUG: 16:48:58.467: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 221s (process:2420): libfprint-device-DEBUG: 16:48:58.467: Device reported finger status change: FP_FINGER_STATUS_NEEDED 221s (process:2420): libfprint-virtual_image-DEBUG: 16:48:58.467: image data: 0xfa5de90 221s (process:2420): libfprint-device-DEBUG: 16:48:58.467: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 221s (process:2420): libfprint-image_device-DEBUG: 16:48:58.467: Image device reported finger status: on 221s (process:2420): libfprint-image_device-DEBUG: 16:48:58.467: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 221s (process:2420): libfprint-image_device-DEBUG: 16:48:58.467: Image device captured an image 221s (process:2420): libfprint-image_device-DEBUG: 16:48:58.467: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 221s (process:2420): libfprint-device-DEBUG: 16:48:58.467: Device reported finger status change: FP_FINGER_STATUS_PRESENT 221s (process:2420): libfprint-device-DEBUG: 16:48:58.467: Device reported finger status change: FP_FINGER_STATUS_NONE 221s (process:2420): libfprint-image_device-DEBUG: 16:48:58.467: Image device reported finger status: off 221s (process:2420): libfprint-image_device-DEBUG: 16:48:58.467: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 221s (process:2420): libfprint-image_device-DEBUG: 16:48:58.467: Deactivating image device 221s (process:2420): libfprint-image_device-DEBUG: 16:48:58.467: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_DEACTIVATING 221s (process:2420): libfprint-image_device-DEBUG: 16:48:58.467: Image device deactivation completed 221s (process:2420): libfprint-image_device-DEBUG: 16:48:58.467: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE 221s (process:2420): libfprint-image-DEBUG: 16:48:58.488: Minutiae scan completed in 0.020762 secs 221s (process:2420): libfprint-print-DEBUG: 16:48:58.494: score 10/40 221s (process:2420): libfprint-print-DEBUG: 16:48:58.500: score 10/40 221s (process:2420): libfprint-print-DEBUG: 16:48:58.505: score 10/40 221s (process:2420): libfprint-print-DEBUG: 16:48:58.516: score 10/40 221s (process:2420): libfprint-print-DEBUG: 16:48:58.522: score 10/40 221s (process:2420): libfprint-print-DEBUG: 16:48:58.719: score 855/40 221s (process:2420): libfprint-device-DEBUG: 16:48:58.719: Device reported identify result 221s (process:2420): libfprint-device-DEBUG: 16:48:58.719: Device reported identify completion 221s (process:2420): libfprint-device-DEBUG: 16:48:58.719: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 221s (process:2420): libfprint-device-DEBUG: 16:48:58.719: Updated temperature model after 0.25 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 221s (process:2420): libfprint-device-DEBUG: 16:48:58.719: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 221s (process:2420): libfprint-image_device-DEBUG: 16:48:58.719: Activating image device 221s (process:2420): libfprint-image_device-DEBUG: 16:48:58.719: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING 221s (process:2420): libfprint-image_device-DEBUG: 16:48:58.719: Image device activation completed 221s (process:2420): libfprint-image_device-DEBUG: 16:48:58.719: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE 221s (process:2420): libfprint-image_device-DEBUG: 16:48:58.719: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 221s (process:2420): libfprint-device-DEBUG: 16:48:58.719: Device reported finger status change: FP_FINGER_STATUS_NEEDED 221s (process:2420): libfprint-virtual_image-DEBUG: 16:48:58.719: image data: 0xfa5cf30 221s (process:2420): libfprint-device-DEBUG: 16:48:58.719: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 221s (process:2420): libfprint-image_device-DEBUG: 16:48:58.719: Image device reported finger status: on 221s (process:2420): libfprint-image_device-DEBUG: 16:48:58.719: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 221s (process:2420): libfprint-image_device-DEBUG: 16:48:58.719: Image device captured an image 221s (process:2420): libfprint-image_device-DEBUG: 16:48:58.719: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 221s (process:2420): libfprint-device-DEBUG: 16:48:58.719: Device reported finger status change: FP_FINGER_STATUS_PRESENT 221s (process:2420): libfprint-device-DEBUG: 16:48:58.719: Device reported finger status change: FP_FINGER_STATUS_NONE 221s (process:2420): libfprint-image_device-DEBUG: 16:48:58.719: Image device reported finger status: off 221s (process:2420): libfprint-image_device-DEBUG: 16:48:58.719: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 221s (process:2420): libfprint-image_device-DEBUG: 16:48:58.719: Deactivating image device 221s (process:2420): libfprint-image_device-DEBUG: 16:48:58.719: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_DEACTIVATING 221s (process:2420): libfprint-image_device-DEBUG: 16:48:58.719: Image device deactivation completed 221s (process:2420): libfprint-image_device-DEBUG: 16:48:58.719: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE 221s (process:2420): libfprint-image-DEBUG: 16:48:58.743: Minutiae scan completed in 0.023135 secs 222s Executing: libfprint-2/virtual-image.test 222s (process:2420): libfprint-print-DEBUG: 16:48:59.706: score 1093/40 222s (process:2420): libfprint-device-DEBUG: 16:48:59.706: Device reported identify result 222s (process:2420): libfprint-device-DEBUG: 16:48:59.706: Device reported identify completion 222s (process:2420): libfprint-device-DEBUG: 16:48:59.706: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 222s (process:2420): libfprint-device-DEBUG: 16:48:59.706: Updated temperature model after 0.99 seconds, ratio 0.28 -> 0.29, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 222s (process:2420): libfprint-device-DEBUG: 16:48:59.706: Updated temperature model after 0.00 seconds, ratio 0.29 -> 0.29, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 222s (process:2420): libfprint-image_device-DEBUG: 16:48:59.706: Activating image device 222s (process:2420): libfprint-image_device-DEBUG: 16:48:59.706: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING 222s (process:2420): libfprint-image_device-DEBUG: 16:48:59.706: Image device activation completed 222s (process:2420): libfprint-image_device-DEBUG: 16:48:59.706: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE 222s (process:2420): libfprint-image_device-DEBUG: 16:48:59.706: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 222s (process:2420): libfprint-device-DEBUG: 16:48:59.706: Device reported finger status change: FP_FINGER_STATUS_NEEDED 222s (process:2420): libfprint-device-DEBUG: 16:48:59.706: Device reported identify result 222s (process:2420): libfprint-image_device-DEBUG: 16:48:59.706: Deactivating image device 222s (process:2420): libfprint-image_device-DEBUG: 16:48:59.706: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_DEACTIVATING 222s (process:2420): libfprint-image_device-DEBUG: 16:48:59.706: Image device deactivation completed 222s (process:2420): libfprint-image_device-DEBUG: 16:48:59.706: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE 222s (process:2420): libfprint-device-DEBUG: 16:48:59.706: Device reported identify completion 222s (process:2420): libfprint-device-DEBUG: 16:48:59.706: Device reported finger status change: FP_FINGER_STATUS_NONE 222s (process:2420): libfprint-device-DEBUG: 16:48:59.706: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 222s (process:2420): libfprint-device-DEBUG: 16:48:59.706: Updated temperature model after 0.00 seconds, ratio 0.29 -> 0.29, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 222s (process:2420): libfprint-device-DEBUG: 16:48:59.707: Updated temperature model after 0.00 seconds, ratio 0.29 -> 0.29, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 222s (process:2420): libfprint-image_device-DEBUG: 16:48:59.707: Activating image device 222s (process:2420): libfprint-image_device-DEBUG: 16:48:59.707: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING 222s (process:2420): libfprint-image_device-DEBUG: 16:48:59.707: Image device activation completed 222s (process:2420): libfprint-image_device-DEBUG: 16:48:59.707: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE 222s (process:2420): libfprint-image_device-DEBUG: 16:48:59.707: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 222s (process:2420): libfprint-device-DEBUG: 16:48:59.707: Device reported finger status change: FP_FINGER_STATUS_NEEDED 222s (process:2420): libfprint-image_device-DEBUG: 16:48:59.707: Deactivating image device 222s (process:2420): libfprint-image_device-DEBUG: 16:48:59.707: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_DEACTIVATING 222s (process:2420): libfprint-image_device-DEBUG: 16:48:59.707: Image device deactivation completed 222s (process:2420): libfprint-image_device-DEBUG: 16:48:59.707: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE 222s (process:2420): libfprint-device-DEBUG: 16:48:59.707: Device reported generic error (An unspecified error occurred!) during action; action was: FPI_DEVICE_ACTION_IDENTIFY 222s (process:2420): libfprint-device-DEBUG: 16:48:59.707: Device reported identify completion 222s (process:2420): libfprint-device-DEBUG: 16:48:59.707: Device reported finger status change: FP_FINGER_STATUS_NONE 222s (process:2420): libfprint-device-DEBUG: 16:48:59.707: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 222s (process:2420): libfprint-device-DEBUG: 16:48:59.707: Updated temperature model after 0.00 seconds, ratio 0.29 -> 0.29, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 222s (process:2420): libfprint-virtual_image-DEBUG: 16:48:59.707: 110708428: ../libfprint/drivers/virtual-image.c:244 222s (process:2420): libfprint-image_device-DEBUG: 16:48:59.808: Image device close completed 222s (process:2420): libfprint-device-DEBUG: 16:48:59.808: Device reported close completion 222s (process:2420): libfprint-device-DEBUG: 16:48:59.808: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 222s (process:2420): libfprint-device-DEBUG: 16:48:59.808: Updated temperature model after 0.10 seconds, ratio 0.29 -> 0.29, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 222s Print was processed, continuing 222s Print was processed, continuing 222s Print was processed, continuing 222s Print was processed, continuing 222s Print was processed, continuing 222s Enroll done 222s Print was processed, continuing 222s Print was processed, continuing 222s Print was processed, continuing 222s Print was processed, continuing 222s Print was processed, continuing 222s Enroll done 222s Identify finished 222s Identify finished 222s Identify finished 222s fp - device - retry - quark: The swipe was too short, please try again. (1) 222s Identify finished 222s fp - device - error - quark: An unspecified error occurred! (0) 222s ok 222s test_verify_serialized (__main__.VirtualImage.test_verify_serialized) ... (process:2420): libfprint-virtual_image-DEBUG: 16:48:59.808: 110809059: ../libfprint/drivers/virtual-image.c:216 222s (process:2420): libfprint-virtual_device_connection-DEBUG: 16:48:59.808: 110809104: ../libfprint/drivers/virtual-device-listener.c:153 222s (process:2420): libfprint-image_device-DEBUG: 16:48:59.908: Image device open completed 222s (process:2420): libfprint-device-DEBUG: 16:48:59.908: Device reported open completion 222s (process:2420): libfprint-device-DEBUG: 16:48:59.908: Completing action FPI_DEVICE_ACTION_OPEN in idle! 222s (process:2420): libfprint-device-DEBUG: 16:48:59.908: Updated temperature model after 0.10 seconds, ratio 0.29 -> 0.29, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 222s (process:2420): libfprint-device-DEBUG: 16:48:59.909: Updated temperature model after 0.00 seconds, ratio 0.29 -> 0.29, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 222s (process:2420): libfprint-image_device-DEBUG: 16:48:59.909: Activating image device 222s (process:2420): libfprint-image_device-DEBUG: 16:48:59.909: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING 222s (process:2420): libfprint-image_device-DEBUG: 16:48:59.909: Image device activation completed 222s (process:2420): libfprint-image_device-DEBUG: 16:48:59.909: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE 222s (process:2420): libfprint-image_device-DEBUG: 16:48:59.909: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 222s (process:2420): libfprint-device-DEBUG: 16:48:59.909: Device reported finger status change: FP_FINGER_STATUS_NEEDED 222s (process:2420): libfprint-virtual_device_connection-DEBUG: 16:48:59.909: Got a new connection! 222s (process:2420): libfprint-virtual_image-DEBUG: 16:48:59.909: image data: 0xfa5cf30 222s (process:2420): libfprint-device-DEBUG: 16:48:59.909: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 222s (process:2420): libfprint-image_device-DEBUG: 16:48:59.909: Image device reported finger status: on 222s (process:2420): libfprint-image_device-DEBUG: 16:48:59.909: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 222s (process:2420): libfprint-image_device-DEBUG: 16:48:59.909: Image device captured an image 222s (process:2420): libfprint-image_device-DEBUG: 16:48:59.911: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 222s (process:2420): libfprint-device-DEBUG: 16:48:59.911: Device reported finger status change: FP_FINGER_STATUS_PRESENT 222s (process:2420): libfprint-device-DEBUG: 16:48:59.911: Device reported finger status change: FP_FINGER_STATUS_NONE 222s (process:2420): libfprint-image_device-DEBUG: 16:48:59.911: Image device reported finger status: off 222s (process:2420): libfprint-image_device-DEBUG: 16:48:59.911: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 222s (process:2420): libfprint-image-DEBUG: 16:48:59.933: Minutiae scan completed in 0.023352 secs 222s (process:2420): libfprint-device-DEBUG: 16:48:59.933: Device reported enroll progress, reported 1 of 5 have been completed 222s (process:2420): libfprint-image_device-DEBUG: 16:48:59.933: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 222s (process:2420): libfprint-device-DEBUG: 16:48:59.933: Device reported finger status change: FP_FINGER_STATUS_NEEDED 222s (process:2420): libfprint-device-DEBUG: 16:48:59.933: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 222s (process:2420): libfprint-image_device-DEBUG: 16:48:59.933: Image device reported finger status: on 222s (process:2420): libfprint-image_device-DEBUG: 16:48:59.933: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 222s (process:2420): libfprint-virtual_image-DEBUG: 16:48:59.933: image data: 0xfa5cf30 222s (process:2420): libfprint-image_device-DEBUG: 16:48:59.933: Image device captured an image 222s (process:2420): libfprint-image_device-DEBUG: 16:48:59.933: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 222s (process:2420): libfprint-device-DEBUG: 16:48:59.934: Device reported finger status change: FP_FINGER_STATUS_PRESENT 222s (process:2420): libfprint-image-DEBUG: 16:48:59.957: Minutiae scan completed in 0.023052 secs 222s (process:2420): libfprint-device-DEBUG: 16:48:59.957: Device reported enroll progress, reported 2 of 5 have been completed 223s (process:2420): libfprint-device-DEBUG: 16:48:59.957: Device reported finger status change: FP_FINGER_STATUS_NONE 223s (process:2420): libfprint-image_device-DEBUG: 16:48:59.957: Image device reported finger status: off 223s (process:2420): libfprint-image_device-DEBUG: 16:48:59.957: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 223s (process:2420): libfprint-image_device-DEBUG: 16:48:59.957: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 223s (process:2420): libfprint-device-DEBUG: 16:48:59.957: Device reported finger status change: FP_FINGER_STATUS_NEEDED 223s (process:2420): libfprint-virtual_image-DEBUG: 16:48:59.957: image data: 0xfa5cf30 223s (process:2420): libfprint-device-DEBUG: 16:48:59.957: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 223s (process:2420): libfprint-image_device-DEBUG: 16:48:59.957: Image device reported finger status: on 223s (process:2420): libfprint-image_device-DEBUG: 16:48:59.957: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 223s (process:2420): libfprint-image_device-DEBUG: 16:48:59.957: Image device captured an image 223s (process:2420): libfprint-image_device-DEBUG: 16:48:59.957: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 223s (process:2420): libfprint-device-DEBUG: 16:48:59.957: Device reported finger status change: FP_FINGER_STATUS_PRESENT 223s (process:2420): libfprint-device-DEBUG: 16:48:59.957: Device reported finger status change: FP_FINGER_STATUS_NONE 223s (process:2420): libfprint-image_device-DEBUG: 16:48:59.957: Image device reported finger status: off 223s (process:2420): libfprint-image_device-DEBUG: 16:48:59.957: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 223s (process:2420): libfprint-image-DEBUG: 16:48:59.980: Minutiae scan completed in 0.023047 secs 223s (process:2420): libfprint-device-DEBUG: 16:48:59.980: Device reported enroll progress, reported 3 of 5 have been completed 223s (process:2420): libfprint-image_device-DEBUG: 16:48:59.980: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 223s (process:2420): libfprint-device-DEBUG: 16:48:59.980: Device reported finger status change: FP_FINGER_STATUS_NEEDED 223s (process:2420): libfprint-virtual_image-DEBUG: 16:48:59.981: image data: 0xfa5cf30 223s (process:2420): libfprint-device-DEBUG: 16:48:59.981: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 223s (process:2420): libfprint-image_device-DEBUG: 16:48:59.981: Image device reported finger status: on 223s (process:2420): libfprint-image_device-DEBUG: 16:48:59.981: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 223s (process:2420): libfprint-image_device-DEBUG: 16:48:59.981: Image device captured an image 223s (process:2420): libfprint-image_device-DEBUG: 16:48:59.981: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 223s (process:2420): libfprint-device-DEBUG: 16:48:59.981: Device reported finger status change: FP_FINGER_STATUS_PRESENT 223s (process:2420): libfprint-device-DEBUG: 16:48:59.981: Device reported finger status change: FP_FINGER_STATUS_NONE 223s (process:2420): libfprint-image_device-DEBUG: 16:48:59.981: Image device reported finger status: off 223s (process:2420): libfprint-image_device-DEBUG: 16:48:59.981: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 223s (process:2420): libfprint-image-DEBUG: 16:49:00.004: Minutiae scan completed in 0.022904 secs 223s (process:2420): libfprint-device-DEBUG: 16:49:00.004: Device reported enroll progress, reported 4 of 5 have been completed 223s (process:2420): libfprint-image_device-DEBUG: 16:49:00.004: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 223s (process:2420): libfprint-device-DEBUG: 16:49:00.004: Device reported finger status change: FP_FINGER_STATUS_NEEDED 223s (process:2420): libfprint-virtual_image-DEBUG: 16:49:00.004: image data: 0xfa5cf30 223s (process:2420): libfprint-device-DEBUG: 16:49:00.004: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 223s (process:2420): libfprint-image_device-DEBUG: 16:49:00.004: Image device reported finger status: on 223s (process:2420): libfprint-image_device-DEBUG: 16:49:00.004: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 223s (process:2420): libfprint-image_device-DEBUG: 16:49:00.004: Image device captured an image 223s (process:2420): libfprint-image_device-DEBUG: 16:49:00.004: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 223s (process:2420): libfprint-device-DEBUG: 16:49:00.004: Device reported finger status change: FP_FINGER_STATUS_PRESENT 223s (process:2420): libfprint-device-DEBUG: 16:49:00.004: Device reported finger status change: FP_FINGER_STATUS_NONE 223s (process:2420): libfprint-image_device-DEBUG: 16:49:00.004: Image device reported finger status: off 223s (process:2420): libfprint-image_device-DEBUG: 16:49:00.004: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 223s (process:2420): libfprint-image-DEBUG: 16:49:00.027: Minutiae scan completed in 0.022945 secs 223s (process:2420): libfprint-device-DEBUG: 16:49:00.027: Device reported enroll progress, reported 5 of 5 have been completed 223s (process:2420): libfprint-image_device-DEBUG: 16:49:00.027: Deactivating image device 223s (process:2420): libfprint-image_device-DEBUG: 16:49:00.027: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_DEACTIVATING 223s (process:2420): libfprint-image_device-DEBUG: 16:49:00.027: Image device deactivation completed 223s (process:2420): libfprint-image_device-DEBUG: 16:49:00.027: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE 223s (process:2420): libfprint-device-DEBUG: 16:49:00.027: Device reported enroll completion 223s (process:2420): libfprint-device-DEBUG: 16:49:00.028: Print for finger FP_FINGER_LEFT_THUMB enrolled 223s (process:2420): libfprint-device-DEBUG: 16:49:00.028: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 223s (process:2420): libfprint-device-DEBUG: 16:49:00.028: Updated temperature model after 0.12 seconds, ratio 0.29 -> 0.29, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 223s (process:2420): libfprint-device-DEBUG: 16:49:00.028: Updated temperature model after 0.00 seconds, ratio 0.29 -> 0.29, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 223s (process:2420): libfprint-image_device-DEBUG: 16:49:00.028: Activating image device 223s (process:2420): libfprint-image_device-DEBUG: 16:49:00.028: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING 223s (process:2420): libfprint-image_device-DEBUG: 16:49:00.028: Image device activation completed 223s (process:2420): libfprint-image_device-DEBUG: 16:49:00.028: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE 223s (process:2420): libfprint-image_device-DEBUG: 16:49:00.028: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 223s (process:2420): libfprint-device-DEBUG: 16:49:00.028: Device reported finger status change: FP_FINGER_STATUS_NEEDED 223s (process:2420): libfprint-virtual_image-DEBUG: 16:49:00.028: image data: 0xfa5cf30 223s (process:2420): libfprint-device-DEBUG: 16:49:00.028: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 223s (process:2420): libfprint-image_device-DEBUG: 16:49:00.028: Image device reported finger status: on 223s (process:2420): libfprint-image_device-DEBUG: 16:49:00.028: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 223s (process:2420): libfprint-image_device-DEBUG: 16:49:00.028: Image device captured an image 223s (process:2420): libfprint-image_device-DEBUG: 16:49:00.028: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 223s (process:2420): libfprint-device-DEBUG: 16:49:00.028: Device reported finger status change: FP_FINGER_STATUS_PRESENT 223s (process:2420): libfprint-device-DEBUG: 16:49:00.028: Device reported finger status change: FP_FINGER_STATUS_NONE 223s (process:2420): libfprint-image_device-DEBUG: 16:49:00.028: Image device reported finger status: off 223s (process:2420): libfprint-image_device-DEBUG: 16:49:00.028: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 223s (process:2420): libfprint-image_device-DEBUG: 16:49:00.028: Deactivating image device 223s (process:2420): libfprint-image_device-DEBUG: 16:49:00.028: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_DEACTIVATING 223s (process:2420): libfprint-image_device-DEBUG: 16:49:00.028: Image device deactivation completed 223s (process:2420): libfprint-image_device-DEBUG: 16:49:00.028: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE 223s (process:2420): libfprint-image-DEBUG: 16:49:00.051: Minutiae scan completed in 0.022956 secs 224s (process:2420): libfprint-print-DEBUG: 16:49:01.003: score 1093/40 224s (process:2420): libfprint-device-DEBUG: 16:49:01.003: Device reported verify result 224s (process:2420): libfprint-device-DEBUG: 16:49:01.003: Device reported verify completion 224s (process:2420): libfprint-device-DEBUG: 16:49:01.003: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 224s (process:2420): libfprint-device-DEBUG: 16:49:01.003: Updated temperature model after 0.98 seconds, ratio 0.29 -> 0.29, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 224s (process:2420): libfprint-device-DEBUG: 16:49:01.003: Updated temperature model after 0.00 seconds, ratio 0.29 -> 0.29, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 224s (process:2420): libfprint-image_device-DEBUG: 16:49:01.003: Activating image device 224s (process:2420): libfprint-image_device-DEBUG: 16:49:01.003: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING 224s (process:2420): libfprint-image_device-DEBUG: 16:49:01.003: Image device activation completed 224s (process:2420): libfprint-image_device-DEBUG: 16:49:01.003: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE 224s (process:2420): libfprint-image_device-DEBUG: 16:49:01.003: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 224s (process:2420): libfprint-device-DEBUG: 16:49:01.003: Device reported finger status change: FP_FINGER_STATUS_NEEDED 224s (process:2420): libfprint-virtual_image-DEBUG: 16:49:01.003: image data: 0xfa5de90 224s (process:2420): libfprint-device-DEBUG: 16:49:01.004: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 224s (process:2420): libfprint-image_device-DEBUG: 16:49:01.004: Image device reported finger status: on 224s (process:2420): libfprint-image_device-DEBUG: 16:49:01.004: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 224s (process:2420): libfprint-image_device-DEBUG: 16:49:01.004: Image device captured an image 224s (process:2420): libfprint-image_device-DEBUG: 16:49:01.007: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 224s (process:2420): libfprint-device-DEBUG: 16:49:01.007: Device reported finger status change: FP_FINGER_STATUS_PRESENT 224s (process:2420): libfprint-device-DEBUG: 16:49:01.007: Device reported finger status change: FP_FINGER_STATUS_NONE 224s (process:2420): libfprint-image_device-DEBUG: 16:49:01.007: Image device reported finger status: off 224s (process:2420): libfprint-image_device-DEBUG: 16:49:01.007: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 224s (process:2420): libfprint-image_device-DEBUG: 16:49:01.007: Deactivating image device 224s (process:2420): libfprint-image_device-DEBUG: 16:49:01.007: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_DEACTIVATING 224s (process:2420): libfprint-image_device-DEBUG: 16:49:01.007: Image device deactivation completed 224s (process:2420): libfprint-image_device-DEBUG: 16:49:01.007: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE 224s (process:2420): libfprint-image-DEBUG: 16:49:01.024: Minutiae scan completed in 0.020389 secs 224s (process:2420): libfprint-print-DEBUG: 16:49:01.030: score 10/40 224s (process:2420): libfprint-print-DEBUG: 16:49:01.036: score 10/40 224s (process:2420): libfprint-print-DEBUG: 16:49:01.041: score 10/40 224s (process:2420): libfprint-print-DEBUG: 16:49:01.046: score 10/40 224s (process:2420): libfprint-print-DEBUG: 16:49:01.052: score 10/40 224s (process:2420): libfprint-device-DEBUG: 16:49:01.052: Device reported verify result 224s (process:2420): libfprint-device-DEBUG: 16:49:01.052: Device reported verify completion 224s (process:2420): libfprint-device-DEBUG: 16:49:01.052: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 224s (process:2420): libfprint-device-DEBUG: 16:49:01.052: Updated temperature model after 0.05 seconds, ratio 0.29 -> 0.29, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 224s (process:2420): libfprint-virtual_image-DEBUG: 16:49:01.052: 112053340: ../libfprint/drivers/virtual-image.c:244 224s (process:2420): libfprint-image_device-DEBUG: 16:49:01.152: Image device close completed 224s (process:2420): libfprint-device-DEBUG: 16:49:01.152: Device reported close completion 224s (process:2420): libfprint-device-DEBUG: 16:49:01.153: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 224s (process:2420): libfprint-device-DEBUG: 16:49:01.153: Updated temperature model after 0.10 seconds, ratio 0.29 -> 0.29, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 224s Print was processed, continuing 224s Print was processed, continuing 224s Print was processed, continuing 224s Print was processed, continuing 224s Print was processed, continuing 224s Enroll done 224s ok 224s 224s ---------------------------------------------------------------------- 224s Ran 5 tests in 6.690s 224s 224s OK 224s PASS: libfprint-2/virtual-image.test 224s Running test: libfprint-2/driver-egismoc-05a1.test 224s ** (umockdev-run:2430): DEBUG: 16:49:01.520: umockdev.vala:123: Created udev test bed /tmp/umockdev.B61BK2 224s ** (umockdev-run:2430): DEBUG: 16:49:01.520: umockdev.vala:1297: parsing device description for /devices/pci0000:00/0000:00:14.0/usb1/1-5 224s ** (umockdev-run:2430): DEBUG: 16:49:01.522: umockdev.vala:1366: creating device /devices/pci0000:00/0000:00:14.0/usb1/1-5 (subsystem usb) 224s ** (umockdev-run:2430): DEBUG: 16:49:01.524: umockdev.vala:1411: create_node_for_device: creating file device /tmp/umockdev.B61BK2/dev/bus/usb/001/003 224s ** (umockdev-run:2430): DEBUG: 16:49:01.524: umockdev.vala:1297: parsing device description for /devices/pci0000:00/0000:00:14.0/usb1 224s ** (umockdev-run:2430): DEBUG: 16:49:01.525: umockdev.vala:1366: creating device /devices/pci0000:00/0000:00:14.0/usb1 (subsystem usb) 224s ** (umockdev-run:2430): DEBUG: 16:49:01.527: umockdev.vala:1411: create_node_for_device: creating file device /tmp/umockdev.B61BK2/dev/bus/usb/001/001 224s ** (umockdev-run:2430): DEBUG: 16:49:01.527: umockdev.vala:1297: parsing device description for /devices/pci0000:00/0000:00:14.0 224s ** (umockdev-run:2430): DEBUG: 16:49:01.527: umockdev.vala:1366: creating device /devices/pci0000:00/0000:00:14.0 (subsystem pci) 224s (process:2434): libfprint-context-DEBUG: 16:49:01.602: Initializing FpContext (libfprint version 1.94.7+tod1) 224s (process:2434): libfprint-tod-DEBUG: 16:49:01.602: Impossible to load the shared drivers dir Error opening directory “/usr/lib/aarch64-linux-gnu/libfprint-2/tod-1”: No such file or directory 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.604: 112605418: ../libfprint/drivers/egismoc/egismoc.c:1515 224s (process:2434): libfprint-context-DEBUG: 16:49:01.605: No driver found for USB device 1D6B:0002 224s (process:2434): libfprint-device-DEBUG: 16:49:01.605: Device reported probe completion 224s (process:2434): libfprint-device-DEBUG: 16:49:01.605: Completing action FPI_DEVICE_ACTION_PROBE in idle! 224s (process:2434): libfprint-device-DEBUG: 16:49:01.605: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.606: Opening device 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.606: [egismoc] DEV_INIT_STATES entering state 0 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.607: [egismoc] DEV_INIT_STATES entering state 1 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.608: [egismoc] DEV_INIT_STATES entering state 2 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.608: [egismoc] DEV_INIT_STATES entering state 3 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.608: [egismoc] DEV_INIT_STATES entering state 4 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.609: [egismoc] DEV_INIT_STATES entering state 5 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.609: Execute command and get response 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.609: Get check bytes 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.609: [egismoc] CMD_STATES entering state 0 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.610: [egismoc] CMD_STATES entering state 1 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.610: Command receive callback 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.610: [egismoc] CMD_STATES completed successfully 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.610: Firmware version callback 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.610: Response suffix valid: yes 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.610: Device firmware version is 9050.1.2.13 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.610: [egismoc] DEV_INIT_STATES completed successfully 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.610: Task SSM done 224s (process:2434): libfprint-device-DEBUG: 16:49:01.610: Device reported open completion 224s (process:2434): libfprint-device-DEBUG: 16:49:01.610: Completing action FPI_DEVICE_ACTION_OPEN in idle! 224s (process:2434): libfprint-device-DEBUG: 16:49:01.610: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.611: List 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.611: [egismoc] LIST_STATES entering state 0 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.611: Execute command and get response 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.611: Get check bytes 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.611: [egismoc] CMD_STATES entering state 0 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.612: [egismoc] CMD_STATES entering state 1 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.612: Command receive callback 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.612: [egismoc] CMD_STATES completed successfully 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.612: List callback 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.612: Device fingerprint 0: FP1-20231209-3-A9E16FBD-root 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.612: Device fingerprint 1: FP1-20231209-1-85DC4FAC-root 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.612: Device fingerprint 2: FP1-20231209-2-04EFB67C-root 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.612: Number of currently enrolled fingerprints on the device is 3 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.612: [egismoc] LIST_STATES entering state 1 224s (process:2434): libfprint-device-DEBUG: 16:49:01.612: Device reported listing completion 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.612: [egismoc] LIST_STATES completed successfully 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.612: Task SSM done 224s (process:2434): libfprint-device-DEBUG: 16:49:01.613: Completing action FPI_DEVICE_ACTION_LIST in idle! 224s (process:2434): libfprint-device-DEBUG: 16:49:01.613: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.613: Clear storage 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.613: [egismoc] DELETE_STATES entering state 0 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.613: Execute command and get response 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.613: Get check bytes 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.613: [egismoc] CMD_STATES entering state 0 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.613: [egismoc] CMD_STATES entering state 1 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.614: Command receive callback 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.614: [egismoc] CMD_STATES completed successfully 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.614: List callback 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.614: Device fingerprint 0: FP1-20231209-3-A9E16FBD-root 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.614: Device fingerprint 1: FP1-20231209-1-85DC4FAC-root 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.614: Device fingerprint 2: FP1-20231209-2-04EFB67C-root 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.614: Number of currently enrolled fingerprints on the device is 3 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.614: [egismoc] DELETE_STATES entering state 1 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.614: Get delete command 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.614: Execute command and get response 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.614: Get check bytes 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.614: [egismoc] CMD_STATES entering state 0 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.615: [egismoc] CMD_STATES entering state 1 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.615: Command receive callback 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.615: [egismoc] CMD_STATES completed successfully 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.615: Delete callback 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.615: Response prefix valid: yes 224s (process:2434): libfprint-device-DEBUG: 16:49:01.615: Device reported deletion completion 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.615: [egismoc] DELETE_STATES completed successfully 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.615: Task SSM done 224s (process:2434): libfprint-device-DEBUG: 16:49:01.615: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 224s (process:2434): libfprint-device-DEBUG: 16:49:01.615: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.615: List 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.615: [egismoc] LIST_STATES entering state 0 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.616: Execute command and get response 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.616: Get check bytes 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.616: [egismoc] CMD_STATES entering state 0 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.616: [egismoc] CMD_STATES entering state 1 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.616: Command receive callback 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.616: [egismoc] CMD_STATES completed successfully 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.617: List callback 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.617: Number of currently enrolled fingerprints on the device is 0 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.617: [egismoc] LIST_STATES entering state 1 224s (process:2434): libfprint-device-DEBUG: 16:49:01.617: Device reported listing completion 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.617: [egismoc] LIST_STATES completed successfully 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.617: Task SSM done 224s (process:2434): libfprint-device-DEBUG: 16:49:01.617: Completing action FPI_DEVICE_ACTION_LIST in idle! 224s (process:2434): libfprint-device-DEBUG: 16:49:01.617: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 224s (process:2434): libfprint-device-DEBUG: 16:49:01.624: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.624: Enroll 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.624: [egismoc] ENROLL_STATES entering state 0 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.625: Execute command and get response 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.625: Get check bytes 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.625: [egismoc] CMD_STATES entering state 0 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.625: [egismoc] CMD_STATES entering state 1 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.626: Command receive callback 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.626: [egismoc] CMD_STATES completed successfully 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.626: List callback 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.626: Number of currently enrolled fingerprints on the device is 0 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.626: [egismoc] ENROLL_STATES entering state 1 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.626: [egismoc] ENROLL_STATES entering state 2 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.626: Execute command and get response 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.626: Get check bytes 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.626: [egismoc] CMD_STATES entering state 0 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.626: [egismoc] CMD_STATES entering state 1 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.627: Command receive callback 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.627: [egismoc] CMD_STATES completed successfully 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.627: Task SSM next state callback 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.627: [egismoc] ENROLL_STATES entering state 3 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.627: Execute command and get response 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.627: Get check bytes 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.627: [egismoc] CMD_STATES entering state 0 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.627: [egismoc] CMD_STATES entering state 1 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.628: Command receive callback 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.628: [egismoc] CMD_STATES completed successfully 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.628: Task SSM next state callback 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.628: [egismoc] ENROLL_STATES entering state 4 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.628: Wait for finger on sensor 224s (process:2434): libfprint-device-DEBUG: 16:49:01.628: Device reported finger status change: FP_FINGER_STATUS_NEEDED 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.628: Finger on sensor callback 224s (process:2434): libfprint-device-DEBUG: 16:49:01.628: Device reported finger status change: FP_FINGER_STATUS_PRESENT 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.629: [egismoc] ENROLL_STATES entering state 5 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.629: Execute command and get response 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.629: Get check bytes 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.629: [egismoc] CMD_STATES entering state 0 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.629: [egismoc] CMD_STATES entering state 1 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.629: Command receive callback 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.630: [egismoc] CMD_STATES completed successfully 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.630: Task SSM next state callback 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.630: [egismoc] ENROLL_STATES entering state 6 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.630: Get check command 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.630: Execute command and get response 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.630: Get check bytes 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.630: [egismoc] CMD_STATES entering state 0 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.630: [egismoc] CMD_STATES entering state 1 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.631: Command receive callback 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.631: [egismoc] CMD_STATES completed successfully 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.631: Enroll check callback 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.631: Response suffix valid: yes 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.631: [egismoc] ENROLL_STATES entering state 7 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.631: Execute command and get response 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.631: Get check bytes 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.631: [egismoc] CMD_STATES entering state 0 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.631: [egismoc] CMD_STATES entering state 1 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.632: Command receive callback 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.632: [egismoc] CMD_STATES completed successfully 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.632: Task SSM next state callback 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.632: [egismoc] ENROLL_STATES entering state 8 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.632: Execute command and get response 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.632: Get check bytes 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.632: [egismoc] CMD_STATES entering state 0 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.632: [egismoc] CMD_STATES entering state 1 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.633: Command receive callback 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.633: [egismoc] CMD_STATES completed successfully 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.633: Task SSM next state callback 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.633: [egismoc] ENROLL_STATES entering state 9 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.633: Execute command and get response 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.633: Get check bytes 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.633: [egismoc] CMD_STATES entering state 0 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.633: [egismoc] CMD_STATES entering state 1 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.634: Command receive callback 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.634: [egismoc] CMD_STATES completed successfully 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.634: Task SSM next state callback 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.634: [egismoc] ENROLL_STATES entering state 10 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.634: Wait for finger on sensor 224s (process:2434): libfprint-device-DEBUG: 16:49:01.634: Device reported finger status change: FP_FINGER_STATUS_NEEDED 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.634: Finger on sensor callback 224s (process:2434): libfprint-device-DEBUG: 16:49:01.634: Device reported finger status change: FP_FINGER_STATUS_PRESENT 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.634: [egismoc] ENROLL_STATES entering state 11 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.635: Execute command and get response 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.635: Get check bytes 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.635: [egismoc] CMD_STATES entering state 0 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.635: [egismoc] CMD_STATES entering state 1 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.635: Command receive callback 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.636: [egismoc] CMD_STATES completed successfully 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.636: Read capture callback 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.636: Response prefix valid: yes 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.636: Response suffix valid: yes 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.636: Partial capture successful. Please touch the sensor again (1/10) 224s (process:2434): libfprint-device-DEBUG: 16:49:01.636: Device reported enroll progress, reported 1 of 10 have been completed 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.648: [egismoc] ENROLL_STATES entering state 8 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.648: Execute command and get response 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.648: Get check bytes 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.648: [egismoc] CMD_STATES entering state 0 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.648: [egismoc] CMD_STATES entering state 1 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.649: Command receive callback 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.649: [egismoc] CMD_STATES completed successfully 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.649: Task SSM next state callback 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.649: [egismoc] ENROLL_STATES entering state 9 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.649: Execute command and get response 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.649: Get check bytes 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.649: [egismoc] CMD_STATES entering state 0 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.649: [egismoc] CMD_STATES entering state 1 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.650: Command receive callback 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.650: [egismoc] CMD_STATES completed successfully 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.650: Task SSM next state callback 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.650: [egismoc] ENROLL_STATES entering state 10 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.650: Wait for finger on sensor 224s (process:2434): libfprint-device-DEBUG: 16:49:01.650: Device reported finger status change: FP_FINGER_STATUS_NEEDED 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.650: Finger on sensor callback 224s (process:2434): libfprint-device-DEBUG: 16:49:01.650: Device reported finger status change: FP_FINGER_STATUS_PRESENT 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.650: [egismoc] ENROLL_STATES entering state 11 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.650: Execute command and get response 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.650: Get check bytes 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.650: [egismoc] CMD_STATES entering state 0 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.651: [egismoc] CMD_STATES entering state 1 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.651: Command receive callback 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.651: [egismoc] CMD_STATES completed successfully 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.651: Read capture callback 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.651: Response prefix valid: yes 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.651: Response suffix valid: yes 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.651: Partial capture successful. Please touch the sensor again (2/10) 224s (process:2434): libfprint-device-DEBUG: 16:49:01.651: Device reported enroll progress, reported 2 of 10 have been completed 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.651: [egismoc] ENROLL_STATES entering state 8 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.651: Execute command and get response 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.651: Get check bytes 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.651: [egismoc] CMD_STATES entering state 0 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.652: [egismoc] CMD_STATES entering state 1 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.652: Command receive callback 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.652: [egismoc] CMD_STATES completed successfully 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.652: Task SSM next state callback 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.652: [egismoc] ENROLL_STATES entering state 9 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.652: Execute command and get response 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.652: Get check bytes 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.652: [egismoc] CMD_STATES entering state 0 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.653: [egismoc] CMD_STATES entering state 1 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.653: Command receive callback 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.653: [egismoc] CMD_STATES completed successfully 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.653: Task SSM next state callback 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.653: [egismoc] ENROLL_STATES entering state 10 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.653: Wait for finger on sensor 224s (process:2434): libfprint-device-DEBUG: 16:49:01.653: Device reported finger status change: FP_FINGER_STATUS_NEEDED 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.654: Finger on sensor callback 224s (process:2434): libfprint-device-DEBUG: 16:49:01.654: Device reported finger status change: FP_FINGER_STATUS_PRESENT 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.654: [egismoc] ENROLL_STATES entering state 11 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.654: Execute command and get response 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.654: Get check bytes 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.654: [egismoc] CMD_STATES entering state 0 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.654: [egismoc] CMD_STATES entering state 1 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.655: Command receive callback 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.655: [egismoc] CMD_STATES completed successfully 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.655: Read capture callback 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.655: Response prefix valid: NO 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.655: Response prefix valid: NO 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.655: Response prefix valid: yes 224s (process:2434): libfprint-device-DEBUG: 16:49:01.655: Device reported enroll progress, reported 2 of 10 have been completed 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.655: [egismoc] ENROLL_STATES entering state 8 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.655: Execute command and get response 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.655: Get check bytes 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.655: [egismoc] CMD_STATES entering state 0 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.655: [egismoc] CMD_STATES entering state 1 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.656: Command receive callback 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.656: [egismoc] CMD_STATES completed successfully 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.656: Task SSM next state callback 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.656: [egismoc] ENROLL_STATES entering state 9 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.656: Execute command and get response 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.656: Get check bytes 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.656: [egismoc] CMD_STATES entering state 0 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.656: [egismoc] CMD_STATES entering state 1 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.657: Command receive callback 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.657: [egismoc] CMD_STATES completed successfully 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.657: Task SSM next state callback 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.657: [egismoc] ENROLL_STATES entering state 10 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.657: Wait for finger on sensor 224s (process:2434): libfprint-device-DEBUG: 16:49:01.657: Device reported finger status change: FP_FINGER_STATUS_NEEDED 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.657: Finger on sensor callback 224s (process:2434): libfprint-device-DEBUG: 16:49:01.657: Device reported finger status change: FP_FINGER_STATUS_PRESENT 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.657: [egismoc] ENROLL_STATES entering state 11 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.657: Execute command and get response 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.657: Get check bytes 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.657: [egismoc] CMD_STATES entering state 0 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.657: [egismoc] CMD_STATES entering state 1 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.658: Command receive callback 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.658: [egismoc] CMD_STATES completed successfully 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.658: Read capture callback 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.658: Response prefix valid: yes 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.658: Response suffix valid: yes 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.658: Partial capture successful. Please touch the sensor again (3/10) 224s (process:2434): libfprint-device-DEBUG: 16:49:01.658: Device reported enroll progress, reported 3 of 10 have been completed 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.658: [egismoc] ENROLL_STATES entering state 8 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.658: Execute command and get response 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.658: Get check bytes 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.658: [egismoc] CMD_STATES entering state 0 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.658: [egismoc] CMD_STATES entering state 1 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.659: Command receive callback 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.659: [egismoc] CMD_STATES completed successfully 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.659: Task SSM next state callback 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.659: [egismoc] ENROLL_STATES entering state 9 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.659: Execute command and get response 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.659: Get check bytes 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.659: [egismoc] CMD_STATES entering state 0 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.659: [egismoc] CMD_STATES entering state 1 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.660: Command receive callback 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.660: [egismoc] CMD_STATES completed successfully 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.660: Task SSM next state callback 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.660: [egismoc] ENROLL_STATES entering state 10 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.660: Wait for finger on sensor 224s (process:2434): libfprint-device-DEBUG: 16:49:01.660: Device reported finger status change: FP_FINGER_STATUS_NEEDED 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.660: Finger on sensor callback 224s (process:2434): libfprint-device-DEBUG: 16:49:01.660: Device reported finger status change: FP_FINGER_STATUS_PRESENT 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.660: [egismoc] ENROLL_STATES entering state 11 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.660: Execute command and get response 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.660: Get check bytes 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.660: [egismoc] CMD_STATES entering state 0 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.660: [egismoc] CMD_STATES entering state 1 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.661: Command receive callback 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.661: [egismoc] CMD_STATES completed successfully 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.661: Read capture callback 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.661: Response prefix valid: yes 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.661: Response suffix valid: yes 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.661: Partial capture successful. Please touch the sensor again (4/10) 224s (process:2434): libfprint-device-DEBUG: 16:49:01.661: Device reported enroll progress, reported 4 of 10 have been completed 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.661: [egismoc] ENROLL_STATES entering state 8 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.661: Execute command and get response 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.661: Get check bytes 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.661: [egismoc] CMD_STATES entering state 0 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.661: [egismoc] CMD_STATES entering state 1 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.662: Command receive callback 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.662: [egismoc] CMD_STATES completed successfully 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.662: Task SSM next state callback 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.662: [egismoc] ENROLL_STATES entering state 9 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.662: Execute command and get response 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.662: Get check bytes 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.662: [egismoc] CMD_STATES entering state 0 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.662: [egismoc] CMD_STATES entering state 1 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.663: Command receive callback 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.663: [egismoc] CMD_STATES completed successfully 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.663: Task SSM next state callback 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.663: [egismoc] ENROLL_STATES entering state 10 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.663: Wait for finger on sensor 224s (process:2434): libfprint-device-DEBUG: 16:49:01.663: Device reported finger status change: FP_FINGER_STATUS_NEEDED 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.663: Finger on sensor callback 224s (process:2434): libfprint-device-DEBUG: 16:49:01.663: Device reported finger status change: FP_FINGER_STATUS_PRESENT 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.663: [egismoc] ENROLL_STATES entering state 11 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.663: Execute command and get response 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.663: Get check bytes 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.663: [egismoc] CMD_STATES entering state 0 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.664: [egismoc] CMD_STATES entering state 1 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.664: Command receive callback 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.664: [egismoc] CMD_STATES completed successfully 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.664: Read capture callback 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.664: Response prefix valid: yes 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.664: Response suffix valid: yes 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.664: Partial capture successful. Please touch the sensor again (5/10) 224s (process:2434): libfprint-device-DEBUG: 16:49:01.664: Device reported enroll progress, reported 5 of 10 have been completed 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.664: [egismoc] ENROLL_STATES entering state 8 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.664: Execute command and get response 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.664: Get check bytes 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.664: [egismoc] CMD_STATES entering state 0 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.665: [egismoc] CMD_STATES entering state 1 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.665: Command receive callback 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.665: [egismoc] CMD_STATES completed successfully 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.665: Task SSM next state callback 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.665: [egismoc] ENROLL_STATES entering state 9 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.665: Execute command and get response 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.665: Get check bytes 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.665: [egismoc] CMD_STATES entering state 0 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.666: [egismoc] CMD_STATES entering state 1 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.666: Command receive callback 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.666: [egismoc] CMD_STATES completed successfully 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.666: Task SSM next state callback 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.666: [egismoc] ENROLL_STATES entering state 10 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.666: Wait for finger on sensor 224s (process:2434): libfprint-device-DEBUG: 16:49:01.666: Device reported finger status change: FP_FINGER_STATUS_NEEDED 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.667: Finger on sensor callback 224s (process:2434): libfprint-device-DEBUG: 16:49:01.667: Device reported finger status change: FP_FINGER_STATUS_PRESENT 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.667: [egismoc] ENROLL_STATES entering state 11 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.667: Execute command and get response 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.667: Get check bytes 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.667: [egismoc] CMD_STATES entering state 0 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.667: [egismoc] CMD_STATES entering state 1 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.668: Command receive callback 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.668: [egismoc] CMD_STATES completed successfully 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.668: Read capture callback 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.668: Response prefix valid: yes 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.668: Response suffix valid: yes 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.668: Partial capture successful. Please touch the sensor again (6/10) 224s (process:2434): libfprint-device-DEBUG: 16:49:01.668: Device reported enroll progress, reported 6 of 10 have been completed 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.668: [egismoc] ENROLL_STATES entering state 8 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.668: Execute command and get response 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.668: Get check bytes 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.668: [egismoc] CMD_STATES entering state 0 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.668: [egismoc] CMD_STATES entering state 1 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.669: Command receive callback 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.669: [egismoc] CMD_STATES completed successfully 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.669: Task SSM next state callback 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.669: [egismoc] ENROLL_STATES entering state 9 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.669: Execute command and get response 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.669: Get check bytes 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.669: [egismoc] CMD_STATES entering state 0 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.669: [egismoc] CMD_STATES entering state 1 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.670: Command receive callback 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.670: [egismoc] CMD_STATES completed successfully 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.670: Task SSM next state callback 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.670: [egismoc] ENROLL_STATES entering state 10 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.670: Wait for finger on sensor 224s (process:2434): libfprint-device-DEBUG: 16:49:01.670: Device reported finger status change: FP_FINGER_STATUS_NEEDED 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.670: Finger on sensor callback 224s (process:2434): libfprint-device-DEBUG: 16:49:01.670: Device reported finger status change: FP_FINGER_STATUS_PRESENT 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.670: [egismoc] ENROLL_STATES entering state 11 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.670: Execute command and get response 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.670: Get check bytes 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.670: [egismoc] CMD_STATES entering state 0 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.671: [egismoc] CMD_STATES entering state 1 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.671: Command receive callback 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.671: [egismoc] CMD_STATES completed successfully 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.671: Read capture callback 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.671: Response prefix valid: yes 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.671: Response suffix valid: yes 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.671: Partial capture successful. Please touch the sensor again (7/10) 224s (process:2434): libfprint-device-DEBUG: 16:49:01.671: Device reported enroll progress, reported 7 of 10 have been completed 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.671: [egismoc] ENROLL_STATES entering state 8 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.671: Execute command and get response 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.671: Get check bytes 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.671: [egismoc] CMD_STATES entering state 0 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.672: [egismoc] CMD_STATES entering state 1 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.672: Command receive callback 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.672: [egismoc] CMD_STATES completed successfully 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.672: Task SSM next state callback 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.672: [egismoc] ENROLL_STATES entering state 9 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.672: Execute command and get response 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.672: Get check bytes 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.672: [egismoc] CMD_STATES entering state 0 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.673: [egismoc] CMD_STATES entering state 1 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.673: Command receive callback 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.673: [egismoc] CMD_STATES completed successfully 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.673: Task SSM next state callback 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.673: [egismoc] ENROLL_STATES entering state 10 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.673: Wait for finger on sensor 224s (process:2434): libfprint-device-DEBUG: 16:49:01.673: Device reported finger status change: FP_FINGER_STATUS_NEEDED 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.674: Finger on sensor callback 224s (process:2434): libfprint-device-DEBUG: 16:49:01.674: Device reported finger status change: FP_FINGER_STATUS_PRESENT 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.674: [egismoc] ENROLL_STATES entering state 11 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.674: Execute command and get response 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.674: Get check bytes 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.674: [egismoc] CMD_STATES entering state 0 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.674: [egismoc] CMD_STATES entering state 1 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.675: Command receive callback 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.675: [egismoc] CMD_STATES completed successfully 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.675: Read capture callback 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.675: Response prefix valid: yes 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.675: Response suffix valid: yes 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.675: Partial capture successful. Please touch the sensor again (8/10) 224s (process:2434): libfprint-device-DEBUG: 16:49:01.675: Device reported enroll progress, reported 8 of 10 have been completed 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.675: [egismoc] ENROLL_STATES entering state 8 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.675: Execute command and get response 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.675: Get check bytes 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.675: [egismoc] CMD_STATES entering state 0 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.675: [egismoc] CMD_STATES entering state 1 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.676: Command receive callback 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.676: [egismoc] CMD_STATES completed successfully 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.676: Task SSM next state callback 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.676: [egismoc] ENROLL_STATES entering state 9 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.676: Execute command and get response 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.676: Get check bytes 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.676: [egismoc] CMD_STATES entering state 0 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.676: [egismoc] CMD_STATES entering state 1 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.677: Command receive callback 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.677: [egismoc] CMD_STATES completed successfully 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.677: Task SSM next state callback 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.677: [egismoc] ENROLL_STATES entering state 10 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.677: Wait for finger on sensor 224s (process:2434): libfprint-device-DEBUG: 16:49:01.677: Device reported finger status change: FP_FINGER_STATUS_NEEDED 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.677: Finger on sensor callback 224s (process:2434): libfprint-device-DEBUG: 16:49:01.677: Device reported finger status change: FP_FINGER_STATUS_PRESENT 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.677: [egismoc] ENROLL_STATES entering state 11 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.677: Execute command and get response 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.677: Get check bytes 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.677: [egismoc] CMD_STATES entering state 0 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.678: [egismoc] CMD_STATES entering state 1 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.678: Command receive callback 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.678: [egismoc] CMD_STATES completed successfully 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.678: Read capture callback 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.678: Response prefix valid: yes 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.678: Response suffix valid: yes 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.678: Partial capture successful. Please touch the sensor again (9/10) 224s (process:2434): libfprint-device-DEBUG: 16:49:01.678: Device reported enroll progress, reported 9 of 10 have been completed 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.678: [egismoc] ENROLL_STATES entering state 8 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.678: Execute command and get response 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.678: Get check bytes 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.678: [egismoc] CMD_STATES entering state 0 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.679: [egismoc] CMD_STATES entering state 1 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.679: Command receive callback 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.679: [egismoc] CMD_STATES completed successfully 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.679: Task SSM next state callback 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.679: [egismoc] ENROLL_STATES entering state 9 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.679: Execute command and get response 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.679: Get check bytes 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.679: [egismoc] CMD_STATES entering state 0 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.680: [egismoc] CMD_STATES entering state 1 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.680: Command receive callback 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.680: [egismoc] CMD_STATES completed successfully 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.680: Task SSM next state callback 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.680: [egismoc] ENROLL_STATES entering state 10 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.680: Wait for finger on sensor 224s (process:2434): libfprint-device-DEBUG: 16:49:01.680: Device reported finger status change: FP_FINGER_STATUS_NEEDED 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.681: Finger on sensor callback 224s (process:2434): libfprint-device-DEBUG: 16:49:01.681: Device reported finger status change: FP_FINGER_STATUS_PRESENT 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.681: [egismoc] ENROLL_STATES entering state 11 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.681: Execute command and get response 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.681: Get check bytes 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.681: [egismoc] CMD_STATES entering state 0 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.681: [egismoc] CMD_STATES entering state 1 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.681: Command receive callback 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.681: [egismoc] CMD_STATES completed successfully 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.681: Read capture callback 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.681: Response prefix valid: yes 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.681: Response suffix valid: yes 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.682: Partial capture successful. Please touch the sensor again (10/10) 224s (process:2434): libfprint-device-DEBUG: 16:49:01.682: Device reported enroll progress, reported 10 of 10 have been completed 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.682: [egismoc] ENROLL_STATES entering state 12 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.682: Execute command and get response 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.682: Get check bytes 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.682: [egismoc] CMD_STATES entering state 0 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.682: [egismoc] CMD_STATES entering state 1 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.682: Command receive callback 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.682: [egismoc] CMD_STATES completed successfully 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.682: Task SSM next state callback 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.682: [egismoc] ENROLL_STATES entering state 13 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.682: New fingerprint ID: FP1-00000000-2-00000000-nobody 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.682: Execute command and get response 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.682: Get check bytes 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.682: [egismoc] CMD_STATES entering state 0 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.683: [egismoc] CMD_STATES entering state 1 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.683: Command receive callback 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.683: [egismoc] CMD_STATES completed successfully 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.683: Task SSM next state callback 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.683: [egismoc] ENROLL_STATES entering state 14 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.683: Execute command and get response 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.683: Get check bytes 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.683: [egismoc] CMD_STATES entering state 0 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.684: [egismoc] CMD_STATES entering state 1 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.684: Command receive callback 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.684: [egismoc] CMD_STATES completed successfully 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.684: Task SSM next state callback 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.684: [egismoc] ENROLL_STATES entering state 15 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.684: Enrollment was successful! 224s (process:2434): libfprint-device-DEBUG: 16:49:01.684: Device reported enroll completion 224s (process:2434): libfprint-device-DEBUG: 16:49:01.684: Device reported finger status change: FP_FINGER_STATUS_NONE 224s (process:2434): libfprint-device-DEBUG: 16:49:01.684: Print for finger FP_FINGER_LEFT_INDEX enrolled 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.684: [egismoc] ENROLL_STATES completed successfully 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.684: Task SSM done 224s (process:2434): libfprint-device-DEBUG: 16:49:01.684: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 224s (process:2434): libfprint-device-DEBUG: 16:49:01.684: Updated temperature model after 0.06 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.684: List 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.684: [egismoc] LIST_STATES entering state 0 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.684: Execute command and get response 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.684: Get check bytes 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.684: [egismoc] CMD_STATES entering state 0 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.685: [egismoc] CMD_STATES entering state 1 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.685: Command receive callback 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.685: [egismoc] CMD_STATES completed successfully 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.685: List callback 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.685: Device fingerprint 0: FP1-00000000-2-00000000-nobody 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.685: Number of currently enrolled fingerprints on the device is 1 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.685: [egismoc] LIST_STATES entering state 1 224s (process:2434): libfprint-device-DEBUG: 16:49:01.685: Device reported listing completion 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.685: [egismoc] LIST_STATES completed successfully 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.685: Task SSM done 224s (process:2434): libfprint-device-DEBUG: 16:49:01.686: Completing action FPI_DEVICE_ACTION_LIST in idle! 224s (process:2434): libfprint-device-DEBUG: 16:49:01.686: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 224s (process:2434): libfprint-device-DEBUG: 16:49:01.686: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.686: Identify or Verify 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.686: [egismoc] IDENTIFY_STATES entering state 0 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.686: Execute command and get response 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.686: Get check bytes 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.686: [egismoc] CMD_STATES entering state 0 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.686: [egismoc] CMD_STATES entering state 1 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.687: Command receive callback 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.687: [egismoc] CMD_STATES completed successfully 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.687: List callback 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.687: Device fingerprint 0: FP1-00000000-2-00000000-nobody 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.687: Number of currently enrolled fingerprints on the device is 1 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.687: [egismoc] IDENTIFY_STATES entering state 1 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.687: [egismoc] IDENTIFY_STATES entering state 2 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.687: Execute command and get response 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.687: Get check bytes 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.687: [egismoc] CMD_STATES entering state 0 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.688: [egismoc] CMD_STATES entering state 1 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.688: Command receive callback 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.688: [egismoc] CMD_STATES completed successfully 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.688: Task SSM next state callback 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.688: [egismoc] IDENTIFY_STATES entering state 3 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.688: Execute command and get response 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.688: Get check bytes 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.688: [egismoc] CMD_STATES entering state 0 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.689: [egismoc] CMD_STATES entering state 1 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.689: Command receive callback 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.689: [egismoc] CMD_STATES completed successfully 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.689: Task SSM next state callback 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.689: [egismoc] IDENTIFY_STATES entering state 4 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.689: Wait for finger on sensor 224s (process:2434): libfprint-device-DEBUG: 16:49:01.689: Device reported finger status change: FP_FINGER_STATUS_NEEDED 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.690: Finger on sensor callback 224s (process:2434): libfprint-device-DEBUG: 16:49:01.690: Device reported finger status change: FP_FINGER_STATUS_PRESENT 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.690: [egismoc] IDENTIFY_STATES entering state 5 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.690: Execute command and get response 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.690: Get check bytes 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.690: [egismoc] CMD_STATES entering state 0 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.690: [egismoc] CMD_STATES entering state 1 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.690: Command receive callback 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.690: [egismoc] CMD_STATES completed successfully 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.690: Task SSM next state callback 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.690: [egismoc] IDENTIFY_STATES entering state 6 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.690: Get check command 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.690: Execute command and get response 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.690: Get check bytes 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.690: [egismoc] CMD_STATES entering state 0 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.691: [egismoc] CMD_STATES entering state 1 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.691: Command receive callback 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.691: [egismoc] CMD_STATES completed successfully 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.691: Identify check callback 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.691: Response suffix valid: yes 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.691: Identify successful for: FP1-00000000-2-00000000-nobody 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.691: Verifying against: FP1-00000000-2-00000000-nobody 224s (process:2434): libfprint-device-DEBUG: 16:49:01.691: Device reported verify result 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.691: [egismoc] IDENTIFY_STATES entering state 7 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.691: Execute command and get response 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.691: Get check bytes 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.691: [egismoc] CMD_STATES entering state 0 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.692: [egismoc] CMD_STATES entering state 1 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.692: Command receive callback 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.692: [egismoc] CMD_STATES completed successfully 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.692: Task SSM next state callback 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.692: [egismoc] IDENTIFY_STATES entering state 8 224s (process:2434): libfprint-device-DEBUG: 16:49:01.692: Device reported verify completion 224s (process:2434): libfprint-device-DEBUG: 16:49:01.692: Device reported finger status change: FP_FINGER_STATUS_NONE 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.692: [egismoc] IDENTIFY_STATES completed successfully 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.692: Task SSM done 224s (process:2434): libfprint-device-DEBUG: 16:49:01.692: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 224s (process:2434): libfprint-device-DEBUG: 16:49:01.692: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 224s (process:2434): libfprint-device-DEBUG: 16:49:01.693: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.693: Identify or Verify 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.693: [egismoc] IDENTIFY_STATES entering state 0 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.693: Execute command and get response 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.693: Get check bytes 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.693: [egismoc] CMD_STATES entering state 0 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.693: [egismoc] CMD_STATES entering state 1 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.694: Command receive callback 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.694: [egismoc] CMD_STATES completed successfully 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.694: List callback 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.694: Device fingerprint 0: FP1-00000000-2-00000000-nobody 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.694: Number of currently enrolled fingerprints on the device is 1 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.694: [egismoc] IDENTIFY_STATES entering state 1 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.694: [egismoc] IDENTIFY_STATES entering state 2 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.694: Execute command and get response 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.694: Get check bytes 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.694: [egismoc] CMD_STATES entering state 0 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.694: [egismoc] CMD_STATES entering state 1 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.695: Command receive callback 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.695: [egismoc] CMD_STATES completed successfully 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.695: Task SSM next state callback 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.695: [egismoc] IDENTIFY_STATES entering state 3 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.695: Execute command and get response 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.695: Get check bytes 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.695: [egismoc] CMD_STATES entering state 0 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.695: [egismoc] CMD_STATES entering state 1 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.696: Command receive callback 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.696: [egismoc] CMD_STATES completed successfully 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.696: Task SSM next state callback 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.696: [egismoc] IDENTIFY_STATES entering state 4 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.696: Wait for finger on sensor 224s (process:2434): libfprint-device-DEBUG: 16:49:01.696: Device reported finger status change: FP_FINGER_STATUS_NEEDED 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.696: Finger on sensor callback 224s (process:2434): libfprint-device-DEBUG: 16:49:01.696: Device reported finger status change: FP_FINGER_STATUS_PRESENT 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.696: [egismoc] IDENTIFY_STATES entering state 5 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.696: Execute command and get response 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.696: Get check bytes 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.696: [egismoc] CMD_STATES entering state 0 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.697: [egismoc] CMD_STATES entering state 1 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.697: Command receive callback 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.697: [egismoc] CMD_STATES completed successfully 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.697: Task SSM next state callback 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.697: [egismoc] IDENTIFY_STATES entering state 6 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.697: Get check command 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.697: Execute command and get response 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.697: Get check bytes 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.697: [egismoc] CMD_STATES entering state 0 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.698: [egismoc] CMD_STATES entering state 1 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.698: Command receive callback 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.698: [egismoc] CMD_STATES completed successfully 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.698: Identify check callback 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.698: Response suffix valid: yes 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.698: Identify successful for: FP1-00000000-2-00000000-nobody 224s (process:2434): libfprint-device-DEBUG: 16:49:01.698: Device reported identify result 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.698: [egismoc] IDENTIFY_STATES entering state 7 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.698: Execute command and get response 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.698: Get check bytes 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.698: [egismoc] CMD_STATES entering state 0 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.699: [egismoc] CMD_STATES entering state 1 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.699: Command receive callback 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.699: [egismoc] CMD_STATES completed successfully 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.699: Task SSM next state callback 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.699: [egismoc] IDENTIFY_STATES entering state 8 224s (process:2434): libfprint-device-DEBUG: 16:49:01.699: Device reported identify completion 224s (process:2434): libfprint-device-DEBUG: 16:49:01.699: Device reported finger status change: FP_FINGER_STATUS_NONE 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.699: [egismoc] IDENTIFY_STATES completed successfully 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.699: Task SSM done 224s (process:2434): libfprint-device-DEBUG: 16:49:01.699: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 224s (process:2434): libfprint-device-DEBUG: 16:49:01.699: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 224s (process:2434): libfprint-device-DEBUG: 16:49:01.700: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.700: Enroll 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.700: [egismoc] ENROLL_STATES entering state 0 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.700: Execute command and get response 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.700: Get check bytes 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.700: [egismoc] CMD_STATES entering state 0 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.700: [egismoc] CMD_STATES entering state 1 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.701: Command receive callback 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.701: [egismoc] CMD_STATES completed successfully 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.701: List callback 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.701: Device fingerprint 0: FP1-00000000-2-00000000-nobody 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.701: Number of currently enrolled fingerprints on the device is 1 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.701: [egismoc] ENROLL_STATES entering state 1 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.701: [egismoc] ENROLL_STATES entering state 2 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.701: Execute command and get response 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.701: Get check bytes 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.701: [egismoc] CMD_STATES entering state 0 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.702: [egismoc] CMD_STATES entering state 1 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.702: Command receive callback 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.702: [egismoc] CMD_STATES completed successfully 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.702: Task SSM next state callback 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.702: [egismoc] ENROLL_STATES entering state 3 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.702: Execute command and get response 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.702: Get check bytes 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.702: [egismoc] CMD_STATES entering state 0 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.703: [egismoc] CMD_STATES entering state 1 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.703: Command receive callback 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.703: [egismoc] CMD_STATES completed successfully 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.703: Task SSM next state callback 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.703: [egismoc] ENROLL_STATES entering state 4 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.703: Wait for finger on sensor 224s (process:2434): libfprint-device-DEBUG: 16:49:01.703: Device reported finger status change: FP_FINGER_STATUS_NEEDED 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.704: Finger on sensor callback 224s (process:2434): libfprint-device-DEBUG: 16:49:01.704: Device reported finger status change: FP_FINGER_STATUS_PRESENT 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.704: [egismoc] ENROLL_STATES entering state 5 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.704: Execute command and get response 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.704: Get check bytes 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.704: [egismoc] CMD_STATES entering state 0 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.704: [egismoc] CMD_STATES entering state 1 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.704: Command receive callback 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.704: [egismoc] CMD_STATES completed successfully 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.704: Task SSM next state callback 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.704: [egismoc] ENROLL_STATES entering state 6 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.704: Get check command 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.704: Execute command and get response 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.704: Get check bytes 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.704: [egismoc] CMD_STATES entering state 0 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.705: [egismoc] CMD_STATES entering state 1 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.705: Command receive callback 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.705: [egismoc] CMD_STATES completed successfully 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.705: Enroll check callback 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.705: Response suffix valid: NO 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.705: [egismoc] SSM ENROLL_STATES failed in state 6 with error: This finger has already enrolled, please try a different finger 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.705: [egismoc] ENROLL_STATES completed with error: This finger has already enrolled, please try a different finger 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.705: Task SSM done 224s (process:2434): libfprint-device-DEBUG: 16:49:01.705: Device reported generic error (This finger has already enrolled, please try a different finger) during action; action was: FPI_DEVICE_ACTION_ENROLL 224s (process:2434): libfprint-device-DEBUG: 16:49:01.705: Device reported enroll completion 224s (process:2434): libfprint-device-DEBUG: 16:49:01.705: Device reported finger status change: FP_FINGER_STATUS_NONE 224s (process:2434): libfprint-device-DEBUG: 16:49:01.705: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 224s (process:2434): libfprint-device-DEBUG: 16:49:01.705: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.706: List 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.706: [egismoc] LIST_STATES entering state 0 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.706: Execute command and get response 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.706: Get check bytes 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.706: [egismoc] CMD_STATES entering state 0 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.706: [egismoc] CMD_STATES entering state 1 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.707: Command receive callback 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.707: [egismoc] CMD_STATES completed successfully 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.707: List callback 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.707: Device fingerprint 0: FP1-00000000-2-00000000-nobody 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.707: Number of currently enrolled fingerprints on the device is 1 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.707: [egismoc] LIST_STATES entering state 1 224s (process:2434): libfprint-device-DEBUG: 16:49:01.707: Device reported listing completion 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.707: [egismoc] LIST_STATES completed successfully 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.707: Task SSM done 224s (process:2434): libfprint-device-DEBUG: 16:49:01.707: Completing action FPI_DEVICE_ACTION_LIST in idle! 224s (process:2434): libfprint-device-DEBUG: 16:49:01.707: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 224s (process:2434): libfprint-device-DEBUG: 16:49:01.707: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.707: Enroll 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.707: [egismoc] ENROLL_STATES entering state 0 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.707: Execute command and get response 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.707: Get check bytes 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.707: [egismoc] CMD_STATES entering state 0 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.707: [egismoc] CMD_STATES entering state 1 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.708: Command receive callback 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.708: [egismoc] CMD_STATES completed successfully 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.708: List callback 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.708: Device fingerprint 0: FP1-00000000-2-00000000-nobody 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.708: Number of currently enrolled fingerprints on the device is 1 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.708: [egismoc] ENROLL_STATES entering state 1 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.708: [egismoc] ENROLL_STATES entering state 2 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.708: Execute command and get response 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.708: Get check bytes 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.708: [egismoc] CMD_STATES entering state 0 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.708: [egismoc] CMD_STATES entering state 1 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.709: Command receive callback 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.709: [egismoc] CMD_STATES completed successfully 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.709: Task SSM next state callback 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.709: [egismoc] ENROLL_STATES entering state 3 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.709: Execute command and get response 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.709: Get check bytes 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.709: [egismoc] CMD_STATES entering state 0 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.709: [egismoc] CMD_STATES entering state 1 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.710: Command receive callback 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.710: [egismoc] CMD_STATES completed successfully 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.710: Task SSM next state callback 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.710: [egismoc] ENROLL_STATES entering state 4 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.710: Wait for finger on sensor 224s (process:2434): libfprint-device-DEBUG: 16:49:01.710: Device reported finger status change: FP_FINGER_STATUS_NEEDED 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.710: Finger on sensor callback 224s (process:2434): libfprint-device-DEBUG: 16:49:01.710: Device reported finger status change: FP_FINGER_STATUS_PRESENT 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.710: [egismoc] ENROLL_STATES entering state 5 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.710: Execute command and get response 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.710: Get check bytes 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.710: [egismoc] CMD_STATES entering state 0 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.711: [egismoc] CMD_STATES entering state 1 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.711: Command receive callback 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.711: [egismoc] CMD_STATES completed successfully 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.711: Task SSM next state callback 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.711: [egismoc] ENROLL_STATES entering state 6 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.711: Get check command 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.711: Execute command and get response 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.711: Get check bytes 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.711: [egismoc] CMD_STATES entering state 0 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.712: [egismoc] CMD_STATES entering state 1 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.712: Command receive callback 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.712: [egismoc] CMD_STATES completed successfully 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.712: Enroll check callback 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.712: Response suffix valid: yes 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.712: [egismoc] ENROLL_STATES entering state 7 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.712: Execute command and get response 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.712: Get check bytes 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.712: [egismoc] CMD_STATES entering state 0 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.713: [egismoc] CMD_STATES entering state 1 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.713: Command receive callback 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.713: [egismoc] CMD_STATES completed successfully 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.713: Task SSM next state callback 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.713: [egismoc] ENROLL_STATES entering state 8 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.713: Execute command and get response 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.713: Get check bytes 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.713: [egismoc] CMD_STATES entering state 0 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.713: [egismoc] CMD_STATES entering state 1 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.714: Command receive callback 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.714: [egismoc] CMD_STATES completed successfully 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.714: Task SSM next state callback 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.714: [egismoc] ENROLL_STATES entering state 9 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.714: Execute command and get response 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.714: Get check bytes 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.714: [egismoc] CMD_STATES entering state 0 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.714: [egismoc] CMD_STATES entering state 1 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.715: Command receive callback 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.715: [egismoc] CMD_STATES completed successfully 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.715: Task SSM next state callback 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.715: [egismoc] ENROLL_STATES entering state 10 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.715: Wait for finger on sensor 224s (process:2434): libfprint-device-DEBUG: 16:49:01.715: Device reported finger status change: FP_FINGER_STATUS_NEEDED 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.715: Finger on sensor callback 224s (process:2434): libfprint-device-DEBUG: 16:49:01.715: Device reported finger status change: FP_FINGER_STATUS_PRESENT 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.715: [egismoc] ENROLL_STATES entering state 11 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.715: Execute command and get response 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.715: Get check bytes 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.715: [egismoc] CMD_STATES entering state 0 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.716: [egismoc] CMD_STATES entering state 1 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.716: Command receive callback 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.716: [egismoc] CMD_STATES completed successfully 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.716: Read capture callback 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.716: Response prefix valid: yes 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.716: Response suffix valid: yes 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.716: Partial capture successful. Please touch the sensor again (1/10) 224s (process:2434): libfprint-device-DEBUG: 16:49:01.716: Device reported enroll progress, reported 1 of 10 have been completed 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.716: [egismoc] ENROLL_STATES entering state 8 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.716: Execute command and get response 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.716: Get check bytes 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.716: [egismoc] CMD_STATES entering state 0 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.717: [egismoc] CMD_STATES entering state 1 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.717: Command receive callback 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.717: [egismoc] CMD_STATES completed successfully 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.717: Task SSM next state callback 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.717: [egismoc] ENROLL_STATES entering state 9 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.717: Execute command and get response 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.717: Get check bytes 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.717: [egismoc] CMD_STATES entering state 0 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.717: [egismoc] CMD_STATES entering state 1 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.718: Command receive callback 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.718: [egismoc] CMD_STATES completed successfully 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.718: Task SSM next state callback 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.718: [egismoc] ENROLL_STATES entering state 10 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.718: Wait for finger on sensor 224s (process:2434): libfprint-device-DEBUG: 16:49:01.718: Device reported finger status change: FP_FINGER_STATUS_NEEDED 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.718: Finger on sensor callback 224s (process:2434): libfprint-device-DEBUG: 16:49:01.718: Device reported finger status change: FP_FINGER_STATUS_PRESENT 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.718: [egismoc] ENROLL_STATES entering state 11 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.718: Execute command and get response 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.718: Get check bytes 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.718: [egismoc] CMD_STATES entering state 0 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.719: [egismoc] CMD_STATES entering state 1 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.719: Command receive callback 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.719: [egismoc] CMD_STATES completed successfully 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.719: Read capture callback 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.719: Response prefix valid: yes 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.719: Response suffix valid: yes 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.719: Partial capture successful. Please touch the sensor again (2/10) 224s (process:2434): libfprint-device-DEBUG: 16:49:01.719: Device reported enroll progress, reported 2 of 10 have been completed 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.719: [egismoc] ENROLL_STATES entering state 8 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.719: Execute command and get response 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.719: Get check bytes 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.719: [egismoc] CMD_STATES entering state 0 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.720: [egismoc] CMD_STATES entering state 1 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.720: Command receive callback 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.720: [egismoc] CMD_STATES completed successfully 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.720: Task SSM next state callback 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.720: [egismoc] ENROLL_STATES entering state 9 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.720: Execute command and get response 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.720: Get check bytes 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.720: [egismoc] CMD_STATES entering state 0 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.721: [egismoc] CMD_STATES entering state 1 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.721: Command receive callback 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.721: [egismoc] CMD_STATES completed successfully 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.721: Task SSM next state callback 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.721: [egismoc] ENROLL_STATES entering state 10 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.721: Wait for finger on sensor 224s (process:2434): libfprint-device-DEBUG: 16:49:01.721: Device reported finger status change: FP_FINGER_STATUS_NEEDED 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.722: Finger on sensor callback 224s (process:2434): libfprint-device-DEBUG: 16:49:01.722: Device reported finger status change: FP_FINGER_STATUS_PRESENT 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.722: [egismoc] ENROLL_STATES entering state 11 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.722: Execute command and get response 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.722: Get check bytes 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.722: [egismoc] CMD_STATES entering state 0 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.722: [egismoc] CMD_STATES entering state 1 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.722: Command receive callback 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.722: [egismoc] CMD_STATES completed successfully 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.722: Read capture callback 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.722: Response prefix valid: yes 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.722: Response suffix valid: NO 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.722: Response prefix valid: yes 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.722: Response suffix valid: yes 224s (process:2434): libfprint-device-DEBUG: 16:49:01.722: Device reported enroll progress, reported 2 of 10 have been completed 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.722: [egismoc] ENROLL_STATES entering state 8 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.722: Execute command and get response 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.722: Get check bytes 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.722: [egismoc] CMD_STATES entering state 0 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.723: [egismoc] CMD_STATES entering state 1 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.723: Command receive callback 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.723: [egismoc] CMD_STATES completed successfully 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.723: Task SSM next state callback 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.723: [egismoc] ENROLL_STATES entering state 9 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.723: Execute command and get response 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.723: Get check bytes 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.723: [egismoc] CMD_STATES entering state 0 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.724: [egismoc] CMD_STATES entering state 1 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.724: Command receive callback 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.724: [egismoc] CMD_STATES completed successfully 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.724: Task SSM next state callback 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.724: [egismoc] ENROLL_STATES entering state 10 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.724: Wait for finger on sensor 224s (process:2434): libfprint-device-DEBUG: 16:49:01.724: Device reported finger status change: FP_FINGER_STATUS_NEEDED 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.725: Finger on sensor callback 224s (process:2434): libfprint-device-DEBUG: 16:49:01.725: Device reported finger status change: FP_FINGER_STATUS_PRESENT 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.725: [egismoc] ENROLL_STATES entering state 11 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.725: Execute command and get response 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.725: Get check bytes 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.725: [egismoc] CMD_STATES entering state 0 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.725: [egismoc] CMD_STATES entering state 1 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.725: Command receive callback 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.725: [egismoc] CMD_STATES completed successfully 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.725: Read capture callback 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.725: Response prefix valid: yes 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.725: Response suffix valid: NO 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.725: Response prefix valid: yes 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.725: Response suffix valid: yes 224s (process:2434): libfprint-device-DEBUG: 16:49:01.725: Device reported enroll progress, reported 2 of 10 have been completed 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.726: [egismoc] ENROLL_STATES entering state 8 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.726: Execute command and get response 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.726: Get check bytes 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.726: [egismoc] CMD_STATES entering state 0 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.726: [egismoc] CMD_STATES entering state 1 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.726: Command receive callback 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.726: [egismoc] CMD_STATES completed successfully 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.726: Task SSM next state callback 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.726: [egismoc] ENROLL_STATES entering state 9 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.726: Execute command and get response 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.726: Get check bytes 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.726: [egismoc] CMD_STATES entering state 0 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.727: [egismoc] CMD_STATES entering state 1 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.727: Command receive callback 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.727: [egismoc] CMD_STATES completed successfully 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.727: Task SSM next state callback 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.727: [egismoc] ENROLL_STATES entering state 10 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.727: Wait for finger on sensor 224s (process:2434): libfprint-device-DEBUG: 16:49:01.727: Device reported finger status change: FP_FINGER_STATUS_NEEDED 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.728: Finger on sensor callback 224s (process:2434): libfprint-device-DEBUG: 16:49:01.728: Device reported finger status change: FP_FINGER_STATUS_PRESENT 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.728: [egismoc] ENROLL_STATES entering state 11 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.728: Execute command and get response 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.728: Get check bytes 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.728: [egismoc] CMD_STATES entering state 0 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.728: [egismoc] CMD_STATES entering state 1 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.729: Command receive callback 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.729: [egismoc] CMD_STATES completed successfully 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.729: Read capture callback 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.729: Response prefix valid: yes 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.729: Response suffix valid: yes 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.729: Partial capture successful. Please touch the sensor again (3/10) 224s (process:2434): libfprint-device-DEBUG: 16:49:01.729: Device reported enroll progress, reported 3 of 10 have been completed 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.729: [egismoc] ENROLL_STATES entering state 8 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.729: Execute command and get response 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.729: Get check bytes 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.729: [egismoc] CMD_STATES entering state 0 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.729: [egismoc] CMD_STATES entering state 1 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.730: Command receive callback 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.730: [egismoc] CMD_STATES completed successfully 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.730: Task SSM next state callback 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.730: [egismoc] ENROLL_STATES entering state 9 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.730: Execute command and get response 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.730: Get check bytes 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.730: [egismoc] CMD_STATES entering state 0 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.730: [egismoc] CMD_STATES entering state 1 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.731: Command receive callback 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.731: [egismoc] CMD_STATES completed successfully 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.731: Task SSM next state callback 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.731: [egismoc] ENROLL_STATES entering state 10 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.731: Wait for finger on sensor 224s (process:2434): libfprint-device-DEBUG: 16:49:01.731: Device reported finger status change: FP_FINGER_STATUS_NEEDED 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.731: Finger on sensor callback 224s (process:2434): libfprint-device-DEBUG: 16:49:01.731: Device reported finger status change: FP_FINGER_STATUS_PRESENT 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.731: [egismoc] ENROLL_STATES entering state 11 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.731: Execute command and get response 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.731: Get check bytes 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.731: [egismoc] CMD_STATES entering state 0 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.731: [egismoc] CMD_STATES entering state 1 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.732: Command receive callback 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.732: [egismoc] CMD_STATES completed successfully 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.732: Read capture callback 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.732: Response prefix valid: yes 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.732: Response suffix valid: NO 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.732: Response prefix valid: yes 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.732: Response suffix valid: yes 224s (process:2434): libfprint-device-DEBUG: 16:49:01.732: Device reported enroll progress, reported 3 of 10 have been completed 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.732: [egismoc] ENROLL_STATES entering state 8 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.732: Execute command and get response 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.732: Get check bytes 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.732: [egismoc] CMD_STATES entering state 0 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.732: [egismoc] CMD_STATES entering state 1 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.733: Command receive callback 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.733: [egismoc] CMD_STATES completed successfully 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.733: Task SSM next state callback 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.733: [egismoc] ENROLL_STATES entering state 9 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.733: Execute command and get response 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.733: Get check bytes 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.733: [egismoc] CMD_STATES entering state 0 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.733: [egismoc] CMD_STATES entering state 1 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.734: Command receive callback 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.734: [egismoc] CMD_STATES completed successfully 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.734: Task SSM next state callback 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.734: [egismoc] ENROLL_STATES entering state 10 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.734: Wait for finger on sensor 224s (process:2434): libfprint-device-DEBUG: 16:49:01.734: Device reported finger status change: FP_FINGER_STATUS_NEEDED 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.734: Finger on sensor callback 224s (process:2434): libfprint-device-DEBUG: 16:49:01.734: Device reported finger status change: FP_FINGER_STATUS_PRESENT 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.734: [egismoc] ENROLL_STATES entering state 11 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.734: Execute command and get response 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.735: Get check bytes 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.735: [egismoc] CMD_STATES entering state 0 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.735: [egismoc] CMD_STATES entering state 1 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.735: Command receive callback 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.735: [egismoc] CMD_STATES completed successfully 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.735: Read capture callback 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.735: Response prefix valid: yes 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.735: Response suffix valid: yes 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.735: Partial capture successful. Please touch the sensor again (4/10) 224s (process:2434): libfprint-device-DEBUG: 16:49:01.735: Device reported enroll progress, reported 4 of 10 have been completed 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.736: [egismoc] ENROLL_STATES entering state 8 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.736: Execute command and get response 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.736: Get check bytes 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.736: [egismoc] CMD_STATES entering state 0 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.736: [egismoc] CMD_STATES entering state 1 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.736: Command receive callback 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.736: [egismoc] CMD_STATES completed successfully 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.736: Task SSM next state callback 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.736: [egismoc] ENROLL_STATES entering state 9 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.736: Execute command and get response 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.736: Get check bytes 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.736: [egismoc] CMD_STATES entering state 0 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.737: [egismoc] CMD_STATES entering state 1 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.737: Command receive callback 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.737: [egismoc] CMD_STATES completed successfully 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.737: Task SSM next state callback 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.737: [egismoc] ENROLL_STATES entering state 10 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.737: Wait for finger on sensor 224s (process:2434): libfprint-device-DEBUG: 16:49:01.737: Device reported finger status change: FP_FINGER_STATUS_NEEDED 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.738: Finger on sensor callback 224s (process:2434): libfprint-device-DEBUG: 16:49:01.738: Device reported finger status change: FP_FINGER_STATUS_PRESENT 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.738: [egismoc] ENROLL_STATES entering state 11 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.738: Execute command and get response 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.738: Get check bytes 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.738: [egismoc] CMD_STATES entering state 0 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.738: [egismoc] CMD_STATES entering state 1 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.739: Command receive callback 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.739: [egismoc] CMD_STATES completed successfully 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.739: Read capture callback 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.739: Response prefix valid: yes 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.739: Response suffix valid: yes 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.739: Partial capture successful. Please touch the sensor again (5/10) 224s (process:2434): libfprint-device-DEBUG: 16:49:01.739: Device reported enroll progress, reported 5 of 10 have been completed 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.739: [egismoc] ENROLL_STATES entering state 8 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.739: Execute command and get response 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.739: Get check bytes 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.739: [egismoc] CMD_STATES entering state 0 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.740: [egismoc] CMD_STATES entering state 1 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.740: Command receive callback 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.740: [egismoc] CMD_STATES completed successfully 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.740: Task SSM next state callback 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.740: [egismoc] ENROLL_STATES entering state 9 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.740: Execute command and get response 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.740: Get check bytes 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.740: [egismoc] CMD_STATES entering state 0 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.741: [egismoc] CMD_STATES entering state 1 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.741: Command receive callback 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.741: [egismoc] CMD_STATES completed successfully 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.741: Task SSM next state callback 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.741: [egismoc] ENROLL_STATES entering state 10 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.741: Wait for finger on sensor 224s (process:2434): libfprint-device-DEBUG: 16:49:01.741: Device reported finger status change: FP_FINGER_STATUS_NEEDED 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.742: Finger on sensor callback 224s (process:2434): libfprint-device-DEBUG: 16:49:01.742: Device reported finger status change: FP_FINGER_STATUS_PRESENT 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.742: [egismoc] ENROLL_STATES entering state 11 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.742: Execute command and get response 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.742: Get check bytes 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.742: [egismoc] CMD_STATES entering state 0 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.742: [egismoc] CMD_STATES entering state 1 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.743: Command receive callback 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.743: [egismoc] CMD_STATES completed successfully 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.743: Read capture callback 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.743: Response prefix valid: yes 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.743: Response suffix valid: yes 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.743: Partial capture successful. Please touch the sensor again (6/10) 224s (process:2434): libfprint-device-DEBUG: 16:49:01.743: Device reported enroll progress, reported 6 of 10 have been completed 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.743: [egismoc] ENROLL_STATES entering state 8 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.743: Execute command and get response 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.743: Get check bytes 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.743: [egismoc] CMD_STATES entering state 0 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.743: [egismoc] CMD_STATES entering state 1 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.744: Command receive callback 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.744: [egismoc] CMD_STATES completed successfully 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.744: Task SSM next state callback 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.744: [egismoc] ENROLL_STATES entering state 9 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.744: Execute command and get response 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.744: Get check bytes 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.744: [egismoc] CMD_STATES entering state 0 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.744: [egismoc] CMD_STATES entering state 1 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.745: Command receive callback 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.745: [egismoc] CMD_STATES completed successfully 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.745: Task SSM next state callback 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.745: [egismoc] ENROLL_STATES entering state 10 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.745: Wait for finger on sensor 224s (process:2434): libfprint-device-DEBUG: 16:49:01.745: Device reported finger status change: FP_FINGER_STATUS_NEEDED 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.745: Finger on sensor callback 224s (process:2434): libfprint-device-DEBUG: 16:49:01.745: Device reported finger status change: FP_FINGER_STATUS_PRESENT 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.745: [egismoc] ENROLL_STATES entering state 11 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.745: Execute command and get response 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.746: Get check bytes 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.746: [egismoc] CMD_STATES entering state 0 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.746: [egismoc] CMD_STATES entering state 1 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.746: Command receive callback 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.746: [egismoc] CMD_STATES completed successfully 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.746: Read capture callback 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.746: Response prefix valid: yes 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.746: Response suffix valid: yes 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.746: Partial capture successful. Please touch the sensor again (7/10) 224s (process:2434): libfprint-device-DEBUG: 16:49:01.746: Device reported enroll progress, reported 7 of 10 have been completed 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.746: [egismoc] ENROLL_STATES entering state 8 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.746: Execute command and get response 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.746: Get check bytes 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.746: [egismoc] CMD_STATES entering state 0 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.747: [egismoc] CMD_STATES entering state 1 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.747: Command receive callback 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.747: [egismoc] CMD_STATES completed successfully 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.747: Task SSM next state callback 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.747: [egismoc] ENROLL_STATES entering state 9 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.747: Execute command and get response 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.747: Get check bytes 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.747: [egismoc] CMD_STATES entering state 0 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.748: [egismoc] CMD_STATES entering state 1 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.748: Command receive callback 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.748: [egismoc] CMD_STATES completed successfully 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.748: Task SSM next state callback 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.748: [egismoc] ENROLL_STATES entering state 10 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.748: Wait for finger on sensor 224s (process:2434): libfprint-device-DEBUG: 16:49:01.748: Device reported finger status change: FP_FINGER_STATUS_NEEDED 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.749: Finger on sensor callback 224s (process:2434): libfprint-device-DEBUG: 16:49:01.749: Device reported finger status change: FP_FINGER_STATUS_PRESENT 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.749: [egismoc] ENROLL_STATES entering state 11 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.749: Execute command and get response 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.749: Get check bytes 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.749: [egismoc] CMD_STATES entering state 0 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.749: [egismoc] CMD_STATES entering state 1 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.750: Command receive callback 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.750: [egismoc] CMD_STATES completed successfully 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.750: Read capture callback 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.750: Response prefix valid: yes 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.750: Response suffix valid: yes 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.750: Partial capture successful. Please touch the sensor again (8/10) 224s (process:2434): libfprint-device-DEBUG: 16:49:01.750: Device reported enroll progress, reported 8 of 10 have been completed 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.750: [egismoc] ENROLL_STATES entering state 8 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.750: Execute command and get response 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.750: Get check bytes 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.750: [egismoc] CMD_STATES entering state 0 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.750: [egismoc] CMD_STATES entering state 1 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.751: Command receive callback 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.751: [egismoc] CMD_STATES completed successfully 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.751: Task SSM next state callback 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.751: [egismoc] ENROLL_STATES entering state 9 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.751: Execute command and get response 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.751: Get check bytes 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.751: [egismoc] CMD_STATES entering state 0 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.751: [egismoc] CMD_STATES entering state 1 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.752: Command receive callback 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.752: [egismoc] CMD_STATES completed successfully 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.752: Task SSM next state callback 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.752: [egismoc] ENROLL_STATES entering state 10 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.752: Wait for finger on sensor 224s (process:2434): libfprint-device-DEBUG: 16:49:01.752: Device reported finger status change: FP_FINGER_STATUS_NEEDED 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.752: Finger on sensor callback 224s (process:2434): libfprint-device-DEBUG: 16:49:01.752: Device reported finger status change: FP_FINGER_STATUS_PRESENT 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.752: [egismoc] ENROLL_STATES entering state 11 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.752: Execute command and get response 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.752: Get check bytes 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.752: [egismoc] CMD_STATES entering state 0 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.753: [egismoc] CMD_STATES entering state 1 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.753: Command receive callback 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.753: [egismoc] CMD_STATES completed successfully 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.753: Read capture callback 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.753: Response prefix valid: yes 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.753: Response suffix valid: yes 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.753: Partial capture successful. Please touch the sensor again (9/10) 224s (process:2434): libfprint-device-DEBUG: 16:49:01.753: Device reported enroll progress, reported 9 of 10 have been completed 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.753: [egismoc] ENROLL_STATES entering state 8 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.753: Execute command and get response 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.753: Get check bytes 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.753: [egismoc] CMD_STATES entering state 0 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.754: [egismoc] CMD_STATES entering state 1 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.754: Command receive callback 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.754: [egismoc] CMD_STATES completed successfully 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.754: Task SSM next state callback 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.754: [egismoc] ENROLL_STATES entering state 9 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.754: Execute command and get response 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.754: Get check bytes 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.754: [egismoc] CMD_STATES entering state 0 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.755: [egismoc] CMD_STATES entering state 1 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.755: Command receive callback 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.755: [egismoc] CMD_STATES completed successfully 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.755: Task SSM next state callback 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.755: [egismoc] ENROLL_STATES entering state 10 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.755: Wait for finger on sensor 224s (process:2434): libfprint-device-DEBUG: 16:49:01.755: Device reported finger status change: FP_FINGER_STATUS_NEEDED 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.756: Finger on sensor callback 224s (process:2434): libfprint-device-DEBUG: 16:49:01.756: Device reported finger status change: FP_FINGER_STATUS_PRESENT 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.756: [egismoc] ENROLL_STATES entering state 11 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.756: Execute command and get response 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.756: Get check bytes 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.756: [egismoc] CMD_STATES entering state 0 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.756: [egismoc] CMD_STATES entering state 1 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.756: Command receive callback 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.756: [egismoc] CMD_STATES completed successfully 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.756: Read capture callback 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.757: Response prefix valid: yes 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.757: Response suffix valid: yes 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.757: Partial capture successful. Please touch the sensor again (10/10) 224s (process:2434): libfprint-device-DEBUG: 16:49:01.757: Device reported enroll progress, reported 10 of 10 have been completed 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.757: [egismoc] ENROLL_STATES entering state 12 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.757: Execute command and get response 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.757: Get check bytes 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.757: [egismoc] CMD_STATES entering state 0 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.757: [egismoc] CMD_STATES entering state 1 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.757: Command receive callback 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.757: [egismoc] CMD_STATES completed successfully 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.757: Task SSM next state callback 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.757: [egismoc] ENROLL_STATES entering state 13 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.757: New fingerprint ID: FP1-00000000-7-00000000-nobody 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.758: Execute command and get response 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.758: Get check bytes 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.758: [egismoc] CMD_STATES entering state 0 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.758: [egismoc] CMD_STATES entering state 1 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.758: Command receive callback 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.758: [egismoc] CMD_STATES completed successfully 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.758: Task SSM next state callback 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.758: [egismoc] ENROLL_STATES entering state 14 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.758: Execute command and get response 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.758: Get check bytes 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.758: [egismoc] CMD_STATES entering state 0 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.759: [egismoc] CMD_STATES entering state 1 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.759: Command receive callback 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.759: [egismoc] CMD_STATES completed successfully 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.759: Task SSM next state callback 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.759: [egismoc] ENROLL_STATES entering state 15 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.759: Enrollment was successful! 224s (process:2434): libfprint-device-DEBUG: 16:49:01.759: Device reported enroll completion 224s (process:2434): libfprint-device-DEBUG: 16:49:01.759: Device reported finger status change: FP_FINGER_STATUS_NONE 224s (process:2434): libfprint-device-DEBUG: 16:49:01.759: Print for finger FP_FINGER_RIGHT_INDEX enrolled 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.759: [egismoc] ENROLL_STATES completed successfully 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.759: Task SSM done 224s (process:2434): libfprint-device-DEBUG: 16:49:01.759: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 224s (process:2434): libfprint-device-DEBUG: 16:49:01.759: Updated temperature model after 0.05 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.759: List 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.759: [egismoc] LIST_STATES entering state 0 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.759: Execute command and get response 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.759: Get check bytes 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.759: [egismoc] CMD_STATES entering state 0 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.760: [egismoc] CMD_STATES entering state 1 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.760: Command receive callback 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.760: [egismoc] CMD_STATES completed successfully 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.760: List callback 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.760: Device fingerprint 0: FP1-00000000-2-00000000-nobody 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.760: Device fingerprint 1: FP1-00000000-7-00000000-nobody 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.760: Number of currently enrolled fingerprints on the device is 2 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.760: [egismoc] LIST_STATES entering state 1 224s (process:2434): libfprint-device-DEBUG: 16:49:01.760: Device reported listing completion 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.760: [egismoc] LIST_STATES completed successfully 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.760: Task SSM done 224s (process:2434): libfprint-device-DEBUG: 16:49:01.760: Completing action FPI_DEVICE_ACTION_LIST in idle! 224s (process:2434): libfprint-device-DEBUG: 16:49:01.760: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.761: Delete 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.761: [egismoc] DELETE_STATES entering state 0 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.761: Execute command and get response 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.761: Get check bytes 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.761: [egismoc] CMD_STATES entering state 0 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.761: [egismoc] CMD_STATES entering state 1 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.761: Command receive callback 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.761: [egismoc] CMD_STATES completed successfully 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.761: List callback 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.761: Device fingerprint 0: FP1-00000000-2-00000000-nobody 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.762: Device fingerprint 1: FP1-00000000-7-00000000-nobody 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.762: Number of currently enrolled fingerprints on the device is 2 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.762: [egismoc] DELETE_STATES entering state 1 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.762: Get delete command 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.762: Delete fingerprint FP1-00000000-2-00000000-nobody (FP1-00000000-2-00000000-nobody) 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.762: Execute command and get response 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.762: Get check bytes 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.762: [egismoc] CMD_STATES entering state 0 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.762: [egismoc] CMD_STATES entering state 1 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.762: Command receive callback 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.762: [egismoc] CMD_STATES completed successfully 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.762: Delete callback 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.762: Response prefix valid: yes 224s (process:2434): libfprint-device-DEBUG: 16:49:01.762: Device reported deletion completion 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.762: [egismoc] DELETE_STATES completed successfully 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.762: Task SSM done 224s (process:2434): libfprint-device-DEBUG: 16:49:01.762: Completing action FPI_DEVICE_ACTION_DELETE in idle! 224s (process:2434): libfprint-device-DEBUG: 16:49:01.762: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.762: List 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.762: [egismoc] LIST_STATES entering state 0 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.762: Execute command and get response 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.762: Get check bytes 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.762: [egismoc] CMD_STATES entering state 0 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.763: [egismoc] CMD_STATES entering state 1 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.763: Command receive callback 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.763: [egismoc] CMD_STATES completed successfully 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.763: List callback 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.763: Device fingerprint 0: FP1-00000000-7-00000000-nobody 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.763: Number of currently enrolled fingerprints on the device is 1 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.763: [egismoc] LIST_STATES entering state 1 224s (process:2434): libfprint-device-DEBUG: 16:49:01.763: Device reported listing completion 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.763: [egismoc] LIST_STATES completed successfully 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.763: Task SSM done 224s (process:2434): libfprint-device-DEBUG: 16:49:01.763: Completing action FPI_DEVICE_ACTION_LIST in idle! 224s (process:2434): libfprint-device-DEBUG: 16:49:01.763: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.763: Clear storage 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.763: [egismoc] DELETE_STATES entering state 0 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.763: Execute command and get response 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.763: Get check bytes 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.763: [egismoc] CMD_STATES entering state 0 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.764: [egismoc] CMD_STATES entering state 1 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.764: Command receive callback 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.764: [egismoc] CMD_STATES completed successfully 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.764: List callback 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.764: Device fingerprint 0: FP1-00000000-7-00000000-nobody 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.764: Number of currently enrolled fingerprints on the device is 1 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.764: [egismoc] DELETE_STATES entering state 1 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.764: Get delete command 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.764: Execute command and get response 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.764: Get check bytes 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.764: [egismoc] CMD_STATES entering state 0 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.765: [egismoc] CMD_STATES entering state 1 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.765: Command receive callback 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.765: [egismoc] CMD_STATES completed successfully 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.765: Delete callback 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.765: Response prefix valid: yes 224s (process:2434): libfprint-device-DEBUG: 16:49:01.765: Device reported deletion completion 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.765: [egismoc] DELETE_STATES completed successfully 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.765: Task SSM done 224s (process:2434): libfprint-device-DEBUG: 16:49:01.765: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 224s (process:2434): libfprint-device-DEBUG: 16:49:01.765: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.765: List 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.765: [egismoc] LIST_STATES entering state 0 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.765: Execute command and get response 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.765: Get check bytes 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.765: [egismoc] CMD_STATES entering state 0 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.766: [egismoc] CMD_STATES entering state 1 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.766: Command receive callback 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.766: [egismoc] CMD_STATES completed successfully 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.766: List callback 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.766: Number of currently enrolled fingerprints on the device is 0 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.766: [egismoc] LIST_STATES entering state 1 224s (process:2434): libfprint-device-DEBUG: 16:49:01.766: Device reported listing completion 224s (process:2434): libfprint-SSM-DEBUG: 16:49:01.766: [egismoc] LIST_STATES completed successfully 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.766: Task SSM done 224s (process:2434): libfprint-device-DEBUG: 16:49:01.766: Completing action FPI_DEVICE_ACTION_LIST in idle! 224s (process:2434): libfprint-device-DEBUG: 16:49:01.766: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.766: Closing device 224s (process:2434): libfprint-egismoc-DEBUG: 16:49:01.766: Cancel 224s (process:2434): libfprint-device-DEBUG: 16:49:01.767: Device reported close completion 224s (process:2434): libfprint-device-DEBUG: 16:49:01.767: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 224s (process:2434): libfprint-device-DEBUG: 16:49:01.767: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 224s listing - device should have prints 224s clear device storage 224s clear done 224s listing - device should be empty 224s enrolling 224s finger status: 224s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xe8fdb34341c0 (FpiDeviceEgisMoc at 0xf2e56b0)>, 1, , None, None) 224s finger status: 224s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xe8fdb34341c0 (FpiDeviceEgisMoc at 0xf2e56b0)>, 2, , None, None) 224s finger status: 224s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xe8fdb34341c0 (FpiDeviceEgisMoc at 0xf2e56b0)>, 2, None, None, GLib.Error('Your device is having trouble recognizing you. Make sure your sensor is clean.', 'fp - device - retry - quark', 3)) 224s finger status: 224s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xe8fdb34341c0 (FpiDeviceEgisMoc at 0xf2e56b0)>, 3, , None, None) 224s finger status: 224s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xe8fdb34341c0 (FpiDeviceEgisMoc at 0xf2e56b0)>, 4, , None, None) 224s finger status: 224s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xe8fdb34341c0 (FpiDeviceEgisMoc at 0xf2e56b0)>, 5, , None, None) 224s finger status: 224s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xe8fdb34341c0 (FpiDeviceEgisMoc at 0xf2e56b0)>, 6, , None, None) 224s finger status: 224s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xe8fdb34341c0 (FpiDeviceEgisMoc at 0xf2e56b0)>, 7, , None, None) 224s finger status: 224s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xe8fdb34341c0 (FpiDeviceEgisMoc at 0xf2e56b0)>, 8, , None, None) 224s finger status: 224s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xe8fdb34341c0 (FpiDeviceEgisMoc at 0xf2e56b0)>, 9, , None, None) 224s finger status: 224s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xe8fdb34341c0 (FpiDeviceEgisMoc at 0xf2e56b0)>, 10, , None, None) 224s enroll done 224s listing - device should have 1 print 224s verifying 224s verify done 224s async identifying 224s indentification_done: 224s try to enroll duplicate 224s duplicate enroll attempt done 224s listing - device should still only have 1 print 224s enroll new finger 224s finger status: 224s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xe8fdb34341c0 (FpiDeviceEgisMoc at 0xf2e56b0)>, 1, , None, None) 224s finger status: 224s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xe8fdb34341c0 (FpiDeviceEgisMoc at 0xf2e56b0)>, 2, , None, None) 224s finger status: 224s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xe8fdb34341c0 (FpiDeviceEgisMoc at 0xf2e56b0)>, 2, None, None, GLib.Error('The finger was not centered properly, please try again.', 'fp - device - retry - quark', 2)) 224s finger status: 224s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xe8fdb34341c0 (FpiDeviceEgisMoc at 0xf2e56b0)>, 2, None, None, GLib.Error('The finger was not centered properly, please try again.', 'fp - device - retry - quark', 2)) 224s finger status: 224s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xe8fdb34341c0 (FpiDeviceEgisMoc at 0xf2e56b0)>, 3, , None, None) 224s finger status: 224s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xe8fdb34341c0 (FpiDeviceEgisMoc at 0xf2e56b0)>, 3, None, None, GLib.Error('The finger was not centered properly, please try again.', 'fp - device - retry - quark', 2)) 224s finger status: 224s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xe8fdb34341c0 (FpiDeviceEgisMoc at 0xf2e56b0)>, 4, , None, None) 224s finger status: 224s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xe8fdb34341c0 (FpiDeviceEgisMoc at 0xf2e56b0)>, 5, , None, None) 224s finger status: 224s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xe8fdb34341c0 (FpiDeviceEgisMoc at 0xf2e56b0)>, 6, , None, None) 224s finger status: 224s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xe8fdb34341c0 (FpiDeviceEgisMoc at 0xf2e56b0)>, 7, , None, None) 224s finger status: 224s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xe8fdb34341c0 (FpiDeviceEgisMoc at 0xf2e56b0)>, 8, , None, None) 224s finger status: 224s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xe8fdb34341c0 (FpiDeviceEgisMoc at 0xf2e56b0)>, 9, , None, None) 224s finger status: 224s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xe8fdb34341c0 (FpiDeviceEgisMoc at 0xf2e56b0)>, 10, , None, None) 224s enroll new finger done 224s listing - device should have 2 prints 224s deleting first print 224s delete done 224s listing - device should only have second print 224s clear device storage 224s clear done 224s listing - device should be empty 224s ** (umockdev-run:2430): DEBUG: 16:49:01.779: umockdev.vala:150: Removing test bed /tmp/umockdev.B61BK2 224s (umockdev-run:2430): GLib-DEBUG: 16:49:01.783: unsetenv() is not thread-safe and should not be used after threads are created 224s PASS: libfprint-2/driver-egismoc-05a1.test 224s Running test: libfprint-2/driver-vfs5011.test 224s ** (umockdev-run:2442): DEBUG: 16:49:01.955: umockdev.vala:123: Created udev test bed /tmp/umockdev.UWQYJ2 224s ** (umockdev-run:2442): DEBUG: 16:49:01.955: umockdev.vala:1297: parsing device description for /devices/pci0000:00/0000:00:14.0/usb2/2-6 224s ** (umockdev-run:2442): DEBUG: 16:49:01.956: umockdev.vala:1366: creating device /devices/pci0000:00/0000:00:14.0/usb2/2-6 (subsystem usb) 224s ** (umockdev-run:2442): DEBUG: 16:49:01.958: umockdev.vala:1411: create_node_for_device: creating file device /tmp/umockdev.UWQYJ2/dev/bus/usb/002/017 224s ** (umockdev-run:2442): DEBUG: 16:49:01.959: umockdev.vala:1297: parsing device description for /devices/pci0000:00/0000:00:14.0/usb2 224s ** (umockdev-run:2442): DEBUG: 16:49:01.960: umockdev.vala:1366: creating device /devices/pci0000:00/0000:00:14.0/usb2 (subsystem usb) 224s ** (umockdev-run:2442): DEBUG: 16:49:01.961: umockdev.vala:1411: create_node_for_device: creating file device /tmp/umockdev.UWQYJ2/dev/bus/usb/002/001 224s ** (umockdev-run:2442): DEBUG: 16:49:01.962: umockdev.vala:1297: parsing device description for /devices/pci0000:00/0000:00:14.0 224s ** (umockdev-run:2442): DEBUG: 16:49:01.962: umockdev.vala:1366: creating device /devices/pci0000:00/0000:00:14.0 (subsystem pci) 224s (umockdev-run:2442): GLib-GIO-DEBUG: 16:49:01.963: _g_io_module_get_default: Found default implementation local (GLocalVfs) for ?gio-vfs? 225s (process:2446): libfprint-context-DEBUG: 16:49:02.025: Initializing FpContext (libfprint version 1.94.7+tod1) 225s (process:2446): libfprint-tod-DEBUG: 16:49:02.025: Impossible to load the shared drivers dir Error opening directory “/usr/lib/aarch64-linux-gnu/libfprint-2/tod-1”: No such file or directory 225s (process:2446): libfprint-context-DEBUG: 16:49:02.027: No driver found for USB device 1D6B:0002 225s (process:2446): libfprint-device-DEBUG: 16:49:02.027: Device reported probe completion 225s (process:2446): libfprint-device-DEBUG: 16:49:02.027: Completing action FPI_DEVICE_ACTION_PROBE in idle! 225s (process:2446): libfprint-device-DEBUG: 16:49:02.027: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 225s (process:2446): libfprint-SSM-DEBUG: 16:49:02.028: [vfs5011] DEV_OPEN_NUM_STATES entering state 0 225s (process:2446): libfprint-SSM-DEBUG: 16:49:02.028: [vfs5011] DEVICE OPEN entering state 0 225s (process:2446): libfprint-vfs5011-DEBUG: 16:49:02.028: Sending vfs5011_cmd_01 225s (process:2446): libfprint-SSM-DEBUG: 16:49:02.029: [vfs5011] DEVICE OPEN entering state 1 225s (process:2446): libfprint-vfs5011-DEBUG: 16:49:02.029: Receiving 64 bytes 225s (process:2446): libfprint-vfs5011-DEBUG: 16:49:02.029: Got 38 bytes out of 64 225s (process:2446): libfprint-SSM-DEBUG: 16:49:02.029: [vfs5011] DEVICE OPEN entering state 2 225s (process:2446): libfprint-vfs5011-DEBUG: 16:49:02.029: Sending vfs5011_cmd_19 225s (process:2446): libfprint-SSM-DEBUG: 16:49:02.030: [vfs5011] DEVICE OPEN entering state 3 225s (process:2446): libfprint-vfs5011-DEBUG: 16:49:02.030: Receiving 64 bytes 225s (process:2446): libfprint-vfs5011-DEBUG: 16:49:02.030: Got 64 bytes out of 64 225s (process:2446): libfprint-SSM-DEBUG: 16:49:02.030: [vfs5011] DEVICE OPEN entering state 4 225s (process:2446): libfprint-vfs5011-DEBUG: 16:49:02.030: Receiving 64 bytes 225s (process:2446): libfprint-vfs5011-DEBUG: 16:49:02.031: Got 4 bytes out of 64 225s (process:2446): libfprint-SSM-DEBUG: 16:49:02.031: [vfs5011] DEVICE OPEN entering state 5 225s (process:2446): libfprint-vfs5011-DEBUG: 16:49:02.031: Sending vfs5011_init_00 225s (process:2446): libfprint-SSM-DEBUG: 16:49:02.031: [vfs5011] DEVICE OPEN entering state 6 225s (process:2446): libfprint-vfs5011-DEBUG: 16:49:02.031: Receiving 64 bytes 225s (process:2446): libfprint-vfs5011-DEBUG: 16:49:02.032: Got 6 bytes out of 64 225s (process:2446): libfprint-SSM-DEBUG: 16:49:02.032: [vfs5011] DEVICE OPEN entering state 7 225s (process:2446): libfprint-vfs5011-DEBUG: 16:49:02.032: Sending vfs5011_init_01 225s (process:2446): libfprint-SSM-DEBUG: 16:49:02.032: [vfs5011] DEVICE OPEN entering state 8 225s (process:2446): libfprint-vfs5011-DEBUG: 16:49:02.032: Receiving 64 bytes 225s (process:2446): libfprint-vfs5011-DEBUG: 16:49:02.033: Got 7 bytes out of 64 225s (process:2446): libfprint-SSM-DEBUG: 16:49:02.033: [vfs5011] DEVICE OPEN entering state 9 225s (process:2446): libfprint-vfs5011-DEBUG: 16:49:02.033: Sending vfs5011_init_02 225s (process:2446): libfprint-SSM-DEBUG: 16:49:02.033: [vfs5011] DEVICE OPEN entering state 10 225s (process:2446): libfprint-vfs5011-DEBUG: 16:49:02.033: Receiving 64 bytes 225s (process:2446): libfprint-SSM-DEBUG: 16:49:02.034: [vfs5011] DEVICE OPEN entering state 11 225s (process:2446): libfprint-vfs5011-DEBUG: 16:49:02.034: Sending vfs5011_cmd_01 225s (process:2446): libfprint-SSM-DEBUG: 16:49:02.034: [vfs5011] DEVICE OPEN entering state 12 225s (process:2446): libfprint-vfs5011-DEBUG: 16:49:02.034: Receiving 64 bytes 225s (process:2446): libfprint-vfs5011-DEBUG: 16:49:02.035: Got 38 bytes out of 64 225s (process:2446): libfprint-SSM-DEBUG: 16:49:02.035: [vfs5011] DEVICE OPEN entering state 13 225s (process:2446): libfprint-vfs5011-DEBUG: 16:49:02.035: Sending vfs5011_cmd_1A 225s (process:2446): libfprint-SSM-DEBUG: 16:49:02.035: [vfs5011] DEVICE OPEN entering state 14 225s (process:2446): libfprint-vfs5011-DEBUG: 16:49:02.035: Receiving 64 bytes 225s (process:2446): libfprint-SSM-DEBUG: 16:49:02.036: [vfs5011] DEVICE OPEN entering state 15 225s (process:2446): libfprint-vfs5011-DEBUG: 16:49:02.036: Sending vfs5011_init_03 225s (process:2446): libfprint-SSM-DEBUG: 16:49:02.036: [vfs5011] DEVICE OPEN entering state 16 225s (process:2446): libfprint-vfs5011-DEBUG: 16:49:02.036: Receiving 64 bytes 225s (process:2446): libfprint-SSM-DEBUG: 16:49:02.036: [vfs5011] DEVICE OPEN entering state 17 225s (process:2446): libfprint-vfs5011-DEBUG: 16:49:02.037: Sending vfs5011_init_04 225s (process:2446): libfprint-SSM-DEBUG: 16:49:02.037: [vfs5011] DEVICE OPEN entering state 18 225s (process:2446): libfprint-vfs5011-DEBUG: 16:49:02.037: Receiving 64 bytes 225s (process:2446): libfprint-SSM-DEBUG: 16:49:02.037: [vfs5011] DEVICE OPEN entering state 19 225s (process:2446): libfprint-vfs5011-DEBUG: 16:49:02.037: Receiving 256 bytes 225s (process:2446): libfprint-vfs5011-DEBUG: 16:49:02.038: Got 256 bytes out of 256 225s (process:2446): libfprint-SSM-DEBUG: 16:49:02.038: [vfs5011] DEVICE OPEN entering state 20 225s (process:2446): libfprint-vfs5011-DEBUG: 16:49:02.038: Receiving 64 bytes 225s (process:2446): libfprint-vfs5011-DEBUG: 16:49:02.038: Got 32 bytes out of 64 225s (process:2446): libfprint-SSM-DEBUG: 16:49:02.038: [vfs5011] DEVICE OPEN entering state 21 225s (process:2446): libfprint-vfs5011-DEBUG: 16:49:02.038: Sending vfs5011_cmd_1A 225s (process:2446): libfprint-SSM-DEBUG: 16:49:02.039: [vfs5011] DEVICE OPEN entering state 22 225s (process:2446): libfprint-vfs5011-DEBUG: 16:49:02.039: Receiving 64 bytes 225s (process:2446): libfprint-SSM-DEBUG: 16:49:02.039: [vfs5011] DEVICE OPEN entering state 23 225s (process:2446): libfprint-vfs5011-DEBUG: 16:49:02.039: Sending vfs5011_init_05 225s (process:2446): libfprint-SSM-DEBUG: 16:49:02.040: [vfs5011] DEVICE OPEN entering state 24 225s (process:2446): libfprint-vfs5011-DEBUG: 16:49:02.040: Receiving 64 bytes 225s (process:2446): libfprint-SSM-DEBUG: 16:49:02.040: [vfs5011] DEVICE OPEN entering state 25 225s (process:2446): libfprint-vfs5011-DEBUG: 16:49:02.040: Sending vfs5011_cmd_01 225s (process:2446): libfprint-SSM-DEBUG: 16:49:02.041: [vfs5011] DEVICE OPEN entering state 26 225s (process:2446): libfprint-vfs5011-DEBUG: 16:49:02.041: Receiving 64 bytes 225s (process:2446): libfprint-vfs5011-DEBUG: 16:49:02.041: Got 38 bytes out of 64 225s (process:2446): libfprint-SSM-DEBUG: 16:49:02.041: [vfs5011] DEVICE OPEN entering state 27 225s (process:2446): libfprint-vfs5011-DEBUG: 16:49:02.041: Sending vfs5011_init_06 225s (process:2446): libfprint-SSM-DEBUG: 16:49:02.042: [vfs5011] DEVICE OPEN entering state 28 225s (process:2446): libfprint-vfs5011-DEBUG: 16:49:02.042: Receiving 64 bytes 225s (process:2446): libfprint-SSM-DEBUG: 16:49:02.042: [vfs5011] DEVICE OPEN entering state 29 225s (process:2446): libfprint-vfs5011-DEBUG: 16:49:02.042: Receiving 17216 bytes 225s (process:2446): libfprint-vfs5011-DEBUG: 16:49:02.043: Got 17216 bytes out of 17216 225s (process:2446): libfprint-SSM-DEBUG: 16:49:02.043: [vfs5011] DEVICE OPEN entering state 30 225s (process:2446): libfprint-vfs5011-DEBUG: 16:49:02.043: Receiving 32 bytes 225s (process:2446): libfprint-vfs5011-DEBUG: 16:49:02.043: Got 32 bytes out of 32 225s (process:2446): libfprint-SSM-DEBUG: 16:49:02.043: [vfs5011] DEVICE OPEN entering state 31 225s (process:2446): libfprint-vfs5011-DEBUG: 16:49:02.043: Sending vfs5011_init_07 225s (process:2446): libfprint-SSM-DEBUG: 16:49:02.044: [vfs5011] DEVICE OPEN entering state 32 225s (process:2446): libfprint-vfs5011-DEBUG: 16:49:02.044: Receiving 64 bytes 225s (process:2446): libfprint-SSM-DEBUG: 16:49:02.044: [vfs5011] DEVICE OPEN entering state 33 225s (process:2446): libfprint-vfs5011-DEBUG: 16:49:02.044: Receiving 45056 bytes 225s (process:2446): libfprint-vfs5011-DEBUG: 16:49:02.045: Got 45056 bytes out of 45056 225s (process:2446): libfprint-SSM-DEBUG: 16:49:02.045: [vfs5011] DEVICE OPEN entering state 34 225s (process:2446): libfprint-vfs5011-DEBUG: 16:49:02.045: Sending vfs5011_init_08 225s (process:2446): libfprint-SSM-DEBUG: 16:49:02.045: [vfs5011] DEVICE OPEN entering state 35 225s (process:2446): libfprint-vfs5011-DEBUG: 16:49:02.045: Receiving 64 bytes 225s (process:2446): libfprint-SSM-DEBUG: 16:49:02.046: [vfs5011] DEVICE OPEN entering state 36 225s (process:2446): libfprint-vfs5011-DEBUG: 16:49:02.046: Receiving 16896 bytes 225s (process:2446): libfprint-vfs5011-DEBUG: 16:49:02.046: Got 16896 bytes out of 16896 225s (process:2446): libfprint-SSM-DEBUG: 16:49:02.046: [vfs5011] DEVICE OPEN entering state 37 225s (process:2446): libfprint-vfs5011-DEBUG: 16:49:02.046: Sending vfs5011_init_09 225s (process:2446): libfprint-SSM-DEBUG: 16:49:02.047: [vfs5011] DEVICE OPEN entering state 38 225s (process:2446): libfprint-vfs5011-DEBUG: 16:49:02.047: Receiving 64 bytes 225s (process:2446): libfprint-SSM-DEBUG: 16:49:02.047: [vfs5011] DEVICE OPEN entering state 39 225s (process:2446): libfprint-vfs5011-DEBUG: 16:49:02.047: Receiving 4928 bytes 225s (process:2446): libfprint-vfs5011-DEBUG: 16:49:02.048: Got 4928 bytes out of 4928 225s (process:2446): libfprint-SSM-DEBUG: 16:49:02.048: [vfs5011] DEVICE OPEN entering state 40 225s (process:2446): libfprint-vfs5011-DEBUG: 16:49:02.048: Sending vfs5011_init_10 225s (process:2446): libfprint-SSM-DEBUG: 16:49:02.048: [vfs5011] DEVICE OPEN entering state 41 225s (process:2446): libfprint-vfs5011-DEBUG: 16:49:02.048: Receiving 64 bytes 225s (process:2446): libfprint-SSM-DEBUG: 16:49:02.049: [vfs5011] DEVICE OPEN entering state 42 225s (process:2446): libfprint-vfs5011-DEBUG: 16:49:02.049: Receiving 5632 bytes 225s (process:2446): libfprint-vfs5011-DEBUG: 16:49:02.049: Got 5632 bytes out of 5632 225s (process:2446): libfprint-SSM-DEBUG: 16:49:02.049: [vfs5011] DEVICE OPEN entering state 43 225s (process:2446): libfprint-vfs5011-DEBUG: 16:49:02.049: Sending vfs5011_init_11 225s (process:2446): libfprint-SSM-DEBUG: 16:49:02.050: [vfs5011] DEVICE OPEN entering state 44 225s (process:2446): libfprint-vfs5011-DEBUG: 16:49:02.050: Receiving 64 bytes 225s (process:2446): libfprint-SSM-DEBUG: 16:49:02.050: [vfs5011] DEVICE OPEN entering state 45 225s (process:2446): libfprint-vfs5011-DEBUG: 16:49:02.050: Receiving 5632 bytes 225s (process:2446): libfprint-vfs5011-DEBUG: 16:49:02.051: Got 5632 bytes out of 5632 225s (process:2446): libfprint-SSM-DEBUG: 16:49:02.051: [vfs5011] DEVICE OPEN entering state 46 225s (process:2446): libfprint-vfs5011-DEBUG: 16:49:02.051: Sending vfs5011_init_12 225s (process:2446): libfprint-SSM-DEBUG: 16:49:02.051: [vfs5011] DEVICE OPEN entering state 47 225s (process:2446): libfprint-vfs5011-DEBUG: 16:49:02.051: Receiving 64 bytes 225s (process:2446): libfprint-SSM-DEBUG: 16:49:02.052: [vfs5011] DEVICE OPEN entering state 48 225s (process:2446): libfprint-vfs5011-DEBUG: 16:49:02.052: Receiving 3328 bytes 225s (process:2446): libfprint-vfs5011-DEBUG: 16:49:02.052: Got 3328 bytes out of 3328 225s (process:2446): libfprint-SSM-DEBUG: 16:49:02.052: [vfs5011] DEVICE OPEN entering state 49 225s (process:2446): libfprint-vfs5011-DEBUG: 16:49:02.052: Receiving 64 bytes 225s (process:2446): libfprint-vfs5011-DEBUG: 16:49:02.053: Got 32 bytes out of 64 225s (process:2446): libfprint-SSM-DEBUG: 16:49:02.053: [vfs5011] DEVICE OPEN entering state 50 225s (process:2446): libfprint-vfs5011-DEBUG: 16:49:02.053: Sending vfs5011_init_13 225s (process:2446): libfprint-SSM-DEBUG: 16:49:02.053: [vfs5011] DEVICE OPEN entering state 51 225s (process:2446): libfprint-vfs5011-DEBUG: 16:49:02.053: Receiving 64 bytes 225s (process:2446): libfprint-SSM-DEBUG: 16:49:02.054: [vfs5011] DEVICE OPEN entering state 52 225s (process:2446): libfprint-vfs5011-DEBUG: 16:49:02.054: Sending vfs5011_cmd_1A 225s (process:2446): libfprint-SSM-DEBUG: 16:49:02.054: [vfs5011] DEVICE OPEN entering state 53 225s (process:2446): libfprint-vfs5011-DEBUG: 16:49:02.054: Receiving 64 bytes 225s (process:2446): libfprint-SSM-DEBUG: 16:49:02.055: [vfs5011] DEVICE OPEN entering state 54 225s (process:2446): libfprint-vfs5011-DEBUG: 16:49:02.055: Sending vfs5011_init_03 225s (process:2446): libfprint-SSM-DEBUG: 16:49:02.055: [vfs5011] DEVICE OPEN entering state 55 225s (process:2446): libfprint-vfs5011-DEBUG: 16:49:02.055: Receiving 64 bytes 225s (process:2446): libfprint-SSM-DEBUG: 16:49:02.056: [vfs5011] DEVICE OPEN entering state 56 225s (process:2446): libfprint-vfs5011-DEBUG: 16:49:02.056: Sending vfs5011_init_14 225s (process:2446): libfprint-SSM-DEBUG: 16:49:02.056: [vfs5011] DEVICE OPEN entering state 57 225s (process:2446): libfprint-vfs5011-DEBUG: 16:49:02.056: Receiving 64 bytes 225s (process:2446): libfprint-SSM-DEBUG: 16:49:02.057: [vfs5011] DEVICE OPEN entering state 58 225s (process:2446): libfprint-vfs5011-DEBUG: 16:49:02.057: Receiving 4800 bytes 225s (process:2446): libfprint-vfs5011-DEBUG: 16:49:02.057: Got 4800 bytes out of 4800 225s (process:2446): libfprint-SSM-DEBUG: 16:49:02.057: [vfs5011] DEVICE OPEN entering state 59 225s (process:2446): libfprint-vfs5011-DEBUG: 16:49:02.057: Sending vfs5011_cmd_1A 225s (process:2446): libfprint-SSM-DEBUG: 16:49:02.058: [vfs5011] DEVICE OPEN entering state 60 225s (process:2446): libfprint-vfs5011-DEBUG: 16:49:02.058: Receiving 64 bytes 225s (process:2446): libfprint-SSM-DEBUG: 16:49:02.058: [vfs5011] DEVICE OPEN entering state 61 225s (process:2446): libfprint-vfs5011-DEBUG: 16:49:02.058: Sending vfs5011_init_02 225s (process:2446): libfprint-SSM-DEBUG: 16:49:02.059: [vfs5011] DEVICE OPEN entering state 62 225s (process:2446): libfprint-vfs5011-DEBUG: 16:49:02.059: Receiving 64 bytes 225s (process:2446): libfprint-SSM-DEBUG: 16:49:02.059: [vfs5011] DEVICE OPEN entering state 63 225s (process:2446): libfprint-vfs5011-DEBUG: 16:49:02.059: Sending vfs5011_cmd_27 225s (process:2446): libfprint-SSM-DEBUG: 16:49:02.060: [vfs5011] DEVICE OPEN entering state 64 225s (process:2446): libfprint-vfs5011-DEBUG: 16:49:02.060: Receiving 64 bytes 225s (process:2446): libfprint-vfs5011-DEBUG: 16:49:02.060: Got 22 bytes out of 64 225s (process:2446): libfprint-SSM-DEBUG: 16:49:02.060: [vfs5011] DEVICE OPEN entering state 65 225s (process:2446): libfprint-vfs5011-DEBUG: 16:49:02.060: Sending vfs5011_cmd_1A 225s (process:2446): libfprint-SSM-DEBUG: 16:49:02.061: [vfs5011] DEVICE OPEN entering state 66 225s (process:2446): libfprint-vfs5011-DEBUG: 16:49:02.061: Receiving 64 bytes 225s (process:2446): libfprint-SSM-DEBUG: 16:49:02.061: [vfs5011] DEVICE OPEN entering state 67 225s (process:2446): libfprint-vfs5011-DEBUG: 16:49:02.061: Sending vfs5011_init_15 225s (process:2446): libfprint-SSM-DEBUG: 16:49:02.062: [vfs5011] DEVICE OPEN entering state 68 225s (process:2446): libfprint-vfs5011-DEBUG: 16:49:02.062: Receiving 64 bytes 225s (process:2446): libfprint-SSM-DEBUG: 16:49:02.062: [vfs5011] DEVICE OPEN entering state 69 225s (process:2446): libfprint-vfs5011-DEBUG: 16:49:02.062: Sending vfs5011_init_16 225s (process:2446): libfprint-SSM-DEBUG: 16:49:02.063: [vfs5011] DEVICE OPEN entering state 70 225s (process:2446): libfprint-vfs5011-DEBUG: 16:49:02.063: Receiving 2368 bytes 225s (process:2446): libfprint-vfs5011-DEBUG: 16:49:02.063: Got 2368 bytes out of 2368 225s (process:2446): libfprint-SSM-DEBUG: 16:49:02.063: [vfs5011] DEVICE OPEN entering state 71 225s (process:2446): libfprint-vfs5011-DEBUG: 16:49:02.063: Receiving 64 bytes 225s (process:2446): libfprint-vfs5011-DEBUG: 16:49:02.064: Got 36 bytes out of 64 225s (process:2446): libfprint-SSM-DEBUG: 16:49:02.064: [vfs5011] DEVICE OPEN entering state 72 225s (process:2446): libfprint-vfs5011-DEBUG: 16:49:02.064: Receiving 4800 bytes 225s (process:2446): libfprint-vfs5011-DEBUG: 16:49:02.064: Got 4800 bytes out of 4800 225s (process:2446): libfprint-SSM-DEBUG: 16:49:02.064: [vfs5011] DEVICE OPEN entering state 73 225s (process:2446): libfprint-vfs5011-DEBUG: 16:49:02.064: Sending vfs5011_init_17 225s (process:2446): libfprint-SSM-DEBUG: 16:49:02.065: [vfs5011] DEVICE OPEN entering state 74 225s (process:2446): libfprint-vfs5011-DEBUG: 16:49:02.065: Receiving 64 bytes 225s (process:2446): libfprint-SSM-DEBUG: 16:49:02.065: [vfs5011] DEVICE OPEN entering state 75 225s (process:2446): libfprint-vfs5011-DEBUG: 16:49:02.065: Sending vfs5011_init_18 225s (process:2446): libfprint-SSM-DEBUG: 16:49:02.066: [vfs5011] DEVICE OPEN entering state 76 225s (process:2446): libfprint-vfs5011-DEBUG: 16:49:02.066: Receiving 64 bytes 225s (process:2446): libfprint-SSM-DEBUG: 16:49:02.066: [vfs5011] DEVICE OPEN completed successfully 225s (process:2446): libfprint-SSM-DEBUG: 16:49:02.066: [vfs5011] DEV_OPEN_NUM_STATES completed successfully 225s (process:2446): libfprint-image_device-DEBUG: 16:49:02.066: Image device open completed 225s (process:2446): libfprint-device-DEBUG: 16:49:02.066: Device reported open completion 225s (process:2446): libfprint-device-DEBUG: 16:49:02.066: Completing action FPI_DEVICE_ACTION_OPEN in idle! 225s (process:2446): libfprint-device-DEBUG: 16:49:02.066: Updated temperature model after 0.04 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 225s (process:2446): libfprint-device-DEBUG: 16:49:02.066: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 225s (process:2446): libfprint-image_device-DEBUG: 16:49:02.066: Activating image device 225s (process:2446): libfprint-image_device-DEBUG: 16:49:02.067: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING 225s (process:2446): libfprint-vfs5011-DEBUG: 16:49:02.067: device initialized 225s (process:2446): libfprint-vfs5011-DEBUG: 16:49:02.067: creating ssm 225s (process:2446): libfprint-vfs5011-DEBUG: 16:49:02.067: starting ssm 225s (process:2446): libfprint-SSM-DEBUG: 16:49:02.067: [vfs5011] DEV_ACTIVATE_NUM_STATES entering state 0 225s (process:2446): libfprint-vfs5011-DEBUG: 16:49:02.067: main_loop: state 0 225s (process:2446): libfprint-SSM-DEBUG: 16:49:02.067: [vfs5011] ACTIVATE REQUEST entering state 0 225s (process:2446): libfprint-vfs5011-DEBUG: 16:49:02.067: Sending vfs5011_cmd_04 225s (process:2446): libfprint-vfs5011-DEBUG: 16:49:02.072: ssm done, getting out 225s (process:2446): libfprint-SSM-DEBUG: 16:49:02.072: [vfs5011] ACTIVATE REQUEST entering state 1 225s (process:2446): libfprint-vfs5011-DEBUG: 16:49:02.072: Receiving 64 bytes 225s (process:2446): libfprint-vfs5011-DEBUG: 16:49:02.073: Got 64 bytes out of 64 225s (process:2446): libfprint-SSM-DEBUG: 16:49:02.073: [vfs5011] ACTIVATE REQUEST entering state 2 225s (process:2446): libfprint-vfs5011-DEBUG: 16:49:02.073: Receiving 84032 bytes 225s (process:2446): libfprint-vfs5011-DEBUG: 16:49:02.074: Got 176 bytes out of 84032 225s (process:2446): libfprint-SSM-DEBUG: 16:49:02.074: [vfs5011] ACTIVATE REQUEST entering state 3 225s (process:2446): libfprint-vfs5011-DEBUG: 16:49:02.074: Receiving 64 bytes 225s (process:2446): libfprint-SSM-DEBUG: 16:49:02.074: [vfs5011] ACTIVATE REQUEST entering state 4 225s (process:2446): libfprint-vfs5011-DEBUG: 16:49:02.074: Sending vfs5011_cmd_1A 225s (process:2446): libfprint-SSM-DEBUG: 16:49:02.075: [vfs5011] ACTIVATE REQUEST entering state 5 225s (process:2446): libfprint-vfs5011-DEBUG: 16:49:02.075: Receiving 64 bytes 225s (process:2446): libfprint-SSM-DEBUG: 16:49:02.075: [vfs5011] ACTIVATE REQUEST entering state 6 225s (process:2446): libfprint-vfs5011-DEBUG: 16:49:02.075: Sending vfs5011_prepare_00 225s (process:2446): libfprint-SSM-DEBUG: 16:49:02.076: [vfs5011] ACTIVATE REQUEST entering state 7 225s (process:2446): libfprint-vfs5011-DEBUG: 16:49:02.076: Receiving 64 bytes 225s (process:2446): libfprint-SSM-DEBUG: 16:49:02.076: [vfs5011] ACTIVATE REQUEST entering state 8 225s (process:2446): libfprint-vfs5011-DEBUG: 16:49:02.076: Sending vfs5011_cmd_1A 225s (process:2446): libfprint-SSM-DEBUG: 16:49:02.077: [vfs5011] ACTIVATE REQUEST entering state 9 225s (process:2446): libfprint-vfs5011-DEBUG: 16:49:02.077: Receiving 64 bytes 225s (process:2446): libfprint-SSM-DEBUG: 16:49:02.077: [vfs5011] ACTIVATE REQUEST entering state 10 225s (process:2446): libfprint-vfs5011-DEBUG: 16:49:02.077: Sending vfs5011_prepare_01 225s (process:2446): libfprint-SSM-DEBUG: 16:49:02.078: [vfs5011] ACTIVATE REQUEST entering state 11 225s (process:2446): libfprint-vfs5011-DEBUG: 16:49:02.078: Receiving 64 bytes 225s (process:2446): libfprint-SSM-DEBUG: 16:49:02.078: [vfs5011] ACTIVATE REQUEST entering state 12 225s (process:2446): libfprint-vfs5011-DEBUG: 16:49:02.078: Sending vfs5011_prepare_02 225s (process:2446): libfprint-SSM-DEBUG: 16:49:02.079: [vfs5011] ACTIVATE REQUEST entering state 13 225s (process:2446): libfprint-vfs5011-DEBUG: 16:49:02.079: Receiving 2368 bytes 225s (process:2446): libfprint-vfs5011-DEBUG: 16:49:02.079: Got 2368 bytes out of 2368 225s (process:2446): libfprint-SSM-DEBUG: 16:49:02.079: [vfs5011] ACTIVATE REQUEST entering state 14 225s (process:2446): libfprint-vfs5011-DEBUG: 16:49:02.079: Receiving 64 bytes 225s (process:2446): libfprint-vfs5011-DEBUG: 16:49:02.080: Got 36 bytes out of 64 225s (process:2446): libfprint-SSM-DEBUG: 16:49:02.080: [vfs5011] ACTIVATE REQUEST entering state 15 225s (process:2446): libfprint-vfs5011-DEBUG: 16:49:02.080: Receiving 4800 bytes 225s (process:2446): libfprint-vfs5011-DEBUG: 16:49:02.080: Got 4800 bytes out of 4800 225s (process:2446): libfprint-SSM-DEBUG: 16:49:02.080: [vfs5011] ACTIVATE REQUEST entering state 16 225s (process:2446): libfprint-vfs5011-DEBUG: 16:49:02.080: Sending vfs5011_prepare_03 225s (process:2446): libfprint-SSM-DEBUG: 16:49:02.081: [vfs5011] ACTIVATE REQUEST entering state 17 225s (process:2446): libfprint-vfs5011-DEBUG: 16:49:02.081: Receiving 64 bytes 225s (process:2446): libfprint-SSM-DEBUG: 16:49:02.081: [vfs5011] ACTIVATE REQUEST entering state 18 225s (process:2446): libfprint-vfs5011-DEBUG: 16:49:02.081: Sending vfs5011_prepare_04 225s (process:2446): libfprint-SSM-DEBUG: 16:49:02.082: [vfs5011] ACTIVATE REQUEST entering state 19 225s (process:2446): libfprint-vfs5011-DEBUG: 16:49:02.082: Receiving 2368 bytes 225s (process:2446): libfprint-SSM-DEBUG: 16:49:02.082: [vfs5011] ACTIVATE REQUEST completed successfully 225s (process:2446): libfprint-SSM-DEBUG: 16:49:02.082: [vfs5011] DEV_ACTIVATE_NUM_STATES entering state 1 225s (process:2446): libfprint-vfs5011-DEBUG: 16:49:02.082: main_loop: state 1 225s (process:2446): libfprint-vfs5011-DEBUG: 16:49:02.082: capture_init 225s (process:2446): libfprint-image_device-DEBUG: 16:49:02.082: Image device activation completed 225s (process:2446): libfprint-image_device-DEBUG: 16:49:02.082: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE 225s (process:2446): libfprint-image_device-DEBUG: 16:49:02.082: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 225s (process:2446): libfprint-device-DEBUG: 16:49:02.082: Device reported finger status change: FP_FINGER_STATUS_NEEDED 225s (process:2446): libfprint-SSM-DEBUG: 16:49:02.082: [vfs5011] DEV_ACTIVATE_NUM_STATES entering state 2 225s (process:2446): libfprint-vfs5011-DEBUG: 16:49:02.082: main_loop: state 2 225s (process:2446): libfprint-vfs5011-DEBUG: 16:49:02.082: capture_chunk_async: capture 256 lines, already have 0 225s (process:2446): libfprint-device-DEBUG: 16:49:02.083: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 225s (process:2446): libfprint-image_device-DEBUG: 16:49:02.083: Image device reported finger status: on 225s (process:2446): libfprint-image_device-DEBUG: 16:49:02.083: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 225s (process:2446): libfprint-vfs5011-DEBUG: 16:49:02.083: process_chunk: got 61440 bytes 225s (process:2446): libfprint-SSM-DEBUG: 16:49:02.083: [vfs5011] DEV_ACTIVATE_NUM_STATES entering state 2 225s (process:2446): libfprint-vfs5011-DEBUG: 16:49:02.083: main_loop: state 2 225s (process:2446): libfprint-vfs5011-DEBUG: 16:49:02.083: capture_chunk_async: capture 256 lines, already have 6 225s (process:2446): libfprint-image_device-DEBUG: 16:49:02.084: Image device reported finger status: on 225s (process:2446): libfprint-vfs5011-DEBUG: 16:49:02.084: process_chunk: got 61440 bytes 225s (process:2446): libfprint-SSM-DEBUG: 16:49:02.084: [vfs5011] DEV_ACTIVATE_NUM_STATES entering state 2 225s (process:2446): libfprint-vfs5011-DEBUG: 16:49:02.084: main_loop: state 2 225s (process:2446): libfprint-vfs5011-DEBUG: 16:49:02.084: capture_chunk_async: capture 256 lines, already have 25 225s (process:2446): libfprint-image_device-DEBUG: 16:49:02.084: Image device reported finger status: on 225s (process:2446): libfprint-vfs5011-DEBUG: 16:49:02.084: process_chunk: got 61440 bytes 225s (process:2446): libfprint-SSM-DEBUG: 16:49:02.085: [vfs5011] DEV_ACTIVATE_NUM_STATES entering state 2 225s (process:2446): libfprint-vfs5011-DEBUG: 16:49:02.085: main_loop: state 2 225s (process:2446): libfprint-vfs5011-DEBUG: 16:49:02.085: capture_chunk_async: capture 256 lines, already have 54 225s (process:2446): libfprint-image_device-DEBUG: 16:49:02.085: Image device reported finger status: on 225s (process:2446): libfprint-vfs5011-DEBUG: 16:49:02.085: process_chunk: got 61440 bytes 225s (process:2446): libfprint-SSM-DEBUG: 16:49:02.085: [vfs5011] DEV_ACTIVATE_NUM_STATES entering state 2 225s (process:2446): libfprint-vfs5011-DEBUG: 16:49:02.085: main_loop: state 2 225s (process:2446): libfprint-vfs5011-DEBUG: 16:49:02.085: capture_chunk_async: capture 256 lines, already have 89 225s (process:2446): libfprint-image_device-DEBUG: 16:49:02.086: Image device reported finger status: on 225s (process:2446): libfprint-vfs5011-DEBUG: 16:49:02.086: process_chunk: got 61440 bytes 225s (process:2446): libfprint-SSM-DEBUG: 16:49:02.086: [vfs5011] DEV_ACTIVATE_NUM_STATES entering state 2 225s (process:2446): libfprint-vfs5011-DEBUG: 16:49:02.086: main_loop: state 2 225s (process:2446): libfprint-vfs5011-DEBUG: 16:49:02.086: capture_chunk_async: capture 256 lines, already have 117 225s (process:2446): libfprint-image_device-DEBUG: 16:49:02.087: Image device reported finger status: on 225s (process:2446): libfprint-vfs5011-DEBUG: 16:49:02.087: process_chunk: got 61440 bytes 225s (process:2446): libfprint-SSM-DEBUG: 16:49:02.087: [vfs5011] DEV_ACTIVATE_NUM_STATES entering state 2 225s (process:2446): libfprint-vfs5011-DEBUG: 16:49:02.087: main_loop: state 2 225s (process:2446): libfprint-vfs5011-DEBUG: 16:49:02.087: capture_chunk_async: capture 256 lines, already have 144 225s (process:2446): libfprint-image_device-DEBUG: 16:49:02.087: Image device reported finger status: on 225s (process:2446): libfprint-vfs5011-DEBUG: 16:49:02.087: process_chunk: got 61440 bytes 225s (process:2446): libfprint-SSM-DEBUG: 16:49:02.088: [vfs5011] DEV_ACTIVATE_NUM_STATES entering state 2 225s (process:2446): libfprint-vfs5011-DEBUG: 16:49:02.088: main_loop: state 2 225s (process:2446): libfprint-vfs5011-DEBUG: 16:49:02.088: capture_chunk_async: capture 256 lines, already have 180 225s (process:2446): libfprint-image_device-DEBUG: 16:49:02.088: Image device reported finger status: on 225s (process:2446): libfprint-vfs5011-DEBUG: 16:49:02.088: process_chunk: got 61440 bytes 225s (process:2446): libfprint-SSM-DEBUG: 16:49:02.088: [vfs5011] DEV_ACTIVATE_NUM_STATES entering state 2 225s (process:2446): libfprint-vfs5011-DEBUG: 16:49:02.088: main_loop: state 2 225s (process:2446): libfprint-vfs5011-DEBUG: 16:49:02.088: capture_chunk_async: capture 256 lines, already have 273 225s (process:2446): libfprint-image_device-DEBUG: 16:49:02.089: Image device reported finger status: on 225s (process:2446): libfprint-vfs5011-DEBUG: 16:49:02.089: process_chunk: got 61440 bytes 225s (process:2446): libfprint-vfs5011-DEBUG: 16:49:02.089: process_chunk: got 50 empty lines, finishing 225s (process:2446): libfprint-SSM-DEBUG: 16:49:02.089: [vfs5011] DEV_ACTIVATE_NUM_STATES entering state 3 225s (process:2446): libfprint-vfs5011-DEBUG: 16:49:02.089: main_loop: state 3 225s (process:2446): libfprint-SSM-DEBUG: 16:49:02.090: [vfs5011] DEV_ACTIVATE_NUM_STATES entering state 4 225s (process:2446): libfprint-vfs5011-DEBUG: 16:49:02.090: main_loop: state 4 225s (process:2446): libfprint-SSM-DEBUG: 16:49:02.090: [vfs5011] PREPARE CAPTURE entering state 0 225s (process:2446): libfprint-vfs5011-DEBUG: 16:49:02.090: Sending vfs5011_cmd_04 225s (process:2446): libfprint-SSM-DEBUG: 16:49:02.091: [vfs5011] PREPARE CAPTURE entering state 1 225s (process:2446): libfprint-vfs5011-DEBUG: 16:49:02.091: Receiving 64 bytes 225s (process:2446): libfprint-vfs5011-DEBUG: 16:49:02.091: Got 64 bytes out of 64 225s (process:2446): libfprint-SSM-DEBUG: 16:49:02.091: [vfs5011] PREPARE CAPTURE entering state 2 225s (process:2446): libfprint-vfs5011-DEBUG: 16:49:02.091: Receiving 84032 bytes 225s (process:2446): libfprint-vfs5011-DEBUG: 16:49:02.092: Got 176 bytes out of 84032 225s (process:2446): libfprint-SSM-DEBUG: 16:49:02.092: [vfs5011] PREPARE CAPTURE entering state 3 225s (process:2446): libfprint-vfs5011-DEBUG: 16:49:02.092: Receiving 64 bytes 225s (process:2446): libfprint-SSM-DEBUG: 16:49:02.092: [vfs5011] PREPARE CAPTURE entering state 4 225s (process:2446): libfprint-vfs5011-DEBUG: 16:49:02.092: Sending vfs5011_cmd_1A 225s (process:2446): libfprint-SSM-DEBUG: 16:49:02.093: [vfs5011] PREPARE CAPTURE entering state 5 225s (process:2446): libfprint-vfs5011-DEBUG: 16:49:02.093: Receiving 64 bytes 225s (process:2446): libfprint-SSM-DEBUG: 16:49:02.093: [vfs5011] PREPARE CAPTURE entering state 6 225s (process:2446): libfprint-vfs5011-DEBUG: 16:49:02.093: Sending vfs5011_prepare_00 225s (process:2446): libfprint-SSM-DEBUG: 16:49:02.094: [vfs5011] PREPARE CAPTURE entering state 7 225s (process:2446): libfprint-vfs5011-DEBUG: 16:49:02.094: Receiving 64 bytes 225s (process:2446): libfprint-SSM-DEBUG: 16:49:02.094: [vfs5011] PREPARE CAPTURE entering state 8 225s (process:2446): libfprint-vfs5011-DEBUG: 16:49:02.094: Sending vfs5011_cmd_1A 225s (process:2446): libfprint-SSM-DEBUG: 16:49:02.095: [vfs5011] PREPARE CAPTURE entering state 9 225s (process:2446): libfprint-vfs5011-DEBUG: 16:49:02.095: Receiving 64 bytes 225s (process:2446): libfprint-SSM-DEBUG: 16:49:02.095: [vfs5011] PREPARE CAPTURE entering state 10 225s (process:2446): libfprint-vfs5011-DEBUG: 16:49:02.095: Sending vfs5011_prepare_01 225s (process:2446): libfprint-SSM-DEBUG: 16:49:02.096: [vfs5011] PREPARE CAPTURE entering state 11 225s (process:2446): libfprint-vfs5011-DEBUG: 16:49:02.096: Receiving 64 bytes 225s (process:2446): libfprint-SSM-DEBUG: 16:49:02.096: [vfs5011] PREPARE CAPTURE entering state 12 225s (process:2446): libfprint-vfs5011-DEBUG: 16:49:02.096: Sending vfs5011_prepare_02 225s (process:2446): libfprint-SSM-DEBUG: 16:49:02.097: [vfs5011] PREPARE CAPTURE entering state 13 225s (process:2446): libfprint-vfs5011-DEBUG: 16:49:02.097: Receiving 2368 bytes 225s (process:2446): libfprint-vfs5011-DEBUG: 16:49:02.097: Got 2368 bytes out of 2368 225s (process:2446): libfprint-SSM-DEBUG: 16:49:02.097: [vfs5011] PREPARE CAPTURE entering state 14 225s (process:2446): libfprint-vfs5011-DEBUG: 16:49:02.097: Receiving 64 bytes 225s (process:2446): libfprint-vfs5011-DEBUG: 16:49:02.098: Got 36 bytes out of 64 225s (process:2446): libfprint-SSM-DEBUG: 16:49:02.098: [vfs5011] PREPARE CAPTURE entering state 15 225s (process:2446): libfprint-vfs5011-DEBUG: 16:49:02.098: Receiving 4800 bytes 225s (process:2446): libfprint-vfs5011-DEBUG: 16:49:02.098: Got 4800 bytes out of 4800 225s (process:2446): libfprint-SSM-DEBUG: 16:49:02.098: [vfs5011] PREPARE CAPTURE entering state 16 225s (process:2446): libfprint-vfs5011-DEBUG: 16:49:02.098: Sending vfs5011_prepare_03 225s (process:2446): libfprint-SSM-DEBUG: 16:49:02.099: [vfs5011] PREPARE CAPTURE entering state 17 225s (process:2446): libfprint-vfs5011-DEBUG: 16:49:02.099: Receiving 64 bytes 225s (process:2446): libfprint-SSM-DEBUG: 16:49:02.099: [vfs5011] PREPARE CAPTURE entering state 18 225s (process:2446): libfprint-vfs5011-DEBUG: 16:49:02.100: Sending vfs5011_prepare_04 225s (process:2446): libfprint-SSM-DEBUG: 16:49:02.100: [vfs5011] PREPARE CAPTURE entering state 19 225s (process:2446): libfprint-vfs5011-DEBUG: 16:49:02.100: Receiving 2368 bytes 225s (process:2446): libfprint-SSM-DEBUG: 16:49:02.100: [vfs5011] PREPARE CAPTURE completed successfully 225s (process:2446): libfprint-SSM-DEBUG: 16:49:02.100: [vfs5011] DEV_ACTIVATE_NUM_STATES completed successfully 225s (process:2446): libfprint-vfs5011-DEBUG: 16:49:02.100: finishing 225s (process:2446): libfprint-assembling-DEBUG: 16:49:02.101: 1710002942101027 225s (process:2446): libfprint-assembling-DEBUG: 16:49:02.101: 1 225s (process:2446): libfprint-assembling-DEBUG: 16:49:02.101: 6 225s (process:2446): libfprint-assembling-DEBUG: 16:49:02.101: 5 225s (process:2446): libfprint-assembling-DEBUG: 16:49:02.101: 4 225s (process:2446): libfprint-assembling-DEBUG: 16:49:02.101: 4 225s (process:2446): libfprint-assembling-DEBUG: 16:49:02.101: 3 225s (process:2446): libfprint-assembling-DEBUG: 16:49:02.101: 3 225s (process:2446): libfprint-assembling-DEBUG: 16:49:02.101: 5 225s (process:2446): libfprint-assembling-DEBUG: 16:49:02.101: 4 225s (process:2446): libfprint-assembling-DEBUG: 16:49:02.101: 27 225s (process:2446): libfprint-assembling-DEBUG: 16:49:02.101: 27 225s (process:2446): libfprint-assembling-DEBUG: 16:49:02.101: 27 225s (process:2446): libfprint-assembling-DEBUG: 16:49:02.101: 27 225s (process:2446): libfprint-assembling-DEBUG: 16:49:02.101: 28 225s (process:2446): libfprint-assembling-DEBUG: 16:49:02.101: 5 225s (process:2446): libfprint-assembling-DEBUG: 16:49:02.101: 28 225s (process:2446): libfprint-assembling-DEBUG: 16:49:02.101: 29 225s (process:2446): libfprint-assembling-DEBUG: 16:49:02.101: 29 225s (process:2446): libfprint-assembling-DEBUG: 16:49:02.101: 29 225s (process:2446): libfprint-assembling-DEBUG: 16:49:02.101: 29 225s (process:2446): libfprint-assembling-DEBUG: 16:49:02.101: 28 225s (process:2446): libfprint-assembling-DEBUG: 16:49:02.101: 28 225s (process:2446): libfprint-assembling-DEBUG: 16:49:02.101: 29 225s (process:2446): libfprint-assembling-DEBUG: 16:49:02.101: 28 225s (process:2446): libfprint-assembling-DEBUG: 16:49:02.101: 30 225s (process:2446): libfprint-assembling-DEBUG: 16:49:02.101: 29 225s (process:2446): libfprint-assembling-DEBUG: 16:49:02.101: 30 225s (process:2446): libfprint-assembling-DEBUG: 16:49:02.101: 5 225s (process:2446): libfprint-assembling-DEBUG: 16:49:02.101: 5 225s (process:2446): libfprint-assembling-DEBUG: 16:49:02.101: 6 225s (process:2446): libfprint-assembling-DEBUG: 16:49:02.101: 6 225s (process:2446): libfprint-assembling-DEBUG: 16:49:02.101: 30 225s (process:2446): libfprint-assembling-DEBUG: 16:49:02.101: 30 225s (process:2446): libfprint-assembling-DEBUG: 16:49:02.101: 30 225s (process:2446): libfprint-assembling-DEBUG: 16:49:02.101: 30 225s (process:2446): libfprint-assembling-DEBUG: 16:49:02.101: 30 225s (process:2446): libfprint-assembling-DEBUG: 16:49:02.101: 7 225s (process:2446): libfprint-assembling-DEBUG: 16:49:02.101: 7 225s (process:2446): libfprint-assembling-DEBUG: 16:49:02.101: 6 225s (process:2446): libfprint-assembling-DEBUG: 16:49:02.101: 6 225s (process:2446): libfprint-assembling-DEBUG: 16:49:02.101: 6 225s (process:2446): libfprint-assembling-DEBUG: 16:49:02.101: 7 225s (process:2446): libfprint-assembling-DEBUG: 16:49:02.101: 6 225s (process:2446): libfprint-assembling-DEBUG: 16:49:02.101: 6 225s (process:2446): libfprint-assembling-DEBUG: 16:49:02.101: 6 225s (process:2446): libfprint-assembling-DEBUG: 16:49:02.101: 6 225s (process:2446): libfprint-assembling-DEBUG: 16:49:02.101: 6 225s (process:2446): libfprint-assembling-DEBUG: 16:49:02.101: 6 225s (process:2446): libfprint-assembling-DEBUG: 16:49:02.101: 4 225s (process:2446): libfprint-assembling-DEBUG: 16:49:02.101: 4 225s (process:2446): libfprint-assembling-DEBUG: 16:49:02.101: 6 225s (process:2446): libfprint-assembling-DEBUG: 16:49:02.101: 6 225s (process:2446): libfprint-assembling-DEBUG: 16:49:02.101: 29 225s (process:2446): libfprint-assembling-DEBUG: 16:49:02.101: 7 225s (process:2446): libfprint-assembling-DEBUG: 16:49:02.101: 7 225s (process:2446): libfprint-assembling-DEBUG: 16:49:02.101: 6 225s (process:2446): libfprint-assembling-DEBUG: 16:49:02.101: 6 225s (process:2446): libfprint-assembling-DEBUG: 16:49:02.101: 30 225s (process:2446): libfprint-assembling-DEBUG: 16:49:02.101: 29 225s (process:2446): libfprint-assembling-DEBUG: 16:49:02.101: 7 225s (process:2446): libfprint-assembling-DEBUG: 16:49:02.101: 7 225s (process:2446): libfprint-assembling-DEBUG: 16:49:02.101: 9 225s (process:2446): libfprint-assembling-DEBUG: 16:49:02.101: 30 225s (process:2446): libfprint-assembling-DEBUG: 16:49:02.101: 30 225s (process:2446): libfprint-assembling-DEBUG: 16:49:02.101: 30 225s (process:2446): libfprint-assembling-DEBUG: 16:49:02.101: 8 225s (process:2446): libfprint-assembling-DEBUG: 16:49:02.101: 8 225s (process:2446): libfprint-assembling-DEBUG: 16:49:02.101: 8 225s (process:2446): libfprint-assembling-DEBUG: 16:49:02.101: 8 225s (process:2446): libfprint-assembling-DEBUG: 16:49:02.101: 7 225s (process:2446): libfprint-assembling-DEBUG: 16:49:02.101: 6 225s (process:2446): libfprint-assembling-DEBUG: 16:49:02.101: 7 225s (process:2446): libfprint-assembling-DEBUG: 16:49:02.101: 30 225s (process:2446): libfprint-assembling-DEBUG: 16:49:02.101: 30 225s (process:2446): libfprint-assembling-DEBUG: 16:49:02.101: 8 225s (process:2446): libfprint-assembling-DEBUG: 16:49:02.101: 7 225s (process:2446): libfprint-assembling-DEBUG: 16:49:02.101: 8 225s (process:2446): libfprint-assembling-DEBUG: 16:49:02.101: 9 225s (process:2446): libfprint-assembling-DEBUG: 16:49:02.101: 8 225s (process:2446): libfprint-assembling-DEBUG: 16:49:02.101: 8 225s (process:2446): libfprint-assembling-DEBUG: 16:49:02.101: 8 225s (process:2446): libfprint-assembling-DEBUG: 16:49:02.101: 9 225s (process:2446): libfprint-assembling-DEBUG: 16:49:02.101: 9 225s (process:2446): libfprint-assembling-DEBUG: 16:49:02.101: 8 225s (process:2446): libfprint-assembling-DEBUG: 16:49:02.101: 9 225s (process:2446): libfprint-assembling-DEBUG: 16:49:02.101: 9 225s (process:2446): libfprint-assembling-DEBUG: 16:49:02.101: 8 225s (process:2446): libfprint-assembling-DEBUG: 16:49:02.101: 8 225s (process:2446): libfprint-assembling-DEBUG: 16:49:02.101: 9 225s (process:2446): libfprint-assembling-DEBUG: 16:49:02.101: 9 225s (process:2446): libfprint-assembling-DEBUG: 16:49:02.101: 8 225s (process:2446): libfprint-assembling-DEBUG: 16:49:02.101: 8 225s (process:2446): libfprint-assembling-DEBUG: 16:49:02.101: 8 225s (process:2446): libfprint-assembling-DEBUG: 16:49:02.101: 8 225s (process:2446): libfprint-assembling-DEBUG: 16:49:02.101: 8 225s (process:2446): libfprint-assembling-DEBUG: 16:49:02.101: 7 225s (process:2446): libfprint-assembling-DEBUG: 16:49:02.101: 29 225s (process:2446): libfprint-assembling-DEBUG: 16:49:02.101: 29 225s (process:2446): libfprint-assembling-DEBUG: 16:49:02.101: 11 225s (process:2446): libfprint-assembling-DEBUG: 16:49:02.101: 9 225s (process:2446): libfprint-assembling-DEBUG: 16:49:02.101: 9 225s (process:2446): libfprint-assembling-DEBUG: 16:49:02.101: 9 225s (process:2446): libfprint-assembling-DEBUG: 16:49:02.101: 9 225s (process:2446): libfprint-assembling-DEBUG: 16:49:02.101: 8 225s (process:2446): libfprint-assembling-DEBUG: 16:49:02.101: 9 225s (process:2446): libfprint-assembling-DEBUG: 16:49:02.101: 8 225s (process:2446): libfprint-assembling-DEBUG: 16:49:02.101: 30 225s (process:2446): libfprint-assembling-DEBUG: 16:49:02.101: 9 225s (process:2446): libfprint-assembling-DEBUG: 16:49:02.101: 7 225s (process:2446): libfprint-assembling-DEBUG: 16:49:02.101: 8 225s (process:2446): libfprint-assembling-DEBUG: 16:49:02.101: 8 225s (process:2446): libfprint-assembling-DEBUG: 16:49:02.101: 27 225s (process:2446): libfprint-assembling-DEBUG: 16:49:02.101: 26 225s (process:2446): libfprint-assembling-DEBUG: 16:49:02.101: 8 225s (process:2446): libfprint-assembling-DEBUG: 16:49:02.101: 7 225s (process:2446): libfprint-assembling-DEBUG: 16:49:02.101: 8 225s (process:2446): libfprint-assembling-DEBUG: 16:49:02.101: 7 225s (process:2446): libfprint-assembling-DEBUG: 16:49:02.101: 8 225s (process:2446): libfprint-assembling-DEBUG: 16:49:02.101: 7 225s (process:2446): libfprint-assembling-DEBUG: 16:49:02.101: 7 225s (process:2446): libfprint-assembling-DEBUG: 16:49:02.101: 8 225s (process:2446): libfprint-assembling-DEBUG: 16:49:02.101: 6 225s (process:2446): libfprint-assembling-DEBUG: 16:49:02.101: 7 225s (process:2446): libfprint-assembling-DEBUG: 16:49:02.101: 6 225s (process:2446): libfprint-assembling-DEBUG: 16:49:02.101: 8 225s (process:2446): libfprint-assembling-DEBUG: 16:49:02.101: 8 225s (process:2446): libfprint-assembling-DEBUG: 16:49:02.101: 8 225s (process:2446): libfprint-assembling-DEBUG: 16:49:02.101: 8 225s (process:2446): libfprint-assembling-DEBUG: 16:49:02.101: 7 225s (process:2446): libfprint-assembling-DEBUG: 16:49:02.101: 6 225s (process:2446): libfprint-assembling-DEBUG: 16:49:02.101: 6 225s (process:2446): libfprint-assembling-DEBUG: 16:49:02.101: 7 225s (process:2446): libfprint-assembling-DEBUG: 16:49:02.101: 7 225s (process:2446): libfprint-assembling-DEBUG: 16:49:02.101: 5 225s (process:2446): libfprint-assembling-DEBUG: 16:49:02.101: 4 225s (process:2446): libfprint-assembling-DEBUG: 16:49:02.101: 2 225s (process:2446): libfprint-assembling-DEBUG: 16:49:02.101: offsets_filtered: 1710002942101756 225s (process:2446): libfprint-assembling-DEBUG: 16:49:02.101: 5 225s (process:2446): libfprint-assembling-DEBUG: 16:49:02.101: 5 225s (process:2446): libfprint-assembling-DEBUG: 16:49:02.101: 5 225s (process:2446): libfprint-assembling-DEBUG: 16:49:02.101: 5 225s (process:2446): libfprint-assembling-DEBUG: 16:49:02.101: 5 225s (process:2446): libfprint-assembling-DEBUG: 16:49:02.101: 6 225s (process:2446): libfprint-assembling-DEBUG: 16:49:02.101: 6 225s (process:2446): libfprint-assembling-DEBUG: 16:49:02.101: 27 225s (process:2446): libfprint-assembling-DEBUG: 16:49:02.101: 27 225s (process:2446): libfprint-assembling-DEBUG: 16:49:02.101: 27 225s (process:2446): libfprint-assembling-DEBUG: 16:49:02.101: 27 225s (process:2446): libfprint-assembling-DEBUG: 16:49:02.101: 27 225s (process:2446): libfprint-assembling-DEBUG: 16:49:02.101: 27 225s (process:2446): libfprint-assembling-DEBUG: 16:49:02.101: 27 225s (process:2446): libfprint-assembling-DEBUG: 16:49:02.101: 28 225s (process:2446): libfprint-assembling-DEBUG: 16:49:02.101: 28 225s (process:2446): libfprint-assembling-DEBUG: 16:49:02.101: 28 225s (process:2446): libfprint-assembling-DEBUG: 16:49:02.101: 28 225s (process:2446): libfprint-assembling-DEBUG: 16:49:02.101: 28 225s (process:2446): libfprint-assembling-DEBUG: 16:49:02.101: 28 225s (process:2446): libfprint-assembling-DEBUG: 16:49:02.101: 28 225s (process:2446): libfprint-assembling-DEBUG: 16:49:02.101: 28 225s (process:2446): libfprint-assembling-DEBUG: 16:49:02.101: 28 225s (process:2446): libfprint-assembling-DEBUG: 16:49:02.101: 29 225s (process:2446): libfprint-assembling-DEBUG: 16:49:02.101: 29 225s (process:2446): libfprint-assembling-DEBUG: 16:49:02.101: 29 225s (process:2446): libfprint-assembling-DEBUG: 16:49:02.101: 29 225s (process:2446): libfprint-assembling-DEBUG: 16:49:02.101: 29 225s (process:2446): libfprint-assembling-DEBUG: 16:49:02.101: 29 225s (process:2446): libfprint-assembling-DEBUG: 16:49:02.101: 28 225s (process:2446): libfprint-assembling-DEBUG: 16:49:02.101: 28 225s (process:2446): libfprint-assembling-DEBUG: 16:49:02.101: 28 225s (process:2446): libfprint-assembling-DEBUG: 16:49:02.101: 7 225s (process:2446): libfprint-assembling-DEBUG: 16:49:02.101: 7 225s (process:2446): libfprint-assembling-DEBUG: 16:49:02.101: 7 225s (process:2446): libfprint-assembling-DEBUG: 16:49:02.101: 6 225s (process:2446): libfprint-assembling-DEBUG: 16:49:02.101: 6 225s (process:2446): libfprint-assembling-DEBUG: 16:49:02.101: 6 225s (process:2446): libfprint-assembling-DEBUG: 16:49:02.101: 6 225s (process:2446): libfprint-assembling-DEBUG: 16:49:02.101: 6 225s (process:2446): libfprint-assembling-DEBUG: 16:49:02.101: 6 225s (process:2446): libfprint-assembling-DEBUG: 16:49:02.101: 6 225s (process:2446): libfprint-assembling-DEBUG: 16:49:02.101: 6 225s (process:2446): libfprint-assembling-DEBUG: 16:49:02.101: 6 225s (process:2446): libfprint-assembling-DEBUG: 16:49:02.101: 6 225s (process:2446): libfprint-assembling-DEBUG: 16:49:02.101: 6 225s (process:2446): libfprint-assembling-DEBUG: 16:49:02.101: 6 225s (process:2446): libfprint-assembling-DEBUG: 16:49:02.101: 6 225s (process:2446): libfprint-assembling-DEBUG: 16:49:02.101: 6 225s (process:2446): libfprint-assembling-DEBUG: 16:49:02.101: 6 225s (process:2446): libfprint-assembling-DEBUG: 16:49:02.101: 6 225s (process:2446): libfprint-assembling-DEBUG: 16:49:02.101: 6 225s (process:2446): libfprint-assembling-DEBUG: 16:49:02.101: 6 225s (process:2446): libfprint-assembling-DEBUG: 16:49:02.101: 7 225s (process:2446): libfprint-assembling-DEBUG: 16:49:02.101: 7 225s (process:2446): libfprint-assembling-DEBUG: 16:49:02.101: 7 225s (process:2446): libfprint-assembling-DEBUG: 16:49:02.101: 7 225s (process:2446): libfprint-assembling-DEBUG: 16:49:02.101: 7 225s (process:2446): libfprint-assembling-DEBUG: 16:49:02.101: 7 225s (process:2446): libfprint-assembling-DEBUG: 16:49:02.101: 7 225s (process:2446): libfprint-assembling-DEBUG: 16:49:02.101: 7 225s (process:2446): libfprint-assembling-DEBUG: 16:49:02.101: 8 225s (process:2446): libfprint-assembling-DEBUG: 16:49:02.101: 8 225s (process:2446): libfprint-assembling-DEBUG: 16:49:02.101: 8 225s (process:2446): libfprint-assembling-DEBUG: 16:49:02.101: 8 225s (process:2446): libfprint-assembling-DEBUG: 16:49:02.101: 8 225s (process:2446): libfprint-assembling-DEBUG: 16:49:02.101: 8 225s (process:2446): libfprint-assembling-DEBUG: 16:49:02.101: 8 225s (process:2446): libfprint-assembling-DEBUG: 16:49:02.101: 8 225s (process:2446): libfprint-assembling-DEBUG: 16:49:02.101: 8 225s (process:2446): libfprint-assembling-DEBUG: 16:49:02.101: 8 225s (process:2446): libfprint-assembling-DEBUG: 16:49:02.101: 8 225s (process:2446): libfprint-assembling-DEBUG: 16:49:02.101: 8 225s (process:2446): libfprint-assembling-DEBUG: 16:49:02.101: 8 225s (process:2446): libfprint-assembling-DEBUG: 16:49:02.101: 8 225s (process:2446): libfprint-assembling-DEBUG: 16:49:02.101: 8 225s (process:2446): libfprint-assembling-DEBUG: 16:49:02.101: 8 225s (process:2446): libfprint-assembling-DEBUG: 16:49:02.101: 8 225s (process:2446): libfprint-assembling-DEBUG: 16:49:02.101: 8 225s (process:2446): libfprint-assembling-DEBUG: 16:49:02.101: 8 225s (process:2446): libfprint-assembling-DEBUG: 16:49:02.101: 8 225s (process:2446): libfprint-assembling-DEBUG: 16:49:02.101: 8 225s (process:2446): libfprint-assembling-DEBUG: 16:49:02.101: 8 225s (process:2446): libfprint-assembling-DEBUG: 16:49:02.102: 8 225s (process:2446): libfprint-assembling-DEBUG: 16:49:02.102: 8 225s (process:2446): libfprint-assembling-DEBUG: 16:49:02.102: 8 225s (process:2446): libfprint-assembling-DEBUG: 16:49:02.102: 8 225s (process:2446): libfprint-assembling-DEBUG: 16:49:02.102: 8 225s (process:2446): libfprint-assembling-DEBUG: 16:49:02.102: 8 225s (process:2446): libfprint-assembling-DEBUG: 16:49:02.102: 9 225s (process:2446): libfprint-assembling-DEBUG: 16:49:02.102: 9 225s (process:2446): libfprint-assembling-DEBUG: 16:49:02.102: 9 225s (process:2446): libfprint-assembling-DEBUG: 16:49:02.102: 9 225s (process:2446): libfprint-assembling-DEBUG: 16:49:02.102: 9 225s (process:2446): libfprint-assembling-DEBUG: 16:49:02.102: 9 225s (process:2446): libfprint-assembling-DEBUG: 16:49:02.102: 9 225s (process:2446): libfprint-assembling-DEBUG: 16:49:02.102: 9 225s (process:2446): libfprint-assembling-DEBUG: 16:49:02.102: 9 225s (process:2446): libfprint-assembling-DEBUG: 16:49:02.102: 8 225s (process:2446): libfprint-assembling-DEBUG: 16:49:02.102: 9 225s (process:2446): libfprint-assembling-DEBUG: 16:49:02.102: 9 225s (process:2446): libfprint-assembling-DEBUG: 16:49:02.102: 9 225s (process:2446): libfprint-assembling-DEBUG: 16:49:02.102: 8 225s (process:2446): libfprint-assembling-DEBUG: 16:49:02.102: 8 225s (process:2446): libfprint-assembling-DEBUG: 16:49:02.102: 8 225s (process:2446): libfprint-assembling-DEBUG: 16:49:02.102: 8 225s (process:2446): libfprint-assembling-DEBUG: 16:49:02.102: 8 225s (process:2446): libfprint-assembling-DEBUG: 16:49:02.102: 8 225s (process:2446): libfprint-assembling-DEBUG: 16:49:02.102: 8 225s (process:2446): libfprint-assembling-DEBUG: 16:49:02.102: 8 225s (process:2446): libfprint-assembling-DEBUG: 16:49:02.102: 8 225s (process:2446): libfprint-assembling-DEBUG: 16:49:02.102: 8 225s (process:2446): libfprint-assembling-DEBUG: 16:49:02.102: 8 225s (process:2446): libfprint-assembling-DEBUG: 16:49:02.102: 8 225s (process:2446): libfprint-assembling-DEBUG: 16:49:02.102: 8 225s (process:2446): libfprint-assembling-DEBUG: 16:49:02.102: 8 225s (process:2446): libfprint-assembling-DEBUG: 16:49:02.102: 8 225s (process:2446): libfprint-assembling-DEBUG: 16:49:02.102: 8 225s (process:2446): libfprint-assembling-DEBUG: 16:49:02.102: 8 225s (process:2446): libfprint-assembling-DEBUG: 16:49:02.102: 8 225s (process:2446): libfprint-assembling-DEBUG: 16:49:02.102: 7 225s (process:2446): libfprint-assembling-DEBUG: 16:49:02.102: 7 225s (process:2446): libfprint-assembling-DEBUG: 16:49:02.102: 7 225s (process:2446): libfprint-assembling-DEBUG: 16:49:02.102: 7 225s (process:2446): libfprint-assembling-DEBUG: 16:49:02.102: 7 225s (process:2446): libfprint-assembling-DEBUG: 16:49:02.102: 7 225s (process:2446): libfprint-assembling-DEBUG: 16:49:02.102: 7 225s (process:2446): libfprint-assembling-DEBUG: 16:49:02.102: 7 225s (process:2446): libfprint-assembling-DEBUG: 16:49:02.102: 7 225s (process:2446): libfprint-assembling-DEBUG: 16:49:02.102: 7 225s (process:2446): libfprint-assembling-DEBUG: 16:49:02.102: 7 225s (process:2446): libfprint-assembling-DEBUG: 16:49:02.102: 7 225s (process:2446): libfprint-assembling-DEBUG: 16:49:02.102: 7 225s (process:2446): libfprint-assembling-DEBUG: 16:49:02.102: 7 225s (process:2446): libfprint-assembling-DEBUG: 16:49:02.102: 7 225s (process:2446): libfprint-assembling-DEBUG: 16:49:02.102: 2 225s (process:2446): libfprint-vfs5011-DEBUG: 16:49:02.102: Image captured, committing 225s (process:2446): libfprint-image_device-DEBUG: 16:49:02.102: Image device captured an image 225s (process:2446): libfprint-image_device-DEBUG: 16:49:02.103: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 225s (process:2446): libfprint-device-DEBUG: 16:49:02.103: Device reported finger status change: FP_FINGER_STATUS_PRESENT 225s (process:2446): libfprint-device-DEBUG: 16:49:02.103: Device reported finger status change: FP_FINGER_STATUS_NONE 225s (process:2446): libfprint-image_device-DEBUG: 16:49:02.103: Image device reported finger status: off 225s (process:2446): libfprint-image_device-DEBUG: 16:49:02.103: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 225s (process:2446): libfprint-image_device-DEBUG: 16:49:02.103: Deactivating image device 225s (process:2446): libfprint-image_device-DEBUG: 16:49:02.103: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_DEACTIVATING 225s (process:2446): libfprint-image_device-DEBUG: 16:49:02.103: Image device deactivation completed 225s (process:2446): libfprint-image_device-DEBUG: 16:49:02.103: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE 225s (process:2446): libfprint-image-DEBUG: 16:49:02.117: Minutiae scan completed in 0.014048 secs 225s (process:2446): libfprint-device-DEBUG: 16:49:02.117: Device reported capture completion 225s (process:2446): libfprint-device-DEBUG: 16:49:02.117: Completing action FPI_DEVICE_ACTION_CAPTURE in idle! 225s (process:2446): libfprint-device-DEBUG: 16:49:02.117: Updated temperature model after 0.05 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 225s (process:2446): libfprint-image_device-DEBUG: 16:49:02.117: Image device close completed 225s (process:2446): libfprint-device-DEBUG: 16:49:02.117: Device reported close completion 225s (process:2446): libfprint-device-DEBUG: 16:49:02.117: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 225s (process:2446): libfprint-device-DEBUG: 16:49:02.117: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 225s ** (umockdev-run:2442): DEBUG: 16:49:02.218: umockdev.vala:150: Removing test bed /tmp/umockdev.UWQYJ2 225s (umockdev-run:2442): GLib-DEBUG: 16:49:02.221: unsetenv() is not thread-safe and should not be used after threads are created 225s Comparing PNGs /tmp/libfprint-umockdev-test-wt6g42d8/capture.png and /usr/share/installed-tests/libfprint-2/vfs5011/capture.png 225s PASS: libfprint-2/driver-vfs5011.test 225s SUMMARY: total=33; passed=33; skipped=0; failed=0; user=22.0s; system=10.5s; maxrss=39864 225s autopkgtest [16:49:02]: test installed-tests: -----------------------] 226s autopkgtest [16:49:03]: test installed-tests: - - - - - - - - - - results - - - - - - - - - - 226s installed-tests PASS 226s autopkgtest [16:49:03]: @@@@@@@@@@@@@@@@@@@@ summary 226s installed-tests PASS 238s Creating nova instance adt-noble-arm64-libfprint-20240309-164517-juju-7f2275-prod-proposed-migration-environment-2 from image adt/ubuntu-noble-arm64-server-20240308.img (UUID ddbc0ee7-bb97-4aa3-b5e1-9386758c2ba2)...