0s autopkgtest [00:47:29]: starting date and time: 2025-02-16 00:47:29+0000 0s autopkgtest [00:47:29]: git checkout: 325255d2 Merge branch 'pin-any-arch' into 'ubuntu/production' 0s autopkgtest [00:47:29]: host juju-7f2275-prod-proposed-migration-environment-9; command line: /home/ubuntu/autopkgtest/runner/autopkgtest --output-dir /tmp/autopkgtest-work.49kz_cc7/out --timeout-copy=6000 --setup-commands 'ln -s /dev/null /etc/systemd/system/bluetooth.service; printf "http_proxy=http://squid.internal:3128\nhttps_proxy=http://squid.internal:3128\nno_proxy=127.0.0.1,127.0.1.1,login.ubuntu.com,localhost,localdomain,novalocal,internal,archive.ubuntu.com,ports.ubuntu.com,security.ubuntu.com,ddebs.ubuntu.com,changelogs.ubuntu.com,keyserver.ubuntu.com,launchpadlibrarian.net,launchpadcontent.net,launchpad.net,10.24.0.0/24,keystone.ps5.canonical.com,objectstorage.prodstack5.canonical.com,radosgw.ps5.canonical.com\n" >> /etc/environment' --apt-pocket=proposed=src:glibc,src:iproute2,src:php-twig,src:postgresql-17,src:postgresql-common,src:roundcube --apt-upgrade libfprint --timeout-short=300 --timeout-copy=20000 --timeout-build=20000 '--env=ADT_TEST_TRIGGERS=glibc/2.41-1ubuntu1 iproute2/6.13.0-1ubuntu1 php-twig/3.19.0-1 postgresql-17/17.3-2 postgresql-common/273 roundcube/1.6.10+dfsg-1' -- lxd -r lxd-armhf-10.145.243.27 lxd-armhf-10.145.243.27:autopkgtest/ubuntu/plucky/armhf 55s autopkgtest [00:48:24]: testbed dpkg architecture: armhf 58s autopkgtest [00:48:27]: testbed apt version: 2.9.14ubuntu1 62s autopkgtest [00:48:31]: @@@@@@@@@@@@@@@@@@@@ test bed setup 64s autopkgtest [00:48:33]: testbed release detected to be: None 74s autopkgtest [00:48:43]: updating testbed package index (apt update) 76s Get:1 http://ftpmaster.internal/ubuntu plucky-proposed InRelease [110 kB] 77s Get:2 http://ftpmaster.internal/ubuntu plucky InRelease [249 kB] 77s Get:3 http://ftpmaster.internal/ubuntu plucky-updates InRelease [110 kB] 77s Get:4 http://ftpmaster.internal/ubuntu plucky-security InRelease [110 kB] 77s Get:5 http://ftpmaster.internal/ubuntu plucky-proposed/multiverse Sources [13.1 kB] 77s Get:6 http://ftpmaster.internal/ubuntu plucky-proposed/universe Sources [823 kB] 77s Get:7 http://ftpmaster.internal/ubuntu plucky-proposed/main Sources [73.1 kB] 77s Get:8 http://ftpmaster.internal/ubuntu plucky-proposed/restricted Sources [3120 B] 77s Get:9 http://ftpmaster.internal/ubuntu plucky-proposed/main armhf Packages [145 kB] 77s Get:10 http://ftpmaster.internal/ubuntu plucky-proposed/main armhf Components [5072 B] 77s Get:11 http://ftpmaster.internal/ubuntu plucky-proposed/restricted armhf Packages [760 B] 77s Get:12 http://ftpmaster.internal/ubuntu plucky-proposed/restricted armhf Components [216 B] 77s Get:13 http://ftpmaster.internal/ubuntu plucky-proposed/universe armhf Packages [867 kB] 77s Get:14 http://ftpmaster.internal/ubuntu plucky-proposed/universe armhf Components [421 kB] 77s Get:15 http://ftpmaster.internal/ubuntu plucky-proposed/multiverse armhf Packages [1896 B] 77s Get:16 http://ftpmaster.internal/ubuntu plucky-proposed/multiverse armhf Components [1316 B] 77s Get:17 http://ftpmaster.internal/ubuntu plucky/restricted Sources [17.8 kB] 77s Get:18 http://ftpmaster.internal/ubuntu plucky/multiverse Sources [296 kB] 77s Get:19 http://ftpmaster.internal/ubuntu plucky/main Sources [1381 kB] 77s Get:20 http://ftpmaster.internal/ubuntu plucky/universe Sources [20.9 MB] 78s Get:21 http://ftpmaster.internal/ubuntu plucky/main armhf Packages [1368 kB] 78s Get:22 http://ftpmaster.internal/ubuntu plucky/main armhf Components [404 kB] 78s Get:23 http://ftpmaster.internal/ubuntu plucky/restricted armhf Packages [2900 B] 78s Get:24 http://ftpmaster.internal/ubuntu plucky/restricted armhf Components [196 B] 78s Get:25 http://ftpmaster.internal/ubuntu plucky/universe armhf Packages [15.2 MB] 78s Get:26 http://ftpmaster.internal/ubuntu plucky/universe armhf Components [3922 kB] 78s Get:27 http://ftpmaster.internal/ubuntu plucky/multiverse armhf Packages [172 kB] 78s Get:28 http://ftpmaster.internal/ubuntu plucky/multiverse armhf Components [39.7 kB] 78s Get:29 http://ftpmaster.internal/ubuntu plucky-updates/main armhf Components [208 B] 78s Get:30 http://ftpmaster.internal/ubuntu plucky-updates/restricted armhf Components [212 B] 78s Get:31 http://ftpmaster.internal/ubuntu plucky-updates/universe armhf Components [212 B] 78s Get:32 http://ftpmaster.internal/ubuntu plucky-updates/multiverse armhf Components [212 B] 78s Get:33 http://ftpmaster.internal/ubuntu plucky-security/main armhf Components [204 B] 78s Get:34 http://ftpmaster.internal/ubuntu plucky-security/restricted armhf Components [212 B] 78s Get:35 http://ftpmaster.internal/ubuntu plucky-security/universe armhf Components [208 B] 78s Get:36 http://ftpmaster.internal/ubuntu plucky-security/multiverse armhf Components [208 B] 85s Fetched 46.7 MB in 6s (7612 kB/s) 86s Reading package lists... 93s autopkgtest [00:49:02]: upgrading testbed (apt dist-upgrade and autopurge) 95s Reading package lists... 96s Building dependency tree... 96s Reading state information... 97s Calculating upgrade...Starting pkgProblemResolver with broken count: 0 97s Starting 2 pkgProblemResolver with broken count: 0 97s Done 97s Entering ResolveByKeep 98s 98s The following packages were automatically installed and are no longer required: 98s libassuan0 libicu74 libnsl2 libpython3.12-minimal libpython3.12-stdlib 98s libunwind8 linux-headers-6.11.0-8 linux-headers-6.11.0-8-generic python3.12 98s python3.12-minimal 98s Use 'apt autoremove' to remove them. 98s The following NEW packages will be installed: 98s libicu76 libpython3.13-minimal libpython3.13-stdlib linux-headers-6.12.0-15 98s linux-headers-6.12.0-15-generic login.defs openssl-provider-legacy 98s python3-bcrypt python3.13 python3.13-minimal 98s The following packages will be upgraded: 98s apparmor apport apport-core-dump-handler appstream apt apt-utils base-passwd 98s bash bash-completion bind9-dnsutils bind9-host bind9-libs binutils 98s binutils-arm-linux-gnueabihf binutils-common bsdextrautils bsdutils 98s btrfs-progs busybox-initramfs busybox-static ca-certificates cloud-init 98s cloud-init-base console-setup console-setup-linux coreutils cron 98s cron-daemon-common curl dash dbus dbus-bin dbus-daemon 98s dbus-session-bus-common dbus-system-bus-common dbus-user-session dhcpcd-base 98s diffutils dirmngr distro-info dmsetup dpkg dpkg-dev dracut-install e2fsprogs 98s e2fsprogs-l10n ed eject ethtool fdisk fwupd gcc-14-base gettext-base 98s gir1.2-girepository-2.0 gir1.2-glib-2.0 gnupg gnupg-l10n gnupg-utils gpg 98s gpg-agent gpg-wks-client gpgconf gpgsm gpgv groff-base gzip htop 98s ibverbs-providers init init-system-helpers initramfs-tools 98s initramfs-tools-bin initramfs-tools-core iproute2 iptables iputils-ping 98s iputils-tracepath keyboard-configuration keyboxd kpartx krb5-locales 98s libapparmor1 libappstream5 libapt-pkg6.0t64 libarchive13t64 libatomic1 98s libbinutils libblkid1 libblockdev-crypto3 libblockdev-fs3 libblockdev-loop3 98s libblockdev-mdraid3 libblockdev-nvme3 libblockdev-part3 libblockdev-swap3 98s libblockdev-utils3 libblockdev3 libbpf1 libc-bin libc6 libcap-ng0 98s libcom-err2 libcrypt1 libctf-nobfd0 libctf0 libcurl3t64-gnutls libcurl4t64 98s libdbus-1-3 libdebconfclient0 libdevmapper1.02.1 libdpkg-perl libedit2 98s libext2fs2t64 libfdisk1 libffi8 libfribidi0 libftdi1-2 libfwupd3 libgcc-s1 98s libgirepository-1.0-1 libglib2.0-0t64 libglib2.0-bin libglib2.0-data 98s libgnutls30t64 libgpg-error-l10n libgpg-error0 libgpgme11t64 98s libgssapi-krb5-2 libgstreamer1.0-0 libgudev-1.0-0 libibverbs1 libicu74 98s libip4tc2 libip6tc2 libjson-glib-1.0-0 libjson-glib-1.0-common libk5crypto3 98s libkrb5-3 libkrb5support0 libldap-common libldap2 liblz4-1 libmount1 98s libncurses6 libncursesw6 libnetplan1 libnewt0.52 libnftables1 libnftnl11 98s libnpth0t64 libnspr4 libnss-systemd libnss3 libnvme1t64 libpam-systemd 98s libpcap0.8t64 libpng16-16t64 libpolkit-agent-1-0 libpolkit-gobject-1-0 98s libprotobuf-c1 libpython3-stdlib libpython3.12-minimal libpython3.12-stdlib 98s libqmi-glib5 libqmi-proxy libreadline8t64 libsasl2-2 libsasl2-modules 98s libsasl2-modules-db libselinux1 libsemanage-common libsemanage2 libsframe1 98s libsmartcols1 libss2 libssl3t64 libstdc++6 libsystemd-shared libsystemd0 98s libtasn1-6 libtinfo6 libtraceevent1 libtraceevent1-plugin libudev1 98s libudisks2-0 libunistring5 libusb-1.0-0 libuuid1 libvolume-key1 libwrap0 98s libxdmcp6 libxkbcommon0 libxml2 libxtables12 libyaml-0-2 libzstd1 98s linux-headers-generic locales login logsave lshw make mawk mount 98s multipath-tools nano ncurses-base ncurses-bin ncurses-term netcat-openbsd 98s netplan-generator netplan.io nftables openssl passwd pci.ids pinentry-curses 98s polkitd pollinate powermgmt-base publicsuffix python-apt-common 98s python-babel-localedata python3 python3-apport python3-apt python3-attr 98s python3-babel python3-certifi python3-chardet python3-cryptography 98s python3-distro-info python3-gdbm python3-gi python3-idna python3-jinja2 98s python3-json-pointer python3-jsonpatch python3-jsonschema python3-jwt 98s python3-launchpadlib python3-lazr.uri python3-minimal python3-more-itertools 98s python3-netplan python3-newt python3-oauthlib python3-openssl 98s python3-pkg-resources python3-problem-report python3-pygments 98s python3-referencing python3-rich python3-setuptools 98s python3-software-properties python3-urllib3 python3-wadllib python3.12 98s python3.12-gdbm python3.12-minimal python3.13-gdbm readline-common rsync 98s rsyslog software-properties-common systemd systemd-cryptsetup 98s systemd-resolved systemd-sysv systemd-timesyncd tar tzdata ubuntu-minimal 98s ubuntu-standard ucf udev udisks2 ufw unattended-upgrades usb.ids util-linux 98s uuid-runtime whiptail xauth xfsprogs zstd 99s 286 upgraded, 10 newly installed, 0 to remove and 0 not upgraded. 99s Need to get 132 MB of archives. 99s After this operation, 208 MB of additional disk space will be used. 99s Get:1 http://ftpmaster.internal/ubuntu plucky/main armhf bash armhf 5.2.37-1ubuntu1 [677 kB] 99s Get:2 http://ftpmaster.internal/ubuntu plucky/main armhf bsdutils armhf 1:2.40.2-14ubuntu1 [110 kB] 99s Get:3 http://ftpmaster.internal/ubuntu plucky/main armhf coreutils armhf 9.5-1ubuntu1 [1275 kB] 99s Get:4 http://ftpmaster.internal/ubuntu plucky/main armhf dash armhf 0.5.12-12ubuntu1 [87.4 kB] 99s Get:5 http://ftpmaster.internal/ubuntu plucky/main armhf diffutils armhf 1:3.10-2 [172 kB] 99s Get:6 http://ftpmaster.internal/ubuntu plucky-proposed/main armhf locales all 2.41-1ubuntu1 [4246 kB] 99s Get:7 http://ftpmaster.internal/ubuntu plucky-proposed/main armhf libc6 armhf 2.41-1ubuntu1 [2932 kB] 99s Get:8 http://ftpmaster.internal/ubuntu plucky-proposed/main armhf libc-bin armhf 2.41-1ubuntu1 [545 kB] 99s Get:9 http://ftpmaster.internal/ubuntu plucky/main armhf libatomic1 armhf 14.2.0-17ubuntu1 [7898 B] 99s Get:10 http://ftpmaster.internal/ubuntu plucky/main armhf gcc-14-base armhf 14.2.0-17ubuntu1 [53.5 kB] 99s Get:11 http://ftpmaster.internal/ubuntu plucky/main armhf libgcc-s1 armhf 14.2.0-17ubuntu1 [40.6 kB] 99s Get:12 http://ftpmaster.internal/ubuntu plucky/main armhf libstdc++6 armhf 14.2.0-17ubuntu1 [711 kB] 99s Get:13 http://ftpmaster.internal/ubuntu plucky/main armhf liblz4-1 armhf 1.10.0-3 [57.2 kB] 99s Get:14 http://ftpmaster.internal/ubuntu plucky/main armhf openssl-provider-legacy armhf 3.4.0-1ubuntu2 [29.4 kB] 99s Get:15 http://ftpmaster.internal/ubuntu plucky/main armhf libssl3t64 armhf 3.4.0-1ubuntu2 [1756 kB] 99s Get:16 http://ftpmaster.internal/ubuntu plucky/main armhf libzstd1 armhf 1.5.6+dfsg-2 [266 kB] 99s Get:17 http://ftpmaster.internal/ubuntu plucky/main armhf systemd-timesyncd armhf 257.2-3ubuntu1 [42.1 kB] 99s Get:18 http://ftpmaster.internal/ubuntu plucky/main armhf dbus-session-bus-common all 1.16.0-1ubuntu1 [53.1 kB] 99s Get:19 http://ftpmaster.internal/ubuntu plucky/main armhf systemd-sysv armhf 257.2-3ubuntu1 [11.9 kB] 99s Get:20 http://ftpmaster.internal/ubuntu plucky/main armhf libpam-systemd armhf 257.2-3ubuntu1 [238 kB] 99s Get:21 http://ftpmaster.internal/ubuntu plucky/main armhf dbus-user-session armhf 1.16.0-1ubuntu1 [9684 B] 99s Get:22 http://ftpmaster.internal/ubuntu plucky/main armhf libapparmor1 armhf 4.1.0~beta1-0ubuntu5 [47.3 kB] 99s Get:23 http://ftpmaster.internal/ubuntu plucky/main armhf libcap-ng0 armhf 0.8.5-4 [13.8 kB] 99s Get:24 http://ftpmaster.internal/ubuntu plucky/main armhf libselinux1 armhf 3.7-3ubuntu2 [73.2 kB] 99s Get:25 http://ftpmaster.internal/ubuntu plucky/main armhf dbus-system-bus-common all 1.16.0-1ubuntu1 [54.3 kB] 99s Get:26 http://ftpmaster.internal/ubuntu plucky/main armhf dbus-bin armhf 1.16.0-1ubuntu1 [37.9 kB] 99s Get:27 http://ftpmaster.internal/ubuntu plucky/main armhf dbus armhf 1.16.0-1ubuntu1 [28.1 kB] 99s Get:28 http://ftpmaster.internal/ubuntu plucky/main armhf dbus-daemon armhf 1.16.0-1ubuntu1 [111 kB] 99s Get:29 http://ftpmaster.internal/ubuntu plucky/main armhf libdbus-1-3 armhf 1.16.0-1ubuntu1 [162 kB] 99s Get:30 http://ftpmaster.internal/ubuntu plucky/main armhf systemd-resolved armhf 257.2-3ubuntu1 [315 kB] 99s Get:31 http://ftpmaster.internal/ubuntu plucky/main armhf systemd-cryptsetup armhf 257.2-3ubuntu1 [126 kB] 99s Get:32 http://ftpmaster.internal/ubuntu plucky/main armhf libncurses6 armhf 6.5+20250125-2 [88.8 kB] 99s Get:33 http://ftpmaster.internal/ubuntu plucky/main armhf libncursesw6 armhf 6.5+20250125-2 [118 kB] 99s Get:34 http://ftpmaster.internal/ubuntu plucky/main armhf libtinfo6 armhf 6.5+20250125-2 [91.9 kB] 100s Get:35 http://ftpmaster.internal/ubuntu plucky/main armhf bsdextrautils armhf 2.40.2-14ubuntu1 [94.2 kB] 100s Get:36 http://ftpmaster.internal/ubuntu plucky/main armhf eject armhf 2.40.2-14ubuntu1 [63.4 kB] 100s Get:37 http://ftpmaster.internal/ubuntu plucky/main armhf fdisk armhf 2.40.2-14ubuntu1 [157 kB] 100s Get:38 http://ftpmaster.internal/ubuntu plucky/main armhf libblkid1 armhf 2.40.2-14ubuntu1 [169 kB] 100s Get:39 http://ftpmaster.internal/ubuntu plucky/main armhf libmount1 armhf 2.40.2-14ubuntu1 [194 kB] 100s Get:40 http://ftpmaster.internal/ubuntu plucky/main armhf libsmartcols1 armhf 2.40.2-14ubuntu1 [137 kB] 100s Get:41 http://ftpmaster.internal/ubuntu plucky/main armhf libuuid1 armhf 2.40.2-14ubuntu1 [41.0 kB] 100s Get:42 http://ftpmaster.internal/ubuntu plucky/main armhf util-linux armhf 2.40.2-14ubuntu1 [1190 kB] 100s Get:43 http://ftpmaster.internal/ubuntu plucky/main armhf uuid-runtime armhf 2.40.2-14ubuntu1 [63.7 kB] 100s Get:44 http://ftpmaster.internal/ubuntu plucky/main armhf libfdisk1 armhf 2.40.2-14ubuntu1 [217 kB] 100s Get:45 http://ftpmaster.internal/ubuntu plucky/main armhf mount armhf 2.40.2-14ubuntu1 [158 kB] 100s Get:46 http://ftpmaster.internal/ubuntu plucky/main armhf readline-common all 8.2-6 [56.5 kB] 100s Get:47 http://ftpmaster.internal/ubuntu plucky/main armhf libreadline8t64 armhf 8.2-6 [131 kB] 100s Get:48 http://ftpmaster.internal/ubuntu plucky/main armhf libcrypt1 armhf 1:4.4.38-1 [91.7 kB] 100s Get:49 http://ftpmaster.internal/ubuntu plucky/main armhf libsystemd-shared armhf 257.2-3ubuntu1 [2203 kB] 100s Get:50 http://ftpmaster.internal/ubuntu plucky/main armhf systemd armhf 257.2-3ubuntu1 [3028 kB] 100s Get:51 http://ftpmaster.internal/ubuntu plucky/main armhf udev armhf 257.2-3ubuntu1 [1402 kB] 100s Get:52 http://ftpmaster.internal/ubuntu plucky/main armhf libnss-systemd armhf 257.2-3ubuntu1 [164 kB] 100s Get:53 http://ftpmaster.internal/ubuntu plucky/main armhf libudev1 armhf 257.2-3ubuntu1 [193 kB] 100s Get:54 http://ftpmaster.internal/ubuntu plucky/main armhf libsystemd0 armhf 257.2-3ubuntu1 [494 kB] 100s Get:55 http://ftpmaster.internal/ubuntu plucky/main armhf libapt-pkg6.0t64 armhf 2.9.28 [1080 kB] 100s Get:56 http://ftpmaster.internal/ubuntu plucky/main armhf tar armhf 1.35+dfsg-3.1 [240 kB] 100s Get:57 http://ftpmaster.internal/ubuntu plucky/main armhf dpkg armhf 1.22.11ubuntu4 [1242 kB] 100s Get:58 http://ftpmaster.internal/ubuntu plucky/main armhf gzip armhf 1.13-1ubuntu2 [98.1 kB] 100s Get:59 http://ftpmaster.internal/ubuntu plucky/main armhf ncurses-bin armhf 6.5+20250125-2 [179 kB] 100s Get:60 http://ftpmaster.internal/ubuntu plucky/main armhf libdebconfclient0 armhf 0.274ubuntu1 [11.2 kB] 100s Get:61 http://ftpmaster.internal/ubuntu plucky/main armhf base-passwd armhf 3.6.6 [53.4 kB] 100s Get:62 http://ftpmaster.internal/ubuntu plucky/main armhf init-system-helpers all 1.68 [39.0 kB] 100s Get:63 http://ftpmaster.internal/ubuntu plucky/main armhf ncurses-base all 6.5+20250125-2 [25.8 kB] 100s Get:64 http://ftpmaster.internal/ubuntu plucky/main armhf ncurses-term all 6.5+20250125-2 [276 kB] 100s Get:65 http://ftpmaster.internal/ubuntu plucky/main armhf apt armhf 2.9.28 [1389 kB] 100s Get:66 http://ftpmaster.internal/ubuntu plucky/main armhf apt-utils armhf 2.9.28 [214 kB] 100s Get:67 http://ftpmaster.internal/ubuntu plucky/main armhf libgpg-error-l10n all 1.51-3 [8800 B] 100s Get:68 http://ftpmaster.internal/ubuntu plucky/main armhf libgpg-error0 armhf 1.51-3 [64.8 kB] 100s Get:69 http://ftpmaster.internal/ubuntu plucky/main armhf libnpth0t64 armhf 1.8-2 [7572 B] 100s Get:70 http://ftpmaster.internal/ubuntu plucky/main armhf gpg-wks-client armhf 2.4.4-2ubuntu22 [87.5 kB] 100s Get:71 http://ftpmaster.internal/ubuntu plucky/main armhf dirmngr armhf 2.4.4-2ubuntu22 [347 kB] 100s Get:72 http://ftpmaster.internal/ubuntu plucky/main armhf gpgsm armhf 2.4.4-2ubuntu22 [242 kB] 100s Get:73 http://ftpmaster.internal/ubuntu plucky/main armhf gnupg-utils armhf 2.4.4-2ubuntu22 [159 kB] 100s Get:74 http://ftpmaster.internal/ubuntu plucky/main armhf gpg-agent armhf 2.4.4-2ubuntu22 [237 kB] 100s Get:75 http://ftpmaster.internal/ubuntu plucky/main armhf gpg armhf 2.4.4-2ubuntu22 [525 kB] 100s Get:76 http://ftpmaster.internal/ubuntu plucky/main armhf gpgconf armhf 2.4.4-2ubuntu22 [116 kB] 100s Get:77 http://ftpmaster.internal/ubuntu plucky/main armhf gnupg all 2.4.4-2ubuntu22 [359 kB] 100s Get:78 http://ftpmaster.internal/ubuntu plucky/main armhf keyboxd armhf 2.4.4-2ubuntu22 [111 kB] 100s Get:79 http://ftpmaster.internal/ubuntu plucky/main armhf pinentry-curses armhf 1.3.1-2ubuntu2 [40.6 kB] 100s Get:80 http://ftpmaster.internal/ubuntu plucky/main armhf libtasn1-6 armhf 4.20.0-2 [38.2 kB] 100s Get:81 http://ftpmaster.internal/ubuntu plucky/main armhf libunistring5 armhf 1.3-1 [583 kB] 100s Get:82 http://ftpmaster.internal/ubuntu plucky/main armhf libgnutls30t64 armhf 3.8.9-2ubuntu1 [961 kB] 100s Get:83 http://ftpmaster.internal/ubuntu plucky/main armhf libsasl2-modules-db armhf 2.1.28+dfsg1-8build1 [19.0 kB] 100s Get:84 http://ftpmaster.internal/ubuntu plucky/main armhf libsasl2-2 armhf 2.1.28+dfsg1-8build1 [49.9 kB] 100s Get:85 http://ftpmaster.internal/ubuntu plucky/main armhf libldap-common all 2.6.9+dfsg-1~exp2ubuntu1 [33.2 kB] 100s Get:86 http://ftpmaster.internal/ubuntu plucky/main armhf libldap2 armhf 2.6.9+dfsg-1~exp2ubuntu1 [177 kB] 100s Get:87 http://ftpmaster.internal/ubuntu plucky/main armhf gpgv armhf 2.4.4-2ubuntu22 [225 kB] 100s Get:88 http://ftpmaster.internal/ubuntu plucky/main armhf e2fsprogs-l10n all 1.47.2-1ubuntu1 [7030 B] 100s Get:89 http://ftpmaster.internal/ubuntu plucky/main armhf logsave armhf 1.47.2-1ubuntu1 [25.7 kB] 100s Get:90 http://ftpmaster.internal/ubuntu plucky/main armhf ubuntu-minimal armhf 1.547 [11.4 kB] 100s Get:91 http://ftpmaster.internal/ubuntu plucky/main armhf initramfs-tools all 0.145ubuntu2 [7948 B] 100s Get:92 http://ftpmaster.internal/ubuntu plucky/main armhf initramfs-tools-core all 0.145ubuntu2 [51.5 kB] 100s Get:93 http://ftpmaster.internal/ubuntu plucky/main armhf libext2fs2t64 armhf 1.47.2-1ubuntu1 [207 kB] 100s Get:94 http://ftpmaster.internal/ubuntu plucky/main armhf e2fsprogs armhf 1.47.2-1ubuntu1 [588 kB] 100s Get:95 http://ftpmaster.internal/ubuntu plucky/main armhf console-setup-linux all 1.226ubuntu3 [1880 kB] 101s Get:96 http://ftpmaster.internal/ubuntu plucky/main armhf console-setup all 1.226ubuntu3 [110 kB] 101s Get:97 http://ftpmaster.internal/ubuntu plucky/main armhf keyboard-configuration all 1.226ubuntu3 [212 kB] 101s Get:98 http://ftpmaster.internal/ubuntu plucky/main armhf dhcpcd-base armhf 1:10.1.0-6 [188 kB] 101s Get:99 http://ftpmaster.internal/ubuntu plucky/main armhf init armhf 1.68 [6296 B] 101s Get:100 http://ftpmaster.internal/ubuntu plucky/main armhf libbpf1 armhf 1:1.5.0-2 [158 kB] 101s Get:101 http://ftpmaster.internal/ubuntu plucky/main armhf iptables armhf 1.8.11-2ubuntu1 [342 kB] 101s Get:102 http://ftpmaster.internal/ubuntu plucky/main armhf libip4tc2 armhf 1.8.11-2ubuntu1 [21.7 kB] 101s Get:103 http://ftpmaster.internal/ubuntu plucky/main armhf libip6tc2 armhf 1.8.11-2ubuntu1 [22.1 kB] 101s Get:104 http://ftpmaster.internal/ubuntu plucky/main armhf libnftnl11 armhf 1.2.8-1 [53.3 kB] 101s Get:105 http://ftpmaster.internal/ubuntu plucky/main armhf libxtables12 armhf 1.8.11-2ubuntu1 [33.0 kB] 101s Get:106 http://ftpmaster.internal/ubuntu plucky-proposed/main armhf iproute2 armhf 6.13.0-1ubuntu1 [1096 kB] 101s Get:107 http://ftpmaster.internal/ubuntu plucky/main armhf iputils-ping armhf 3:20240905-1ubuntu1 [45.0 kB] 101s Get:108 http://ftpmaster.internal/ubuntu plucky/main armhf login.defs all 1:4.16.0-7ubuntu1 [38.5 kB] 101s Get:109 http://ftpmaster.internal/ubuntu plucky/main armhf login armhf 1:4.16.0-2+really2.40.2-14ubuntu1 [85.0 kB] 101s Get:110 http://ftpmaster.internal/ubuntu plucky/main armhf mawk armhf 1.3.4.20250131-1 [119 kB] 101s Get:111 http://ftpmaster.internal/ubuntu plucky/main armhf netcat-openbsd armhf 1.228-1 [42.4 kB] 101s Get:112 http://ftpmaster.internal/ubuntu plucky/main armhf libpython3.13-minimal armhf 3.13.2-1 [868 kB] 101s Get:113 http://ftpmaster.internal/ubuntu plucky/main armhf python3.13-minimal armhf 3.13.2-1 [2012 kB] 101s Get:114 http://ftpmaster.internal/ubuntu plucky/main armhf python3-cryptography armhf 43.0.0-1 [925 kB] 101s Get:115 http://ftpmaster.internal/ubuntu plucky/main armhf python3-minimal armhf 3.13.1-1~exp2 [27.6 kB] 101s Get:116 http://ftpmaster.internal/ubuntu plucky/main armhf python3 armhf 3.13.1-1~exp2 [23.9 kB] 101s Get:117 http://ftpmaster.internal/ubuntu plucky/main armhf python3-bcrypt armhf 4.2.0-2.1 [239 kB] 101s Get:118 http://ftpmaster.internal/ubuntu plucky/main armhf tzdata all 2024b-6ubuntu1 [197 kB] 101s Get:119 http://ftpmaster.internal/ubuntu plucky/main armhf libffi8 armhf 3.4.7-1 [21.1 kB] 101s Get:120 http://ftpmaster.internal/ubuntu plucky/main armhf libpython3.13-stdlib armhf 3.13.2-1 [1969 kB] 101s Get:121 http://ftpmaster.internal/ubuntu plucky/main armhf python3.13 armhf 3.13.2-1 [734 kB] 101s Get:122 http://ftpmaster.internal/ubuntu plucky/main armhf libpython3-stdlib armhf 3.13.1-1~exp2 [10.2 kB] 101s Get:123 http://ftpmaster.internal/ubuntu plucky/main armhf gir1.2-girepository-2.0 armhf 1.82.0-4 [25.3 kB] 101s Get:124 http://ftpmaster.internal/ubuntu plucky/main armhf gir1.2-glib-2.0 armhf 2.83.3-2 [184 kB] 101s Get:125 http://ftpmaster.internal/ubuntu plucky/main armhf libgirepository-1.0-1 armhf 1.82.0-4 [109 kB] 101s Get:126 http://ftpmaster.internal/ubuntu plucky/main armhf libglib2.0-data all 2.83.3-2 [52.7 kB] 101s Get:127 http://ftpmaster.internal/ubuntu plucky/main armhf libglib2.0-bin armhf 2.83.3-2 [92.7 kB] 101s Get:128 http://ftpmaster.internal/ubuntu plucky/main armhf libglib2.0-0t64 armhf 2.83.3-2 [1452 kB] 102s Get:129 http://ftpmaster.internal/ubuntu plucky/main armhf netplan-generator armhf 1.1.2-2ubuntu1 [60.8 kB] 102s Get:130 http://ftpmaster.internal/ubuntu plucky/main armhf libyaml-0-2 armhf 0.2.5-2 [45.3 kB] 102s Get:131 http://ftpmaster.internal/ubuntu plucky/main armhf python3-netplan armhf 1.1.2-2ubuntu1 [24.2 kB] 102s Get:132 http://ftpmaster.internal/ubuntu plucky/main armhf netplan.io armhf 1.1.2-2ubuntu1 [67.7 kB] 102s Get:133 http://ftpmaster.internal/ubuntu plucky/main armhf libnetplan1 armhf 1.1.2-2ubuntu1 [123 kB] 102s Get:134 http://ftpmaster.internal/ubuntu plucky/main armhf ethtool armhf 1:6.11-1 [222 kB] 102s Get:135 http://ftpmaster.internal/ubuntu plucky/main armhf libsemanage-common all 3.7-2.1 [7198 B] 102s Get:136 http://ftpmaster.internal/ubuntu plucky/main armhf libsemanage2 armhf 3.7-2.1 [85.4 kB] 102s Get:137 http://ftpmaster.internal/ubuntu plucky/main armhf passwd armhf 1:4.16.0-7ubuntu1 [1041 kB] 102s Get:138 http://ftpmaster.internal/ubuntu plucky/main armhf python3-newt armhf 0.52.24-4ubuntu1 [20.1 kB] 102s Get:139 http://ftpmaster.internal/ubuntu plucky/main armhf libnewt0.52 armhf 0.52.24-4ubuntu1 [39.7 kB] 102s Get:140 http://ftpmaster.internal/ubuntu plucky/main armhf whiptail armhf 0.52.24-4ubuntu1 [17.3 kB] 102s Get:141 http://ftpmaster.internal/ubuntu plucky/main armhf dracut-install armhf 106-2ubuntu1 [38.7 kB] 102s Get:142 http://ftpmaster.internal/ubuntu plucky/main armhf initramfs-tools-bin armhf 0.145ubuntu2 [24.5 kB] 102s Get:143 http://ftpmaster.internal/ubuntu plucky/main armhf busybox-initramfs armhf 1:1.37.0-4ubuntu1 [188 kB] 102s Get:144 http://ftpmaster.internal/ubuntu plucky/main armhf python3.12 armhf 3.12.9-1 [671 kB] 102s Get:145 http://ftpmaster.internal/ubuntu plucky/main armhf libpython3.12-stdlib armhf 3.12.9-1 [1946 kB] 102s Get:146 http://ftpmaster.internal/ubuntu plucky/main armhf python3.12-minimal armhf 3.12.9-1 [2012 kB] 102s Get:147 http://ftpmaster.internal/ubuntu plucky/main armhf libpython3.12-minimal armhf 3.12.9-1 [825 kB] 102s Get:148 http://ftpmaster.internal/ubuntu plucky/main armhf cron armhf 3.0pl1-192ubuntu1 [84.2 kB] 102s Get:149 http://ftpmaster.internal/ubuntu plucky/main armhf rsync armhf 3.4.1-0syncable1 [422 kB] 102s Get:150 http://ftpmaster.internal/ubuntu plucky/main armhf python-apt-common all 2.9.8 [21.1 kB] 102s Get:151 http://ftpmaster.internal/ubuntu plucky/main armhf python3-apt armhf 2.9.8 [174 kB] 102s Get:152 http://ftpmaster.internal/ubuntu plucky/main armhf python3-lazr.uri all 1.0.6-5 [13.6 kB] 102s Get:153 http://ftpmaster.internal/ubuntu plucky/main armhf python3-launchpadlib all 2.1.0-1 [126 kB] 102s Get:154 http://ftpmaster.internal/ubuntu plucky/main armhf python3-problem-report all 2.31.0-0ubuntu5 [25.5 kB] 102s Get:155 http://ftpmaster.internal/ubuntu plucky/main armhf python3-apport all 2.31.0-0ubuntu5 [93.1 kB] 102s Get:156 http://ftpmaster.internal/ubuntu plucky/main armhf python3-gi armhf 3.50.0-4 [260 kB] 102s Get:157 http://ftpmaster.internal/ubuntu plucky/main armhf apport-core-dump-handler all 2.31.0-0ubuntu5 [18.4 kB] 102s Get:158 http://ftpmaster.internal/ubuntu plucky/main armhf apport all 2.31.0-0ubuntu5 [83.0 kB] 102s Get:159 http://ftpmaster.internal/ubuntu plucky/main armhf libcom-err2 armhf 1.47.2-1ubuntu1 [25.6 kB] 102s Get:160 http://ftpmaster.internal/ubuntu plucky/main armhf libss2 armhf 1.47.2-1ubuntu1 [15.6 kB] 102s Get:161 http://ftpmaster.internal/ubuntu plucky/main armhf openssl armhf 3.4.0-1ubuntu2 [1159 kB] 102s Get:162 http://ftpmaster.internal/ubuntu plucky/main armhf ca-certificates all 20241223 [165 kB] 102s Get:163 http://ftpmaster.internal/ubuntu plucky/main armhf distro-info armhf 1.13 [19.1 kB] 102s Get:164 http://ftpmaster.internal/ubuntu plucky/main armhf krb5-locales all 1.21.3-4ubuntu1 [14.7 kB] 102s Get:165 http://ftpmaster.internal/ubuntu plucky/main armhf libfribidi0 armhf 1.0.16-1 [24.3 kB] 102s Get:166 http://ftpmaster.internal/ubuntu plucky/main armhf libgssapi-krb5-2 armhf 1.21.3-4ubuntu1 [121 kB] 102s Get:167 http://ftpmaster.internal/ubuntu plucky/main armhf libkrb5-3 armhf 1.21.3-4ubuntu1 [314 kB] 102s Get:168 http://ftpmaster.internal/ubuntu plucky/main armhf libkrb5support0 armhf 1.21.3-4ubuntu1 [31.8 kB] 102s Get:169 http://ftpmaster.internal/ubuntu plucky/main armhf libk5crypto3 armhf 1.21.3-4ubuntu1 [78.6 kB] 102s Get:170 http://ftpmaster.internal/ubuntu plucky/main armhf libicu74 armhf 74.2-1ubuntu6 [10.5 MB] 103s Get:171 http://ftpmaster.internal/ubuntu plucky/main armhf libxml2 armhf 2.12.7+dfsg+really2.9.14-0.2ubuntu3 [599 kB] 103s Get:172 http://ftpmaster.internal/ubuntu plucky/main armhf python3-pygments all 2.18.0+dfsg-2 [835 kB] 103s Get:173 http://ftpmaster.internal/ubuntu plucky/main armhf python3-rich all 13.9.4-1 [190 kB] 103s Get:174 http://ftpmaster.internal/ubuntu plucky/main armhf ucf all 3.0049 [43.3 kB] 103s Get:175 http://ftpmaster.internal/ubuntu plucky/main armhf rsyslog armhf 8.2412.0-1ubuntu1 [470 kB] 103s Get:176 http://ftpmaster.internal/ubuntu plucky/main armhf apparmor armhf 4.1.0~beta1-0ubuntu5 [589 kB] 103s Get:177 http://ftpmaster.internal/ubuntu plucky/main armhf bash-completion all 1:2.16.0-7 [214 kB] 103s Get:178 http://ftpmaster.internal/ubuntu plucky/main armhf bind9-dnsutils armhf 1:9.20.0-2ubuntu4 [155 kB] 103s Get:179 http://ftpmaster.internal/ubuntu plucky/main armhf bind9-host armhf 1:9.20.0-2ubuntu4 [46.2 kB] 103s Get:180 http://ftpmaster.internal/ubuntu plucky/main armhf bind9-libs armhf 1:9.20.0-2ubuntu4 [1176 kB] 103s Get:181 http://ftpmaster.internal/ubuntu plucky/main armhf libedit2 armhf 3.1-20250104-1 [79.3 kB] 103s Get:182 http://ftpmaster.internal/ubuntu plucky/main armhf busybox-static armhf 1:1.37.0-4ubuntu1 [857 kB] 103s Get:183 http://ftpmaster.internal/ubuntu plucky/main armhf cron-daemon-common all 3.0pl1-192ubuntu1 [14.5 kB] 103s Get:184 http://ftpmaster.internal/ubuntu plucky/main armhf libdevmapper1.02.1 armhf 2:1.02.201-1ubuntu1 [137 kB] 103s Get:185 http://ftpmaster.internal/ubuntu plucky/main armhf dmsetup armhf 2:1.02.201-1ubuntu1 [80.4 kB] 103s Get:186 http://ftpmaster.internal/ubuntu plucky/main armhf ed armhf 1.21-1 [52.8 kB] 103s Get:187 http://ftpmaster.internal/ubuntu plucky/main armhf gettext-base armhf 0.23.1-1 [43.3 kB] 103s Get:188 http://ftpmaster.internal/ubuntu plucky/main armhf groff-base armhf 1.23.0-7 [949 kB] 103s Get:189 http://ftpmaster.internal/ubuntu plucky/main armhf libibverbs1 armhf 55.0-1ubuntu1 [58.5 kB] 103s Get:190 http://ftpmaster.internal/ubuntu plucky/main armhf ibverbs-providers armhf 55.0-1ubuntu1 [27.6 kB] 103s Get:191 http://ftpmaster.internal/ubuntu plucky/main armhf iputils-tracepath armhf 3:20240905-1ubuntu1 [13.3 kB] 103s Get:192 http://ftpmaster.internal/ubuntu plucky/main armhf nftables armhf 1.1.1-1build1 [70.8 kB] 103s Get:193 http://ftpmaster.internal/ubuntu plucky/main armhf libnftables1 armhf 1.1.1-1build1 [321 kB] 103s Get:194 http://ftpmaster.internal/ubuntu plucky/main armhf libpcap0.8t64 armhf 1.10.5-2ubuntu1 [140 kB] 103s Get:195 http://ftpmaster.internal/ubuntu plucky/main armhf libpng16-16t64 armhf 1.6.46-4 [171 kB] 103s Get:196 http://ftpmaster.internal/ubuntu plucky/main armhf libtraceevent1-plugin armhf 1:1.8.4-2 [19.0 kB] 103s Get:197 http://ftpmaster.internal/ubuntu plucky/main armhf libtraceevent1 armhf 1:1.8.4-2 [53.8 kB] 103s Get:198 http://ftpmaster.internal/ubuntu plucky/main armhf libusb-1.0-0 armhf 2:1.0.27-2 [49.5 kB] 103s Get:199 http://ftpmaster.internal/ubuntu plucky/main armhf libxdmcp6 armhf 1:1.1.5-1 [9060 B] 103s Get:200 http://ftpmaster.internal/ubuntu plucky/main armhf libxkbcommon0 armhf 1.7.0-2 [113 kB] 103s Get:201 http://ftpmaster.internal/ubuntu plucky/main armhf lshw armhf 02.19.git.2021.06.19.996aaad9c7-2.1ubuntu1 [311 kB] 103s Get:202 http://ftpmaster.internal/ubuntu plucky/main armhf nano armhf 8.3-1 [277 kB] 103s Get:203 http://ftpmaster.internal/ubuntu plucky/main armhf pci.ids all 0.0~2025.02.05-1 [284 kB] 104s Get:204 http://ftpmaster.internal/ubuntu plucky/main armhf powermgmt-base all 1.38 [7378 B] 104s Get:205 http://ftpmaster.internal/ubuntu plucky/main armhf publicsuffix all 20250108.1153-0.1 [134 kB] 104s Get:206 http://ftpmaster.internal/ubuntu plucky/main armhf python3-distro-info all 1.13 [7798 B] 104s Get:207 http://ftpmaster.internal/ubuntu plucky/main armhf python3.13-gdbm armhf 3.13.2-1 [30.2 kB] 104s Get:208 http://ftpmaster.internal/ubuntu plucky/main armhf python3.12-gdbm armhf 3.12.9-1 [29.3 kB] 104s Get:209 http://ftpmaster.internal/ubuntu plucky/main armhf python3-gdbm armhf 3.13.1-1 [8668 B] 104s Get:210 http://ftpmaster.internal/ubuntu plucky/main armhf ubuntu-standard armhf 1.547 [11.4 kB] 104s Get:211 http://ftpmaster.internal/ubuntu plucky/main armhf ufw all 0.36.2-9 [170 kB] 104s Get:212 http://ftpmaster.internal/ubuntu plucky/main armhf usb.ids all 2025.01.14-1 [223 kB] 104s Get:213 http://ftpmaster.internal/ubuntu plucky/main armhf xauth armhf 1:1.1.2-1.1 [23.0 kB] 104s Get:214 http://ftpmaster.internal/ubuntu plucky/main armhf libcurl3t64-gnutls armhf 8.12.0+git20250209.89ed161+ds-1ubuntu1 [330 kB] 104s Get:215 http://ftpmaster.internal/ubuntu plucky/main armhf libappstream5 armhf 1.0.4-1 [211 kB] 104s Get:216 http://ftpmaster.internal/ubuntu plucky/main armhf appstream armhf 1.0.4-1 [67.3 kB] 104s Get:217 http://ftpmaster.internal/ubuntu plucky/main armhf libctf0 armhf 2.44-1ubuntu1 [74.4 kB] 104s Get:218 http://ftpmaster.internal/ubuntu plucky/main armhf libctf-nobfd0 armhf 2.44-1ubuntu1 [77.6 kB] 104s Get:219 http://ftpmaster.internal/ubuntu plucky/main armhf binutils-arm-linux-gnueabihf armhf 2.44-1ubuntu1 [995 kB] 104s Get:220 http://ftpmaster.internal/ubuntu plucky/main armhf libbinutils armhf 2.44-1ubuntu1 [405 kB] 104s Get:221 http://ftpmaster.internal/ubuntu plucky/main armhf binutils armhf 2.44-1ubuntu1 [3238 B] 104s Get:222 http://ftpmaster.internal/ubuntu plucky/main armhf binutils-common armhf 2.44-1ubuntu1 [216 kB] 104s Get:223 http://ftpmaster.internal/ubuntu plucky/main armhf libsframe1 armhf 2.44-1ubuntu1 [12.5 kB] 104s Get:224 http://ftpmaster.internal/ubuntu plucky/main armhf btrfs-progs armhf 6.12-1build1 [884 kB] 104s Get:225 http://ftpmaster.internal/ubuntu plucky/main armhf python3-jinja2 all 3.1.5-2 [109 kB] 104s Get:226 http://ftpmaster.internal/ubuntu plucky/main armhf python3-json-pointer all 2.4-3 [8444 B] 104s Get:227 http://ftpmaster.internal/ubuntu plucky/main armhf python3-jsonpatch all 1.32-5 [12.3 kB] 104s Get:228 http://ftpmaster.internal/ubuntu plucky/main armhf python3-attr all 25.1.0-1 [50.4 kB] 104s Get:229 http://ftpmaster.internal/ubuntu plucky/main armhf python3-referencing all 0.35.1-2ubuntu1 [21.9 kB] 104s Get:230 http://ftpmaster.internal/ubuntu plucky/main armhf python3-jsonschema all 4.19.2-6ubuntu1 [65.5 kB] 104s Get:231 http://ftpmaster.internal/ubuntu plucky/main armhf python3-jwt all 2.10.1-2 [21.0 kB] 104s Get:232 http://ftpmaster.internal/ubuntu plucky/main armhf python3-oauthlib all 3.2.2-3 [89.9 kB] 104s Get:233 http://ftpmaster.internal/ubuntu plucky/main armhf cloud-init-base all 25.1~3geb1965a4-0ubuntu1 [615 kB] 104s Get:234 http://ftpmaster.internal/ubuntu plucky/main armhf curl armhf 8.12.0+git20250209.89ed161+ds-1ubuntu1 [247 kB] 104s Get:235 http://ftpmaster.internal/ubuntu plucky/main armhf libcurl4t64 armhf 8.12.0+git20250209.89ed161+ds-1ubuntu1 [335 kB] 104s Get:236 http://ftpmaster.internal/ubuntu plucky/main armhf dpkg-dev all 1.22.11ubuntu4 [1088 kB] 104s Get:237 http://ftpmaster.internal/ubuntu plucky/main armhf libdpkg-perl all 1.22.11ubuntu4 [279 kB] 104s Get:238 http://ftpmaster.internal/ubuntu plucky/main armhf make armhf 4.4.1-1 [180 kB] 104s Get:239 http://ftpmaster.internal/ubuntu plucky/main armhf libarchive13t64 armhf 3.7.7-0ubuntu1 [335 kB] 104s Get:240 http://ftpmaster.internal/ubuntu plucky/main armhf libjson-glib-1.0-common all 1.10.6+ds-1 [5636 B] 104s Get:241 http://ftpmaster.internal/ubuntu plucky/main armhf libjson-glib-1.0-0 armhf 1.10.6+ds-1 [59.5 kB] 104s Get:242 http://ftpmaster.internal/ubuntu plucky/main armhf fwupd armhf 2.0.5-1 [5151 kB] 104s Get:243 http://ftpmaster.internal/ubuntu plucky/main armhf libfwupd3 armhf 2.0.5-1 [125 kB] 104s Get:244 http://ftpmaster.internal/ubuntu plucky/main armhf polkitd armhf 126-2 [92.5 kB] 104s Get:245 http://ftpmaster.internal/ubuntu plucky/main armhf libpolkit-agent-1-0 armhf 126-2 [15.1 kB] 104s Get:246 http://ftpmaster.internal/ubuntu plucky/main armhf libpolkit-gobject-1-0 armhf 126-2 [45.0 kB] 104s Get:247 http://ftpmaster.internal/ubuntu plucky/main armhf libprotobuf-c1 armhf 1.5.1-1ubuntu1 [18.1 kB] 104s Get:248 http://ftpmaster.internal/ubuntu plucky/main armhf libqmi-proxy armhf 1.35.6-1 [5878 B] 104s Get:249 http://ftpmaster.internal/ubuntu plucky/main armhf libqmi-glib5 armhf 1.35.6-1 [928 kB] 104s Get:250 http://ftpmaster.internal/ubuntu plucky/main armhf gnupg-l10n all 2.4.4-2ubuntu22 [66.4 kB] 104s Get:251 http://ftpmaster.internal/ubuntu plucky/main armhf htop armhf 3.3.0-5 [140 kB] 104s Get:252 http://ftpmaster.internal/ubuntu plucky/main armhf libblockdev-utils3 armhf 3.3.0-1 [17.5 kB] 104s Get:253 http://ftpmaster.internal/ubuntu plucky/main armhf libnspr4 armhf 2:4.36-1ubuntu1 [94.5 kB] 104s Get:254 http://ftpmaster.internal/ubuntu plucky/main armhf libnss3 armhf 2:3.106-1ubuntu1 [1321 kB] 104s Get:255 http://ftpmaster.internal/ubuntu plucky/main armhf libgpgme11t64 armhf 1.24.1-4ubuntu1 [125 kB] 104s Get:256 http://ftpmaster.internal/ubuntu plucky/main armhf libvolume-key1 armhf 0.3.12-9 [39.1 kB] 104s Get:257 http://ftpmaster.internal/ubuntu plucky/main armhf libblockdev-crypto3 armhf 3.3.0-1 [22.4 kB] 104s Get:258 http://ftpmaster.internal/ubuntu plucky/main armhf libblockdev-fs3 armhf 3.3.0-1 [34.5 kB] 104s Get:259 http://ftpmaster.internal/ubuntu plucky/main armhf libblockdev-loop3 armhf 3.3.0-1 [6594 B] 104s Get:260 http://ftpmaster.internal/ubuntu plucky/main armhf libblockdev-mdraid3 armhf 3.3.0-1 [13.4 kB] 104s Get:261 http://ftpmaster.internal/ubuntu plucky/main armhf libnvme1t64 armhf 1.11.1-1build1 [73.6 kB] 104s Get:262 http://ftpmaster.internal/ubuntu plucky/main armhf libblockdev-nvme3 armhf 3.3.0-1 [17.7 kB] 104s Get:263 http://ftpmaster.internal/ubuntu plucky/main armhf libblockdev-part3 armhf 3.3.0-1 [16.6 kB] 105s Get:264 http://ftpmaster.internal/ubuntu plucky/main armhf libblockdev-swap3 armhf 3.3.0-1 [9010 B] 105s Get:265 http://ftpmaster.internal/ubuntu plucky/main armhf libblockdev3 armhf 3.3.0-1 [44.4 kB] 105s Get:266 http://ftpmaster.internal/ubuntu plucky/main armhf libftdi1-2 armhf 1.5-8 [26.3 kB] 105s Get:267 http://ftpmaster.internal/ubuntu plucky/main armhf libgstreamer1.0-0 armhf 1.25.50-1 [1164 kB] 105s Get:268 http://ftpmaster.internal/ubuntu plucky/main armhf libgudev-1.0-0 armhf 1:238-6 [13.7 kB] 105s Get:269 http://ftpmaster.internal/ubuntu plucky/main armhf libicu76 armhf 76.1-1ubuntu2 [10.8 MB] 105s Get:270 http://ftpmaster.internal/ubuntu plucky/main armhf libsasl2-modules armhf 2.1.28+dfsg1-8build1 [62.7 kB] 105s Get:271 http://ftpmaster.internal/ubuntu plucky/main armhf udisks2 armhf 2.10.1-11ubuntu2 [278 kB] 105s Get:272 http://ftpmaster.internal/ubuntu plucky/main armhf libudisks2-0 armhf 2.10.1-11ubuntu2 [142 kB] 105s Get:273 http://ftpmaster.internal/ubuntu plucky/main armhf libwrap0 armhf 7.6.q-35 [45.6 kB] 105s Get:274 http://ftpmaster.internal/ubuntu plucky/main armhf linux-headers-6.12.0-15 all 6.12.0-15.15 [14.1 MB] 105s Get:275 http://ftpmaster.internal/ubuntu plucky/main armhf linux-headers-6.12.0-15-generic armhf 6.12.0-15.15 [1414 kB] 105s Get:276 http://ftpmaster.internal/ubuntu plucky/main armhf linux-headers-generic armhf 6.12.0-15.15+1 [10.8 kB] 105s Get:277 http://ftpmaster.internal/ubuntu plucky/main armhf pollinate all 4.33-4ubuntu2 [12.4 kB] 105s Get:278 http://ftpmaster.internal/ubuntu plucky/main armhf python3-babel all 2.17.0-1 [101 kB] 105s Get:279 http://ftpmaster.internal/ubuntu plucky/main armhf python-babel-localedata all 2.17.0-1 [6678 kB] 106s Get:280 http://ftpmaster.internal/ubuntu plucky/main armhf python3-certifi all 2025.1.31+ds-1 [9816 B] 106s Get:281 http://ftpmaster.internal/ubuntu plucky/main armhf python3-chardet all 5.2.0+dfsg-2 [116 kB] 106s Get:282 http://ftpmaster.internal/ubuntu plucky/main armhf python3-idna all 3.10-1 [47.4 kB] 106s Get:283 http://ftpmaster.internal/ubuntu plucky/main armhf python3-more-itertools all 10.6.0-1 [57.7 kB] 106s Get:284 http://ftpmaster.internal/ubuntu plucky/main armhf python3-openssl all 25.0.0-1 [46.1 kB] 106s Get:285 http://ftpmaster.internal/ubuntu plucky/main armhf python3-pkg-resources all 75.6.0-1 [144 kB] 106s Get:286 http://ftpmaster.internal/ubuntu plucky/main armhf python3-setuptools all 75.6.0-1 [645 kB] 106s Get:287 http://ftpmaster.internal/ubuntu plucky/main armhf software-properties-common all 0.108 [16.5 kB] 106s Get:288 http://ftpmaster.internal/ubuntu plucky/main armhf python3-software-properties all 0.108 [30.9 kB] 106s Get:289 http://ftpmaster.internal/ubuntu plucky/main armhf python3-urllib3 all 2.3.0-1 [94.0 kB] 106s Get:290 http://ftpmaster.internal/ubuntu plucky/main armhf python3-wadllib all 2.0.0-2 [36.2 kB] 106s Get:291 http://ftpmaster.internal/ubuntu plucky/main armhf unattended-upgrades all 2.12ubuntu2 [55.0 kB] 106s Get:292 http://ftpmaster.internal/ubuntu plucky/main armhf xfsprogs armhf 6.8.0-2.2ubuntu3 [893 kB] 106s Get:293 http://ftpmaster.internal/ubuntu plucky/main armhf zstd armhf 1.5.6+dfsg-2 [690 kB] 106s Get:294 http://ftpmaster.internal/ubuntu plucky/main armhf cloud-init all 25.1~3geb1965a4-0ubuntu1 [2102 B] 106s Get:295 http://ftpmaster.internal/ubuntu plucky/main armhf kpartx armhf 0.9.9-1ubuntu4 [35.0 kB] 106s Get:296 http://ftpmaster.internal/ubuntu plucky/main armhf multipath-tools armhf 0.9.9-1ubuntu4 [294 kB] 107s Preconfiguring packages ... 108s Fetched 132 MB in 7s (17.7 MB/s) 108s (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 ... 59970 files and directories currently installed.) 108s Preparing to unpack .../bash_5.2.37-1ubuntu1_armhf.deb ... 108s Unpacking bash (5.2.37-1ubuntu1) over (5.2.32-1ubuntu2) ... 108s Setting up bash (5.2.37-1ubuntu1) ... 108s update-alternatives: using /usr/share/man/man7/bash-builtins.7.gz to provide /usr/share/man/man7/builtins.7.gz (builtins.7.gz) in auto mode 108s (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 ... 59970 files and directories currently installed.) 108s Preparing to unpack .../bsdutils_1%3a2.40.2-14ubuntu1_armhf.deb ... 108s Unpacking bsdutils (1:2.40.2-14ubuntu1) over (1:2.40.2-1ubuntu1) ... 108s Setting up bsdutils (1:2.40.2-14ubuntu1) ... 108s (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 ... 59970 files and directories currently installed.) 108s Preparing to unpack .../coreutils_9.5-1ubuntu1_armhf.deb ... 108s Unpacking coreutils (9.5-1ubuntu1) over (9.4-3.1ubuntu1) ... 109s Setting up coreutils (9.5-1ubuntu1) ... 109s (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 ... 59970 files and directories currently installed.) 109s Preparing to unpack .../dash_0.5.12-12ubuntu1_armhf.deb ... 109s Unpacking dash (0.5.12-12ubuntu1) over (0.5.12-9ubuntu1) ... 109s Setting up dash (0.5.12-12ubuntu1) ... 109s (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 ... 59970 files and directories currently installed.) 109s Preparing to unpack .../diffutils_1%3a3.10-2_armhf.deb ... 109s Unpacking diffutils (1:3.10-2) over (1:3.10-1build1) ... 109s Setting up diffutils (1:3.10-2) ... 109s (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 ... 59970 files and directories currently installed.) 109s Preparing to unpack .../locales_2.41-1ubuntu1_all.deb ... 109s Unpacking locales (2.41-1ubuntu1) over (2.40-1ubuntu3) ... 109s Preparing to unpack .../libc6_2.41-1ubuntu1_armhf.deb ... 109s Checking for services that may need to be restarted... 109s Checking init scripts... 109s Checking for services that may need to be restarted... 109s Checking init scripts... 109s Stopping some services possibly affected by the upgrade (will be restarted later): 109s cron: stopping...done. 109s 109s Unpacking libc6:armhf (2.41-1ubuntu1) over (2.40-1ubuntu3) ... 110s Setting up libc6:armhf (2.41-1ubuntu1) ... 110s Checking for services that may need to be restarted... 110s Checking init scripts... 110s Restarting services possibly affected by the upgrade: 110s cron: restarting...done. 110s 110s Services restarted successfully. 110s (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 ... 59970 files and directories currently installed.) 110s Preparing to unpack .../libc-bin_2.41-1ubuntu1_armhf.deb ... 110s Unpacking libc-bin (2.41-1ubuntu1) over (2.40-1ubuntu3) ... 110s Setting up libc-bin (2.41-1ubuntu1) ... 110s (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 ... 59970 files and directories currently installed.) 110s Preparing to unpack .../libatomic1_14.2.0-17ubuntu1_armhf.deb ... 110s Unpacking libatomic1:armhf (14.2.0-17ubuntu1) over (14.2.0-8ubuntu1) ... 110s Preparing to unpack .../gcc-14-base_14.2.0-17ubuntu1_armhf.deb ... 110s Unpacking gcc-14-base:armhf (14.2.0-17ubuntu1) over (14.2.0-8ubuntu1) ... 110s Setting up gcc-14-base:armhf (14.2.0-17ubuntu1) ... 110s (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 ... 59970 files and directories currently installed.) 110s Preparing to unpack .../libgcc-s1_14.2.0-17ubuntu1_armhf.deb ... 110s Unpacking libgcc-s1:armhf (14.2.0-17ubuntu1) over (14.2.0-8ubuntu1) ... 110s Setting up libgcc-s1:armhf (14.2.0-17ubuntu1) ... 110s (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 ... 59970 files and directories currently installed.) 110s Preparing to unpack .../libstdc++6_14.2.0-17ubuntu1_armhf.deb ... 110s Unpacking libstdc++6:armhf (14.2.0-17ubuntu1) over (14.2.0-8ubuntu1) ... 110s Setting up libstdc++6:armhf (14.2.0-17ubuntu1) ... 110s (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 ... 59970 files and directories currently installed.) 110s Preparing to unpack .../liblz4-1_1.10.0-3_armhf.deb ... 110s Unpacking liblz4-1:armhf (1.10.0-3) over (1.9.4-3) ... 111s Setting up liblz4-1:armhf (1.10.0-3) ... 111s (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 ... 59970 files and directories currently installed.) 111s Preparing to unpack .../libssl3t64_3.4.0-1ubuntu2_armhf.deb ... 111s Unpacking libssl3t64:armhf (3.4.0-1ubuntu2) over (3.3.1-2ubuntu2) ... 111s Selecting previously unselected package openssl-provider-legacy. 111s Preparing to unpack .../openssl-provider-legacy_3.4.0-1ubuntu2_armhf.deb ... 111s Unpacking openssl-provider-legacy (3.4.0-1ubuntu2) ... 111s Setting up libssl3t64:armhf (3.4.0-1ubuntu2) ... 111s Setting up openssl-provider-legacy (3.4.0-1ubuntu2) ... 111s (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 ... 59973 files and directories currently installed.) 111s Preparing to unpack .../libzstd1_1.5.6+dfsg-2_armhf.deb ... 111s Unpacking libzstd1:armhf (1.5.6+dfsg-2) over (1.5.6+dfsg-1) ... 111s Setting up libzstd1:armhf (1.5.6+dfsg-2) ... 111s (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 ... 59973 files and directories currently installed.) 111s Preparing to unpack .../0-systemd-timesyncd_257.2-3ubuntu1_armhf.deb ... 111s Unpacking systemd-timesyncd (257.2-3ubuntu1) over (256.5-2ubuntu4) ... 111s Preparing to unpack .../1-dbus-session-bus-common_1.16.0-1ubuntu1_all.deb ... 111s Unpacking dbus-session-bus-common (1.16.0-1ubuntu1) over (1.14.10-4ubuntu5) ... 111s Preparing to unpack .../2-systemd-sysv_257.2-3ubuntu1_armhf.deb ... 111s Unpacking systemd-sysv (257.2-3ubuntu1) over (256.5-2ubuntu4) ... 111s Preparing to unpack .../3-libpam-systemd_257.2-3ubuntu1_armhf.deb ... 111s Unpacking libpam-systemd:armhf (257.2-3ubuntu1) over (256.5-2ubuntu4) ... 111s Preparing to unpack .../4-dbus-user-session_1.16.0-1ubuntu1_armhf.deb ... 111s Unpacking dbus-user-session (1.16.0-1ubuntu1) over (1.14.10-4ubuntu5) ... 111s Preparing to unpack .../5-libapparmor1_4.1.0~beta1-0ubuntu5_armhf.deb ... 111s Unpacking libapparmor1:armhf (4.1.0~beta1-0ubuntu5) over (4.1.0~beta1-0ubuntu4) ... 111s Preparing to unpack .../6-libcap-ng0_0.8.5-4_armhf.deb ... 111s Unpacking libcap-ng0:armhf (0.8.5-4) over (0.8.5-3build1) ... 111s Setting up libcap-ng0:armhf (0.8.5-4) ... 111s (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 ... 59974 files and directories currently installed.) 111s Preparing to unpack .../libselinux1_3.7-3ubuntu2_armhf.deb ... 111s Unpacking libselinux1:armhf (3.7-3ubuntu2) over (3.7-3ubuntu1) ... 111s Setting up libselinux1:armhf (3.7-3ubuntu2) ... 111s (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 ... 59974 files and directories currently installed.) 111s Preparing to unpack .../0-dbus-system-bus-common_1.16.0-1ubuntu1_all.deb ... 111s Unpacking dbus-system-bus-common (1.16.0-1ubuntu1) over (1.14.10-4ubuntu5) ... 111s Preparing to unpack .../1-dbus-bin_1.16.0-1ubuntu1_armhf.deb ... 111s Unpacking dbus-bin (1.16.0-1ubuntu1) over (1.14.10-4ubuntu5) ... 111s Preparing to unpack .../2-dbus_1.16.0-1ubuntu1_armhf.deb ... 111s Unpacking dbus (1.16.0-1ubuntu1) over (1.14.10-4ubuntu5) ... 112s Preparing to unpack .../3-dbus-daemon_1.16.0-1ubuntu1_armhf.deb ... 112s Unpacking dbus-daemon (1.16.0-1ubuntu1) over (1.14.10-4ubuntu5) ... 112s Preparing to unpack .../4-libdbus-1-3_1.16.0-1ubuntu1_armhf.deb ... 112s Unpacking libdbus-1-3:armhf (1.16.0-1ubuntu1) over (1.14.10-4ubuntu5) ... 112s Preparing to unpack .../5-systemd-resolved_257.2-3ubuntu1_armhf.deb ... 112s Unpacking systemd-resolved (257.2-3ubuntu1) over (256.5-2ubuntu4) ... 112s Preparing to unpack .../6-systemd-cryptsetup_257.2-3ubuntu1_armhf.deb ... 112s Unpacking systemd-cryptsetup (257.2-3ubuntu1) over (256.5-2ubuntu4) ... 112s Preparing to unpack .../7-libncurses6_6.5+20250125-2_armhf.deb ... 112s Unpacking libncurses6:armhf (6.5+20250125-2) over (6.5-2) ... 112s Preparing to unpack .../8-libncursesw6_6.5+20250125-2_armhf.deb ... 112s Unpacking libncursesw6:armhf (6.5+20250125-2) over (6.5-2) ... 112s Preparing to unpack .../9-libtinfo6_6.5+20250125-2_armhf.deb ... 112s Unpacking libtinfo6:armhf (6.5+20250125-2) over (6.5-2) ... 112s Setting up libtinfo6:armhf (6.5+20250125-2) ... 112s (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 ... 59974 files and directories currently installed.) 112s Preparing to unpack .../bsdextrautils_2.40.2-14ubuntu1_armhf.deb ... 112s Unpacking bsdextrautils (2.40.2-14ubuntu1) over (2.40.2-1ubuntu1) ... 112s Preparing to unpack .../eject_2.40.2-14ubuntu1_armhf.deb ... 112s Unpacking eject (2.40.2-14ubuntu1) over (2.40.2-1ubuntu1) ... 112s Preparing to unpack .../fdisk_2.40.2-14ubuntu1_armhf.deb ... 112s Unpacking fdisk (2.40.2-14ubuntu1) over (2.40.2-1ubuntu1) ... 112s Preparing to unpack .../libblkid1_2.40.2-14ubuntu1_armhf.deb ... 112s Unpacking libblkid1:armhf (2.40.2-14ubuntu1) over (2.40.2-1ubuntu1) ... 112s Setting up libblkid1:armhf (2.40.2-14ubuntu1) ... 112s (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 ... 59970 files and directories currently installed.) 112s Preparing to unpack .../libmount1_2.40.2-14ubuntu1_armhf.deb ... 112s Unpacking libmount1:armhf (2.40.2-14ubuntu1) over (2.40.2-1ubuntu1) ... 112s Setting up libmount1:armhf (2.40.2-14ubuntu1) ... 112s (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 ... 59970 files and directories currently installed.) 112s Preparing to unpack .../libsmartcols1_2.40.2-14ubuntu1_armhf.deb ... 112s Unpacking libsmartcols1:armhf (2.40.2-14ubuntu1) over (2.40.2-1ubuntu1) ... 112s Setting up libsmartcols1:armhf (2.40.2-14ubuntu1) ... 112s (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 ... 59970 files and directories currently installed.) 112s Preparing to unpack .../libuuid1_2.40.2-14ubuntu1_armhf.deb ... 112s Unpacking libuuid1:armhf (2.40.2-14ubuntu1) over (2.40.2-1ubuntu1) ... 112s Setting up libuuid1:armhf (2.40.2-14ubuntu1) ... 112s (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 ... 59970 files and directories currently installed.) 112s Preparing to unpack .../util-linux_2.40.2-14ubuntu1_armhf.deb ... 112s Unpacking util-linux (2.40.2-14ubuntu1) over (2.40.2-1ubuntu1) ... 113s Setting up util-linux (2.40.2-14ubuntu1) ... 113s fstrim.service is a disabled or a static unit not running, not starting it. 113s (Reading database ... (Reading database ... 5% (Reading database ... 10% (Reading database ... 15% (Reading database ... 20% (Reading database ... 25% (Reading database ... 30% (Reading database ... 35% (Reading database ... 40% (Reading database ... 45% (Reading database ... 50% (Reading database ... 55% (Reading database ... 60% (Reading database ... 65% (Reading database ... 70% (Reading database ... 75% (Reading database ... 80% (Reading database ... 85% (Reading database ... 90% (Reading database ... 95% (Reading database ... 100% (Reading database ... 59963 files and directories currently installed.) 113s Preparing to unpack .../0-uuid-runtime_2.40.2-14ubuntu1_armhf.deb ... 113s Unpacking uuid-runtime (2.40.2-14ubuntu1) over (2.40.2-1ubuntu1) ... 113s Preparing to unpack .../1-libfdisk1_2.40.2-14ubuntu1_armhf.deb ... 113s Unpacking libfdisk1:armhf (2.40.2-14ubuntu1) over (2.40.2-1ubuntu1) ... 113s Preparing to unpack .../2-mount_2.40.2-14ubuntu1_armhf.deb ... 113s Unpacking mount (2.40.2-14ubuntu1) over (2.40.2-1ubuntu1) ... 114s Preparing to unpack .../3-readline-common_8.2-6_all.deb ... 114s Unpacking readline-common (8.2-6) over (8.2-5) ... 114s Preparing to unpack .../4-libreadline8t64_8.2-6_armhf.deb ... 114s Leaving 'diversion of /lib/arm-linux-gnueabihf/libhistory.so.8 to /lib/arm-linux-gnueabihf/libhistory.so.8.usr-is-merged by libreadline8t64' 114s Leaving 'diversion of /lib/arm-linux-gnueabihf/libhistory.so.8.2 to /lib/arm-linux-gnueabihf/libhistory.so.8.2.usr-is-merged by libreadline8t64' 114s Leaving 'diversion of /lib/arm-linux-gnueabihf/libreadline.so.8 to /lib/arm-linux-gnueabihf/libreadline.so.8.usr-is-merged by libreadline8t64' 114s Leaving 'diversion of /lib/arm-linux-gnueabihf/libreadline.so.8.2 to /lib/arm-linux-gnueabihf/libreadline.so.8.2.usr-is-merged by libreadline8t64' 114s Unpacking libreadline8t64:armhf (8.2-6) over (8.2-5) ... 114s Preparing to unpack .../5-libcrypt1_1%3a4.4.38-1_armhf.deb ... 114s Unpacking libcrypt1:armhf (1:4.4.38-1) over (1:4.4.36-5) ... 114s Setting up libcrypt1:armhf (1:4.4.38-1) ... 114s (Reading database ... (Reading database ... 5% (Reading database ... 10% (Reading database ... 15% (Reading database ... 20% (Reading database ... 25% (Reading database ... 30% (Reading database ... 35% (Reading database ... 40% (Reading database ... 45% (Reading database ... 50% (Reading database ... 55% (Reading database ... 60% (Reading database ... 65% (Reading database ... 70% (Reading database ... 75% (Reading database ... 80% (Reading database ... 85% (Reading database ... 90% (Reading database ... 95% (Reading database ... 100% (Reading database ... 59963 files and directories currently installed.) 114s Preparing to unpack .../libsystemd-shared_257.2-3ubuntu1_armhf.deb ... 114s Unpacking libsystemd-shared:armhf (257.2-3ubuntu1) over (256.5-2ubuntu4) ... 114s Setting up libsystemd-shared:armhf (257.2-3ubuntu1) ... 114s (Reading database ... (Reading database ... 5% (Reading database ... 10% (Reading database ... 15% (Reading database ... 20% (Reading database ... 25% (Reading database ... 30% (Reading database ... 35% (Reading database ... 40% (Reading database ... 45% (Reading database ... 50% (Reading database ... 55% (Reading database ... 60% (Reading database ... 65% (Reading database ... 70% (Reading database ... 75% (Reading database ... 80% (Reading database ... 85% (Reading database ... 90% (Reading database ... 95% (Reading database ... 100% (Reading database ... 59963 files and directories currently installed.) 114s Preparing to unpack .../systemd_257.2-3ubuntu1_armhf.deb ... 114s Unpacking systemd (257.2-3ubuntu1) over (256.5-2ubuntu4) ... 114s Preparing to unpack .../udev_257.2-3ubuntu1_armhf.deb ... 114s Unpacking udev (257.2-3ubuntu1) over (256.5-2ubuntu4) ... 114s Preparing to unpack .../libnss-systemd_257.2-3ubuntu1_armhf.deb ... 114s Unpacking libnss-systemd:armhf (257.2-3ubuntu1) over (256.5-2ubuntu4) ... 114s Preparing to unpack .../libudev1_257.2-3ubuntu1_armhf.deb ... 114s Unpacking libudev1:armhf (257.2-3ubuntu1) over (256.5-2ubuntu4) ... 114s Setting up libudev1:armhf (257.2-3ubuntu1) ... 114s (Reading database ... (Reading database ... 5% (Reading database ... 10% (Reading database ... 15% (Reading database ... 20% (Reading database ... 25% (Reading database ... 30% (Reading database ... 35% (Reading database ... 40% (Reading database ... 45% (Reading database ... 50% (Reading database ... 55% (Reading database ... 60% (Reading database ... 65% (Reading database ... 70% (Reading database ... 75% (Reading database ... 80% (Reading database ... 85% (Reading database ... 90% (Reading database ... 95% (Reading database ... 100% (Reading database ... 59957 files and directories currently installed.) 114s Preparing to unpack .../libsystemd0_257.2-3ubuntu1_armhf.deb ... 114s Unpacking libsystemd0:armhf (257.2-3ubuntu1) over (256.5-2ubuntu4) ... 115s Setting up libsystemd0:armhf (257.2-3ubuntu1) ... 115s (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 ... 59957 files and directories currently installed.) 115s Preparing to unpack .../libapt-pkg6.0t64_2.9.28_armhf.deb ... 115s Unpacking libapt-pkg6.0t64:armhf (2.9.28) over (2.9.14ubuntu1) ... 115s Setting up libapt-pkg6.0t64:armhf (2.9.28) ... 115s (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 ... 59957 files and directories currently installed.) 115s Preparing to unpack .../tar_1.35+dfsg-3.1_armhf.deb ... 115s Unpacking tar (1.35+dfsg-3.1) over (1.35+dfsg-3build1) ... 115s Setting up tar (1.35+dfsg-3.1) ... 115s (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 ... 59957 files and directories currently installed.) 115s Preparing to unpack .../dpkg_1.22.11ubuntu4_armhf.deb ... 115s Unpacking dpkg (1.22.11ubuntu4) over (1.22.11ubuntu3) ... 115s Setting up dpkg (1.22.11ubuntu4) ... 115s (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 ... 59957 files and directories currently installed.) 115s Preparing to unpack .../gzip_1.13-1ubuntu2_armhf.deb ... 115s Unpacking gzip (1.13-1ubuntu2) over (1.12-1.1ubuntu1) ... 115s Setting up gzip (1.13-1ubuntu2) ... 116s (Reading database ... (Reading database ... 5% (Reading database ... 10% (Reading database ... 15% (Reading database ... 20% (Reading database ... 25% (Reading database ... 30% (Reading database ... 35% (Reading database ... 40% (Reading database ... 45% (Reading database ... 50% (Reading database ... 55% (Reading database ... 60% (Reading database ... 65% (Reading database ... 70% (Reading database ... 75% (Reading database ... 80% (Reading database ... 85% (Reading database ... 90% (Reading database ... 95% (Reading database ... 100% (Reading database ... 59957 files and directories currently installed.) 116s Preparing to unpack .../ncurses-bin_6.5+20250125-2_armhf.deb ... 116s Unpacking ncurses-bin (6.5+20250125-2) over (6.5-2) ... 116s Setting up ncurses-bin (6.5+20250125-2) ... 116s (Reading database ... (Reading database ... 5% (Reading database ... 10% (Reading database ... 15% (Reading database ... 20% (Reading database ... 25% (Reading database ... 30% (Reading database ... 35% (Reading database ... 40% (Reading database ... 45% (Reading database ... 50% (Reading database ... 55% (Reading database ... 60% (Reading database ... 65% (Reading database ... 70% (Reading database ... 75% (Reading database ... 80% (Reading database ... 85% (Reading database ... 90% (Reading database ... 95% (Reading database ... 100% (Reading database ... 59957 files and directories currently installed.) 116s Preparing to unpack .../libdebconfclient0_0.274ubuntu1_armhf.deb ... 116s Unpacking libdebconfclient0:armhf (0.274ubuntu1) over (0.272ubuntu1) ... 116s Setting up libdebconfclient0:armhf (0.274ubuntu1) ... 116s (Reading database ... (Reading database ... 5% (Reading database ... 10% (Reading database ... 15% (Reading database ... 20% (Reading database ... 25% (Reading database ... 30% (Reading database ... 35% (Reading database ... 40% (Reading database ... 45% (Reading database ... 50% (Reading database ... 55% (Reading database ... 60% (Reading database ... 65% (Reading database ... 70% (Reading database ... 75% (Reading database ... 80% (Reading database ... 85% (Reading database ... 90% (Reading database ... 95% (Reading database ... 100% (Reading database ... 59957 files and directories currently installed.) 116s Preparing to unpack .../base-passwd_3.6.6_armhf.deb ... 116s Unpacking base-passwd (3.6.6) over (3.6.5) ... 116s Setting up base-passwd (3.6.6) ... 116s (Reading database ... (Reading database ... 5% (Reading database ... 10% (Reading database ... 15% (Reading database ... 20% (Reading database ... 25% (Reading database ... 30% (Reading database ... 35% (Reading database ... 40% (Reading database ... 45% (Reading database ... 50% (Reading database ... 55% (Reading database ... 60% (Reading database ... 65% (Reading database ... 70% (Reading database ... 75% (Reading database ... 80% (Reading database ... 85% (Reading database ... 90% (Reading database ... 95% (Reading database ... 100% (Reading database ... 59957 files and directories currently installed.) 116s Preparing to unpack .../init-system-helpers_1.68_all.deb ... 116s Unpacking init-system-helpers (1.68) over (1.67ubuntu1) ... 116s Setting up init-system-helpers (1.68) ... 116s (Reading database ... (Reading database ... 5% (Reading database ... 10% (Reading database ... 15% (Reading database ... 20% (Reading database ... 25% (Reading database ... 30% (Reading database ... 35% (Reading database ... 40% (Reading database ... 45% (Reading database ... 50% (Reading database ... 55% (Reading database ... 60% (Reading database ... 65% (Reading database ... 70% (Reading database ... 75% (Reading database ... 80% (Reading database ... 85% (Reading database ... 90% (Reading database ... 95% (Reading database ... 100% (Reading database ... 59957 files and directories currently installed.) 116s Preparing to unpack .../ncurses-base_6.5+20250125-2_all.deb ... 116s Unpacking ncurses-base (6.5+20250125-2) over (6.5-2) ... 116s Setting up ncurses-base (6.5+20250125-2) ... 116s (Reading database ... (Reading database ... 5% (Reading database ... 10% (Reading database ... 15% (Reading database ... 20% (Reading database ... 25% (Reading database ... 30% (Reading database ... 35% (Reading database ... 40% (Reading database ... 45% (Reading database ... 50% (Reading database ... 55% (Reading database ... 60% (Reading database ... 65% (Reading database ... 70% (Reading database ... 75% (Reading database ... 80% (Reading database ... 85% (Reading database ... 90% (Reading database ... 95% (Reading database ... 100% (Reading database ... 59957 files and directories currently installed.) 116s Preparing to unpack .../ncurses-term_6.5+20250125-2_all.deb ... 116s Unpacking ncurses-term (6.5+20250125-2) over (6.5-2) ... 117s Preparing to unpack .../archives/apt_2.9.28_armhf.deb ... 117s Unpacking apt (2.9.28) over (2.9.14ubuntu1) ... 117s Setting up apt (2.9.28) ... 118s (Reading database ... (Reading database ... 5% (Reading database ... 10% (Reading database ... 15% (Reading database ... 20% (Reading database ... 25% (Reading database ... 30% (Reading database ... 35% (Reading database ... 40% (Reading database ... 45% (Reading database ... 50% (Reading database ... 55% (Reading database ... 60% (Reading database ... 65% (Reading database ... 70% (Reading database ... 75% (Reading database ... 80% (Reading database ... 85% (Reading database ... 90% (Reading database ... 95% (Reading database ... 100% (Reading database ... 59966 files and directories currently installed.) 118s Preparing to unpack .../apt-utils_2.9.28_armhf.deb ... 118s Unpacking apt-utils (2.9.28) over (2.9.14ubuntu1) ... 118s Preparing to unpack .../libgpg-error-l10n_1.51-3_all.deb ... 118s Unpacking libgpg-error-l10n (1.51-3) over (1.50-4) ... 118s Preparing to unpack .../libgpg-error0_1.51-3_armhf.deb ... 118s Unpacking libgpg-error0:armhf (1.51-3) over (1.50-4) ... 118s Setting up libgpg-error0:armhf (1.51-3) ... 118s (Reading database ... (Reading database ... 5% (Reading database ... 10% (Reading database ... 15% (Reading database ... 20% (Reading database ... 25% (Reading database ... 30% (Reading database ... 35% (Reading database ... 40% (Reading database ... 45% (Reading database ... 50% (Reading database ... 55% (Reading database ... 60% (Reading database ... 65% (Reading database ... 70% (Reading database ... 75% (Reading database ... 80% (Reading database ... 85% (Reading database ... 90% (Reading database ... 95% (Reading database ... 100% (Reading database ... 59966 files and directories currently installed.) 118s Preparing to unpack .../libnpth0t64_1.8-2_armhf.deb ... 118s Unpacking libnpth0t64:armhf (1.8-2) over (1.6-3.1build1) ... 118s Setting up libnpth0t64:armhf (1.8-2) ... 118s (Reading database ... (Reading database ... 5% (Reading database ... 10% (Reading database ... 15% (Reading database ... 20% (Reading database ... 25% (Reading database ... 30% (Reading database ... 35% (Reading database ... 40% (Reading database ... 45% (Reading database ... 50% (Reading database ... 55% (Reading database ... 60% (Reading database ... 65% (Reading database ... 70% (Reading database ... 75% (Reading database ... 80% (Reading database ... 85% (Reading database ... 90% (Reading database ... 95% (Reading database ... 100% (Reading database ... 59966 files and directories currently installed.) 118s Preparing to unpack .../00-gpg-wks-client_2.4.4-2ubuntu22_armhf.deb ... 118s Unpacking gpg-wks-client (2.4.4-2ubuntu22) over (2.4.4-2ubuntu18) ... 118s Preparing to unpack .../01-dirmngr_2.4.4-2ubuntu22_armhf.deb ... 118s Unpacking dirmngr (2.4.4-2ubuntu22) over (2.4.4-2ubuntu18) ... 118s Preparing to unpack .../02-gpgsm_2.4.4-2ubuntu22_armhf.deb ... 118s Unpacking gpgsm (2.4.4-2ubuntu22) over (2.4.4-2ubuntu18) ... 118s Preparing to unpack .../03-gnupg-utils_2.4.4-2ubuntu22_armhf.deb ... 118s Unpacking gnupg-utils (2.4.4-2ubuntu22) over (2.4.4-2ubuntu18) ... 118s Preparing to unpack .../04-gpg-agent_2.4.4-2ubuntu22_armhf.deb ... 118s Unpacking gpg-agent (2.4.4-2ubuntu22) over (2.4.4-2ubuntu18) ... 118s Preparing to unpack .../05-gpg_2.4.4-2ubuntu22_armhf.deb ... 118s Unpacking gpg (2.4.4-2ubuntu22) over (2.4.4-2ubuntu18) ... 118s Preparing to unpack .../06-gpgconf_2.4.4-2ubuntu22_armhf.deb ... 118s Unpacking gpgconf (2.4.4-2ubuntu22) over (2.4.4-2ubuntu18) ... 118s Preparing to unpack .../07-gnupg_2.4.4-2ubuntu22_all.deb ... 118s Unpacking gnupg (2.4.4-2ubuntu22) over (2.4.4-2ubuntu18) ... 118s Preparing to unpack .../08-keyboxd_2.4.4-2ubuntu22_armhf.deb ... 118s Unpacking keyboxd (2.4.4-2ubuntu22) over (2.4.4-2ubuntu18) ... 118s Preparing to unpack .../09-pinentry-curses_1.3.1-2ubuntu2_armhf.deb ... 118s Unpacking pinentry-curses (1.3.1-2ubuntu2) over (1.3.1-0ubuntu2) ... 118s Preparing to unpack .../10-libtasn1-6_4.20.0-2_armhf.deb ... 118s Unpacking libtasn1-6:armhf (4.20.0-2) over (4.19.0-3build1) ... 118s Setting up libtasn1-6:armhf (4.20.0-2) ... 118s (Reading database ... (Reading database ... 5% (Reading database ... 10% (Reading database ... 15% (Reading database ... 20% (Reading database ... 25% (Reading database ... 30% (Reading database ... 35% (Reading database ... 40% (Reading database ... 45% (Reading database ... 50% (Reading database ... 55% (Reading database ... 60% (Reading database ... 65% (Reading database ... 70% (Reading database ... 75% (Reading database ... 80% (Reading database ... 85% (Reading database ... 90% (Reading database ... 95% (Reading database ... 100% (Reading database ... 59966 files and directories currently installed.) 118s Preparing to unpack .../libunistring5_1.3-1_armhf.deb ... 118s Unpacking libunistring5:armhf (1.3-1) over (1.2-1) ... 119s Setting up libunistring5:armhf (1.3-1) ... 119s (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 ... 59966 files and directories currently installed.) 119s Preparing to unpack .../libgnutls30t64_3.8.9-2ubuntu1_armhf.deb ... 119s Unpacking libgnutls30t64:armhf (3.8.9-2ubuntu1) over (3.8.8-2ubuntu1) ... 119s Setting up libgnutls30t64:armhf (3.8.9-2ubuntu1) ... 119s (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 ... 59966 files and directories currently installed.) 119s Preparing to unpack .../libsasl2-modules-db_2.1.28+dfsg1-8build1_armhf.deb ... 119s Unpacking libsasl2-modules-db:armhf (2.1.28+dfsg1-8build1) over (2.1.28+dfsg1-8) ... 119s Preparing to unpack .../libsasl2-2_2.1.28+dfsg1-8build1_armhf.deb ... 119s Unpacking libsasl2-2:armhf (2.1.28+dfsg1-8build1) over (2.1.28+dfsg1-8) ... 119s Preparing to unpack .../libldap-common_2.6.9+dfsg-1~exp2ubuntu1_all.deb ... 119s Unpacking libldap-common (2.6.9+dfsg-1~exp2ubuntu1) over (2.6.8+dfsg-1~exp4ubuntu3) ... 119s Preparing to unpack .../libldap2_2.6.9+dfsg-1~exp2ubuntu1_armhf.deb ... 119s Unpacking libldap2:armhf (2.6.9+dfsg-1~exp2ubuntu1) over (2.6.8+dfsg-1~exp4ubuntu3) ... 119s Preparing to unpack .../gpgv_2.4.4-2ubuntu22_armhf.deb ... 119s Unpacking gpgv (2.4.4-2ubuntu22) over (2.4.4-2ubuntu18) ... 119s Setting up gpgv (2.4.4-2ubuntu22) ... 119s (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 ... 59965 files and directories currently installed.) 119s Preparing to unpack .../0-e2fsprogs-l10n_1.47.2-1ubuntu1_all.deb ... 119s Unpacking e2fsprogs-l10n (1.47.2-1ubuntu1) over (1.47.1-1ubuntu1) ... 119s Preparing to unpack .../1-logsave_1.47.2-1ubuntu1_armhf.deb ... 119s Unpacking logsave (1.47.2-1ubuntu1) over (1.47.1-1ubuntu1) ... 119s Preparing to unpack .../2-ubuntu-minimal_1.547_armhf.deb ... 119s Unpacking ubuntu-minimal (1.547) over (1.544) ... 119s Preparing to unpack .../3-initramfs-tools_0.145ubuntu2_all.deb ... 119s Unpacking initramfs-tools (0.145ubuntu2) over (0.142ubuntu35) ... 119s Preparing to unpack .../4-initramfs-tools-core_0.145ubuntu2_all.deb ... 119s Unpacking initramfs-tools-core (0.145ubuntu2) over (0.142ubuntu35) ... 119s Preparing to unpack .../5-libext2fs2t64_1.47.2-1ubuntu1_armhf.deb ... 119s Leaving 'diversion of /lib/arm-linux-gnueabihf/libe2p.so.2 to /lib/arm-linux-gnueabihf/libe2p.so.2.usr-is-merged by libext2fs2t64' 119s Leaving 'diversion of /lib/arm-linux-gnueabihf/libe2p.so.2.3 to /lib/arm-linux-gnueabihf/libe2p.so.2.3.usr-is-merged by libext2fs2t64' 119s Leaving 'diversion of /lib/arm-linux-gnueabihf/libext2fs.so.2 to /lib/arm-linux-gnueabihf/libext2fs.so.2.usr-is-merged by libext2fs2t64' 119s Leaving 'diversion of /lib/arm-linux-gnueabihf/libext2fs.so.2.4 to /lib/arm-linux-gnueabihf/libext2fs.so.2.4.usr-is-merged by libext2fs2t64' 119s Unpacking libext2fs2t64:armhf (1.47.2-1ubuntu1) over (1.47.1-1ubuntu1) ... 119s Setting up libext2fs2t64:armhf (1.47.2-1ubuntu1) ... 119s (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 ... 59965 files and directories currently installed.) 119s Preparing to unpack .../e2fsprogs_1.47.2-1ubuntu1_armhf.deb ... 119s Unpacking e2fsprogs (1.47.2-1ubuntu1) over (1.47.1-1ubuntu1) ... 119s Preparing to unpack .../console-setup-linux_1.226ubuntu3_all.deb ... 119s Unpacking console-setup-linux (1.226ubuntu3) over (1.226ubuntu2) ... 119s Preparing to unpack .../console-setup_1.226ubuntu3_all.deb ... 119s Unpacking console-setup (1.226ubuntu3) over (1.226ubuntu2) ... 119s Preparing to unpack .../keyboard-configuration_1.226ubuntu3_all.deb ... 120s Unpacking keyboard-configuration (1.226ubuntu3) over (1.226ubuntu2) ... 120s Preparing to unpack .../dhcpcd-base_1%3a10.1.0-6_armhf.deb ... 120s Unpacking dhcpcd-base (1:10.1.0-6) over (1:10.1.0-2) ... 120s Setting up libapparmor1:armhf (4.1.0~beta1-0ubuntu5) ... 120s Setting up mount (2.40.2-14ubuntu1) ... 120s Setting up systemd (257.2-3ubuntu1) ... 120s Installing new version of config file /etc/systemd/logind.conf ... 120s Installing new version of config file /etc/systemd/sleep.conf ... 120s /usr/lib/tmpfiles.d/legacy.conf:14: Duplicate line for path "/run/lock", ignoring. 120s Created symlink '/run/systemd/system/tmp.mount' → '/dev/null'. 120s /usr/lib/tmpfiles.d/legacy.conf:14: Duplicate line for path "/run/lock", ignoring. 120s Setting up systemd-sysv (257.2-3ubuntu1) ... 121s (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 ... 59964 files and directories currently installed.) 121s Preparing to unpack .../0-init_1.68_armhf.deb ... 121s Unpacking init (1.68) over (1.67ubuntu1) ... 121s Preparing to unpack .../1-libbpf1_1%3a1.5.0-2_armhf.deb ... 121s Unpacking libbpf1:armhf (1:1.5.0-2) over (1:1.5.0-1) ... 121s Preparing to unpack .../2-iptables_1.8.11-2ubuntu1_armhf.deb ... 121s Unpacking iptables (1.8.11-2ubuntu1) over (1.8.10-3ubuntu2) ... 121s Preparing to unpack .../3-libip4tc2_1.8.11-2ubuntu1_armhf.deb ... 121s Unpacking libip4tc2:armhf (1.8.11-2ubuntu1) over (1.8.10-3ubuntu2) ... 121s Preparing to unpack .../4-libip6tc2_1.8.11-2ubuntu1_armhf.deb ... 121s Unpacking libip6tc2:armhf (1.8.11-2ubuntu1) over (1.8.10-3ubuntu2) ... 121s Preparing to unpack .../5-libnftnl11_1.2.8-1_armhf.deb ... 121s Unpacking libnftnl11:armhf (1.2.8-1) over (1.2.7-1) ... 121s Preparing to unpack .../6-libxtables12_1.8.11-2ubuntu1_armhf.deb ... 121s Unpacking libxtables12:armhf (1.8.11-2ubuntu1) over (1.8.10-3ubuntu2) ... 121s Preparing to unpack .../7-iproute2_6.13.0-1ubuntu1_armhf.deb ... 121s Unpacking iproute2 (6.13.0-1ubuntu1) over (6.10.0-2ubuntu1) ... 121s Preparing to unpack .../8-iputils-ping_3%3a20240905-1ubuntu1_armhf.deb ... 121s Unpacking iputils-ping (3:20240905-1ubuntu1) over (3:20240117-1build1) ... 121s Selecting previously unselected package login.defs. 121s Preparing to unpack .../9-login.defs_1%3a4.16.0-7ubuntu1_all.deb ... 121s Unpacking login.defs (1:4.16.0-7ubuntu1) ... 121s Replacing files in old package login (1:4.15.3-3ubuntu2) ... 121s Setting up login.defs (1:4.16.0-7ubuntu1) ... 121s Installing new version of config file /etc/login.defs ... 121s (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 ... 59971 files and directories currently installed.) 121s Preparing to unpack .../0-login_1%3a4.16.0-2+really2.40.2-14ubuntu1_armhf.deb ... 121s Unpacking login (1:4.16.0-2+really2.40.2-14ubuntu1) over (1:4.15.3-3ubuntu2) ... 121s Preparing to unpack .../1-mawk_1.3.4.20250131-1_armhf.deb ... 121s Unpacking mawk (1.3.4.20250131-1) over (1.3.4.20240905-1) ... 122s Preparing to unpack .../2-netcat-openbsd_1.228-1_armhf.deb ... 122s Unpacking netcat-openbsd (1.228-1) over (1.226-1.1) ... 122s Selecting previously unselected package libpython3.13-minimal:armhf. 122s Preparing to unpack .../3-libpython3.13-minimal_3.13.2-1_armhf.deb ... 122s Unpacking libpython3.13-minimal:armhf (3.13.2-1) ... 122s Selecting previously unselected package python3.13-minimal. 122s Preparing to unpack .../4-python3.13-minimal_3.13.2-1_armhf.deb ... 122s Unpacking python3.13-minimal (3.13.2-1) ... 122s Preparing to unpack .../5-python3-cryptography_43.0.0-1_armhf.deb ... 122s Unpacking python3-cryptography (43.0.0-1) over (42.0.5-2build1) ... 122s Setting up libpython3.13-minimal:armhf (3.13.2-1) ... 122s Setting up python3.13-minimal (3.13.2-1) ... 123s (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 ... 60253 files and directories currently installed.) 123s Preparing to unpack .../python3-minimal_3.13.1-1~exp2_armhf.deb ... 123s Unpacking python3-minimal (3.13.1-1~exp2) over (3.12.6-0ubuntu1) ... 123s Setting up python3-minimal (3.13.1-1~exp2) ... 123s (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 ... 60253 files and directories currently installed.) 123s Preparing to unpack .../python3_3.13.1-1~exp2_armhf.deb ... 123s Unpacking python3 (3.13.1-1~exp2) over (3.12.6-0ubuntu1) ... 123s Selecting previously unselected package python3-bcrypt. 123s Preparing to unpack .../python3-bcrypt_4.2.0-2.1_armhf.deb ... 123s Unpacking python3-bcrypt (4.2.0-2.1) ... 123s Preparing to unpack .../tzdata_2024b-6ubuntu1_all.deb ... 123s Unpacking tzdata (2024b-6ubuntu1) over (2024b-1ubuntu2) ... 124s Preparing to unpack .../libffi8_3.4.7-1_armhf.deb ... 124s Unpacking libffi8:armhf (3.4.7-1) over (3.4.6-1build1) ... 124s Setting up libffi8:armhf (3.4.7-1) ... 124s Selecting previously unselected package libpython3.13-stdlib:armhf. 124s (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 ... 60257 files and directories currently installed.) 124s Preparing to unpack .../00-libpython3.13-stdlib_3.13.2-1_armhf.deb ... 124s Unpacking libpython3.13-stdlib:armhf (3.13.2-1) ... 124s Selecting previously unselected package python3.13. 124s Preparing to unpack .../01-python3.13_3.13.2-1_armhf.deb ... 124s Unpacking python3.13 (3.13.2-1) ... 124s Preparing to unpack .../02-libpython3-stdlib_3.13.1-1~exp2_armhf.deb ... 124s Unpacking libpython3-stdlib:armhf (3.13.1-1~exp2) over (3.12.6-0ubuntu1) ... 124s Preparing to unpack .../03-gir1.2-girepository-2.0_1.82.0-4_armhf.deb ... 124s Unpacking gir1.2-girepository-2.0:armhf (1.82.0-4) over (1.82.0-2) ... 124s Preparing to unpack .../04-gir1.2-glib-2.0_2.83.3-2_armhf.deb ... 124s Unpacking gir1.2-glib-2.0:armhf (2.83.3-2) over (2.82.2-3) ... 124s Preparing to unpack .../05-libgirepository-1.0-1_1.82.0-4_armhf.deb ... 124s Unpacking libgirepository-1.0-1:armhf (1.82.0-4) over (1.82.0-2) ... 124s Preparing to unpack .../06-libglib2.0-data_2.83.3-2_all.deb ... 124s Unpacking libglib2.0-data (2.83.3-2) over (2.82.2-3) ... 124s Preparing to unpack .../07-libglib2.0-bin_2.83.3-2_armhf.deb ... 124s Unpacking libglib2.0-bin (2.83.3-2) over (2.82.2-3) ... 124s Preparing to unpack .../08-libglib2.0-0t64_2.83.3-2_armhf.deb ... 124s Unpacking libglib2.0-0t64:armhf (2.83.3-2) over (2.82.2-3) ... 124s Preparing to unpack .../09-netplan-generator_1.1.2-2ubuntu1_armhf.deb ... 124s Adding 'diversion of /lib/systemd/system-generators/netplan to /lib/systemd/system-generators/netplan.usr-is-merged by netplan-generator' 124s Unpacking netplan-generator (1.1.2-2ubuntu1) over (1.1.1-1) ... 124s Preparing to unpack .../10-libyaml-0-2_0.2.5-2_armhf.deb ... 124s Unpacking libyaml-0-2:armhf (0.2.5-2) over (0.2.5-1build1) ... 124s Preparing to unpack .../11-python3-netplan_1.1.2-2ubuntu1_armhf.deb ... 124s /usr/bin/py3clean:101: DeprecationWarning: glob.glob1 is deprecated and will be removed in Python 3.15. Use glob.glob and pass a directory to its root_dir argument instead. 124s for fn in glob1(directory, "%s.*" % fname): 124s Unpacking python3-netplan (1.1.2-2ubuntu1) over (1.1.1-1) ... 124s Preparing to unpack .../12-netplan.io_1.1.2-2ubuntu1_armhf.deb ... 124s Unpacking netplan.io (1.1.2-2ubuntu1) over (1.1.1-1) ... 125s Preparing to unpack .../13-libnetplan1_1.1.2-2ubuntu1_armhf.deb ... 125s Unpacking libnetplan1:armhf (1.1.2-2ubuntu1) over (1.1.1-1) ... 125s Preparing to unpack .../14-ethtool_1%3a6.11-1_armhf.deb ... 125s Unpacking ethtool (1:6.11-1) over (1:6.10-1) ... 125s Preparing to unpack .../15-libsemanage-common_3.7-2.1_all.deb ... 125s Unpacking libsemanage-common (3.7-2.1) over (3.7-2build1) ... 125s Setting up libsemanage-common (3.7-2.1) ... 125s (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 ... 60676 files and directories currently installed.) 125s Preparing to unpack .../libsemanage2_3.7-2.1_armhf.deb ... 125s Unpacking libsemanage2:armhf (3.7-2.1) over (3.7-2build1) ... 125s Setting up libsemanage2:armhf (3.7-2.1) ... 125s (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 ... 60676 files and directories currently installed.) 125s Preparing to unpack .../passwd_1%3a4.16.0-7ubuntu1_armhf.deb ... 125s Unpacking passwd (1:4.16.0-7ubuntu1) over (1:4.15.3-3ubuntu2) ... 125s Setting up passwd (1:4.16.0-7ubuntu1) ... 125s (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 ... 60711 files and directories currently installed.) 125s Preparing to unpack .../000-python3-newt_0.52.24-4ubuntu1_armhf.deb ... 125s /usr/bin/py3clean:101: DeprecationWarning: glob.glob1 is deprecated and will be removed in Python 3.15. Use glob.glob and pass a directory to its root_dir argument instead. 125s for fn in glob1(directory, "%s.*" % fname): 125s Unpacking python3-newt:armhf (0.52.24-4ubuntu1) over (0.52.24-2ubuntu4) ... 125s Preparing to unpack .../001-libnewt0.52_0.52.24-4ubuntu1_armhf.deb ... 125s Unpacking libnewt0.52:armhf (0.52.24-4ubuntu1) over (0.52.24-2ubuntu4) ... 125s Preparing to unpack .../002-whiptail_0.52.24-4ubuntu1_armhf.deb ... 125s Unpacking whiptail (0.52.24-4ubuntu1) over (0.52.24-2ubuntu4) ... 125s Preparing to unpack .../003-dracut-install_106-2ubuntu1_armhf.deb ... 125s Unpacking dracut-install (106-2ubuntu1) over (105-2ubuntu3) ... 126s Preparing to unpack .../004-initramfs-tools-bin_0.145ubuntu2_armhf.deb ... 126s Unpacking initramfs-tools-bin (0.145ubuntu2) over (0.142ubuntu35) ... 126s Preparing to unpack .../005-busybox-initramfs_1%3a1.37.0-4ubuntu1_armhf.deb ... 126s Unpacking busybox-initramfs (1:1.37.0-4ubuntu1) over (1:1.36.1-9ubuntu1) ... 126s Preparing to unpack .../006-python3.12_3.12.9-1_armhf.deb ... 126s Unpacking python3.12 (3.12.9-1) over (3.12.7-3) ... 126s Preparing to unpack .../007-libpython3.12-stdlib_3.12.9-1_armhf.deb ... 126s Unpacking libpython3.12-stdlib:armhf (3.12.9-1) over (3.12.7-3) ... 126s Preparing to unpack .../008-python3.12-minimal_3.12.9-1_armhf.deb ... 126s Unpacking python3.12-minimal (3.12.9-1) over (3.12.7-3) ... 126s Preparing to unpack .../009-libpython3.12-minimal_3.12.9-1_armhf.deb ... 126s Unpacking libpython3.12-minimal:armhf (3.12.9-1) over (3.12.7-3) ... 126s Preparing to unpack .../010-cron_3.0pl1-192ubuntu1_armhf.deb ... 126s Unpacking cron (3.0pl1-192ubuntu1) over (3.0pl1-189ubuntu1) ... 126s Preparing to unpack .../011-rsync_3.4.1-0syncable1_armhf.deb ... 126s Unpacking rsync (3.4.1-0syncable1) over (3.3.0-1) ... 127s Preparing to unpack .../012-python-apt-common_2.9.8_all.deb ... 127s Unpacking python-apt-common (2.9.8) over (2.9.0ubuntu2) ... 127s Preparing to unpack .../013-python3-apt_2.9.8_armhf.deb ... 127s /usr/bin/py3clean:101: DeprecationWarning: glob.glob1 is deprecated and will be removed in Python 3.15. Use glob.glob and pass a directory to its root_dir argument instead. 127s for fn in glob1(directory, "%s.*" % fname): 127s Unpacking python3-apt (2.9.8) over (2.9.0ubuntu2) ... 127s Preparing to unpack .../014-python3-lazr.uri_1.0.6-5_all.deb ... 127s /usr/bin/py3clean:101: DeprecationWarning: glob.glob1 is deprecated and will be removed in Python 3.15. Use glob.glob and pass a directory to its root_dir argument instead. 127s for fn in glob1(directory, "%s.*" % fname): 127s Unpacking python3-lazr.uri (1.0.6-5) over (1.0.6-4) ... 127s Preparing to unpack .../015-python3-launchpadlib_2.1.0-1_all.deb ... 127s /usr/bin/py3clean:101: DeprecationWarning: glob.glob1 is deprecated and will be removed in Python 3.15. Use glob.glob and pass a directory to its root_dir argument instead. 127s for fn in glob1(directory, "%s.*" % fname): 127s Unpacking python3-launchpadlib (2.1.0-1) over (2.0.0-1) ... 127s Preparing to unpack .../016-python3-problem-report_2.31.0-0ubuntu5_all.deb ... 127s /usr/bin/py3clean:101: DeprecationWarning: glob.glob1 is deprecated and will be removed in Python 3.15. Use glob.glob and pass a directory to its root_dir argument instead. 127s for fn in glob1(directory, "%s.*" % fname): 127s Unpacking python3-problem-report (2.31.0-0ubuntu5) over (2.30.0-0ubuntu5) ... 127s Preparing to unpack .../017-python3-apport_2.31.0-0ubuntu5_all.deb ... 127s /usr/bin/py3clean:101: DeprecationWarning: glob.glob1 is deprecated and will be removed in Python 3.15. Use glob.glob and pass a directory to its root_dir argument instead. 127s for fn in glob1(directory, "%s.*" % fname): 127s Unpacking python3-apport (2.31.0-0ubuntu5) over (2.30.0-0ubuntu5) ... 127s Preparing to unpack .../018-python3-gi_3.50.0-4_armhf.deb ... 127s /usr/bin/py3clean:101: DeprecationWarning: glob.glob1 is deprecated and will be removed in Python 3.15. Use glob.glob and pass a directory to its root_dir argument instead. 127s for fn in glob1(directory, "%s.*" % fname): 127s Unpacking python3-gi (3.50.0-4) over (3.50.0-3build1) ... 127s Preparing to unpack .../019-apport-core-dump-handler_2.31.0-0ubuntu5_all.deb ... 127s Unpacking apport-core-dump-handler (2.31.0-0ubuntu5) over (2.30.0-0ubuntu5) ... 128s Preparing to unpack .../020-apport_2.31.0-0ubuntu5_all.deb ... 128s Unpacking apport (2.31.0-0ubuntu5) over (2.30.0-0ubuntu5) ... 128s Preparing to unpack .../021-libcom-err2_1.47.2-1ubuntu1_armhf.deb ... 128s Unpacking libcom-err2:armhf (1.47.2-1ubuntu1) over (1.47.1-1ubuntu1) ... 128s Preparing to unpack .../022-libss2_1.47.2-1ubuntu1_armhf.deb ... 128s Unpacking libss2:armhf (1.47.2-1ubuntu1) over (1.47.1-1ubuntu1) ... 128s Preparing to unpack .../023-openssl_3.4.0-1ubuntu2_armhf.deb ... 128s Unpacking openssl (3.4.0-1ubuntu2) over (3.3.1-2ubuntu2) ... 128s Preparing to unpack .../024-ca-certificates_20241223_all.deb ... 128s Unpacking ca-certificates (20241223) over (20240203) ... 128s Preparing to unpack .../025-distro-info_1.13_armhf.deb ... 128s Unpacking distro-info (1.13) over (1.12) ... 128s Preparing to unpack .../026-krb5-locales_1.21.3-4ubuntu1_all.deb ... 128s Unpacking krb5-locales (1.21.3-4ubuntu1) over (1.21.3-3) ... 128s Preparing to unpack .../027-libfribidi0_1.0.16-1_armhf.deb ... 128s Unpacking libfribidi0:armhf (1.0.16-1) over (1.0.15-1) ... 128s Preparing to unpack .../028-libgssapi-krb5-2_1.21.3-4ubuntu1_armhf.deb ... 128s Unpacking libgssapi-krb5-2:armhf (1.21.3-4ubuntu1) over (1.21.3-3) ... 128s Preparing to unpack .../029-libkrb5-3_1.21.3-4ubuntu1_armhf.deb ... 128s Unpacking libkrb5-3:armhf (1.21.3-4ubuntu1) over (1.21.3-3) ... 128s Preparing to unpack .../030-libkrb5support0_1.21.3-4ubuntu1_armhf.deb ... 128s Unpacking libkrb5support0:armhf (1.21.3-4ubuntu1) over (1.21.3-3) ... 128s Preparing to unpack .../031-libk5crypto3_1.21.3-4ubuntu1_armhf.deb ... 128s Unpacking libk5crypto3:armhf (1.21.3-4ubuntu1) over (1.21.3-3) ... 128s Preparing to unpack .../032-libicu74_74.2-1ubuntu6_armhf.deb ... 128s Unpacking libicu74:armhf (74.2-1ubuntu6) over (74.2-1ubuntu4) ... 128s Preparing to unpack .../033-libxml2_2.12.7+dfsg+really2.9.14-0.2ubuntu3_armhf.deb ... 128s Unpacking libxml2:armhf (2.12.7+dfsg+really2.9.14-0.2ubuntu3) over (2.12.7+dfsg-3) ... 129s Preparing to unpack .../034-python3-pygments_2.18.0+dfsg-2_all.deb ... 129s /usr/bin/py3clean:101: DeprecationWarning: glob.glob1 is deprecated and will be removed in Python 3.15. Use glob.glob and pass a directory to its root_dir argument instead. 129s for fn in glob1(directory, "%s.*" % fname): 129s Unpacking python3-pygments (2.18.0+dfsg-2) over (2.18.0+dfsg-1ubuntu1) ... 129s Preparing to unpack .../035-python3-rich_13.9.4-1_all.deb ... 129s /usr/bin/py3clean:101: DeprecationWarning: glob.glob1 is deprecated and will be removed in Python 3.15. Use glob.glob and pass a directory to its root_dir argument instead. 129s for fn in glob1(directory, "%s.*" % fname): 129s Unpacking python3-rich (13.9.4-1) over (13.7.1-1) ... 129s Preparing to unpack .../036-ucf_3.0049_all.deb ... 129s Unpacking ucf (3.0049) over (3.0043+nmu1) ... 129s Preparing to unpack .../037-rsyslog_8.2412.0-1ubuntu1_armhf.deb ... 129s Unpacking rsyslog (8.2412.0-1ubuntu1) over (8.2406.0-1ubuntu2) ... 129s Preparing to unpack .../038-apparmor_4.1.0~beta1-0ubuntu5_armhf.deb ... 130s Unpacking apparmor (4.1.0~beta1-0ubuntu5) over (4.1.0~beta1-0ubuntu4) ... 130s Preparing to unpack .../039-bash-completion_1%3a2.16.0-7_all.deb ... 130s Unpacking bash-completion (1:2.16.0-7) over (1:2.14.0-2) ... 131s Preparing to unpack .../040-bind9-dnsutils_1%3a9.20.0-2ubuntu4_armhf.deb ... 131s Unpacking bind9-dnsutils (1:9.20.0-2ubuntu4) over (1:9.20.0-2ubuntu3) ... 131s Preparing to unpack .../041-bind9-host_1%3a9.20.0-2ubuntu4_armhf.deb ... 131s Unpacking bind9-host (1:9.20.0-2ubuntu4) over (1:9.20.0-2ubuntu3) ... 131s Preparing to unpack .../042-bind9-libs_1%3a9.20.0-2ubuntu4_armhf.deb ... 131s Unpacking bind9-libs:armhf (1:9.20.0-2ubuntu4) over (1:9.20.0-2ubuntu3) ... 131s Preparing to unpack .../043-libedit2_3.1-20250104-1_armhf.deb ... 131s Unpacking libedit2:armhf (3.1-20250104-1) over (3.1-20240808-1) ... 131s Preparing to unpack .../044-busybox-static_1%3a1.37.0-4ubuntu1_armhf.deb ... 131s Unpacking busybox-static (1:1.37.0-4ubuntu1) over (1:1.36.1-9ubuntu1) ... 131s Preparing to unpack .../045-cron-daemon-common_3.0pl1-192ubuntu1_all.deb ... 131s Unpacking cron-daemon-common (3.0pl1-192ubuntu1) over (3.0pl1-189ubuntu1) ... 131s Preparing to unpack .../046-libdevmapper1.02.1_2%3a1.02.201-1ubuntu1_armhf.deb ... 131s Unpacking libdevmapper1.02.1:armhf (2:1.02.201-1ubuntu1) over (2:1.02.196-1ubuntu2) ... 131s Preparing to unpack .../047-dmsetup_2%3a1.02.201-1ubuntu1_armhf.deb ... 131s Unpacking dmsetup (2:1.02.201-1ubuntu1) over (2:1.02.196-1ubuntu2) ... 131s Preparing to unpack .../048-ed_1.21-1_armhf.deb ... 131s Unpacking ed (1.21-1) over (1.20.2-2) ... 131s Preparing to unpack .../049-gettext-base_0.23.1-1_armhf.deb ... 131s Unpacking gettext-base (0.23.1-1) over (0.22.5-2) ... 131s Preparing to unpack .../050-groff-base_1.23.0-7_armhf.deb ... 131s Unpacking groff-base (1.23.0-7) over (1.23.0-5) ... 131s Preparing to unpack .../051-libibverbs1_55.0-1ubuntu1_armhf.deb ... 131s Unpacking libibverbs1:armhf (55.0-1ubuntu1) over (52.0-2ubuntu1) ... 131s Preparing to unpack .../052-ibverbs-providers_55.0-1ubuntu1_armhf.deb ... 131s Unpacking ibverbs-providers:armhf (55.0-1ubuntu1) over (52.0-2ubuntu1) ... 131s Preparing to unpack .../053-iputils-tracepath_3%3a20240905-1ubuntu1_armhf.deb ... 131s Unpacking iputils-tracepath (3:20240905-1ubuntu1) over (3:20240117-1build1) ... 131s Preparing to unpack .../054-nftables_1.1.1-1build1_armhf.deb ... 131s Unpacking nftables (1.1.1-1build1) over (1.1.0-2) ... 131s Preparing to unpack .../055-libnftables1_1.1.1-1build1_armhf.deb ... 131s Unpacking libnftables1:armhf (1.1.1-1build1) over (1.1.0-2) ... 131s Preparing to unpack .../056-libpcap0.8t64_1.10.5-2ubuntu1_armhf.deb ... 131s Unpacking libpcap0.8t64:armhf (1.10.5-2ubuntu1) over (1.10.5-1ubuntu1) ... 132s Preparing to unpack .../057-libpng16-16t64_1.6.46-4_armhf.deb ... 132s Unpacking libpng16-16t64:armhf (1.6.46-4) over (1.6.44-2) ... 132s Preparing to unpack .../058-libtraceevent1-plugin_1%3a1.8.4-2_armhf.deb ... 132s Unpacking libtraceevent1-plugin:armhf (1:1.8.4-2) over (1:1.8.4-1) ... 132s Preparing to unpack .../059-libtraceevent1_1%3a1.8.4-2_armhf.deb ... 132s Unpacking libtraceevent1:armhf (1:1.8.4-2) over (1:1.8.4-1) ... 132s Preparing to unpack .../060-libusb-1.0-0_2%3a1.0.27-2_armhf.deb ... 132s Unpacking libusb-1.0-0:armhf (2:1.0.27-2) over (2:1.0.27-1) ... 132s Preparing to unpack .../061-libxdmcp6_1%3a1.1.5-1_armhf.deb ... 132s Unpacking libxdmcp6:armhf (1:1.1.5-1) over (1:1.1.3-0ubuntu6) ... 132s Preparing to unpack .../062-libxkbcommon0_1.7.0-2_armhf.deb ... 132s Unpacking libxkbcommon0:armhf (1.7.0-2) over (1.7.0-1) ... 132s Preparing to unpack .../063-lshw_02.19.git.2021.06.19.996aaad9c7-2.1ubuntu1_armhf.deb ... 132s Unpacking lshw (02.19.git.2021.06.19.996aaad9c7-2.1ubuntu1) over (02.19.git.2021.06.19.996aaad9c7-2ubuntu2) ... 132s Preparing to unpack .../064-nano_8.3-1_armhf.deb ... 132s Unpacking nano (8.3-1) over (8.2-1) ... 132s Preparing to unpack .../065-pci.ids_0.0~2025.02.05-1_all.deb ... 132s Unpacking pci.ids (0.0~2025.02.05-1) over (0.0~2024.10.24-1) ... 132s Preparing to unpack .../066-powermgmt-base_1.38_all.deb ... 132s Unpacking powermgmt-base (1.38) over (1.37+nmu1ubuntu1) ... 132s Preparing to unpack .../067-publicsuffix_20250108.1153-0.1_all.deb ... 132s Unpacking publicsuffix (20250108.1153-0.1) over (20231001.0357-0.1) ... 132s Preparing to unpack .../068-python3-distro-info_1.13_all.deb ... 132s /usr/bin/py3clean:101: DeprecationWarning: glob.glob1 is deprecated and will be removed in Python 3.15. Use glob.glob and pass a directory to its root_dir argument instead. 132s for fn in glob1(directory, "%s.*" % fname): 132s Unpacking python3-distro-info (1.13) over (1.12) ... 132s Preparing to unpack .../069-python3.13-gdbm_3.13.2-1_armhf.deb ... 132s Unpacking python3.13-gdbm (3.13.2-1) over (3.13.0-2) ... 132s Preparing to unpack .../070-python3.12-gdbm_3.12.9-1_armhf.deb ... 132s Unpacking python3.12-gdbm (3.12.9-1) over (3.12.7-3) ... 132s Preparing to unpack .../071-python3-gdbm_3.13.1-1_armhf.deb ... 132s Unpacking python3-gdbm:armhf (3.13.1-1) over (3.12.7-1) ... 132s Preparing to unpack .../072-ubuntu-standard_1.547_armhf.deb ... 132s Unpacking ubuntu-standard (1.547) over (1.544) ... 132s Preparing to unpack .../073-ufw_0.36.2-9_all.deb ... 132s /usr/bin/py3clean:101: DeprecationWarning: glob.glob1 is deprecated and will be removed in Python 3.15. Use glob.glob and pass a directory to its root_dir argument instead. 132s for fn in glob1(directory, "%s.*" % fname): 132s Unpacking ufw (0.36.2-9) over (0.36.2-8) ... 132s Preparing to unpack .../074-usb.ids_2025.01.14-1_all.deb ... 132s Unpacking usb.ids (2025.01.14-1) over (2024.07.04-1) ... 132s Preparing to unpack .../075-xauth_1%3a1.1.2-1.1_armhf.deb ... 132s Unpacking xauth (1:1.1.2-1.1) over (1:1.1.2-1build1) ... 132s Preparing to unpack .../076-libcurl3t64-gnutls_8.12.0+git20250209.89ed161+ds-1ubuntu1_armhf.deb ... 132s Unpacking libcurl3t64-gnutls:armhf (8.12.0+git20250209.89ed161+ds-1ubuntu1) over (8.11.0-1ubuntu2) ... 133s Preparing to unpack .../077-libappstream5_1.0.4-1_armhf.deb ... 133s Unpacking libappstream5:armhf (1.0.4-1) over (1.0.3-1) ... 133s Preparing to unpack .../078-appstream_1.0.4-1_armhf.deb ... 133s Unpacking appstream (1.0.4-1) over (1.0.3-1) ... 133s Preparing to unpack .../079-libctf0_2.44-1ubuntu1_armhf.deb ... 133s Unpacking libctf0:armhf (2.44-1ubuntu1) over (2.43.1-4ubuntu1) ... 133s Preparing to unpack .../080-libctf-nobfd0_2.44-1ubuntu1_armhf.deb ... 133s Unpacking libctf-nobfd0:armhf (2.44-1ubuntu1) over (2.43.1-4ubuntu1) ... 133s Preparing to unpack .../081-binutils-arm-linux-gnueabihf_2.44-1ubuntu1_armhf.deb ... 133s Unpacking binutils-arm-linux-gnueabihf (2.44-1ubuntu1) over (2.43.1-4ubuntu1) ... 133s Preparing to unpack .../082-libbinutils_2.44-1ubuntu1_armhf.deb ... 133s Unpacking libbinutils:armhf (2.44-1ubuntu1) over (2.43.1-4ubuntu1) ... 133s Preparing to unpack .../083-binutils_2.44-1ubuntu1_armhf.deb ... 133s Unpacking binutils (2.44-1ubuntu1) over (2.43.1-4ubuntu1) ... 133s Preparing to unpack .../084-binutils-common_2.44-1ubuntu1_armhf.deb ... 133s Unpacking binutils-common:armhf (2.44-1ubuntu1) over (2.43.1-4ubuntu1) ... 133s Preparing to unpack .../085-libsframe1_2.44-1ubuntu1_armhf.deb ... 133s Unpacking libsframe1:armhf (2.44-1ubuntu1) over (2.43.1-4ubuntu1) ... 133s Preparing to unpack .../086-btrfs-progs_6.12-1build1_armhf.deb ... 133s Unpacking btrfs-progs (6.12-1build1) over (6.6.3-1.2) ... 133s Preparing to unpack .../087-python3-jinja2_3.1.5-2_all.deb ... 133s /usr/bin/py3clean:101: DeprecationWarning: glob.glob1 is deprecated and will be removed in Python 3.15. Use glob.glob and pass a directory to its root_dir argument instead. 133s for fn in glob1(directory, "%s.*" % fname): 133s Unpacking python3-jinja2 (3.1.5-2) over (3.1.3-1ubuntu1) ... 133s Preparing to unpack .../088-python3-json-pointer_2.4-3_all.deb ... 133s /usr/bin/py3clean:101: DeprecationWarning: glob.glob1 is deprecated and will be removed in Python 3.15. Use glob.glob and pass a directory to its root_dir argument instead. 133s for fn in glob1(directory, "%s.*" % fname): 133s Unpacking python3-json-pointer (2.4-3) over (2.4-2) ... 133s Preparing to unpack .../089-python3-jsonpatch_1.32-5_all.deb ... 133s /usr/bin/py3clean:101: DeprecationWarning: glob.glob1 is deprecated and will be removed in Python 3.15. Use glob.glob and pass a directory to its root_dir argument instead. 133s for fn in glob1(directory, "%s.*" % fname): 133s Unpacking python3-jsonpatch (1.32-5) over (1.32-4) ... 133s Preparing to unpack .../090-python3-attr_25.1.0-1_all.deb ... 133s /usr/bin/py3clean:101: DeprecationWarning: glob.glob1 is deprecated and will be removed in Python 3.15. Use glob.glob and pass a directory to its root_dir argument instead. 133s for fn in glob1(directory, "%s.*" % fname): 133s Unpacking python3-attr (25.1.0-1) over (23.2.0-2) ... 133s Preparing to unpack .../091-python3-referencing_0.35.1-2ubuntu1_all.deb ... 134s /usr/bin/py3clean:101: DeprecationWarning: glob.glob1 is deprecated and will be removed in Python 3.15. Use glob.glob and pass a directory to its root_dir argument instead. 134s for fn in glob1(directory, "%s.*" % fname): 134s Unpacking python3-referencing (0.35.1-2ubuntu1) over (0.35.1-1ubuntu1) ... 134s Preparing to unpack .../092-python3-jsonschema_4.19.2-6ubuntu1_all.deb ... 134s /usr/bin/py3clean:101: DeprecationWarning: glob.glob1 is deprecated and will be removed in Python 3.15. Use glob.glob and pass a directory to its root_dir argument instead. 134s for fn in glob1(directory, "%s.*" % fname): 134s Unpacking python3-jsonschema (4.19.2-6ubuntu1) over (4.19.2-3ubuntu1) ... 134s Preparing to unpack .../093-python3-jwt_2.10.1-2_all.deb ... 134s /usr/bin/py3clean:101: DeprecationWarning: glob.glob1 is deprecated and will be removed in Python 3.15. Use glob.glob and pass a directory to its root_dir argument instead. 134s for fn in glob1(directory, "%s.*" % fname): 134s Unpacking python3-jwt (2.10.1-2) over (2.7.0-1) ... 134s Preparing to unpack .../094-python3-oauthlib_3.2.2-3_all.deb ... 134s /usr/bin/py3clean:101: DeprecationWarning: glob.glob1 is deprecated and will be removed in Python 3.15. Use glob.glob and pass a directory to its root_dir argument instead. 134s for fn in glob1(directory, "%s.*" % fname): 134s Unpacking python3-oauthlib (3.2.2-3) over (3.2.2-2) ... 134s Preparing to unpack .../095-cloud-init-base_25.1~3geb1965a4-0ubuntu1_all.deb ... 134s /usr/bin/py3clean:101: DeprecationWarning: glob.glob1 is deprecated and will be removed in Python 3.15. Use glob.glob and pass a directory to its root_dir argument instead. 134s for fn in glob1(directory, "%s.*" % fname): 134s Unpacking cloud-init-base (25.1~3geb1965a4-0ubuntu1) over (24.4-0ubuntu1) ... 134s dpkg: warning: unable to delete old directory '/lib/systemd/system/sshd-keygen@.service.d': Directory not empty 134s Preparing to unpack .../096-curl_8.12.0+git20250209.89ed161+ds-1ubuntu1_armhf.deb ... 134s Unpacking curl (8.12.0+git20250209.89ed161+ds-1ubuntu1) over (8.11.0-1ubuntu2) ... 134s Preparing to unpack .../097-libcurl4t64_8.12.0+git20250209.89ed161+ds-1ubuntu1_armhf.deb ... 134s Unpacking libcurl4t64:armhf (8.12.0+git20250209.89ed161+ds-1ubuntu1) over (8.11.0-1ubuntu2) ... 134s Preparing to unpack .../098-dpkg-dev_1.22.11ubuntu4_all.deb ... 134s Unpacking dpkg-dev (1.22.11ubuntu4) over (1.22.11ubuntu3) ... 135s Preparing to unpack .../099-libdpkg-perl_1.22.11ubuntu4_all.deb ... 135s Unpacking libdpkg-perl (1.22.11ubuntu4) over (1.22.11ubuntu3) ... 135s Preparing to unpack .../100-make_4.4.1-1_armhf.deb ... 135s Unpacking make (4.4.1-1) over (4.3-4.1build2) ... 135s Preparing to unpack .../101-libarchive13t64_3.7.7-0ubuntu1_armhf.deb ... 135s Unpacking libarchive13t64:armhf (3.7.7-0ubuntu1) over (3.7.4-1.1) ... 135s Preparing to unpack .../102-libjson-glib-1.0-common_1.10.6+ds-1_all.deb ... 135s Unpacking libjson-glib-1.0-common (1.10.6+ds-1) over (1.10.0+ds-3) ... 135s Preparing to unpack .../103-libjson-glib-1.0-0_1.10.6+ds-1_armhf.deb ... 135s Unpacking libjson-glib-1.0-0:armhf (1.10.6+ds-1) over (1.10.0+ds-3) ... 135s Preparing to unpack .../104-fwupd_2.0.5-1_armhf.deb ... 135s Unpacking fwupd (2.0.5-1) over (2.0.2-1) ... 135s Preparing to unpack .../105-libfwupd3_2.0.5-1_armhf.deb ... 135s Unpacking libfwupd3:armhf (2.0.5-1) over (2.0.2-1) ... 135s Preparing to unpack .../106-polkitd_126-2_armhf.deb ... 135s Unpacking polkitd (126-2) over (125-2ubuntu1) ... 136s Preparing to unpack .../107-libpolkit-agent-1-0_126-2_armhf.deb ... 136s Unpacking libpolkit-agent-1-0:armhf (126-2) over (125-2ubuntu1) ... 136s Preparing to unpack .../108-libpolkit-gobject-1-0_126-2_armhf.deb ... 136s Unpacking libpolkit-gobject-1-0:armhf (126-2) over (125-2ubuntu1) ... 136s Preparing to unpack .../109-libprotobuf-c1_1.5.1-1ubuntu1_armhf.deb ... 136s Unpacking libprotobuf-c1:armhf (1.5.1-1ubuntu1) over (1.4.1-1ubuntu4) ... 136s Preparing to unpack .../110-libqmi-proxy_1.35.6-1_armhf.deb ... 136s Unpacking libqmi-proxy (1.35.6-1) over (1.35.2-0ubuntu2) ... 136s Preparing to unpack .../111-libqmi-glib5_1.35.6-1_armhf.deb ... 136s Unpacking libqmi-glib5:armhf (1.35.6-1) over (1.35.2-0ubuntu2) ... 136s Preparing to unpack .../112-gnupg-l10n_2.4.4-2ubuntu22_all.deb ... 136s Unpacking gnupg-l10n (2.4.4-2ubuntu22) over (2.4.4-2ubuntu18) ... 136s Preparing to unpack .../113-htop_3.3.0-5_armhf.deb ... 136s Unpacking htop (3.3.0-5) over (3.3.0-4build1) ... 136s Preparing to unpack .../114-libblockdev-utils3_3.3.0-1_armhf.deb ... 136s Unpacking libblockdev-utils3:armhf (3.3.0-1) over (3.2.1-1) ... 136s Preparing to unpack .../115-libnspr4_2%3a4.36-1ubuntu1_armhf.deb ... 136s Unpacking libnspr4:armhf (2:4.36-1ubuntu1) over (2:4.35-1.1ubuntu2) ... 136s Preparing to unpack .../116-libnss3_2%3a3.106-1ubuntu1_armhf.deb ... 136s Unpacking libnss3:armhf (2:3.106-1ubuntu1) over (2:3.103-1) ... 136s Preparing to unpack .../117-libgpgme11t64_1.24.1-4ubuntu1_armhf.deb ... 136s Unpacking libgpgme11t64:armhf (1.24.1-4ubuntu1) over (1.24.0-2ubuntu1) ... 136s Preparing to unpack .../118-libvolume-key1_0.3.12-9_armhf.deb ... 136s Unpacking libvolume-key1:armhf (0.3.12-9) over (0.3.12-8) ... 136s Preparing to unpack .../119-libblockdev-crypto3_3.3.0-1_armhf.deb ... 136s Unpacking libblockdev-crypto3:armhf (3.3.0-1) over (3.2.1-1) ... 136s Preparing to unpack .../120-libblockdev-fs3_3.3.0-1_armhf.deb ... 136s Unpacking libblockdev-fs3:armhf (3.3.0-1) over (3.2.1-1) ... 136s Preparing to unpack .../121-libblockdev-loop3_3.3.0-1_armhf.deb ... 136s Unpacking libblockdev-loop3:armhf (3.3.0-1) over (3.2.1-1) ... 136s Preparing to unpack .../122-libblockdev-mdraid3_3.3.0-1_armhf.deb ... 136s Unpacking libblockdev-mdraid3:armhf (3.3.0-1) over (3.2.1-1) ... 136s Preparing to unpack .../123-libnvme1t64_1.11.1-1build1_armhf.deb ... 136s Unpacking libnvme1t64 (1.11.1-1build1) over (1.11.1-1) ... 136s Preparing to unpack .../124-libblockdev-nvme3_3.3.0-1_armhf.deb ... 136s Unpacking libblockdev-nvme3:armhf (3.3.0-1) over (3.2.1-1) ... 136s Preparing to unpack .../125-libblockdev-part3_3.3.0-1_armhf.deb ... 136s Unpacking libblockdev-part3:armhf (3.3.0-1) over (3.2.1-1) ... 136s Preparing to unpack .../126-libblockdev-swap3_3.3.0-1_armhf.deb ... 136s Unpacking libblockdev-swap3:armhf (3.3.0-1) over (3.2.1-1) ... 136s Preparing to unpack .../127-libblockdev3_3.3.0-1_armhf.deb ... 136s Unpacking libblockdev3:armhf (3.3.0-1) over (3.2.1-1) ... 137s Preparing to unpack .../128-libftdi1-2_1.5-8_armhf.deb ... 137s Unpacking libftdi1-2:armhf (1.5-8) over (1.5-7build1) ... 137s Preparing to unpack .../129-libgstreamer1.0-0_1.25.50-1_armhf.deb ... 137s Unpacking libgstreamer1.0-0:armhf (1.25.50-1) over (1.24.9-1) ... 137s Preparing to unpack .../130-libgudev-1.0-0_1%3a238-6_armhf.deb ... 137s Unpacking libgudev-1.0-0:armhf (1:238-6) over (1:238-5ubuntu1) ... 137s Selecting previously unselected package libicu76:armhf. 137s Preparing to unpack .../131-libicu76_76.1-1ubuntu2_armhf.deb ... 137s Unpacking libicu76:armhf (76.1-1ubuntu2) ... 137s Preparing to unpack .../132-libsasl2-modules_2.1.28+dfsg1-8build1_armhf.deb ... 137s Unpacking libsasl2-modules:armhf (2.1.28+dfsg1-8build1) over (2.1.28+dfsg1-8) ... 137s Preparing to unpack .../133-udisks2_2.10.1-11ubuntu2_armhf.deb ... 137s Unpacking udisks2 (2.10.1-11ubuntu2) over (2.10.1-11ubuntu1) ... 137s Preparing to unpack .../134-libudisks2-0_2.10.1-11ubuntu2_armhf.deb ... 137s Unpacking libudisks2-0:armhf (2.10.1-11ubuntu2) over (2.10.1-11ubuntu1) ... 137s Preparing to unpack .../135-libwrap0_7.6.q-35_armhf.deb ... 137s Unpacking libwrap0:armhf (7.6.q-35) over (7.6.q-33) ... 137s Selecting previously unselected package linux-headers-6.12.0-15. 137s Preparing to unpack .../136-linux-headers-6.12.0-15_6.12.0-15.15_all.deb ... 137s Unpacking linux-headers-6.12.0-15 (6.12.0-15.15) ... 140s Selecting previously unselected package linux-headers-6.12.0-15-generic. 140s Preparing to unpack .../137-linux-headers-6.12.0-15-generic_6.12.0-15.15_armhf.deb ... 140s Unpacking linux-headers-6.12.0-15-generic (6.12.0-15.15) ... 142s Preparing to unpack .../138-linux-headers-generic_6.12.0-15.15+1_armhf.deb ... 142s Unpacking linux-headers-generic (6.12.0-15.15+1) over (6.11.0-8.8) ... 142s Preparing to unpack .../139-pollinate_4.33-4ubuntu2_all.deb ... 142s Unpacking pollinate (4.33-4ubuntu2) over (4.33-4ubuntu1) ... 142s Preparing to unpack .../140-python3-babel_2.17.0-1_all.deb ... 142s /usr/bin/py3clean:101: DeprecationWarning: glob.glob1 is deprecated and will be removed in Python 3.15. Use glob.glob and pass a directory to its root_dir argument instead. 142s for fn in glob1(directory, "%s.*" % fname): 142s Unpacking python3-babel (2.17.0-1) over (2.16.0-1) ... 142s Preparing to unpack .../141-python-babel-localedata_2.17.0-1_all.deb ... 142s Unpacking python-babel-localedata (2.17.0-1) over (2.16.0-1) ... 142s Preparing to unpack .../142-python3-certifi_2025.1.31+ds-1_all.deb ... 142s /usr/bin/py3clean:101: DeprecationWarning: glob.glob1 is deprecated and will be removed in Python 3.15. Use glob.glob and pass a directory to its root_dir argument instead. 142s for fn in glob1(directory, "%s.*" % fname): 142s Unpacking python3-certifi (2025.1.31+ds-1) over (2024.8.30+dfsg-1) ... 143s Preparing to unpack .../143-python3-chardet_5.2.0+dfsg-2_all.deb ... 143s /usr/bin/py3clean:101: DeprecationWarning: glob.glob1 is deprecated and will be removed in Python 3.15. Use glob.glob and pass a directory to its root_dir argument instead. 143s for fn in glob1(directory, "%s.*" % fname): 143s Unpacking python3-chardet (5.2.0+dfsg-2) over (5.2.0+dfsg-1) ... 143s Preparing to unpack .../144-python3-idna_3.10-1_all.deb ... 143s /usr/bin/py3clean:101: DeprecationWarning: glob.glob1 is deprecated and will be removed in Python 3.15. Use glob.glob and pass a directory to its root_dir argument instead. 143s for fn in glob1(directory, "%s.*" % fname): 143s Unpacking python3-idna (3.10-1) over (3.8-2) ... 143s Preparing to unpack .../145-python3-more-itertools_10.6.0-1_all.deb ... 143s /usr/bin/py3clean:101: DeprecationWarning: glob.glob1 is deprecated and will be removed in Python 3.15. Use glob.glob and pass a directory to its root_dir argument instead. 143s for fn in glob1(directory, "%s.*" % fname): 143s Unpacking python3-more-itertools (10.6.0-1) over (10.5.0-1) ... 143s Preparing to unpack .../146-python3-openssl_25.0.0-1_all.deb ... 143s /usr/bin/py3clean:101: DeprecationWarning: glob.glob1 is deprecated and will be removed in Python 3.15. Use glob.glob and pass a directory to its root_dir argument instead. 143s for fn in glob1(directory, "%s.*" % fname): 143s Unpacking python3-openssl (25.0.0-1) over (24.2.1-1) ... 143s Preparing to unpack .../147-python3-pkg-resources_75.6.0-1_all.deb ... 143s /usr/bin/py3clean:101: DeprecationWarning: glob.glob1 is deprecated and will be removed in Python 3.15. Use glob.glob and pass a directory to its root_dir argument instead. 143s for fn in glob1(directory, "%s.*" % fname): 143s Unpacking python3-pkg-resources (75.6.0-1) over (75.2.0-1) ... 143s Preparing to unpack .../148-python3-setuptools_75.6.0-1_all.deb ... 143s /usr/bin/py3clean:101: DeprecationWarning: glob.glob1 is deprecated and will be removed in Python 3.15. Use glob.glob and pass a directory to its root_dir argument instead. 143s for fn in glob1(directory, "%s.*" % fname): 143s Unpacking python3-setuptools (75.6.0-1) over (75.2.0-1) ... 143s Preparing to unpack .../149-software-properties-common_0.108_all.deb ... 144s /usr/bin/py3clean:101: DeprecationWarning: glob.glob1 is deprecated and will be removed in Python 3.15. Use glob.glob and pass a directory to its root_dir argument instead. 144s for fn in glob1(directory, "%s.*" % fname): 144s Unpacking software-properties-common (0.108) over (0.105) ... 144s Preparing to unpack .../150-python3-software-properties_0.108_all.deb ... 144s /usr/bin/py3clean:101: DeprecationWarning: glob.glob1 is deprecated and will be removed in Python 3.15. Use glob.glob and pass a directory to its root_dir argument instead. 144s for fn in glob1(directory, "%s.*" % fname): 144s Unpacking python3-software-properties (0.108) over (0.105) ... 144s Preparing to unpack .../151-python3-urllib3_2.3.0-1_all.deb ... 144s /usr/bin/py3clean:101: DeprecationWarning: glob.glob1 is deprecated and will be removed in Python 3.15. Use glob.glob and pass a directory to its root_dir argument instead. 144s for fn in glob1(directory, "%s.*" % fname): 144s Unpacking python3-urllib3 (2.3.0-1) over (2.0.7-2ubuntu0.1) ... 144s Preparing to unpack .../152-python3-wadllib_2.0.0-2_all.deb ... 144s /usr/bin/py3clean:101: DeprecationWarning: glob.glob1 is deprecated and will be removed in Python 3.15. Use glob.glob and pass a directory to its root_dir argument instead. 144s for fn in glob1(directory, "%s.*" % fname): 144s Unpacking python3-wadllib (2.0.0-2) over (2.0.0-1) ... 144s Preparing to unpack .../153-unattended-upgrades_2.12ubuntu2_all.deb ... 144s Unpacking unattended-upgrades (2.12ubuntu2) over (2.9.1+nmu4ubuntu1) ... 144s dpkg: warning: unable to delete old directory '/lib/systemd/system-sleep': Directory not empty 144s Preparing to unpack .../154-xfsprogs_6.8.0-2.2ubuntu3_armhf.deb ... 144s Unpacking xfsprogs (6.8.0-2.2ubuntu3) over (6.8.0-2.2ubuntu2) ... 144s Preparing to unpack .../155-zstd_1.5.6+dfsg-2_armhf.deb ... 144s Unpacking zstd (1.5.6+dfsg-2) over (1.5.6+dfsg-1) ... 144s Preparing to unpack .../156-cloud-init_25.1~3geb1965a4-0ubuntu1_all.deb ... 144s Unpacking cloud-init (25.1~3geb1965a4-0ubuntu1) over (24.4-0ubuntu1) ... 144s Preparing to unpack .../157-kpartx_0.9.9-1ubuntu4_armhf.deb ... 144s Unpacking kpartx (0.9.9-1ubuntu4) over (0.9.9-1ubuntu3) ... 144s Preparing to unpack .../158-multipath-tools_0.9.9-1ubuntu4_armhf.deb ... 144s Unpacking multipath-tools (0.9.9-1ubuntu4) over (0.9.9-1ubuntu3) ... 145s Setting up libip4tc2:armhf (1.8.11-2ubuntu1) ... 145s Setting up powermgmt-base (1.38) ... 145s Setting up distro-info (1.13) ... 145s Setting up libibverbs1:armhf (55.0-1ubuntu1) ... 145s Setting up libxdmcp6:armhf (1:1.1.5-1) ... 145s Setting up pci.ids (0.0~2025.02.05-1) ... 145s Setting up libnewt0.52:armhf (0.52.24-4ubuntu1) ... 145s Setting up apt-utils (2.9.28) ... 145s Setting up bsdextrautils (2.40.2-14ubuntu1) ... 145s Setting up init (1.68) ... 145s Setting up ibverbs-providers:armhf (55.0-1ubuntu1) ... 145s Setting up libyaml-0-2:armhf (0.2.5-2) ... 145s Setting up libip6tc2:armhf (1.8.11-2ubuntu1) ... 145s Setting up python3.12-gdbm (3.12.9-1) ... 145s Setting up libedit2:armhf (3.1-20250104-1) ... 145s Setting up libsasl2-modules:armhf (2.1.28+dfsg1-8build1) ... 145s Setting up netcat-openbsd (1.228-1) ... 145s Setting up libpython3.12-minimal:armhf (3.12.9-1) ... 145s Setting up binutils-common:armhf (2.44-1ubuntu1) ... 145s Setting up libctf-nobfd0:armhf (2.44-1ubuntu1) ... 145s Setting up gettext-base (0.23.1-1) ... 145s Setting up libnss-systemd:armhf (257.2-3ubuntu1) ... 145s Setting up libnftnl11:armhf (1.2.8-1) ... 145s Setting up krb5-locales (1.21.3-4ubuntu1) ... 145s Setting up libcom-err2:armhf (1.47.2-1ubuntu1) ... 145s Setting up lshw (02.19.git.2021.06.19.996aaad9c7-2.1ubuntu1) ... 145s Setting up locales (2.41-1ubuntu1) ... 145s Installing new version of config file /etc/locale.alias ... 145s Generating locales (this might take a while)... 148s en_US.UTF-8... done 148s Generation complete. 148s Setting up libldap-common (2.6.9+dfsg-1~exp2ubuntu1) ... 148s Installing new version of config file /etc/ldap/ldap.conf ... 148s Setting up libprotobuf-c1:armhf (1.5.1-1ubuntu1) ... 148s Setting up libsframe1:armhf (2.44-1ubuntu1) ... 148s Setting up python-babel-localedata (2.17.0-1) ... 148s Setting up libkrb5support0:armhf (1.21.3-4ubuntu1) ... 148s Setting up libsasl2-modules-db:armhf (2.1.28+dfsg1-8build1) ... 148s Setting up tzdata (2024b-6ubuntu1) ... 148s 148s Current default time zone: 'Etc/UTC' 148s Local time is now: Sun Feb 16 00:49:57 UTC 2025. 148s Universal Time is now: Sun Feb 16 00:49:57 UTC 2025. 148s Run 'dpkg-reconfigure tzdata' if you wish to change it. 148s 148s Setting up eject (2.40.2-14ubuntu1) ... 148s Setting up apparmor (4.1.0~beta1-0ubuntu5) ... 148s apparmor_parser: Unable to replace "lsb_release". apparmor_parser: Access denied. You need policy admin privileges to manage profiles. 148s 148s apparmor_parser: Unable to replace "kmod". apparmor_parser: Access denied. You need policy admin privileges to manage profiles. 148s 148s apparmor_parser: Unable to replace "nvidia_modprobe". apparmor_parser: Access denied. You need policy admin privileges to manage profiles. 148s 149s Reloading AppArmor profiles 149s /sbin/apparmor_parser: Unable to replace "1password". /sbin/apparmor_parser: Access denied. You need policy admin privileges to manage profiles. 149s 149s /sbin/apparmor_parser: Unable to replace "Discord". /sbin/apparmor_parser: Access denied. You need policy admin privileges to manage profiles. 149s 149s /sbin/apparmor_parser: Unable to replace "QtWebEngineProcess". /sbin/apparmor_parser: Access denied. You need policy admin privileges to manage profiles. 149s 149s /sbin/apparmor_parser: Unable to replace "MongoDB Compass". /sbin/apparmor_parser: Access denied. You need policy admin privileges to manage profiles. 149s 149s /sbin/apparmor_parser: Unable to replace "balena-etcher". /sbin/apparmor_parser: Access denied. You need policy admin privileges to manage profiles. 149s 149s /sbin/apparmor_parser: Unable to replace "brave". /sbin/apparmor_parser: Access denied. You need policy admin privileges to manage profiles. 149s 149s /sbin/apparmor_parser: Unable to replace "buildah". /sbin/apparmor_parser: Access denied. You need policy admin privileges to manage profiles. 149s 149s /sbin/apparmor_parser: Unable to replace "busybox". /sbin/apparmor_parser: Access denied. You need policy admin privileges to manage profiles. 149s 149s /sbin/apparmor_parser: Unable to replace "cam". /sbin/apparmor_parser: Access denied. You need policy admin privileges to manage profiles. 149s 149s /sbin/apparmor_parser: Unable to replace "ch-checkns". /sbin/apparmor_parser: Access denied. You need policy admin privileges to manage profiles. 149s 149s /sbin/apparmor_parser: Unable to replace "ch-run". /sbin/apparmor_parser: Access denied. You need policy admin privileges to manage profiles. 149s 149s /sbin/apparmor_parser: Unable to replace "chrome". /sbin/apparmor_parser: Access denied. You need policy admin privileges to manage profiles. 149s 149s /sbin/apparmor_parser: Unable to replace "chromium". /sbin/apparmor_parser: Access denied. You need policy admin privileges to manage profiles. 149s 149s /sbin/apparmor_parser: Unable to replace "vscode". /sbin/apparmor_parser: Access denied. You need policy admin privileges to manage profiles. 149s 149s /sbin/apparmor_parser: Unable to replace "crun". /sbin/apparmor_parser: Access denied. You need policy admin privileges to manage profiles. 149s 149s /sbin/apparmor_parser: Unable to replace "devhelp". /sbin/apparmor_parser: Access denied. You need policy admin privileges to manage profiles. 149s 149s /sbin/apparmor_parser: Unable to replace "element-desktop". /sbin/apparmor_parser: Access denied. You need policy admin privileges to manage profiles. 149s 149s /sbin/apparmor_parser: Unable to replace "epiphany". /sbin/apparmor_parser: Access denied. You need policy admin privileges to manage profiles. 149s 149s /sbin/apparmor_parser: Unable to replace "evolution". /sbin/apparmor_parser: Access denied. You need policy admin privileges to manage profiles. 149s 149s /sbin/apparmor_parser: Unable to replace "firefox". /sbin/apparmor_parser: Access denied. You need policy admin privileges to manage profiles. 149s 149s /sbin/apparmor_parser: Unable to replace "flatpak". /sbin/apparmor_parser: Access denied. You need policy admin privileges to manage profiles. 149s 149s /sbin/apparmor_parser: Unable to replace "foliate". /sbin/apparmor_parser: Access denied. You need policy admin privileges to manage profiles. 149s 149s /sbin/apparmor_parser: Unable to replace "geary". /sbin/apparmor_parser: Access denied. You need policy admin privileges to manage profiles. 149s 149s /sbin/apparmor_parser: Unable to replace "github-desktop". /sbin/apparmor_parser: Access denied. You need policy admin privileges to manage profiles. 149s 149s /sbin/apparmor_parser: Unable to replace "ipa_verify". /sbin/apparmor_parser: Access denied. You need policy admin privileges to manage profiles. 149s 149s /sbin/apparmor_parser: Unable to replace "goldendict". /sbin/apparmor_parser: Access denied. You need policy admin privileges to manage profiles. 149s 149s /sbin/apparmor_parser: Unable to replace "kchmviewer". /sbin/apparmor_parser: Access denied. You need policy admin privileges to manage profiles. 149s 149s /sbin/apparmor_parser: Unable to replace "keybase". /sbin/apparmor_parser: Access denied. You need policy admin privileges to manage profiles. 149s 149s /sbin/apparmor_parser: Unable to replace "lc-compliance". /sbin/apparmor_parser: Access denied. You need policy admin privileges to manage profiles. 149s 149s /sbin/apparmor_parser: Unable to replace "libcamerify". /sbin/apparmor_parser: Access denied. You need policy admin privileges to manage profiles. 149s 149s /sbin/apparmor_parser: Unable to replace "linux-sandbox". /sbin/apparmor_parser: Access denied. You need policy admin privileges to manage profiles. 149s 149s /sbin/apparmor_parser: Unable to replace "loupe". /sbin/apparmor_parser: Access denied. You need policy admin privileges to manage profiles. 149s 149s /sbin/apparmor_parser: Unable to replace "lxc-attach". /sbin/apparmor_parser: Access denied. You need policy admin privileges to manage profiles. 149s 149s /sbin/apparmor_parser: Unable to replace "lxc-create". /sbin/apparmor_parser: Access denied. You need policy admin privileges to manage profiles. 149s 149s /sbin/apparmor_parser: Unable to replace "lxc-destroy". /sbin/apparmor_parser: Access denied. You need policy admin privileges to manage profiles. 149s 149s /sbin/apparmor_parser: Unable to replace "lxc-execute". /sbin/apparmor_parser: Access denied. You need policy admin privileges to manage profiles. 149s 149s /sbin/apparmor_parser: Unable to replace "lxc-stop". /sbin/apparmor_parser: Access denied. You need policy admin privileges to manage profiles. 149s 149s /sbin/apparmor_parser: Unable to replace "lxc-unshare". /sbin/apparmor_parser: Access denied. You need policy admin privileges to manage profiles. 149s 149s /sbin/apparmor_parser: Unable to replace "lxc-usernsexec". /sbin/apparmor_parser: Access denied. You need policy admin privileges to manage profiles. 149s 149s /sbin/apparmor_parser: Unable to replace "mmdebstrap". /sbin/apparmor_parser: Access denied. You need policy admin privileges to manage profiles. 149s 149s /sbin/apparmor_parser: Unable to replace "msedge". /sbin/apparmor_parser: Access denied. You need policy admin privileges to manage profiles. 149s 149s /sbin/apparmor_parser: Unable to replace "nautilus". /sbin/apparmor_parser: Access denied. You need policy admin privileges to manage profiles. 149s 149s /sbin/apparmor_parser: Unable to replace "notepadqq". /sbin/apparmor_parser: Access denied. You need policy admin privileges to manage profiles. 149s 149s /sbin/apparmor_parser: Unable to replace "obsidian". /sbin/apparmor_parser: Access denied. You need policy admin privileges to manage profiles. 149s 149s /sbin/apparmor_parser: Unable to replace "opam". /sbin/apparmor_parser: Access denied. You need policy admin privileges to manage profiles. 149s 149s /sbin/apparmor_parser: Unable to replace "opera". /sbin/apparmor_parser: Access denied. You need policy admin privileges to manage profiles. 149s 149s /sbin/apparmor_parser: Unable to replace "pageedit". /sbin/apparmor_parser: Access denied. You need policy admin privileges to manage profiles. 149s 149s /sbin/apparmor_parser: Unable to replace "podman". /sbin/apparmor_parser: Access denied. You need policy admin privileges to manage profiles. 149s 149s /sbin/apparmor_parser: Unable to replace "polypane". /sbin/apparmor_parser: Access denied. You need policy admin privileges to manage profiles. 149s 149s /sbin/apparmor_parser: Unable to replace "privacybrowser". /sbin/apparmor_parser: Access denied. You need policy admin privileges to manage profiles. 149s 149s /sbin/apparmor_parser: Unable to replace "qcam". /sbin/apparmor_parser: Access denied. You need policy admin privileges to manage profiles. 149s 149s /sbin/apparmor_parser: Unable to replace "qmapshack". /sbin/apparmor_parser: Access denied. You need policy admin privileges to manage profiles. 149s 149s /sbin/apparmor_parser: Unable to replace "QtWebEngineProcess". /sbin/apparmor_parser: Access denied. You need policy admin privileges to manage profiles. 149s 149s /sbin/apparmor_parser: Unable to replace "plasmashell". /sbin/apparmor_parser: Access denied. You need policy admin privileges to manage profiles. 149s 149s /sbin/apparmor_parser: Unable to replace "qutebrowser". /sbin/apparmor_parser: Access denied. You need policy admin privileges to manage profiles. 149s 149s /sbin/apparmor_parser: Unable to replace "rpm". /sbin/apparmor_parser: Unable to replace "rootlesskit". /sbin/apparmor_parser: Unable to replace "rssguard". /sbin/apparmor_parser: Access denied. You need policy admin privileges to manage profiles. 149s 149s /sbin/apparmor_parser: Unable to replace "lsb_release". /sbin/apparmor_parser: Access denied. You need policy admin privileges to manage profiles. 149s 149s /sbin/apparmor_parser: Access denied. You need policy admin privileges to manage profiles. 149s 149s /sbin/apparmor_parser: Access denied. You need policy admin privileges to manage profiles. 149s 149s /sbin/apparmor_parser: Unable to replace "runc". /sbin/apparmor_parser: Access denied. You need policy admin privileges to manage profiles. 149s 149s /sbin/apparmor_parser: Unable to replace "sbuild". /sbin/apparmor_parser: Access denied. You need policy admin privileges to manage profiles. 149s 149s /sbin/apparmor_parser: Unable to replace "sbuild-abort". /sbin/apparmor_parser: Access denied. You need policy admin privileges to manage profiles. 149s 149s /sbin/apparmor_parser: Unable to replace "sbuild-apt". /sbin/apparmor_parser: Access denied. You need policy admin privileges to manage profiles. 149s 149s /sbin/apparmor_parser: Unable to replace "sbuild-adduser". /sbin/apparmor_parser: Access denied. You need policy admin privileges to manage profiles. 149s 149s /sbin/apparmor_parser: Unable to replace "sbuild-checkpackages". /sbin/apparmor_parser: Access denied. You need policy admin privileges to manage profiles. 149s 149s /sbin/apparmor_parser: Unable to replace "sbuild-clean". /sbin/apparmor_parser: Access denied. You need policy admin privileges to manage profiles. 149s 149s /sbin/apparmor_parser: Unable to replace "sbuild-createchroot". /sbin/apparmor_parser: Access denied. You need policy admin privileges to manage profiles. 149s 149s /sbin/apparmor_parser: Unable to replace "sbuild-hold". /sbin/apparmor_parser: Access denied. You need policy admin privileges to manage profiles. 149s 149s /sbin/apparmor_parser: Unable to replace "sbuild-shell". /sbin/apparmor_parser: Unable to replace "sbuild-destroychroot". /sbin/apparmor_parser: Unable to replace "sbuild-unhold". /sbin/apparmor_parser: Access denied. You need policy admin privileges to manage profiles. 149s 149s /sbin/apparmor_parser: Access denied. You need policy admin privileges to manage profiles. 149s 149s /sbin/apparmor_parser: Access denied. You need policy admin privileges to manage profiles. 149s 149s /sbin/apparmor_parser: Unable to replace "sbuild-update". /sbin/apparmor_parser: Access denied. You need policy admin privileges to manage profiles. 149s 149s /sbin/apparmor_parser: Unable to replace "sbuild-distupgrade". /sbin/apparmor_parser: Access denied. You need policy admin privileges to manage profiles. 149s 149s /sbin/apparmor_parser: Unable to replace "signal-desktop". /sbin/apparmor_parser: Unable to replace "scide". /sbin/apparmor_parser: Access denied. You need policy admin privileges to manage profiles. 149s 149s /sbin/apparmor_parser: Unable to replace "slirp4netns". /sbin/apparmor_parser: Unable to replace "sbuild-upgrade". /sbin/apparmor_parser: Access denied. You need policy admin privileges to manage profiles. 149s 149s /sbin/apparmor_parser: Access denied. You need policy admin privileges to manage profiles. 149s 149s /sbin/apparmor_parser: Access denied. You need policy admin privileges to manage profiles. 149s 149s /sbin/apparmor_parser: Unable to replace "slack". /sbin/apparmor_parser: Access denied. You need policy admin privileges to manage profiles. 149s 149s /sbin/apparmor_parser: Unable to replace "steam". /sbin/apparmor_parser: Unable to replace "systemd-coredump". /sbin/apparmor_parser: Unable to replace "surfshark". /sbin/apparmor_parser: Access denied. You need policy admin privileges to manage profiles. 149s 149s /sbin/apparmor_parser: Unable to replace "stress-ng". /sbin/apparmor_parser: Access denied. You need policy admin privileges to manage profiles. 149s 149s /sbin/apparmor_parser: Access denied. You need policy admin privileges to manage profiles. 149s 149s /sbin/apparmor_parser: Unable to replace "thunderbird". /sbin/apparmor_parser: Unable to replace "toybox". /sbin/apparmor_parser: Access denied. You need policy admin privileges to manage profiles. 149s 149s /sbin/apparmor_parser: Access denied. You need policy admin privileges to manage profiles. 149s 149s /sbin/apparmor_parser: Unable to replace "Xorg". /sbin/apparmor_parser: Access denied. You need policy admin privileges to manage profiles. 149s 149s /sbin/apparmor_parser: Access denied. You need policy admin privileges to manage profiles. 149s 149s /sbin/apparmor_parser: Unable to replace "trinity". /sbin/apparmor_parser: Access denied. You need policy admin privileges to manage profiles. 149s 149s /sbin/apparmor_parser: Unable to replace "tup". /sbin/apparmor_parser: Access denied. You need policy admin privileges to manage profiles. 149s 149s /sbin/apparmor_parser: Unable to replace "userbindmount". /sbin/apparmor_parser: Access denied. You need policy admin privileges to manage profiles. 149s 149s /sbin/apparmor_parser: Unable to replace "tuxedo-control-center". /sbin/apparmor_parser: Access denied. You need policy admin privileges to manage profiles. 149s 149s /sbin/apparmor_parser: Unable to replace "unprivileged_userns". /sbin/apparmor_parser: Access denied. You need policy admin privileges to manage profiles. 149s 149s /sbin/apparmor_parser: Unable to replace "kmod". /sbin/apparmor_parser: Access denied. You need policy admin privileges to manage profiles. 149s 149s /sbin/apparmor_parser: Unable to replace "nvidia_modprobe". /sbin/apparmor_parser: Access denied. You need policy admin privileges to manage profiles. 149s 149s /sbin/apparmor_parser: Unable to replace "uwsgi-core". /sbin/apparmor_parser: Access denied. You need policy admin privileges to manage profiles. 149s 149s /sbin/apparmor_parser: Unable to replace "vdens". /sbin/apparmor_parser: Access denied. You need policy admin privileges to manage profiles. 149s 149s /sbin/apparmor_parser: Unable to replace "virtiofsd". /sbin/apparmor_parser: Access denied. You need policy admin privileges to manage profiles. 149s 149s /sbin/apparmor_parser: Unable to replace "vivaldi-bin". /sbin/apparmor_parser: Access denied. You need policy admin privileges to manage profiles. 149s 149s /sbin/apparmor_parser: Unable to replace "vpnns". /sbin/apparmor_parser: Access denied. You need policy admin privileges to manage profiles. 149s 149s /sbin/apparmor_parser: Unable to replace "wike". /sbin/apparmor_parser: Access denied. You need policy admin privileges to manage profiles. 149s 149s /sbin/apparmor_parser: Unable to replace "wpcom". /sbin/apparmor_parser: Access denied. You need policy admin privileges to manage profiles. 149s 149s /sbin/apparmor_parser: Unable to replace "unix-chkpwd". /sbin/apparmor_parser: Access denied. You need policy admin privileges to manage profiles. 149s 149s /sbin/apparmor_parser: Unable to replace "rsyslogd". /sbin/apparmor_parser: Access denied. You need policy admin privileges to manage profiles. 149s 149s /sbin/apparmor_parser: Unable to replace "ubuntu_pro_apt_news". /sbin/apparmor_parser: Access denied. You need policy admin privileges to manage profiles. 149s 149s /sbin/apparmor_parser: Unable to replace "/usr/bin/man". /sbin/apparmor_parser: Access denied. You need policy admin privileges to manage profiles. 149s 150s /sbin/apparmor_parser: Unable to replace "tcpdump". /sbin/apparmor_parser: Access denied. You need policy admin privileges to manage profiles. 150s 150s /sbin/apparmor_parser: Unable to replace "apt_methods". /sbin/apparmor_parser: Access denied. You need policy admin privileges to manage profiles. 150s 150s /sbin/apparmor_parser: Unable to replace "ubuntu_pro_esm_cache". /sbin/apparmor_parser: Access denied. You need policy admin privileges to manage profiles. 150s 150s /sbin/apparmor_parser: Unable to replace "transmission-cli". /sbin/apparmor_parser: Access denied. You need policy admin privileges to manage profiles. 150s 150s Error: At least one profile failed to load 150s Setting up libglib2.0-data (2.83.3-2) ... 150s Setting up busybox-static (1:1.37.0-4ubuntu1) ... 150s Setting up systemd-cryptsetup (257.2-3ubuntu1) ... 150s Setting up libwrap0:armhf (7.6.q-35) ... 150s Setting up libnvme1t64 (1.11.1-1build1) ... 150s Setting up make (4.4.1-1) ... 150s Setting up libnspr4:armhf (2:4.36-1ubuntu1) ... 150s Setting up gnupg-l10n (2.4.4-2ubuntu22) ... 150s Setting up ed (1.21-1) ... 150s Setting up bash-completion (1:2.16.0-7) ... 150s Setting up libncurses6:armhf (6.5+20250125-2) ... 150s Setting up libdbus-1-3:armhf (1.16.0-1ubuntu1) ... 150s Setting up libfribidi0:armhf (1.0.16-1) ... 150s Setting up libpng16-16t64:armhf (1.6.46-4) ... 150s Setting up systemd-timesyncd (257.2-3ubuntu1) ... 150s systemd-time-wait-sync.service is a disabled or a static unit not running, not starting it. 150s Setting up libatomic1:armhf (14.2.0-17ubuntu1) ... 150s Setting up udev (257.2-3ubuntu1) ... 151s Setting up libss2:armhf (1.47.2-1ubuntu1) ... 151s Setting up usb.ids (2025.01.14-1) ... 151s Setting up dhcpcd-base (1:10.1.0-6) ... 151s Installing new version of config file /etc/dhcpcd.conf ... 151s Setting up ucf (3.0049) ... 151s Installing new version of config file /etc/ucf.conf ... 151s Setting up libncursesw6:armhf (6.5+20250125-2) ... 151s Setting up libk5crypto3:armhf (1.21.3-4ubuntu1) ... 151s Setting up busybox-initramfs (1:1.37.0-4ubuntu1) ... 151s Setting up libxtables12:armhf (1.8.11-2ubuntu1) ... 151s Setting up libdpkg-perl (1.22.11ubuntu4) ... 151s Setting up logsave (1.47.2-1ubuntu1) ... 151s Setting up libsasl2-2:armhf (2.1.28+dfsg1-8build1) ... 151s Setting up libfdisk1:armhf (2.40.2-14ubuntu1) ... 151s Setting up libicu74:armhf (74.2-1ubuntu6) ... 151s Setting up nano (8.3-1) ... 151s Installing new version of config file /etc/nanorc ... 151s Setting up libdevmapper1.02.1:armhf (2:1.02.201-1ubuntu1) ... 151s Setting up whiptail (0.52.24-4ubuntu1) ... 151s Setting up python-apt-common (2.9.8) ... 151s Setting up dracut-install (106-2ubuntu1) ... 151s Setting up dmsetup (2:1.02.201-1ubuntu1) ... 151s Setting up uuid-runtime (2.40.2-14ubuntu1) ... 152s uuidd.service is a disabled or a static unit not running, not starting it. 152s Setting up xauth (1:1.1.2-1.1) ... 152s Setting up groff-base (1.23.0-7) ... 152s Setting up libtraceevent1:armhf (1:1.8.4-2) ... 152s Setting up dbus-session-bus-common (1.16.0-1ubuntu1) ... 152s Setting up kpartx (0.9.9-1ubuntu4) ... 152s Setting up libpcap0.8t64:armhf (1.10.5-2ubuntu1) ... 152s Setting up libjson-glib-1.0-common (1.10.6+ds-1) ... 152s Setting up mawk (1.3.4.20250131-1) ... 152s Setting up libkrb5-3:armhf (1.21.3-4ubuntu1) ... 152s Setting up libusb-1.0-0:armhf (2:1.0.27-2) ... 152s Setting up libicu76:armhf (76.1-1ubuntu2) ... 152s Setting up linux-headers-6.12.0-15 (6.12.0-15.15) ... 152s Setting up keyboard-configuration (1.226ubuntu3) ... 153s Your console font configuration will be updated the next time your system 153s boots. If you want to update it now, run 'setupcon' from a virtual console. 153s update-initramfs: deferring update (trigger activated) 153s Setting up libbinutils:armhf (2.44-1ubuntu1) ... 153s Setting up dbus-system-bus-common (1.16.0-1ubuntu1) ... 153s Setting up openssl (3.4.0-1ubuntu2) ... 153s Installing new version of config file /etc/ssl/openssl.cnf ... 153s Setting up libgpg-error-l10n (1.51-3) ... 153s Setting up iputils-ping (3:20240905-1ubuntu1) ... 153s Setting up readline-common (8.2-6) ... 153s Setting up publicsuffix (20250108.1153-0.1) ... 153s Setting up libxml2:armhf (2.12.7+dfsg+really2.9.14-0.2ubuntu3) ... 153s Setting up zstd (1.5.6+dfsg-2) ... 153s Setting up libldap2:armhf (2.6.9+dfsg-1~exp2ubuntu1) ... 153s Setting up dbus-bin (1.16.0-1ubuntu1) ... 153s Setting up libbpf1:armhf (1:1.5.0-2) ... 153s Setting up iputils-tracepath (3:20240905-1ubuntu1) ... 153s Setting up rsync (3.4.1-0syncable1) ... 154s rsync.service is a disabled or a static unit not running, not starting it. 154s Setting up python3.13-gdbm (3.13.2-1) ... 154s Setting up ethtool (1:6.11-1) ... 154s Setting up gnupg-utils (2.4.4-2ubuntu22) ... 154s Setting up initramfs-tools-bin (0.145ubuntu2) ... 154s Setting up ncurses-term (6.5+20250125-2) ... 154s Setting up login (1:4.16.0-2+really2.40.2-14ubuntu1) ... 154s Setting up cron-daemon-common (3.0pl1-192ubuntu1) ... 154s Setting up libxkbcommon0:armhf (1.7.0-2) ... 154s Setting up libctf0:armhf (2.44-1ubuntu1) ... 154s Setting up pinentry-curses (1.3.1-2ubuntu2) ... 154s Setting up python3.12-minimal (3.12.9-1) ... 155s Setting up libnftables1:armhf (1.1.1-1build1) ... 155s Setting up nftables (1.1.1-1build1) ... 156s Setting up iptables (1.8.11-2ubuntu1) ... 156s Setting up htop (3.3.0-5) ... 156s Setting up iproute2 (6.13.0-1ubuntu1) ... 156s Setting up btrfs-progs (6.12-1build1) ... 156s Setting up cron (3.0pl1-192ubuntu1) ... 157s Setting up rsyslog (8.2412.0-1ubuntu1) ... 157s Installing new version of config file /etc/apparmor.d/usr.sbin.rsyslogd ... 157s info: The user `syslog' is already a member of `adm'. 157s apparmor_parser: Unable to replace "rsyslogd". apparmor_parser: Access denied. You need policy admin privileges to manage profiles. 157s 158s Setting up e2fsprogs (1.47.2-1ubuntu1) ... 158s update-initramfs: deferring update (trigger activated) 159s Setting up libnss3:armhf (2:3.106-1ubuntu1) ... 159s Setting up dbus-daemon (1.16.0-1ubuntu1) ... 159s Setting up multipath-tools (0.9.9-1ubuntu4) ... 159s Setting up libftdi1-2:armhf (1.5-8) ... 159s Setting up ca-certificates (20241223) ... 162s Updating certificates in /etc/ssl/certs... 163s rehash: warning: skipping ca-certificates.crt, it does not contain exactly one certificate or CRL 163s 7 added, 1 removed; done. 163s Setting up libglib2.0-0t64:armhf (2.83.3-2) ... 163s No schema files found: doing nothing. 163s Setting up dbus (1.16.0-1ubuntu1) ... 163s A reboot is required to replace the running dbus-daemon. 163s Please reboot the system when convenient. 163s Setting up libblockdev-utils3:armhf (3.3.0-1) ... 163s Setting up linux-headers-6.12.0-15-generic (6.12.0-15.15) ... 163s Setting up libgssapi-krb5-2:armhf (1.21.3-4ubuntu1) ... 163s Setting up gir1.2-glib-2.0:armhf (2.83.3-2) ... 163s Setting up libreadline8t64:armhf (8.2-6) ... 163s Setting up libblockdev-nvme3:armhf (3.3.0-1) ... 163s Setting up libblockdev-fs3:armhf (3.3.0-1) ... 163s Setting up libtraceevent1-plugin:armhf (1:1.8.4-2) ... 163s Setting up gpgconf (2.4.4-2ubuntu22) ... 163s Setting up libpam-systemd:armhf (257.2-3ubuntu1) ... 164s Setting up libgirepository-1.0-1:armhf (1.82.0-4) ... 164s Setting up console-setup-linux (1.226ubuntu3) ... 165s Setting up initramfs-tools-core (0.145ubuntu2) ... 165s Setting up binutils-arm-linux-gnueabihf (2.44-1ubuntu1) ... 165s Setting up libarchive13t64:armhf (3.7.7-0ubuntu1) ... 165s Setting up libpython3.13-stdlib:armhf (3.13.2-1) ... 165s Setting up gpg (2.4.4-2ubuntu22) ... 165s Setting up libgudev-1.0-0:armhf (1:238-6) ... 165s Setting up libpolkit-gobject-1-0:armhf (126-2) ... 165s Setting up libgstreamer1.0-0:armhf (1.25.50-1) ... 165s Setcap worked! gst-ptp-helper is not suid! 165s Setting up libudisks2-0:armhf (2.10.1-11ubuntu2) ... 165s Setting up libpython3-stdlib:armhf (3.13.1-1~exp2) ... 165s Setting up systemd-resolved (257.2-3ubuntu1) ... 166s Setting up console-setup (1.226ubuntu3) ... 166s update-initramfs: deferring update (trigger activated) 166s Setting up gpg-agent (2.4.4-2ubuntu22) ... 167s Setting up libpython3.12-stdlib:armhf (3.12.9-1) ... 167s Setting up initramfs-tools (0.145ubuntu2) ... 167s update-initramfs: deferring update (trigger activated) 167s Setting up libblockdev-mdraid3:armhf (3.3.0-1) ... 167s Setting up libcurl4t64:armhf (8.12.0+git20250209.89ed161+ds-1ubuntu1) ... 167s Setting up bind9-libs:armhf (1:9.20.0-2ubuntu4) ... 167s Setting up e2fsprogs-l10n (1.47.2-1ubuntu1) ... 167s Setting up python3.13 (3.13.2-1) ... 168s Setting up libblockdev-swap3:armhf (3.3.0-1) ... 168s Setting up python3.12 (3.12.9-1) ... 169s Setting up libblockdev-loop3:armhf (3.3.0-1) ... 169s Setting up gpgsm (2.4.4-2ubuntu22) ... 169s Setting up libcurl3t64-gnutls:armhf (8.12.0+git20250209.89ed161+ds-1ubuntu1) ... 169s Setting up libglib2.0-bin (2.83.3-2) ... 169s Setting up libappstream5:armhf (1.0.4-1) ... 169s Setting up libqmi-glib5:armhf (1.35.6-1) ... 169s Setting up python3 (3.13.1-1~exp2) ... 169s /usr/bin/py3clean:101: DeprecationWarning: glob.glob1 is deprecated and will be removed in Python 3.15. Use glob.glob and pass a directory to its root_dir argument instead. 169s for fn in glob1(directory, "%s.*" % fname): 170s Setting up linux-headers-generic (6.12.0-15.15+1) ... 170s Setting up binutils (2.44-1ubuntu1) ... 170s Setting up libnetplan1:armhf (1.1.2-2ubuntu1) ... 170s Setting up python3-newt:armhf (0.52.24-4ubuntu1) ... 170s Setting up libblockdev3:armhf (3.3.0-1) ... 170s Setting up fdisk (2.40.2-14ubuntu1) ... 170s Setting up dpkg-dev (1.22.11ubuntu4) ... 170s Setting up libjson-glib-1.0-0:armhf (1.10.6+ds-1) ... 170s Setting up libblockdev-part3:armhf (3.3.0-1) ... 170s Setting up dirmngr (2.4.4-2ubuntu22) ... 170s Setting up dbus-user-session (1.16.0-1ubuntu1) ... 170s Setting up python3-jinja2 (3.1.5-2) ... 171s Setting up python3-pygments (2.18.0+dfsg-2) ... 173s Setting up python3-chardet (5.2.0+dfsg-2) ... 173s Setting up appstream (1.0.4-1) ... 175s ✔ Metadata cache was updated successfully. 175s Setting up python3-certifi (2025.1.31+ds-1) ... 175s Setting up gir1.2-girepository-2.0:armhf (1.82.0-4) ... 175s Setting up python3-gi (3.50.0-4) ... 176s Setting up python3-idna (3.10-1) ... 176s Setting up xfsprogs (6.8.0-2.2ubuntu3) ... 176s update-initramfs: deferring update (trigger activated) 177s Setting up keyboxd (2.4.4-2ubuntu22) ... 177s Setting up python3-urllib3 (2.3.0-1) ... 177s Setting up python3-json-pointer (2.4-3) ... 177s Setting up gnupg (2.4.4-2ubuntu22) ... 177s Setting up python3-netplan (1.1.2-2ubuntu1) ... 177s Setting up libpolkit-agent-1-0:armhf (126-2) ... 177s Setting up libgpgme11t64:armhf (1.24.1-4ubuntu1) ... 177s Setting up curl (8.12.0+git20250209.89ed161+ds-1ubuntu1) ... 177s Setting up libvolume-key1:armhf (0.3.12-9) ... 177s Setting up netplan-generator (1.1.2-2ubuntu1) ... 177s Removing 'diversion of /lib/systemd/system-generators/netplan to /lib/systemd/system-generators/netplan.usr-is-merged by netplan-generator' 177s Setting up bind9-host (1:9.20.0-2ubuntu4) ... 177s Setting up python3-distro-info (1.13) ... 178s Setting up polkitd (126-2) ... 178s Setting up python3-more-itertools (10.6.0-1) ... 178s Setting up python3-attr (25.1.0-1) ... 179s Setting up gpg-wks-client (2.4.4-2ubuntu22) ... 179s Setting up libblockdev-crypto3:armhf (3.3.0-1) ... 179s Setting up python3-jwt (2.10.1-2) ... 179s Setting up python3-babel (2.17.0-1) ... 179s Setting up python3-rich (13.9.4-1) ... 180s Setting up python3-gdbm:armhf (3.13.1-1) ... 180s Setting up python3-problem-report (2.31.0-0ubuntu5) ... 180s Setting up python3-apt (2.9.8) ... 180s Setting up python3-jsonpatch (1.32-5) ... 180s Setting up python3-bcrypt (4.2.0-2.1) ... 180s Setting up libqmi-proxy (1.35.6-1) ... 180s Setting up libfwupd3:armhf (2.0.5-1) ... 180s Setting up ufw (0.36.2-9) ... 182s Setting up python3-lazr.uri (1.0.6-5) ... 182s Setting up netplan.io (1.1.2-2ubuntu1) ... 182s Setting up unattended-upgrades (2.12ubuntu2) ... 182s Replacing config file /etc/apt/apt.conf.d/50unattended-upgrades with new version 182s Setting up pollinate (4.33-4ubuntu2) ... 183s Setting up python3-cryptography (43.0.0-1) ... 183s Setting up python3-wadllib (2.0.0-2) ... 184s Setting up bind9-dnsutils (1:9.20.0-2ubuntu4) ... 184s Setting up fwupd (2.0.5-1) ... 184s fwupd-refresh.service is a disabled or a static unit not running, not starting it. 184s fwupd.service is a disabled or a static unit not running, not starting it. 184s Setting up python3-referencing (0.35.1-2ubuntu1) ... 184s Setting up python3-pkg-resources (75.6.0-1) ... 185s Setting up udisks2 (2.10.1-11ubuntu2) ... 185s vda: Failed to write 'change' to '/sys/devices/pci0000:00/0000:00:01.3/0000:04:00.0/virtio2/block/vda/uevent': Permission denied 185s vda1: Failed to write 'change' to '/sys/devices/pci0000:00/0000:00:01.3/0000:04:00.0/virtio2/block/vda/vda1/uevent': Permission denied 185s vda15: Failed to write 'change' to '/sys/devices/pci0000:00/0000:00:01.3/0000:04:00.0/virtio2/block/vda/vda15/uevent': Permission denied 185s vda2: Failed to write 'change' to '/sys/devices/pci0000:00/0000:00:01.3/0000:04:00.0/virtio2/block/vda/vda2/uevent': Permission denied 185s loop0: Failed to write 'change' to '/sys/devices/virtual/block/loop0/uevent': Permission denied 185s loop1: Failed to write 'change' to '/sys/devices/virtual/block/loop1/uevent': Permission denied 185s loop2: Failed to write 'change' to '/sys/devices/virtual/block/loop2/uevent': Permission denied 185s loop3: Failed to write 'change' to '/sys/devices/virtual/block/loop3/uevent': Permission denied 185s loop4: Failed to write 'change' to '/sys/devices/virtual/block/loop4/uevent': Permission denied 185s loop5: Failed to write 'change' to '/sys/devices/virtual/block/loop5/uevent': Permission denied 185s loop6: Failed to write 'change' to '/sys/devices/virtual/block/loop6/uevent': Permission denied 185s loop7: Failed to write 'change' to '/sys/devices/virtual/block/loop7/uevent': Permission denied 185s loop8: Failed to write 'change' to '/sys/devices/virtual/block/loop8/uevent': Permission denied 185s loop9: Failed to write 'change' to '/sys/devices/virtual/block/loop9/uevent': Permission denied 185s Setting up python3-setuptools (75.6.0-1) ... 187s Setting up ubuntu-minimal (1.547) ... 187s Setting up python3-openssl (25.0.0-1) ... 187s Setting up python3-launchpadlib (2.1.0-1) ... 187s Setting up ubuntu-standard (1.547) ... 187s Setting up python3-apport (2.31.0-0ubuntu5) ... 188s Setting up python3-oauthlib (3.2.2-3) ... 188s Setting up python3-software-properties (0.108) ... 188s Setting up python3-jsonschema (4.19.2-6ubuntu1) ... 189s Setting up cloud-init-base (25.1~3geb1965a4-0ubuntu1) ... 189s Installing new version of config file /etc/cloud/templates/sources.list.debian.deb822.tmpl ... 189s Installing new version of config file /etc/cloud/templates/sources.list.ubuntu.deb822.tmpl ... 191s Setting up software-properties-common (0.108) ... 191s Setting up cloud-init (25.1~3geb1965a4-0ubuntu1) ... 191s Setting up apport-core-dump-handler (2.31.0-0ubuntu5) ... 192s Setting up apport (2.31.0-0ubuntu5) ... 193s apport-autoreport.service is a disabled or a static unit not running, not starting it. 193s Processing triggers for shared-mime-info (2.4-5) ... 193s Warning: program compiled against libxml 212 using older 209 193s Processing triggers for sgml-base (1.31) ... 193s Processing triggers for debianutils (5.21) ... 193s Processing triggers for install-info (7.1.1-1) ... 193s Processing triggers for libc-bin (2.41-1ubuntu1) ... 193s Processing triggers for systemd (257.2-3ubuntu1) ... 193s Processing triggers for man-db (2.13.0-1) ... 195s Processing triggers for ca-certificates (20241223) ... 195s Updating certificates in /etc/ssl/certs... 196s 0 added, 0 removed; done. 196s Running hooks in /etc/ca-certificates/update.d... 196s done. 196s Processing triggers for initramfs-tools (0.145ubuntu2) ... 199s Reading package lists... 200s Building dependency tree... 200s Reading state information... 200s Starting pkgProblemResolver with broken count: 0 200s Starting 2 pkgProblemResolver with broken count: 0 200s Done 201s The following packages will be REMOVED: 201s libassuan0* libicu74* libnsl2* libpython3.12-minimal* libpython3.12-stdlib* 201s libunwind8* linux-headers-6.11.0-8* linux-headers-6.11.0-8-generic* 201s python3.12* python3.12-minimal* 201s 0 upgraded, 0 newly installed, 10 to remove and 0 not upgraded. 201s After this operation, 151 MB disk space will be freed. 201s (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 ... 92703 files and directories currently installed.) 201s Removing libassuan0:armhf (2.5.6-1build1) ... 201s Removing libicu74:armhf (74.2-1ubuntu6) ... 201s Removing python3.12 (3.12.9-1) ... 202s Removing libpython3.12-stdlib:armhf (3.12.9-1) ... 202s Removing libnsl2:armhf (1.3.0-3build3) ... 202s Removing python3.12-minimal (3.12.9-1) ... 202s /usr/bin/py3clean:125: DeprecationWarning: glob.glob1 is deprecated and will be removed in Python 3.15. Use glob.glob and pass a directory to its root_dir argument instead. 202s for fn in glob1(directory, "%s.%s.py[co]" % (fname, magic_tag)): 202s Removing libpython3.12-minimal:armhf (3.12.9-1) ... 202s Removing libunwind8:armhf (1.6.2-3.1) ... 202s Removing linux-headers-6.11.0-8-generic (6.11.0-8.8) ... 203s Removing linux-headers-6.11.0-8 (6.11.0-8.8) ... 204s Processing triggers for systemd (257.2-3ubuntu1) ... 204s Processing triggers for man-db (2.13.0-1) ... 204s Processing triggers for libc-bin (2.41-1ubuntu1) ... 204s (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 ... 60247 files and directories currently installed.) 204s Purging configuration files for python3.12-minimal (3.12.9-1) ... 204s Purging configuration files for libpython3.12-minimal:armhf (3.12.9-1) ... 207s autopkgtest [00:50:56]: rebooting testbed after setup commands that affected boot 251s autopkgtest [00:51:40]: testbed running kernel: Linux 6.8.0-49-generic #49~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Wed Nov 6 18:12:14 UTC 2 280s autopkgtest [00:52:09]: @@@@@@@@@@@@@@@@@@@@ apt-source libfprint 319s Get:1 http://ftpmaster.internal/ubuntu plucky/main libfprint 1:1.94.8+tod1-0ubuntu1 (dsc) [2928 B] 319s Get:2 http://ftpmaster.internal/ubuntu plucky/main libfprint 1:1.94.8+tod1-0ubuntu1 (tar) [9278 kB] 319s Get:3 http://ftpmaster.internal/ubuntu plucky/main libfprint 1:1.94.8+tod1-0ubuntu1 (diff) [17.5 kB] 319s gpgv: Signature made Tue Sep 3 05:15:30 2024 UTC 319s gpgv: using RSA key D4C501DA48EB797A081750939449C2F50996635F 319s gpgv: Can't check signature: No public key 319s dpkg-source: warning: cannot verify inline signature for ./libfprint_1.94.8+tod1-0ubuntu1.dsc: no acceptable signature found 322s autopkgtest [00:52:51]: testing package libfprint version 1:1.94.8+tod1-0ubuntu1 325s autopkgtest [00:52:54]: build not needed 329s autopkgtest [00:52:58]: test installed-tests: preparing testbed 331s Reading package lists... 331s Building dependency tree... 331s Reading state information... 332s Starting pkgProblemResolver with broken count: 0 332s Starting 2 pkgProblemResolver with broken count: 0 332s Done 333s The following NEW packages will be installed: 333s fontconfig-config fonts-dejavu-core fonts-dejavu-mono gir1.2-fprint-2.0 333s gir1.2-gusb-1.0 gir1.2-json-1.0 gnome-desktop-testing libcairo2 333s libfontconfig1 libfprint-2-2 libfprint-2-tests libfprint-2-tod1 libfreetype6 333s libgusb2 libpixman-1-0 libumockdev0 libxcb-render0 libxcb-shm0 libxrender1 333s python3-cairo umockdev 333s 0 upgraded, 21 newly installed, 0 to remove and 0 not upgraded. 333s Need to get 9758 kB of archives. 333s After this operation, 32.3 MB of additional disk space will be used. 333s Get:1 http://ftpmaster.internal/ubuntu plucky/main armhf fonts-dejavu-mono all 2.37-8 [502 kB] 333s Get:2 http://ftpmaster.internal/ubuntu plucky/main armhf fonts-dejavu-core all 2.37-8 [835 kB] 333s Get:3 http://ftpmaster.internal/ubuntu plucky/main armhf fontconfig-config armhf 2.15.0-1.1ubuntu2 [37.4 kB] 333s Get:4 http://ftpmaster.internal/ubuntu plucky/main armhf gir1.2-json-1.0 armhf 1.10.6+ds-1 [9998 B] 333s Get:5 http://ftpmaster.internal/ubuntu plucky/main armhf libgusb2 armhf 0.4.9-1 [34.8 kB] 333s Get:6 http://ftpmaster.internal/ubuntu plucky/main armhf gir1.2-gusb-1.0 armhf 0.4.9-1 [7450 B] 333s Get:7 http://ftpmaster.internal/ubuntu plucky/main armhf libpixman-1-0 armhf 0.44.0-3 [183 kB] 333s Get:8 http://ftpmaster.internal/ubuntu plucky/main armhf libfprint-2-tod1 armhf 1:1.94.8+tod1-0ubuntu1 [58.1 kB] 333s Get:9 http://ftpmaster.internal/ubuntu plucky/main armhf libfprint-2-2 armhf 1:1.94.8+tod1-0ubuntu1 [239 kB] 333s Get:10 http://ftpmaster.internal/ubuntu plucky/main armhf gir1.2-fprint-2.0 armhf 1:1.94.8+tod1-0ubuntu1 [7182 B] 333s Get:11 http://ftpmaster.internal/ubuntu plucky/universe armhf gnome-desktop-testing armhf 2021.1-4 [16.2 kB] 333s Get:12 http://ftpmaster.internal/ubuntu plucky/main armhf libfreetype6 armhf 2.13.3+dfsg-1 [330 kB] 334s Get:13 http://ftpmaster.internal/ubuntu plucky/main armhf libfontconfig1 armhf 2.15.0-1.1ubuntu2 [113 kB] 334s Get:14 http://ftpmaster.internal/ubuntu plucky/main armhf libxcb-render0 armhf 1.17.0-2 [15.3 kB] 334s Get:15 http://ftpmaster.internal/ubuntu plucky/main armhf libxcb-shm0 armhf 1.17.0-2 [5774 B] 334s Get:16 http://ftpmaster.internal/ubuntu plucky/main armhf libxrender1 armhf 1:0.9.10-1.1build1 [16.0 kB] 334s Get:17 http://ftpmaster.internal/ubuntu plucky/main armhf libcairo2 armhf 1.18.2-2 [484 kB] 334s Get:18 http://ftpmaster.internal/ubuntu plucky/main armhf python3-cairo armhf 1.26.1-2build1 [129 kB] 334s Get:19 http://ftpmaster.internal/ubuntu plucky/universe armhf libumockdev0 armhf 0.19.1-3 [70.2 kB] 334s Get:20 http://ftpmaster.internal/ubuntu plucky/universe armhf umockdev armhf 0.19.1-3 [76.1 kB] 334s Get:21 http://ftpmaster.internal/ubuntu plucky/universe armhf libfprint-2-tests armhf 1:1.94.8+tod1-0ubuntu1 [6588 kB] 334s Fetched 9758 kB in 1s (7677 kB/s) 334s Selecting previously unselected package fonts-dejavu-mono. 335s (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 ... 60245 files and directories currently installed.) 335s Preparing to unpack .../00-fonts-dejavu-mono_2.37-8_all.deb ... 335s Unpacking fonts-dejavu-mono (2.37-8) ... 335s Selecting previously unselected package fonts-dejavu-core. 335s Preparing to unpack .../01-fonts-dejavu-core_2.37-8_all.deb ... 335s Unpacking fonts-dejavu-core (2.37-8) ... 335s Selecting previously unselected package fontconfig-config. 335s Preparing to unpack .../02-fontconfig-config_2.15.0-1.1ubuntu2_armhf.deb ... 335s Unpacking fontconfig-config (2.15.0-1.1ubuntu2) ... 335s Selecting previously unselected package gir1.2-json-1.0:armhf. 335s Preparing to unpack .../03-gir1.2-json-1.0_1.10.6+ds-1_armhf.deb ... 335s Unpacking gir1.2-json-1.0:armhf (1.10.6+ds-1) ... 335s Selecting previously unselected package libgusb2:armhf. 335s Preparing to unpack .../04-libgusb2_0.4.9-1_armhf.deb ... 335s Unpacking libgusb2:armhf (0.4.9-1) ... 335s Selecting previously unselected package gir1.2-gusb-1.0:armhf. 335s Preparing to unpack .../05-gir1.2-gusb-1.0_0.4.9-1_armhf.deb ... 335s Unpacking gir1.2-gusb-1.0:armhf (0.4.9-1) ... 335s Selecting previously unselected package libpixman-1-0:armhf. 335s Preparing to unpack .../06-libpixman-1-0_0.44.0-3_armhf.deb ... 335s Unpacking libpixman-1-0:armhf (0.44.0-3) ... 335s Selecting previously unselected package libfprint-2-tod1:armhf. 335s Preparing to unpack .../07-libfprint-2-tod1_1%3a1.94.8+tod1-0ubuntu1_armhf.deb ... 335s Unpacking libfprint-2-tod1:armhf (1:1.94.8+tod1-0ubuntu1) ... 335s Selecting previously unselected package libfprint-2-2. 335s Preparing to unpack .../08-libfprint-2-2_1%3a1.94.8+tod1-0ubuntu1_armhf.deb ... 335s Unpacking libfprint-2-2 (1:1.94.8+tod1-0ubuntu1) ... 335s Selecting previously unselected package gir1.2-fprint-2.0:armhf. 335s Preparing to unpack .../09-gir1.2-fprint-2.0_1%3a1.94.8+tod1-0ubuntu1_armhf.deb ... 335s Unpacking gir1.2-fprint-2.0:armhf (1:1.94.8+tod1-0ubuntu1) ... 335s Selecting previously unselected package gnome-desktop-testing. 335s Preparing to unpack .../10-gnome-desktop-testing_2021.1-4_armhf.deb ... 335s Unpacking gnome-desktop-testing (2021.1-4) ... 335s Selecting previously unselected package libfreetype6:armhf. 335s Preparing to unpack .../11-libfreetype6_2.13.3+dfsg-1_armhf.deb ... 335s Unpacking libfreetype6:armhf (2.13.3+dfsg-1) ... 335s Selecting previously unselected package libfontconfig1:armhf. 335s Preparing to unpack .../12-libfontconfig1_2.15.0-1.1ubuntu2_armhf.deb ... 335s Unpacking libfontconfig1:armhf (2.15.0-1.1ubuntu2) ... 335s Selecting previously unselected package libxcb-render0:armhf. 335s Preparing to unpack .../13-libxcb-render0_1.17.0-2_armhf.deb ... 335s Unpacking libxcb-render0:armhf (1.17.0-2) ... 335s Selecting previously unselected package libxcb-shm0:armhf. 335s Preparing to unpack .../14-libxcb-shm0_1.17.0-2_armhf.deb ... 335s Unpacking libxcb-shm0:armhf (1.17.0-2) ... 335s Selecting previously unselected package libxrender1:armhf. 335s Preparing to unpack .../15-libxrender1_1%3a0.9.10-1.1build1_armhf.deb ... 335s Unpacking libxrender1:armhf (1:0.9.10-1.1build1) ... 335s Selecting previously unselected package libcairo2:armhf. 335s Preparing to unpack .../16-libcairo2_1.18.2-2_armhf.deb ... 335s Unpacking libcairo2:armhf (1.18.2-2) ... 335s Selecting previously unselected package python3-cairo. 335s Preparing to unpack .../17-python3-cairo_1.26.1-2build1_armhf.deb ... 335s Unpacking python3-cairo (1.26.1-2build1) ... 335s Selecting previously unselected package libumockdev0:armhf. 335s Preparing to unpack .../18-libumockdev0_0.19.1-3_armhf.deb ... 335s Unpacking libumockdev0:armhf (0.19.1-3) ... 335s Selecting previously unselected package umockdev. 335s Preparing to unpack .../19-umockdev_0.19.1-3_armhf.deb ... 335s Unpacking umockdev (0.19.1-3) ... 336s Selecting previously unselected package libfprint-2-tests. 336s Preparing to unpack .../20-libfprint-2-tests_1%3a1.94.8+tod1-0ubuntu1_armhf.deb ... 336s Unpacking libfprint-2-tests (1:1.94.8+tod1-0ubuntu1) ... 336s Setting up gnome-desktop-testing (2021.1-4) ... 336s Setting up libpixman-1-0:armhf (0.44.0-3) ... 336s Setting up libxrender1:armhf (1:0.9.10-1.1build1) ... 336s Setting up libxcb-render0:armhf (1.17.0-2) ... 336s Setting up libgusb2:armhf (0.4.9-1) ... 336s Setting up libfprint-2-tod1:armhf (1:1.94.8+tod1-0ubuntu1) ... 336s Setting up libxcb-shm0:armhf (1.17.0-2) ... 336s Setting up libfreetype6:armhf (2.13.3+dfsg-1) ... 336s Setting up fonts-dejavu-mono (2.37-8) ... 336s Setting up fonts-dejavu-core (2.37-8) ... 336s Setting up libumockdev0:armhf (0.19.1-3) ... 336s Setting up gir1.2-json-1.0:armhf (1.10.6+ds-1) ... 336s Setting up libfprint-2-2 (1:1.94.8+tod1-0ubuntu1) ... 350s Setting up umockdev (0.19.1-3) ... 350s Setting up fontconfig-config (2.15.0-1.1ubuntu2) ... 350s Setting up gir1.2-gusb-1.0:armhf (0.4.9-1) ... 350s Setting up gir1.2-fprint-2.0:armhf (1:1.94.8+tod1-0ubuntu1) ... 350s Processing triggers for libc-bin (2.41-1ubuntu1) ... 350s Processing triggers for man-db (2.13.0-1) ... 350s Processing triggers for udev (257.2-3ubuntu1) ... 351s Processing triggers for sgml-base (1.31) ... 351s Setting up libfontconfig1:armhf (2.15.0-1.1ubuntu2) ... 351s Setting up libcairo2:armhf (1.18.2-2) ... 351s Setting up python3-cairo (1.26.1-2build1) ... 351s Setting up libfprint-2-tests (1:1.94.8+tod1-0ubuntu1) ... 351s Processing triggers for libc-bin (2.41-1ubuntu1) ... 360s autopkgtest [00:53:29]: test installed-tests: gnome-desktop-testing-runner libfprint-2 360s autopkgtest [00:53:29]: test installed-tests: [----------------------- 362s Running test: libfprint-2/driver-nb1010.test 362s ** (umockdev-run:1844): DEBUG: 00:53:31.461: umockdev.vala:127: Created udev test bed /tmp/umockdev.MKD812 362s ** (umockdev-run:1844): DEBUG: 00:53:31.461: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:01.3/0000:02:00.0/usb1/1-7 362s ** (umockdev-run:1844): DEBUG: 00:53:31.467: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:01.3/0000:02:00.0/usb1/1-7 (subsystem usb) 362s ** (umockdev-run:1844): DEBUG: 00:53:31.471: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.MKD812/dev/bus/usb/001/003 362s ** (umockdev-run:1844): DEBUG: 00:53:31.471: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:01.3/0000:02:00.0/usb1 362s ** (umockdev-run:1844): DEBUG: 00:53:31.477: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:01.3/0000:02:00.0/usb1 (subsystem usb) 362s ** (umockdev-run:1844): DEBUG: 00:53:31.480: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.MKD812/dev/bus/usb/001/001 362s ** (umockdev-run:1844): DEBUG: 00:53:31.480: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:01.3/0000:02:00.0 362s ** (umockdev-run:1844): DEBUG: 00:53:31.483: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:01.3/0000:02:00.0 (subsystem pci) 362s ** (umockdev-run:1844): DEBUG: 00:53:31.487: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:01.3 362s ** (umockdev-run:1844): DEBUG: 00:53:31.488: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:01.3 (subsystem pci) 362s (umockdev-run:1844): GLib-GIO-DEBUG: 00:53:31.495: _g_io_module_get_default: Found default implementation local (GLocalVfs) for ?gio-vfs? 362s (process:1848): libfprint-context-DEBUG: 00:53:31.623: Initializing FpContext (libfprint version 1.94.8+tod1) 362s (process:1848): libfprint-tod-DEBUG: 00:53:31.624: Impossible to load the shared drivers dir Error opening directory “/usr/lib/arm-linux-gnueabihf/libfprint-2/tod-1”: No such file or directory 362s (process:1848): libfprint-context-DEBUG: 00:53:31.627: No driver found for USB device 1D6B:0002 362s (process:1848): libfprint-device-DEBUG: 00:53:31.628: Device reported probe completion 362s (process:1848): libfprint-device-DEBUG: 00:53:31.628: Completing action FPI_DEVICE_ACTION_PROBE in idle! 362s (process:1848): libfprint-device-DEBUG: 00:53:31.628: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 362s (process:1848): libfprint-image_device-DEBUG: 00:53:31.630: Image device open completed 362s (process:1848): libfprint-device-DEBUG: 00:53:31.630: Device reported open completion 362s (process:1848): libfprint-nb1010-DEBUG: 00:53:31.630: nb1010 Initialized 362s (process:1848): libfprint-device-DEBUG: 00:53:31.630: Completing action FPI_DEVICE_ACTION_OPEN in idle! 362s (process:1848): libfprint-device-DEBUG: 00:53:31.630: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 362s (process:1848): libfprint-device-DEBUG: 00:53:31.630: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 362s (process:1848): libfprint-image_device-DEBUG: 00:53:31.630: Activating image device 362s (process:1848): libfprint-image_device-DEBUG: 00:53:31.630: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING 362s (process:1848): libfprint-image_device-DEBUG: 00:53:31.630: Image device activation completed 362s (process:1848): libfprint-image_device-DEBUG: 00:53:31.630: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE 362s (process:1848): libfprint-image_device-DEBUG: 00:53:31.630: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 362s (process:1848): libfprint-SSM-DEBUG: 00:53:31.630: [nb1010] M_LOOP_NUM_STATES entering state 0 362s (process:1848): libfprint-device-DEBUG: 00:53:31.630: Device reported finger status change: FP_FINGER_STATUS_NEEDED 362s (process:1848): libfprint-nb1010-DEBUG: 00:53:31.630: nb1010 Activated 362s (process:1848): libfprint-SSM-DEBUG: 00:53:31.680: [nb1010] M_LOOP_NUM_STATES entering state 1 362s (process:1848): libfprint-SSM-DEBUG: 00:53:31.681: [nb1010] M_LOOP_NUM_STATES entering state 2 362s (process:1848): libfprint-SSM-DEBUG: 00:53:31.681: [nb1010] M_LOOP_NUM_STATES entering state 3 362s (process:1848): libfprint-device-DEBUG: 00:53:31.681: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 362s (process:1848): libfprint-image_device-DEBUG: 00:53:31.681: Image device reported finger status: on 362s (process:1848): libfprint-image_device-DEBUG: 00:53:31.681: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 362s (process:1848): libfprint-SSM-DEBUG: 00:53:31.682: [nb1010] M_LOOP_NUM_STATES entering state 4 362s (process:1848): libfprint-SSM-DEBUG: 00:53:31.683: [nb1010] M_LOOP_NUM_STATES entering state 5 362s (process:1848): libfprint-device-DEBUG: 00:53:31.730: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 362s (process:1848): libfprint-SSM-DEBUG: 00:53:31.730: [nb1010] M_LOOP_NUM_STATES entering state 6 362s (process:1848): libfprint-image_device-DEBUG: 00:53:31.731: Image device captured an image 362s (process:1848): libfprint-image_device-DEBUG: 00:53:31.732: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 362s (process:1848): libfprint-device-DEBUG: 00:53:31.732: Device reported finger status change: FP_FINGER_STATUS_PRESENT 362s (process:1848): libfprint-SSM-DEBUG: 00:53:31.732: [nb1010] M_LOOP_NUM_STATES completed successfully 362s (process:1848): libfprint-nb1010-DEBUG: 00:53:31.732: nb1010 ssm complete cb 362s (process:1848): libfprint-device-DEBUG: 00:53:31.732: Device reported finger status change: FP_FINGER_STATUS_NONE 362s (process:1848): libfprint-image_device-DEBUG: 00:53:31.732: Image device reported finger status: off 362s (process:1848): libfprint-image_device-DEBUG: 00:53:31.732: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 362s (process:1848): libfprint-image_device-DEBUG: 00:53:31.732: Deactivating image device 362s (process:1848): libfprint-image_device-DEBUG: 00:53:31.732: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_DEACTIVATING 362s (process:1848): libfprint-image_device-DEBUG: 00:53:31.732: Image device deactivation completed 362s (process:1848): libfprint-image_device-DEBUG: 00:53:31.732: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE 362s (process:1848): libfprint-nb1010-DEBUG: 00:53:31.732: nb1010 Deactivated 362s (process:1848): libfprint-image-DEBUG: 00:53:31.745: Minutiae scan completed in 0.013073 secs 362s (process:1848): libfprint-device-DEBUG: 00:53:31.745: Device reported capture completion 362s (process:1848): libfprint-device-DEBUG: 00:53:31.745: Completing action FPI_DEVICE_ACTION_CAPTURE in idle! 362s (process:1848): libfprint-device-DEBUG: 00:53:31.745: Updated temperature model after 0.02 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 362s (process:1848): libfprint-image_device-DEBUG: 00:53:31.746: Image device close completed 362s (process:1848): libfprint-device-DEBUG: 00:53:31.746: Device reported close completion 362s (process:1848): libfprint-nb1010-DEBUG: 00:53:31.746: nb1010 Deinitialized 362s (process:1848): libfprint-device-DEBUG: 00:53:31.746: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 362s (process:1848): libfprint-device-DEBUG: 00:53:31.746: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 362s ** (umockdev-run:1844): DEBUG: 00:53:31.850: umockdev.vala:154: Removing test bed /tmp/umockdev.MKD812 362s (umockdev-run:1844): GLib-DEBUG: 00:53:31.859: unsetenv() is not thread-safe and should not be used after threads are created 362s Comparing PNGs /tmp/libfprint-umockdev-test-_wir_rno/capture.png and /usr/share/installed-tests/libfprint-2/nb1010/capture.png 362s PASS: libfprint-2/driver-nb1010.test 362s Running test: libfprint-2/driver-realtek-5816.test 362s ** (umockdev-run:1857): DEBUG: 00:53:31.943: umockdev.vala:127: Created udev test bed /tmp/umockdev.OA8K22 362s ** (umockdev-run:1857): DEBUG: 00:53:31.943: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0/usb1/1-6 362s ** (umockdev-run:1857): DEBUG: 00:53:31.945: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0/usb1/1-6 (subsystem usb) 362s ** (umockdev-run:1857): DEBUG: 00:53:31.950: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.OA8K22/dev/bus/usb/001/006 362s ** (umockdev-run:1857): DEBUG: 00:53:31.950: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0/usb1 362s ** (umockdev-run:1857): DEBUG: 00:53:31.952: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0/usb1 (subsystem usb) 362s ** (umockdev-run:1857): DEBUG: 00:53:31.956: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.OA8K22/dev/bus/usb/001/001 362s ** (umockdev-run:1857): DEBUG: 00:53:31.956: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0 362s ** (umockdev-run:1857): DEBUG: 00:53:31.956: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0 (subsystem pci) 363s (process:1861): libfprint-context-DEBUG: 00:53:32.067: Initializing FpContext (libfprint version 1.94.8+tod1) 363s (process:1861): libfprint-tod-DEBUG: 00:53:32.067: Impossible to load the shared drivers dir Error opening directory “/usr/lib/arm-linux-gnueabihf/libfprint-2/tod-1”: No such file or directory 363s (process:1861): libfprint-context-DEBUG: 00:53:32.070: No driver found for USB device 1D6B:0002 363s (process:1861): libfprint-realtek-DEBUG: 00:53:32.071: 7399780132203: ../libfprint/drivers/realtek/realtek.c:1225 363s (process:1861): libfprint-realtek-DEBUG: 00:53:32.077: Device name: Realtek USB2.0 Finger Print Bridge 363s (process:1861): libfprint-device-DEBUG: 00:53:32.077: Device reported probe completion 363s (process:1861): libfprint-device-DEBUG: 00:53:32.077: Completing action FPI_DEVICE_ACTION_PROBE in idle! 363s (process:1861): libfprint-device-DEBUG: 00:53:32.077: Not updating temperature model, device can run continuously! 363s (process:1861): libfprint-realtek-DEBUG: 00:53:32.078: 7399780139897: ../libfprint/drivers/realtek/realtek.c:1270 363s (process:1861): libfprint-SSM-DEBUG: 00:53:32.080: [realtek] Init entering state 0 363s (process:1861): libfprint-SSM-DEBUG: 00:53:32.081: [realtek] Init entering state 1 363s (process:1861): libfprint-SSM-DEBUG: 00:53:32.081: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 363s (process:1861): libfprint-SSM-DEBUG: 00:53:32.082: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 363s (process:1861): libfprint-SSM-DEBUG: 00:53:32.082: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 363s (process:1861): libfprint-SSM-DEBUG: 00:53:32.082: [realtek] Init entering state 2 363s (process:1861): libfprint-SSM-DEBUG: 00:53:32.082: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 363s (process:1861): libfprint-SSM-DEBUG: 00:53:32.083: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 363s (process:1861): libfprint-SSM-DEBUG: 00:53:32.083: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 363s (process:1861): libfprint-SSM-DEBUG: 00:53:32.083: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 363s (process:1861): libfprint-SSM-DEBUG: 00:53:32.084: [realtek] Init completed successfully 363s (process:1861): libfprint-realtek-DEBUG: 00:53:32.084: Init complete! 363s (process:1861): libfprint-device-DEBUG: 00:53:32.084: Device reported open completion 363s (process:1861): libfprint-SSM-DEBUG: 00:53:32.084: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 363s (process:1861): libfprint-device-DEBUG: 00:53:32.084: Completing action FPI_DEVICE_ACTION_OPEN in idle! 363s (process:1861): libfprint-device-DEBUG: 00:53:32.084: Not updating temperature model, device can run continuously! 363s (process:1861): libfprint-realtek-DEBUG: 00:53:32.084: 7399780145402: ../libfprint/drivers/realtek/realtek.c:1333 363s (process:1861): libfprint-SSM-DEBUG: 00:53:32.084: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 363s (process:1861): libfprint-SSM-DEBUG: 00:53:32.085: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 363s (process:1861): libfprint-SSM-DEBUG: 00:53:32.085: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 363s (process:1861): libfprint-realtek-DEBUG: 00:53:32.085: Successfully cleared storage 363s (process:1861): libfprint-device-DEBUG: 00:53:32.085: Device reported deletion completion 363s (process:1861): libfprint-SSM-DEBUG: 00:53:32.085: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 363s (process:1861): libfprint-device-DEBUG: 00:53:32.085: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 363s (process:1861): libfprint-device-DEBUG: 00:53:32.085: Not updating temperature model, device can run continuously! 363s (process:1861): libfprint-device-DEBUG: 00:53:32.086: Not updating temperature model, device can run continuously! 363s (process:1861): libfprint-realtek-DEBUG: 00:53:32.086: 7399780147636: ../libfprint/drivers/realtek/realtek.c:1202 363s (process:1861): libfprint-SSM-DEBUG: 00:53:32.086: [realtek] Enroll entering state 0 363s (process:1861): libfprint-SSM-DEBUG: 00:53:32.086: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 363s (process:1861): libfprint-SSM-DEBUG: 00:53:32.087: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 363s (process:1861): libfprint-SSM-DEBUG: 00:53:32.087: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 363s (process:1861): libfprint-SSM-DEBUG: 00:53:32.088: [realtek] Enroll entering state 1 363s (process:1861): libfprint-SSM-DEBUG: 00:53:32.088: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 363s (process:1861): libfprint-SSM-DEBUG: 00:53:32.088: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 363s (process:1861): libfprint-SSM-DEBUG: 00:53:32.088: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 363s (process:1861): libfprint-SSM-DEBUG: 00:53:32.088: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 363s (process:1861): libfprint-SSM-DEBUG: 00:53:32.089: [realtek] Enroll entering state 2 363s (process:1861): libfprint-device-DEBUG: 00:53:32.089: Device reported finger status change: FP_FINGER_STATUS_NEEDED 363s (process:1861): libfprint-SSM-DEBUG: 00:53:32.089: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 363s (process:1861): libfprint-SSM-DEBUG: 00:53:32.089: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 363s (process:1861): libfprint-SSM-DEBUG: 00:53:32.089: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 363s (process:1861): libfprint-SSM-DEBUG: 00:53:32.089: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 363s (process:1861): libfprint-SSM-DEBUG: 00:53:32.090: [realtek] Enroll entering state 3 363s (process:1861): libfprint-SSM-DEBUG: 00:53:32.090: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 363s (process:1861): libfprint-SSM-DEBUG: 00:53:32.090: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 363s (process:1861): libfprint-SSM-DEBUG: 00:53:32.090: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 363s (process:1861): libfprint-SSM-DEBUG: 00:53:32.091: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 363s (process:1861): libfprint-device-DEBUG: 00:53:32.091: Device reported finger status change: FP_FINGER_STATUS_PRESENT 363s (process:1861): libfprint-SSM-DEBUG: 00:53:32.091: [realtek] Enroll entering state 4 363s (process:1861): libfprint-SSM-DEBUG: 00:53:32.091: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 363s (process:1861): libfprint-SSM-DEBUG: 00:53:32.091: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 363s (process:1861): libfprint-SSM-DEBUG: 00:53:32.092: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 363s (process:1861): libfprint-SSM-DEBUG: 00:53:32.092: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 363s (process:1861): libfprint-device-DEBUG: 00:53:32.093: Device reported finger status change: FP_FINGER_STATUS_NONE 363s (process:1861): libfprint-device-DEBUG: 00:53:32.093: Device reported enroll progress, reported 1 of 8 have been completed 363s (process:1861): libfprint-SSM-DEBUG: 00:53:32.093: [realtek] Enroll entering state 2 363s (process:1861): libfprint-device-DEBUG: 00:53:32.093: Device reported finger status change: FP_FINGER_STATUS_NEEDED 363s (process:1861): libfprint-SSM-DEBUG: 00:53:32.093: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 363s (process:1861): libfprint-SSM-DEBUG: 00:53:32.093: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 363s (process:1861): libfprint-SSM-DEBUG: 00:53:32.093: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 363s (process:1861): libfprint-SSM-DEBUG: 00:53:32.093: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 363s (process:1861): libfprint-SSM-DEBUG: 00:53:32.094: [realtek] Enroll entering state 3 363s (process:1861): libfprint-SSM-DEBUG: 00:53:32.094: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 363s (process:1861): libfprint-SSM-DEBUG: 00:53:32.094: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 363s (process:1861): libfprint-SSM-DEBUG: 00:53:32.094: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 363s (process:1861): libfprint-SSM-DEBUG: 00:53:32.095: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 363s (process:1861): libfprint-device-DEBUG: 00:53:32.095: Device reported finger status change: FP_FINGER_STATUS_PRESENT 363s (process:1861): libfprint-SSM-DEBUG: 00:53:32.095: [realtek] Enroll entering state 4 363s (process:1861): libfprint-SSM-DEBUG: 00:53:32.095: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 363s (process:1861): libfprint-SSM-DEBUG: 00:53:32.095: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 363s (process:1861): libfprint-SSM-DEBUG: 00:53:32.096: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 363s (process:1861): libfprint-SSM-DEBUG: 00:53:32.096: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 363s (process:1861): libfprint-device-DEBUG: 00:53:32.097: Device reported finger status change: FP_FINGER_STATUS_NONE 363s (process:1861): libfprint-device-DEBUG: 00:53:32.097: Device reported enroll progress, reported 2 of 8 have been completed 363s (process:1861): libfprint-SSM-DEBUG: 00:53:32.097: [realtek] Enroll entering state 2 363s (process:1861): libfprint-device-DEBUG: 00:53:32.097: Device reported finger status change: FP_FINGER_STATUS_NEEDED 363s (process:1861): libfprint-SSM-DEBUG: 00:53:32.097: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 363s (process:1861): libfprint-SSM-DEBUG: 00:53:32.097: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 363s (process:1861): libfprint-SSM-DEBUG: 00:53:32.097: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 363s (process:1861): libfprint-SSM-DEBUG: 00:53:32.097: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 363s (process:1861): libfprint-SSM-DEBUG: 00:53:32.098: [realtek] Enroll entering state 3 363s (process:1861): libfprint-SSM-DEBUG: 00:53:32.098: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 363s (process:1861): libfprint-SSM-DEBUG: 00:53:32.098: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 363s (process:1861): libfprint-SSM-DEBUG: 00:53:32.098: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 363s (process:1861): libfprint-SSM-DEBUG: 00:53:32.099: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 363s (process:1861): libfprint-device-DEBUG: 00:53:32.099: Device reported finger status change: FP_FINGER_STATUS_PRESENT 363s (process:1861): libfprint-SSM-DEBUG: 00:53:32.099: [realtek] Enroll entering state 4 363s (process:1861): libfprint-SSM-DEBUG: 00:53:32.099: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 363s (process:1861): libfprint-SSM-DEBUG: 00:53:32.099: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 363s (process:1861): libfprint-SSM-DEBUG: 00:53:32.100: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 363s (process:1861): libfprint-SSM-DEBUG: 00:53:32.100: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 363s (process:1861): libfprint-device-DEBUG: 00:53:32.101: Device reported finger status change: FP_FINGER_STATUS_NONE 363s (process:1861): libfprint-device-DEBUG: 00:53:32.101: Device reported enroll progress, reported 3 of 8 have been completed 363s (process:1861): libfprint-SSM-DEBUG: 00:53:32.101: [realtek] Enroll entering state 2 363s (process:1861): libfprint-device-DEBUG: 00:53:32.101: Device reported finger status change: FP_FINGER_STATUS_NEEDED 363s (process:1861): libfprint-SSM-DEBUG: 00:53:32.101: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 363s (process:1861): libfprint-SSM-DEBUG: 00:53:32.101: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 363s (process:1861): libfprint-SSM-DEBUG: 00:53:32.101: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 363s (process:1861): libfprint-SSM-DEBUG: 00:53:32.101: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 363s (process:1861): libfprint-SSM-DEBUG: 00:53:32.102: [realtek] Enroll entering state 3 363s (process:1861): libfprint-SSM-DEBUG: 00:53:32.102: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 363s (process:1861): libfprint-SSM-DEBUG: 00:53:32.102: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 363s (process:1861): libfprint-SSM-DEBUG: 00:53:32.102: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 363s (process:1861): libfprint-SSM-DEBUG: 00:53:32.103: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 363s (process:1861): libfprint-device-DEBUG: 00:53:32.104: Device reported finger status change: FP_FINGER_STATUS_PRESENT 363s (process:1861): libfprint-SSM-DEBUG: 00:53:32.104: [realtek] Enroll entering state 4 363s (process:1861): libfprint-SSM-DEBUG: 00:53:32.104: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 363s (process:1861): libfprint-SSM-DEBUG: 00:53:32.104: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 363s (process:1861): libfprint-SSM-DEBUG: 00:53:32.104: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 363s (process:1861): libfprint-SSM-DEBUG: 00:53:32.105: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 363s (process:1861): libfprint-device-DEBUG: 00:53:32.106: Device reported finger status change: FP_FINGER_STATUS_NONE 363s (process:1861): libfprint-device-DEBUG: 00:53:32.106: Device reported enroll progress, reported 4 of 8 have been completed 363s (process:1861): libfprint-SSM-DEBUG: 00:53:32.106: [realtek] Enroll entering state 2 363s (process:1861): libfprint-device-DEBUG: 00:53:32.106: Device reported finger status change: FP_FINGER_STATUS_NEEDED 363s (process:1861): libfprint-SSM-DEBUG: 00:53:32.106: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 363s (process:1861): libfprint-SSM-DEBUG: 00:53:32.106: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 363s (process:1861): libfprint-SSM-DEBUG: 00:53:32.107: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 363s (process:1861): libfprint-SSM-DEBUG: 00:53:32.107: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 363s (process:1861): libfprint-SSM-DEBUG: 00:53:32.108: [realtek] Enroll entering state 3 363s (process:1861): libfprint-SSM-DEBUG: 00:53:32.108: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 363s (process:1861): libfprint-SSM-DEBUG: 00:53:32.108: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 363s (process:1861): libfprint-SSM-DEBUG: 00:53:32.109: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 363s (process:1861): libfprint-SSM-DEBUG: 00:53:32.109: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 363s (process:1861): libfprint-device-DEBUG: 00:53:32.110: Device reported finger status change: FP_FINGER_STATUS_PRESENT 363s (process:1861): libfprint-SSM-DEBUG: 00:53:32.110: [realtek] Enroll entering state 4 363s (process:1861): libfprint-SSM-DEBUG: 00:53:32.110: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 363s (process:1861): libfprint-SSM-DEBUG: 00:53:32.110: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 363s (process:1861): libfprint-SSM-DEBUG: 00:53:32.111: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 363s (process:1861): libfprint-SSM-DEBUG: 00:53:32.111: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 363s (process:1861): libfprint-device-DEBUG: 00:53:32.112: Device reported finger status change: FP_FINGER_STATUS_NONE 363s (process:1861): libfprint-device-DEBUG: 00:53:32.112: Device reported enroll progress, reported 5 of 8 have been completed 363s (process:1861): libfprint-SSM-DEBUG: 00:53:32.112: [realtek] Enroll entering state 2 363s (process:1861): libfprint-device-DEBUG: 00:53:32.112: Device reported finger status change: FP_FINGER_STATUS_NEEDED 363s (process:1861): libfprint-SSM-DEBUG: 00:53:32.112: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 363s (process:1861): libfprint-SSM-DEBUG: 00:53:32.112: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 363s (process:1861): libfprint-SSM-DEBUG: 00:53:32.113: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 363s (process:1861): libfprint-SSM-DEBUG: 00:53:32.113: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 363s (process:1861): libfprint-SSM-DEBUG: 00:53:32.113: [realtek] Enroll entering state 3 363s (process:1861): libfprint-SSM-DEBUG: 00:53:32.113: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 363s (process:1861): libfprint-SSM-DEBUG: 00:53:32.113: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 363s (process:1861): libfprint-SSM-DEBUG: 00:53:32.114: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 363s (process:1861): libfprint-SSM-DEBUG: 00:53:32.114: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 363s (process:1861): libfprint-device-DEBUG: 00:53:32.115: Device reported finger status change: FP_FINGER_STATUS_PRESENT 363s (process:1861): libfprint-SSM-DEBUG: 00:53:32.115: [realtek] Enroll entering state 4 363s (process:1861): libfprint-SSM-DEBUG: 00:53:32.115: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 363s (process:1861): libfprint-SSM-DEBUG: 00:53:32.115: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 363s (process:1861): libfprint-SSM-DEBUG: 00:53:32.116: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 363s (process:1861): libfprint-SSM-DEBUG: 00:53:32.118: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 363s (process:1861): libfprint-device-DEBUG: 00:53:32.118: Device reported finger status change: FP_FINGER_STATUS_NONE 363s (process:1861): libfprint-device-DEBUG: 00:53:32.119: Device reported enroll progress, reported 6 of 8 have been completed 363s (process:1861): libfprint-SSM-DEBUG: 00:53:32.119: [realtek] Enroll entering state 2 363s (process:1861): libfprint-device-DEBUG: 00:53:32.119: Device reported finger status change: FP_FINGER_STATUS_NEEDED 363s (process:1861): libfprint-SSM-DEBUG: 00:53:32.119: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 363s (process:1861): libfprint-SSM-DEBUG: 00:53:32.119: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 363s (process:1861): libfprint-SSM-DEBUG: 00:53:32.119: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 363s (process:1861): libfprint-SSM-DEBUG: 00:53:32.119: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 363s (process:1861): libfprint-SSM-DEBUG: 00:53:32.120: [realtek] Enroll entering state 3 363s (process:1861): libfprint-SSM-DEBUG: 00:53:32.120: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 363s (process:1861): libfprint-SSM-DEBUG: 00:53:32.121: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 363s (process:1861): libfprint-SSM-DEBUG: 00:53:32.121: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 363s (process:1861): libfprint-SSM-DEBUG: 00:53:32.122: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 363s (process:1861): libfprint-device-DEBUG: 00:53:32.122: Device reported finger status change: FP_FINGER_STATUS_PRESENT 363s (process:1861): libfprint-SSM-DEBUG: 00:53:32.122: [realtek] Enroll entering state 4 363s (process:1861): libfprint-SSM-DEBUG: 00:53:32.122: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 363s (process:1861): libfprint-SSM-DEBUG: 00:53:32.123: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 363s (process:1861): libfprint-SSM-DEBUG: 00:53:32.123: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 363s (process:1861): libfprint-SSM-DEBUG: 00:53:32.123: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 363s (process:1861): libfprint-device-DEBUG: 00:53:32.124: Device reported finger status change: FP_FINGER_STATUS_NONE 363s (process:1861): libfprint-device-DEBUG: 00:53:32.124: Device reported enroll progress, reported 7 of 8 have been completed 363s (process:1861): libfprint-SSM-DEBUG: 00:53:32.124: [realtek] Enroll entering state 2 363s (process:1861): libfprint-device-DEBUG: 00:53:32.124: Device reported finger status change: FP_FINGER_STATUS_NEEDED 363s (process:1861): libfprint-SSM-DEBUG: 00:53:32.124: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 363s (process:1861): libfprint-SSM-DEBUG: 00:53:32.124: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 363s (process:1861): libfprint-SSM-DEBUG: 00:53:32.124: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 363s (process:1861): libfprint-SSM-DEBUG: 00:53:32.124: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 363s (process:1861): libfprint-SSM-DEBUG: 00:53:32.125: [realtek] Enroll entering state 3 363s (process:1861): libfprint-SSM-DEBUG: 00:53:32.125: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 363s (process:1861): libfprint-SSM-DEBUG: 00:53:32.125: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 363s (process:1861): libfprint-SSM-DEBUG: 00:53:32.125: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 363s (process:1861): libfprint-SSM-DEBUG: 00:53:32.126: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 363s (process:1861): libfprint-device-DEBUG: 00:53:32.126: Device reported finger status change: FP_FINGER_STATUS_PRESENT 363s (process:1861): libfprint-SSM-DEBUG: 00:53:32.126: [realtek] Enroll entering state 4 363s (process:1861): libfprint-SSM-DEBUG: 00:53:32.126: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 363s (process:1861): libfprint-SSM-DEBUG: 00:53:32.127: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 363s (process:1861): libfprint-SSM-DEBUG: 00:53:32.127: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 363s (process:1861): libfprint-SSM-DEBUG: 00:53:32.127: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 363s (process:1861): libfprint-device-DEBUG: 00:53:32.128: Device reported finger status change: FP_FINGER_STATUS_NONE 363s (process:1861): libfprint-device-DEBUG: 00:53:32.128: Device reported enroll progress, reported 8 of 8 have been completed 363s (process:1861): libfprint-SSM-DEBUG: 00:53:32.128: [realtek] Enroll entering state 2 363s (process:1861): libfprint-device-DEBUG: 00:53:32.128: Device reported finger status change: FP_FINGER_STATUS_NEEDED 363s (process:1861): libfprint-SSM-DEBUG: 00:53:32.128: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 363s (process:1861): libfprint-SSM-DEBUG: 00:53:32.128: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 363s (process:1861): libfprint-SSM-DEBUG: 00:53:32.128: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 363s (process:1861): libfprint-SSM-DEBUG: 00:53:32.128: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 363s (process:1861): libfprint-SSM-DEBUG: 00:53:32.129: [realtek] Enroll entering state 3 363s (process:1861): libfprint-SSM-DEBUG: 00:53:32.129: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 363s (process:1861): libfprint-SSM-DEBUG: 00:53:32.129: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 363s (process:1861): libfprint-SSM-DEBUG: 00:53:32.129: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 363s (process:1861): libfprint-SSM-DEBUG: 00:53:32.130: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 363s (process:1861): libfprint-device-DEBUG: 00:53:32.130: Device reported finger status change: FP_FINGER_STATUS_PRESENT 363s (process:1861): libfprint-SSM-DEBUG: 00:53:32.130: [realtek] Enroll entering state 4 363s (process:1861): libfprint-SSM-DEBUG: 00:53:32.130: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 363s (process:1861): libfprint-SSM-DEBUG: 00:53:32.130: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 363s (process:1861): libfprint-SSM-DEBUG: 00:53:32.131: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 363s (process:1861): libfprint-SSM-DEBUG: 00:53:32.132: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 363s (process:1861): libfprint-device-DEBUG: 00:53:32.133: Device reported finger status change: FP_FINGER_STATUS_NONE 363s (process:1861): libfprint-SSM-DEBUG: 00:53:32.133: [realtek] Enroll entering state 5 363s (process:1861): libfprint-SSM-DEBUG: 00:53:32.133: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 363s (process:1861): libfprint-SSM-DEBUG: 00:53:32.133: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 363s (process:1861): libfprint-SSM-DEBUG: 00:53:32.133: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 363s (process:1861): libfprint-SSM-DEBUG: 00:53:32.134: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 363s (process:1861): libfprint-SSM-DEBUG: 00:53:32.134: [realtek] Enroll entering state 6 363s (process:1861): libfprint-realtek-DEBUG: 00:53:32.134: user_id: FP1-00000000-0-00000000-nobody, finger: 0xff 363s (process:1861): libfprint-SSM-DEBUG: 00:53:32.134: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 363s (process:1861): libfprint-SSM-DEBUG: 00:53:32.135: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 363s (process:1861): libfprint-SSM-DEBUG: 00:53:32.135: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 363s (process:1861): libfprint-SSM-DEBUG: 00:53:32.135: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 363s (process:1861): libfprint-SSM-DEBUG: 00:53:32.136: [realtek] Enroll completed successfully 363s (process:1861): libfprint-realtek-DEBUG: 00:53:32.136: Enrollment complete! 363s (process:1861): libfprint-device-DEBUG: 00:53:32.136: Device reported enroll completion 363s (process:1861): libfprint-device-DEBUG: 00:53:32.136: Print for finger FP_FINGER_UNKNOWN enrolled 363s (process:1861): libfprint-SSM-DEBUG: 00:53:32.136: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 363s (process:1861): libfprint-device-DEBUG: 00:53:32.136: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 363s (process:1861): libfprint-device-DEBUG: 00:53:32.136: Not updating temperature model, device can run continuously! 363s (process:1861): libfprint-realtek-DEBUG: 00:53:32.136: 7399780197485: ../libfprint/drivers/realtek/realtek.c:1345 363s (process:1861): libfprint-SSM-DEBUG: 00:53:32.136: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 363s (process:1861): libfprint-SSM-DEBUG: 00:53:32.137: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 363s (process:1861): libfprint-SSM-DEBUG: 00:53:32.137: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 363s (process:1861): libfprint-realtek-DEBUG: 00:53:32.138: Query templates complete! 363s (process:1861): libfprint-device-DEBUG: 00:53:32.138: Device reported listing completion 363s (process:1861): libfprint-SSM-DEBUG: 00:53:32.138: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 363s (process:1861): libfprint-device-DEBUG: 00:53:32.138: Completing action FPI_DEVICE_ACTION_LIST in idle! 363s (process:1861): libfprint-device-DEBUG: 00:53:32.138: Not updating temperature model, device can run continuously! 363s (process:1861): libfprint-device-DEBUG: 00:53:32.138: Not updating temperature model, device can run continuously! 363s (process:1861): libfprint-realtek-DEBUG: 00:53:32.138: 7399780199413: ../libfprint/drivers/realtek/realtek.c:1178 363s (process:1861): libfprint-SSM-DEBUG: 00:53:32.138: [realtek] Verify & Identify entering state 0 363s (process:1861): libfprint-SSM-DEBUG: 00:53:32.138: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 363s (process:1861): libfprint-SSM-DEBUG: 00:53:32.138: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 363s (process:1861): libfprint-SSM-DEBUG: 00:53:32.139: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 363s (process:1861): libfprint-SSM-DEBUG: 00:53:32.139: [realtek] Verify & Identify entering state 1 363s (process:1861): libfprint-device-DEBUG: 00:53:32.139: Device reported finger status change: FP_FINGER_STATUS_NEEDED 363s (process:1861): libfprint-SSM-DEBUG: 00:53:32.139: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 363s (process:1861): libfprint-SSM-DEBUG: 00:53:32.140: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 363s (process:1861): libfprint-SSM-DEBUG: 00:53:32.140: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 363s (process:1861): libfprint-SSM-DEBUG: 00:53:32.140: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 363s (process:1861): libfprint-SSM-DEBUG: 00:53:32.140: [realtek] Verify & Identify entering state 2 363s (process:1861): libfprint-SSM-DEBUG: 00:53:32.140: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 363s (process:1861): libfprint-SSM-DEBUG: 00:53:32.141: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 363s (process:1861): libfprint-SSM-DEBUG: 00:53:32.141: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 363s (process:1861): libfprint-SSM-DEBUG: 00:53:32.141: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 363s (process:1861): libfprint-device-DEBUG: 00:53:32.142: Device reported finger status change: FP_FINGER_STATUS_PRESENT 363s (process:1861): libfprint-SSM-DEBUG: 00:53:32.142: [realtek] Verify & Identify entering state 3 363s (process:1861): libfprint-SSM-DEBUG: 00:53:32.142: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 363s (process:1861): libfprint-SSM-DEBUG: 00:53:32.142: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 363s (process:1861): libfprint-SSM-DEBUG: 00:53:32.142: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 363s (process:1861): libfprint-SSM-DEBUG: 00:53:32.143: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 363s (process:1861): libfprint-device-DEBUG: 00:53:32.143: Device reported finger status change: FP_FINGER_STATUS_NONE 363s (process:1861): libfprint-SSM-DEBUG: 00:53:32.143: [realtek] Verify & Identify entering state 4 363s (process:1861): libfprint-SSM-DEBUG: 00:53:32.143: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 363s (process:1861): libfprint-SSM-DEBUG: 00:53:32.144: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 363s (process:1861): libfprint-SSM-DEBUG: 00:53:32.144: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 363s (process:1861): libfprint-SSM-DEBUG: 00:53:32.144: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 363s (process:1861): libfprint-device-DEBUG: 00:53:32.145: Device reported verify result 363s (process:1861): libfprint-SSM-DEBUG: 00:53:32.145: [realtek] Verify & Identify entering state 5 363s (process:1861): libfprint-SSM-DEBUG: 00:53:32.145: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 363s (process:1861): libfprint-SSM-DEBUG: 00:53:32.145: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 363s (process:1861): libfprint-SSM-DEBUG: 00:53:32.145: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 363s (process:1861): libfprint-SSM-DEBUG: 00:53:32.145: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 363s (process:1861): libfprint-SSM-DEBUG: 00:53:32.146: [realtek] Verify & Identify completed successfully 363s (process:1861): libfprint-realtek-DEBUG: 00:53:32.146: Verify complete! 363s (process:1861): libfprint-device-DEBUG: 00:53:32.146: Device reported verify completion 363s (process:1861): libfprint-SSM-DEBUG: 00:53:32.146: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 363s (process:1861): libfprint-device-DEBUG: 00:53:32.146: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 363s (process:1861): libfprint-device-DEBUG: 00:53:32.146: Not updating temperature model, device can run continuously! 363s (process:1861): libfprint-device-DEBUG: 00:53:32.146: Not updating temperature model, device can run continuously! 363s (process:1861): libfprint-realtek-DEBUG: 00:53:32.146: 7399780207768: ../libfprint/drivers/realtek/realtek.c:1178 363s (process:1861): libfprint-SSM-DEBUG: 00:53:32.146: [realtek] Verify & Identify entering state 0 363s (process:1861): libfprint-SSM-DEBUG: 00:53:32.146: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 363s (process:1861): libfprint-SSM-DEBUG: 00:53:32.147: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 363s (process:1861): libfprint-SSM-DEBUG: 00:53:32.148: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 363s (process:1861): libfprint-SSM-DEBUG: 00:53:32.148: [realtek] Verify & Identify entering state 1 363s (process:1861): libfprint-device-DEBUG: 00:53:32.148: Device reported finger status change: FP_FINGER_STATUS_NEEDED 363s (process:1861): libfprint-SSM-DEBUG: 00:53:32.148: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 363s (process:1861): libfprint-SSM-DEBUG: 00:53:32.148: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 363s (process:1861): libfprint-SSM-DEBUG: 00:53:32.149: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 363s (process:1861): libfprint-SSM-DEBUG: 00:53:32.149: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 363s (process:1861): libfprint-SSM-DEBUG: 00:53:32.149: [realtek] Verify & Identify entering state 2 363s (process:1861): libfprint-SSM-DEBUG: 00:53:32.149: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 363s (process:1861): libfprint-SSM-DEBUG: 00:53:32.149: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 363s (process:1861): libfprint-SSM-DEBUG: 00:53:32.150: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 363s (process:1861): libfprint-SSM-DEBUG: 00:53:32.150: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 363s (process:1861): libfprint-device-DEBUG: 00:53:32.151: Device reported finger status change: FP_FINGER_STATUS_PRESENT 363s (process:1861): libfprint-SSM-DEBUG: 00:53:32.151: [realtek] Verify & Identify entering state 3 363s (process:1861): libfprint-SSM-DEBUG: 00:53:32.151: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 363s (process:1861): libfprint-SSM-DEBUG: 00:53:32.151: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 363s (process:1861): libfprint-SSM-DEBUG: 00:53:32.151: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 363s (process:1861): libfprint-SSM-DEBUG: 00:53:32.152: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 363s (process:1861): libfprint-device-DEBUG: 00:53:32.152: Device reported finger status change: FP_FINGER_STATUS_NONE 363s (process:1861): libfprint-SSM-DEBUG: 00:53:32.152: [realtek] Verify & Identify entering state 4 363s (process:1861): libfprint-SSM-DEBUG: 00:53:32.152: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 363s (process:1861): libfprint-SSM-DEBUG: 00:53:32.152: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 363s (process:1861): libfprint-SSM-DEBUG: 00:53:32.153: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 363s (process:1861): libfprint-SSM-DEBUG: 00:53:32.153: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 363s (process:1861): libfprint-device-DEBUG: 00:53:32.154: Device reported identify result 363s (process:1861): libfprint-SSM-DEBUG: 00:53:32.154: [realtek] Verify & Identify completed successfully 363s (process:1861): libfprint-realtek-DEBUG: 00:53:32.154: Verify complete! 363s (process:1861): libfprint-device-DEBUG: 00:53:32.154: Device reported identify completion 363s (process:1861): libfprint-SSM-DEBUG: 00:53:32.154: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 363s (process:1861): libfprint-device-DEBUG: 00:53:32.154: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 363s (process:1861): libfprint-device-DEBUG: 00:53:32.154: Not updating temperature model, device can run continuously! 363s (process:1861): libfprint-realtek-DEBUG: 00:53:32.154: 7399780215821: ../libfprint/drivers/realtek/realtek.c:1314 363s (process:1861): libfprint-SSM-DEBUG: 00:53:32.154: [realtek] Delete print entering state 0 363s (process:1861): libfprint-SSM-DEBUG: 00:53:32.154: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 363s (process:1861): libfprint-SSM-DEBUG: 00:53:32.155: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 363s (process:1861): libfprint-SSM-DEBUG: 00:53:32.156: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 363s (process:1861): libfprint-SSM-DEBUG: 00:53:32.156: [realtek] Delete print entering state 1 363s (process:1861): libfprint-SSM-DEBUG: 00:53:32.156: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 363s (process:1861): libfprint-SSM-DEBUG: 00:53:32.156: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 363s (process:1861): libfprint-SSM-DEBUG: 00:53:32.157: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 363s (process:1861): libfprint-SSM-DEBUG: 00:53:32.157: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 363s (process:1861): libfprint-SSM-DEBUG: 00:53:32.157: [realtek] Delete print completed successfully 363s (process:1861): libfprint-realtek-DEBUG: 00:53:32.157: Delete print complete! 363s (process:1861): libfprint-device-DEBUG: 00:53:32.157: Device reported deletion completion 363s (process:1861): libfprint-SSM-DEBUG: 00:53:32.157: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 363s (process:1861): libfprint-device-DEBUG: 00:53:32.157: Completing action FPI_DEVICE_ACTION_DELETE in idle! 363s (process:1861): libfprint-device-DEBUG: 00:53:32.157: Not updating temperature model, device can run continuously! 363s (process:1861): libfprint-realtek-DEBUG: 00:53:32.157: 7399780218704: ../libfprint/drivers/realtek/realtek.c:1302 363s (process:1861): libfprint-device-DEBUG: 00:53:32.158: Device reported close completion 363s (process:1861): libfprint-device-DEBUG: 00:53:32.158: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 363s (process:1861): libfprint-device-DEBUG: 00:53:32.158: Not updating temperature model, device can run continuously! 363s enrolling 363s enroll progress: (<__gi__.FpiDeviceRealtek object at 0xea817108 (FpiDeviceRealtek at 0xea3ed0)>, 1, None, None, None) 363s enroll progress: (<__gi__.FpiDeviceRealtek object at 0xea817108 (FpiDeviceRealtek at 0xea3ed0)>, 2, None, None, None) 363s enroll progress: (<__gi__.FpiDeviceRealtek object at 0xea817108 (FpiDeviceRealtek at 0xea3ed0)>, 3, None, None, None) 363s enroll progress: (<__gi__.FpiDeviceRealtek object at 0xea817108 (FpiDeviceRealtek at 0xea3ed0)>, 4, None, None, None) 363s enroll progress: (<__gi__.FpiDeviceRealtek object at 0xea817108 (FpiDeviceRealtek at 0xea3ed0)>, 5, None, None, None) 363s enroll progress: (<__gi__.FpiDeviceRealtek object at 0xea817108 (FpiDeviceRealtek at 0xea3ed0)>, 6, None, None, None) 363s enroll progress: (<__gi__.FpiDeviceRealtek object at 0xea817108 (FpiDeviceRealtek at 0xea3ed0)>, 7, None, None, None) 363s enroll progress: (<__gi__.FpiDeviceRealtek object at 0xea817108 (FpiDeviceRealtek at 0xea3ed0)>, 8, None, None, None) 363s enroll done 363s listing 363s listing done 363s verifying 363s verify done 363s async identifying 363s indentification_done: 363s deleting 363s delete done 363s ** (umockdev-run:1857): DEBUG: 00:53:32.186: umockdev.vala:154: Removing test bed /tmp/umockdev.OA8K22 363s (umockdev-run:1857): GLib-DEBUG: 00:53:32.197: unsetenv() is not thread-safe and should not be used after threads are created 363s PASS: libfprint-2/driver-realtek-5816.test 363s Running test: libfprint-2/driver-egis0570.test 363s ** (umockdev-run:1869): DEBUG: 00:53:32.257: umockdev.vala:127: Created udev test bed /tmp/umockdev.PEP312 363s ** (umockdev-run:1869): DEBUG: 00:53:32.257: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0/usb1/1-9 363s ** (umockdev-run:1869): DEBUG: 00:53:32.259: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0/usb1/1-9 (subsystem usb) 363s ** (umockdev-run:1869): DEBUG: 00:53:32.264: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.PEP312/dev/bus/usb/001/005 363s ** (umockdev-run:1869): DEBUG: 00:53:32.264: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0/usb1 363s ** (umockdev-run:1869): DEBUG: 00:53:32.265: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0/usb1 (subsystem usb) 363s ** (umockdev-run:1869): DEBUG: 00:53:32.269: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.PEP312/dev/bus/usb/001/001 363s ** (umockdev-run:1869): DEBUG: 00:53:32.269: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0 363s ** (umockdev-run:1869): DEBUG: 00:53:32.270: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0 (subsystem pci) 363s (process:1873): libfprint-context-DEBUG: 00:53:32.380: Initializing FpContext (libfprint version 1.94.8+tod1) 363s (process:1873): libfprint-tod-DEBUG: 00:53:32.381: Impossible to load the shared drivers dir Error opening directory “/usr/lib/arm-linux-gnueabihf/libfprint-2/tod-1”: No such file or directory 363s (process:1873): libfprint-context-DEBUG: 00:53:32.384: No driver found for USB device 1D6B:0002 363s (process:1873): libfprint-device-DEBUG: 00:53:32.384: Device reported probe completion 363s (process:1873): libfprint-device-DEBUG: 00:53:32.384: Completing action FPI_DEVICE_ACTION_PROBE in idle! 363s (process:1873): libfprint-device-DEBUG: 00:53:32.384: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 363s (process:1873): libfprint-image_device-DEBUG: 00:53:32.386: Image device open completed 363s (process:1873): libfprint-device-DEBUG: 00:53:32.386: Device reported open completion 363s (process:1873): libfprint-device-DEBUG: 00:53:32.386: Completing action FPI_DEVICE_ACTION_OPEN in idle! 363s (process:1873): libfprint-device-DEBUG: 00:53:32.386: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 363s (process:1873): libfprint-device-DEBUG: 00:53:32.387: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 363s (process:1873): libfprint-image_device-DEBUG: 00:53:32.387: Activating image device 363s (process:1873): libfprint-image_device-DEBUG: 00:53:32.387: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.387: [egis0570] SM_STATES_NUM entering state 0 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.387: [egis0570] SM_STATES_NUM entering state 1 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.387: [egis0570] SM_STATES_NUM entering state 2 363s (process:1873): libfprint-image_device-DEBUG: 00:53:32.387: Image device activation completed 363s (process:1873): libfprint-image_device-DEBUG: 00:53:32.387: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE 363s (process:1873): libfprint-image_device-DEBUG: 00:53:32.387: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 363s (process:1873): libfprint-device-DEBUG: 00:53:32.387: Device reported finger status change: FP_FINGER_STATUS_NEEDED 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.387: [egis0570] SM_STATES_NUM entering state 3 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.387: [egis0570] SM_STATES_NUM entering state 2 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.388: [egis0570] SM_STATES_NUM entering state 3 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.388: [egis0570] SM_STATES_NUM entering state 2 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.389: [egis0570] SM_STATES_NUM entering state 3 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.389: [egis0570] SM_STATES_NUM entering state 2 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.390: [egis0570] SM_STATES_NUM entering state 3 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.391: [egis0570] SM_STATES_NUM entering state 2 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.392: [egis0570] SM_STATES_NUM entering state 3 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.392: [egis0570] SM_STATES_NUM entering state 2 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.393: [egis0570] SM_STATES_NUM entering state 3 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.393: [egis0570] SM_STATES_NUM entering state 2 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.393: [egis0570] SM_STATES_NUM entering state 3 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.394: [egis0570] SM_STATES_NUM entering state 2 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.394: [egis0570] SM_STATES_NUM entering state 3 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.395: [egis0570] SM_STATES_NUM entering state 2 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.395: [egis0570] SM_STATES_NUM entering state 3 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.396: [egis0570] SM_STATES_NUM entering state 2 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.396: [egis0570] SM_STATES_NUM entering state 3 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.397: [egis0570] SM_STATES_NUM entering state 2 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.397: [egis0570] SM_STATES_NUM entering state 3 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.398: [egis0570] SM_STATES_NUM entering state 2 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.398: [egis0570] SM_STATES_NUM entering state 3 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.399: [egis0570] SM_STATES_NUM entering state 2 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.399: [egis0570] SM_STATES_NUM entering state 3 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.400: [egis0570] SM_STATES_NUM entering state 2 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.400: [egis0570] SM_STATES_NUM entering state 3 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.401: [egis0570] SM_STATES_NUM entering state 2 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.401: [egis0570] SM_STATES_NUM entering state 3 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.402: [egis0570] SM_STATES_NUM entering state 2 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.402: [egis0570] SM_STATES_NUM entering state 3 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.403: [egis0570] SM_STATES_NUM entering state 2 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.403: [egis0570] SM_STATES_NUM entering state 3 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.404: [egis0570] SM_STATES_NUM entering state 2 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.404: [egis0570] SM_STATES_NUM entering state 3 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.405: [egis0570] SM_STATES_NUM entering state 2 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.405: [egis0570] SM_STATES_NUM entering state 3 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.405: [egis0570] SM_STATES_NUM entering state 2 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.406: [egis0570] SM_STATES_NUM entering state 3 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.406: [egis0570] SM_STATES_NUM entering state 2 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.407: [egis0570] SM_STATES_NUM entering state 3 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.407: [egis0570] SM_STATES_NUM entering state 2 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.408: [egis0570] SM_STATES_NUM entering state 3 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.408: [egis0570] SM_STATES_NUM entering state 2 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.409: [egis0570] SM_STATES_NUM entering state 3 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.409: [egis0570] SM_STATES_NUM entering state 4 363s (process:1873): libfprint-image_device-DEBUG: 00:53:32.410: Image device reported finger status: off 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.410: [egis0570] SM_STATES_NUM entering state 5 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.410: [egis0570] SM_STATES_NUM entering state 1 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.410: [egis0570] SM_STATES_NUM entering state 2 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.410: [egis0570] SM_STATES_NUM entering state 3 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.410: [egis0570] SM_STATES_NUM entering state 2 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.411: [egis0570] SM_STATES_NUM entering state 3 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.411: [egis0570] SM_STATES_NUM entering state 2 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.412: [egis0570] SM_STATES_NUM entering state 3 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.412: [egis0570] SM_STATES_NUM entering state 2 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.413: [egis0570] SM_STATES_NUM entering state 3 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.413: [egis0570] SM_STATES_NUM entering state 4 363s (process:1873): libfprint-egis0570-DEBUG: 00:53:32.414: Finger status (picture number, mean) : 0 , 0 363s (process:1873): libfprint-egis0570-DEBUG: 00:53:32.414: Finger status (picture number, mean) : 1 , 0 363s (process:1873): libfprint-egis0570-DEBUG: 00:53:32.414: Finger status (picture number, mean) : 2 , 0 363s (process:1873): libfprint-egis0570-DEBUG: 00:53:32.414: Finger status (picture number, mean) : 3 , 0 363s (process:1873): libfprint-egis0570-DEBUG: 00:53:32.414: Finger status (picture number, mean) : 4 , 0 363s (process:1873): libfprint-image_device-DEBUG: 00:53:32.414: Image device reported finger status: off 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.414: [egis0570] SM_STATES_NUM entering state 5 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.414: [egis0570] SM_STATES_NUM entering state 1 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.414: [egis0570] SM_STATES_NUM entering state 2 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.414: [egis0570] SM_STATES_NUM entering state 3 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.414: [egis0570] SM_STATES_NUM entering state 2 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.415: [egis0570] SM_STATES_NUM entering state 3 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.415: [egis0570] SM_STATES_NUM entering state 2 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.416: [egis0570] SM_STATES_NUM entering state 3 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.416: [egis0570] SM_STATES_NUM entering state 2 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.417: [egis0570] SM_STATES_NUM entering state 3 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.417: [egis0570] SM_STATES_NUM entering state 4 363s (process:1873): libfprint-egis0570-DEBUG: 00:53:32.418: Finger status (picture number, mean) : 0 , 0 363s (process:1873): libfprint-egis0570-DEBUG: 00:53:32.418: Finger status (picture number, mean) : 1 , 0 363s (process:1873): libfprint-egis0570-DEBUG: 00:53:32.418: Finger status (picture number, mean) : 2 , 0 363s (process:1873): libfprint-egis0570-DEBUG: 00:53:32.418: Finger status (picture number, mean) : 3 , 0 363s (process:1873): libfprint-egis0570-DEBUG: 00:53:32.418: Finger status (picture number, mean) : 4 , 0 363s (process:1873): libfprint-image_device-DEBUG: 00:53:32.418: Image device reported finger status: off 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.418: [egis0570] SM_STATES_NUM entering state 5 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.418: [egis0570] SM_STATES_NUM entering state 1 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.418: [egis0570] SM_STATES_NUM entering state 2 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.418: [egis0570] SM_STATES_NUM entering state 3 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.418: [egis0570] SM_STATES_NUM entering state 2 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.419: [egis0570] SM_STATES_NUM entering state 3 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.419: [egis0570] SM_STATES_NUM entering state 2 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.420: [egis0570] SM_STATES_NUM entering state 3 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.420: [egis0570] SM_STATES_NUM entering state 2 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.421: [egis0570] SM_STATES_NUM entering state 3 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.421: [egis0570] SM_STATES_NUM entering state 4 363s (process:1873): libfprint-egis0570-DEBUG: 00:53:32.422: Finger status (picture number, mean) : 0 , 0 363s (process:1873): libfprint-egis0570-DEBUG: 00:53:32.422: Finger status (picture number, mean) : 1 , 0 363s (process:1873): libfprint-egis0570-DEBUG: 00:53:32.422: Finger status (picture number, mean) : 2 , 0 363s (process:1873): libfprint-egis0570-DEBUG: 00:53:32.422: Finger status (picture number, mean) : 3 , 0 363s (process:1873): libfprint-egis0570-DEBUG: 00:53:32.422: Finger status (picture number, mean) : 4 , 0 363s (process:1873): libfprint-image_device-DEBUG: 00:53:32.422: Image device reported finger status: off 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.422: [egis0570] SM_STATES_NUM entering state 5 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.422: [egis0570] SM_STATES_NUM entering state 1 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.422: [egis0570] SM_STATES_NUM entering state 2 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.422: [egis0570] SM_STATES_NUM entering state 3 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.422: [egis0570] SM_STATES_NUM entering state 2 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.423: [egis0570] SM_STATES_NUM entering state 3 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.423: [egis0570] SM_STATES_NUM entering state 2 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.424: [egis0570] SM_STATES_NUM entering state 3 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.424: [egis0570] SM_STATES_NUM entering state 2 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.425: [egis0570] SM_STATES_NUM entering state 3 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.425: [egis0570] SM_STATES_NUM entering state 4 363s (process:1873): libfprint-egis0570-DEBUG: 00:53:32.426: Finger status (picture number, mean) : 0 , 0 363s (process:1873): libfprint-egis0570-DEBUG: 00:53:32.426: Finger status (picture number, mean) : 1 , 0 363s (process:1873): libfprint-egis0570-DEBUG: 00:53:32.426: Finger status (picture number, mean) : 2 , 0 363s (process:1873): libfprint-egis0570-DEBUG: 00:53:32.426: Finger status (picture number, mean) : 3 , 0 363s (process:1873): libfprint-egis0570-DEBUG: 00:53:32.426: Finger status (picture number, mean) : 4 , 0 363s (process:1873): libfprint-image_device-DEBUG: 00:53:32.426: Image device reported finger status: off 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.426: [egis0570] SM_STATES_NUM entering state 5 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.426: [egis0570] SM_STATES_NUM entering state 1 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.426: [egis0570] SM_STATES_NUM entering state 2 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.426: [egis0570] SM_STATES_NUM entering state 3 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.426: [egis0570] SM_STATES_NUM entering state 2 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.427: [egis0570] SM_STATES_NUM entering state 3 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.427: [egis0570] SM_STATES_NUM entering state 2 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.428: [egis0570] SM_STATES_NUM entering state 3 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.428: [egis0570] SM_STATES_NUM entering state 2 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.429: [egis0570] SM_STATES_NUM entering state 3 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.429: [egis0570] SM_STATES_NUM entering state 4 363s (process:1873): libfprint-egis0570-DEBUG: 00:53:32.429: Finger status (picture number, mean) : 0 , 0 363s (process:1873): libfprint-egis0570-DEBUG: 00:53:32.429: Finger status (picture number, mean) : 1 , 0 363s (process:1873): libfprint-egis0570-DEBUG: 00:53:32.429: Finger status (picture number, mean) : 2 , 0 363s (process:1873): libfprint-egis0570-DEBUG: 00:53:32.429: Finger status (picture number, mean) : 3 , 0 363s (process:1873): libfprint-egis0570-DEBUG: 00:53:32.430: Finger status (picture number, mean) : 4 , 0 363s (process:1873): libfprint-image_device-DEBUG: 00:53:32.430: Image device reported finger status: off 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.430: [egis0570] SM_STATES_NUM entering state 5 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.430: [egis0570] SM_STATES_NUM entering state 1 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.430: [egis0570] SM_STATES_NUM entering state 2 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.430: [egis0570] SM_STATES_NUM entering state 3 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.430: [egis0570] SM_STATES_NUM entering state 2 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.431: [egis0570] SM_STATES_NUM entering state 3 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.431: [egis0570] SM_STATES_NUM entering state 2 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.432: [egis0570] SM_STATES_NUM entering state 3 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.432: [egis0570] SM_STATES_NUM entering state 2 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.433: [egis0570] SM_STATES_NUM entering state 3 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.433: [egis0570] SM_STATES_NUM entering state 4 363s (process:1873): libfprint-egis0570-DEBUG: 00:53:32.433: Finger status (picture number, mean) : 0 , 0 363s (process:1873): libfprint-egis0570-DEBUG: 00:53:32.433: Finger status (picture number, mean) : 1 , 0 363s (process:1873): libfprint-egis0570-DEBUG: 00:53:32.433: Finger status (picture number, mean) : 2 , 0 363s (process:1873): libfprint-egis0570-DEBUG: 00:53:32.433: Finger status (picture number, mean) : 3 , 0 363s (process:1873): libfprint-egis0570-DEBUG: 00:53:32.433: Finger status (picture number, mean) : 4 , 0 363s (process:1873): libfprint-image_device-DEBUG: 00:53:32.433: Image device reported finger status: off 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.433: [egis0570] SM_STATES_NUM entering state 5 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.433: [egis0570] SM_STATES_NUM entering state 1 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.433: [egis0570] SM_STATES_NUM entering state 2 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.434: [egis0570] SM_STATES_NUM entering state 3 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.434: [egis0570] SM_STATES_NUM entering state 2 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.435: [egis0570] SM_STATES_NUM entering state 3 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.435: [egis0570] SM_STATES_NUM entering state 2 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.436: [egis0570] SM_STATES_NUM entering state 3 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.436: [egis0570] SM_STATES_NUM entering state 2 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.437: [egis0570] SM_STATES_NUM entering state 3 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.437: [egis0570] SM_STATES_NUM entering state 4 363s (process:1873): libfprint-egis0570-DEBUG: 00:53:32.438: Finger status (picture number, mean) : 0 , 0 363s (process:1873): libfprint-egis0570-DEBUG: 00:53:32.438: Finger status (picture number, mean) : 1 , 0 363s (process:1873): libfprint-egis0570-DEBUG: 00:53:32.438: Finger status (picture number, mean) : 2 , 0 363s (process:1873): libfprint-egis0570-DEBUG: 00:53:32.438: Finger status (picture number, mean) : 3 , 0 363s (process:1873): libfprint-egis0570-DEBUG: 00:53:32.438: Finger status (picture number, mean) : 4 , 0 363s (process:1873): libfprint-image_device-DEBUG: 00:53:32.438: Image device reported finger status: off 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.438: [egis0570] SM_STATES_NUM entering state 5 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.438: [egis0570] SM_STATES_NUM entering state 1 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.438: [egis0570] SM_STATES_NUM entering state 2 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.438: [egis0570] SM_STATES_NUM entering state 3 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.438: [egis0570] SM_STATES_NUM entering state 2 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.439: [egis0570] SM_STATES_NUM entering state 3 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.439: [egis0570] SM_STATES_NUM entering state 2 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.440: [egis0570] SM_STATES_NUM entering state 3 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.440: [egis0570] SM_STATES_NUM entering state 2 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.441: [egis0570] SM_STATES_NUM entering state 3 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.441: [egis0570] SM_STATES_NUM entering state 4 363s (process:1873): libfprint-egis0570-DEBUG: 00:53:32.441: Finger status (picture number, mean) : 0 , 0 363s (process:1873): libfprint-egis0570-DEBUG: 00:53:32.441: Finger status (picture number, mean) : 1 , 0 363s (process:1873): libfprint-egis0570-DEBUG: 00:53:32.441: Finger status (picture number, mean) : 2 , 0 363s (process:1873): libfprint-egis0570-DEBUG: 00:53:32.441: Finger status (picture number, mean) : 3 , 0 363s (process:1873): libfprint-egis0570-DEBUG: 00:53:32.441: Finger status (picture number, mean) : 4 , 0 363s (process:1873): libfprint-image_device-DEBUG: 00:53:32.441: Image device reported finger status: off 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.441: [egis0570] SM_STATES_NUM entering state 5 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.441: [egis0570] SM_STATES_NUM entering state 1 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.441: [egis0570] SM_STATES_NUM entering state 2 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.442: [egis0570] SM_STATES_NUM entering state 3 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.442: [egis0570] SM_STATES_NUM entering state 2 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.443: [egis0570] SM_STATES_NUM entering state 3 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.443: [egis0570] SM_STATES_NUM entering state 2 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.444: [egis0570] SM_STATES_NUM entering state 3 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.444: [egis0570] SM_STATES_NUM entering state 2 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.445: [egis0570] SM_STATES_NUM entering state 3 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.445: [egis0570] SM_STATES_NUM entering state 4 363s (process:1873): libfprint-egis0570-DEBUG: 00:53:32.446: Finger status (picture number, mean) : 0 , 0 363s (process:1873): libfprint-egis0570-DEBUG: 00:53:32.446: Finger status (picture number, mean) : 1 , 0 363s (process:1873): libfprint-egis0570-DEBUG: 00:53:32.446: Finger status (picture number, mean) : 2 , 0 363s (process:1873): libfprint-egis0570-DEBUG: 00:53:32.446: Finger status (picture number, mean) : 3 , 0 363s (process:1873): libfprint-egis0570-DEBUG: 00:53:32.446: Finger status (picture number, mean) : 4 , 0 363s (process:1873): libfprint-image_device-DEBUG: 00:53:32.446: Image device reported finger status: off 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.446: [egis0570] SM_STATES_NUM entering state 5 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.446: [egis0570] SM_STATES_NUM entering state 1 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.446: [egis0570] SM_STATES_NUM entering state 2 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.446: [egis0570] SM_STATES_NUM entering state 3 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.446: [egis0570] SM_STATES_NUM entering state 2 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.447: [egis0570] SM_STATES_NUM entering state 3 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.447: [egis0570] SM_STATES_NUM entering state 2 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.448: [egis0570] SM_STATES_NUM entering state 3 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.448: [egis0570] SM_STATES_NUM entering state 2 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.449: [egis0570] SM_STATES_NUM entering state 3 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.449: [egis0570] SM_STATES_NUM entering state 4 363s (process:1873): libfprint-egis0570-DEBUG: 00:53:32.450: Finger status (picture number, mean) : 0 , 0 363s (process:1873): libfprint-egis0570-DEBUG: 00:53:32.450: Finger status (picture number, mean) : 1 , 0 363s (process:1873): libfprint-egis0570-DEBUG: 00:53:32.450: Finger status (picture number, mean) : 2 , 0 363s (process:1873): libfprint-egis0570-DEBUG: 00:53:32.450: Finger status (picture number, mean) : 3 , 0 363s (process:1873): libfprint-egis0570-DEBUG: 00:53:32.450: Finger status (picture number, mean) : 4 , 0 363s (process:1873): libfprint-image_device-DEBUG: 00:53:32.450: Image device reported finger status: off 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.450: [egis0570] SM_STATES_NUM entering state 5 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.450: [egis0570] SM_STATES_NUM entering state 1 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.450: [egis0570] SM_STATES_NUM entering state 2 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.450: [egis0570] SM_STATES_NUM entering state 3 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.450: [egis0570] SM_STATES_NUM entering state 2 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.451: [egis0570] SM_STATES_NUM entering state 3 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.451: [egis0570] SM_STATES_NUM entering state 2 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.452: [egis0570] SM_STATES_NUM entering state 3 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.452: [egis0570] SM_STATES_NUM entering state 2 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.453: [egis0570] SM_STATES_NUM entering state 3 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.453: [egis0570] SM_STATES_NUM entering state 4 363s (process:1873): libfprint-egis0570-DEBUG: 00:53:32.454: Finger status (picture number, mean) : 0 , 0 363s (process:1873): libfprint-egis0570-DEBUG: 00:53:32.454: Finger status (picture number, mean) : 1 , 0 363s (process:1873): libfprint-egis0570-DEBUG: 00:53:32.454: Finger status (picture number, mean) : 2 , 0 363s (process:1873): libfprint-egis0570-DEBUG: 00:53:32.454: Finger status (picture number, mean) : 3 , 0 363s (process:1873): libfprint-egis0570-DEBUG: 00:53:32.454: Finger status (picture number, mean) : 4 , 0 363s (process:1873): libfprint-image_device-DEBUG: 00:53:32.454: Image device reported finger status: off 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.454: [egis0570] SM_STATES_NUM entering state 5 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.454: [egis0570] SM_STATES_NUM entering state 1 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.454: [egis0570] SM_STATES_NUM entering state 2 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.454: [egis0570] SM_STATES_NUM entering state 3 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.454: [egis0570] SM_STATES_NUM entering state 2 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.455: [egis0570] SM_STATES_NUM entering state 3 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.456: [egis0570] SM_STATES_NUM entering state 2 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.456: [egis0570] SM_STATES_NUM entering state 3 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.456: [egis0570] SM_STATES_NUM entering state 2 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.457: [egis0570] SM_STATES_NUM entering state 3 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.457: [egis0570] SM_STATES_NUM entering state 4 363s (process:1873): libfprint-egis0570-DEBUG: 00:53:32.458: Finger status (picture number, mean) : 0 , 0 363s (process:1873): libfprint-egis0570-DEBUG: 00:53:32.458: Finger status (picture number, mean) : 1 , 0 363s (process:1873): libfprint-egis0570-DEBUG: 00:53:32.458: Finger status (picture number, mean) : 2 , 0 363s (process:1873): libfprint-egis0570-DEBUG: 00:53:32.458: Finger status (picture number, mean) : 3 , 0 363s (process:1873): libfprint-egis0570-DEBUG: 00:53:32.458: Finger status (picture number, mean) : 4 , 0 363s (process:1873): libfprint-image_device-DEBUG: 00:53:32.458: Image device reported finger status: off 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.458: [egis0570] SM_STATES_NUM entering state 5 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.458: [egis0570] SM_STATES_NUM entering state 1 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.458: [egis0570] SM_STATES_NUM entering state 2 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.458: [egis0570] SM_STATES_NUM entering state 3 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.458: [egis0570] SM_STATES_NUM entering state 2 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.459: [egis0570] SM_STATES_NUM entering state 3 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.459: [egis0570] SM_STATES_NUM entering state 2 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.460: [egis0570] SM_STATES_NUM entering state 3 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.460: [egis0570] SM_STATES_NUM entering state 2 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.461: [egis0570] SM_STATES_NUM entering state 3 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.461: [egis0570] SM_STATES_NUM entering state 4 363s (process:1873): libfprint-egis0570-DEBUG: 00:53:32.462: Finger status (picture number, mean) : 0 , 0 363s (process:1873): libfprint-egis0570-DEBUG: 00:53:32.462: Finger status (picture number, mean) : 1 , 0 363s (process:1873): libfprint-egis0570-DEBUG: 00:53:32.462: Finger status (picture number, mean) : 2 , 0 363s (process:1873): libfprint-egis0570-DEBUG: 00:53:32.462: Finger status (picture number, mean) : 3 , 0 363s (process:1873): libfprint-egis0570-DEBUG: 00:53:32.462: Finger status (picture number, mean) : 4 , 0 363s (process:1873): libfprint-image_device-DEBUG: 00:53:32.462: Image device reported finger status: off 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.462: [egis0570] SM_STATES_NUM entering state 5 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.462: [egis0570] SM_STATES_NUM entering state 1 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.462: [egis0570] SM_STATES_NUM entering state 2 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.462: [egis0570] SM_STATES_NUM entering state 3 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.462: [egis0570] SM_STATES_NUM entering state 2 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.463: [egis0570] SM_STATES_NUM entering state 3 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.463: [egis0570] SM_STATES_NUM entering state 2 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.464: [egis0570] SM_STATES_NUM entering state 3 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.465: [egis0570] SM_STATES_NUM entering state 2 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.465: [egis0570] SM_STATES_NUM entering state 3 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.465: [egis0570] SM_STATES_NUM entering state 4 363s (process:1873): libfprint-egis0570-DEBUG: 00:53:32.466: Finger status (picture number, mean) : 0 , 0 363s (process:1873): libfprint-egis0570-DEBUG: 00:53:32.466: Finger status (picture number, mean) : 1 , 0 363s (process:1873): libfprint-egis0570-DEBUG: 00:53:32.466: Finger status (picture number, mean) : 2 , 0 363s (process:1873): libfprint-egis0570-DEBUG: 00:53:32.466: Finger status (picture number, mean) : 3 , 0 363s (process:1873): libfprint-egis0570-DEBUG: 00:53:32.466: Finger status (picture number, mean) : 4 , 0 363s (process:1873): libfprint-image_device-DEBUG: 00:53:32.466: Image device reported finger status: off 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.466: [egis0570] SM_STATES_NUM entering state 5 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.466: [egis0570] SM_STATES_NUM entering state 1 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.466: [egis0570] SM_STATES_NUM entering state 2 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.467: [egis0570] SM_STATES_NUM entering state 3 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.467: [egis0570] SM_STATES_NUM entering state 2 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.468: [egis0570] SM_STATES_NUM entering state 3 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.468: [egis0570] SM_STATES_NUM entering state 2 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.468: [egis0570] SM_STATES_NUM entering state 3 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.469: [egis0570] SM_STATES_NUM entering state 2 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.469: [egis0570] SM_STATES_NUM entering state 3 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.469: [egis0570] SM_STATES_NUM entering state 4 363s (process:1873): libfprint-egis0570-DEBUG: 00:53:32.470: Finger status (picture number, mean) : 0 , 0 363s (process:1873): libfprint-egis0570-DEBUG: 00:53:32.470: Finger status (picture number, mean) : 1 , 0 363s (process:1873): libfprint-egis0570-DEBUG: 00:53:32.470: Finger status (picture number, mean) : 2 , 0 363s (process:1873): libfprint-egis0570-DEBUG: 00:53:32.470: Finger status (picture number, mean) : 3 , 0 363s (process:1873): libfprint-egis0570-DEBUG: 00:53:32.470: Finger status (picture number, mean) : 4 , 0 363s (process:1873): libfprint-image_device-DEBUG: 00:53:32.470: Image device reported finger status: off 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.470: [egis0570] SM_STATES_NUM entering state 5 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.470: [egis0570] SM_STATES_NUM entering state 1 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.470: [egis0570] SM_STATES_NUM entering state 2 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.471: [egis0570] SM_STATES_NUM entering state 3 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.471: [egis0570] SM_STATES_NUM entering state 2 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.471: [egis0570] SM_STATES_NUM entering state 3 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.472: [egis0570] SM_STATES_NUM entering state 2 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.473: [egis0570] SM_STATES_NUM entering state 3 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.473: [egis0570] SM_STATES_NUM entering state 2 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.473: [egis0570] SM_STATES_NUM entering state 3 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.473: [egis0570] SM_STATES_NUM entering state 4 363s (process:1873): libfprint-egis0570-DEBUG: 00:53:32.474: Finger status (picture number, mean) : 0 , 0 363s (process:1873): libfprint-egis0570-DEBUG: 00:53:32.474: Finger status (picture number, mean) : 1 , 0 363s (process:1873): libfprint-egis0570-DEBUG: 00:53:32.474: Finger status (picture number, mean) : 2 , 0 363s (process:1873): libfprint-egis0570-DEBUG: 00:53:32.474: Finger status (picture number, mean) : 3 , 0 363s (process:1873): libfprint-egis0570-DEBUG: 00:53:32.474: Finger status (picture number, mean) : 4 , 0 363s (process:1873): libfprint-image_device-DEBUG: 00:53:32.474: Image device reported finger status: off 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.474: [egis0570] SM_STATES_NUM entering state 5 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.474: [egis0570] SM_STATES_NUM entering state 1 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.474: [egis0570] SM_STATES_NUM entering state 2 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.475: [egis0570] SM_STATES_NUM entering state 3 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.475: [egis0570] SM_STATES_NUM entering state 2 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.476: [egis0570] SM_STATES_NUM entering state 3 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.476: [egis0570] SM_STATES_NUM entering state 2 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.477: [egis0570] SM_STATES_NUM entering state 3 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.477: [egis0570] SM_STATES_NUM entering state 2 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.478: [egis0570] SM_STATES_NUM entering state 3 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.478: [egis0570] SM_STATES_NUM entering state 4 363s (process:1873): libfprint-egis0570-DEBUG: 00:53:32.478: Finger status (picture number, mean) : 0 , 0 363s (process:1873): libfprint-egis0570-DEBUG: 00:53:32.478: Finger status (picture number, mean) : 1 , 0 363s (process:1873): libfprint-egis0570-DEBUG: 00:53:32.478: Finger status (picture number, mean) : 2 , 0 363s (process:1873): libfprint-egis0570-DEBUG: 00:53:32.478: Finger status (picture number, mean) : 3 , 0 363s (process:1873): libfprint-egis0570-DEBUG: 00:53:32.478: Finger status (picture number, mean) : 4 , 0 363s (process:1873): libfprint-image_device-DEBUG: 00:53:32.478: Image device reported finger status: off 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.478: [egis0570] SM_STATES_NUM entering state 5 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.478: [egis0570] SM_STATES_NUM entering state 1 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.478: [egis0570] SM_STATES_NUM entering state 2 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.479: [egis0570] SM_STATES_NUM entering state 3 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.479: [egis0570] SM_STATES_NUM entering state 2 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.480: [egis0570] SM_STATES_NUM entering state 3 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.480: [egis0570] SM_STATES_NUM entering state 2 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.481: [egis0570] SM_STATES_NUM entering state 3 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.481: [egis0570] SM_STATES_NUM entering state 2 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.482: [egis0570] SM_STATES_NUM entering state 3 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.482: [egis0570] SM_STATES_NUM entering state 4 363s (process:1873): libfprint-egis0570-DEBUG: 00:53:32.482: Finger status (picture number, mean) : 0 , 0 363s (process:1873): libfprint-egis0570-DEBUG: 00:53:32.482: Finger status (picture number, mean) : 1 , 0 363s (process:1873): libfprint-egis0570-DEBUG: 00:53:32.482: Finger status (picture number, mean) : 2 , 0 363s (process:1873): libfprint-egis0570-DEBUG: 00:53:32.482: Finger status (picture number, mean) : 3 , 0 363s (process:1873): libfprint-egis0570-DEBUG: 00:53:32.482: Finger status (picture number, mean) : 4 , 0 363s (process:1873): libfprint-image_device-DEBUG: 00:53:32.482: Image device reported finger status: off 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.482: [egis0570] SM_STATES_NUM entering state 5 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.482: [egis0570] SM_STATES_NUM entering state 1 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.482: [egis0570] SM_STATES_NUM entering state 2 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.483: [egis0570] SM_STATES_NUM entering state 3 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.483: [egis0570] SM_STATES_NUM entering state 2 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.484: [egis0570] SM_STATES_NUM entering state 3 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.484: [egis0570] SM_STATES_NUM entering state 2 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.485: [egis0570] SM_STATES_NUM entering state 3 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.485: [egis0570] SM_STATES_NUM entering state 2 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.486: [egis0570] SM_STATES_NUM entering state 3 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.486: [egis0570] SM_STATES_NUM entering state 4 363s (process:1873): libfprint-egis0570-DEBUG: 00:53:32.486: Finger status (picture number, mean) : 0 , 0 363s (process:1873): libfprint-egis0570-DEBUG: 00:53:32.486: Finger status (picture number, mean) : 1 , 0 363s (process:1873): libfprint-egis0570-DEBUG: 00:53:32.486: Finger status (picture number, mean) : 2 , 0 363s (process:1873): libfprint-egis0570-DEBUG: 00:53:32.486: Finger status (picture number, mean) : 3 , 0 363s (process:1873): libfprint-egis0570-DEBUG: 00:53:32.486: Finger status (picture number, mean) : 4 , 0 363s (process:1873): libfprint-image_device-DEBUG: 00:53:32.486: Image device reported finger status: off 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.486: [egis0570] SM_STATES_NUM entering state 5 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.486: [egis0570] SM_STATES_NUM entering state 1 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.486: [egis0570] SM_STATES_NUM entering state 2 363s (process:1873): libfprint-device-DEBUG: 00:53:32.487: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.487: [egis0570] SM_STATES_NUM entering state 3 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.487: [egis0570] SM_STATES_NUM entering state 2 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.488: [egis0570] SM_STATES_NUM entering state 3 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.488: [egis0570] SM_STATES_NUM entering state 2 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.489: [egis0570] SM_STATES_NUM entering state 3 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.489: [egis0570] SM_STATES_NUM entering state 2 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.490: [egis0570] SM_STATES_NUM entering state 3 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.490: [egis0570] SM_STATES_NUM entering state 4 363s (process:1873): libfprint-egis0570-DEBUG: 00:53:32.491: Finger status (picture number, mean) : 0 , 0 363s (process:1873): libfprint-egis0570-DEBUG: 00:53:32.491: Finger status (picture number, mean) : 1 , 0 363s (process:1873): libfprint-egis0570-DEBUG: 00:53:32.491: Finger status (picture number, mean) : 2 , 0 363s (process:1873): libfprint-egis0570-DEBUG: 00:53:32.491: Finger status (picture number, mean) : 3 , 0 363s (process:1873): libfprint-egis0570-DEBUG: 00:53:32.491: Finger status (picture number, mean) : 4 , 0 363s (process:1873): libfprint-image_device-DEBUG: 00:53:32.491: Image device reported finger status: off 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.491: [egis0570] SM_STATES_NUM entering state 5 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.491: [egis0570] SM_STATES_NUM entering state 1 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.491: [egis0570] SM_STATES_NUM entering state 2 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.491: [egis0570] SM_STATES_NUM entering state 3 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.491: [egis0570] SM_STATES_NUM entering state 2 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.492: [egis0570] SM_STATES_NUM entering state 3 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.492: [egis0570] SM_STATES_NUM entering state 2 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.493: [egis0570] SM_STATES_NUM entering state 3 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.493: [egis0570] SM_STATES_NUM entering state 2 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.494: [egis0570] SM_STATES_NUM entering state 3 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.494: [egis0570] SM_STATES_NUM entering state 4 363s (process:1873): libfprint-egis0570-DEBUG: 00:53:32.495: Finger status (picture number, mean) : 0 , 0 363s (process:1873): libfprint-egis0570-DEBUG: 00:53:32.495: Finger status (picture number, mean) : 1 , 0 363s (process:1873): libfprint-egis0570-DEBUG: 00:53:32.495: Finger status (picture number, mean) : 2 , 0 363s (process:1873): libfprint-egis0570-DEBUG: 00:53:32.495: Finger status (picture number, mean) : 3 , 0 363s (process:1873): libfprint-egis0570-DEBUG: 00:53:32.495: Finger status (picture number, mean) : 4 , 0 363s (process:1873): libfprint-image_device-DEBUG: 00:53:32.495: Image device reported finger status: off 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.495: [egis0570] SM_STATES_NUM entering state 5 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.495: [egis0570] SM_STATES_NUM entering state 1 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.495: [egis0570] SM_STATES_NUM entering state 2 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.495: [egis0570] SM_STATES_NUM entering state 3 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.496: [egis0570] SM_STATES_NUM entering state 2 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.496: [egis0570] SM_STATES_NUM entering state 3 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.496: [egis0570] SM_STATES_NUM entering state 2 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.497: [egis0570] SM_STATES_NUM entering state 3 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.498: [egis0570] SM_STATES_NUM entering state 2 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.498: [egis0570] SM_STATES_NUM entering state 3 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.498: [egis0570] SM_STATES_NUM entering state 4 363s (process:1873): libfprint-egis0570-DEBUG: 00:53:32.499: Finger status (picture number, mean) : 0 , 0 363s (process:1873): libfprint-egis0570-DEBUG: 00:53:32.499: Finger status (picture number, mean) : 1 , 0 363s (process:1873): libfprint-egis0570-DEBUG: 00:53:32.499: Finger status (picture number, mean) : 2 , 0 363s (process:1873): libfprint-egis0570-DEBUG: 00:53:32.499: Finger status (picture number, mean) : 3 , 0 363s (process:1873): libfprint-egis0570-DEBUG: 00:53:32.499: Finger status (picture number, mean) : 4 , 0 363s (process:1873): libfprint-image_device-DEBUG: 00:53:32.499: Image device reported finger status: off 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.499: [egis0570] SM_STATES_NUM entering state 5 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.499: [egis0570] SM_STATES_NUM entering state 1 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.499: [egis0570] SM_STATES_NUM entering state 2 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.499: [egis0570] SM_STATES_NUM entering state 3 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.500: [egis0570] SM_STATES_NUM entering state 2 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.500: [egis0570] SM_STATES_NUM entering state 3 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.500: [egis0570] SM_STATES_NUM entering state 2 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.501: [egis0570] SM_STATES_NUM entering state 3 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.501: [egis0570] SM_STATES_NUM entering state 2 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.502: [egis0570] SM_STATES_NUM entering state 3 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.502: [egis0570] SM_STATES_NUM entering state 4 363s (process:1873): libfprint-egis0570-DEBUG: 00:53:32.503: Finger status (picture number, mean) : 0 , 0 363s (process:1873): libfprint-egis0570-DEBUG: 00:53:32.503: Finger status (picture number, mean) : 1 , 0 363s (process:1873): libfprint-egis0570-DEBUG: 00:53:32.503: Finger status (picture number, mean) : 2 , 0 363s (process:1873): libfprint-egis0570-DEBUG: 00:53:32.503: Finger status (picture number, mean) : 3 , 0 363s (process:1873): libfprint-egis0570-DEBUG: 00:53:32.503: Finger status (picture number, mean) : 4 , 0 363s (process:1873): libfprint-image_device-DEBUG: 00:53:32.503: Image device reported finger status: off 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.503: [egis0570] SM_STATES_NUM entering state 5 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.503: [egis0570] SM_STATES_NUM entering state 1 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.503: [egis0570] SM_STATES_NUM entering state 2 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.503: [egis0570] SM_STATES_NUM entering state 3 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.504: [egis0570] SM_STATES_NUM entering state 2 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.505: [egis0570] SM_STATES_NUM entering state 3 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.506: [egis0570] SM_STATES_NUM entering state 2 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.507: [egis0570] SM_STATES_NUM entering state 3 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.507: [egis0570] SM_STATES_NUM entering state 2 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.508: [egis0570] SM_STATES_NUM entering state 3 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.508: [egis0570] SM_STATES_NUM entering state 4 363s (process:1873): libfprint-egis0570-DEBUG: 00:53:32.509: Finger status (picture number, mean) : 0 , 0 363s (process:1873): libfprint-egis0570-DEBUG: 00:53:32.509: Finger status (picture number, mean) : 1 , 0 363s (process:1873): libfprint-egis0570-DEBUG: 00:53:32.509: Finger status (picture number, mean) : 2 , 0 363s (process:1873): libfprint-egis0570-DEBUG: 00:53:32.509: Finger status (picture number, mean) : 3 , 0 363s (process:1873): libfprint-egis0570-DEBUG: 00:53:32.509: Finger status (picture number, mean) : 4 , 0 363s (process:1873): libfprint-image_device-DEBUG: 00:53:32.509: Image device reported finger status: off 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.509: [egis0570] SM_STATES_NUM entering state 5 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.509: [egis0570] SM_STATES_NUM entering state 1 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.509: [egis0570] SM_STATES_NUM entering state 2 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.509: [egis0570] SM_STATES_NUM entering state 3 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.509: [egis0570] SM_STATES_NUM entering state 2 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.510: [egis0570] SM_STATES_NUM entering state 3 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.510: [egis0570] SM_STATES_NUM entering state 2 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.511: [egis0570] SM_STATES_NUM entering state 3 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.511: [egis0570] SM_STATES_NUM entering state 2 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.512: [egis0570] SM_STATES_NUM entering state 3 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.512: [egis0570] SM_STATES_NUM entering state 4 363s (process:1873): libfprint-egis0570-DEBUG: 00:53:32.513: Finger status (picture number, mean) : 0 , 0 363s (process:1873): libfprint-egis0570-DEBUG: 00:53:32.513: Finger status (picture number, mean) : 1 , 0 363s (process:1873): libfprint-egis0570-DEBUG: 00:53:32.513: Finger status (picture number, mean) : 2 , 0 363s (process:1873): libfprint-egis0570-DEBUG: 00:53:32.513: Finger status (picture number, mean) : 3 , 0 363s (process:1873): libfprint-egis0570-DEBUG: 00:53:32.513: Finger status (picture number, mean) : 4 , 0 363s (process:1873): libfprint-image_device-DEBUG: 00:53:32.513: Image device reported finger status: off 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.513: [egis0570] SM_STATES_NUM entering state 5 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.513: [egis0570] SM_STATES_NUM entering state 1 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.513: [egis0570] SM_STATES_NUM entering state 2 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.513: [egis0570] SM_STATES_NUM entering state 3 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.513: [egis0570] SM_STATES_NUM entering state 2 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.514: [egis0570] SM_STATES_NUM entering state 3 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.514: [egis0570] SM_STATES_NUM entering state 2 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.515: [egis0570] SM_STATES_NUM entering state 3 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.515: [egis0570] SM_STATES_NUM entering state 2 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.516: [egis0570] SM_STATES_NUM entering state 3 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.516: [egis0570] SM_STATES_NUM entering state 4 363s (process:1873): libfprint-egis0570-DEBUG: 00:53:32.517: Finger status (picture number, mean) : 0 , 0 363s (process:1873): libfprint-egis0570-DEBUG: 00:53:32.517: Finger status (picture number, mean) : 1 , 0 363s (process:1873): libfprint-egis0570-DEBUG: 00:53:32.517: Finger status (picture number, mean) : 2 , 0 363s (process:1873): libfprint-egis0570-DEBUG: 00:53:32.517: Finger status (picture number, mean) : 3 , 0 363s (process:1873): libfprint-egis0570-DEBUG: 00:53:32.517: Finger status (picture number, mean) : 4 , 0 363s (process:1873): libfprint-image_device-DEBUG: 00:53:32.517: Image device reported finger status: off 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.517: [egis0570] SM_STATES_NUM entering state 5 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.517: [egis0570] SM_STATES_NUM entering state 1 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.517: [egis0570] SM_STATES_NUM entering state 2 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.517: [egis0570] SM_STATES_NUM entering state 3 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.517: [egis0570] SM_STATES_NUM entering state 2 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.518: [egis0570] SM_STATES_NUM entering state 3 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.518: [egis0570] SM_STATES_NUM entering state 2 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.519: [egis0570] SM_STATES_NUM entering state 3 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.519: [egis0570] SM_STATES_NUM entering state 2 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.520: [egis0570] SM_STATES_NUM entering state 3 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.520: [egis0570] SM_STATES_NUM entering state 4 363s (process:1873): libfprint-egis0570-DEBUG: 00:53:32.521: Finger status (picture number, mean) : 0 , 0 363s (process:1873): libfprint-egis0570-DEBUG: 00:53:32.521: Finger status (picture number, mean) : 1 , 0 363s (process:1873): libfprint-egis0570-DEBUG: 00:53:32.521: Finger status (picture number, mean) : 2 , 0 363s (process:1873): libfprint-egis0570-DEBUG: 00:53:32.521: Finger status (picture number, mean) : 3 , 0 363s (process:1873): libfprint-egis0570-DEBUG: 00:53:32.521: Finger status (picture number, mean) : 4 , 0 363s (process:1873): libfprint-image_device-DEBUG: 00:53:32.521: Image device reported finger status: off 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.521: [egis0570] SM_STATES_NUM entering state 5 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.521: [egis0570] SM_STATES_NUM entering state 1 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.521: [egis0570] SM_STATES_NUM entering state 2 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.521: [egis0570] SM_STATES_NUM entering state 3 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.522: [egis0570] SM_STATES_NUM entering state 2 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.522: [egis0570] SM_STATES_NUM entering state 3 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.523: [egis0570] SM_STATES_NUM entering state 2 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.523: [egis0570] SM_STATES_NUM entering state 3 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.524: [egis0570] SM_STATES_NUM entering state 2 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.524: [egis0570] SM_STATES_NUM entering state 3 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.524: [egis0570] SM_STATES_NUM entering state 4 363s (process:1873): libfprint-egis0570-DEBUG: 00:53:32.525: Finger status (picture number, mean) : 0 , 0 363s (process:1873): libfprint-egis0570-DEBUG: 00:53:32.525: Finger status (picture number, mean) : 1 , 0 363s (process:1873): libfprint-egis0570-DEBUG: 00:53:32.525: Finger status (picture number, mean) : 2 , 0 363s (process:1873): libfprint-egis0570-DEBUG: 00:53:32.525: Finger status (picture number, mean) : 3 , 0 363s (process:1873): libfprint-egis0570-DEBUG: 00:53:32.525: Finger status (picture number, mean) : 4 , 0 363s (process:1873): libfprint-image_device-DEBUG: 00:53:32.525: Image device reported finger status: off 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.525: [egis0570] SM_STATES_NUM entering state 5 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.525: [egis0570] SM_STATES_NUM entering state 1 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.525: [egis0570] SM_STATES_NUM entering state 2 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.525: [egis0570] SM_STATES_NUM entering state 3 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.526: [egis0570] SM_STATES_NUM entering state 2 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.526: [egis0570] SM_STATES_NUM entering state 3 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.527: [egis0570] SM_STATES_NUM entering state 2 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.527: [egis0570] SM_STATES_NUM entering state 3 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.528: [egis0570] SM_STATES_NUM entering state 2 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.528: [egis0570] SM_STATES_NUM entering state 3 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.528: [egis0570] SM_STATES_NUM entering state 4 363s (process:1873): libfprint-egis0570-DEBUG: 00:53:32.529: Finger status (picture number, mean) : 0 , 0 363s (process:1873): libfprint-egis0570-DEBUG: 00:53:32.529: Finger status (picture number, mean) : 1 , 0 363s (process:1873): libfprint-egis0570-DEBUG: 00:53:32.529: Finger status (picture number, mean) : 2 , 0 363s (process:1873): libfprint-egis0570-DEBUG: 00:53:32.529: Finger status (picture number, mean) : 3 , 0 363s (process:1873): libfprint-egis0570-DEBUG: 00:53:32.529: Finger status (picture number, mean) : 4 , 0 363s (process:1873): libfprint-image_device-DEBUG: 00:53:32.529: Image device reported finger status: off 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.529: [egis0570] SM_STATES_NUM entering state 5 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.529: [egis0570] SM_STATES_NUM entering state 1 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.529: [egis0570] SM_STATES_NUM entering state 2 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.529: [egis0570] SM_STATES_NUM entering state 3 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.530: [egis0570] SM_STATES_NUM entering state 2 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.530: [egis0570] SM_STATES_NUM entering state 3 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.531: [egis0570] SM_STATES_NUM entering state 2 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.531: [egis0570] SM_STATES_NUM entering state 3 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.532: [egis0570] SM_STATES_NUM entering state 2 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.532: [egis0570] SM_STATES_NUM entering state 3 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.532: [egis0570] SM_STATES_NUM entering state 4 363s (process:1873): libfprint-egis0570-DEBUG: 00:53:32.533: Finger status (picture number, mean) : 0 , 0 363s (process:1873): libfprint-egis0570-DEBUG: 00:53:32.533: Finger status (picture number, mean) : 1 , 0 363s (process:1873): libfprint-egis0570-DEBUG: 00:53:32.533: Finger status (picture number, mean) : 2 , 0 363s (process:1873): libfprint-egis0570-DEBUG: 00:53:32.533: Finger status (picture number, mean) : 3 , 0 363s (process:1873): libfprint-egis0570-DEBUG: 00:53:32.533: Finger status (picture number, mean) : 4 , 0 363s (process:1873): libfprint-image_device-DEBUG: 00:53:32.533: Image device reported finger status: off 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.533: [egis0570] SM_STATES_NUM entering state 5 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.533: [egis0570] SM_STATES_NUM entering state 1 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.533: [egis0570] SM_STATES_NUM entering state 2 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.533: [egis0570] SM_STATES_NUM entering state 3 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.534: [egis0570] SM_STATES_NUM entering state 2 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.534: [egis0570] SM_STATES_NUM entering state 3 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.534: [egis0570] SM_STATES_NUM entering state 2 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.535: [egis0570] SM_STATES_NUM entering state 3 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.535: [egis0570] SM_STATES_NUM entering state 2 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.536: [egis0570] SM_STATES_NUM entering state 3 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.536: [egis0570] SM_STATES_NUM entering state 4 363s (process:1873): libfprint-egis0570-DEBUG: 00:53:32.537: Finger status (picture number, mean) : 0 , 0 363s (process:1873): libfprint-egis0570-DEBUG: 00:53:32.537: Finger status (picture number, mean) : 1 , 0 363s (process:1873): libfprint-egis0570-DEBUG: 00:53:32.537: Finger status (picture number, mean) : 2 , 0 363s (process:1873): libfprint-egis0570-DEBUG: 00:53:32.537: Finger status (picture number, mean) : 3 , 0 363s (process:1873): libfprint-egis0570-DEBUG: 00:53:32.537: Finger status (picture number, mean) : 4 , 0 363s (process:1873): libfprint-image_device-DEBUG: 00:53:32.537: Image device reported finger status: off 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.537: [egis0570] SM_STATES_NUM entering state 5 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.537: [egis0570] SM_STATES_NUM entering state 1 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.537: [egis0570] SM_STATES_NUM entering state 2 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.537: [egis0570] SM_STATES_NUM entering state 3 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.537: [egis0570] SM_STATES_NUM entering state 2 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.538: [egis0570] SM_STATES_NUM entering state 3 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.538: [egis0570] SM_STATES_NUM entering state 2 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.539: [egis0570] SM_STATES_NUM entering state 3 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.539: [egis0570] SM_STATES_NUM entering state 2 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.540: [egis0570] SM_STATES_NUM entering state 3 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.540: [egis0570] SM_STATES_NUM entering state 4 363s (process:1873): libfprint-egis0570-DEBUG: 00:53:32.541: Finger status (picture number, mean) : 0 , 0 363s (process:1873): libfprint-egis0570-DEBUG: 00:53:32.541: Finger status (picture number, mean) : 1 , 0 363s (process:1873): libfprint-egis0570-DEBUG: 00:53:32.541: Finger status (picture number, mean) : 2 , 0 363s (process:1873): libfprint-egis0570-DEBUG: 00:53:32.541: Finger status (picture number, mean) : 3 , 0 363s (process:1873): libfprint-egis0570-DEBUG: 00:53:32.541: Finger status (picture number, mean) : 4 , 0 363s (process:1873): libfprint-image_device-DEBUG: 00:53:32.541: Image device reported finger status: off 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.541: [egis0570] SM_STATES_NUM entering state 5 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.541: [egis0570] SM_STATES_NUM entering state 1 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.541: [egis0570] SM_STATES_NUM entering state 2 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.541: [egis0570] SM_STATES_NUM entering state 3 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.541: [egis0570] SM_STATES_NUM entering state 2 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.542: [egis0570] SM_STATES_NUM entering state 3 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.542: [egis0570] SM_STATES_NUM entering state 2 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.543: [egis0570] SM_STATES_NUM entering state 3 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.543: [egis0570] SM_STATES_NUM entering state 2 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.544: [egis0570] SM_STATES_NUM entering state 3 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.544: [egis0570] SM_STATES_NUM entering state 4 363s (process:1873): libfprint-egis0570-DEBUG: 00:53:32.545: Finger status (picture number, mean) : 0 , 0 363s (process:1873): libfprint-egis0570-DEBUG: 00:53:32.545: Finger status (picture number, mean) : 1 , 0 363s (process:1873): libfprint-egis0570-DEBUG: 00:53:32.545: Finger status (picture number, mean) : 2 , 0 363s (process:1873): libfprint-egis0570-DEBUG: 00:53:32.545: Finger status (picture number, mean) : 3 , 0 363s (process:1873): libfprint-egis0570-DEBUG: 00:53:32.545: Finger status (picture number, mean) : 4 , 0 363s (process:1873): libfprint-image_device-DEBUG: 00:53:32.545: Image device reported finger status: off 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.545: [egis0570] SM_STATES_NUM entering state 5 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.545: [egis0570] SM_STATES_NUM entering state 1 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.545: [egis0570] SM_STATES_NUM entering state 2 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.545: [egis0570] SM_STATES_NUM entering state 3 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.545: [egis0570] SM_STATES_NUM entering state 2 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.546: [egis0570] SM_STATES_NUM entering state 3 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.546: [egis0570] SM_STATES_NUM entering state 2 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.547: [egis0570] SM_STATES_NUM entering state 3 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.547: [egis0570] SM_STATES_NUM entering state 2 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.548: [egis0570] SM_STATES_NUM entering state 3 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.548: [egis0570] SM_STATES_NUM entering state 4 363s (process:1873): libfprint-egis0570-DEBUG: 00:53:32.548: Finger status (picture number, mean) : 0 , 0 363s (process:1873): libfprint-egis0570-DEBUG: 00:53:32.548: Finger status (picture number, mean) : 1 , 0 363s (process:1873): libfprint-egis0570-DEBUG: 00:53:32.548: Finger status (picture number, mean) : 2 , 0 363s (process:1873): libfprint-egis0570-DEBUG: 00:53:32.548: Finger status (picture number, mean) : 3 , 0 363s (process:1873): libfprint-egis0570-DEBUG: 00:53:32.548: Finger status (picture number, mean) : 4 , 0 363s (process:1873): libfprint-image_device-DEBUG: 00:53:32.548: Image device reported finger status: off 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.548: [egis0570] SM_STATES_NUM entering state 5 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.548: [egis0570] SM_STATES_NUM entering state 1 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.548: [egis0570] SM_STATES_NUM entering state 2 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.549: [egis0570] SM_STATES_NUM entering state 3 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.549: [egis0570] SM_STATES_NUM entering state 2 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.550: [egis0570] SM_STATES_NUM entering state 3 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.550: [egis0570] SM_STATES_NUM entering state 2 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.552: [egis0570] SM_STATES_NUM entering state 3 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.552: [egis0570] SM_STATES_NUM entering state 2 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.553: [egis0570] SM_STATES_NUM entering state 3 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.553: [egis0570] SM_STATES_NUM entering state 4 363s (process:1873): libfprint-egis0570-DEBUG: 00:53:32.553: Finger status (picture number, mean) : 0 , 0 363s (process:1873): libfprint-egis0570-DEBUG: 00:53:32.553: Finger status (picture number, mean) : 1 , 0 363s (process:1873): libfprint-egis0570-DEBUG: 00:53:32.553: Finger status (picture number, mean) : 2 , 0 363s (process:1873): libfprint-egis0570-DEBUG: 00:53:32.553: Finger status (picture number, mean) : 3 , 0 363s (process:1873): libfprint-egis0570-DEBUG: 00:53:32.553: Finger status (picture number, mean) : 4 , 0 363s (process:1873): libfprint-image_device-DEBUG: 00:53:32.553: Image device reported finger status: off 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.553: [egis0570] SM_STATES_NUM entering state 5 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.553: [egis0570] SM_STATES_NUM entering state 1 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.553: [egis0570] SM_STATES_NUM entering state 2 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.554: [egis0570] SM_STATES_NUM entering state 3 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.554: [egis0570] SM_STATES_NUM entering state 2 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.555: [egis0570] SM_STATES_NUM entering state 3 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.555: [egis0570] SM_STATES_NUM entering state 2 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.556: [egis0570] SM_STATES_NUM entering state 3 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.556: [egis0570] SM_STATES_NUM entering state 2 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.557: [egis0570] SM_STATES_NUM entering state 3 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.557: [egis0570] SM_STATES_NUM entering state 4 363s (process:1873): libfprint-egis0570-DEBUG: 00:53:32.557: Finger status (picture number, mean) : 0 , 0 363s (process:1873): libfprint-egis0570-DEBUG: 00:53:32.557: Finger status (picture number, mean) : 1 , 0 363s (process:1873): libfprint-egis0570-DEBUG: 00:53:32.557: Finger status (picture number, mean) : 2 , 0 363s (process:1873): libfprint-egis0570-DEBUG: 00:53:32.557: Finger status (picture number, mean) : 3 , 0 363s (process:1873): libfprint-egis0570-DEBUG: 00:53:32.557: Finger status (picture number, mean) : 4 , 0 363s (process:1873): libfprint-image_device-DEBUG: 00:53:32.557: Image device reported finger status: off 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.557: [egis0570] SM_STATES_NUM entering state 5 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.557: [egis0570] SM_STATES_NUM entering state 1 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.557: [egis0570] SM_STATES_NUM entering state 2 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.558: [egis0570] SM_STATES_NUM entering state 3 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.558: [egis0570] SM_STATES_NUM entering state 2 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.558: [egis0570] SM_STATES_NUM entering state 3 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.559: [egis0570] SM_STATES_NUM entering state 2 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.559: [egis0570] SM_STATES_NUM entering state 3 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.560: [egis0570] SM_STATES_NUM entering state 2 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.560: [egis0570] SM_STATES_NUM entering state 3 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.560: [egis0570] SM_STATES_NUM entering state 4 363s (process:1873): libfprint-egis0570-DEBUG: 00:53:32.562: Finger status (picture number, mean) : 0 , 0 363s (process:1873): libfprint-egis0570-DEBUG: 00:53:32.562: Finger status (picture number, mean) : 1 , 1 363s (process:1873): libfprint-egis0570-DEBUG: 00:53:32.562: Finger status (picture number, mean) : 2 , 2 363s (process:1873): libfprint-egis0570-DEBUG: 00:53:32.562: Finger status (picture number, mean) : 3 , 3 363s (process:1873): libfprint-egis0570-DEBUG: 00:53:32.562: Finger status (picture number, mean) : 4 , 6 363s (process:1873): libfprint-image_device-DEBUG: 00:53:32.562: Image device reported finger status: off 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.562: [egis0570] SM_STATES_NUM entering state 5 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.562: [egis0570] SM_STATES_NUM entering state 1 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.562: [egis0570] SM_STATES_NUM entering state 2 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.563: [egis0570] SM_STATES_NUM entering state 3 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.563: [egis0570] SM_STATES_NUM entering state 2 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.564: [egis0570] SM_STATES_NUM entering state 3 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.564: [egis0570] SM_STATES_NUM entering state 2 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.565: [egis0570] SM_STATES_NUM entering state 3 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.566: [egis0570] SM_STATES_NUM entering state 2 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.566: [egis0570] SM_STATES_NUM entering state 3 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.566: [egis0570] SM_STATES_NUM entering state 4 363s (process:1873): libfprint-egis0570-DEBUG: 00:53:32.567: Finger status (picture number, mean) : 0 , 11 363s (process:1873): libfprint-egis0570-DEBUG: 00:53:32.567: Finger status (picture number, mean) : 1 , 16 363s (process:1873): libfprint-egis0570-DEBUG: 00:53:32.567: Finger status (picture number, mean) : 2 , 23 363s (process:1873): libfprint-egis0570-DEBUG: 00:53:32.567: Finger status (picture number, mean) : 3 , 28 363s (process:1873): libfprint-egis0570-DEBUG: 00:53:32.567: Finger status (picture number, mean) : 4 , 32 363s (process:1873): libfprint-device-DEBUG: 00:53:32.567: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 363s (process:1873): libfprint-image_device-DEBUG: 00:53:32.567: Image device reported finger status: on 363s (process:1873): libfprint-image_device-DEBUG: 00:53:32.567: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 363s (process:1873): libfprint-device-DEBUG: 00:53:32.567: Device reported finger status change: FP_FINGER_STATUS_NEEDED 363s (process:1873): libfprint-image_device-DEBUG: 00:53:32.567: Image device reported finger status: off 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.567: [egis0570] SM_STATES_NUM entering state 5 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.567: [egis0570] SM_STATES_NUM entering state 1 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.567: [egis0570] SM_STATES_NUM entering state 2 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.567: [egis0570] SM_STATES_NUM entering state 3 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.568: [egis0570] SM_STATES_NUM entering state 2 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.568: [egis0570] SM_STATES_NUM entering state 3 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.569: [egis0570] SM_STATES_NUM entering state 2 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.569: [egis0570] SM_STATES_NUM entering state 3 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.569: [egis0570] SM_STATES_NUM entering state 2 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.570: [egis0570] SM_STATES_NUM entering state 3 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.570: [egis0570] SM_STATES_NUM entering state 4 363s (process:1873): libfprint-egis0570-DEBUG: 00:53:32.571: Finger status (picture number, mean) : 0 , 38 363s (process:1873): libfprint-egis0570-DEBUG: 00:53:32.571: Finger status (picture number, mean) : 1 , 43 363s (process:1873): libfprint-egis0570-DEBUG: 00:53:32.571: Finger status (picture number, mean) : 2 , 48 363s (process:1873): libfprint-egis0570-DEBUG: 00:53:32.571: Finger status (picture number, mean) : 3 , 54 363s (process:1873): libfprint-egis0570-DEBUG: 00:53:32.571: Finger status (picture number, mean) : 4 , 58 363s (process:1873): libfprint-device-DEBUG: 00:53:32.571: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 363s (process:1873): libfprint-image_device-DEBUG: 00:53:32.571: Image device reported finger status: on 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.571: [egis0570] SM_STATES_NUM entering state 5 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.571: [egis0570] SM_STATES_NUM entering state 1 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.571: [egis0570] SM_STATES_NUM entering state 2 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.571: [egis0570] SM_STATES_NUM entering state 3 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.571: [egis0570] SM_STATES_NUM entering state 2 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.572: [egis0570] SM_STATES_NUM entering state 3 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.572: [egis0570] SM_STATES_NUM entering state 2 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.573: [egis0570] SM_STATES_NUM entering state 3 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.573: [egis0570] SM_STATES_NUM entering state 2 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.574: [egis0570] SM_STATES_NUM entering state 3 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.574: [egis0570] SM_STATES_NUM entering state 4 363s (process:1873): libfprint-egis0570-DEBUG: 00:53:32.575: Finger status (picture number, mean) : 0 , 62 363s (process:1873): libfprint-egis0570-DEBUG: 00:53:32.575: Finger status (picture number, mean) : 1 , 68 363s (process:1873): libfprint-egis0570-DEBUG: 00:53:32.575: Finger status (picture number, mean) : 2 , 71 363s (process:1873): libfprint-egis0570-DEBUG: 00:53:32.575: Finger status (picture number, mean) : 3 , 73 363s (process:1873): libfprint-egis0570-DEBUG: 00:53:32.575: Finger status (picture number, mean) : 4 , 77 363s (process:1873): libfprint-image_device-DEBUG: 00:53:32.575: Image device reported finger status: on 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.575: [egis0570] SM_STATES_NUM entering state 5 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.575: [egis0570] SM_STATES_NUM entering state 1 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.575: [egis0570] SM_STATES_NUM entering state 2 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.575: [egis0570] SM_STATES_NUM entering state 3 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.576: [egis0570] SM_STATES_NUM entering state 2 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.576: [egis0570] SM_STATES_NUM entering state 3 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.577: [egis0570] SM_STATES_NUM entering state 2 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.577: [egis0570] SM_STATES_NUM entering state 3 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.578: [egis0570] SM_STATES_NUM entering state 2 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.578: [egis0570] SM_STATES_NUM entering state 3 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.578: [egis0570] SM_STATES_NUM entering state 4 363s (process:1873): libfprint-egis0570-DEBUG: 00:53:32.579: Finger status (picture number, mean) : 0 , 79 363s (process:1873): libfprint-egis0570-DEBUG: 00:53:32.579: Finger status (picture number, mean) : 1 , 79 363s (process:1873): libfprint-egis0570-DEBUG: 00:53:32.579: Finger status (picture number, mean) : 2 , 82 363s (process:1873): libfprint-egis0570-DEBUG: 00:53:32.579: Finger status (picture number, mean) : 3 , 84 363s (process:1873): libfprint-egis0570-DEBUG: 00:53:32.579: Finger status (picture number, mean) : 4 , 85 363s (process:1873): libfprint-image_device-DEBUG: 00:53:32.579: Image device reported finger status: on 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.579: [egis0570] SM_STATES_NUM entering state 5 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.579: [egis0570] SM_STATES_NUM entering state 1 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.579: [egis0570] SM_STATES_NUM entering state 2 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.579: [egis0570] SM_STATES_NUM entering state 3 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.580: [egis0570] SM_STATES_NUM entering state 2 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.580: [egis0570] SM_STATES_NUM entering state 3 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.580: [egis0570] SM_STATES_NUM entering state 2 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.581: [egis0570] SM_STATES_NUM entering state 3 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.581: [egis0570] SM_STATES_NUM entering state 2 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.582: [egis0570] SM_STATES_NUM entering state 3 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.582: [egis0570] SM_STATES_NUM entering state 4 363s (process:1873): libfprint-egis0570-DEBUG: 00:53:32.583: Finger status (picture number, mean) : 0 , 88 363s (process:1873): libfprint-egis0570-DEBUG: 00:53:32.583: Finger status (picture number, mean) : 1 , 89 363s (process:1873): libfprint-egis0570-DEBUG: 00:53:32.583: Finger status (picture number, mean) : 2 , 90 363s (process:1873): libfprint-egis0570-DEBUG: 00:53:32.583: Finger status (picture number, mean) : 3 , 92 363s (process:1873): libfprint-egis0570-DEBUG: 00:53:32.583: Finger status (picture number, mean) : 4 , 92 363s (process:1873): libfprint-image_device-DEBUG: 00:53:32.583: Image device reported finger status: on 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.583: [egis0570] SM_STATES_NUM entering state 5 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.583: [egis0570] SM_STATES_NUM entering state 1 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.583: [egis0570] SM_STATES_NUM entering state 2 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.583: [egis0570] SM_STATES_NUM entering state 3 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.584: [egis0570] SM_STATES_NUM entering state 2 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.584: [egis0570] SM_STATES_NUM entering state 3 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.585: [egis0570] SM_STATES_NUM entering state 2 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.585: [egis0570] SM_STATES_NUM entering state 3 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.586: [egis0570] SM_STATES_NUM entering state 2 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.586: [egis0570] SM_STATES_NUM entering state 3 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.586: [egis0570] SM_STATES_NUM entering state 4 363s (process:1873): libfprint-egis0570-DEBUG: 00:53:32.587: Finger status (picture number, mean) : 0 , 93 363s (process:1873): libfprint-egis0570-DEBUG: 00:53:32.587: Finger status (picture number, mean) : 1 , 94 363s (process:1873): libfprint-egis0570-DEBUG: 00:53:32.587: Finger status (picture number, mean) : 2 , 95 363s (process:1873): libfprint-egis0570-DEBUG: 00:53:32.587: Finger status (picture number, mean) : 3 , 96 363s (process:1873): libfprint-egis0570-DEBUG: 00:53:32.587: Finger status (picture number, mean) : 4 , 97 363s (process:1873): libfprint-image_device-DEBUG: 00:53:32.587: Image device reported finger status: on 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.587: [egis0570] SM_STATES_NUM entering state 5 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.587: [egis0570] SM_STATES_NUM entering state 1 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.587: [egis0570] SM_STATES_NUM entering state 2 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.588: [egis0570] SM_STATES_NUM entering state 3 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.588: [egis0570] SM_STATES_NUM entering state 2 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.588: [egis0570] SM_STATES_NUM entering state 3 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.589: [egis0570] SM_STATES_NUM entering state 2 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.590: [egis0570] SM_STATES_NUM entering state 3 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.590: [egis0570] SM_STATES_NUM entering state 2 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.591: [egis0570] SM_STATES_NUM entering state 3 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.591: [egis0570] SM_STATES_NUM entering state 4 363s (process:1873): libfprint-egis0570-DEBUG: 00:53:32.591: Finger status (picture number, mean) : 0 , 97 363s (process:1873): libfprint-egis0570-DEBUG: 00:53:32.591: Finger status (picture number, mean) : 1 , 95 363s (process:1873): libfprint-egis0570-DEBUG: 00:53:32.591: Finger status (picture number, mean) : 2 , 95 363s (process:1873): libfprint-egis0570-DEBUG: 00:53:32.591: Finger status (picture number, mean) : 3 , 96 363s (process:1873): libfprint-egis0570-DEBUG: 00:53:32.591: Finger status (picture number, mean) : 4 , 97 363s (process:1873): libfprint-image_device-DEBUG: 00:53:32.591: Image device reported finger status: on 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.591: [egis0570] SM_STATES_NUM entering state 5 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.591: [egis0570] SM_STATES_NUM entering state 1 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.591: [egis0570] SM_STATES_NUM entering state 2 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.592: [egis0570] SM_STATES_NUM entering state 3 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.592: [egis0570] SM_STATES_NUM entering state 2 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.593: [egis0570] SM_STATES_NUM entering state 3 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.593: [egis0570] SM_STATES_NUM entering state 2 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.593: [egis0570] SM_STATES_NUM entering state 3 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.594: [egis0570] SM_STATES_NUM entering state 2 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.594: [egis0570] SM_STATES_NUM entering state 3 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.595: [egis0570] SM_STATES_NUM entering state 4 363s (process:1873): libfprint-egis0570-DEBUG: 00:53:32.595: Finger status (picture number, mean) : 0 , 96 363s (process:1873): libfprint-egis0570-DEBUG: 00:53:32.595: Finger status (picture number, mean) : 1 , 97 363s (process:1873): libfprint-egis0570-DEBUG: 00:53:32.595: Finger status (picture number, mean) : 2 , 98 363s (process:1873): libfprint-egis0570-DEBUG: 00:53:32.595: Finger status (picture number, mean) : 3 , 98 363s (process:1873): libfprint-egis0570-DEBUG: 00:53:32.595: Finger status (picture number, mean) : 4 , 98 363s (process:1873): libfprint-image_device-DEBUG: 00:53:32.595: Image device reported finger status: on 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.595: [egis0570] SM_STATES_NUM entering state 5 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.595: [egis0570] SM_STATES_NUM entering state 1 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.595: [egis0570] SM_STATES_NUM entering state 2 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.596: [egis0570] SM_STATES_NUM entering state 3 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.596: [egis0570] SM_STATES_NUM entering state 2 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.597: [egis0570] SM_STATES_NUM entering state 3 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.597: [egis0570] SM_STATES_NUM entering state 2 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.597: [egis0570] SM_STATES_NUM entering state 3 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.598: [egis0570] SM_STATES_NUM entering state 2 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.598: [egis0570] SM_STATES_NUM entering state 3 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.598: [egis0570] SM_STATES_NUM entering state 4 363s (process:1873): libfprint-egis0570-DEBUG: 00:53:32.599: Finger status (picture number, mean) : 0 , 98 363s (process:1873): libfprint-egis0570-DEBUG: 00:53:32.599: Finger status (picture number, mean) : 1 , 99 363s (process:1873): libfprint-egis0570-DEBUG: 00:53:32.599: Finger status (picture number, mean) : 2 , 100 363s (process:1873): libfprint-egis0570-DEBUG: 00:53:32.599: Finger status (picture number, mean) : 3 , 99 363s (process:1873): libfprint-egis0570-DEBUG: 00:53:32.599: Finger status (picture number, mean) : 4 , 97 363s (process:1873): libfprint-image_device-DEBUG: 00:53:32.599: Image device reported finger status: on 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.599: [egis0570] SM_STATES_NUM entering state 5 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.599: [egis0570] SM_STATES_NUM entering state 1 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.599: [egis0570] SM_STATES_NUM entering state 2 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.599: [egis0570] SM_STATES_NUM entering state 3 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.600: [egis0570] SM_STATES_NUM entering state 2 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.600: [egis0570] SM_STATES_NUM entering state 3 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.600: [egis0570] SM_STATES_NUM entering state 2 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.601: [egis0570] SM_STATES_NUM entering state 3 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.601: [egis0570] SM_STATES_NUM entering state 2 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.602: [egis0570] SM_STATES_NUM entering state 3 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.602: [egis0570] SM_STATES_NUM entering state 4 363s (process:1873): libfprint-egis0570-DEBUG: 00:53:32.603: Finger status (picture number, mean) : 0 , 98 363s (process:1873): libfprint-egis0570-DEBUG: 00:53:32.603: Finger status (picture number, mean) : 1 , 98 363s (process:1873): libfprint-egis0570-DEBUG: 00:53:32.603: Finger status (picture number, mean) : 2 , 98 363s (process:1873): libfprint-egis0570-DEBUG: 00:53:32.603: Finger status (picture number, mean) : 3 , 95 363s (process:1873): libfprint-egis0570-DEBUG: 00:53:32.603: Finger status (picture number, mean) : 4 , 91 363s (process:1873): libfprint-image_device-DEBUG: 00:53:32.603: Image device reported finger status: on 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.603: [egis0570] SM_STATES_NUM entering state 5 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.603: [egis0570] SM_STATES_NUM entering state 1 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.603: [egis0570] SM_STATES_NUM entering state 2 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.603: [egis0570] SM_STATES_NUM entering state 3 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.603: [egis0570] SM_STATES_NUM entering state 2 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.604: [egis0570] SM_STATES_NUM entering state 3 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.604: [egis0570] SM_STATES_NUM entering state 2 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.605: [egis0570] SM_STATES_NUM entering state 3 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.605: [egis0570] SM_STATES_NUM entering state 2 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.606: [egis0570] SM_STATES_NUM entering state 3 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.606: [egis0570] SM_STATES_NUM entering state 4 363s (process:1873): libfprint-egis0570-DEBUG: 00:53:32.606: Finger status (picture number, mean) : 0 , 88 363s (process:1873): libfprint-egis0570-DEBUG: 00:53:32.606: Finger status (picture number, mean) : 1 , 88 363s (process:1873): libfprint-egis0570-DEBUG: 00:53:32.606: Finger status (picture number, mean) : 2 , 88 363s (process:1873): libfprint-egis0570-DEBUG: 00:53:32.606: Finger status (picture number, mean) : 3 , 87 363s (process:1873): libfprint-egis0570-DEBUG: 00:53:32.606: Finger status (picture number, mean) : 4 , 89 363s (process:1873): libfprint-image_device-DEBUG: 00:53:32.606: Image device reported finger status: on 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.606: [egis0570] SM_STATES_NUM entering state 5 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.606: [egis0570] SM_STATES_NUM entering state 1 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.606: [egis0570] SM_STATES_NUM entering state 2 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.607: [egis0570] SM_STATES_NUM entering state 3 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.607: [egis0570] SM_STATES_NUM entering state 2 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.608: [egis0570] SM_STATES_NUM entering state 3 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.608: [egis0570] SM_STATES_NUM entering state 2 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.609: [egis0570] SM_STATES_NUM entering state 3 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.609: [egis0570] SM_STATES_NUM entering state 2 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.610: [egis0570] SM_STATES_NUM entering state 3 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.610: [egis0570] SM_STATES_NUM entering state 4 363s (process:1873): libfprint-egis0570-DEBUG: 00:53:32.610: Finger status (picture number, mean) : 0 , 88 363s (process:1873): libfprint-egis0570-DEBUG: 00:53:32.610: Finger status (picture number, mean) : 1 , 89 363s (process:1873): libfprint-egis0570-DEBUG: 00:53:32.610: Finger status (picture number, mean) : 2 , 90 363s (process:1873): libfprint-egis0570-DEBUG: 00:53:32.610: Finger status (picture number, mean) : 3 , 91 363s (process:1873): libfprint-egis0570-DEBUG: 00:53:32.610: Finger status (picture number, mean) : 4 , 89 363s (process:1873): libfprint-image_device-DEBUG: 00:53:32.610: Image device reported finger status: on 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.610: [egis0570] SM_STATES_NUM entering state 5 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.610: [egis0570] SM_STATES_NUM entering state 1 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.610: [egis0570] SM_STATES_NUM entering state 2 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.611: [egis0570] SM_STATES_NUM entering state 3 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.611: [egis0570] SM_STATES_NUM entering state 2 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.612: [egis0570] SM_STATES_NUM entering state 3 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.612: [egis0570] SM_STATES_NUM entering state 2 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.613: [egis0570] SM_STATES_NUM entering state 3 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.613: [egis0570] SM_STATES_NUM entering state 2 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.613: [egis0570] SM_STATES_NUM entering state 3 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.613: [egis0570] SM_STATES_NUM entering state 4 363s (process:1873): libfprint-egis0570-DEBUG: 00:53:32.614: Finger status (picture number, mean) : 0 , 90 363s (process:1873): libfprint-egis0570-DEBUG: 00:53:32.614: Finger status (picture number, mean) : 1 , 89 363s (process:1873): libfprint-egis0570-DEBUG: 00:53:32.614: Finger status (picture number, mean) : 2 , 85 363s (process:1873): libfprint-egis0570-DEBUG: 00:53:32.614: Finger status (picture number, mean) : 3 , 75 363s (process:1873): libfprint-egis0570-DEBUG: 00:53:32.614: Finger status (picture number, mean) : 4 , 46 363s (process:1873): libfprint-image_device-DEBUG: 00:53:32.614: Image device reported finger status: on 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.614: [egis0570] SM_STATES_NUM entering state 5 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.614: [egis0570] SM_STATES_NUM entering state 1 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.614: [egis0570] SM_STATES_NUM entering state 2 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.614: [egis0570] SM_STATES_NUM entering state 3 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.615: [egis0570] SM_STATES_NUM entering state 2 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.615: [egis0570] SM_STATES_NUM entering state 3 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.616: [egis0570] SM_STATES_NUM entering state 2 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.616: [egis0570] SM_STATES_NUM entering state 3 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.616: [egis0570] SM_STATES_NUM entering state 2 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.617: [egis0570] SM_STATES_NUM entering state 3 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.617: [egis0570] SM_STATES_NUM entering state 4 363s (process:1873): libfprint-egis0570-DEBUG: 00:53:32.618: Finger status (picture number, mean) : 0 , 17 363s (process:1873): libfprint-egis0570-DEBUG: 00:53:32.618: Finger status (picture number, mean) : 1 , 14 363s (process:1873): libfprint-egis0570-DEBUG: 00:53:32.618: Finger status (picture number, mean) : 2 , 15 363s (process:1873): libfprint-egis0570-DEBUG: 00:53:32.618: Finger status (picture number, mean) : 3 , 15 363s (process:1873): libfprint-egis0570-DEBUG: 00:53:32.618: Finger status (picture number, mean) : 4 , 15 363s (process:1873): libfprint-assembling-DEBUG: 00:53:32.699: calc delta completed in 0.081911 secs 363s (process:1873): libfprint-assembling-DEBUG: 00:53:32.782: calc delta completed in 0.082584 secs 363s (process:1873): libfprint-assembling-DEBUG: 00:53:32.782: errors: 10243 rev: 29954 363s (process:1873): libfprint-assembling-DEBUG: 00:53:32.865: calc delta completed in 0.082427 secs 363s (process:1873): libfprint-assembling-DEBUG: 00:53:32.865: height is 292 363s (process:1873): libfprint-image_device-DEBUG: 00:53:32.867: Image device captured an image 363s (process:1873): libfprint-image_device-DEBUG: 00:53:32.868: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 363s (process:1873): libfprint-device-DEBUG: 00:53:32.868: Device reported finger status change: FP_FINGER_STATUS_PRESENT 363s (process:1873): libfprint-device-DEBUG: 00:53:32.868: Device reported finger status change: FP_FINGER_STATUS_NONE 363s (process:1873): libfprint-image_device-DEBUG: 00:53:32.868: Image device reported finger status: off 363s (process:1873): libfprint-image_device-DEBUG: 00:53:32.868: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 363s (process:1873): libfprint-image_device-DEBUG: 00:53:32.868: Deactivating image device 363s (process:1873): libfprint-image_device-DEBUG: 00:53:32.868: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_DEACTIVATING 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.868: [egis0570] SM_STATES_NUM entering state 5 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.868: [egis0570] SM_STATES_NUM entering state 1 363s (process:1873): libfprint-egis0570-DEBUG: 00:53:32.868: deactivating, marking completed 363s (process:1873): libfprint-SSM-DEBUG: 00:53:32.868: [egis0570] SM_STATES_NUM completed successfully 363s (process:1873): libfprint-image_device-DEBUG: 00:53:32.868: Image device deactivation completed 363s (process:1873): libfprint-image_device-DEBUG: 00:53:32.868: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE 363s (process:1873): libfprint-image-DEBUG: 00:53:32.918: Minutiae scan completed in 0.049284 secs 363s (process:1873): libfprint-device-DEBUG: 00:53:32.918: Device reported capture completion 363s (process:1873): libfprint-device-DEBUG: 00:53:32.918: Completing action FPI_DEVICE_ACTION_CAPTURE in idle! 363s (process:1873): libfprint-device-DEBUG: 00:53:32.918: Updated temperature model after 0.43 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 363s (process:1873): libfprint-image_device-DEBUG: 00:53:32.919: Image device close completed 363s (process:1873): libfprint-device-DEBUG: 00:53:32.919: Device reported close completion 363s (process:1873): libfprint-device-DEBUG: 00:53:32.919: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 363s (process:1873): libfprint-device-DEBUG: 00:53:32.919: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 364s ** (umockdev-run:1869): DEBUG: 00:53:33.221: umockdev.vala:154: Removing test bed /tmp/umockdev.PEP312 364s (umockdev-run:1869): GLib-DEBUG: 00:53:33.228: unsetenv() is not thread-safe and should not be used after threads are created 364s Comparing PNGs /tmp/libfprint-umockdev-test-4pk3b50h/capture.png and /usr/share/installed-tests/libfprint-2/egis0570/capture.png 364s PASS: libfprint-2/driver-egis0570.test 364s Running test: libfprint-2/driver-fpcmoc.test 364s ** (umockdev-run:1882): DEBUG: 00:53:33.359: umockdev.vala:127: Created udev test bed /tmp/umockdev.WNQ512 364s ** (umockdev-run:1882): DEBUG: 00:53:33.359: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0/usb1/1-1 364s ** (umockdev-run:1882): DEBUG: 00:53:33.361: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0/usb1/1-1 (subsystem usb) 364s ** (umockdev-run:1882): DEBUG: 00:53:33.368: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.WNQ512/dev/bus/usb/001/019 364s ** (umockdev-run:1882): DEBUG: 00:53:33.368: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0/usb1 364s ** (umockdev-run:1882): DEBUG: 00:53:33.369: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0/usb1 (subsystem usb) 364s ** (umockdev-run:1882): DEBUG: 00:53:33.374: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.WNQ512/dev/bus/usb/001/001 364s ** (umockdev-run:1882): DEBUG: 00:53:33.374: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0 364s ** (umockdev-run:1882): DEBUG: 00:53:33.374: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0 (subsystem pci) 364s (process:1886): libfprint-context-DEBUG: 00:53:33.487: Initializing FpContext (libfprint version 1.94.8+tod1) 364s (process:1886): libfprint-tod-DEBUG: 00:53:33.487: Impossible to load the shared drivers dir Error opening directory “/usr/lib/arm-linux-gnueabihf/libfprint-2/tod-1”: No such file or directory 364s (process:1886): libfprint-DEBUG: 00:53:33.490: fpi_device_fpcmoc_init enter --> 364s (process:1886): libfprint-DEBUG: 00:53:33.490: 7399781551684: ../libfprint/drivers/fpcmoc/fpc.c:1873 364s (process:1886): libfprint-context-DEBUG: 00:53:33.491: No driver found for USB device 1D6B:0002 364s (process:1886): libfprint-DEBUG: 00:53:33.491: fpc_dev_probe enter --> 364s (process:1886): libfprint-DEBUG: 00:53:33.494: Device name: FPC L:0001 FW:127010 364s (process:1886): libfprint-device-DEBUG: 00:53:33.494: Device reported probe completion 364s (process:1886): libfprint-device-DEBUG: 00:53:33.494: Completing action FPI_DEVICE_ACTION_PROBE in idle! 364s (process:1886): libfprint-device-DEBUG: 00:53:33.494: Not updating temperature model, device can run continuously! 364s (process:1886): libfprint-DEBUG: 00:53:33.496: fpc_dev_open enter --> 364s (process:1886): libfprint-SSM-DEBUG: 00:53:33.496: [fpcmoc] FP_INIT_NUM_STATES entering state 0 364s (process:1886): libfprint-SSM-DEBUG: 00:53:33.496: [fpcmoc] FP_CMD_NUM_STATES entering state 0 364s (process:1886): libfprint-DEBUG: 00:53:33.496: fpc_send_ctrl_cmd CMD: 0x1, value: 0x1, index: 0 type: 2 364s (process:1886): libfprint-DEBUG: 00:53:33.497: fpc_cmd_receive_cb current ssm request: 1 state: 0 364s (process:1886): libfprint-SSM-DEBUG: 00:53:33.497: [fpcmoc] FP_CMD_NUM_STATES entering state 1 364s (process:1886): libfprint-DEBUG: 00:53:33.497: fpc_cmd_receive_cb current ssm request: 1 state: 1 364s (process:1886): libfprint-DEBUG: 00:53:33.497: fpc_cmd_receive_cb recv evt data length: 38 364s (process:1886): libfprint-DEBUG: 00:53:33.497: fpc_evt_cb INIT: status=0, Sensor = 1523, HWID = 0x1711, WxH = 96 x 96 364s (process:1886): libfprint-DEBUG: 00:53:33.497: fpc_evt_cb INIT: FW version: 1.27.0.10 364s (process:1886): libfprint-SSM-DEBUG: 00:53:33.497: [fpcmoc] FP_INIT_NUM_STATES entering state 1 364s (process:1886): libfprint-SSM-DEBUG: 00:53:33.497: [fpcmoc] FP_CMD_NUM_STATES entering state 0 364s (process:1886): libfprint-DEBUG: 00:53:33.497: fpc_send_ctrl_cmd CMD: 0x60, value: 0x0, index: 0 type: 3 364s (process:1886): libfprint-SSM-DEBUG: 00:53:33.498: [fpcmoc] FP_CMD_NUM_STATES completed successfully 364s (process:1886): libfprint-DEBUG: 00:53:33.498: fpc_cmd_receive_cb current ssm request: 96 state: 0 364s (process:1886): libfprint-DEBUG: 00:53:33.498: fpc_init_load_db_cb got dbid size: 16 364s (process:1886): libfprint-DEBUG: 00:53:33.498: fpc_init_load_db_cb dbid: 0xa981b581-adfc-e643-a0d0-88c2138092f7 364s (process:1886): libfprint-SSM-DEBUG: 00:53:33.498: [fpcmoc] FP_INIT_NUM_STATES completed successfully 364s (process:1886): libfprint-device-DEBUG: 00:53:33.498: Device reported open completion 364s (process:1886): libfprint-SSM-DEBUG: 00:53:33.498: [fpcmoc] FP_CMD_NUM_STATES completed successfully 364s (process:1886): libfprint-device-DEBUG: 00:53:33.498: Completing action FPI_DEVICE_ACTION_OPEN in idle! 364s (process:1886): libfprint-device-DEBUG: 00:53:33.498: Not updating temperature model, device can run continuously! 364s (process:1886): libfprint-DEBUG: 00:53:33.498: fpc_dev_clear_storage enter --> 364s (process:1886): libfprint-SSM-DEBUG: 00:53:33.498: [fpcmoc] Clear storage entering state 0 364s (process:1886): libfprint-SSM-DEBUG: 00:53:33.498: [fpcmoc] FP_CMD_NUM_STATES entering state 0 364s (process:1886): libfprint-DEBUG: 00:53:33.498: fpc_send_ctrl_cmd CMD: 0x62, value: 0x0, index: 0 type: 1 364s (process:1886): libfprint-DEBUG: 00:53:33.498: fpc_cmd_receive_cb current ssm request: 98 state: 0 364s (process:1886): libfprint-SSM-DEBUG: 00:53:33.498: [fpcmoc] Clear storage entering state 1 364s (process:1886): libfprint-SSM-DEBUG: 00:53:33.498: [fpcmoc] FP_CMD_NUM_STATES entering state 0 364s (process:1886): libfprint-DEBUG: 00:53:33.499: fpc_send_ctrl_cmd CMD: 0x60, value: 0x1, index: 0 type: 1 364s (process:1886): libfprint-SSM-DEBUG: 00:53:33.499: [fpcmoc] FP_CMD_NUM_STATES completed successfully 364s (process:1886): libfprint-DEBUG: 00:53:33.499: fpc_cmd_receive_cb current ssm request: 96 state: 0 364s (process:1886): libfprint-SSM-DEBUG: 00:53:33.499: [fpcmoc] Clear storage completed successfully 364s (process:1886): libfprint-DEBUG: 00:53:33.499: Clear Storage complete! 364s (process:1886): libfprint-device-DEBUG: 00:53:33.499: Device reported deletion completion 364s (process:1886): libfprint-SSM-DEBUG: 00:53:33.499: [fpcmoc] FP_CMD_NUM_STATES completed successfully 364s (process:1886): libfprint-device-DEBUG: 00:53:33.499: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 364s (process:1886): libfprint-device-DEBUG: 00:53:33.499: Not updating temperature model, device can run continuously! 364s (process:1886): libfprint-device-DEBUG: 00:53:33.500: Not updating temperature model, device can run continuously! 364s (process:1886): libfprint-DEBUG: 00:53:33.500: fpc_dev_enroll enter --> 364s (process:1886): libfprint-SSM-DEBUG: 00:53:33.500: [fpcmoc] enroll entering state 0 364s (process:1886): libfprint-SSM-DEBUG: 00:53:33.500: [fpcmoc] FP_CMD_NUM_STATES entering state 0 364s (process:1886): libfprint-DEBUG: 00:53:33.500: fpc_send_ctrl_cmd CMD: 0x70, value: 0x0, index: 0 type: 2 364s (process:1886): libfprint-DEBUG: 00:53:33.501: fpc_cmd_receive_cb current ssm request: 112 state: 0 364s (process:1886): libfprint-SSM-DEBUG: 00:53:33.501: [fpcmoc] FP_CMD_NUM_STATES entering state 1 364s (process:1886): libfprint-DEBUG: 00:53:33.501: fpc_cmd_receive_cb current ssm request: 112 state: 1 364s (process:1886): libfprint-DEBUG: 00:53:33.501: fpc_cmd_receive_cb recv evt data length: 790 364s (process:1886): libfprint-DEBUG: 00:53:33.501: fpc_evt_cb Enum Fids: status = 0, NumFids = 0 364s (process:1886): libfprint-SSM-DEBUG: 00:53:33.501: [fpcmoc] enroll entering state 1 364s (process:1886): libfprint-SSM-DEBUG: 00:53:33.501: [fpcmoc] FP_CMD_NUM_STATES entering state 0 364s (process:1886): libfprint-DEBUG: 00:53:33.501: fpc_send_ctrl_cmd CMD: 0x67, value: 0x0, index: 0 type: 3 364s (process:1886): libfprint-SSM-DEBUG: 00:53:33.501: [fpcmoc] FP_CMD_NUM_STATES completed successfully 364s (process:1886): libfprint-DEBUG: 00:53:33.502: fpc_cmd_receive_cb current ssm request: 103 state: 0 364s (process:1886): libfprint-SSM-DEBUG: 00:53:33.502: [fpcmoc] enroll entering state 2 364s (process:1886): libfprint-device-DEBUG: 00:53:33.502: Device reported finger status change: FP_FINGER_STATUS_NEEDED 364s (process:1886): libfprint-SSM-DEBUG: 00:53:33.502: [fpcmoc] FP_CMD_NUM_STATES entering state 0 364s (process:1886): libfprint-DEBUG: 00:53:33.502: fpc_send_ctrl_cmd CMD: 0x2, value: 0x1, index: 0 type: 2 364s (process:1886): libfprint-SSM-DEBUG: 00:53:33.502: [fpcmoc] FP_CMD_NUM_STATES completed successfully 364s (process:1886): libfprint-DEBUG: 00:53:33.502: fpc_cmd_receive_cb current ssm request: 2 state: 0 364s (process:1886): libfprint-SSM-DEBUG: 00:53:33.502: [fpcmoc] FP_CMD_NUM_STATES entering state 1 364s (process:1886): libfprint-DEBUG: 00:53:33.503: fpc_cmd_receive_cb current ssm request: 2 state: 1 364s (process:1886): libfprint-DEBUG: 00:53:33.503: fpc_cmd_receive_cb recv evt data length: 12 364s (process:1886): libfprint-DEBUG: 00:53:33.503: fpc_evt_cb Got finger down event (0) 364s (process:1886): libfprint-device-DEBUG: 00:53:33.503: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 364s (process:1886): libfprint-SSM-DEBUG: 00:53:33.503: [fpcmoc] enroll entering state 3 364s (process:1886): libfprint-SSM-DEBUG: 00:53:33.503: [fpcmoc] FP_CMD_NUM_STATES entering state 0 364s (process:1886): libfprint-DEBUG: 00:53:33.503: fpc_send_ctrl_cmd CMD: 0x9, value: 0x0, index: 0 type: 2 364s (process:1886): libfprint-SSM-DEBUG: 00:53:33.503: [fpcmoc] FP_CMD_NUM_STATES completed successfully 364s (process:1886): libfprint-DEBUG: 00:53:33.503: fpc_cmd_receive_cb current ssm request: 9 state: 0 364s (process:1886): libfprint-SSM-DEBUG: 00:53:33.503: [fpcmoc] FP_CMD_NUM_STATES entering state 1 364s (process:1886): libfprint-DEBUG: 00:53:33.504: fpc_cmd_receive_cb current ssm request: 9 state: 1 364s (process:1886): libfprint-DEBUG: 00:53:33.504: fpc_cmd_receive_cb recv evt data length: 24 364s (process:1886): libfprint-DEBUG: 00:53:33.504: fpc_evt_cb Got capture event 364s (process:1886): libfprint-device-DEBUG: 00:53:33.504: Device reported finger status change: FP_FINGER_STATUS_NEEDED 364s (process:1886): libfprint-SSM-DEBUG: 00:53:33.504: [fpcmoc] enroll entering state 4 364s (process:1886): libfprint-SSM-DEBUG: 00:53:33.504: [fpcmoc] FP_CMD_NUM_STATES entering state 0 364s (process:1886): libfprint-DEBUG: 00:53:33.504: fpc_send_ctrl_cmd CMD: 0x68, value: 0x0, index: 0 type: 3 364s (process:1886): libfprint-SSM-DEBUG: 00:53:33.504: [fpcmoc] FP_CMD_NUM_STATES completed successfully 364s (process:1886): libfprint-DEBUG: 00:53:33.504: fpc_cmd_receive_cb current ssm request: 104 state: 0 364s (process:1886): libfprint-DEBUG: 00:53:33.504: Enrol Update status: 1, remaining: 11 364s (process:1886): libfprint-device-DEBUG: 00:53:33.504: Device reported enroll progress, reported 1 of 25 have been completed 364s (process:1886): libfprint-SSM-DEBUG: 00:53:33.504: [fpcmoc] enroll entering state 2 364s (process:1886): libfprint-SSM-DEBUG: 00:53:33.504: [fpcmoc] FP_CMD_NUM_STATES entering state 0 364s (process:1886): libfprint-DEBUG: 00:53:33.504: fpc_send_ctrl_cmd CMD: 0x2, value: 0x1, index: 0 type: 2 364s (process:1886): libfprint-SSM-DEBUG: 00:53:33.505: [fpcmoc] FP_CMD_NUM_STATES completed successfully 364s (process:1886): libfprint-DEBUG: 00:53:33.505: fpc_cmd_receive_cb current ssm request: 2 state: 0 364s (process:1886): libfprint-SSM-DEBUG: 00:53:33.505: [fpcmoc] FP_CMD_NUM_STATES entering state 1 364s (process:1886): libfprint-DEBUG: 00:53:33.505: fpc_cmd_receive_cb current ssm request: 2 state: 1 364s (process:1886): libfprint-DEBUG: 00:53:33.506: fpc_cmd_receive_cb recv evt data length: 12 364s (process:1886): libfprint-DEBUG: 00:53:33.506: fpc_evt_cb Got finger down event (0) 364s (process:1886): libfprint-device-DEBUG: 00:53:33.506: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 364s (process:1886): libfprint-SSM-DEBUG: 00:53:33.506: [fpcmoc] enroll entering state 3 364s (process:1886): libfprint-SSM-DEBUG: 00:53:33.506: [fpcmoc] FP_CMD_NUM_STATES entering state 0 364s (process:1886): libfprint-DEBUG: 00:53:33.506: fpc_send_ctrl_cmd CMD: 0x9, value: 0x0, index: 0 type: 2 364s (process:1886): libfprint-SSM-DEBUG: 00:53:33.506: [fpcmoc] FP_CMD_NUM_STATES completed successfully 364s (process:1886): libfprint-DEBUG: 00:53:33.506: fpc_cmd_receive_cb current ssm request: 9 state: 0 364s (process:1886): libfprint-SSM-DEBUG: 00:53:33.506: [fpcmoc] FP_CMD_NUM_STATES entering state 1 364s (process:1886): libfprint-DEBUG: 00:53:33.506: fpc_cmd_receive_cb current ssm request: 9 state: 1 364s (process:1886): libfprint-DEBUG: 00:53:33.506: fpc_cmd_receive_cb recv evt data length: 24 364s (process:1886): libfprint-DEBUG: 00:53:33.506: fpc_evt_cb Got capture event 364s (process:1886): libfprint-device-DEBUG: 00:53:33.506: Device reported finger status change: FP_FINGER_STATUS_NEEDED 364s (process:1886): libfprint-SSM-DEBUG: 00:53:33.506: [fpcmoc] enroll entering state 4 364s (process:1886): libfprint-SSM-DEBUG: 00:53:33.506: [fpcmoc] FP_CMD_NUM_STATES entering state 0 364s (process:1886): libfprint-DEBUG: 00:53:33.506: fpc_send_ctrl_cmd CMD: 0x68, value: 0x0, index: 0 type: 3 364s (process:1886): libfprint-SSM-DEBUG: 00:53:33.507: [fpcmoc] FP_CMD_NUM_STATES completed successfully 364s (process:1886): libfprint-DEBUG: 00:53:33.507: fpc_cmd_receive_cb current ssm request: 104 state: 0 364s (process:1886): libfprint-DEBUG: 00:53:33.507: Enrol Update status: 1, remaining: 10 364s (process:1886): libfprint-device-DEBUG: 00:53:33.507: Device reported enroll progress, reported 2 of 25 have been completed 364s (process:1886): libfprint-SSM-DEBUG: 00:53:33.507: [fpcmoc] enroll entering state 2 364s (process:1886): libfprint-SSM-DEBUG: 00:53:33.507: [fpcmoc] FP_CMD_NUM_STATES entering state 0 364s (process:1886): libfprint-DEBUG: 00:53:33.507: fpc_send_ctrl_cmd CMD: 0x2, value: 0x1, index: 0 type: 2 364s (process:1886): libfprint-SSM-DEBUG: 00:53:33.507: [fpcmoc] FP_CMD_NUM_STATES completed successfully 364s (process:1886): libfprint-DEBUG: 00:53:33.507: fpc_cmd_receive_cb current ssm request: 2 state: 0 364s (process:1886): libfprint-SSM-DEBUG: 00:53:33.507: [fpcmoc] FP_CMD_NUM_STATES entering state 1 364s (process:1886): libfprint-DEBUG: 00:53:33.508: fpc_cmd_receive_cb current ssm request: 2 state: 1 364s (process:1886): libfprint-DEBUG: 00:53:33.508: fpc_cmd_receive_cb recv evt data length: 12 364s (process:1886): libfprint-DEBUG: 00:53:33.508: fpc_evt_cb Got finger down event (0) 364s (process:1886): libfprint-device-DEBUG: 00:53:33.508: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 364s (process:1886): libfprint-SSM-DEBUG: 00:53:33.508: [fpcmoc] enroll entering state 3 364s (process:1886): libfprint-SSM-DEBUG: 00:53:33.508: [fpcmoc] FP_CMD_NUM_STATES entering state 0 364s (process:1886): libfprint-DEBUG: 00:53:33.508: fpc_send_ctrl_cmd CMD: 0x9, value: 0x0, index: 0 type: 2 364s (process:1886): libfprint-SSM-DEBUG: 00:53:33.508: [fpcmoc] FP_CMD_NUM_STATES completed successfully 364s (process:1886): libfprint-DEBUG: 00:53:33.508: fpc_cmd_receive_cb current ssm request: 9 state: 0 364s (process:1886): libfprint-SSM-DEBUG: 00:53:33.508: [fpcmoc] FP_CMD_NUM_STATES entering state 1 364s (process:1886): libfprint-DEBUG: 00:53:33.509: fpc_cmd_receive_cb current ssm request: 9 state: 1 364s (process:1886): libfprint-DEBUG: 00:53:33.509: fpc_cmd_receive_cb recv evt data length: 24 364s (process:1886): libfprint-DEBUG: 00:53:33.509: fpc_evt_cb Got capture event 364s (process:1886): libfprint-device-DEBUG: 00:53:33.509: Device reported finger status change: FP_FINGER_STATUS_NEEDED 364s (process:1886): libfprint-SSM-DEBUG: 00:53:33.509: [fpcmoc] enroll entering state 4 364s (process:1886): libfprint-SSM-DEBUG: 00:53:33.509: [fpcmoc] FP_CMD_NUM_STATES entering state 0 364s (process:1886): libfprint-DEBUG: 00:53:33.509: fpc_send_ctrl_cmd CMD: 0x68, value: 0x0, index: 0 type: 3 364s (process:1886): libfprint-SSM-DEBUG: 00:53:33.509: [fpcmoc] FP_CMD_NUM_STATES completed successfully 364s (process:1886): libfprint-DEBUG: 00:53:33.510: fpc_cmd_receive_cb current ssm request: 104 state: 0 364s (process:1886): libfprint-DEBUG: 00:53:33.510: Enrol Update status: 1, remaining: 9 364s (process:1886): libfprint-device-DEBUG: 00:53:33.510: Device reported enroll progress, reported 3 of 25 have been completed 364s (process:1886): libfprint-SSM-DEBUG: 00:53:33.510: [fpcmoc] enroll entering state 2 364s (process:1886): libfprint-SSM-DEBUG: 00:53:33.510: [fpcmoc] FP_CMD_NUM_STATES entering state 0 364s (process:1886): libfprint-DEBUG: 00:53:33.510: fpc_send_ctrl_cmd CMD: 0x2, value: 0x1, index: 0 type: 2 364s (process:1886): libfprint-SSM-DEBUG: 00:53:33.510: [fpcmoc] FP_CMD_NUM_STATES completed successfully 364s (process:1886): libfprint-DEBUG: 00:53:33.510: fpc_cmd_receive_cb current ssm request: 2 state: 0 364s (process:1886): libfprint-SSM-DEBUG: 00:53:33.510: [fpcmoc] FP_CMD_NUM_STATES entering state 1 364s (process:1886): libfprint-DEBUG: 00:53:33.511: fpc_cmd_receive_cb current ssm request: 2 state: 1 364s (process:1886): libfprint-DEBUG: 00:53:33.511: fpc_cmd_receive_cb recv evt data length: 12 364s (process:1886): libfprint-DEBUG: 00:53:33.511: fpc_evt_cb Got finger down event (0) 364s (process:1886): libfprint-device-DEBUG: 00:53:33.511: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 364s (process:1886): libfprint-SSM-DEBUG: 00:53:33.511: [fpcmoc] enroll entering state 3 364s (process:1886): libfprint-SSM-DEBUG: 00:53:33.511: [fpcmoc] FP_CMD_NUM_STATES entering state 0 364s (process:1886): libfprint-DEBUG: 00:53:33.511: fpc_send_ctrl_cmd CMD: 0x9, value: 0x0, index: 0 type: 2 364s (process:1886): libfprint-SSM-DEBUG: 00:53:33.511: [fpcmoc] FP_CMD_NUM_STATES completed successfully 364s (process:1886): libfprint-DEBUG: 00:53:33.511: fpc_cmd_receive_cb current ssm request: 9 state: 0 364s (process:1886): libfprint-SSM-DEBUG: 00:53:33.511: [fpcmoc] FP_CMD_NUM_STATES entering state 1 364s (process:1886): libfprint-DEBUG: 00:53:33.512: fpc_cmd_receive_cb current ssm request: 9 state: 1 364s (process:1886): libfprint-DEBUG: 00:53:33.512: fpc_cmd_receive_cb recv evt data length: 24 364s (process:1886): libfprint-DEBUG: 00:53:33.512: fpc_evt_cb Got capture event 364s (process:1886): libfprint-device-DEBUG: 00:53:33.512: Device reported finger status change: FP_FINGER_STATUS_NEEDED 364s (process:1886): libfprint-SSM-DEBUG: 00:53:33.512: [fpcmoc] enroll entering state 4 364s (process:1886): libfprint-SSM-DEBUG: 00:53:33.512: [fpcmoc] FP_CMD_NUM_STATES entering state 0 364s (process:1886): libfprint-DEBUG: 00:53:33.512: fpc_send_ctrl_cmd CMD: 0x68, value: 0x0, index: 0 type: 3 364s (process:1886): libfprint-SSM-DEBUG: 00:53:33.512: [fpcmoc] FP_CMD_NUM_STATES completed successfully 364s (process:1886): libfprint-DEBUG: 00:53:33.512: fpc_cmd_receive_cb current ssm request: 104 state: 0 364s (process:1886): libfprint-DEBUG: 00:53:33.512: Enrol Update status: 1, remaining: 8 364s (process:1886): libfprint-device-DEBUG: 00:53:33.512: Device reported enroll progress, reported 4 of 25 have been completed 364s (process:1886): libfprint-SSM-DEBUG: 00:53:33.512: [fpcmoc] enroll entering state 2 364s (process:1886): libfprint-SSM-DEBUG: 00:53:33.512: [fpcmoc] FP_CMD_NUM_STATES entering state 0 364s (process:1886): libfprint-DEBUG: 00:53:33.512: fpc_send_ctrl_cmd CMD: 0x2, value: 0x1, index: 0 type: 2 364s (process:1886): libfprint-SSM-DEBUG: 00:53:33.513: [fpcmoc] FP_CMD_NUM_STATES completed successfully 364s (process:1886): libfprint-DEBUG: 00:53:33.513: fpc_cmd_receive_cb current ssm request: 2 state: 0 364s (process:1886): libfprint-SSM-DEBUG: 00:53:33.513: [fpcmoc] FP_CMD_NUM_STATES entering state 1 364s (process:1886): libfprint-DEBUG: 00:53:33.513: fpc_cmd_receive_cb current ssm request: 2 state: 1 364s (process:1886): libfprint-DEBUG: 00:53:33.513: fpc_cmd_receive_cb recv evt data length: 12 364s (process:1886): libfprint-DEBUG: 00:53:33.513: fpc_evt_cb Got finger down event (0) 364s (process:1886): libfprint-device-DEBUG: 00:53:33.513: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 364s (process:1886): libfprint-SSM-DEBUG: 00:53:33.513: [fpcmoc] enroll entering state 3 364s (process:1886): libfprint-SSM-DEBUG: 00:53:33.513: [fpcmoc] FP_CMD_NUM_STATES entering state 0 364s (process:1886): libfprint-DEBUG: 00:53:33.513: fpc_send_ctrl_cmd CMD: 0x9, value: 0x0, index: 0 type: 2 364s (process:1886): libfprint-SSM-DEBUG: 00:53:33.514: [fpcmoc] FP_CMD_NUM_STATES completed successfully 364s (process:1886): libfprint-DEBUG: 00:53:33.514: fpc_cmd_receive_cb current ssm request: 9 state: 0 364s (process:1886): libfprint-SSM-DEBUG: 00:53:33.514: [fpcmoc] FP_CMD_NUM_STATES entering state 1 364s (process:1886): libfprint-DEBUG: 00:53:33.514: fpc_cmd_receive_cb current ssm request: 9 state: 1 364s (process:1886): libfprint-DEBUG: 00:53:33.514: fpc_cmd_receive_cb recv evt data length: 24 364s (process:1886): libfprint-DEBUG: 00:53:33.514: fpc_evt_cb Got capture event 364s (process:1886): libfprint-device-DEBUG: 00:53:33.514: Device reported finger status change: FP_FINGER_STATUS_NEEDED 364s (process:1886): libfprint-SSM-DEBUG: 00:53:33.514: [fpcmoc] enroll entering state 4 364s (process:1886): libfprint-SSM-DEBUG: 00:53:33.514: [fpcmoc] FP_CMD_NUM_STATES entering state 0 364s (process:1886): libfprint-DEBUG: 00:53:33.514: fpc_send_ctrl_cmd CMD: 0x68, value: 0x0, index: 0 type: 3 364s (process:1886): libfprint-SSM-DEBUG: 00:53:33.515: [fpcmoc] FP_CMD_NUM_STATES completed successfully 364s (process:1886): libfprint-DEBUG: 00:53:33.515: fpc_cmd_receive_cb current ssm request: 104 state: 0 364s (process:1886): libfprint-DEBUG: 00:53:33.515: Enrol Update status: 1, remaining: 7 364s (process:1886): libfprint-device-DEBUG: 00:53:33.515: Device reported enroll progress, reported 5 of 25 have been completed 364s (process:1886): libfprint-SSM-DEBUG: 00:53:33.515: [fpcmoc] enroll entering state 2 364s (process:1886): libfprint-SSM-DEBUG: 00:53:33.515: [fpcmoc] FP_CMD_NUM_STATES entering state 0 364s (process:1886): libfprint-DEBUG: 00:53:33.515: fpc_send_ctrl_cmd CMD: 0x2, value: 0x1, index: 0 type: 2 364s (process:1886): libfprint-SSM-DEBUG: 00:53:33.515: [fpcmoc] FP_CMD_NUM_STATES completed successfully 364s (process:1886): libfprint-DEBUG: 00:53:33.515: fpc_cmd_receive_cb current ssm request: 2 state: 0 364s (process:1886): libfprint-SSM-DEBUG: 00:53:33.515: [fpcmoc] FP_CMD_NUM_STATES entering state 1 364s (process:1886): libfprint-DEBUG: 00:53:33.516: fpc_cmd_receive_cb current ssm request: 2 state: 1 364s (process:1886): libfprint-DEBUG: 00:53:33.516: fpc_cmd_receive_cb recv evt data length: 12 364s (process:1886): libfprint-DEBUG: 00:53:33.516: fpc_evt_cb Got finger down event (0) 364s (process:1886): libfprint-device-DEBUG: 00:53:33.516: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 364s (process:1886): libfprint-SSM-DEBUG: 00:53:33.516: [fpcmoc] enroll entering state 3 364s (process:1886): libfprint-SSM-DEBUG: 00:53:33.516: [fpcmoc] FP_CMD_NUM_STATES entering state 0 364s (process:1886): libfprint-DEBUG: 00:53:33.516: fpc_send_ctrl_cmd CMD: 0x9, value: 0x0, index: 0 type: 2 364s (process:1886): libfprint-SSM-DEBUG: 00:53:33.516: [fpcmoc] FP_CMD_NUM_STATES completed successfully 364s (process:1886): libfprint-DEBUG: 00:53:33.516: fpc_cmd_receive_cb current ssm request: 9 state: 0 364s (process:1886): libfprint-SSM-DEBUG: 00:53:33.516: [fpcmoc] FP_CMD_NUM_STATES entering state 1 364s (process:1886): libfprint-DEBUG: 00:53:33.517: fpc_cmd_receive_cb current ssm request: 9 state: 1 364s (process:1886): libfprint-DEBUG: 00:53:33.517: fpc_cmd_receive_cb recv evt data length: 24 364s (process:1886): libfprint-DEBUG: 00:53:33.517: fpc_evt_cb Got capture event 364s (process:1886): libfprint-device-DEBUG: 00:53:33.517: Device reported finger status change: FP_FINGER_STATUS_NEEDED 364s (process:1886): libfprint-SSM-DEBUG: 00:53:33.517: [fpcmoc] enroll entering state 4 364s (process:1886): libfprint-SSM-DEBUG: 00:53:33.517: [fpcmoc] FP_CMD_NUM_STATES entering state 0 364s (process:1886): libfprint-DEBUG: 00:53:33.517: fpc_send_ctrl_cmd CMD: 0x68, value: 0x0, index: 0 type: 3 364s (process:1886): libfprint-SSM-DEBUG: 00:53:33.517: [fpcmoc] FP_CMD_NUM_STATES completed successfully 364s (process:1886): libfprint-DEBUG: 00:53:33.517: fpc_cmd_receive_cb current ssm request: 104 state: 0 364s (process:1886): libfprint-DEBUG: 00:53:33.517: Enrol Update status: 5, remaining: 7 364s (process:1886): libfprint-DEBUG: 00:53:33.517: Sample overlapping ratio is too High 364s (process:1886): libfprint-device-DEBUG: 00:53:33.517: Device reported enroll progress, reported 5 of 25 have been completed 364s (process:1886): libfprint-SSM-DEBUG: 00:53:33.517: [fpcmoc] enroll entering state 2 364s (process:1886): libfprint-SSM-DEBUG: 00:53:33.517: [fpcmoc] FP_CMD_NUM_STATES entering state 0 364s (process:1886): libfprint-DEBUG: 00:53:33.517: fpc_send_ctrl_cmd CMD: 0x2, value: 0x1, index: 0 type: 2 364s (process:1886): libfprint-SSM-DEBUG: 00:53:33.518: [fpcmoc] FP_CMD_NUM_STATES completed successfully 364s (process:1886): libfprint-DEBUG: 00:53:33.518: fpc_cmd_receive_cb current ssm request: 2 state: 0 364s (process:1886): libfprint-SSM-DEBUG: 00:53:33.518: [fpcmoc] FP_CMD_NUM_STATES entering state 1 364s (process:1886): libfprint-DEBUG: 00:53:33.518: fpc_cmd_receive_cb current ssm request: 2 state: 1 364s (process:1886): libfprint-DEBUG: 00:53:33.518: fpc_cmd_receive_cb recv evt data length: 12 364s (process:1886): libfprint-DEBUG: 00:53:33.518: fpc_evt_cb Got finger down event (0) 364s (process:1886): libfprint-device-DEBUG: 00:53:33.518: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 364s (process:1886): libfprint-SSM-DEBUG: 00:53:33.518: [fpcmoc] enroll entering state 3 364s (process:1886): libfprint-SSM-DEBUG: 00:53:33.518: [fpcmoc] FP_CMD_NUM_STATES entering state 0 364s (process:1886): libfprint-DEBUG: 00:53:33.518: fpc_send_ctrl_cmd CMD: 0x9, value: 0x0, index: 0 type: 2 364s (process:1886): libfprint-SSM-DEBUG: 00:53:33.519: [fpcmoc] FP_CMD_NUM_STATES completed successfully 364s (process:1886): libfprint-DEBUG: 00:53:33.519: fpc_cmd_receive_cb current ssm request: 9 state: 0 364s (process:1886): libfprint-SSM-DEBUG: 00:53:33.519: [fpcmoc] FP_CMD_NUM_STATES entering state 1 364s (process:1886): libfprint-DEBUG: 00:53:33.519: fpc_cmd_receive_cb current ssm request: 9 state: 1 364s (process:1886): libfprint-DEBUG: 00:53:33.519: fpc_cmd_receive_cb recv evt data length: 24 364s (process:1886): libfprint-DEBUG: 00:53:33.519: fpc_evt_cb Got capture event 364s (process:1886): libfprint-device-DEBUG: 00:53:33.519: Device reported finger status change: FP_FINGER_STATUS_NEEDED 364s (process:1886): libfprint-SSM-DEBUG: 00:53:33.519: [fpcmoc] enroll entering state 4 364s (process:1886): libfprint-SSM-DEBUG: 00:53:33.519: [fpcmoc] FP_CMD_NUM_STATES entering state 0 364s (process:1886): libfprint-DEBUG: 00:53:33.519: fpc_send_ctrl_cmd CMD: 0x68, value: 0x0, index: 0 type: 3 364s (process:1886): libfprint-SSM-DEBUG: 00:53:33.520: [fpcmoc] FP_CMD_NUM_STATES completed successfully 364s (process:1886): libfprint-DEBUG: 00:53:33.520: fpc_cmd_receive_cb current ssm request: 104 state: 0 364s (process:1886): libfprint-DEBUG: 00:53:33.520: Enrol Update status: 1, remaining: 6 364s (process:1886): libfprint-device-DEBUG: 00:53:33.520: Device reported enroll progress, reported 6 of 25 have been completed 364s (process:1886): libfprint-SSM-DEBUG: 00:53:33.520: [fpcmoc] enroll entering state 2 364s (process:1886): libfprint-SSM-DEBUG: 00:53:33.520: [fpcmoc] FP_CMD_NUM_STATES entering state 0 364s (process:1886): libfprint-DEBUG: 00:53:33.520: fpc_send_ctrl_cmd CMD: 0x2, value: 0x1, index: 0 type: 2 364s (process:1886): libfprint-SSM-DEBUG: 00:53:33.520: [fpcmoc] FP_CMD_NUM_STATES completed successfully 364s (process:1886): libfprint-DEBUG: 00:53:33.520: fpc_cmd_receive_cb current ssm request: 2 state: 0 364s (process:1886): libfprint-SSM-DEBUG: 00:53:33.520: [fpcmoc] FP_CMD_NUM_STATES entering state 1 364s (process:1886): libfprint-DEBUG: 00:53:33.521: fpc_cmd_receive_cb current ssm request: 2 state: 1 364s (process:1886): libfprint-DEBUG: 00:53:33.521: fpc_cmd_receive_cb recv evt data length: 12 364s (process:1886): libfprint-DEBUG: 00:53:33.521: fpc_evt_cb Got finger down event (0) 364s (process:1886): libfprint-device-DEBUG: 00:53:33.521: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 364s (process:1886): libfprint-SSM-DEBUG: 00:53:33.521: [fpcmoc] enroll entering state 3 364s (process:1886): libfprint-SSM-DEBUG: 00:53:33.521: [fpcmoc] FP_CMD_NUM_STATES entering state 0 364s (process:1886): libfprint-DEBUG: 00:53:33.521: fpc_send_ctrl_cmd CMD: 0x9, value: 0x0, index: 0 type: 2 364s (process:1886): libfprint-SSM-DEBUG: 00:53:33.521: [fpcmoc] FP_CMD_NUM_STATES completed successfully 364s (process:1886): libfprint-DEBUG: 00:53:33.521: fpc_cmd_receive_cb current ssm request: 9 state: 0 364s (process:1886): libfprint-SSM-DEBUG: 00:53:33.521: [fpcmoc] FP_CMD_NUM_STATES entering state 1 364s (process:1886): libfprint-DEBUG: 00:53:33.522: fpc_cmd_receive_cb current ssm request: 9 state: 1 364s (process:1886): libfprint-DEBUG: 00:53:33.522: fpc_cmd_receive_cb recv evt data length: 24 364s (process:1886): libfprint-DEBUG: 00:53:33.522: fpc_evt_cb Got capture event 364s (process:1886): libfprint-device-DEBUG: 00:53:33.522: Device reported finger status change: FP_FINGER_STATUS_NEEDED 364s (process:1886): libfprint-SSM-DEBUG: 00:53:33.522: [fpcmoc] enroll entering state 4 364s (process:1886): libfprint-SSM-DEBUG: 00:53:33.522: [fpcmoc] FP_CMD_NUM_STATES entering state 0 364s (process:1886): libfprint-DEBUG: 00:53:33.522: fpc_send_ctrl_cmd CMD: 0x68, value: 0x0, index: 0 type: 3 364s (process:1886): libfprint-SSM-DEBUG: 00:53:33.522: [fpcmoc] FP_CMD_NUM_STATES completed successfully 364s (process:1886): libfprint-DEBUG: 00:53:33.523: fpc_cmd_receive_cb current ssm request: 104 state: 0 364s (process:1886): libfprint-DEBUG: 00:53:33.523: Enrol Update status: 1, remaining: 5 364s (process:1886): libfprint-device-DEBUG: 00:53:33.523: Device reported enroll progress, reported 7 of 25 have been completed 364s (process:1886): libfprint-SSM-DEBUG: 00:53:33.523: [fpcmoc] enroll entering state 2 364s (process:1886): libfprint-SSM-DEBUG: 00:53:33.523: [fpcmoc] FP_CMD_NUM_STATES entering state 0 364s (process:1886): libfprint-DEBUG: 00:53:33.523: fpc_send_ctrl_cmd CMD: 0x2, value: 0x1, index: 0 type: 2 364s (process:1886): libfprint-SSM-DEBUG: 00:53:33.523: [fpcmoc] FP_CMD_NUM_STATES completed successfully 364s (process:1886): libfprint-DEBUG: 00:53:33.523: fpc_cmd_receive_cb current ssm request: 2 state: 0 364s (process:1886): libfprint-SSM-DEBUG: 00:53:33.523: [fpcmoc] FP_CMD_NUM_STATES entering state 1 364s (process:1886): libfprint-DEBUG: 00:53:33.524: fpc_cmd_receive_cb current ssm request: 2 state: 1 364s (process:1886): libfprint-DEBUG: 00:53:33.524: fpc_cmd_receive_cb recv evt data length: 12 364s (process:1886): libfprint-DEBUG: 00:53:33.524: fpc_evt_cb Got finger down event (0) 364s (process:1886): libfprint-device-DEBUG: 00:53:33.524: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 364s (process:1886): libfprint-SSM-DEBUG: 00:53:33.524: [fpcmoc] enroll entering state 3 364s (process:1886): libfprint-SSM-DEBUG: 00:53:33.524: [fpcmoc] FP_CMD_NUM_STATES entering state 0 364s (process:1886): libfprint-DEBUG: 00:53:33.524: fpc_send_ctrl_cmd CMD: 0x9, value: 0x0, index: 0 type: 2 364s (process:1886): libfprint-SSM-DEBUG: 00:53:33.524: [fpcmoc] FP_CMD_NUM_STATES completed successfully 364s (process:1886): libfprint-DEBUG: 00:53:33.524: fpc_cmd_receive_cb current ssm request: 9 state: 0 364s (process:1886): libfprint-SSM-DEBUG: 00:53:33.524: [fpcmoc] FP_CMD_NUM_STATES entering state 1 364s (process:1886): libfprint-DEBUG: 00:53:33.525: fpc_cmd_receive_cb current ssm request: 9 state: 1 364s (process:1886): libfprint-DEBUG: 00:53:33.525: fpc_cmd_receive_cb recv evt data length: 24 364s (process:1886): libfprint-DEBUG: 00:53:33.525: fpc_evt_cb Got capture event 364s (process:1886): libfprint-device-DEBUG: 00:53:33.525: Device reported finger status change: FP_FINGER_STATUS_NEEDED 364s (process:1886): libfprint-SSM-DEBUG: 00:53:33.525: [fpcmoc] enroll entering state 4 364s (process:1886): libfprint-SSM-DEBUG: 00:53:33.525: [fpcmoc] FP_CMD_NUM_STATES entering state 0 364s (process:1886): libfprint-DEBUG: 00:53:33.525: fpc_send_ctrl_cmd CMD: 0x68, value: 0x0, index: 0 type: 3 364s (process:1886): libfprint-SSM-DEBUG: 00:53:33.525: [fpcmoc] FP_CMD_NUM_STATES completed successfully 364s (process:1886): libfprint-DEBUG: 00:53:33.525: fpc_cmd_receive_cb current ssm request: 104 state: 0 364s (process:1886): libfprint-DEBUG: 00:53:33.525: Enrol Update status: 5, remaining: 5 364s (process:1886): libfprint-DEBUG: 00:53:33.525: Sample overlapping ratio is too High 364s (process:1886): libfprint-device-DEBUG: 00:53:33.525: Device reported enroll progress, reported 7 of 25 have been completed 364s (process:1886): libfprint-SSM-DEBUG: 00:53:33.525: [fpcmoc] enroll entering state 2 364s (process:1886): libfprint-SSM-DEBUG: 00:53:33.525: [fpcmoc] FP_CMD_NUM_STATES entering state 0 364s (process:1886): libfprint-DEBUG: 00:53:33.525: fpc_send_ctrl_cmd CMD: 0x2, value: 0x1, index: 0 type: 2 364s (process:1886): libfprint-SSM-DEBUG: 00:53:33.525: [fpcmoc] FP_CMD_NUM_STATES completed successfully 364s (process:1886): libfprint-DEBUG: 00:53:33.526: fpc_cmd_receive_cb current ssm request: 2 state: 0 364s (process:1886): libfprint-SSM-DEBUG: 00:53:33.526: [fpcmoc] FP_CMD_NUM_STATES entering state 1 364s (process:1886): libfprint-DEBUG: 00:53:33.526: fpc_cmd_receive_cb current ssm request: 2 state: 1 364s (process:1886): libfprint-DEBUG: 00:53:33.526: fpc_cmd_receive_cb recv evt data length: 12 364s (process:1886): libfprint-DEBUG: 00:53:33.526: fpc_evt_cb Got finger down event (0) 364s (process:1886): libfprint-device-DEBUG: 00:53:33.526: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 364s (process:1886): libfprint-SSM-DEBUG: 00:53:33.526: [fpcmoc] enroll entering state 3 364s (process:1886): libfprint-SSM-DEBUG: 00:53:33.526: [fpcmoc] FP_CMD_NUM_STATES entering state 0 364s (process:1886): libfprint-DEBUG: 00:53:33.526: fpc_send_ctrl_cmd CMD: 0x9, value: 0x0, index: 0 type: 2 364s (process:1886): libfprint-SSM-DEBUG: 00:53:33.527: [fpcmoc] FP_CMD_NUM_STATES completed successfully 364s (process:1886): libfprint-DEBUG: 00:53:33.527: fpc_cmd_receive_cb current ssm request: 9 state: 0 364s (process:1886): libfprint-SSM-DEBUG: 00:53:33.527: [fpcmoc] FP_CMD_NUM_STATES entering state 1 364s (process:1886): libfprint-DEBUG: 00:53:33.527: fpc_cmd_receive_cb current ssm request: 9 state: 1 364s (process:1886): libfprint-DEBUG: 00:53:33.527: fpc_cmd_receive_cb recv evt data length: 24 364s (process:1886): libfprint-DEBUG: 00:53:33.527: fpc_evt_cb Got capture event 364s (process:1886): libfprint-device-DEBUG: 00:53:33.527: Device reported finger status change: FP_FINGER_STATUS_NEEDED 364s (process:1886): libfprint-SSM-DEBUG: 00:53:33.527: [fpcmoc] enroll entering state 4 364s (process:1886): libfprint-SSM-DEBUG: 00:53:33.527: [fpcmoc] FP_CMD_NUM_STATES entering state 0 364s (process:1886): libfprint-DEBUG: 00:53:33.527: fpc_send_ctrl_cmd CMD: 0x68, value: 0x0, index: 0 type: 3 364s (process:1886): libfprint-SSM-DEBUG: 00:53:33.527: [fpcmoc] FP_CMD_NUM_STATES completed successfully 364s (process:1886): libfprint-DEBUG: 00:53:33.528: fpc_cmd_receive_cb current ssm request: 104 state: 0 364s (process:1886): libfprint-DEBUG: 00:53:33.528: Enrol Update status: 1, remaining: 4 364s (process:1886): libfprint-device-DEBUG: 00:53:33.528: Device reported enroll progress, reported 8 of 25 have been completed 364s (process:1886): libfprint-SSM-DEBUG: 00:53:33.528: [fpcmoc] enroll entering state 2 364s (process:1886): libfprint-SSM-DEBUG: 00:53:33.528: [fpcmoc] FP_CMD_NUM_STATES entering state 0 364s (process:1886): libfprint-DEBUG: 00:53:33.528: fpc_send_ctrl_cmd CMD: 0x2, value: 0x1, index: 0 type: 2 364s (process:1886): libfprint-SSM-DEBUG: 00:53:33.528: [fpcmoc] FP_CMD_NUM_STATES completed successfully 364s (process:1886): libfprint-DEBUG: 00:53:33.528: fpc_cmd_receive_cb current ssm request: 2 state: 0 364s (process:1886): libfprint-SSM-DEBUG: 00:53:33.528: [fpcmoc] FP_CMD_NUM_STATES entering state 1 364s (process:1886): libfprint-DEBUG: 00:53:33.529: fpc_cmd_receive_cb current ssm request: 2 state: 1 364s (process:1886): libfprint-DEBUG: 00:53:33.529: fpc_cmd_receive_cb recv evt data length: 12 364s (process:1886): libfprint-DEBUG: 00:53:33.529: fpc_evt_cb Got finger down event (0) 364s (process:1886): libfprint-device-DEBUG: 00:53:33.529: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 364s (process:1886): libfprint-SSM-DEBUG: 00:53:33.529: [fpcmoc] enroll entering state 3 364s (process:1886): libfprint-SSM-DEBUG: 00:53:33.529: [fpcmoc] FP_CMD_NUM_STATES entering state 0 364s (process:1886): libfprint-DEBUG: 00:53:33.529: fpc_send_ctrl_cmd CMD: 0x9, value: 0x0, index: 0 type: 2 364s (process:1886): libfprint-SSM-DEBUG: 00:53:33.529: [fpcmoc] FP_CMD_NUM_STATES completed successfully 364s (process:1886): libfprint-DEBUG: 00:53:33.529: fpc_cmd_receive_cb current ssm request: 9 state: 0 364s (process:1886): libfprint-SSM-DEBUG: 00:53:33.529: [fpcmoc] FP_CMD_NUM_STATES entering state 1 364s (process:1886): libfprint-DEBUG: 00:53:33.530: fpc_cmd_receive_cb current ssm request: 9 state: 1 364s (process:1886): libfprint-DEBUG: 00:53:33.530: fpc_cmd_receive_cb recv evt data length: 24 364s (process:1886): libfprint-DEBUG: 00:53:33.530: fpc_evt_cb Got capture event 364s (process:1886): libfprint-device-DEBUG: 00:53:33.530: Device reported finger status change: FP_FINGER_STATUS_NEEDED 364s (process:1886): libfprint-SSM-DEBUG: 00:53:33.530: [fpcmoc] enroll entering state 4 364s (process:1886): libfprint-SSM-DEBUG: 00:53:33.530: [fpcmoc] FP_CMD_NUM_STATES entering state 0 364s (process:1886): libfprint-DEBUG: 00:53:33.530: fpc_send_ctrl_cmd CMD: 0x68, value: 0x0, index: 0 type: 3 364s (process:1886): libfprint-SSM-DEBUG: 00:53:33.530: [fpcmoc] FP_CMD_NUM_STATES completed successfully 364s (process:1886): libfprint-DEBUG: 00:53:33.531: fpc_cmd_receive_cb current ssm request: 104 state: 0 364s (process:1886): libfprint-DEBUG: 00:53:33.531: Enrol Update status: 1, remaining: 3 364s (process:1886): libfprint-device-DEBUG: 00:53:33.531: Device reported enroll progress, reported 9 of 25 have been completed 364s (process:1886): libfprint-SSM-DEBUG: 00:53:33.531: [fpcmoc] enroll entering state 2 364s (process:1886): libfprint-SSM-DEBUG: 00:53:33.531: [fpcmoc] FP_CMD_NUM_STATES entering state 0 364s (process:1886): libfprint-DEBUG: 00:53:33.531: fpc_send_ctrl_cmd CMD: 0x2, value: 0x1, index: 0 type: 2 364s (process:1886): libfprint-SSM-DEBUG: 00:53:33.531: [fpcmoc] FP_CMD_NUM_STATES completed successfully 364s (process:1886): libfprint-DEBUG: 00:53:33.531: fpc_cmd_receive_cb current ssm request: 2 state: 0 364s (process:1886): libfprint-SSM-DEBUG: 00:53:33.531: [fpcmoc] FP_CMD_NUM_STATES entering state 1 364s (process:1886): libfprint-DEBUG: 00:53:33.532: fpc_cmd_receive_cb current ssm request: 2 state: 1 364s (process:1886): libfprint-DEBUG: 00:53:33.532: fpc_cmd_receive_cb recv evt data length: 12 364s (process:1886): libfprint-DEBUG: 00:53:33.532: fpc_evt_cb Got finger down event (0) 364s (process:1886): libfprint-device-DEBUG: 00:53:33.532: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 364s (process:1886): libfprint-SSM-DEBUG: 00:53:33.532: [fpcmoc] enroll entering state 3 364s (process:1886): libfprint-SSM-DEBUG: 00:53:33.532: [fpcmoc] FP_CMD_NUM_STATES entering state 0 364s (process:1886): libfprint-DEBUG: 00:53:33.532: fpc_send_ctrl_cmd CMD: 0x9, value: 0x0, index: 0 type: 2 364s (process:1886): libfprint-SSM-DEBUG: 00:53:33.532: [fpcmoc] FP_CMD_NUM_STATES completed successfully 364s (process:1886): libfprint-DEBUG: 00:53:33.532: fpc_cmd_receive_cb current ssm request: 9 state: 0 364s (process:1886): libfprint-SSM-DEBUG: 00:53:33.532: [fpcmoc] FP_CMD_NUM_STATES entering state 1 364s (process:1886): libfprint-DEBUG: 00:53:33.533: fpc_cmd_receive_cb current ssm request: 9 state: 1 364s (process:1886): libfprint-DEBUG: 00:53:33.533: fpc_cmd_receive_cb recv evt data length: 24 364s (process:1886): libfprint-DEBUG: 00:53:33.533: fpc_evt_cb Got capture event 364s (process:1886): libfprint-device-DEBUG: 00:53:33.533: Device reported finger status change: FP_FINGER_STATUS_NEEDED 364s (process:1886): libfprint-SSM-DEBUG: 00:53:33.533: [fpcmoc] enroll entering state 4 364s (process:1886): libfprint-SSM-DEBUG: 00:53:33.533: [fpcmoc] FP_CMD_NUM_STATES entering state 0 364s (process:1886): libfprint-DEBUG: 00:53:33.533: fpc_send_ctrl_cmd CMD: 0x68, value: 0x0, index: 0 type: 3 364s (process:1886): libfprint-SSM-DEBUG: 00:53:33.533: [fpcmoc] FP_CMD_NUM_STATES completed successfully 364s (process:1886): libfprint-DEBUG: 00:53:33.533: fpc_cmd_receive_cb current ssm request: 104 state: 0 364s (process:1886): libfprint-DEBUG: 00:53:33.533: Enrol Update status: 1, remaining: 2 364s (process:1886): libfprint-device-DEBUG: 00:53:33.533: Device reported enroll progress, reported 10 of 25 have been completed 364s (process:1886): libfprint-SSM-DEBUG: 00:53:33.533: [fpcmoc] enroll entering state 2 364s (process:1886): libfprint-SSM-DEBUG: 00:53:33.533: [fpcmoc] FP_CMD_NUM_STATES entering state 0 364s (process:1886): libfprint-DEBUG: 00:53:33.533: fpc_send_ctrl_cmd CMD: 0x2, value: 0x1, index: 0 type: 2 364s (process:1886): libfprint-SSM-DEBUG: 00:53:33.533: [fpcmoc] FP_CMD_NUM_STATES completed successfully 364s (process:1886): libfprint-DEBUG: 00:53:33.534: fpc_cmd_receive_cb current ssm request: 2 state: 0 364s (process:1886): libfprint-SSM-DEBUG: 00:53:33.534: [fpcmoc] FP_CMD_NUM_STATES entering state 1 364s (process:1886): libfprint-DEBUG: 00:53:33.534: fpc_cmd_receive_cb current ssm request: 2 state: 1 364s (process:1886): libfprint-DEBUG: 00:53:33.534: fpc_cmd_receive_cb recv evt data length: 12 364s (process:1886): libfprint-DEBUG: 00:53:33.534: fpc_evt_cb Got finger down event (0) 364s (process:1886): libfprint-device-DEBUG: 00:53:33.534: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 364s (process:1886): libfprint-SSM-DEBUG: 00:53:33.534: [fpcmoc] enroll entering state 3 364s (process:1886): libfprint-SSM-DEBUG: 00:53:33.534: [fpcmoc] FP_CMD_NUM_STATES entering state 0 364s (process:1886): libfprint-DEBUG: 00:53:33.534: fpc_send_ctrl_cmd CMD: 0x9, value: 0x0, index: 0 type: 2 364s (process:1886): libfprint-SSM-DEBUG: 00:53:33.534: [fpcmoc] FP_CMD_NUM_STATES completed successfully 364s (process:1886): libfprint-DEBUG: 00:53:33.535: fpc_cmd_receive_cb current ssm request: 9 state: 0 364s (process:1886): libfprint-SSM-DEBUG: 00:53:33.535: [fpcmoc] FP_CMD_NUM_STATES entering state 1 364s (process:1886): libfprint-DEBUG: 00:53:33.535: fpc_cmd_receive_cb current ssm request: 9 state: 1 364s (process:1886): libfprint-DEBUG: 00:53:33.535: fpc_cmd_receive_cb recv evt data length: 24 364s (process:1886): libfprint-DEBUG: 00:53:33.535: fpc_evt_cb Got capture event 364s (process:1886): libfprint-device-DEBUG: 00:53:33.535: Device reported finger status change: FP_FINGER_STATUS_NEEDED 364s (process:1886): libfprint-SSM-DEBUG: 00:53:33.535: [fpcmoc] enroll entering state 4 364s (process:1886): libfprint-SSM-DEBUG: 00:53:33.535: [fpcmoc] FP_CMD_NUM_STATES entering state 0 364s (process:1886): libfprint-DEBUG: 00:53:33.535: fpc_send_ctrl_cmd CMD: 0x68, value: 0x0, index: 0 type: 3 364s (process:1886): libfprint-SSM-DEBUG: 00:53:33.535: [fpcmoc] FP_CMD_NUM_STATES completed successfully 364s (process:1886): libfprint-DEBUG: 00:53:33.536: fpc_cmd_receive_cb current ssm request: 104 state: 0 364s (process:1886): libfprint-DEBUG: 00:53:33.536: Enrol Update status: 5, remaining: 2 364s (process:1886): libfprint-DEBUG: 00:53:33.536: Sample overlapping ratio is too High 364s (process:1886): libfprint-device-DEBUG: 00:53:33.536: Device reported enroll progress, reported 10 of 25 have been completed 364s (process:1886): libfprint-SSM-DEBUG: 00:53:33.536: [fpcmoc] enroll entering state 2 364s (process:1886): libfprint-SSM-DEBUG: 00:53:33.536: [fpcmoc] FP_CMD_NUM_STATES entering state 0 364s (process:1886): libfprint-DEBUG: 00:53:33.536: fpc_send_ctrl_cmd CMD: 0x2, value: 0x1, index: 0 type: 2 364s (process:1886): libfprint-SSM-DEBUG: 00:53:33.536: [fpcmoc] FP_CMD_NUM_STATES completed successfully 364s (process:1886): libfprint-DEBUG: 00:53:33.536: fpc_cmd_receive_cb current ssm request: 2 state: 0 364s (process:1886): libfprint-SSM-DEBUG: 00:53:33.536: [fpcmoc] FP_CMD_NUM_STATES entering state 1 364s (process:1886): libfprint-DEBUG: 00:53:33.537: fpc_cmd_receive_cb current ssm request: 2 state: 1 364s (process:1886): libfprint-DEBUG: 00:53:33.537: fpc_cmd_receive_cb recv evt data length: 12 364s (process:1886): libfprint-DEBUG: 00:53:33.537: fpc_evt_cb Got finger down event (0) 364s (process:1886): libfprint-device-DEBUG: 00:53:33.537: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 364s (process:1886): libfprint-SSM-DEBUG: 00:53:33.537: [fpcmoc] enroll entering state 3 364s (process:1886): libfprint-SSM-DEBUG: 00:53:33.537: [fpcmoc] FP_CMD_NUM_STATES entering state 0 364s (process:1886): libfprint-DEBUG: 00:53:33.537: fpc_send_ctrl_cmd CMD: 0x9, value: 0x0, index: 0 type: 2 364s (process:1886): libfprint-SSM-DEBUG: 00:53:33.537: [fpcmoc] FP_CMD_NUM_STATES completed successfully 364s (process:1886): libfprint-DEBUG: 00:53:33.537: fpc_cmd_receive_cb current ssm request: 9 state: 0 364s (process:1886): libfprint-SSM-DEBUG: 00:53:33.537: [fpcmoc] FP_CMD_NUM_STATES entering state 1 364s (process:1886): libfprint-DEBUG: 00:53:33.538: fpc_cmd_receive_cb current ssm request: 9 state: 1 364s (process:1886): libfprint-DEBUG: 00:53:33.538: fpc_cmd_receive_cb recv evt data length: 24 364s (process:1886): libfprint-DEBUG: 00:53:33.538: fpc_evt_cb Got capture event 364s (process:1886): libfprint-device-DEBUG: 00:53:33.538: Device reported finger status change: FP_FINGER_STATUS_NEEDED 364s (process:1886): libfprint-SSM-DEBUG: 00:53:33.538: [fpcmoc] enroll entering state 4 364s (process:1886): libfprint-SSM-DEBUG: 00:53:33.538: [fpcmoc] FP_CMD_NUM_STATES entering state 0 364s (process:1886): libfprint-DEBUG: 00:53:33.538: fpc_send_ctrl_cmd CMD: 0x68, value: 0x0, index: 0 type: 3 364s (process:1886): libfprint-SSM-DEBUG: 00:53:33.538: [fpcmoc] FP_CMD_NUM_STATES completed successfully 364s (process:1886): libfprint-DEBUG: 00:53:33.538: fpc_cmd_receive_cb current ssm request: 104 state: 0 364s (process:1886): libfprint-DEBUG: 00:53:33.538: Enrol Update status: 1, remaining: 1 364s (process:1886): libfprint-device-DEBUG: 00:53:33.538: Device reported enroll progress, reported 11 of 25 have been completed 364s (process:1886): libfprint-SSM-DEBUG: 00:53:33.538: [fpcmoc] enroll entering state 2 364s (process:1886): libfprint-SSM-DEBUG: 00:53:33.538: [fpcmoc] FP_CMD_NUM_STATES entering state 0 364s (process:1886): libfprint-DEBUG: 00:53:33.538: fpc_send_ctrl_cmd CMD: 0x2, value: 0x1, index: 0 type: 2 364s (process:1886): libfprint-SSM-DEBUG: 00:53:33.538: [fpcmoc] FP_CMD_NUM_STATES completed successfully 364s (process:1886): libfprint-DEBUG: 00:53:33.539: fpc_cmd_receive_cb current ssm request: 2 state: 0 364s (process:1886): libfprint-SSM-DEBUG: 00:53:33.539: [fpcmoc] FP_CMD_NUM_STATES entering state 1 364s (process:1886): libfprint-DEBUG: 00:53:33.539: fpc_cmd_receive_cb current ssm request: 2 state: 1 364s (process:1886): libfprint-DEBUG: 00:53:33.539: fpc_cmd_receive_cb recv evt data length: 12 364s (process:1886): libfprint-DEBUG: 00:53:33.539: fpc_evt_cb Got finger down event (0) 364s (process:1886): libfprint-device-DEBUG: 00:53:33.539: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 364s (process:1886): libfprint-SSM-DEBUG: 00:53:33.539: [fpcmoc] enroll entering state 3 364s (process:1886): libfprint-SSM-DEBUG: 00:53:33.539: [fpcmoc] FP_CMD_NUM_STATES entering state 0 364s (process:1886): libfprint-DEBUG: 00:53:33.539: fpc_send_ctrl_cmd CMD: 0x9, value: 0x0, index: 0 type: 2 364s (process:1886): libfprint-SSM-DEBUG: 00:53:33.539: [fpcmoc] FP_CMD_NUM_STATES completed successfully 364s (process:1886): libfprint-DEBUG: 00:53:33.540: fpc_cmd_receive_cb current ssm request: 9 state: 0 364s (process:1886): libfprint-SSM-DEBUG: 00:53:33.540: [fpcmoc] FP_CMD_NUM_STATES entering state 1 364s (process:1886): libfprint-DEBUG: 00:53:33.540: fpc_cmd_receive_cb current ssm request: 9 state: 1 364s (process:1886): libfprint-DEBUG: 00:53:33.540: fpc_cmd_receive_cb recv evt data length: 24 364s (process:1886): libfprint-DEBUG: 00:53:33.540: fpc_evt_cb Got capture event 364s (process:1886): libfprint-device-DEBUG: 00:53:33.540: Device reported finger status change: FP_FINGER_STATUS_NEEDED 364s (process:1886): libfprint-SSM-DEBUG: 00:53:33.540: [fpcmoc] enroll entering state 4 364s (process:1886): libfprint-SSM-DEBUG: 00:53:33.540: [fpcmoc] FP_CMD_NUM_STATES entering state 0 364s (process:1886): libfprint-DEBUG: 00:53:33.540: fpc_send_ctrl_cmd CMD: 0x68, value: 0x0, index: 0 type: 3 364s (process:1886): libfprint-SSM-DEBUG: 00:53:33.540: [fpcmoc] FP_CMD_NUM_STATES completed successfully 364s (process:1886): libfprint-DEBUG: 00:53:33.540: fpc_cmd_receive_cb current ssm request: 104 state: 0 364s (process:1886): libfprint-DEBUG: 00:53:33.540: Enrol Update status: 0, remaining: 0 364s (process:1886): libfprint-device-DEBUG: 00:53:33.541: Device reported enroll progress, reported 12 of 25 have been completed 364s (process:1886): libfprint-SSM-DEBUG: 00:53:33.541: [fpcmoc] enroll entering state 5 364s (process:1886): libfprint-SSM-DEBUG: 00:53:33.541: [fpcmoc] FP_CMD_NUM_STATES entering state 0 364s (process:1886): libfprint-DEBUG: 00:53:33.541: fpc_send_ctrl_cmd CMD: 0x69, value: 0x0, index: 0 type: 3 364s (process:1886): libfprint-SSM-DEBUG: 00:53:33.541: [fpcmoc] FP_CMD_NUM_STATES completed successfully 364s (process:1886): libfprint-DEBUG: 00:53:33.541: fpc_cmd_receive_cb current ssm request: 105 state: 0 364s (process:1886): libfprint-DEBUG: 00:53:33.541: Enrol End status: 0, fid: 0x0 364s (process:1886): libfprint-SSM-DEBUG: 00:53:33.541: [fpcmoc] enroll entering state 6 364s (process:1886): libfprint-SSM-DEBUG: 00:53:33.541: [fpcmoc] FP_CMD_NUM_STATES entering state 0 364s (process:1886): libfprint-DEBUG: 00:53:33.541: fpc_send_ctrl_cmd CMD: 0x6b, value: 0x0, index: 0 type: 3 364s (process:1886): libfprint-SSM-DEBUG: 00:53:33.541: [fpcmoc] FP_CMD_NUM_STATES completed successfully 364s (process:1886): libfprint-DEBUG: 00:53:33.541: fpc_cmd_receive_cb current ssm request: 107 state: 0 364s (process:1886): libfprint-SSM-DEBUG: 00:53:33.541: [fpcmoc] enroll entering state 7 364s (process:1886): libfprint-DEBUG: 00:53:33.542: user_id: FP1-00000000-0-00000000-nobody, finger: 0xf5 364s (process:1886): libfprint-SSM-DEBUG: 00:53:33.542: [fpcmoc] FP_CMD_NUM_STATES entering state 0 364s (process:1886): libfprint-DEBUG: 00:53:33.542: fpc_send_ctrl_cmd CMD: 0x6a, value: 0x0, index: 0 type: 1 364s (process:1886): libfprint-SSM-DEBUG: 00:53:33.542: [fpcmoc] FP_CMD_NUM_STATES completed successfully 364s (process:1886): libfprint-DEBUG: 00:53:33.542: fpc_cmd_receive_cb current ssm request: 106 state: 0 364s (process:1886): libfprint-SSM-DEBUG: 00:53:33.542: [fpcmoc] enroll entering state 8 364s (process:1886): libfprint-SSM-DEBUG: 00:53:33.542: [fpcmoc] FP_CMD_NUM_STATES entering state 0 364s (process:1886): libfprint-DEBUG: 00:53:33.542: fpc_send_ctrl_cmd CMD: 0x61, value: 0x0, index: 0 type: 3 364s (process:1886): libfprint-SSM-DEBUG: 00:53:33.542: [fpcmoc] FP_CMD_NUM_STATES completed successfully 364s (process:1886): libfprint-DEBUG: 00:53:33.542: fpc_cmd_receive_cb current ssm request: 97 state: 0 364s (process:1886): libfprint-SSM-DEBUG: 00:53:33.542: [fpcmoc] enroll entering state 9 364s (process:1886): libfprint-SSM-DEBUG: 00:53:33.542: [fpcmoc] FP_CMD_NUM_STATES entering state 0 364s (process:1886): libfprint-DEBUG: 00:53:33.542: fpc_send_ctrl_cmd CMD: 0x3, value: 0x1, index: 0 type: 1 364s (process:1886): libfprint-SSM-DEBUG: 00:53:33.543: [fpcmoc] FP_CMD_NUM_STATES completed successfully 364s (process:1886): libfprint-DEBUG: 00:53:33.543: fpc_cmd_receive_cb current ssm request: 3 state: 0 364s (process:1886): libfprint-DEBUG: 00:53:33.543: fpc_do_abort_cb Do abort for reasons 364s (process:1886): libfprint-SSM-DEBUG: 00:53:33.543: [fpcmoc] enroll entering state 10 364s (process:1886): libfprint-SSM-DEBUG: 00:53:33.543: [fpcmoc] enroll completed successfully 364s (process:1886): libfprint-DEBUG: 00:53:33.543: Enrollment complete! 364s (process:1886): libfprint-device-DEBUG: 00:53:33.543: Device reported enroll completion 364s (process:1886): libfprint-device-DEBUG: 00:53:33.543: Device reported finger status change: FP_FINGER_STATUS_NONE 364s (process:1886): libfprint-device-DEBUG: 00:53:33.543: Print for finger FP_FINGER_UNKNOWN enrolled 364s (process:1886): libfprint-SSM-DEBUG: 00:53:33.543: [fpcmoc] FP_CMD_NUM_STATES completed successfully 364s (process:1886): libfprint-device-DEBUG: 00:53:33.543: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 364s (process:1886): libfprint-device-DEBUG: 00:53:33.543: Not updating temperature model, device can run continuously! 364s (process:1886): libfprint-DEBUG: 00:53:33.543: fpc_dev_template_list enter --> 364s (process:1886): libfprint-SSM-DEBUG: 00:53:33.543: [fpcmoc] FP_CMD_NUM_STATES entering state 0 364s (process:1886): libfprint-DEBUG: 00:53:33.543: fpc_send_ctrl_cmd CMD: 0x70, value: 0x0, index: 0 type: 2 364s (process:1886): libfprint-DEBUG: 00:53:33.543: fpc_cmd_receive_cb current ssm request: 112 state: 0 364s (process:1886): libfprint-SSM-DEBUG: 00:53:33.543: [fpcmoc] FP_CMD_NUM_STATES entering state 1 364s (process:1886): libfprint-DEBUG: 00:53:33.544: fpc_cmd_receive_cb current ssm request: 112 state: 1 364s (process:1886): libfprint-DEBUG: 00:53:33.544: fpc_cmd_receive_cb recv evt data length: 790 364s (process:1886): libfprint-DEBUG: 00:53:33.544: Query templates complete! 364s (process:1886): libfprint-device-DEBUG: 00:53:33.544: Device reported listing completion 364s (process:1886): libfprint-SSM-DEBUG: 00:53:33.544: [fpcmoc] FP_CMD_NUM_STATES completed successfully 364s (process:1886): libfprint-device-DEBUG: 00:53:33.544: Completing action FPI_DEVICE_ACTION_LIST in idle! 364s (process:1886): libfprint-device-DEBUG: 00:53:33.544: Not updating temperature model, device can run continuously! 364s (process:1886): libfprint-device-DEBUG: 00:53:33.544: Not updating temperature model, device can run continuously! 364s (process:1886): libfprint-DEBUG: 00:53:33.544: fpc_dev_verify_identify enter --> 364s (process:1886): libfprint-SSM-DEBUG: 00:53:33.544: [fpcmoc] verify_identify entering state 0 364s (process:1886): libfprint-device-DEBUG: 00:53:33.544: Device reported finger status change: FP_FINGER_STATUS_NEEDED 364s (process:1886): libfprint-SSM-DEBUG: 00:53:33.544: [fpcmoc] FP_CMD_NUM_STATES entering state 0 364s (process:1886): libfprint-DEBUG: 00:53:33.544: fpc_send_ctrl_cmd CMD: 0x2, value: 0x1, index: 0 type: 2 364s (process:1886): libfprint-DEBUG: 00:53:33.545: fpc_cmd_receive_cb current ssm request: 2 state: 0 364s (process:1886): libfprint-SSM-DEBUG: 00:53:33.545: [fpcmoc] FP_CMD_NUM_STATES entering state 1 364s (process:1886): libfprint-DEBUG: 00:53:33.545: fpc_cmd_receive_cb current ssm request: 2 state: 1 364s (process:1886): libfprint-DEBUG: 00:53:33.545: fpc_cmd_receive_cb recv evt data length: 12 364s (process:1886): libfprint-DEBUG: 00:53:33.545: fpc_evt_cb Got finger down event (0) 364s (process:1886): libfprint-device-DEBUG: 00:53:33.545: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 364s (process:1886): libfprint-SSM-DEBUG: 00:53:33.545: [fpcmoc] verify_identify entering state 1 364s (process:1886): libfprint-SSM-DEBUG: 00:53:33.545: [fpcmoc] FP_CMD_NUM_STATES entering state 0 364s (process:1886): libfprint-DEBUG: 00:53:33.545: fpc_send_ctrl_cmd CMD: 0x9, value: 0x0, index: 0 type: 2 364s (process:1886): libfprint-SSM-DEBUG: 00:53:33.546: [fpcmoc] FP_CMD_NUM_STATES completed successfully 364s (process:1886): libfprint-DEBUG: 00:53:33.546: fpc_cmd_receive_cb current ssm request: 9 state: 0 364s (process:1886): libfprint-SSM-DEBUG: 00:53:33.546: [fpcmoc] FP_CMD_NUM_STATES entering state 1 364s (process:1886): libfprint-DEBUG: 00:53:33.546: fpc_cmd_receive_cb current ssm request: 9 state: 1 364s (process:1886): libfprint-DEBUG: 00:53:33.546: fpc_cmd_receive_cb recv evt data length: 24 364s (process:1886): libfprint-DEBUG: 00:53:33.546: fpc_evt_cb Got capture event 364s (process:1886): libfprint-device-DEBUG: 00:53:33.546: Device reported finger status change: FP_FINGER_STATUS_NEEDED 364s (process:1886): libfprint-SSM-DEBUG: 00:53:33.546: [fpcmoc] verify_identify entering state 2 364s (process:1886): libfprint-SSM-DEBUG: 00:53:33.546: [fpcmoc] FP_CMD_NUM_STATES entering state 0 364s (process:1886): libfprint-DEBUG: 00:53:33.546: fpc_send_ctrl_cmd CMD: 0x6b, value: 0x0, index: 0 type: 3 364s (process:1886): libfprint-SSM-DEBUG: 00:53:33.547: [fpcmoc] FP_CMD_NUM_STATES completed successfully 364s (process:1886): libfprint-DEBUG: 00:53:33.547: fpc_cmd_receive_cb current ssm request: 107 state: 0 364s (process:1886): libfprint-device-DEBUG: 00:53:33.547: Device reported verify result 364s (process:1886): libfprint-SSM-DEBUG: 00:53:33.547: [fpcmoc] verify_identify entering state 3 364s (process:1886): libfprint-SSM-DEBUG: 00:53:33.547: [fpcmoc] FP_CMD_NUM_STATES entering state 0 364s (process:1886): libfprint-DEBUG: 00:53:33.547: fpc_send_ctrl_cmd CMD: 0x3, value: 0x1, index: 0 type: 1 364s (process:1886): libfprint-SSM-DEBUG: 00:53:33.547: [fpcmoc] FP_CMD_NUM_STATES completed successfully 364s (process:1886): libfprint-DEBUG: 00:53:33.547: fpc_cmd_receive_cb current ssm request: 3 state: 0 364s (process:1886): libfprint-DEBUG: 00:53:33.547: fpc_do_abort_cb Do abort for reasons 364s (process:1886): libfprint-SSM-DEBUG: 00:53:33.547: [fpcmoc] verify_identify completed successfully 364s (process:1886): libfprint-DEBUG: 00:53:33.547: Verify_identify complete! 364s (process:1886): libfprint-device-DEBUG: 00:53:33.547: Device reported verify completion 364s (process:1886): libfprint-device-DEBUG: 00:53:33.547: Device reported finger status change: FP_FINGER_STATUS_NONE 364s (process:1886): libfprint-SSM-DEBUG: 00:53:33.547: [fpcmoc] FP_CMD_NUM_STATES completed successfully 364s (process:1886): libfprint-device-DEBUG: 00:53:33.547: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 364s (process:1886): libfprint-device-DEBUG: 00:53:33.547: Not updating temperature model, device can run continuously! 364s (process:1886): libfprint-device-DEBUG: 00:53:33.548: Not updating temperature model, device can run continuously! 364s (process:1886): libfprint-DEBUG: 00:53:33.548: fpc_dev_verify_identify enter --> 364s (process:1886): libfprint-SSM-DEBUG: 00:53:33.548: [fpcmoc] verify_identify entering state 0 364s (process:1886): libfprint-device-DEBUG: 00:53:33.548: Device reported finger status change: FP_FINGER_STATUS_NEEDED 364s (process:1886): libfprint-SSM-DEBUG: 00:53:33.548: [fpcmoc] FP_CMD_NUM_STATES entering state 0 364s (process:1886): libfprint-DEBUG: 00:53:33.548: fpc_send_ctrl_cmd CMD: 0x2, value: 0x1, index: 0 type: 2 364s (process:1886): libfprint-DEBUG: 00:53:33.548: fpc_cmd_receive_cb current ssm request: 2 state: 0 364s (process:1886): libfprint-SSM-DEBUG: 00:53:33.548: [fpcmoc] FP_CMD_NUM_STATES entering state 1 364s (process:1886): libfprint-DEBUG: 00:53:33.549: fpc_cmd_receive_cb current ssm request: 2 state: 1 364s (process:1886): libfprint-DEBUG: 00:53:33.549: fpc_cmd_receive_cb recv evt data length: 12 364s (process:1886): libfprint-DEBUG: 00:53:33.549: fpc_evt_cb Got finger down event (0) 364s (process:1886): libfprint-device-DEBUG: 00:53:33.549: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 364s (process:1886): libfprint-SSM-DEBUG: 00:53:33.549: [fpcmoc] verify_identify entering state 1 364s (process:1886): libfprint-SSM-DEBUG: 00:53:33.549: [fpcmoc] FP_CMD_NUM_STATES entering state 0 364s (process:1886): libfprint-DEBUG: 00:53:33.549: fpc_send_ctrl_cmd CMD: 0x9, value: 0x0, index: 0 type: 2 364s (process:1886): libfprint-SSM-DEBUG: 00:53:33.549: [fpcmoc] FP_CMD_NUM_STATES completed successfully 364s (process:1886): libfprint-DEBUG: 00:53:33.549: fpc_cmd_receive_cb current ssm request: 9 state: 0 364s (process:1886): libfprint-SSM-DEBUG: 00:53:33.549: [fpcmoc] FP_CMD_NUM_STATES entering state 1 364s (process:1886): libfprint-DEBUG: 00:53:33.550: fpc_cmd_receive_cb current ssm request: 9 state: 1 364s (process:1886): libfprint-DEBUG: 00:53:33.550: fpc_cmd_receive_cb recv evt data length: 24 364s (process:1886): libfprint-DEBUG: 00:53:33.550: fpc_evt_cb Got capture event 364s (process:1886): libfprint-device-DEBUG: 00:53:33.550: Device reported finger status change: FP_FINGER_STATUS_NEEDED 364s (process:1886): libfprint-SSM-DEBUG: 00:53:33.550: [fpcmoc] verify_identify entering state 2 364s (process:1886): libfprint-SSM-DEBUG: 00:53:33.550: [fpcmoc] FP_CMD_NUM_STATES entering state 0 364s (process:1886): libfprint-DEBUG: 00:53:33.550: fpc_send_ctrl_cmd CMD: 0x6b, value: 0x0, index: 0 type: 3 364s (process:1886): libfprint-SSM-DEBUG: 00:53:33.550: [fpcmoc] FP_CMD_NUM_STATES completed successfully 364s (process:1886): libfprint-DEBUG: 00:53:33.550: fpc_cmd_receive_cb current ssm request: 107 state: 0 364s (process:1886): libfprint-device-DEBUG: 00:53:33.551: Device reported identify result 364s (process:1886): libfprint-SSM-DEBUG: 00:53:33.551: [fpcmoc] verify_identify entering state 3 364s (process:1886): libfprint-SSM-DEBUG: 00:53:33.551: [fpcmoc] FP_CMD_NUM_STATES entering state 0 364s (process:1886): libfprint-DEBUG: 00:53:33.551: fpc_send_ctrl_cmd CMD: 0x3, value: 0x1, index: 0 type: 1 364s (process:1886): libfprint-SSM-DEBUG: 00:53:33.551: [fpcmoc] FP_CMD_NUM_STATES completed successfully 364s (process:1886): libfprint-DEBUG: 00:53:33.552: fpc_cmd_receive_cb current ssm request: 3 state: 0 364s (process:1886): libfprint-DEBUG: 00:53:33.552: fpc_do_abort_cb Do abort for reasons 364s (process:1886): libfprint-SSM-DEBUG: 00:53:33.552: [fpcmoc] verify_identify completed successfully 364s (process:1886): libfprint-DEBUG: 00:53:33.552: Verify_identify complete! 364s (process:1886): libfprint-device-DEBUG: 00:53:33.552: Device reported identify completion 364s (process:1886): libfprint-device-DEBUG: 00:53:33.552: Device reported finger status change: FP_FINGER_STATUS_NONE 364s (process:1886): libfprint-SSM-DEBUG: 00:53:33.552: [fpcmoc] FP_CMD_NUM_STATES completed successfully 364s (process:1886): libfprint-device-DEBUG: 00:53:33.552: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 364s (process:1886): libfprint-device-DEBUG: 00:53:33.552: Not updating temperature model, device can run continuously! 364s (process:1886): libfprint-DEBUG: 00:53:33.552: fpc_dev_template_delete enter --> 364s (process:1886): libfprint-SSM-DEBUG: 00:53:33.552: [fpcmoc] FP_CMD_NUM_STATES entering state 0 364s (process:1886): libfprint-DEBUG: 00:53:33.552: fpc_send_ctrl_cmd CMD: 0x63, value: 0x0, index: 0 type: 1 364s (process:1886): libfprint-DEBUG: 00:53:33.553: fpc_dev_template_delete exit <-- 364s (process:1886): libfprint-DEBUG: 00:53:33.553: fpc_cmd_receive_cb current ssm request: 99 state: 0 364s (process:1886): libfprint-device-DEBUG: 00:53:33.553: Device reported deletion completion 364s (process:1886): libfprint-SSM-DEBUG: 00:53:33.553: [fpcmoc] FP_CMD_NUM_STATES completed successfully 364s (process:1886): libfprint-device-DEBUG: 00:53:33.553: Completing action FPI_DEVICE_ACTION_DELETE in idle! 364s (process:1886): libfprint-device-DEBUG: 00:53:33.553: Not updating temperature model, device can run continuously! 364s (process:1886): libfprint-DEBUG: 00:53:33.553: fpc_dev_close enter --> 364s (process:1886): libfprint-device-DEBUG: 00:53:33.553: Device reported close completion 364s (process:1886): libfprint-device-DEBUG: 00:53:33.554: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 364s (process:1886): libfprint-device-DEBUG: 00:53:33.554: Not updating temperature model, device can run continuously! 364s Clear 364s Clear done 364s enrolling 364s enroll progress: (<__gi__.FpiDeviceFpcMoc object at 0xee1c9888 (FpiDeviceFpcMoc at 0x16dec68)>, 1, None, None, None) 364s enroll progress: (<__gi__.FpiDeviceFpcMoc object at 0xee1c9888 (FpiDeviceFpcMoc at 0x16dec68)>, 2, None, None, None) 364s enroll progress: (<__gi__.FpiDeviceFpcMoc object at 0xee1c9888 (FpiDeviceFpcMoc at 0x16dec68)>, 3, None, None, None) 364s enroll progress: (<__gi__.FpiDeviceFpcMoc object at 0xee1c9888 (FpiDeviceFpcMoc at 0x16dec68)>, 4, None, None, None) 364s enroll progress: (<__gi__.FpiDeviceFpcMoc object at 0xee1c9888 (FpiDeviceFpcMoc at 0x16dec68)>, 5, None, None, None) 364s enroll progress: (<__gi__.FpiDeviceFpcMoc object at 0xee1c9888 (FpiDeviceFpcMoc at 0x16dec68)>, 5, None, None, GLib.Error('Please try again after removing the finger first.', 'fp - device - retry - quark', 3)) 364s enroll progress: (<__gi__.FpiDeviceFpcMoc object at 0xee1c9888 (FpiDeviceFpcMoc at 0x16dec68)>, 6, None, None, None) 364s enroll progress: (<__gi__.FpiDeviceFpcMoc object at 0xee1c9888 (FpiDeviceFpcMoc at 0x16dec68)>, 7, None, None, None) 364s enroll progress: (<__gi__.FpiDeviceFpcMoc object at 0xee1c9888 (FpiDeviceFpcMoc at 0x16dec68)>, 7, None, None, GLib.Error('Please try again after removing the finger first.', 'fp - device - retry - quark', 3)) 364s enroll progress: (<__gi__.FpiDeviceFpcMoc object at 0xee1c9888 (FpiDeviceFpcMoc at 0x16dec68)>, 8, None, None, None) 364s enroll progress: (<__gi__.FpiDeviceFpcMoc object at 0xee1c9888 (FpiDeviceFpcMoc at 0x16dec68)>, 9, None, None, None) 364s enroll progress: (<__gi__.FpiDeviceFpcMoc object at 0xee1c9888 (FpiDeviceFpcMoc at 0x16dec68)>, 10, None, None, None) 364s enroll progress: (<__gi__.FpiDeviceFpcMoc object at 0xee1c9888 (FpiDeviceFpcMoc at 0x16dec68)>, 10, None, None, GLib.Error('Please try again after removing the finger first.', 'fp - device - retry - quark', 3)) 364s enroll progress: (<__gi__.FpiDeviceFpcMoc object at 0xee1c9888 (FpiDeviceFpcMoc at 0x16dec68)>, 11, None, None, None) 364s enroll progress: (<__gi__.FpiDeviceFpcMoc object at 0xee1c9888 (FpiDeviceFpcMoc at 0x16dec68)>, 12, None, None, None) 364s enroll done 364s listing 364s listing done 364s verifying 364s verify done 364s async identifying 364s indentification_done: 364s deleting 364s delete done 364s ** (umockdev-run:1882): DEBUG: 00:53:33.582: umockdev.vala:154: Removing test bed /tmp/umockdev.WNQ512 364s (umockdev-run:1882): GLib-DEBUG: 00:53:33.589: unsetenv() is not thread-safe and should not be used after threads are created 364s PASS: libfprint-2/driver-fpcmoc.test 364s Running test: libfprint-2/driver-synaptics.test 364s ** (umockdev-run:1894): DEBUG: 00:53:33.646: umockdev.vala:127: Created udev test bed /tmp/umockdev.4P7B22 364s ** (umockdev-run:1894): DEBUG: 00:53:33.647: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0/usb1/1-9 364s ** (umockdev-run:1894): DEBUG: 00:53:33.649: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0/usb1/1-9 (subsystem usb) 364s ** (umockdev-run:1894): DEBUG: 00:53:33.652: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.4P7B22/dev/bus/usb/001/004 364s ** (umockdev-run:1894): DEBUG: 00:53:33.653: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0/usb1 364s ** (umockdev-run:1894): DEBUG: 00:53:33.654: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0/usb1 (subsystem usb) 364s ** (umockdev-run:1894): DEBUG: 00:53:33.658: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.4P7B22/dev/bus/usb/001/001 364s ** (umockdev-run:1894): DEBUG: 00:53:33.658: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0 364s ** (umockdev-run:1894): DEBUG: 00:53:33.659: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0 (subsystem pci) 364s (process:1898): libfprint-context-DEBUG: 00:53:33.772: Initializing FpContext (libfprint version 1.94.8+tod1) 364s (process:1898): libfprint-tod-DEBUG: 00:53:33.773: Impossible to load the shared drivers dir Error opening directory “/usr/lib/arm-linux-gnueabihf/libfprint-2/tod-1”: No such file or directory 364s (process:1898): libfprint-context-DEBUG: 00:53:33.776: No driver found for USB device 1D6B:0002 364s (process:1898): libfprint-synaptics-DEBUG: 00:53:33.776: 7399781837296: ../libfprint/drivers/synaptics/synaptics.c:1243 364s (process:1898): libfprint-synaptics-DEBUG: 00:53:33.778: Build Time: 1596608839 364s (process:1898): libfprint-synaptics-DEBUG: 00:53:33.778: Build Num: 3273255 364s (process:1898): libfprint-synaptics-DEBUG: 00:53:33.778: Version: 10.1 364s (process:1898): libfprint-synaptics-DEBUG: 00:53:33.778: Target: 1 364s (process:1898): libfprint-synaptics-DEBUG: 00:53:33.778: Product: 65 364s (process:1898): libfprint-synaptics-DEBUG: 00:53:33.778: sequence number is 1 364s (process:1898): libfprint-SSM-DEBUG: 00:53:33.778: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 364s (process:1898): libfprint-SSM-DEBUG: 00:53:33.778: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 364s (process:1898): libfprint-device-DEBUG: 00:53:33.779: Device reported probe completion 364s (process:1898): libfprint-SSM-DEBUG: 00:53:33.779: [synaptics] SYNAPTICS_CMD_NUM_STATES completed successfully 364s (process:1898): libfprint-device-DEBUG: 00:53:33.779: Completing action FPI_DEVICE_ACTION_PROBE in idle! 364s (process:1898): libfprint-device-DEBUG: 00:53:33.779: Not updating temperature model, device can run continuously! 364s (process:1898): libfprint-synaptics-DEBUG: 00:53:33.781: 7399781842286: ../libfprint/drivers/synaptics/synaptics.c:1403 364s (process:1898): libfprint-synaptics-DEBUG: 00:53:33.781: sequence number is 2 364s (process:1898): libfprint-SSM-DEBUG: 00:53:33.781: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 364s (process:1898): libfprint-SSM-DEBUG: 00:53:33.782: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 364s (process:1898): libfprint-device-DEBUG: 00:53:33.782: Device reported open completion 364s (process:1898): libfprint-SSM-DEBUG: 00:53:33.782: [synaptics] SYNAPTICS_CMD_NUM_STATES completed successfully 364s (process:1898): libfprint-device-DEBUG: 00:53:33.782: Completing action FPI_DEVICE_ACTION_OPEN in idle! 364s (process:1898): libfprint-device-DEBUG: 00:53:33.782: Not updating temperature model, device can run continuously! 364s (process:1898): libfprint-synaptics-DEBUG: 00:53:33.783: clear all prints in database 364s (process:1898): libfprint-synaptics-DEBUG: 00:53:33.783: sequence number is 3 364s (process:1898): libfprint-SSM-DEBUG: 00:53:33.783: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 364s (process:1898): libfprint-SSM-DEBUG: 00:53:33.783: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 364s (process:1898): libfprint-synaptics-DEBUG: 00:53:33.783: Deleting All Enrolled Users is 0% complete 364s (process:1898): libfprint-SSM-DEBUG: 00:53:33.783: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 364s (process:1898): libfprint-synaptics-DEBUG: 00:53:33.784: interrupt transfer done 364s (process:1898): libfprint-SSM-DEBUG: 00:53:33.784: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 364s (process:1898): libfprint-SSM-DEBUG: 00:53:33.785: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 364s (process:1898): libfprint-SSM-DEBUG: 00:53:33.785: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 364s (process:1898): libfprint-SSM-DEBUG: 00:53:33.785: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 364s (process:1898): libfprint-synaptics-DEBUG: 00:53:33.785: Deleting All Enrolled Users is 100% complete 364s (process:1898): libfprint-SSM-DEBUG: 00:53:33.785: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 364s (process:1898): libfprint-synaptics-DEBUG: 00:53:33.786: interrupt transfer done 364s (process:1898): libfprint-SSM-DEBUG: 00:53:33.786: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 364s (process:1898): libfprint-SSM-DEBUG: 00:53:33.786: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 364s (process:1898): libfprint-SSM-DEBUG: 00:53:33.786: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 364s (process:1898): libfprint-SSM-DEBUG: 00:53:33.786: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 364s (process:1898): libfprint-synaptics-DEBUG: 00:53:33.787: Successfully deleted all enrolled user 364s (process:1898): libfprint-device-DEBUG: 00:53:33.787: Device reported deletion completion 364s (process:1898): libfprint-SSM-DEBUG: 00:53:33.787: [synaptics] SYNAPTICS_CMD_NUM_STATES completed successfully 364s (process:1898): libfprint-device-DEBUG: 00:53:33.787: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 364s (process:1898): libfprint-device-DEBUG: 00:53:33.787: Not updating temperature model, device can run continuously! 364s (process:1898): libfprint-device-DEBUG: 00:53:33.788: Not updating temperature model, device can run continuously! 364s (process:1898): libfprint-synaptics-DEBUG: 00:53:33.788: 7399781849228: ../libfprint/drivers/synaptics/synaptics.c:1014 364s (process:1898): libfprint-synaptics-DEBUG: 00:53:33.788: user_id: FP1-00000000-0-00000000-nobody, finger: 1 364s (process:1898): libfprint-synaptics-DEBUG: 00:53:33.788: sequence number is 4 364s (process:1898): libfprint-SSM-DEBUG: 00:53:33.788: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 364s (process:1898): libfprint-SSM-DEBUG: 00:53:33.788: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 364s (process:1898): libfprint-device-DEBUG: 00:53:33.789: Device reported finger status change: FP_FINGER_STATUS_NEEDED 364s (process:1898): libfprint-synaptics-DEBUG: 00:53:33.789: Place Finger on the Sensor! 364s (process:1898): libfprint-SSM-DEBUG: 00:53:33.789: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 364s (process:1898): libfprint-synaptics-DEBUG: 00:53:33.789: interrupt transfer done 364s (process:1898): libfprint-SSM-DEBUG: 00:53:33.789: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 364s (process:1898): libfprint-SSM-DEBUG: 00:53:33.790: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 364s (process:1898): libfprint-SSM-DEBUG: 00:53:33.790: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 364s (process:1898): libfprint-SSM-DEBUG: 00:53:33.790: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 364s (process:1898): libfprint-device-DEBUG: 00:53:33.790: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 364s (process:1898): libfprint-synaptics-DEBUG: 00:53:33.790: Finger is now on the sensor 364s (process:1898): libfprint-synaptics-DEBUG: 00:53:33.790: Received message with 0 sequence number 0x91, ignoring! 364s (process:1898): libfprint-SSM-DEBUG: 00:53:33.790: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 364s (process:1898): libfprint-synaptics-DEBUG: 00:53:33.791: interrupt transfer done 364s (process:1898): libfprint-SSM-DEBUG: 00:53:33.791: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 364s (process:1898): libfprint-SSM-DEBUG: 00:53:33.791: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 364s (process:1898): libfprint-SSM-DEBUG: 00:53:33.791: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 364s (process:1898): libfprint-SSM-DEBUG: 00:53:33.791: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 364s (process:1898): libfprint-synaptics-DEBUG: 00:53:33.792: Fingerprint image capture complete! 364s (process:1898): libfprint-SSM-DEBUG: 00:53:33.792: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 364s (process:1898): libfprint-synaptics-DEBUG: 00:53:33.793: interrupt transfer done 364s (process:1898): libfprint-SSM-DEBUG: 00:53:33.793: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 364s (process:1898): libfprint-SSM-DEBUG: 00:53:33.793: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 364s (process:1898): libfprint-SSM-DEBUG: 00:53:33.793: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 364s (process:1898): libfprint-SSM-DEBUG: 00:53:33.793: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 364s (process:1898): libfprint-device-DEBUG: 00:53:33.794: Device reported finger status change: FP_FINGER_STATUS_NEEDED 364s (process:1898): libfprint-synaptics-DEBUG: 00:53:33.794: Finger is now off the sensor 364s (process:1898): libfprint-synaptics-DEBUG: 00:53:33.794: Received message with 0 sequence number 0x91, ignoring! 364s (process:1898): libfprint-SSM-DEBUG: 00:53:33.794: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 364s (process:1898): libfprint-synaptics-DEBUG: 00:53:33.794: interrupt transfer done 364s (process:1898): libfprint-SSM-DEBUG: 00:53:33.794: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 364s (process:1898): libfprint-SSM-DEBUG: 00:53:33.795: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 364s (process:1898): libfprint-SSM-DEBUG: 00:53:33.795: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 364s (process:1898): libfprint-SSM-DEBUG: 00:53:33.795: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 364s (process:1898): libfprint-synaptics-DEBUG: 00:53:33.795: Enrollment is 12 % 364s (process:1898): libfprint-device-DEBUG: 00:53:33.795: Device reported enroll progress, reported 1 of 8 have been completed 364s (process:1898): libfprint-SSM-DEBUG: 00:53:33.795: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 364s (process:1898): libfprint-synaptics-DEBUG: 00:53:33.796: interrupt transfer done 364s (process:1898): libfprint-SSM-DEBUG: 00:53:33.796: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 364s (process:1898): libfprint-SSM-DEBUG: 00:53:33.796: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 364s (process:1898): libfprint-SSM-DEBUG: 00:53:33.796: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 364s (process:1898): libfprint-SSM-DEBUG: 00:53:33.796: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 364s (process:1898): libfprint-device-DEBUG: 00:53:33.797: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 364s (process:1898): libfprint-synaptics-DEBUG: 00:53:33.797: Finger is now on the sensor 364s (process:1898): libfprint-synaptics-DEBUG: 00:53:33.797: Received message with 0 sequence number 0x91, ignoring! 364s (process:1898): libfprint-SSM-DEBUG: 00:53:33.797: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 364s (process:1898): libfprint-synaptics-DEBUG: 00:53:33.797: interrupt transfer done 364s (process:1898): libfprint-SSM-DEBUG: 00:53:33.797: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 364s (process:1898): libfprint-SSM-DEBUG: 00:53:33.798: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 364s (process:1898): libfprint-SSM-DEBUG: 00:53:33.798: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 364s (process:1898): libfprint-SSM-DEBUG: 00:53:33.798: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 364s (process:1898): libfprint-synaptics-DEBUG: 00:53:33.798: Fingerprint image capture complete! 364s (process:1898): libfprint-SSM-DEBUG: 00:53:33.798: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 364s (process:1898): libfprint-synaptics-DEBUG: 00:53:33.799: interrupt transfer done 364s (process:1898): libfprint-SSM-DEBUG: 00:53:33.799: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 364s (process:1898): libfprint-SSM-DEBUG: 00:53:33.799: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 364s (process:1898): libfprint-SSM-DEBUG: 00:53:33.799: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 364s (process:1898): libfprint-SSM-DEBUG: 00:53:33.799: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 364s (process:1898): libfprint-device-DEBUG: 00:53:33.800: Device reported finger status change: FP_FINGER_STATUS_NEEDED 364s (process:1898): libfprint-synaptics-DEBUG: 00:53:33.800: Finger is now off the sensor 364s (process:1898): libfprint-synaptics-DEBUG: 00:53:33.800: Received message with 0 sequence number 0x91, ignoring! 364s (process:1898): libfprint-SSM-DEBUG: 00:53:33.800: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 364s (process:1898): libfprint-synaptics-DEBUG: 00:53:33.800: interrupt transfer done 364s (process:1898): libfprint-SSM-DEBUG: 00:53:33.800: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 364s (process:1898): libfprint-SSM-DEBUG: 00:53:33.801: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 364s (process:1898): libfprint-SSM-DEBUG: 00:53:33.801: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 364s (process:1898): libfprint-SSM-DEBUG: 00:53:33.801: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 364s (process:1898): libfprint-synaptics-DEBUG: 00:53:33.801: Enrollment is 25 % 364s (process:1898): libfprint-device-DEBUG: 00:53:33.801: Device reported enroll progress, reported 2 of 8 have been completed 364s (process:1898): libfprint-SSM-DEBUG: 00:53:33.802: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 364s (process:1898): libfprint-synaptics-DEBUG: 00:53:33.802: interrupt transfer done 364s (process:1898): libfprint-SSM-DEBUG: 00:53:33.802: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 364s (process:1898): libfprint-SSM-DEBUG: 00:53:33.803: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 364s (process:1898): libfprint-SSM-DEBUG: 00:53:33.803: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 364s (process:1898): libfprint-SSM-DEBUG: 00:53:33.803: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 364s (process:1898): libfprint-device-DEBUG: 00:53:33.803: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 364s (process:1898): libfprint-synaptics-DEBUG: 00:53:33.803: Finger is now on the sensor 364s (process:1898): libfprint-synaptics-DEBUG: 00:53:33.803: Received message with 0 sequence number 0x91, ignoring! 364s (process:1898): libfprint-SSM-DEBUG: 00:53:33.803: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 364s (process:1898): libfprint-synaptics-DEBUG: 00:53:33.804: interrupt transfer done 364s (process:1898): libfprint-SSM-DEBUG: 00:53:33.804: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 364s (process:1898): libfprint-SSM-DEBUG: 00:53:33.804: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 364s (process:1898): libfprint-SSM-DEBUG: 00:53:33.804: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 364s (process:1898): libfprint-SSM-DEBUG: 00:53:33.804: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 364s (process:1898): libfprint-synaptics-DEBUG: 00:53:33.805: Fingerprint image capture complete! 364s (process:1898): libfprint-SSM-DEBUG: 00:53:33.805: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 364s (process:1898): libfprint-synaptics-DEBUG: 00:53:33.806: interrupt transfer done 364s (process:1898): libfprint-SSM-DEBUG: 00:53:33.806: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 364s (process:1898): libfprint-SSM-DEBUG: 00:53:33.806: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 364s (process:1898): libfprint-SSM-DEBUG: 00:53:33.806: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 364s (process:1898): libfprint-SSM-DEBUG: 00:53:33.806: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 364s (process:1898): libfprint-synaptics-DEBUG: 00:53:33.807: Enrollment is 37 % 364s (process:1898): libfprint-device-DEBUG: 00:53:33.807: Device reported enroll progress, reported 3 of 8 have been completed 364s (process:1898): libfprint-SSM-DEBUG: 00:53:33.807: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 364s (process:1898): libfprint-synaptics-DEBUG: 00:53:33.807: interrupt transfer done 364s (process:1898): libfprint-SSM-DEBUG: 00:53:33.807: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 364s (process:1898): libfprint-SSM-DEBUG: 00:53:33.808: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 364s (process:1898): libfprint-SSM-DEBUG: 00:53:33.808: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 364s (process:1898): libfprint-SSM-DEBUG: 00:53:33.808: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 364s (process:1898): libfprint-device-DEBUG: 00:53:33.809: Device reported finger status change: FP_FINGER_STATUS_NEEDED 364s (process:1898): libfprint-synaptics-DEBUG: 00:53:33.809: Finger is now off the sensor 364s (process:1898): libfprint-synaptics-DEBUG: 00:53:33.809: Received message with 0 sequence number 0x91, ignoring! 364s (process:1898): libfprint-SSM-DEBUG: 00:53:33.809: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 364s (process:1898): libfprint-synaptics-DEBUG: 00:53:33.809: interrupt transfer done 364s (process:1898): libfprint-SSM-DEBUG: 00:53:33.809: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 364s (process:1898): libfprint-SSM-DEBUG: 00:53:33.810: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 364s (process:1898): libfprint-SSM-DEBUG: 00:53:33.810: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 364s (process:1898): libfprint-SSM-DEBUG: 00:53:33.810: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 364s (process:1898): libfprint-device-DEBUG: 00:53:33.810: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 364s (process:1898): libfprint-synaptics-DEBUG: 00:53:33.810: Finger is now on the sensor 364s (process:1898): libfprint-synaptics-DEBUG: 00:53:33.810: Received message with 0 sequence number 0x91, ignoring! 364s (process:1898): libfprint-SSM-DEBUG: 00:53:33.810: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 364s (process:1898): libfprint-synaptics-DEBUG: 00:53:33.811: interrupt transfer done 364s (process:1898): libfprint-SSM-DEBUG: 00:53:33.811: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 364s (process:1898): libfprint-SSM-DEBUG: 00:53:33.811: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 364s (process:1898): libfprint-SSM-DEBUG: 00:53:33.811: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 364s (process:1898): libfprint-SSM-DEBUG: 00:53:33.811: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 364s (process:1898): libfprint-synaptics-DEBUG: 00:53:33.812: Fingerprint image capture complete! 364s (process:1898): libfprint-SSM-DEBUG: 00:53:33.812: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 364s (process:1898): libfprint-synaptics-DEBUG: 00:53:33.812: interrupt transfer done 364s (process:1898): libfprint-SSM-DEBUG: 00:53:33.812: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 364s (process:1898): libfprint-SSM-DEBUG: 00:53:33.813: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 364s (process:1898): libfprint-SSM-DEBUG: 00:53:33.813: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 364s (process:1898): libfprint-SSM-DEBUG: 00:53:33.813: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 364s (process:1898): libfprint-device-DEBUG: 00:53:33.813: Device reported finger status change: FP_FINGER_STATUS_NEEDED 364s (process:1898): libfprint-synaptics-DEBUG: 00:53:33.813: Finger is now off the sensor 364s (process:1898): libfprint-synaptics-DEBUG: 00:53:33.813: Received message with 0 sequence number 0x91, ignoring! 364s (process:1898): libfprint-SSM-DEBUG: 00:53:33.813: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 364s (process:1898): libfprint-synaptics-DEBUG: 00:53:33.814: interrupt transfer done 364s (process:1898): libfprint-SSM-DEBUG: 00:53:33.814: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 364s (process:1898): libfprint-SSM-DEBUG: 00:53:33.814: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 364s (process:1898): libfprint-SSM-DEBUG: 00:53:33.814: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 364s (process:1898): libfprint-SSM-DEBUG: 00:53:33.814: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 364s (process:1898): libfprint-synaptics-DEBUG: 00:53:33.815: Enrollment is 50 % 364s (process:1898): libfprint-device-DEBUG: 00:53:33.815: Device reported enroll progress, reported 4 of 8 have been completed 364s (process:1898): libfprint-SSM-DEBUG: 00:53:33.815: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 364s (process:1898): libfprint-synaptics-DEBUG: 00:53:33.815: interrupt transfer done 364s (process:1898): libfprint-SSM-DEBUG: 00:53:33.815: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 364s (process:1898): libfprint-SSM-DEBUG: 00:53:33.816: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 364s (process:1898): libfprint-SSM-DEBUG: 00:53:33.816: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 364s (process:1898): libfprint-SSM-DEBUG: 00:53:33.816: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 364s (process:1898): libfprint-device-DEBUG: 00:53:33.817: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 364s (process:1898): libfprint-synaptics-DEBUG: 00:53:33.817: Finger is now on the sensor 364s (process:1898): libfprint-synaptics-DEBUG: 00:53:33.817: Received message with 0 sequence number 0x91, ignoring! 364s (process:1898): libfprint-SSM-DEBUG: 00:53:33.817: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 364s (process:1898): libfprint-synaptics-DEBUG: 00:53:33.817: interrupt transfer done 364s (process:1898): libfprint-SSM-DEBUG: 00:53:33.817: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 364s (process:1898): libfprint-SSM-DEBUG: 00:53:33.818: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 364s (process:1898): libfprint-SSM-DEBUG: 00:53:33.818: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 364s (process:1898): libfprint-SSM-DEBUG: 00:53:33.818: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 364s (process:1898): libfprint-synaptics-DEBUG: 00:53:33.818: Fingerprint image capture complete! 364s (process:1898): libfprint-SSM-DEBUG: 00:53:33.818: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 364s (process:1898): libfprint-synaptics-DEBUG: 00:53:33.819: interrupt transfer done 364s (process:1898): libfprint-SSM-DEBUG: 00:53:33.819: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 364s (process:1898): libfprint-SSM-DEBUG: 00:53:33.819: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 364s (process:1898): libfprint-SSM-DEBUG: 00:53:33.819: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 364s (process:1898): libfprint-SSM-DEBUG: 00:53:33.819: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 364s (process:1898): libfprint-device-DEBUG: 00:53:33.820: Device reported finger status change: FP_FINGER_STATUS_NEEDED 364s (process:1898): libfprint-synaptics-DEBUG: 00:53:33.820: Finger is now off the sensor 364s (process:1898): libfprint-synaptics-DEBUG: 00:53:33.820: Received message with 0 sequence number 0x91, ignoring! 364s (process:1898): libfprint-SSM-DEBUG: 00:53:33.820: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 364s (process:1898): libfprint-synaptics-DEBUG: 00:53:33.820: interrupt transfer done 364s (process:1898): libfprint-SSM-DEBUG: 00:53:33.820: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 364s (process:1898): libfprint-SSM-DEBUG: 00:53:33.821: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 364s (process:1898): libfprint-SSM-DEBUG: 00:53:33.821: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 364s (process:1898): libfprint-SSM-DEBUG: 00:53:33.821: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 364s (process:1898): libfprint-synaptics-DEBUG: 00:53:33.821: Enrollment is 62 % 364s (process:1898): libfprint-device-DEBUG: 00:53:33.821: Device reported enroll progress, reported 5 of 8 have been completed 364s (process:1898): libfprint-SSM-DEBUG: 00:53:33.821: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 364s (process:1898): libfprint-synaptics-DEBUG: 00:53:33.822: interrupt transfer done 364s (process:1898): libfprint-SSM-DEBUG: 00:53:33.822: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 364s (process:1898): libfprint-SSM-DEBUG: 00:53:33.822: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 364s (process:1898): libfprint-SSM-DEBUG: 00:53:33.822: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 364s (process:1898): libfprint-SSM-DEBUG: 00:53:33.822: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 364s (process:1898): libfprint-device-DEBUG: 00:53:33.823: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 364s (process:1898): libfprint-synaptics-DEBUG: 00:53:33.823: Finger is now on the sensor 364s (process:1898): libfprint-synaptics-DEBUG: 00:53:33.823: Received message with 0 sequence number 0x91, ignoring! 364s (process:1898): libfprint-SSM-DEBUG: 00:53:33.823: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 364s (process:1898): libfprint-synaptics-DEBUG: 00:53:33.823: interrupt transfer done 364s (process:1898): libfprint-SSM-DEBUG: 00:53:33.823: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 364s (process:1898): libfprint-SSM-DEBUG: 00:53:33.824: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 364s (process:1898): libfprint-SSM-DEBUG: 00:53:33.824: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 364s (process:1898): libfprint-SSM-DEBUG: 00:53:33.824: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 364s (process:1898): libfprint-synaptics-DEBUG: 00:53:33.824: Fingerprint image capture complete! 364s (process:1898): libfprint-SSM-DEBUG: 00:53:33.824: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 364s (process:1898): libfprint-synaptics-DEBUG: 00:53:33.825: interrupt transfer done 364s (process:1898): libfprint-SSM-DEBUG: 00:53:33.825: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 364s (process:1898): libfprint-SSM-DEBUG: 00:53:33.825: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 364s (process:1898): libfprint-SSM-DEBUG: 00:53:33.825: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 364s (process:1898): libfprint-SSM-DEBUG: 00:53:33.825: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 364s (process:1898): libfprint-device-DEBUG: 00:53:33.826: Device reported finger status change: FP_FINGER_STATUS_NEEDED 364s (process:1898): libfprint-synaptics-DEBUG: 00:53:33.826: Finger is now off the sensor 364s (process:1898): libfprint-synaptics-DEBUG: 00:53:33.826: Received message with 0 sequence number 0x91, ignoring! 364s (process:1898): libfprint-SSM-DEBUG: 00:53:33.826: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 364s (process:1898): libfprint-synaptics-DEBUG: 00:53:33.826: interrupt transfer done 364s (process:1898): libfprint-SSM-DEBUG: 00:53:33.826: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 364s (process:1898): libfprint-SSM-DEBUG: 00:53:33.827: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 364s (process:1898): libfprint-SSM-DEBUG: 00:53:33.827: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 364s (process:1898): libfprint-SSM-DEBUG: 00:53:33.827: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 364s (process:1898): libfprint-synaptics-DEBUG: 00:53:33.827: Enrollment is 62 % 364s (process:1898): libfprint-device-DEBUG: 00:53:33.827: Device reported enroll progress, reported 5 of 8 have been completed 364s (process:1898): libfprint-SSM-DEBUG: 00:53:33.827: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 364s (process:1898): libfprint-synaptics-DEBUG: 00:53:33.828: interrupt transfer done 364s (process:1898): libfprint-SSM-DEBUG: 00:53:33.828: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 364s (process:1898): libfprint-SSM-DEBUG: 00:53:33.828: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 364s (process:1898): libfprint-SSM-DEBUG: 00:53:33.828: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 364s (process:1898): libfprint-SSM-DEBUG: 00:53:33.828: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 364s (process:1898): libfprint-device-DEBUG: 00:53:33.829: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 364s (process:1898): libfprint-synaptics-DEBUG: 00:53:33.829: Finger is now on the sensor 364s (process:1898): libfprint-synaptics-DEBUG: 00:53:33.829: Received message with 0 sequence number 0x91, ignoring! 364s (process:1898): libfprint-SSM-DEBUG: 00:53:33.829: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 364s (process:1898): libfprint-synaptics-DEBUG: 00:53:33.829: interrupt transfer done 364s (process:1898): libfprint-SSM-DEBUG: 00:53:33.829: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 364s (process:1898): libfprint-SSM-DEBUG: 00:53:33.830: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 364s (process:1898): libfprint-SSM-DEBUG: 00:53:33.830: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 364s (process:1898): libfprint-SSM-DEBUG: 00:53:33.830: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 364s (process:1898): libfprint-synaptics-DEBUG: 00:53:33.830: Fingerprint image capture complete! 364s (process:1898): libfprint-SSM-DEBUG: 00:53:33.830: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 364s (process:1898): libfprint-synaptics-DEBUG: 00:53:33.831: interrupt transfer done 364s (process:1898): libfprint-SSM-DEBUG: 00:53:33.831: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 364s (process:1898): libfprint-SSM-DEBUG: 00:53:33.832: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 364s (process:1898): libfprint-SSM-DEBUG: 00:53:33.832: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 364s (process:1898): libfprint-SSM-DEBUG: 00:53:33.832: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 364s (process:1898): libfprint-synaptics-DEBUG: 00:53:33.832: Enrollment is 75 % 364s (process:1898): libfprint-device-DEBUG: 00:53:33.832: Device reported enroll progress, reported 6 of 8 have been completed 364s (process:1898): libfprint-SSM-DEBUG: 00:53:33.832: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 364s (process:1898): libfprint-synaptics-DEBUG: 00:53:33.833: interrupt transfer done 364s (process:1898): libfprint-SSM-DEBUG: 00:53:33.833: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 364s (process:1898): libfprint-SSM-DEBUG: 00:53:33.833: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 364s (process:1898): libfprint-SSM-DEBUG: 00:53:33.833: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 364s (process:1898): libfprint-SSM-DEBUG: 00:53:33.833: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 364s (process:1898): libfprint-device-DEBUG: 00:53:33.834: Device reported finger status change: FP_FINGER_STATUS_NEEDED 364s (process:1898): libfprint-synaptics-DEBUG: 00:53:33.834: Finger is now off the sensor 364s (process:1898): libfprint-synaptics-DEBUG: 00:53:33.834: Received message with 0 sequence number 0x91, ignoring! 364s (process:1898): libfprint-SSM-DEBUG: 00:53:33.834: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 364s (process:1898): libfprint-synaptics-DEBUG: 00:53:33.835: interrupt transfer done 364s (process:1898): libfprint-SSM-DEBUG: 00:53:33.835: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 364s (process:1898): libfprint-SSM-DEBUG: 00:53:33.835: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 364s (process:1898): libfprint-SSM-DEBUG: 00:53:33.835: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 364s (process:1898): libfprint-SSM-DEBUG: 00:53:33.835: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 364s (process:1898): libfprint-device-DEBUG: 00:53:33.836: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 364s (process:1898): libfprint-synaptics-DEBUG: 00:53:33.836: Finger is now on the sensor 364s (process:1898): libfprint-synaptics-DEBUG: 00:53:33.836: Received message with 0 sequence number 0x91, ignoring! 364s (process:1898): libfprint-SSM-DEBUG: 00:53:33.836: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 364s (process:1898): libfprint-synaptics-DEBUG: 00:53:33.837: interrupt transfer done 364s (process:1898): libfprint-SSM-DEBUG: 00:53:33.837: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 364s (process:1898): libfprint-SSM-DEBUG: 00:53:33.837: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 364s (process:1898): libfprint-SSM-DEBUG: 00:53:33.837: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 364s (process:1898): libfprint-SSM-DEBUG: 00:53:33.837: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 364s (process:1898): libfprint-synaptics-DEBUG: 00:53:33.838: Fingerprint image capture complete! 364s (process:1898): libfprint-SSM-DEBUG: 00:53:33.838: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 364s (process:1898): libfprint-synaptics-DEBUG: 00:53:33.838: interrupt transfer done 364s (process:1898): libfprint-SSM-DEBUG: 00:53:33.838: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 364s (process:1898): libfprint-SSM-DEBUG: 00:53:33.839: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 364s (process:1898): libfprint-SSM-DEBUG: 00:53:33.839: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 364s (process:1898): libfprint-SSM-DEBUG: 00:53:33.839: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 364s (process:1898): libfprint-device-DEBUG: 00:53:33.839: Device reported finger status change: FP_FINGER_STATUS_NEEDED 364s (process:1898): libfprint-synaptics-DEBUG: 00:53:33.839: Finger is now off the sensor 364s (process:1898): libfprint-synaptics-DEBUG: 00:53:33.839: Received message with 0 sequence number 0x91, ignoring! 364s (process:1898): libfprint-SSM-DEBUG: 00:53:33.839: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 364s (process:1898): libfprint-synaptics-DEBUG: 00:53:33.840: interrupt transfer done 364s (process:1898): libfprint-SSM-DEBUG: 00:53:33.840: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 364s (process:1898): libfprint-SSM-DEBUG: 00:53:33.840: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 364s (process:1898): libfprint-SSM-DEBUG: 00:53:33.840: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 364s (process:1898): libfprint-SSM-DEBUG: 00:53:33.840: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 364s (process:1898): libfprint-synaptics-DEBUG: 00:53:33.841: Enrollment is 87 % 364s (process:1898): libfprint-device-DEBUG: 00:53:33.841: Device reported enroll progress, reported 7 of 8 have been completed 364s (process:1898): libfprint-SSM-DEBUG: 00:53:33.841: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 364s (process:1898): libfprint-synaptics-DEBUG: 00:53:33.842: interrupt transfer done 364s (process:1898): libfprint-SSM-DEBUG: 00:53:33.842: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 364s (process:1898): libfprint-SSM-DEBUG: 00:53:33.842: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 364s (process:1898): libfprint-SSM-DEBUG: 00:53:33.842: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 364s (process:1898): libfprint-SSM-DEBUG: 00:53:33.842: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 364s (process:1898): libfprint-device-DEBUG: 00:53:33.843: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 364s (process:1898): libfprint-synaptics-DEBUG: 00:53:33.843: Finger is now on the sensor 364s (process:1898): libfprint-synaptics-DEBUG: 00:53:33.843: Received message with 0 sequence number 0x91, ignoring! 364s (process:1898): libfprint-SSM-DEBUG: 00:53:33.843: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 364s (process:1898): libfprint-synaptics-DEBUG: 00:53:33.843: interrupt transfer done 364s (process:1898): libfprint-SSM-DEBUG: 00:53:33.843: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 364s (process:1898): libfprint-SSM-DEBUG: 00:53:33.844: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 364s (process:1898): libfprint-SSM-DEBUG: 00:53:33.844: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 364s (process:1898): libfprint-SSM-DEBUG: 00:53:33.844: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 364s (process:1898): libfprint-synaptics-DEBUG: 00:53:33.844: Fingerprint image capture complete! 364s (process:1898): libfprint-SSM-DEBUG: 00:53:33.844: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 364s (process:1898): libfprint-synaptics-DEBUG: 00:53:33.845: interrupt transfer done 364s (process:1898): libfprint-SSM-DEBUG: 00:53:33.845: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 364s (process:1898): libfprint-SSM-DEBUG: 00:53:33.845: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 364s (process:1898): libfprint-SSM-DEBUG: 00:53:33.845: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 364s (process:1898): libfprint-SSM-DEBUG: 00:53:33.845: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 364s (process:1898): libfprint-device-DEBUG: 00:53:33.846: Device reported finger status change: FP_FINGER_STATUS_NEEDED 364s (process:1898): libfprint-synaptics-DEBUG: 00:53:33.846: Finger is now off the sensor 364s (process:1898): libfprint-synaptics-DEBUG: 00:53:33.846: Received message with 0 sequence number 0x91, ignoring! 364s (process:1898): libfprint-SSM-DEBUG: 00:53:33.846: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 364s (process:1898): libfprint-synaptics-DEBUG: 00:53:33.846: interrupt transfer done 364s (process:1898): libfprint-SSM-DEBUG: 00:53:33.846: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 364s (process:1898): libfprint-SSM-DEBUG: 00:53:33.847: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 364s (process:1898): libfprint-SSM-DEBUG: 00:53:33.847: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 364s (process:1898): libfprint-SSM-DEBUG: 00:53:33.847: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 364s (process:1898): libfprint-synaptics-DEBUG: 00:53:33.847: Enrollment is 100 % 364s (process:1898): libfprint-device-DEBUG: 00:53:33.847: Device reported enroll progress, reported 8 of 8 have been completed 364s (process:1898): libfprint-SSM-DEBUG: 00:53:33.847: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 364s (process:1898): libfprint-synaptics-DEBUG: 00:53:33.848: interrupt transfer done 364s (process:1898): libfprint-SSM-DEBUG: 00:53:33.848: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 364s (process:1898): libfprint-SSM-DEBUG: 00:53:33.848: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 364s (process:1898): libfprint-SSM-DEBUG: 00:53:33.848: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 364s (process:1898): libfprint-SSM-DEBUG: 00:53:33.848: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 364s (process:1898): libfprint-device-DEBUG: 00:53:33.849: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 364s (process:1898): libfprint-synaptics-DEBUG: 00:53:33.849: Finger is now on the sensor 364s (process:1898): libfprint-synaptics-DEBUG: 00:53:33.849: Received message with 0 sequence number 0x91, ignoring! 364s (process:1898): libfprint-SSM-DEBUG: 00:53:33.849: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 364s (process:1898): libfprint-synaptics-DEBUG: 00:53:33.849: interrupt transfer done 364s (process:1898): libfprint-SSM-DEBUG: 00:53:33.849: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 364s (process:1898): libfprint-SSM-DEBUG: 00:53:33.850: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 364s (process:1898): libfprint-SSM-DEBUG: 00:53:33.850: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 364s (process:1898): libfprint-SSM-DEBUG: 00:53:33.850: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 364s (process:1898): libfprint-device-DEBUG: 00:53:33.850: Device reported finger status change: FP_FINGER_STATUS_NEEDED 364s (process:1898): libfprint-synaptics-DEBUG: 00:53:33.850: Finger is now off the sensor 364s (process:1898): libfprint-synaptics-DEBUG: 00:53:33.850: Received message with 0 sequence number 0x91, ignoring! 364s (process:1898): libfprint-SSM-DEBUG: 00:53:33.850: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 364s (process:1898): libfprint-synaptics-DEBUG: 00:53:33.851: interrupt transfer done 364s (process:1898): libfprint-SSM-DEBUG: 00:53:33.851: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 364s (process:1898): libfprint-SSM-DEBUG: 00:53:33.852: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 364s (process:1898): libfprint-SSM-DEBUG: 00:53:33.852: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 364s (process:1898): libfprint-SSM-DEBUG: 00:53:33.852: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 364s (process:1898): libfprint-synaptics-DEBUG: 00:53:33.852: Enrollment was successful! 364s (process:1898): libfprint-device-DEBUG: 00:53:33.852: Device reported enroll completion 364s (process:1898): libfprint-device-DEBUG: 00:53:33.852: Device reported finger status change: FP_FINGER_STATUS_NONE 364s (process:1898): libfprint-device-DEBUG: 00:53:33.852: Print for finger FP_FINGER_UNKNOWN enrolled 364s (process:1898): libfprint-SSM-DEBUG: 00:53:33.852: [synaptics] SYNAPTICS_CMD_NUM_STATES completed successfully 364s (process:1898): libfprint-device-DEBUG: 00:53:33.852: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 364s (process:1898): libfprint-device-DEBUG: 00:53:33.852: Not updating temperature model, device can run continuously! 364s (process:1898): libfprint-device-DEBUG: 00:53:33.853: Not updating temperature model, device can run continuously! 364s (process:1898): libfprint-synaptics-DEBUG: 00:53:33.853: data is 0xec57b0 364s (process:1898): libfprint-synaptics-DEBUG: 00:53:33.853: 7399781914541: ../libfprint/drivers/synaptics/synaptics.c:646 364s (process:1898): libfprint-synaptics-DEBUG: 00:53:33.853: sequence number is 5 364s (process:1898): libfprint-SSM-DEBUG: 00:53:33.853: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 364s (process:1898): libfprint-SSM-DEBUG: 00:53:33.854: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 364s (process:1898): libfprint-device-DEBUG: 00:53:33.854: Device reported finger status change: FP_FINGER_STATUS_NEEDED 364s (process:1898): libfprint-synaptics-DEBUG: 00:53:33.854: Place Finger on the Sensor! 364s (process:1898): libfprint-SSM-DEBUG: 00:53:33.854: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 364s (process:1898): libfprint-synaptics-DEBUG: 00:53:33.854: got suspend request 364s (process:1898): libfprint-synaptics-DEBUG: 00:53:33.855: interrupt transfer done 364s (process:1898): libfprint-SSM-DEBUG: 00:53:33.855: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 5 364s (process:1898): libfprint-synaptics-DEBUG: 00:53:33.856: got resume request 364s (process:1898): libfprint-SSM-DEBUG: 00:53:33.856: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 6 364s (process:1898): libfprint-SSM-DEBUG: 00:53:33.856: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 364s (process:1898): libfprint-synaptics-DEBUG: 00:53:33.857: interrupt transfer done 364s (process:1898): libfprint-SSM-DEBUG: 00:53:33.857: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 364s (process:1898): libfprint-SSM-DEBUG: 00:53:33.858: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 364s (process:1898): libfprint-SSM-DEBUG: 00:53:33.858: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 364s (process:1898): libfprint-SSM-DEBUG: 00:53:33.858: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 364s (process:1898): libfprint-device-DEBUG: 00:53:33.858: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 364s (process:1898): libfprint-synaptics-DEBUG: 00:53:33.858: Finger is now on the sensor 364s (process:1898): libfprint-synaptics-DEBUG: 00:53:33.858: Received message with 0 sequence number 0x91, ignoring! 364s (process:1898): libfprint-SSM-DEBUG: 00:53:33.858: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 364s (process:1898): libfprint-synaptics-DEBUG: 00:53:33.859: interrupt transfer done 364s (process:1898): libfprint-SSM-DEBUG: 00:53:33.859: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 364s (process:1898): libfprint-SSM-DEBUG: 00:53:33.860: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 364s (process:1898): libfprint-SSM-DEBUG: 00:53:33.860: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 364s (process:1898): libfprint-SSM-DEBUG: 00:53:33.860: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 364s (process:1898): libfprint-synaptics-DEBUG: 00:53:33.860: Fingerprint image capture complete! 364s (process:1898): libfprint-SSM-DEBUG: 00:53:33.860: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 364s (process:1898): libfprint-synaptics-DEBUG: 00:53:33.861: interrupt transfer done 364s (process:1898): libfprint-SSM-DEBUG: 00:53:33.861: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 364s (process:1898): libfprint-SSM-DEBUG: 00:53:33.861: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 364s (process:1898): libfprint-SSM-DEBUG: 00:53:33.861: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 364s (process:1898): libfprint-SSM-DEBUG: 00:53:33.861: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 364s (process:1898): libfprint-device-DEBUG: 00:53:33.862: Device reported finger status change: FP_FINGER_STATUS_NEEDED 364s (process:1898): libfprint-synaptics-DEBUG: 00:53:33.862: Finger is now off the sensor 364s (process:1898): libfprint-synaptics-DEBUG: 00:53:33.862: Received message with 0 sequence number 0x91, ignoring! 364s (process:1898): libfprint-SSM-DEBUG: 00:53:33.862: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 364s (process:1898): libfprint-synaptics-DEBUG: 00:53:33.862: interrupt transfer done 364s (process:1898): libfprint-SSM-DEBUG: 00:53:33.862: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 364s (process:1898): libfprint-SSM-DEBUG: 00:53:33.863: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 364s (process:1898): libfprint-SSM-DEBUG: 00:53:33.863: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 364s (process:1898): libfprint-SSM-DEBUG: 00:53:33.863: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 364s (process:1898): libfprint-synaptics-DEBUG: 00:53:33.863: Verify was successful! for user: FP1-00000000-0-00000000-nobody finger: 1 score: 61.800000 364s (process:1898): libfprint-device-DEBUG: 00:53:33.863: Device reported verify result 364s (process:1898): libfprint-device-DEBUG: 00:53:33.863: Device reported verify completion 364s (process:1898): libfprint-device-DEBUG: 00:53:33.863: Device reported finger status change: FP_FINGER_STATUS_NONE 364s (process:1898): libfprint-SSM-DEBUG: 00:53:33.863: [synaptics] SYNAPTICS_CMD_NUM_STATES completed successfully 364s (process:1898): libfprint-device-DEBUG: 00:53:33.863: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 364s (process:1898): libfprint-device-DEBUG: 00:53:33.863: Not updating temperature model, device can run continuously! 364s (process:1898): libfprint-synaptics-DEBUG: 00:53:33.863: data is 0xec57b0 364s (process:1898): libfprint-synaptics-DEBUG: 00:53:33.863: 7399781924807: ../libfprint/drivers/synaptics/synaptics.c:1123 364s (process:1898): libfprint-synaptics-DEBUG: 00:53:33.863: sequence number is 6 364s (process:1898): libfprint-SSM-DEBUG: 00:53:33.863: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 364s (process:1898): libfprint-SSM-DEBUG: 00:53:33.864: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 364s (process:1898): libfprint-synaptics-DEBUG: 00:53:33.864: Successfully deleted enrolled user 364s (process:1898): libfprint-device-DEBUG: 00:53:33.864: Device reported deletion completion 364s (process:1898): libfprint-SSM-DEBUG: 00:53:33.864: [synaptics] SYNAPTICS_CMD_NUM_STATES completed successfully 364s (process:1898): libfprint-device-DEBUG: 00:53:33.864: Completing action FPI_DEVICE_ACTION_DELETE in idle! 364s (process:1898): libfprint-device-DEBUG: 00:53:33.864: Not updating temperature model, device can run continuously! 364s (process:1898): libfprint-synaptics-DEBUG: 00:53:33.864: 7399781925847: ../libfprint/drivers/synaptics/synaptics.c:1424 364s (process:1898): libfprint-synaptics-DEBUG: 00:53:33.864: sequence number is 7 364s (process:1898): libfprint-SSM-DEBUG: 00:53:33.864: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 364s (process:1898): libfprint-SSM-DEBUG: 00:53:33.865: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 364s (process:1898): libfprint-synaptics-DEBUG: 00:53:33.866: Fingerprint sensor ready to be powered down 364s (process:1898): libfprint-device-DEBUG: 00:53:33.866: Device reported close completion 364s (process:1898): libfprint-SSM-DEBUG: 00:53:33.866: [synaptics] SYNAPTICS_CMD_NUM_STATES completed successfully 364s (process:1898): libfprint-device-DEBUG: 00:53:33.866: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 364s (process:1898): libfprint-device-DEBUG: 00:53:33.866: Not updating temperature model, device can run continuously! 364s enrolling 364s enroll progress: (<__gi__.FpiDeviceSynaptics object at 0xf57af0e8 (FpiDeviceSynaptics at 0xdc4638)>, 1, None, None, None) 364s enroll progress: (<__gi__.FpiDeviceSynaptics object at 0xf57af0e8 (FpiDeviceSynaptics at 0xdc4638)>, 2, None, None, None) 364s enroll progress: (<__gi__.FpiDeviceSynaptics object at 0xf57af0e8 (FpiDeviceSynaptics at 0xdc4638)>, 3, None, None, None) 364s enroll progress: (<__gi__.FpiDeviceSynaptics object at 0xf57af0e8 (FpiDeviceSynaptics at 0xdc4638)>, 4, None, None, None) 364s enroll progress: (<__gi__.FpiDeviceSynaptics object at 0xf57af0e8 (FpiDeviceSynaptics at 0xdc4638)>, 5, None, None, None) 364s enroll progress: (<__gi__.FpiDeviceSynaptics object at 0xf57af0e8 (FpiDeviceSynaptics at 0xdc4638)>, 5, None, None, GLib.Error('Please try again.', 'fp - device - retry - quark', 0)) 364s enroll progress: (<__gi__.FpiDeviceSynaptics object at 0xf57af0e8 (FpiDeviceSynaptics at 0xdc4638)>, 6, None, None, None) 364s enroll progress: (<__gi__.FpiDeviceSynaptics object at 0xf57af0e8 (FpiDeviceSynaptics at 0xdc4638)>, 7, None, None, None) 364s enroll progress: (<__gi__.FpiDeviceSynaptics object at 0xf57af0e8 (FpiDeviceSynaptics at 0xdc4638)>, 8, None, None, None) 364s enroll done 364s verifying 364s verify done 364s deleting 364s delete done 364s libusb: warning [libusb_exit] device 1.1 still referenced 364s ** (umockdev-run:1894): DEBUG: 00:53:33.892: umockdev.vala:154: Removing test bed /tmp/umockdev.4P7B22 364s (umockdev-run:1894): GLib-DEBUG: 00:53:33.898: unsetenv() is not thread-safe and should not be used after threads are created 364s PASS: libfprint-2/driver-synaptics.test 364s Running test: libfprint-2/virtual-device.test 365s (process:1904): libfprint-context-DEBUG: 00:53:34.043: Initializing FpContext (libfprint version 1.94.8+tod1) 365s (process:1904): libfprint-tod-DEBUG: 00:53:34.043: Impossible to load the shared drivers dir Error opening directory “/usr/lib/arm-linux-gnueabihf/libfprint-2/tod-1”: No such file or directory 365s (process:1904): libfprint-context-DEBUG: 00:53:34.046: No driver found for USB device 1D6B:0003 365s (process:1904): libfprint-context-DEBUG: 00:53:34.046: No driver found for USB device 0627:0001 365s (process:1904): libfprint-context-DEBUG: 00:53:34.046: No driver found for USB device 1D6B:0002 365s (process:1904): libfprint-context-DEBUG: 00:53:34.046: Found virtual environment device: FP_VIRTUAL_DEVICE, /tmp/libfprint-btdgcgun/virtual-device.socket 365s (process:1904): libfprint-context-DEBUG: 00:53:34.047: created 365s (process:1904): libfprint-device-DEBUG: 00:53:34.048: Device reported probe completion 365s (process:1904): libfprint-device-DEBUG: 00:53:34.048: Completing action FPI_DEVICE_ACTION_PROBE in idle! 365s (process:1904): libfprint-device-DEBUG: 00:53:34.048: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 365s test_capture_unsupported (__main__.VirtualDevice.test_capture_unsupported) ... (process:1904): libfprint-virtual_device-DEBUG: 00:53:34.048: 7399782109637: ../libfprint/drivers/virtual-device.c:387 365s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:34.048: 7399782109730: ../libfprint/drivers/virtual-device-listener.c:153 365s (process:1904): libfprint-device-DEBUG: 00:53:34.049: Device reported open completion 365s (process:1904): libfprint-device-DEBUG: 00:53:34.049: Completing action FPI_DEVICE_ACTION_OPEN in idle! 365s (process:1904): libfprint-device-DEBUG: 00:53:34.049: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 365s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:34.049: Got a new connection! 365s (process:1904): libfprint-virtual_device-DEBUG: 00:53:34.049: Got instructions of length 16 365s (process:1904): libfprint-virtual_device-DEBUG: 00:53:34.050: Received command SET_KEEP_ALIVE 0 365s (process:1904): libfprint-virtual_device-DEBUG: 00:53:34.050: Keep alive toggled: 0 365s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:34.050: Got a new connection! 365s (process:1904): libfprint-virtual_device-DEBUG: 00:53:34.050: Got instructions of length 19 365s (process:1904): libfprint-virtual_device-DEBUG: 00:53:34.050: Received command SET_ENROLL_STAGES 5 365s (process:1904): libfprint-device-DEBUG: 00:53:34.050: Device reported close completion 365s (process:1904): libfprint-device-DEBUG: 00:53:34.050: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 365s (process:1904): libfprint-device-DEBUG: 00:53:34.050: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 365s ok 365s test_change_enroll_stages (__main__.VirtualDevice.test_change_enroll_stages) ... (process:1904): libfprint-virtual_device-DEBUG: 00:53:34.050: 7399782111532: ../libfprint/drivers/virtual-device.c:387 365s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:34.050: 7399782111546: ../libfprint/drivers/virtual-device-listener.c:153 365s (process:1904): libfprint-device-DEBUG: 00:53:34.050: Device reported open completion 365s (process:1904): libfprint-device-DEBUG: 00:53:34.050: Completing action FPI_DEVICE_ACTION_OPEN in idle! 365s (process:1904): libfprint-device-DEBUG: 00:53:34.050: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 365s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:34.051: Got a new connection! 365s (process:1904): libfprint-virtual_device-DEBUG: 00:53:34.051: Got instructions of length 20 365s (process:1904): libfprint-virtual_device-DEBUG: 00:53:34.051: Received command SET_ENROLL_STAGES 20 365s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:34.051: Got a new connection! 365s (process:1904): libfprint-virtual_device-DEBUG: 00:53:34.051: Got instructions of length 19 365s (process:1904): libfprint-virtual_device-DEBUG: 00:53:34.051: Received command SET_ENROLL_STAGES 1 365s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:34.051: Got a new connection! 365s (process:1904): libfprint-virtual_device-DEBUG: 00:53:34.052: Got instructions of length 19 365s (process:1904): libfprint-virtual_device-DEBUG: 00:53:34.052: Received command SET_ENROLL_STAGES 0 365s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:34.053: Got a new connection! 365s (process:1904): libfprint-virtual_device-DEBUG: 00:53:34.053: Got instructions of length 16 365s (process:1904): libfprint-virtual_device-DEBUG: 00:53:34.053: Received command SET_KEEP_ALIVE 0 365s (process:1904): libfprint-virtual_device-DEBUG: 00:53:34.053: Keep alive toggled: 0 365s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:34.053: Got a new connection! 365s (process:1904): libfprint-virtual_device-DEBUG: 00:53:34.053: Got instructions of length 19 365s (process:1904): libfprint-virtual_device-DEBUG: 00:53:34.053: Received command SET_ENROLL_STAGES 5 365s (process:1904): libfprint-device-DEBUG: 00:53:34.053: Device reported close completion 365s (process:1904): libfprint-device-DEBUG: 00:53:34.053: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 365s (process:1904): libfprint-device-DEBUG: 00:53:34.053: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 365s ok 365s test_change_scan_type (__main__.VirtualDevice.test_change_scan_type) ... (process:1904): libfprint-virtual_device-DEBUG: 00:53:34.054: 7399782115062: ../libfprint/drivers/virtual-device.c:387 365s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:34.054: 7399782115079: ../libfprint/drivers/virtual-device-listener.c:153 365s (process:1904): libfprint-device-DEBUG: 00:53:34.054: Device reported open completion 365s (process:1904): libfprint-device-DEBUG: 00:53:34.054: Completing action FPI_DEVICE_ACTION_OPEN in idle! 365s (process:1904): libfprint-device-DEBUG: 00:53:34.054: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 365s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:34.054: Got a new connection! 365s (process:1904): libfprint-virtual_device-DEBUG: 00:53:34.054: Got instructions of length 19 365s (process:1904): libfprint-virtual_device-DEBUG: 00:53:34.054: Received command SET_SCAN_TYPE press 365s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:34.055: Got a new connection! 365s (process:1904): libfprint-virtual_device-DEBUG: 00:53:34.055: Got instructions of length 19 365s (process:1904): libfprint-virtual_device-DEBUG: 00:53:34.055: Received command SET_SCAN_TYPE swipe 365s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:34.055: Got a new connection! 365s (process:1904): libfprint-virtual_device-DEBUG: 00:53:34.055: Got instructions of length 25 365s (process:1904): libfprint-virtual_device-DEBUG: 00:53:34.055: Received command SET_SCAN_TYPE eye-contact 365s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:34.055: Got a new connection! 365s (process:1904): libfprint-virtual_device-DEBUG: 00:53:34.056: Got instructions of length 16 365s (process:1904): libfprint-virtual_device-DEBUG: 00:53:34.056: Received command SET_KEEP_ALIVE 0 365s (process:1904): libfprint-virtual_device-DEBUG: 00:53:34.056: Keep alive toggled: 0 365s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:34.056: Got a new connection! 365s (process:1904): libfprint-virtual_device-DEBUG: 00:53:34.056: Got instructions of length 19 365s (process:1904): libfprint-virtual_device-DEBUG: 00:53:34.056: Received command SET_ENROLL_STAGES 5 365s (process:1904): libfprint-device-DEBUG: 00:53:34.056: Device reported close completion 365s (process:1904): libfprint-device-DEBUG: 00:53:34.056: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 365s (process:1904): libfprint-device-DEBUG: 00:53:34.056: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 365s ok 365s test_close_error (__main__.VirtualDevice.test_close_error) ... (process:1904): libfprint-virtual_device-DEBUG: 00:53:34.056: 7399782117404: ../libfprint/drivers/virtual-device.c:387 365s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:34.056: 7399782117421: ../libfprint/drivers/virtual-device-listener.c:153 365s (process:1904): libfprint-device-DEBUG: 00:53:34.056: Device reported open completion 365s (process:1904): libfprint-device-DEBUG: 00:53:34.056: Completing action FPI_DEVICE_ACTION_OPEN in idle! 365s (process:1904): libfprint-device-DEBUG: 00:53:34.056: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 365s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:34.056: Got a new connection! 365s (process:1904): libfprint-virtual_device-DEBUG: 00:53:34.056: Got instructions of length 9 365s (process:1904): libfprint-virtual_device-DEBUG: 00:53:34.056: Received command SLEEP 100 365s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:34.057: Got a new connection! 365s (process:1904): libfprint-virtual_device-DEBUG: 00:53:34.057: Got instructions of length 7 365s (process:1904): libfprint-virtual_device-DEBUG: 00:53:34.057: Received command ERROR 4 365s (process:1904): libfprint-virtual_device-DEBUG: 00:53:34.057: Processing command SLEEP 100 365s (process:1904): libfprint-virtual_device-DEBUG: 00:53:34.057: Sleeping 100ms 365s (process:1904): libfprint-virtual_device-DEBUG: 00:53:34.157: Sleeping completed 365s (process:1904): libfprint-virtual_device-DEBUG: 00:53:34.157: Processing command ERROR 4 365s (process:1904): libfprint-device-DEBUG: 00:53:34.157: Device reported close completion 365s (process:1904): libfprint-device-DEBUG: 00:53:34.158: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 365s (process:1904): libfprint-device-DEBUG: 00:53:34.158: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 365s ok 365s test_close_while_opening (__main__.VirtualDevice.test_close_while_opening) ... (process:1904): libfprint-virtual_device-DEBUG: 00:53:34.158: 7399782219689: ../libfprint/drivers/virtual-device.c:387 365s (process:1904): libfprint-device-DEBUG: 00:53:34.158: Device reported open completion 365s (process:1904): libfprint-device-DEBUG: 00:53:34.158: Completing action FPI_DEVICE_ACTION_OPEN in idle! 365s (process:1904): libfprint-device-DEBUG: 00:53:34.158: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 365s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:34.159: Got a new connection! 365s (process:1904): libfprint-virtual_device-DEBUG: 00:53:34.159: Got instructions of length 16 365s (process:1904): libfprint-virtual_device-DEBUG: 00:53:34.159: Received command SET_KEEP_ALIVE 1 365s (process:1904): libfprint-virtual_device-DEBUG: 00:53:34.159: Keep alive toggled: 1 365s (process:1904): libfprint-device-DEBUG: 00:53:34.159: Device reported close completion 365s (process:1904): libfprint-device-DEBUG: 00:53:34.159: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 365s (process:1904): libfprint-device-DEBUG: 00:53:34.159: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 365s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:34.159: Got a new connection! 365s (process:1904): libfprint-virtual_device-DEBUG: 00:53:34.159: Got instructions of length 9 365s (process:1904): libfprint-virtual_device-DEBUG: 00:53:34.159: Received command SLEEP 500 365s (process:1904): libfprint-virtual_device-DEBUG: 00:53:34.159: 7399782220516: ../libfprint/drivers/virtual-device.c:387 365s (process:1904): libfprint-virtual_device-DEBUG: 00:53:34.159: Processing command SLEEP 500 365s (process:1904): libfprint-virtual_device-DEBUG: 00:53:34.159: Sleeping 500ms 365s (process:1904): libfprint-virtual_device-DEBUG: 00:53:34.660: Sleeping completed 365s (process:1904): libfprint-virtual_device-DEBUG: 00:53:34.660: 7399782721292: ../libfprint/drivers/virtual-device.c:387 365s (process:1904): libfprint-device-DEBUG: 00:53:34.660: Device reported open completion 365s (process:1904): libfprint-device-DEBUG: 00:53:34.660: Completing action FPI_DEVICE_ACTION_OPEN in idle! 365s (process:1904): libfprint-device-DEBUG: 00:53:34.660: Updated temperature model after 0.50 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 365s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:34.660: Got a new connection! 365s (process:1904): libfprint-virtual_device-DEBUG: 00:53:34.661: Got instructions of length 16 365s (process:1904): libfprint-virtual_device-DEBUG: 00:53:34.661: Received command SET_KEEP_ALIVE 0 365s (process:1904): libfprint-virtual_device-DEBUG: 00:53:34.661: Keep alive toggled: 0 365s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:34.661: Got a new connection! 365s (process:1904): libfprint-virtual_device-DEBUG: 00:53:34.661: Got instructions of length 19 365s (process:1904): libfprint-virtual_device-DEBUG: 00:53:34.661: Received command SET_ENROLL_STAGES 5 365s (process:1904): libfprint-device-DEBUG: 00:53:34.661: Device reported close completion 365s (process:1904): libfprint-device-DEBUG: 00:53:34.661: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 365s (process:1904): libfprint-device-DEBUG: 00:53:34.661: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 365s ok 365s test_delayed_open (__main__.VirtualDevice.test_delayed_open) ... (process:1904): libfprint-virtual_device-DEBUG: 00:53:34.661: 7399782722830: ../libfprint/drivers/virtual-device.c:387 365s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:34.661: 7399782722842: ../libfprint/drivers/virtual-device-listener.c:153 365s (process:1904): libfprint-device-DEBUG: 00:53:34.662: Device reported open completion 365s (process:1904): libfprint-device-DEBUG: 00:53:34.662: Completing action FPI_DEVICE_ACTION_OPEN in idle! 365s (process:1904): libfprint-device-DEBUG: 00:53:34.662: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 365s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:34.662: Got a new connection! 365s (process:1904): libfprint-virtual_device-DEBUG: 00:53:34.662: Got instructions of length 16 365s (process:1904): libfprint-virtual_device-DEBUG: 00:53:34.662: Received command IGNORED_COMMAND 365s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:34.662: Got a new connection! 365s (process:1904): libfprint-virtual_device-DEBUG: 00:53:34.662: Got instructions of length 9 365s (process:1904): libfprint-virtual_device-DEBUG: 00:53:34.662: Received command SLEEP 500 365s (process:1904): libfprint-virtual_device-DEBUG: 00:53:34.662: Processing command IGNORED_COMMAND 365s (process:1904): libfprint-device-DEBUG: 00:53:34.663: Device reported close completion 365s (process:1904): libfprint-device-DEBUG: 00:53:34.663: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 365s (process:1904): libfprint-device-DEBUG: 00:53:34.663: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 365s (process:1904): libfprint-virtual_device-DEBUG: 00:53:34.663: 7399782724292: ../libfprint/drivers/virtual-device.c:387 365s (process:1904): libfprint-virtual_device-DEBUG: 00:53:34.663: Processing command SLEEP 500 365s (process:1904): libfprint-virtual_device-DEBUG: 00:53:34.663: Sleeping 500ms 366s (process:1904): libfprint-virtual_device-DEBUG: 00:53:35.164: Sleeping completed 366s (process:1904): libfprint-virtual_device-DEBUG: 00:53:35.164: 7399783225076: ../libfprint/drivers/virtual-device.c:387 366s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:35.164: 7399783225094: ../libfprint/drivers/virtual-device-listener.c:153 366s (process:1904): libfprint-device-DEBUG: 00:53:35.164: Device reported open completion 366s (process:1904): libfprint-device-DEBUG: 00:53:35.164: Completing action FPI_DEVICE_ACTION_OPEN in idle! 366s (process:1904): libfprint-device-DEBUG: 00:53:35.164: Updated temperature model after 0.50 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 366s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:35.164: Got a new connection! 366s (process:1904): libfprint-virtual_device-DEBUG: 00:53:35.164: Got instructions of length 16 366s (process:1904): libfprint-virtual_device-DEBUG: 00:53:35.164: Received command SET_KEEP_ALIVE 0 366s (process:1904): libfprint-virtual_device-DEBUG: 00:53:35.164: Keep alive toggled: 0 366s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:35.165: Got a new connection! 366s (process:1904): libfprint-virtual_device-DEBUG: 00:53:35.165: Got instructions of length 19 366s (process:1904): libfprint-virtual_device-DEBUG: 00:53:35.165: Received command SET_ENROLL_STAGES 5 366s (process:1904): libfprint-device-DEBUG: 00:53:35.165: Device reported close completion 366s (process:1904): libfprint-device-DEBUG: 00:53:35.165: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 366s (process:1904): libfprint-device-DEBUG: 00:53:35.165: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 366s ok 366s test_delayed_open_with_keep_alive (__main__.VirtualDevice.test_delayed_open_with_keep_alive) ... (process:1904): libfprint-virtual_device-DEBUG: 00:53:35.165: 7399783226500: ../libfprint/drivers/virtual-device.c:387 366s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:35.165: 7399783226516: ../libfprint/drivers/virtual-device-listener.c:153 366s (process:1904): libfprint-device-DEBUG: 00:53:35.165: Device reported open completion 366s (process:1904): libfprint-device-DEBUG: 00:53:35.165: Completing action FPI_DEVICE_ACTION_OPEN in idle! 366s (process:1904): libfprint-device-DEBUG: 00:53:35.165: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 366s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:35.166: Got a new connection! 366s (process:1904): libfprint-virtual_device-DEBUG: 00:53:35.166: Got instructions of length 16 366s (process:1904): libfprint-virtual_device-DEBUG: 00:53:35.166: Received command SET_KEEP_ALIVE 1 366s (process:1904): libfprint-virtual_device-DEBUG: 00:53:35.166: Keep alive toggled: 1 366s (process:1904): libfprint-device-DEBUG: 00:53:35.166: Device reported close completion 366s (process:1904): libfprint-device-DEBUG: 00:53:35.166: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 366s (process:1904): libfprint-device-DEBUG: 00:53:35.166: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 366s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:35.166: Got a new connection! 366s (process:1904): libfprint-virtual_device-DEBUG: 00:53:35.166: Got instructions of length 9 366s (process:1904): libfprint-virtual_device-DEBUG: 00:53:35.166: Received command SLEEP 500 366s (process:1904): libfprint-virtual_device-DEBUG: 00:53:35.166: 7399783227692: ../libfprint/drivers/virtual-device.c:387 366s (process:1904): libfprint-virtual_device-DEBUG: 00:53:35.166: Processing command SLEEP 500 366s (process:1904): libfprint-virtual_device-DEBUG: 00:53:35.166: Sleeping 500ms 366s (process:1904): libfprint-virtual_device-DEBUG: 00:53:35.667: Sleeping completed 366s (process:1904): libfprint-virtual_device-DEBUG: 00:53:35.667: 7399783728381: ../libfprint/drivers/virtual-device.c:387 366s (process:1904): libfprint-device-DEBUG: 00:53:35.667: Device reported open completion 366s (process:1904): libfprint-device-DEBUG: 00:53:35.667: Completing action FPI_DEVICE_ACTION_OPEN in idle! 366s (process:1904): libfprint-device-DEBUG: 00:53:35.667: Updated temperature model after 0.50 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 366s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:35.667: Got a new connection! 366s (process:1904): libfprint-virtual_device-DEBUG: 00:53:35.667: Got instructions of length 16 366s (process:1904): libfprint-virtual_device-DEBUG: 00:53:35.667: Received command SET_KEEP_ALIVE 0 366s (process:1904): libfprint-virtual_device-DEBUG: 00:53:35.667: Keep alive toggled: 0 366s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:35.668: Got a new connection! 366s (process:1904): libfprint-virtual_device-DEBUG: 00:53:35.668: Got instructions of length 19 366s (process:1904): libfprint-virtual_device-DEBUG: 00:53:35.668: Received command SET_ENROLL_STAGES 5 366s (process:1904): libfprint-device-DEBUG: 00:53:35.668: Device reported close completion 366s (process:1904): libfprint-device-DEBUG: 00:53:35.668: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 366s (process:1904): libfprint-device-DEBUG: 00:53:35.668: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 366s ok 366s test_device_features (__main__.VirtualDevice.test_device_features) ... (process:1904): libfprint-virtual_device-DEBUG: 00:53:35.668: 7399783729272: ../libfprint/drivers/virtual-device.c:387 366s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:35.668: 7399783729287: ../libfprint/drivers/virtual-device-listener.c:153 366s (process:1904): libfprint-device-DEBUG: 00:53:35.668: Device reported open completion 366s (process:1904): libfprint-device-DEBUG: 00:53:35.668: Completing action FPI_DEVICE_ACTION_OPEN in idle! 366s (process:1904): libfprint-device-DEBUG: 00:53:35.668: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 366s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:35.668: Got a new connection! 366s (process:1904): libfprint-virtual_device-DEBUG: 00:53:35.669: Got instructions of length 16 366s (process:1904): libfprint-virtual_device-DEBUG: 00:53:35.669: Received command SET_KEEP_ALIVE 0 366s (process:1904): libfprint-virtual_device-DEBUG: 00:53:35.669: Keep alive toggled: 0 366s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:35.669: Got a new connection! 366s (process:1904): libfprint-virtual_device-DEBUG: 00:53:35.669: Got instructions of length 19 366s (process:1904): libfprint-virtual_device-DEBUG: 00:53:35.669: Received command SET_ENROLL_STAGES 5 366s (process:1904): libfprint-device-DEBUG: 00:53:35.669: Device reported close completion 366s (process:1904): libfprint-device-DEBUG: 00:53:35.669: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 366s (process:1904): libfprint-device-DEBUG: 00:53:35.669: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 366s ok 366s test_device_properties (__main__.VirtualDevice.test_device_properties) ... (process:1904): libfprint-virtual_device-DEBUG: 00:53:35.669: 7399783730454: ../libfprint/drivers/virtual-device.c:387 366s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:35.669: 7399783730468: ../libfprint/drivers/virtual-device-listener.c:153 366s (process:1904): libfprint-device-DEBUG: 00:53:35.669: Device reported open completion 366s (process:1904): libfprint-device-DEBUG: 00:53:35.669: Completing action FPI_DEVICE_ACTION_OPEN in idle! 366s (process:1904): libfprint-device-DEBUG: 00:53:35.669: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 366s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:35.670: Got a new connection! 366s (process:1904): libfprint-virtual_device-DEBUG: 00:53:35.670: Got instructions of length 16 366s (process:1904): libfprint-virtual_device-DEBUG: 00:53:35.670: Received command SET_KEEP_ALIVE 0 366s (process:1904): libfprint-virtual_device-DEBUG: 00:53:35.670: Keep alive toggled: 0 366s /usr/libexec/installed-tests/libfprint-2/virtual-device.py:463: DeprecationWarning: FPrint.Device.supports_identify is deprecated 366s self.assertFalse(self.dev.supports_identify()) 366s /usr/libexec/installed-tests/libfprint-2/virtual-device.py:464: DeprecationWarning: FPrint.Device.supports_capture is deprecated 366s self.assertFalse(self.dev.supports_capture()) 366s /usr/libexec/installed-tests/libfprint-2/virtual-device.py:465: DeprecationWarning: FPrint.Device.has_storage is deprecated 366s self.assertFalse(self.dev.has_storage()) 366s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:35.670: Got a new connection! 366s (process:1904): libfprint-virtual_device-DEBUG: 00:53:35.670: Got instructions of length 19 366s (process:1904): libfprint-virtual_device-DEBUG: 00:53:35.670: Received command SET_ENROLL_STAGES 5 366s (process:1904): libfprint-device-DEBUG: 00:53:35.670: Device reported close completion 366s (process:1904): libfprint-device-DEBUG: 00:53:35.670: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 366s (process:1904): libfprint-device-DEBUG: 00:53:35.670: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 366s ok 366s test_device_sleep (__main__.VirtualDevice.test_device_sleep) ... (process:1904): libfprint-virtual_device-DEBUG: 00:53:35.670: 7399783731625: ../libfprint/drivers/virtual-device.c:387 366s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:35.670: 7399783731639: ../libfprint/drivers/virtual-device-listener.c:153 366s (process:1904): libfprint-device-DEBUG: 00:53:35.670: Device reported open completion 366s (process:1904): libfprint-device-DEBUG: 00:53:35.670: Completing action FPI_DEVICE_ACTION_OPEN in idle! 366s (process:1904): libfprint-device-DEBUG: 00:53:35.670: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 366s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:35.671: Got a new connection! 366s (process:1904): libfprint-virtual_device-DEBUG: 00:53:35.671: Got instructions of length 10 366s (process:1904): libfprint-virtual_device-DEBUG: 00:53:35.671: Received command SLEEP 1500 366s (process:1904): libfprint-device-DEBUG: 00:53:35.671: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 366s (process:1904): libfprint-virtual_device-DEBUG: 00:53:35.671: Processing command SLEEP 1500 366s (process:1904): libfprint-virtual_device-DEBUG: 00:53:35.671: Sleeping 1500ms 367s (process:1904): libfprint-device-DEBUG: 00:53:35.969: Updated temperature model after 0.30 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 367s (process:1904): libfprint-device-DEBUG: 00:53:35.971: Idle cancelling on ongoing operation! 367s (process:1904): libfprint-virtual_device-DEBUG: 00:53:35.972: Got cancellation! 367s (process:1904): libfprint-device-DEBUG: 00:53:35.972: Device reported finger status change: FP_FINGER_STATUS_NEEDED 367s (process:1904): libfprint-virtual_device-DEBUG: 00:53:35.972: Virtual device scan failed with error: Operation was cancelled 367s (process:1904): libfprint-device-DEBUG: 00:53:35.972: Device reported verify completion 367s (process:1904): libfprint-device-DEBUG: 00:53:35.972: Device reported finger status change: FP_FINGER_STATUS_NONE 367s (process:1904): libfprint-device-DEBUG: 00:53:35.972: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 367s (process:1904): libfprint-device-DEBUG: 00:53:35.972: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 367s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:36.172: Got a new connection! 367s (process:1904): libfprint-virtual_device-DEBUG: 00:53:36.172: Got instructions of length 16 367s (process:1904): libfprint-virtual_device-DEBUG: 00:53:36.172: Received command SET_KEEP_ALIVE 0 367s (process:1904): libfprint-virtual_device-DEBUG: 00:53:36.172: Keep alive toggled: 0 367s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:36.172: Got a new connection! 367s (process:1904): libfprint-virtual_device-DEBUG: 00:53:36.172: Got instructions of length 19 367s (process:1904): libfprint-virtual_device-DEBUG: 00:53:36.172: Received command SET_ENROLL_STAGES 5 367s (process:1904): libfprint-device-DEBUG: 00:53:36.172: Device reported close completion 367s (process:1904): libfprint-device-DEBUG: 00:53:36.172: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 367s (process:1904): libfprint-device-DEBUG: 00:53:36.172: Updated temperature model after 0.20 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 367s ok 367s test_device_sleep_before_completing_verify (__main__.VirtualDevice.test_device_sleep_before_completing_verify) ... (process:1904): libfprint-virtual_device-DEBUG: 00:53:36.172: 7399784233792: ../libfprint/drivers/virtual-device.c:387 367s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:36.172: 7399784233807: ../libfprint/drivers/virtual-device-listener.c:153 367s (process:1904): libfprint-device-DEBUG: 00:53:36.173: Device reported open completion 367s (process:1904): libfprint-device-DEBUG: 00:53:36.173: Completing action FPI_DEVICE_ACTION_OPEN in idle! 367s (process:1904): libfprint-device-DEBUG: 00:53:36.173: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 367s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:36.173: Got a new connection! 367s (process:1904): libfprint-virtual_device-DEBUG: 00:53:36.173: Got instructions of length 14 367s (process:1904): libfprint-virtual_device-DEBUG: 00:53:36.173: Received command SCAN foo-print 367s (process:1904): libfprint-device-DEBUG: 00:53:36.173: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 367s (process:1904): libfprint-virtual_device-DEBUG: 00:53:36.173: Processing command SCAN foo-print 367s (process:1904): libfprint-device-DEBUG: 00:53:36.173: Device reported finger status change: FP_FINGER_STATUS_NEEDED 367s (process:1904): libfprint-device-DEBUG: 00:53:36.173: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 367s (process:1904): libfprint-device-DEBUG: 00:53:36.173: Device reported finger status change: FP_FINGER_STATUS_NEEDED 367s (process:1904): libfprint-device-DEBUG: 00:53:36.173: Device reported enroll progress, reported 1 of 5 have been completed 367s (process:1904): libfprint-virtual_device-DEBUG: 00:53:36.174: Sleeping completed 367s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:36.174: Got a new connection! 367s (process:1904): libfprint-virtual_device-DEBUG: 00:53:36.174: Got instructions of length 14 367s (process:1904): libfprint-virtual_device-DEBUG: 00:53:36.174: Received command SCAN foo-print 367s (process:1904): libfprint-virtual_device-DEBUG: 00:53:36.174: Processing command SCAN foo-print 367s (process:1904): libfprint-device-DEBUG: 00:53:36.174: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 367s (process:1904): libfprint-device-DEBUG: 00:53:36.174: Device reported finger status change: FP_FINGER_STATUS_NEEDED 367s (process:1904): libfprint-device-DEBUG: 00:53:36.174: Device reported enroll progress, reported 2 of 5 have been completed 367s (process:1904): libfprint-virtual_device-DEBUG: 00:53:36.174: Sleeping completed 367s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:36.174: Got a new connection! 367s (process:1904): libfprint-virtual_device-DEBUG: 00:53:36.174: Got instructions of length 14 367s (process:1904): libfprint-virtual_device-DEBUG: 00:53:36.174: Received command SCAN foo-print 367s (process:1904): libfprint-virtual_device-DEBUG: 00:53:36.174: Processing command SCAN foo-print 367s (process:1904): libfprint-device-DEBUG: 00:53:36.174: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 367s (process:1904): libfprint-device-DEBUG: 00:53:36.174: Device reported finger status change: FP_FINGER_STATUS_NEEDED 367s (process:1904): libfprint-device-DEBUG: 00:53:36.174: Device reported enroll progress, reported 3 of 5 have been completed 367s (process:1904): libfprint-virtual_device-DEBUG: 00:53:36.174: Sleeping completed 367s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:36.174: Got a new connection! 367s (process:1904): libfprint-virtual_device-DEBUG: 00:53:36.174: Got instructions of length 14 367s (process:1904): libfprint-virtual_device-DEBUG: 00:53:36.174: Received command SCAN foo-print 367s (process:1904): libfprint-virtual_device-DEBUG: 00:53:36.174: Processing command SCAN foo-print 367s (process:1904): libfprint-device-DEBUG: 00:53:36.174: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 367s (process:1904): libfprint-device-DEBUG: 00:53:36.174: Device reported finger status change: FP_FINGER_STATUS_NEEDED 367s (process:1904): libfprint-device-DEBUG: 00:53:36.174: Device reported enroll progress, reported 4 of 5 have been completed 367s (process:1904): libfprint-virtual_device-DEBUG: 00:53:36.174: Sleeping completed 367s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:36.175: Got a new connection! 367s (process:1904): libfprint-virtual_device-DEBUG: 00:53:36.175: Got instructions of length 14 367s (process:1904): libfprint-virtual_device-DEBUG: 00:53:36.175: Received command SCAN foo-print 367s (process:1904): libfprint-virtual_device-DEBUG: 00:53:36.175: Processing command SCAN foo-print 367s (process:1904): libfprint-device-DEBUG: 00:53:36.175: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 367s (process:1904): libfprint-device-DEBUG: 00:53:36.175: Device reported finger status change: FP_FINGER_STATUS_NEEDED 367s (process:1904): libfprint-device-DEBUG: 00:53:36.175: Device reported enroll progress, reported 5 of 5 have been completed 367s (process:1904): libfprint-device-DEBUG: 00:53:36.175: Device reported enroll completion 367s (process:1904): libfprint-device-DEBUG: 00:53:36.175: Device reported finger status change: FP_FINGER_STATUS_NONE 367s (process:1904): libfprint-device-DEBUG: 00:53:36.175: Print for finger FP_FINGER_LEFT_RING enrolled 367s (process:1904): libfprint-device-DEBUG: 00:53:36.175: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 367s (process:1904): libfprint-device-DEBUG: 00:53:36.175: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 367s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:36.175: Got a new connection! 367s (process:1904): libfprint-virtual_device-DEBUG: 00:53:36.175: Got instructions of length 9 367s (process:1904): libfprint-virtual_device-DEBUG: 00:53:36.175: Received command SLEEP 100 367s (process:1904): libfprint-device-DEBUG: 00:53:36.175: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 367s (process:1904): libfprint-virtual_device-DEBUG: 00:53:36.175: Processing command SLEEP 100 367s (process:1904): libfprint-virtual_device-DEBUG: 00:53:36.175: Sleeping 100ms 367s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:36.175: Got a new connection! 367s (process:1904): libfprint-virtual_device-DEBUG: 00:53:36.176: Got instructions of length 14 367s (process:1904): libfprint-virtual_device-DEBUG: 00:53:36.176: Received command SCAN bar-print 367s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:36.176: Got a new connection! 367s (process:1904): libfprint-virtual_device-DEBUG: 00:53:36.176: Got instructions of length 9 367s (process:1904): libfprint-virtual_device-DEBUG: 00:53:36.176: Received command SLEEP 800 367s (process:1904): libfprint-virtual_device-DEBUG: 00:53:36.275: Sleeping completed 367s (process:1904): libfprint-virtual_device-DEBUG: 00:53:36.275: Processing command SCAN bar-print 367s (process:1904): libfprint-device-DEBUG: 00:53:36.275: Device reported finger status change: FP_FINGER_STATUS_NEEDED 367s (process:1904): libfprint-device-DEBUG: 00:53:36.275: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 367s (process:1904): libfprint-virtual_device-DEBUG: 00:53:36.275: Virtual device scanned print bar-print 367s (process:1904): libfprint-device-DEBUG: 00:53:36.276: Device reported verify result 367s (process:1904): libfprint-device-DEBUG: 00:53:36.276: Device reported finger status change: FP_FINGER_STATUS_NEEDED 367s (process:1904): libfprint-virtual_device-DEBUG: 00:53:36.276: Processing command SLEEP 800 367s (process:1904): libfprint-virtual_device-DEBUG: 00:53:36.276: Sleeping 800ms 367s (process:1904): libfprint-virtual_device-DEBUG: 00:53:36.276: Sleeping now, command queued for later: SCAN bar-print 367s Executing: libfprint-2/virtual-device.test 368s (process:1904): libfprint-virtual_device-DEBUG: 00:53:37.076: Sleeping completed 368s (process:1904): libfprint-virtual_device-DEBUG: 00:53:37.076: Processing command SCAN bar-print 368s (process:1904): libfprint-device-DEBUG: 00:53:37.076: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 368s (process:1904): libfprint-virtual_device-DEBUG: 00:53:37.076: Virtual device scanned print bar-print 368s (process:1904): libfprint-device-DEBUG: 00:53:37.076: Device reported finger status change: FP_FINGER_STATUS_NEEDED 368s (process:1904): libfprint-device-DEBUG: 00:53:37.076: Device reported verify completion 368s (process:1904): libfprint-device-DEBUG: 00:53:37.076: Device reported finger status change: FP_FINGER_STATUS_NONE 368s (process:1904): libfprint-device-DEBUG: 00:53:37.076: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 368s (process:1904): libfprint-device-DEBUG: 00:53:37.076: Updated temperature model after 0.90 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 368s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:37.076: Got a new connection! 368s (process:1904): libfprint-virtual_device-DEBUG: 00:53:37.076: Got instructions of length 16 368s (process:1904): libfprint-virtual_device-DEBUG: 00:53:37.076: Received command SET_KEEP_ALIVE 0 368s (process:1904): libfprint-virtual_device-DEBUG: 00:53:37.076: Keep alive toggled: 0 368s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:37.076: Got a new connection! 368s (process:1904): libfprint-virtual_device-DEBUG: 00:53:37.076: Got instructions of length 19 368s (process:1904): libfprint-virtual_device-DEBUG: 00:53:37.076: Received command SET_ENROLL_STAGES 5 368s (process:1904): libfprint-device-DEBUG: 00:53:37.076: Device reported close completion 368s (process:1904): libfprint-device-DEBUG: 00:53:37.076: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 368s (process:1904): libfprint-device-DEBUG: 00:53:37.077: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 368s Enroll done 368s ok 368s test_device_sleep_on_cancellation (__main__.VirtualDevice.test_device_sleep_on_cancellation) ... (process:1904): libfprint-virtual_device-DEBUG: 00:53:37.077: 7399785138092: ../libfprint/drivers/virtual-device.c:387 368s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:37.077: 7399785138109: ../libfprint/drivers/virtual-device-listener.c:153 368s (process:1904): libfprint-device-DEBUG: 00:53:37.077: Device reported open completion 368s (process:1904): libfprint-device-DEBUG: 00:53:37.077: Completing action FPI_DEVICE_ACTION_OPEN in idle! 368s (process:1904): libfprint-device-DEBUG: 00:53:37.077: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 368s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:37.077: Got a new connection! 368s (process:1904): libfprint-virtual_device-DEBUG: 00:53:37.077: Got instructions of length 26 368s (process:1904): libfprint-virtual_device-DEBUG: 00:53:37.077: Received command SET_CANCELLATION_ENABLED 0 368s (process:1904): libfprint-virtual_device-DEBUG: 00:53:37.077: Cancellation support toggled: 0 368s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:37.077: Got a new connection! 368s (process:1904): libfprint-virtual_device-DEBUG: 00:53:37.077: Got instructions of length 10 368s (process:1904): libfprint-virtual_device-DEBUG: 00:53:37.077: Received command SLEEP 1500 368s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:37.077: Got a new connection! 368s (process:1904): libfprint-virtual_device-DEBUG: 00:53:37.077: Got instructions of length 14 368s (process:1904): libfprint-virtual_device-DEBUG: 00:53:37.077: Received command SCAN foo-print 368s (process:1904): libfprint-device-DEBUG: 00:53:37.078: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 368s (process:1904): libfprint-virtual_device-DEBUG: 00:53:37.078: Processing command SLEEP 1500 368s (process:1904): libfprint-virtual_device-DEBUG: 00:53:37.078: Sleeping 1500ms 368s (process:1904): libfprint-device-DEBUG: 00:53:37.378: Idle cancelling on ongoing operation! 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.579: Sleeping completed 369s (process:1904): libfprint-device-DEBUG: 00:53:38.579: Device reported finger status change: FP_FINGER_STATUS_NEEDED 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.579: Virtual device scan failed with error: Operation was cancelled 369s (process:1904): libfprint-device-DEBUG: 00:53:38.579: Device reported verify completion 369s (process:1904): libfprint-device-DEBUG: 00:53:38.579: Device reported finger status change: FP_FINGER_STATUS_NONE 369s (process:1904): libfprint-device-DEBUG: 00:53:38.579: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 369s (process:1904): libfprint-device-DEBUG: 00:53:38.579: Updated temperature model after 1.50 seconds, ratio 0.27 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.579: Processing command SCAN foo-print 369s (process:1904): libfprint-device-DEBUG: 00:53:38.579: Device reported close completion 369s (process:1904): libfprint-device-DEBUG: 00:53:38.579: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 369s (process:1904): libfprint-device-DEBUG: 00:53:38.579: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 369s ok 369s test_enroll (__main__.VirtualDevice.test_enroll) ... (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.579: 7399786640742: ../libfprint/drivers/virtual-device.c:387 369s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:38.579: 7399786640759: ../libfprint/drivers/virtual-device-listener.c:153 369s (process:1904): libfprint-device-DEBUG: 00:53:38.580: Device reported open completion 369s (process:1904): libfprint-device-DEBUG: 00:53:38.580: Completing action FPI_DEVICE_ACTION_OPEN in idle! 369s (process:1904): libfprint-device-DEBUG: 00:53:38.580: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 369s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:38.580: Got a new connection! 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.580: Got instructions of length 14 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.580: Received command SCAN testprint 369s (process:1904): libfprint-device-DEBUG: 00:53:38.580: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.580: Processing command SCAN testprint 369s (process:1904): libfprint-device-DEBUG: 00:53:38.580: Device reported finger status change: FP_FINGER_STATUS_NEEDED 369s (process:1904): libfprint-device-DEBUG: 00:53:38.580: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 369s (process:1904): libfprint-device-DEBUG: 00:53:38.580: Device reported finger status change: FP_FINGER_STATUS_NEEDED 369s (process:1904): libfprint-device-DEBUG: 00:53:38.580: Device reported enroll progress, reported 1 of 5 have been completed 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.580: Sleeping completed 369s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:38.580: Got a new connection! 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.580: Got instructions of length 14 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.580: Received command SCAN testprint 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.580: Processing command SCAN testprint 369s (process:1904): libfprint-device-DEBUG: 00:53:38.580: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 369s (process:1904): libfprint-device-DEBUG: 00:53:38.580: Device reported finger status change: FP_FINGER_STATUS_NEEDED 369s (process:1904): libfprint-device-DEBUG: 00:53:38.580: Device reported enroll progress, reported 2 of 5 have been completed 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.580: Sleeping completed 369s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:38.580: Got a new connection! 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.581: Got instructions of length 14 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.581: Received command SCAN testprint 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.581: Processing command SCAN testprint 369s (process:1904): libfprint-device-DEBUG: 00:53:38.581: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 369s (process:1904): libfprint-device-DEBUG: 00:53:38.581: Device reported finger status change: FP_FINGER_STATUS_NEEDED 369s (process:1904): libfprint-device-DEBUG: 00:53:38.581: Device reported enroll progress, reported 3 of 5 have been completed 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.581: Sleeping completed 369s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:38.581: Got a new connection! 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.581: Got instructions of length 14 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.581: Received command SCAN testprint 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.581: Processing command SCAN testprint 369s (process:1904): libfprint-device-DEBUG: 00:53:38.581: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 369s (process:1904): libfprint-device-DEBUG: 00:53:38.581: Device reported finger status change: FP_FINGER_STATUS_NEEDED 369s (process:1904): libfprint-device-DEBUG: 00:53:38.581: Device reported enroll progress, reported 4 of 5 have been completed 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.581: Sleeping completed 369s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:38.581: Got a new connection! 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.581: Got instructions of length 14 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.581: Received command SCAN testprint 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.581: Processing command SCAN testprint 369s (process:1904): libfprint-device-DEBUG: 00:53:38.581: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 369s (process:1904): libfprint-device-DEBUG: 00:53:38.581: Device reported finger status change: FP_FINGER_STATUS_NEEDED 369s (process:1904): libfprint-device-DEBUG: 00:53:38.581: Device reported enroll progress, reported 5 of 5 have been completed 369s (process:1904): libfprint-device-DEBUG: 00:53:38.581: Device reported enroll completion 369s (process:1904): libfprint-device-DEBUG: 00:53:38.581: Device reported finger status change: FP_FINGER_STATUS_NONE 369s (process:1904): libfprint-device-DEBUG: 00:53:38.581: Print for finger FP_FINGER_LEFT_LITTLE enrolled 369s (process:1904): libfprint-device-DEBUG: 00:53:38.581: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 369s (process:1904): libfprint-device-DEBUG: 00:53:38.581: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 369s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:38.581: Got a new connection! 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.582: Got instructions of length 16 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.582: Received command SET_KEEP_ALIVE 0 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.582: Keep alive toggled: 0 369s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:38.582: Got a new connection! 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.582: Got instructions of length 19 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.582: Received command SET_ENROLL_STAGES 5 369s (process:1904): libfprint-device-DEBUG: 00:53:38.582: Device reported close completion 369s (process:1904): libfprint-device-DEBUG: 00:53:38.582: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 369s (process:1904): libfprint-device-DEBUG: 00:53:38.582: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 369s Enroll done 369s ok 369s test_enroll_script (__main__.VirtualDevice.test_enroll_script) ... (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.582: 7399786643414: ../libfprint/drivers/virtual-device.c:387 369s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:38.582: 7399786643431: ../libfprint/drivers/virtual-device-listener.c:153 369s (process:1904): libfprint-device-DEBUG: 00:53:38.582: Device reported open completion 369s (process:1904): libfprint-device-DEBUG: 00:53:38.582: Completing action FPI_DEVICE_ACTION_OPEN in idle! 369s (process:1904): libfprint-device-DEBUG: 00:53:38.582: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 369s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:38.582: Got a new connection! 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.582: Got instructions of length 19 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.582: Received command SET_ENROLL_STAGES 8 369s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:38.582: Got a new connection! 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.583: Got instructions of length 13 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.583: Received command SCAN print-id 369s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:38.583: Got a new connection! 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.583: Got instructions of length 13 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.583: Received command SCAN print-id 369s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:38.583: Got a new connection! 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.583: Got instructions of length 7 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.583: Received command RETRY 1 369s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:38.583: Got a new connection! 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.583: Got instructions of length 13 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.583: Received command SCAN print-id 369s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:38.583: Got a new connection! 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.583: Got instructions of length 7 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.583: Received command RETRY 3 369s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:38.583: Got a new connection! 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.583: Got instructions of length 13 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.583: Received command SCAN print-id 369s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:38.583: Got a new connection! 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.583: Got instructions of length 7 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.583: Received command RETRY 2 369s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:38.584: Got a new connection! 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.584: Got instructions of length 13 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.584: Received command SCAN print-id 369s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:38.584: Got a new connection! 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.584: Got instructions of length 8 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.584: Received command SLEEP 10 369s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:38.584: Got a new connection! 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.584: Got instructions of length 8 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.584: Received command SLEEP 20 369s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:38.584: Got a new connection! 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.584: Got instructions of length 7 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.584: Received command RETRY 0 369s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:38.584: Got a new connection! 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.584: Got instructions of length 7 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.584: Received command RETRY 3 369s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:38.584: Got a new connection! 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.584: Got instructions of length 13 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.584: Received command SCAN print-id 369s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:38.585: Got a new connection! 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.585: Got instructions of length 15 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.585: Received command SCAN another-id 369s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:38.585: Got a new connection! 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.585: Got instructions of length 13 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.585: Received command SCAN print-id 369s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:38.585: Got a new connection! 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.585: Got instructions of length 13 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.585: Received command SCAN print-id 369s (process:1904): libfprint-device-DEBUG: 00:53:38.585: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.585: Processing command SCAN print-id 369s (process:1904): libfprint-device-DEBUG: 00:53:38.585: Device reported finger status change: FP_FINGER_STATUS_NEEDED 369s (process:1904): libfprint-device-DEBUG: 00:53:38.585: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 369s (process:1904): libfprint-device-DEBUG: 00:53:38.585: Device reported finger status change: FP_FINGER_STATUS_NEEDED 369s (process:1904): libfprint-device-DEBUG: 00:53:38.585: Device reported enroll progress, reported 1 of 8 have been completed 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.585: Sleeping completed 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.585: Processing command SCAN print-id 369s (process:1904): libfprint-device-DEBUG: 00:53:38.585: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 369s (process:1904): libfprint-device-DEBUG: 00:53:38.585: Device reported finger status change: FP_FINGER_STATUS_NEEDED 369s (process:1904): libfprint-device-DEBUG: 00:53:38.585: Device reported enroll progress, reported 2 of 8 have been completed 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.585: Sleeping completed 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.585: Processing command RETRY 1 369s (process:1904): libfprint-device-DEBUG: 00:53:38.585: Device reported enroll progress, reported 2 of 8 have been completed 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.585: Sleeping completed 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.585: Processing command SCAN print-id 369s (process:1904): libfprint-device-DEBUG: 00:53:38.585: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 369s (process:1904): libfprint-device-DEBUG: 00:53:38.585: Device reported finger status change: FP_FINGER_STATUS_NEEDED 369s (process:1904): libfprint-device-DEBUG: 00:53:38.585: Device reported enroll progress, reported 3 of 8 have been completed 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.585: Sleeping completed 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.585: Processing command RETRY 3 369s (process:1904): libfprint-device-DEBUG: 00:53:38.585: Device reported enroll progress, reported 3 of 8 have been completed 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.585: Sleeping completed 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.585: Processing command SCAN print-id 369s (process:1904): libfprint-device-DEBUG: 00:53:38.585: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 369s (process:1904): libfprint-device-DEBUG: 00:53:38.585: Device reported finger status change: FP_FINGER_STATUS_NEEDED 369s (process:1904): libfprint-device-DEBUG: 00:53:38.585: Device reported enroll progress, reported 4 of 8 have been completed 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.585: Sleeping completed 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.585: Processing command RETRY 2 369s (process:1904): libfprint-device-DEBUG: 00:53:38.585: Device reported enroll progress, reported 4 of 8 have been completed 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.585: Sleeping completed 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.585: Processing command SCAN print-id 369s (process:1904): libfprint-device-DEBUG: 00:53:38.585: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 369s (process:1904): libfprint-device-DEBUG: 00:53:38.585: Device reported finger status change: FP_FINGER_STATUS_NEEDED 369s (process:1904): libfprint-device-DEBUG: 00:53:38.585: Device reported enroll progress, reported 5 of 8 have been completed 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.585: Processing command SLEEP 10 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.585: Sleeping 10ms 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.595: Sleeping completed 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.596: Processing command SLEEP 20 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.596: Sleeping 20ms 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.616: Sleeping completed 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.616: Processing command RETRY 0 369s (process:1904): libfprint-device-DEBUG: 00:53:38.616: Device reported enroll progress, reported 5 of 8 have been completed 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.616: Sleeping completed 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.616: Processing command RETRY 3 369s (process:1904): libfprint-device-DEBUG: 00:53:38.616: Device reported enroll progress, reported 5 of 8 have been completed 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.616: Sleeping completed 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.616: Processing command SCAN print-id 369s (process:1904): libfprint-device-DEBUG: 00:53:38.616: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 369s (process:1904): libfprint-device-DEBUG: 00:53:38.616: Device reported finger status change: FP_FINGER_STATUS_NEEDED 369s (process:1904): libfprint-device-DEBUG: 00:53:38.616: Device reported enroll progress, reported 6 of 8 have been completed 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.616: Sleeping completed 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.616: Processing command SCAN another-id 369s (process:1904): libfprint-device-DEBUG: 00:53:38.616: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 369s (process:1904): libfprint-device-DEBUG: 00:53:38.616: Device reported enroll progress, reported 6 of 8 have been completed 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.616: Sleeping completed 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.616: Processing command SCAN print-id 369s (process:1904): libfprint-device-DEBUG: 00:53:38.616: Device reported finger status change: FP_FINGER_STATUS_NEEDED 369s (process:1904): libfprint-device-DEBUG: 00:53:38.616: Device reported enroll progress, reported 7 of 8 have been completed 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.616: Sleeping completed 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.616: Processing command SCAN print-id 369s (process:1904): libfprint-device-DEBUG: 00:53:38.616: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 369s (process:1904): libfprint-device-DEBUG: 00:53:38.616: Device reported finger status change: FP_FINGER_STATUS_NEEDED 369s (process:1904): libfprint-device-DEBUG: 00:53:38.616: Device reported enroll progress, reported 8 of 8 have been completed 369s (process:1904): libfprint-device-DEBUG: 00:53:38.616: Device reported enroll completion 369s (process:1904): libfprint-device-DEBUG: 00:53:38.616: Device reported finger status change: FP_FINGER_STATUS_NONE 369s (process:1904): libfprint-device-DEBUG: 00:53:38.616: Print for finger FP_FINGER_UNKNOWN enrolled 369s (process:1904): libfprint-device-DEBUG: 00:53:38.616: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 369s (process:1904): libfprint-device-DEBUG: 00:53:38.616: Updated temperature model after 0.03 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 369s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:38.616: Got a new connection! 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.616: Got instructions of length 16 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.616: Received command SET_KEEP_ALIVE 0 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.616: Keep alive toggled: 0 369s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:38.616: Got a new connection! 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.617: Got instructions of length 19 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.617: Received command SET_ENROLL_STAGES 5 369s (process:1904): libfprint-device-DEBUG: 00:53:38.617: Device reported close completion 369s (process:1904): libfprint-device-DEBUG: 00:53:38.617: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 369s (process:1904): libfprint-device-DEBUG: 00:53:38.617: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 369s ok 369s test_enroll_script_interactive (__main__.VirtualDevice.test_enroll_script_interactive) ... (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.617: 7399786678240: ../libfprint/drivers/virtual-device.c:387 369s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:38.617: 7399786678306: ../libfprint/drivers/virtual-device-listener.c:153 369s (process:1904): libfprint-device-DEBUG: 00:53:38.617: Device reported open completion 369s (process:1904): libfprint-device-DEBUG: 00:53:38.617: Completing action FPI_DEVICE_ACTION_OPEN in idle! 369s (process:1904): libfprint-device-DEBUG: 00:53:38.617: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 369s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:38.617: Got a new connection! 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.617: Got instructions of length 8 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.617: Received command SLEEP 50 369s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:38.618: Got a new connection! 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.618: Got instructions of length 13 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.618: Received command SCAN print-id 369s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:38.618: Got a new connection! 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.618: Got instructions of length 13 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.618: Received command SCAN print-id 369s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:38.618: Got a new connection! 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.618: Got instructions of length 7 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.618: Received command RETRY 1 369s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:38.618: Got a new connection! 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.618: Got instructions of length 13 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.618: Received command SCAN print-id 369s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:38.618: Got a new connection! 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.618: Got instructions of length 8 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.618: Received command SLEEP 50 369s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:38.618: Got a new connection! 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.619: Got instructions of length 13 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.619: Received command SCAN print-id 369s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:38.619: Got a new connection! 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.619: Got instructions of length 7 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.619: Received command RETRY 2 369s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:38.619: Got a new connection! 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.619: Got instructions of length 15 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.619: Received command SCAN another-id 369s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:38.619: Got a new connection! 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.619: Got instructions of length 13 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.619: Received command SCAN print-id 369s (process:1904): libfprint-device-DEBUG: 00:53:38.619: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.619: Processing command SLEEP 50 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.619: Sleeping 50ms 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.669: Sleeping completed 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.669: Processing command SCAN print-id 369s (process:1904): libfprint-device-DEBUG: 00:53:38.669: Device reported finger status change: FP_FINGER_STATUS_NEEDED 369s (process:1904): libfprint-device-DEBUG: 00:53:38.669: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 369s (process:1904): libfprint-device-DEBUG: 00:53:38.669: Device reported finger status change: FP_FINGER_STATUS_NEEDED 369s (process:1904): libfprint-device-DEBUG: 00:53:38.669: Device reported enroll progress, reported 1 of 5 have been completed 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.669: Sleeping completed 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.669: Processing command SCAN print-id 369s (process:1904): libfprint-device-DEBUG: 00:53:38.670: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 369s (process:1904): libfprint-device-DEBUG: 00:53:38.670: Device reported finger status change: FP_FINGER_STATUS_NEEDED 369s (process:1904): libfprint-device-DEBUG: 00:53:38.670: Device reported enroll progress, reported 2 of 5 have been completed 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.670: Sleeping completed 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.670: Processing command RETRY 1 369s (process:1904): libfprint-device-DEBUG: 00:53:38.670: Device reported enroll progress, reported 2 of 5 have been completed 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.670: Sleeping completed 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.670: Processing command SCAN print-id 369s (process:1904): libfprint-device-DEBUG: 00:53:38.670: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 369s (process:1904): libfprint-device-DEBUG: 00:53:38.670: Device reported finger status change: FP_FINGER_STATUS_NEEDED 369s (process:1904): libfprint-device-DEBUG: 00:53:38.670: Device reported enroll progress, reported 3 of 5 have been completed 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.670: Processing command SLEEP 50 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.670: Sleeping 50ms 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.720: Sleeping completed 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.720: Processing command SCAN print-id 369s (process:1904): libfprint-device-DEBUG: 00:53:38.720: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 369s (process:1904): libfprint-device-DEBUG: 00:53:38.720: Device reported finger status change: FP_FINGER_STATUS_NEEDED 369s (process:1904): libfprint-device-DEBUG: 00:53:38.720: Device reported enroll progress, reported 4 of 5 have been completed 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.720: Sleeping completed 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.720: Processing command RETRY 2 369s (process:1904): libfprint-device-DEBUG: 00:53:38.720: Device reported enroll progress, reported 4 of 5 have been completed 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.720: Sleeping completed 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.720: Processing command SCAN another-id 369s (process:1904): libfprint-device-DEBUG: 00:53:38.720: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 369s (process:1904): libfprint-device-DEBUG: 00:53:38.720: Device reported enroll progress, reported 4 of 5 have been completed 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.720: Sleeping completed 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.720: Processing command SCAN print-id 369s (process:1904): libfprint-device-DEBUG: 00:53:38.720: Device reported finger status change: FP_FINGER_STATUS_NEEDED 369s (process:1904): libfprint-device-DEBUG: 00:53:38.720: Device reported enroll progress, reported 5 of 5 have been completed 369s (process:1904): libfprint-device-DEBUG: 00:53:38.720: Device reported enroll completion 369s (process:1904): libfprint-device-DEBUG: 00:53:38.720: Device reported finger status change: FP_FINGER_STATUS_NONE 369s (process:1904): libfprint-device-DEBUG: 00:53:38.720: Print for finger FP_FINGER_UNKNOWN enrolled 369s (process:1904): libfprint-device-DEBUG: 00:53:38.720: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 369s (process:1904): libfprint-device-DEBUG: 00:53:38.720: Updated temperature model after 0.10 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 369s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:38.720: Got a new connection! 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.721: Got instructions of length 16 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.721: Received command SET_KEEP_ALIVE 0 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.721: Keep alive toggled: 0 369s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:38.721: Got a new connection! 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.721: Got instructions of length 19 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.721: Received command SET_ENROLL_STAGES 5 369s (process:1904): libfprint-device-DEBUG: 00:53:38.721: Device reported close completion 369s (process:1904): libfprint-device-DEBUG: 00:53:38.721: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 369s (process:1904): libfprint-device-DEBUG: 00:53:38.721: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 369s ok 369s test_enroll_verify_error (__main__.VirtualDevice.test_enroll_verify_error) ... (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.721: 7399786782448: ../libfprint/drivers/virtual-device.c:387 369s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:38.721: 7399786782461: ../libfprint/drivers/virtual-device-listener.c:153 369s (process:1904): libfprint-device-DEBUG: 00:53:38.721: Device reported open completion 369s (process:1904): libfprint-device-DEBUG: 00:53:38.721: Completing action FPI_DEVICE_ACTION_OPEN in idle! 369s (process:1904): libfprint-device-DEBUG: 00:53:38.721: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 369s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:38.721: Got a new connection! 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.721: Got instructions of length 14 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.721: Received command SCAN testprint 369s (process:1904): libfprint-device-DEBUG: 00:53:38.722: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.722: Processing command SCAN testprint 369s (process:1904): libfprint-device-DEBUG: 00:53:38.722: Device reported finger status change: FP_FINGER_STATUS_NEEDED 369s (process:1904): libfprint-device-DEBUG: 00:53:38.722: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 369s (process:1904): libfprint-device-DEBUG: 00:53:38.722: Device reported finger status change: FP_FINGER_STATUS_NEEDED 369s (process:1904): libfprint-device-DEBUG: 00:53:38.722: Device reported enroll progress, reported 1 of 5 have been completed 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.722: Sleeping completed 369s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:38.722: Got a new connection! 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.722: Got instructions of length 14 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.722: Received command SCAN testprint 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.722: Processing command SCAN testprint 369s (process:1904): libfprint-device-DEBUG: 00:53:38.722: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 369s (process:1904): libfprint-device-DEBUG: 00:53:38.722: Device reported finger status change: FP_FINGER_STATUS_NEEDED 369s (process:1904): libfprint-device-DEBUG: 00:53:38.722: Device reported enroll progress, reported 2 of 5 have been completed 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.722: Sleeping completed 369s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:38.722: Got a new connection! 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.722: Got instructions of length 14 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.722: Received command SCAN testprint 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.722: Processing command SCAN testprint 369s (process:1904): libfprint-device-DEBUG: 00:53:38.722: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 369s (process:1904): libfprint-device-DEBUG: 00:53:38.722: Device reported finger status change: FP_FINGER_STATUS_NEEDED 369s (process:1904): libfprint-device-DEBUG: 00:53:38.722: Device reported enroll progress, reported 3 of 5 have been completed 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.722: Sleeping completed 369s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:38.722: Got a new connection! 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.722: Got instructions of length 14 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.722: Received command SCAN testprint 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.722: Processing command SCAN testprint 369s (process:1904): libfprint-device-DEBUG: 00:53:38.722: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 369s (process:1904): libfprint-device-DEBUG: 00:53:38.722: Device reported finger status change: FP_FINGER_STATUS_NEEDED 369s (process:1904): libfprint-device-DEBUG: 00:53:38.722: Device reported enroll progress, reported 4 of 5 have been completed 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.723: Sleeping completed 369s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:38.723: Got a new connection! 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.723: Got instructions of length 14 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.723: Received command SCAN testprint 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.723: Processing command SCAN testprint 369s (process:1904): libfprint-device-DEBUG: 00:53:38.723: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 369s (process:1904): libfprint-device-DEBUG: 00:53:38.723: Device reported finger status change: FP_FINGER_STATUS_NEEDED 369s (process:1904): libfprint-device-DEBUG: 00:53:38.723: Device reported enroll progress, reported 5 of 5 have been completed 369s (process:1904): libfprint-device-DEBUG: 00:53:38.723: Device reported enroll completion 369s (process:1904): libfprint-device-DEBUG: 00:53:38.723: Device reported finger status change: FP_FINGER_STATUS_NONE 369s (process:1904): libfprint-device-DEBUG: 00:53:38.723: Print for finger FP_FINGER_LEFT_RING enrolled 369s (process:1904): libfprint-device-DEBUG: 00:53:38.723: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 369s (process:1904): libfprint-device-DEBUG: 00:53:38.723: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 369s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:38.723: Got a new connection! 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.723: Got instructions of length 7 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.723: Received command ERROR 0 369s (process:1904): libfprint-device-DEBUG: 00:53:38.723: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.723: Processing command ERROR 0 369s (process:1904): libfprint-device-DEBUG: 00:53:38.723: Device reported finger status change: FP_FINGER_STATUS_NEEDED 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.723: Virtual device scan failed with error: An unspecified error occurred! 369s (process:1904): libfprint-device-DEBUG: 00:53:38.723: Device reported verify completion 369s (process:1904): libfprint-device-DEBUG: 00:53:38.723: Device reported finger status change: FP_FINGER_STATUS_NONE 369s (process:1904): libfprint-device-DEBUG: 00:53:38.723: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 369s (process:1904): libfprint-device-DEBUG: 00:53:38.723: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 369s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:38.724: Got a new connection! 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.724: Got instructions of length 16 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.724: Received command SET_KEEP_ALIVE 0 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.724: Keep alive toggled: 0 369s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:38.724: Got a new connection! 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.724: Got instructions of length 19 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.724: Received command SET_ENROLL_STAGES 5 369s (process:1904): libfprint-device-DEBUG: 00:53:38.724: Device reported close completion 369s (process:1904): libfprint-device-DEBUG: 00:53:38.724: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 369s (process:1904): libfprint-device-DEBUG: 00:53:38.724: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 369s Enroll done 369s ok 369s test_enroll_verify_match (__main__.VirtualDevice.test_enroll_verify_match) ... (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.724: 7399786785453: ../libfprint/drivers/virtual-device.c:387 369s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:38.724: 7399786785465: ../libfprint/drivers/virtual-device-listener.c:153 369s (process:1904): libfprint-device-DEBUG: 00:53:38.724: Device reported open completion 369s (process:1904): libfprint-device-DEBUG: 00:53:38.724: Completing action FPI_DEVICE_ACTION_OPEN in idle! 369s (process:1904): libfprint-device-DEBUG: 00:53:38.724: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 369s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:38.724: Got a new connection! 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.724: Got instructions of length 14 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.724: Received command SCAN testprint 369s (process:1904): libfprint-device-DEBUG: 00:53:38.725: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.725: Processing command SCAN testprint 369s (process:1904): libfprint-device-DEBUG: 00:53:38.725: Device reported finger status change: FP_FINGER_STATUS_NEEDED 369s (process:1904): libfprint-device-DEBUG: 00:53:38.725: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 369s (process:1904): libfprint-device-DEBUG: 00:53:38.725: Device reported finger status change: FP_FINGER_STATUS_NEEDED 369s (process:1904): libfprint-device-DEBUG: 00:53:38.725: Device reported enroll progress, reported 1 of 5 have been completed 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.725: Sleeping completed 369s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:38.725: Got a new connection! 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.725: Got instructions of length 14 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.725: Received command SCAN testprint 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.725: Processing command SCAN testprint 369s (process:1904): libfprint-device-DEBUG: 00:53:38.725: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 369s (process:1904): libfprint-device-DEBUG: 00:53:38.725: Device reported finger status change: FP_FINGER_STATUS_NEEDED 369s (process:1904): libfprint-device-DEBUG: 00:53:38.725: Device reported enroll progress, reported 2 of 5 have been completed 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.725: Sleeping completed 369s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:38.725: Got a new connection! 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.725: Got instructions of length 14 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.725: Received command SCAN testprint 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.725: Processing command SCAN testprint 369s (process:1904): libfprint-device-DEBUG: 00:53:38.725: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 369s (process:1904): libfprint-device-DEBUG: 00:53:38.725: Device reported finger status change: FP_FINGER_STATUS_NEEDED 369s (process:1904): libfprint-device-DEBUG: 00:53:38.725: Device reported enroll progress, reported 3 of 5 have been completed 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.725: Sleeping completed 369s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:38.725: Got a new connection! 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.725: Got instructions of length 14 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.725: Received command SCAN testprint 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.725: Processing command SCAN testprint 369s (process:1904): libfprint-device-DEBUG: 00:53:38.725: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 369s (process:1904): libfprint-device-DEBUG: 00:53:38.725: Device reported finger status change: FP_FINGER_STATUS_NEEDED 369s (process:1904): libfprint-device-DEBUG: 00:53:38.725: Device reported enroll progress, reported 4 of 5 have been completed 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.725: Sleeping completed 369s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:38.726: Got a new connection! 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.726: Got instructions of length 14 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.726: Received command SCAN testprint 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.726: Processing command SCAN testprint 369s (process:1904): libfprint-device-DEBUG: 00:53:38.726: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 369s (process:1904): libfprint-device-DEBUG: 00:53:38.726: Device reported finger status change: FP_FINGER_STATUS_NEEDED 369s (process:1904): libfprint-device-DEBUG: 00:53:38.726: Device reported enroll progress, reported 5 of 5 have been completed 369s (process:1904): libfprint-device-DEBUG: 00:53:38.726: Device reported enroll completion 369s (process:1904): libfprint-device-DEBUG: 00:53:38.726: Device reported finger status change: FP_FINGER_STATUS_NONE 369s (process:1904): libfprint-device-DEBUG: 00:53:38.726: Print for finger FP_FINGER_LEFT_THUMB enrolled 369s (process:1904): libfprint-device-DEBUG: 00:53:38.726: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 369s (process:1904): libfprint-device-DEBUG: 00:53:38.726: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 369s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:38.726: Got a new connection! 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.726: Got instructions of length 14 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.726: Received command SCAN testprint 369s (process:1904): libfprint-device-DEBUG: 00:53:38.726: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.726: Processing command SCAN testprint 369s (process:1904): libfprint-device-DEBUG: 00:53:38.726: Device reported finger status change: FP_FINGER_STATUS_NEEDED 369s (process:1904): libfprint-device-DEBUG: 00:53:38.726: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.726: Virtual device scanned print testprint 369s (process:1904): libfprint-device-DEBUG: 00:53:38.726: Device reported verify result 369s (process:1904): libfprint-device-DEBUG: 00:53:38.726: Device reported finger status change: FP_FINGER_STATUS_NEEDED 369s (process:1904): libfprint-device-DEBUG: 00:53:38.726: Device reported verify completion 369s (process:1904): libfprint-device-DEBUG: 00:53:38.726: Device reported finger status change: FP_FINGER_STATUS_NONE 369s (process:1904): libfprint-device-DEBUG: 00:53:38.726: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 369s (process:1904): libfprint-device-DEBUG: 00:53:38.726: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 369s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:38.727: Got a new connection! 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.727: Got instructions of length 16 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.727: Received command SET_KEEP_ALIVE 0 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.727: Keep alive toggled: 0 369s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:38.727: Got a new connection! 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.727: Got instructions of length 19 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.727: Received command SET_ENROLL_STAGES 5 369s (process:1904): libfprint-device-DEBUG: 00:53:38.727: Device reported close completion 369s (process:1904): libfprint-device-DEBUG: 00:53:38.727: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 369s (process:1904): libfprint-device-DEBUG: 00:53:38.727: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 369s Enroll done 369s ok 369s test_enroll_verify_no_match (__main__.VirtualDevice.test_enroll_verify_no_match) ... (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.727: 7399786788437: ../libfprint/drivers/virtual-device.c:387 369s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:38.727: 7399786788451: ../libfprint/drivers/virtual-device-listener.c:153 369s (process:1904): libfprint-device-DEBUG: 00:53:38.727: Device reported open completion 369s (process:1904): libfprint-device-DEBUG: 00:53:38.727: Completing action FPI_DEVICE_ACTION_OPEN in idle! 369s (process:1904): libfprint-device-DEBUG: 00:53:38.727: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 369s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:38.727: Got a new connection! 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.727: Got instructions of length 14 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.727: Received command SCAN testprint 369s (process:1904): libfprint-device-DEBUG: 00:53:38.728: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.728: Processing command SCAN testprint 369s (process:1904): libfprint-device-DEBUG: 00:53:38.728: Device reported finger status change: FP_FINGER_STATUS_NEEDED 369s (process:1904): libfprint-device-DEBUG: 00:53:38.728: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 369s (process:1904): libfprint-device-DEBUG: 00:53:38.728: Device reported finger status change: FP_FINGER_STATUS_NEEDED 369s (process:1904): libfprint-device-DEBUG: 00:53:38.728: Device reported enroll progress, reported 1 of 5 have been completed 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.728: Sleeping completed 369s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:38.728: Got a new connection! 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.728: Got instructions of length 14 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.728: Received command SCAN testprint 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.728: Processing command SCAN testprint 369s (process:1904): libfprint-device-DEBUG: 00:53:38.728: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 369s (process:1904): libfprint-device-DEBUG: 00:53:38.728: Device reported finger status change: FP_FINGER_STATUS_NEEDED 369s (process:1904): libfprint-device-DEBUG: 00:53:38.728: Device reported enroll progress, reported 2 of 5 have been completed 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.728: Sleeping completed 369s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:38.728: Got a new connection! 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.728: Got instructions of length 14 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.728: Received command SCAN testprint 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.728: Processing command SCAN testprint 369s (process:1904): libfprint-device-DEBUG: 00:53:38.728: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 369s (process:1904): libfprint-device-DEBUG: 00:53:38.728: Device reported finger status change: FP_FINGER_STATUS_NEEDED 369s (process:1904): libfprint-device-DEBUG: 00:53:38.728: Device reported enroll progress, reported 3 of 5 have been completed 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.728: Sleeping completed 369s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:38.728: Got a new connection! 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.728: Got instructions of length 14 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.728: Received command SCAN testprint 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.728: Processing command SCAN testprint 369s (process:1904): libfprint-device-DEBUG: 00:53:38.728: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 369s (process:1904): libfprint-device-DEBUG: 00:53:38.728: Device reported finger status change: FP_FINGER_STATUS_NEEDED 369s (process:1904): libfprint-device-DEBUG: 00:53:38.728: Device reported enroll progress, reported 4 of 5 have been completed 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.728: Sleeping completed 369s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:38.729: Got a new connection! 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.729: Got instructions of length 14 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.729: Received command SCAN testprint 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.729: Processing command SCAN testprint 369s (process:1904): libfprint-device-DEBUG: 00:53:38.729: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 369s (process:1904): libfprint-device-DEBUG: 00:53:38.729: Device reported finger status change: FP_FINGER_STATUS_NEEDED 369s (process:1904): libfprint-device-DEBUG: 00:53:38.729: Device reported enroll progress, reported 5 of 5 have been completed 369s (process:1904): libfprint-device-DEBUG: 00:53:38.729: Device reported enroll completion 369s (process:1904): libfprint-device-DEBUG: 00:53:38.729: Device reported finger status change: FP_FINGER_STATUS_NONE 369s (process:1904): libfprint-device-DEBUG: 00:53:38.729: Print for finger FP_FINGER_LEFT_RING enrolled 369s (process:1904): libfprint-device-DEBUG: 00:53:38.729: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 369s (process:1904): libfprint-device-DEBUG: 00:53:38.729: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 369s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:38.729: Got a new connection! 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.729: Got instructions of length 18 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.729: Received command SCAN not-testprint 369s (process:1904): libfprint-device-DEBUG: 00:53:38.729: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.729: Processing command SCAN not-testprint 369s (process:1904): libfprint-device-DEBUG: 00:53:38.729: Device reported finger status change: FP_FINGER_STATUS_NEEDED 369s (process:1904): libfprint-device-DEBUG: 00:53:38.729: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.729: Virtual device scanned print not-testprint 369s (process:1904): libfprint-device-DEBUG: 00:53:38.729: Device reported verify result 369s (process:1904): libfprint-device-DEBUG: 00:53:38.729: Device reported finger status change: FP_FINGER_STATUS_NEEDED 369s (process:1904): libfprint-device-DEBUG: 00:53:38.729: Device reported verify completion 369s (process:1904): libfprint-device-DEBUG: 00:53:38.729: Device reported finger status change: FP_FINGER_STATUS_NONE 369s (process:1904): libfprint-device-DEBUG: 00:53:38.729: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 369s (process:1904): libfprint-device-DEBUG: 00:53:38.729: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 369s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:38.729: Got a new connection! 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.729: Got instructions of length 16 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.729: Received command SET_KEEP_ALIVE 0 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.729: Keep alive toggled: 0 369s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:38.730: Got a new connection! 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.730: Got instructions of length 19 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.730: Received command SET_ENROLL_STAGES 5 369s (process:1904): libfprint-device-DEBUG: 00:53:38.730: Device reported close completion 369s (process:1904): libfprint-device-DEBUG: 00:53:38.730: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 369s (process:1904): libfprint-device-DEBUG: 00:53:38.730: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 369s Enroll done 369s ok 369s test_enroll_verify_retry (__main__.VirtualDevice.test_enroll_verify_retry) ... (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.730: 7399786791261: ../libfprint/drivers/virtual-device.c:387 369s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:38.730: 7399786791271: ../libfprint/drivers/virtual-device-listener.c:153 369s (process:1904): libfprint-device-DEBUG: 00:53:38.730: Device reported open completion 369s (process:1904): libfprint-device-DEBUG: 00:53:38.730: Completing action FPI_DEVICE_ACTION_OPEN in idle! 369s (process:1904): libfprint-device-DEBUG: 00:53:38.730: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 369s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:38.730: Got a new connection! 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.730: Got instructions of length 7 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.730: Received command RETRY 1 369s (process:1904): libfprint-device-DEBUG: 00:53:38.730: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.730: Processing command RETRY 1 369s (process:1904): libfprint-device-DEBUG: 00:53:38.730: Device reported finger status change: FP_FINGER_STATUS_NEEDED 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.730: Virtual device scan failed with error: The swipe was too short, please try again. 369s (process:1904): libfprint-device-DEBUG: 00:53:38.730: Device reported verify result 369s (process:1904): libfprint-device-DEBUG: 00:53:38.730: Device reported verify completion 369s (process:1904): libfprint-device-DEBUG: 00:53:38.730: Device reported finger status change: FP_FINGER_STATUS_NONE 369s (process:1904): libfprint-device-DEBUG: 00:53:38.730: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 369s (process:1904): libfprint-device-DEBUG: 00:53:38.730: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 369s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:38.731: Got a new connection! 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.731: Got instructions of length 16 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.731: Received command SET_KEEP_ALIVE 0 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.731: Keep alive toggled: 0 369s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:38.731: Got a new connection! 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.731: Got instructions of length 19 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.731: Received command SET_ENROLL_STAGES 5 369s (process:1904): libfprint-device-DEBUG: 00:53:38.731: Device reported close completion 369s (process:1904): libfprint-device-DEBUG: 00:53:38.731: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 369s (process:1904): libfprint-device-DEBUG: 00:53:38.731: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 369s ok 369s test_enroll_verify_script (__main__.VirtualDevice.test_enroll_verify_script) ... (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.731: 7399786792588: ../libfprint/drivers/virtual-device.c:387 369s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:38.731: 7399786792597: ../libfprint/drivers/virtual-device-listener.c:153 369s (process:1904): libfprint-device-DEBUG: 00:53:38.731: Device reported open completion 369s (process:1904): libfprint-device-DEBUG: 00:53:38.731: Completing action FPI_DEVICE_ACTION_OPEN in idle! 369s (process:1904): libfprint-device-DEBUG: 00:53:38.731: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 369s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:38.731: Got a new connection! 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.732: Got instructions of length 19 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.732: Received command SET_ENROLL_STAGES 8 369s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:38.732: Got a new connection! 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.732: Got instructions of length 13 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.732: Received command SCAN print-id 369s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:38.732: Got a new connection! 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.732: Got instructions of length 13 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.732: Received command SCAN print-id 369s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:38.732: Got a new connection! 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.732: Got instructions of length 7 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.732: Received command RETRY 1 369s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:38.732: Got a new connection! 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.732: Got instructions of length 13 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.732: Received command SCAN print-id 369s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:38.732: Got a new connection! 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.732: Got instructions of length 7 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.732: Received command RETRY 3 369s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:38.732: Got a new connection! 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.733: Got instructions of length 13 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.733: Received command SCAN print-id 369s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:38.733: Got a new connection! 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.733: Got instructions of length 7 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.733: Received command RETRY 2 369s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:38.733: Got a new connection! 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.733: Got instructions of length 13 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.733: Received command SCAN print-id 369s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:38.733: Got a new connection! 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.733: Got instructions of length 8 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.733: Received command SLEEP 10 369s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:38.733: Got a new connection! 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.733: Got instructions of length 8 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.733: Received command SLEEP 20 369s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:38.733: Got a new connection! 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.733: Got instructions of length 7 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.733: Received command RETRY 0 369s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:38.733: Got a new connection! 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.733: Got instructions of length 7 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.733: Received command RETRY 3 369s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:38.734: Got a new connection! 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.734: Got instructions of length 13 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.734: Received command SCAN print-id 369s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:38.734: Got a new connection! 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.734: Got instructions of length 15 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.734: Received command SCAN another-id 369s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:38.734: Got a new connection! 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.734: Got instructions of length 13 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.734: Received command SCAN print-id 369s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:38.734: Got a new connection! 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.734: Got instructions of length 13 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.734: Received command SCAN print-id 369s (process:1904): libfprint-device-DEBUG: 00:53:38.734: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.734: Processing command SCAN print-id 369s (process:1904): libfprint-device-DEBUG: 00:53:38.734: Device reported finger status change: FP_FINGER_STATUS_NEEDED 369s (process:1904): libfprint-device-DEBUG: 00:53:38.734: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 369s (process:1904): libfprint-device-DEBUG: 00:53:38.734: Device reported finger status change: FP_FINGER_STATUS_NEEDED 369s (process:1904): libfprint-device-DEBUG: 00:53:38.734: Device reported enroll progress, reported 1 of 8 have been completed 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.734: Sleeping completed 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.734: Processing command SCAN print-id 369s (process:1904): libfprint-device-DEBUG: 00:53:38.734: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 369s (process:1904): libfprint-device-DEBUG: 00:53:38.734: Device reported finger status change: FP_FINGER_STATUS_NEEDED 369s (process:1904): libfprint-device-DEBUG: 00:53:38.734: Device reported enroll progress, reported 2 of 8 have been completed 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.734: Sleeping completed 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.734: Processing command RETRY 1 369s (process:1904): libfprint-device-DEBUG: 00:53:38.734: Device reported enroll progress, reported 2 of 8 have been completed 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.734: Sleeping completed 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.734: Processing command SCAN print-id 369s (process:1904): libfprint-device-DEBUG: 00:53:38.734: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 369s (process:1904): libfprint-device-DEBUG: 00:53:38.734: Device reported finger status change: FP_FINGER_STATUS_NEEDED 369s (process:1904): libfprint-device-DEBUG: 00:53:38.734: Device reported enroll progress, reported 3 of 8 have been completed 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.734: Sleeping completed 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.734: Processing command RETRY 3 369s (process:1904): libfprint-device-DEBUG: 00:53:38.734: Device reported enroll progress, reported 3 of 8 have been completed 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.734: Sleeping completed 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.734: Processing command SCAN print-id 369s (process:1904): libfprint-device-DEBUG: 00:53:38.734: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 369s (process:1904): libfprint-device-DEBUG: 00:53:38.734: Device reported finger status change: FP_FINGER_STATUS_NEEDED 369s (process:1904): libfprint-device-DEBUG: 00:53:38.734: Device reported enroll progress, reported 4 of 8 have been completed 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.734: Sleeping completed 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.734: Processing command RETRY 2 369s (process:1904): libfprint-device-DEBUG: 00:53:38.734: Device reported enroll progress, reported 4 of 8 have been completed 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.734: Sleeping completed 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.734: Processing command SCAN print-id 369s (process:1904): libfprint-device-DEBUG: 00:53:38.734: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 369s (process:1904): libfprint-device-DEBUG: 00:53:38.734: Device reported finger status change: FP_FINGER_STATUS_NEEDED 369s (process:1904): libfprint-device-DEBUG: 00:53:38.734: Device reported enroll progress, reported 5 of 8 have been completed 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.734: Processing command SLEEP 10 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.734: Sleeping 10ms 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.745: Sleeping completed 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.745: Processing command SLEEP 20 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.745: Sleeping 20ms 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.765: Sleeping completed 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.765: Processing command RETRY 0 369s (process:1904): libfprint-device-DEBUG: 00:53:38.765: Device reported enroll progress, reported 5 of 8 have been completed 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.765: Sleeping completed 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.765: Processing command RETRY 3 369s (process:1904): libfprint-device-DEBUG: 00:53:38.765: Device reported enroll progress, reported 5 of 8 have been completed 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.765: Sleeping completed 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.765: Processing command SCAN print-id 369s (process:1904): libfprint-device-DEBUG: 00:53:38.765: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 369s (process:1904): libfprint-device-DEBUG: 00:53:38.765: Device reported finger status change: FP_FINGER_STATUS_NEEDED 369s (process:1904): libfprint-device-DEBUG: 00:53:38.765: Device reported enroll progress, reported 6 of 8 have been completed 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.765: Sleeping completed 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.765: Processing command SCAN another-id 369s (process:1904): libfprint-device-DEBUG: 00:53:38.765: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 369s (process:1904): libfprint-device-DEBUG: 00:53:38.765: Device reported enroll progress, reported 6 of 8 have been completed 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.765: Sleeping completed 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.765: Processing command SCAN print-id 369s (process:1904): libfprint-device-DEBUG: 00:53:38.765: Device reported finger status change: FP_FINGER_STATUS_NEEDED 369s (process:1904): libfprint-device-DEBUG: 00:53:38.765: Device reported enroll progress, reported 7 of 8 have been completed 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.765: Sleeping completed 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.765: Processing command SCAN print-id 369s (process:1904): libfprint-device-DEBUG: 00:53:38.765: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 369s (process:1904): libfprint-device-DEBUG: 00:53:38.765: Device reported finger status change: FP_FINGER_STATUS_NEEDED 369s (process:1904): libfprint-device-DEBUG: 00:53:38.765: Device reported enroll progress, reported 8 of 8 have been completed 369s (process:1904): libfprint-device-DEBUG: 00:53:38.765: Device reported enroll completion 369s (process:1904): libfprint-device-DEBUG: 00:53:38.765: Device reported finger status change: FP_FINGER_STATUS_NONE 369s (process:1904): libfprint-device-DEBUG: 00:53:38.765: Print for finger FP_FINGER_UNKNOWN enrolled 369s (process:1904): libfprint-device-DEBUG: 00:53:38.765: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 369s (process:1904): libfprint-device-DEBUG: 00:53:38.765: Updated temperature model after 0.03 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 369s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:38.765: Got a new connection! 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.765: Got instructions of length 7 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.765: Received command RETRY 2 369s (process:1904): libfprint-device-DEBUG: 00:53:38.766: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.766: Processing command RETRY 2 369s (process:1904): libfprint-device-DEBUG: 00:53:38.766: Device reported finger status change: FP_FINGER_STATUS_NEEDED 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.766: Virtual device scan failed with error: The finger was not centered properly, please try again. 369s (process:1904): libfprint-device-DEBUG: 00:53:38.766: Device reported verify result 369s (process:1904): libfprint-device-DEBUG: 00:53:38.766: Device reported verify completion 369s (process:1904): libfprint-device-DEBUG: 00:53:38.766: Device reported finger status change: FP_FINGER_STATUS_NONE 369s (process:1904): libfprint-device-DEBUG: 00:53:38.766: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 369s (process:1904): libfprint-device-DEBUG: 00:53:38.766: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 369s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:38.766: Got a new connection! 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.766: Got instructions of length 8 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.766: Received command SLEEP 50 369s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:38.766: Got a new connection! 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.766: Got instructions of length 7 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.766: Received command RETRY 1 369s (process:1904): libfprint-device-DEBUG: 00:53:38.766: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.766: Processing command SLEEP 50 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.766: Sleeping 50ms 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.816: Sleeping completed 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.816: Processing command RETRY 1 369s (process:1904): libfprint-device-DEBUG: 00:53:38.816: Device reported finger status change: FP_FINGER_STATUS_NEEDED 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.816: Virtual device scan failed with error: The swipe was too short, please try again. 369s (process:1904): libfprint-device-DEBUG: 00:53:38.816: Device reported verify result 369s (process:1904): libfprint-device-DEBUG: 00:53:38.816: Device reported verify completion 369s (process:1904): libfprint-device-DEBUG: 00:53:38.816: Device reported finger status change: FP_FINGER_STATUS_NONE 369s (process:1904): libfprint-device-DEBUG: 00:53:38.816: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 369s (process:1904): libfprint-device-DEBUG: 00:53:38.816: Updated temperature model after 0.05 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 369s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:38.817: Got a new connection! 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.817: Got instructions of length 15 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.817: Received command SCAN another-id 369s (process:1904): libfprint-device-DEBUG: 00:53:38.817: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.817: Processing command SCAN another-id 369s (process:1904): libfprint-device-DEBUG: 00:53:38.817: Device reported finger status change: FP_FINGER_STATUS_NEEDED 369s (process:1904): libfprint-device-DEBUG: 00:53:38.817: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.817: Virtual device scanned print another-id 369s (process:1904): libfprint-device-DEBUG: 00:53:38.817: Device reported verify result 369s (process:1904): libfprint-device-DEBUG: 00:53:38.817: Device reported finger status change: FP_FINGER_STATUS_NEEDED 369s (process:1904): libfprint-device-DEBUG: 00:53:38.817: Device reported verify completion 369s (process:1904): libfprint-device-DEBUG: 00:53:38.817: Device reported finger status change: FP_FINGER_STATUS_NONE 369s (process:1904): libfprint-device-DEBUG: 00:53:38.817: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 369s (process:1904): libfprint-device-DEBUG: 00:53:38.817: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 369s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:38.817: Got a new connection! 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.817: Got instructions of length 13 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.817: Received command SCAN print-id 369s (process:1904): libfprint-device-DEBUG: 00:53:38.817: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.817: Processing command SCAN print-id 369s (process:1904): libfprint-device-DEBUG: 00:53:38.817: Device reported finger status change: FP_FINGER_STATUS_NEEDED 369s (process:1904): libfprint-device-DEBUG: 00:53:38.817: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.817: Virtual device scanned print print-id 369s (process:1904): libfprint-device-DEBUG: 00:53:38.817: Device reported verify result 369s (process:1904): libfprint-device-DEBUG: 00:53:38.817: Device reported finger status change: FP_FINGER_STATUS_NEEDED 369s (process:1904): libfprint-device-DEBUG: 00:53:38.817: Device reported verify completion 369s (process:1904): libfprint-device-DEBUG: 00:53:38.817: Device reported finger status change: FP_FINGER_STATUS_NONE 369s (process:1904): libfprint-device-DEBUG: 00:53:38.817: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 369s (process:1904): libfprint-device-DEBUG: 00:53:38.817: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 369s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:38.818: Got a new connection! 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.818: Got instructions of length 16 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.818: Received command SET_KEEP_ALIVE 0 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.818: Keep alive toggled: 0 369s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:38.818: Got a new connection! 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.818: Got instructions of length 19 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.818: Received command SET_ENROLL_STAGES 5 369s (process:1904): libfprint-device-DEBUG: 00:53:38.818: Device reported close completion 369s (process:1904): libfprint-device-DEBUG: 00:53:38.818: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 369s (process:1904): libfprint-device-DEBUG: 00:53:38.818: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 369s ok 369s test_enroll_with_retry (__main__.VirtualDevice.test_enroll_with_retry) ... (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.818: 7399786879602: ../libfprint/drivers/virtual-device.c:387 369s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:38.818: 7399786879612: ../libfprint/drivers/virtual-device-listener.c:153 369s (process:1904): libfprint-device-DEBUG: 00:53:38.818: Device reported open completion 369s (process:1904): libfprint-device-DEBUG: 00:53:38.818: Completing action FPI_DEVICE_ACTION_OPEN in idle! 369s (process:1904): libfprint-device-DEBUG: 00:53:38.818: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 369s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:38.819: Got a new connection! 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.819: Got instructions of length 14 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.819: Received command SCAN testprint 369s (process:1904): libfprint-device-DEBUG: 00:53:38.819: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.819: Processing command SCAN testprint 369s (process:1904): libfprint-device-DEBUG: 00:53:38.819: Device reported finger status change: FP_FINGER_STATUS_NEEDED 369s (process:1904): libfprint-device-DEBUG: 00:53:38.819: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 369s (process:1904): libfprint-device-DEBUG: 00:53:38.819: Device reported finger status change: FP_FINGER_STATUS_NEEDED 369s (process:1904): libfprint-device-DEBUG: 00:53:38.819: Device reported enroll progress, reported 1 of 5 have been completed 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.819: Sleeping completed 369s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:38.819: Got a new connection! 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.819: Got instructions of length 14 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.819: Received command SCAN testprint 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.819: Processing command SCAN testprint 369s (process:1904): libfprint-device-DEBUG: 00:53:38.819: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 369s (process:1904): libfprint-device-DEBUG: 00:53:38.819: Device reported finger status change: FP_FINGER_STATUS_NEEDED 369s (process:1904): libfprint-device-DEBUG: 00:53:38.819: Device reported enroll progress, reported 2 of 5 have been completed 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.819: Sleeping completed 369s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:38.819: Got a new connection! 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.819: Got instructions of length 7 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.819: Received command RETRY 1 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.819: Processing command RETRY 1 369s (process:1904): libfprint-device-DEBUG: 00:53:38.819: Device reported enroll progress, reported 2 of 5 have been completed 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.819: Sleeping completed 369s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:38.820: Got a new connection! 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.820: Got instructions of length 14 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.820: Received command SCAN testprint 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.820: Processing command SCAN testprint 369s (process:1904): libfprint-device-DEBUG: 00:53:38.820: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 369s (process:1904): libfprint-device-DEBUG: 00:53:38.820: Device reported finger status change: FP_FINGER_STATUS_NEEDED 369s (process:1904): libfprint-device-DEBUG: 00:53:38.820: Device reported enroll progress, reported 3 of 5 have been completed 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.820: Sleeping completed 369s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:38.820: Got a new connection! 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.820: Got instructions of length 14 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.820: Received command SCAN testprint 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.820: Processing command SCAN testprint 369s (process:1904): libfprint-device-DEBUG: 00:53:38.820: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 369s (process:1904): libfprint-device-DEBUG: 00:53:38.820: Device reported finger status change: FP_FINGER_STATUS_NEEDED 369s (process:1904): libfprint-device-DEBUG: 00:53:38.820: Device reported enroll progress, reported 4 of 5 have been completed 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.820: Sleeping completed 369s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:38.820: Got a new connection! 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.820: Got instructions of length 14 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.820: Received command SCAN testprint 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.820: Processing command SCAN testprint 369s (process:1904): libfprint-device-DEBUG: 00:53:38.820: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 369s (process:1904): libfprint-device-DEBUG: 00:53:38.820: Device reported finger status change: FP_FINGER_STATUS_NEEDED 369s (process:1904): libfprint-device-DEBUG: 00:53:38.820: Device reported enroll progress, reported 5 of 5 have been completed 369s (process:1904): libfprint-device-DEBUG: 00:53:38.820: Device reported enroll completion 369s (process:1904): libfprint-device-DEBUG: 00:53:38.820: Device reported finger status change: FP_FINGER_STATUS_NONE 369s (process:1904): libfprint-device-DEBUG: 00:53:38.820: Print for finger FP_FINGER_LEFT_LITTLE enrolled 369s (process:1904): libfprint-device-DEBUG: 00:53:38.820: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 369s (process:1904): libfprint-device-DEBUG: 00:53:38.820: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 369s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:38.821: Got a new connection! 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.821: Got instructions of length 16 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.821: Received command SET_KEEP_ALIVE 0 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.821: Keep alive toggled: 0 369s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:38.821: Got a new connection! 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.821: Got instructions of length 19 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.821: Received command SET_ENROLL_STAGES 5 369s (process:1904): libfprint-device-DEBUG: 00:53:38.821: Device reported close completion 369s (process:1904): libfprint-device-DEBUG: 00:53:38.821: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 369s (process:1904): libfprint-device-DEBUG: 00:53:38.821: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 369s Enroll done 369s ok 369s test_finger_status (__main__.VirtualDevice.test_finger_status) ... (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.821: 7399786882561: ../libfprint/drivers/virtual-device.c:387 369s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:38.821: 7399786882572: ../libfprint/drivers/virtual-device-listener.c:153 369s (process:1904): libfprint-device-DEBUG: 00:53:38.821: Device reported open completion 369s (process:1904): libfprint-device-DEBUG: 00:53:38.821: Completing action FPI_DEVICE_ACTION_OPEN in idle! 369s (process:1904): libfprint-device-DEBUG: 00:53:38.821: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 369s (process:1904): libfprint-device-DEBUG: 00:53:38.821: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 369s (process:1904): libfprint-device-DEBUG: 00:53:38.821: Device reported finger status change: FP_FINGER_STATUS_NEEDED 369s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:38.822: Got a new connection! 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.822: Got instructions of length 8 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.822: Received command FINGER 1 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.822: Processing command FINGER 1 369s (process:1904): libfprint-device-DEBUG: 00:53:38.822: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 369s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:38.822: Got a new connection! 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.822: Got instructions of length 8 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.822: Received command FINGER 0 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.822: Processing command FINGER 0 369s (process:1904): libfprint-device-DEBUG: 00:53:38.822: Device reported finger status change: FP_FINGER_STATUS_NEEDED 369s (process:1904): libfprint-device-DEBUG: 00:53:38.822: Idle cancelling on ongoing operation! 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.822: Got cancellation! 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.822: Virtual device scan failed with error: Operation was cancelled 369s (process:1904): libfprint-device-DEBUG: 00:53:38.822: Device reported verify completion 369s (process:1904): libfprint-device-DEBUG: 00:53:38.822: Device reported finger status change: FP_FINGER_STATUS_NONE 369s (process:1904): libfprint-device-DEBUG: 00:53:38.822: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 369s (process:1904): libfprint-device-DEBUG: 00:53:38.822: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 369s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:38.822: Got a new connection! 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.822: Got instructions of length 16 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.822: Received command SET_KEEP_ALIVE 0 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.822: Keep alive toggled: 0 369s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:38.822: Got a new connection! 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.822: Got instructions of length 19 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.822: Received command SET_ENROLL_STAGES 5 369s (process:1904): libfprint-device-DEBUG: 00:53:38.823: Device reported close completion 369s (process:1904): libfprint-device-DEBUG: 00:53:38.823: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 369s (process:1904): libfprint-device-DEBUG: 00:53:38.823: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 369s ok 369s test_finger_status_after_sleep (__main__.VirtualDevice.test_finger_status_after_sleep) ... (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.823: 7399786884112: ../libfprint/drivers/virtual-device.c:387 369s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:38.823: 7399786884122: ../libfprint/drivers/virtual-device-listener.c:153 369s (process:1904): libfprint-device-DEBUG: 00:53:38.823: Device reported open completion 369s (process:1904): libfprint-device-DEBUG: 00:53:38.823: Completing action FPI_DEVICE_ACTION_OPEN in idle! 369s (process:1904): libfprint-device-DEBUG: 00:53:38.823: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 369s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:38.823: Got a new connection! 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.823: Got instructions of length 8 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.823: Received command SLEEP 10 369s (process:1904): libfprint-device-DEBUG: 00:53:38.823: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.823: Processing command SLEEP 10 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.823: Sleeping 10ms 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.833: Sleeping completed 369s (process:1904): libfprint-device-DEBUG: 00:53:38.833: Device reported finger status change: FP_FINGER_STATUS_NEEDED 369s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:38.834: Got a new connection! 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.834: Got instructions of length 8 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.834: Received command FINGER 1 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.834: Processing command FINGER 1 369s (process:1904): libfprint-device-DEBUG: 00:53:38.834: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 369s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:38.834: Got a new connection! 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.834: Got instructions of length 8 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.834: Received command FINGER 0 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.834: Processing command FINGER 0 369s (process:1904): libfprint-device-DEBUG: 00:53:38.834: Device reported finger status change: FP_FINGER_STATUS_NEEDED 369s (process:1904): libfprint-device-DEBUG: 00:53:38.834: Idle cancelling on ongoing operation! 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.834: Got cancellation! 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.834: Virtual device scan failed with error: Operation was cancelled 369s (process:1904): libfprint-device-DEBUG: 00:53:38.834: Device reported verify completion 369s (process:1904): libfprint-device-DEBUG: 00:53:38.834: Device reported finger status change: FP_FINGER_STATUS_NONE 369s (process:1904): libfprint-device-DEBUG: 00:53:38.834: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 369s (process:1904): libfprint-device-DEBUG: 00:53:38.834: Updated temperature model after 0.01 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 369s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:38.834: Got a new connection! 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.834: Got instructions of length 16 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.834: Received command SET_KEEP_ALIVE 0 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.834: Keep alive toggled: 0 369s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:38.835: Got a new connection! 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.835: Got instructions of length 19 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.835: Received command SET_ENROLL_STAGES 5 369s (process:1904): libfprint-device-DEBUG: 00:53:38.835: Device reported close completion 369s (process:1904): libfprint-device-DEBUG: 00:53:38.835: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 369s (process:1904): libfprint-device-DEBUG: 00:53:38.835: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 369s ok 369s test_identify_unsupported (__main__.VirtualDevice.test_identify_unsupported) ... (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.835: 7399786896295: ../libfprint/drivers/virtual-device.c:387 369s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:38.835: 7399786896306: ../libfprint/drivers/virtual-device-listener.c:153 369s (process:1904): libfprint-device-DEBUG: 00:53:38.835: Device reported open completion 369s (process:1904): libfprint-device-DEBUG: 00:53:38.835: Completing action FPI_DEVICE_ACTION_OPEN in idle! 369s (process:1904): libfprint-device-DEBUG: 00:53:38.835: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 369s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:38.836: Got a new connection! 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.836: Got instructions of length 16 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.836: Received command SET_KEEP_ALIVE 0 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.836: Keep alive toggled: 0 369s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:38.836: Got a new connection! 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.836: Got instructions of length 19 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.836: Received command SET_ENROLL_STAGES 5 369s (process:1904): libfprint-device-DEBUG: 00:53:38.836: Device reported close completion 369s (process:1904): libfprint-device-DEBUG: 00:53:38.836: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 369s (process:1904): libfprint-device-DEBUG: 00:53:38.836: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 369s ok 369s test_open_error (__main__.VirtualDevice.test_open_error) ... (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.836: 7399786897508: ../libfprint/drivers/virtual-device.c:387 369s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:38.836: 7399786897519: ../libfprint/drivers/virtual-device-listener.c:153 369s (process:1904): libfprint-device-DEBUG: 00:53:38.836: Device reported open completion 369s (process:1904): libfprint-device-DEBUG: 00:53:38.836: Completing action FPI_DEVICE_ACTION_OPEN in idle! 369s (process:1904): libfprint-device-DEBUG: 00:53:38.836: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 369s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:38.836: Got a new connection! 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.836: Got instructions of length 16 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.837: Received command IGNORED_COMMAND 369s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:38.837: Got a new connection! 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.837: Got instructions of length 7 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.837: Received command ERROR 5 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.837: Processing command IGNORED_COMMAND 369s (process:1904): libfprint-device-DEBUG: 00:53:38.837: Device reported close completion 369s (process:1904): libfprint-device-DEBUG: 00:53:38.837: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 369s (process:1904): libfprint-device-DEBUG: 00:53:38.837: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.837: 7399786898502: ../libfprint/drivers/virtual-device.c:387 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.837: Processing command ERROR 5 369s (process:1904): libfprint-device-DEBUG: 00:53:38.837: Device reported open completion 369s (process:1904): libfprint-device-DEBUG: 00:53:38.837: Completing action FPI_DEVICE_ACTION_OPEN in idle! 369s (process:1904): libfprint-device-DEBUG: 00:53:38.837: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 369s ok 369s test_open_error_with_keep_alive (__main__.VirtualDevice.test_open_error_with_keep_alive) ... (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.837: 7399786898699: ../libfprint/drivers/virtual-device.c:387 369s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:38.837: 7399786898716: ../libfprint/drivers/virtual-device-listener.c:153 369s (process:1904): libfprint-device-DEBUG: 00:53:38.837: Device reported open completion 369s (process:1904): libfprint-device-DEBUG: 00:53:38.837: Completing action FPI_DEVICE_ACTION_OPEN in idle! 369s (process:1904): libfprint-device-DEBUG: 00:53:38.838: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 369s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:38.838: Got a new connection! 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.838: Got instructions of length 16 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.838: Received command SET_KEEP_ALIVE 1 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.838: Keep alive toggled: 1 369s (process:1904): libfprint-device-DEBUG: 00:53:38.838: Device reported close completion 369s (process:1904): libfprint-device-DEBUG: 00:53:38.838: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 369s (process:1904): libfprint-device-DEBUG: 00:53:38.838: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 369s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:38.838: Got a new connection! 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.838: Got instructions of length 7 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.838: Received command ERROR 5 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.838: 7399786899577: ../libfprint/drivers/virtual-device.c:387 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.838: Processing command ERROR 5 369s (process:1904): libfprint-device-DEBUG: 00:53:38.838: Device reported open completion 369s (process:1904): libfprint-device-DEBUG: 00:53:38.838: Completing action FPI_DEVICE_ACTION_OPEN in idle! 369s (process:1904): libfprint-device-DEBUG: 00:53:38.838: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 369s ok 369s test_quick_enroll (__main__.VirtualDevice.test_quick_enroll) ... (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.838: 7399786899747: ../libfprint/drivers/virtual-device.c:387 369s (process:1904): libfprint-device-DEBUG: 00:53:38.838: Device reported open completion 369s (process:1904): libfprint-device-DEBUG: 00:53:38.838: Completing action FPI_DEVICE_ACTION_OPEN in idle! 369s (process:1904): libfprint-device-DEBUG: 00:53:38.838: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 369s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:38.838: Got a new connection! 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.839: Got instructions of length 19 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.839: Received command SET_ENROLL_STAGES 1 369s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:38.839: Got a new connection! 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.839: Got instructions of length 14 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.839: Received command SCAN testprint 369s (process:1904): libfprint-device-DEBUG: 00:53:38.839: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.839: Processing command SCAN testprint 369s (process:1904): libfprint-device-DEBUG: 00:53:38.839: Device reported finger status change: FP_FINGER_STATUS_NEEDED 369s (process:1904): libfprint-device-DEBUG: 00:53:38.839: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 369s (process:1904): libfprint-device-DEBUG: 00:53:38.839: Device reported finger status change: FP_FINGER_STATUS_NEEDED 369s (process:1904): libfprint-device-DEBUG: 00:53:38.839: Device reported enroll progress, reported 1 of 1 have been completed 369s (process:1904): libfprint-device-DEBUG: 00:53:38.839: Device reported enroll completion 369s (process:1904): libfprint-device-DEBUG: 00:53:38.839: Device reported finger status change: FP_FINGER_STATUS_NONE 369s (process:1904): libfprint-device-DEBUG: 00:53:38.839: Print for finger FP_FINGER_LEFT_LITTLE enrolled 369s (process:1904): libfprint-device-DEBUG: 00:53:38.839: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 369s (process:1904): libfprint-device-DEBUG: 00:53:38.839: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 369s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:38.839: Got a new connection! 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.839: Got instructions of length 16 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.839: Received command SET_KEEP_ALIVE 0 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.839: Keep alive toggled: 0 369s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:38.840: Got a new connection! 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.840: Got instructions of length 19 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.840: Received command SET_ENROLL_STAGES 5 369s (process:1904): libfprint-device-DEBUG: 00:53:38.840: Device reported close completion 369s (process:1904): libfprint-device-DEBUG: 00:53:38.840: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 369s (process:1904): libfprint-device-DEBUG: 00:53:38.840: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 369s Enroll done 369s ok 369s (process:1904): libfprint-context-DEBUG: 00:53:38.841: Initializing FpContext (libfprint version 1.94.8+tod1) 369s (process:1904): libfprint-tod-DEBUG: 00:53:38.841: Impossible to load the shared drivers dir Error opening directory “/usr/lib/arm-linux-gnueabihf/libfprint-2/tod-1”: No such file or directory 369s (process:1904): libfprint-context-DEBUG: 00:53:38.843: No driver found for USB device 1D6B:0003 369s (process:1904): libfprint-context-DEBUG: 00:53:38.843: No driver found for USB device 0627:0001 369s (process:1904): libfprint-context-DEBUG: 00:53:38.843: No driver found for USB device 1D6B:0002 369s (process:1904): libfprint-context-DEBUG: 00:53:38.843: Found virtual environment device: FP_VIRTUAL_DEVICE, /tmp/libfprint-loyeg94r/virtual-device.socket 369s (process:1904): libfprint-context-DEBUG: 00:53:38.843: created 369s (process:1904): libfprint-device-DEBUG: 00:53:38.844: Device reported probe completion 369s (process:1904): libfprint-device-DEBUG: 00:53:38.844: Completing action FPI_DEVICE_ACTION_PROBE in idle! 369s (process:1904): libfprint-device-DEBUG: 00:53:38.844: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 369s test_capture (__main__.VirtualDeviceBusyDeviceOperations.test_capture) ... (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.844: 7399786905734: ../libfprint/drivers/virtual-device.c:387 369s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:38.844: 7399786905745: ../libfprint/drivers/virtual-device-listener.c:153 369s (process:1904): libfprint-device-DEBUG: 00:53:38.844: Device reported open completion 369s (process:1904): libfprint-device-DEBUG: 00:53:38.844: Completing action FPI_DEVICE_ACTION_OPEN in idle! 369s (process:1904): libfprint-device-DEBUG: 00:53:38.844: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 369s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:38.845: Got a new connection! 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.845: Got instructions of length 9 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.845: Received command SLEEP 200 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.845: Processing command SLEEP 200 369s (process:1904): libfprint-virtual_device-DEBUG: 00:53:38.845: Sleeping 200ms 370s (process:1904): libfprint-virtual_device-DEBUG: 00:53:39.045: Sleeping completed 370s (process:1904): libfprint-device-DEBUG: 00:53:39.045: Device reported close completion 370s (process:1904): libfprint-device-DEBUG: 00:53:39.045: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 370s (process:1904): libfprint-device-DEBUG: 00:53:39.045: Updated temperature model after 0.20 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 370s ok 370s test_close (__main__.VirtualDeviceBusyDeviceOperations.test_close) ... (process:1904): libfprint-virtual_device-DEBUG: 00:53:39.045: 7399787106887: ../libfprint/drivers/virtual-device.c:387 370s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:39.045: 7399787106899: ../libfprint/drivers/virtual-device-listener.c:153 370s (process:1904): libfprint-device-DEBUG: 00:53:39.046: Device reported open completion 370s (process:1904): libfprint-device-DEBUG: 00:53:39.046: Completing action FPI_DEVICE_ACTION_OPEN in idle! 370s (process:1904): libfprint-device-DEBUG: 00:53:39.046: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 370s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:39.046: Got a new connection! 370s (process:1904): libfprint-virtual_device-DEBUG: 00:53:39.046: Got instructions of length 9 370s (process:1904): libfprint-virtual_device-DEBUG: 00:53:39.046: Received command SLEEP 200 370s (process:1904): libfprint-virtual_device-DEBUG: 00:53:39.046: Processing command SLEEP 200 370s (process:1904): libfprint-virtual_device-DEBUG: 00:53:39.046: Sleeping 200ms 370s (process:1904): libfprint-virtual_device-DEBUG: 00:53:39.246: Sleeping completed 370s (process:1904): libfprint-device-DEBUG: 00:53:39.247: Device reported close completion 370s (process:1904): libfprint-device-DEBUG: 00:53:39.247: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 370s (process:1904): libfprint-device-DEBUG: 00:53:39.247: Updated temperature model after 0.20 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 370s ok 370s test_delete_print (__main__.VirtualDeviceBusyDeviceOperations.test_delete_print) ... (process:1904): libfprint-virtual_device-DEBUG: 00:53:39.247: 7399787308247: ../libfprint/drivers/virtual-device.c:387 370s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:39.247: 7399787308267: ../libfprint/drivers/virtual-device-listener.c:153 370s (process:1904): libfprint-device-DEBUG: 00:53:39.247: Device reported open completion 370s (process:1904): libfprint-device-DEBUG: 00:53:39.247: Completing action FPI_DEVICE_ACTION_OPEN in idle! 370s (process:1904): libfprint-device-DEBUG: 00:53:39.247: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 370s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:39.247: Got a new connection! 370s (process:1904): libfprint-virtual_device-DEBUG: 00:53:39.247: Got instructions of length 9 370s (process:1904): libfprint-virtual_device-DEBUG: 00:53:39.247: Received command SLEEP 200 370s (process:1904): libfprint-virtual_device-DEBUG: 00:53:39.247: Processing command SLEEP 200 370s (process:1904): libfprint-virtual_device-DEBUG: 00:53:39.247: Sleeping 200ms 370s (process:1904): libfprint-virtual_device-DEBUG: 00:53:39.448: Sleeping completed 370s (process:1904): libfprint-device-DEBUG: 00:53:39.448: Device reported close completion 370s (process:1904): libfprint-device-DEBUG: 00:53:39.448: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 370s (process:1904): libfprint-device-DEBUG: 00:53:39.448: Updated temperature model after 0.20 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 370s ok 370s test_enroll (__main__.VirtualDeviceBusyDeviceOperations.test_enroll) ... (process:1904): libfprint-virtual_device-DEBUG: 00:53:39.448: 7399787509543: ../libfprint/drivers/virtual-device.c:387 370s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:39.448: 7399787509555: ../libfprint/drivers/virtual-device-listener.c:153 370s (process:1904): libfprint-device-DEBUG: 00:53:39.448: Device reported open completion 370s (process:1904): libfprint-device-DEBUG: 00:53:39.448: Completing action FPI_DEVICE_ACTION_OPEN in idle! 370s (process:1904): libfprint-device-DEBUG: 00:53:39.448: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 370s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:39.449: Got a new connection! 370s (process:1904): libfprint-virtual_device-DEBUG: 00:53:39.449: Got instructions of length 9 370s (process:1904): libfprint-virtual_device-DEBUG: 00:53:39.449: Received command SLEEP 200 370s (process:1904): libfprint-virtual_device-DEBUG: 00:53:39.449: Processing command SLEEP 200 370s (process:1904): libfprint-virtual_device-DEBUG: 00:53:39.449: Sleeping 200ms 370s (process:1904): libfprint-virtual_device-DEBUG: 00:53:39.649: Sleeping completed 370s (process:1904): libfprint-device-DEBUG: 00:53:39.649: Device reported close completion 370s (process:1904): libfprint-device-DEBUG: 00:53:39.649: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 370s (process:1904): libfprint-device-DEBUG: 00:53:39.649: Updated temperature model after 0.20 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 370s ok 370s test_identify (__main__.VirtualDeviceBusyDeviceOperations.test_identify) ... (process:1904): libfprint-virtual_device-DEBUG: 00:53:39.649: 7399787710906: ../libfprint/drivers/virtual-device.c:387 370s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:39.649: 7399787710918: ../libfprint/drivers/virtual-device-listener.c:153 370s (process:1904): libfprint-device-DEBUG: 00:53:39.650: Device reported open completion 370s (process:1904): libfprint-device-DEBUG: 00:53:39.650: Completing action FPI_DEVICE_ACTION_OPEN in idle! 370s (process:1904): libfprint-device-DEBUG: 00:53:39.650: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 370s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:39.651: Got a new connection! 370s (process:1904): libfprint-virtual_device-DEBUG: 00:53:39.651: Got instructions of length 9 370s (process:1904): libfprint-virtual_device-DEBUG: 00:53:39.651: Received command SLEEP 200 370s (process:1904): libfprint-virtual_device-DEBUG: 00:53:39.651: Processing command SLEEP 200 370s (process:1904): libfprint-virtual_device-DEBUG: 00:53:39.651: Sleeping 200ms 370s (process:1904): libfprint-virtual_device-DEBUG: 00:53:39.851: Sleeping completed 370s (process:1904): libfprint-device-DEBUG: 00:53:39.851: Device reported close completion 370s (process:1904): libfprint-device-DEBUG: 00:53:39.851: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 370s (process:1904): libfprint-device-DEBUG: 00:53:39.851: Updated temperature model after 0.20 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 370s ok 370s test_list_prints (__main__.VirtualDeviceBusyDeviceOperations.test_list_prints) ... (process:1904): libfprint-virtual_device-DEBUG: 00:53:39.851: 7399787912805: ../libfprint/drivers/virtual-device.c:387 370s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:39.851: 7399787912820: ../libfprint/drivers/virtual-device-listener.c:153 370s (process:1904): libfprint-device-DEBUG: 00:53:39.852: Device reported open completion 370s (process:1904): libfprint-device-DEBUG: 00:53:39.852: Completing action FPI_DEVICE_ACTION_OPEN in idle! 370s (process:1904): libfprint-device-DEBUG: 00:53:39.852: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 370s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:39.852: Got a new connection! 370s (process:1904): libfprint-virtual_device-DEBUG: 00:53:39.852: Got instructions of length 9 370s (process:1904): libfprint-virtual_device-DEBUG: 00:53:39.852: Received command SLEEP 200 370s (process:1904): libfprint-virtual_device-DEBUG: 00:53:39.852: Processing command SLEEP 200 370s (process:1904): libfprint-virtual_device-DEBUG: 00:53:39.852: Sleeping 200ms 371s (process:1904): libfprint-virtual_device-DEBUG: 00:53:40.052: Sleeping completed 371s (process:1904): libfprint-device-DEBUG: 00:53:40.052: Device reported close completion 371s (process:1904): libfprint-device-DEBUG: 00:53:40.052: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 371s (process:1904): libfprint-device-DEBUG: 00:53:40.052: Updated temperature model after 0.20 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 371s ok 371s test_open (__main__.VirtualDeviceBusyDeviceOperations.test_open) ... (process:1904): libfprint-virtual_device-DEBUG: 00:53:40.053: 7399788114099: ../libfprint/drivers/virtual-device.c:387 371s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:40.053: 7399788114113: ../libfprint/drivers/virtual-device-listener.c:153 371s (process:1904): libfprint-device-DEBUG: 00:53:40.053: Device reported open completion 371s (process:1904): libfprint-device-DEBUG: 00:53:40.053: Completing action FPI_DEVICE_ACTION_OPEN in idle! 371s (process:1904): libfprint-device-DEBUG: 00:53:40.053: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 371s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:40.053: Got a new connection! 371s (process:1904): libfprint-virtual_device-DEBUG: 00:53:40.053: Got instructions of length 9 371s (process:1904): libfprint-virtual_device-DEBUG: 00:53:40.053: Received command SLEEP 200 371s (process:1904): libfprint-virtual_device-DEBUG: 00:53:40.053: Processing command SLEEP 200 371s (process:1904): libfprint-virtual_device-DEBUG: 00:53:40.053: Sleeping 200ms 371s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:40.053: Got a new connection! 371s (process:1904): libfprint-virtual_device-DEBUG: 00:53:40.053: Got instructions of length 16 371s (process:1904): libfprint-virtual_device-DEBUG: 00:53:40.053: Received command SET_KEEP_ALIVE 1 371s (process:1904): libfprint-virtual_device-DEBUG: 00:53:40.053: Keep alive toggled: 1 371s (process:1904): libfprint-virtual_device-DEBUG: 00:53:40.254: Sleeping completed 371s (process:1904): libfprint-device-DEBUG: 00:53:40.254: Device reported close completion 371s (process:1904): libfprint-device-DEBUG: 00:53:40.254: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 371s (process:1904): libfprint-device-DEBUG: 00:53:40.254: Updated temperature model after 0.20 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 371s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:40.254: Got a new connection! 371s (process:1904): libfprint-virtual_device-DEBUG: 00:53:40.254: Got instructions of length 9 371s (process:1904): libfprint-virtual_device-DEBUG: 00:53:40.254: Received command SLEEP 100 371s (process:1904): libfprint-virtual_device-DEBUG: 00:53:40.254: 7399788315522: ../libfprint/drivers/virtual-device.c:387 371s (process:1904): libfprint-virtual_device-DEBUG: 00:53:40.254: Processing command SLEEP 100 371s (process:1904): libfprint-virtual_device-DEBUG: 00:53:40.254: Sleeping 100ms 371s (process:1904): libfprint-virtual_device-DEBUG: 00:53:40.355: Sleeping completed 371s (process:1904): libfprint-virtual_device-DEBUG: 00:53:40.355: 7399788415968: ../libfprint/drivers/virtual-device.c:387 371s (process:1904): libfprint-device-DEBUG: 00:53:40.355: Device reported open completion 371s (process:1904): libfprint-device-DEBUG: 00:53:40.355: Completing action FPI_DEVICE_ACTION_OPEN in idle! 371s (process:1904): libfprint-device-DEBUG: 00:53:40.355: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 371s (process:1904): libfprint-device-DEBUG: 00:53:40.355: Device reported close completion 371s (process:1904): libfprint-device-DEBUG: 00:53:40.355: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 371s (process:1904): libfprint-device-DEBUG: 00:53:40.355: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 371s ok 371s test_verify (__main__.VirtualDeviceBusyDeviceOperations.test_verify) ... (process:1904): libfprint-virtual_device-DEBUG: 00:53:40.355: 7399788416292: ../libfprint/drivers/virtual-device.c:387 371s (process:1904): libfprint-device-DEBUG: 00:53:40.355: Device reported open completion 371s (process:1904): libfprint-device-DEBUG: 00:53:40.355: Completing action FPI_DEVICE_ACTION_OPEN in idle! 371s (process:1904): libfprint-device-DEBUG: 00:53:40.355: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 371s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:40.355: Got a new connection! 371s (process:1904): libfprint-virtual_device-DEBUG: 00:53:40.355: Got instructions of length 9 371s (process:1904): libfprint-virtual_device-DEBUG: 00:53:40.355: Received command SLEEP 200 371s (process:1904): libfprint-virtual_device-DEBUG: 00:53:40.355: Processing command SLEEP 200 371s (process:1904): libfprint-virtual_device-DEBUG: 00:53:40.355: Sleeping 200ms 371s (process:1904): libfprint-virtual_device-DEBUG: 00:53:40.556: Sleeping completed 371s (process:1904): libfprint-device-DEBUG: 00:53:40.556: Device reported close completion 371s (process:1904): libfprint-device-DEBUG: 00:53:40.556: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 371s (process:1904): libfprint-device-DEBUG: 00:53:40.556: Updated temperature model after 0.20 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 371s ok 371s (process:1904): libfprint-virtual_device-DEBUG: 00:53:40.556: 7399788617547: ../libfprint/drivers/virtual-device.c:752 371s (process:1904): libfprint-context-DEBUG: 00:53:40.557: Initializing FpContext (libfprint version 1.94.8+tod1) 371s (process:1904): libfprint-tod-DEBUG: 00:53:40.557: Impossible to load the shared drivers dir Error opening directory “/usr/lib/arm-linux-gnueabihf/libfprint-2/tod-1”: No such file or directory 371s (process:1904): libfprint-context-DEBUG: 00:53:40.559: No driver found for USB device 1D6B:0003 371s (process:1904): libfprint-context-DEBUG: 00:53:40.559: No driver found for USB device 0627:0001 371s (process:1904): libfprint-context-DEBUG: 00:53:40.559: No driver found for USB device 1D6B:0002 371s (process:1904): libfprint-context-DEBUG: 00:53:40.559: Found virtual environment device: FP_VIRTUAL_DEVICE, /tmp/libfprint-utfiotga/virtual-device.socket 371s (process:1904): libfprint-context-DEBUG: 00:53:40.559: created 371s (process:1904): libfprint-device-DEBUG: 00:53:40.560: Device reported probe completion 371s (process:1904): libfprint-device-DEBUG: 00:53:40.560: Completing action FPI_DEVICE_ACTION_PROBE in idle! 371s (process:1904): libfprint-device-DEBUG: 00:53:40.560: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 371s test_capture (__main__.VirtualDeviceClosed.test_capture) ... (process:1904): libfprint-virtual_device-DEBUG: 00:53:40.560: 7399788621873: ../libfprint/drivers/virtual-device.c:387 371s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:40.560: 7399788621886: ../libfprint/drivers/virtual-device-listener.c:153 371s (process:1904): libfprint-device-DEBUG: 00:53:40.561: Device reported open completion 371s (process:1904): libfprint-device-DEBUG: 00:53:40.561: Completing action FPI_DEVICE_ACTION_OPEN in idle! 371s (process:1904): libfprint-device-DEBUG: 00:53:40.561: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 371s (process:1904): libfprint-device-DEBUG: 00:53:40.561: Device reported close completion 371s (process:1904): libfprint-device-DEBUG: 00:53:40.561: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 371s (process:1904): libfprint-device-DEBUG: 00:53:40.561: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 371s ok 371s test_close (__main__.VirtualDeviceClosed.test_close) ... (process:1904): libfprint-virtual_device-DEBUG: 00:53:40.561: 7399788622464: ../libfprint/drivers/virtual-device.c:387 371s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:40.561: 7399788622476: ../libfprint/drivers/virtual-device-listener.c:153 371s (process:1904): libfprint-device-DEBUG: 00:53:40.561: Device reported open completion 371s (process:1904): libfprint-device-DEBUG: 00:53:40.561: Completing action FPI_DEVICE_ACTION_OPEN in idle! 371s (process:1904): libfprint-device-DEBUG: 00:53:40.561: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 371s (process:1904): libfprint-device-DEBUG: 00:53:40.561: Device reported close completion 371s (process:1904): libfprint-device-DEBUG: 00:53:40.561: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 371s (process:1904): libfprint-device-DEBUG: 00:53:40.561: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 371s ok 371s test_delete_print (__main__.VirtualDeviceClosed.test_delete_print) ... (process:1904): libfprint-virtual_device-DEBUG: 00:53:40.561: 7399788622848: ../libfprint/drivers/virtual-device.c:387 371s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:40.561: 7399788622857: ../libfprint/drivers/virtual-device-listener.c:153 371s (process:1904): libfprint-device-DEBUG: 00:53:40.562: Device reported open completion 371s (process:1904): libfprint-device-DEBUG: 00:53:40.562: Completing action FPI_DEVICE_ACTION_OPEN in idle! 371s (process:1904): libfprint-device-DEBUG: 00:53:40.562: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 371s (process:1904): libfprint-device-DEBUG: 00:53:40.562: Device reported close completion 371s (process:1904): libfprint-device-DEBUG: 00:53:40.562: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 371s (process:1904): libfprint-device-DEBUG: 00:53:40.562: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 371s ok 371s test_enroll (__main__.VirtualDeviceClosed.test_enroll) ... (process:1904): libfprint-virtual_device-DEBUG: 00:53:40.562: 7399788623341: ../libfprint/drivers/virtual-device.c:387 371s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:40.562: 7399788623350: ../libfprint/drivers/virtual-device-listener.c:153 371s (process:1904): libfprint-device-DEBUG: 00:53:40.562: Device reported open completion 371s (process:1904): libfprint-device-DEBUG: 00:53:40.562: Completing action FPI_DEVICE_ACTION_OPEN in idle! 371s (process:1904): libfprint-device-DEBUG: 00:53:40.562: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 371s (process:1904): libfprint-device-DEBUG: 00:53:40.562: Device reported close completion 371s (process:1904): libfprint-device-DEBUG: 00:53:40.562: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 371s (process:1904): libfprint-device-DEBUG: 00:53:40.562: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 371s ok 371s test_identify (__main__.VirtualDeviceClosed.test_identify) ... (process:1904): libfprint-virtual_device-DEBUG: 00:53:40.562: 7399788623727: ../libfprint/drivers/virtual-device.c:387 371s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:40.562: 7399788623737: ../libfprint/drivers/virtual-device-listener.c:153 371s (process:1904): libfprint-device-DEBUG: 00:53:40.562: Device reported open completion 371s (process:1904): libfprint-device-DEBUG: 00:53:40.562: Completing action FPI_DEVICE_ACTION_OPEN in idle! 371s (process:1904): libfprint-device-DEBUG: 00:53:40.562: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 371s (process:1904): libfprint-device-DEBUG: 00:53:40.562: Device reported close completion 371s (process:1904): libfprint-device-DEBUG: 00:53:40.563: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 371s (process:1904): libfprint-device-DEBUG: 00:53:40.563: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 371s ok 371s test_list_prints (__main__.VirtualDeviceClosed.test_list_prints) ... (process:1904): libfprint-virtual_device-DEBUG: 00:53:40.563: 7399788624105: ../libfprint/drivers/virtual-device.c:387 371s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:40.563: 7399788624117: ../libfprint/drivers/virtual-device-listener.c:153 371s (process:1904): libfprint-device-DEBUG: 00:53:40.563: Device reported open completion 371s (process:1904): libfprint-device-DEBUG: 00:53:40.563: Completing action FPI_DEVICE_ACTION_OPEN in idle! 371s (process:1904): libfprint-device-DEBUG: 00:53:40.563: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 371s (process:1904): libfprint-device-DEBUG: 00:53:40.563: Device reported close completion 371s (process:1904): libfprint-device-DEBUG: 00:53:40.563: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 371s (process:1904): libfprint-device-DEBUG: 00:53:40.563: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 371s ok 371s test_verify (__main__.VirtualDeviceClosed.test_verify) ... (process:1904): libfprint-virtual_device-DEBUG: 00:53:40.563: 7399788624455: ../libfprint/drivers/virtual-device.c:387 371s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:40.563: 7399788624466: ../libfprint/drivers/virtual-device-listener.c:153 371s (process:1904): libfprint-device-DEBUG: 00:53:40.563: Device reported open completion 371s (process:1904): libfprint-device-DEBUG: 00:53:40.563: Completing action FPI_DEVICE_ACTION_OPEN in idle! 371s (process:1904): libfprint-device-DEBUG: 00:53:40.563: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 371s (process:1904): libfprint-device-DEBUG: 00:53:40.563: Device reported close completion 371s (process:1904): libfprint-device-DEBUG: 00:53:40.563: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 371s (process:1904): libfprint-device-DEBUG: 00:53:40.563: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 371s ok 371s (process:1904): libfprint-virtual_device-DEBUG: 00:53:40.564: 7399788624999: ../libfprint/drivers/virtual-device.c:752 371s (process:1904): libfprint-context-DEBUG: 00:53:40.564: Initializing FpContext (libfprint version 1.94.8+tod1) 371s (process:1904): libfprint-tod-DEBUG: 00:53:40.564: Impossible to load the shared drivers dir Error opening directory “/usr/lib/arm-linux-gnueabihf/libfprint-2/tod-1”: No such file or directory 371s (process:1904): libfprint-context-DEBUG: 00:53:40.566: No driver found for USB device 1D6B:0003 371s (process:1904): libfprint-context-DEBUG: 00:53:40.566: No driver found for USB device 0627:0001 371s (process:1904): libfprint-context-DEBUG: 00:53:40.566: No driver found for USB device 1D6B:0002 371s (process:1904): libfprint-context-DEBUG: 00:53:40.566: Found virtual environment device: FP_VIRTUAL_DEVICE, /tmp/libfprint-utfiotga/virtual-device.socket 371s (process:1904): libfprint-context-DEBUG: 00:53:40.566: created 371s (process:1904): libfprint-context-DEBUG: 00:53:40.566: Found virtual environment device: FP_VIRTUAL_DEVICE_STORAGE, /tmp/libfprint-nrcvdau3/virtual-device-storage.socket 371s (process:1904): libfprint-context-DEBUG: 00:53:40.566: created 371s (process:1904): libfprint-device-DEBUG: 00:53:40.567: Device reported probe completion 371s (process:1904): libfprint-device-DEBUG: 00:53:40.567: Device reported probe completion 371s (process:1904): libfprint-device-DEBUG: 00:53:40.567: Completing action FPI_DEVICE_ACTION_PROBE in idle! 371s (process:1904): libfprint-device-DEBUG: 00:53:40.567: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 371s (process:1904): libfprint-device-DEBUG: 00:53:40.567: Completing action FPI_DEVICE_ACTION_PROBE in idle! 371s (process:1904): libfprint-device-DEBUG: 00:53:40.567: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 371s test_capture_unsupported (__main__.VirtualDeviceStorage.test_capture_unsupported) ... (process:1904): libfprint-virtual_device-DEBUG: 00:53:40.568: 7399788629282: ../libfprint/drivers/virtual-device.c:387 371s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:40.568: 7399788629302: ../libfprint/drivers/virtual-device-listener.c:153 371s (process:1904): libfprint-device-DEBUG: 00:53:40.568: Device reported open completion 371s (process:1904): libfprint-device-DEBUG: 00:53:40.568: Completing action FPI_DEVICE_ACTION_OPEN in idle! 371s (process:1904): libfprint-device-DEBUG: 00:53:40.568: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 371s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:40.568: Got a new connection! 371s (process:1904): libfprint-virtual_device-DEBUG: 00:53:40.568: Got instructions of length 5 371s (process:1904): libfprint-virtual_device-DEBUG: 00:53:40.568: Received command CONT 371s (process:1904): libfprint-virtual_device-DEBUG: 00:53:40.569: Processing command CONT 371s (process:1904): libfprint-device-DEBUG: 00:53:40.569: Device reported deletion completion 371s (process:1904): libfprint-device-DEBUG: 00:53:40.569: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 371s (process:1904): libfprint-device-DEBUG: 00:53:40.569: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 371s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:40.569: Got a new connection! 371s (process:1904): libfprint-virtual_device-DEBUG: 00:53:40.569: Got instructions of length 16 371s (process:1904): libfprint-virtual_device-DEBUG: 00:53:40.569: Received command SET_KEEP_ALIVE 0 371s (process:1904): libfprint-virtual_device-DEBUG: 00:53:40.569: Keep alive toggled: 0 371s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:40.569: Got a new connection! 371s (process:1904): libfprint-virtual_device-DEBUG: 00:53:40.569: Got instructions of length 19 371s (process:1904): libfprint-virtual_device-DEBUG: 00:53:40.569: Received command SET_ENROLL_STAGES 5 371s (process:1904): libfprint-device-DEBUG: 00:53:40.569: Device reported close completion 371s (process:1904): libfprint-device-DEBUG: 00:53:40.569: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 371s (process:1904): libfprint-device-DEBUG: 00:53:40.569: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 371s ok 371s test_change_enroll_stages (__main__.VirtualDeviceStorage.test_change_enroll_stages) ... (process:1904): libfprint-virtual_device-DEBUG: 00:53:40.569: 7399788630709: ../libfprint/drivers/virtual-device.c:387 371s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:40.569: 7399788630720: ../libfprint/drivers/virtual-device-listener.c:153 371s (process:1904): libfprint-device-DEBUG: 00:53:40.569: Device reported open completion 371s (process:1904): libfprint-device-DEBUG: 00:53:40.570: Completing action FPI_DEVICE_ACTION_OPEN in idle! 371s (process:1904): libfprint-device-DEBUG: 00:53:40.570: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 371s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:40.570: Got a new connection! 371s (process:1904): libfprint-virtual_device-DEBUG: 00:53:40.570: Got instructions of length 20 371s (process:1904): libfprint-virtual_device-DEBUG: 00:53:40.570: Received command SET_ENROLL_STAGES 20 371s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:40.570: Got a new connection! 371s (process:1904): libfprint-virtual_device-DEBUG: 00:53:40.570: Got instructions of length 19 371s (process:1904): libfprint-virtual_device-DEBUG: 00:53:40.570: Received command SET_ENROLL_STAGES 1 371s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:40.570: Got a new connection! 371s (process:1904): libfprint-virtual_device-DEBUG: 00:53:40.570: Got instructions of length 19 371s (process:1904): libfprint-virtual_device-DEBUG: 00:53:40.570: Received command SET_ENROLL_STAGES 0 371s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:40.571: Got a new connection! 371s (process:1904): libfprint-virtual_device-DEBUG: 00:53:40.571: Got instructions of length 5 371s (process:1904): libfprint-virtual_device-DEBUG: 00:53:40.571: Received command CONT 371s (process:1904): libfprint-virtual_device-DEBUG: 00:53:40.571: Processing command CONT 371s (process:1904): libfprint-device-DEBUG: 00:53:40.571: Device reported deletion completion 371s (process:1904): libfprint-device-DEBUG: 00:53:40.571: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 371s (process:1904): libfprint-device-DEBUG: 00:53:40.571: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 371s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:40.571: Got a new connection! 371s (process:1904): libfprint-virtual_device-DEBUG: 00:53:40.571: Got instructions of length 16 371s (process:1904): libfprint-virtual_device-DEBUG: 00:53:40.571: Received command SET_KEEP_ALIVE 0 371s (process:1904): libfprint-virtual_device-DEBUG: 00:53:40.571: Keep alive toggled: 0 371s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:40.571: Got a new connection! 371s (process:1904): libfprint-virtual_device-DEBUG: 00:53:40.571: Got instructions of length 19 371s (process:1904): libfprint-virtual_device-DEBUG: 00:53:40.571: Received command SET_ENROLL_STAGES 5 371s (process:1904): libfprint-device-DEBUG: 00:53:40.571: Device reported close completion 371s (process:1904): libfprint-device-DEBUG: 00:53:40.571: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 371s (process:1904): libfprint-device-DEBUG: 00:53:40.571: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 371s ok 371s test_change_scan_type (__main__.VirtualDeviceStorage.test_change_scan_type) ... (process:1904): libfprint-virtual_device-DEBUG: 00:53:40.571: 7399788632874: ../libfprint/drivers/virtual-device.c:387 371s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:40.571: 7399788632885: ../libfprint/drivers/virtual-device-listener.c:153 371s (process:1904): libfprint-device-DEBUG: 00:53:40.572: Device reported open completion 371s (process:1904): libfprint-device-DEBUG: 00:53:40.572: Completing action FPI_DEVICE_ACTION_OPEN in idle! 371s (process:1904): libfprint-device-DEBUG: 00:53:40.572: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 371s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:40.572: Got a new connection! 371s (process:1904): libfprint-virtual_device-DEBUG: 00:53:40.572: Got instructions of length 19 371s (process:1904): libfprint-virtual_device-DEBUG: 00:53:40.572: Received command SET_SCAN_TYPE press 371s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:40.572: Got a new connection! 371s (process:1904): libfprint-virtual_device-DEBUG: 00:53:40.572: Got instructions of length 19 371s (process:1904): libfprint-virtual_device-DEBUG: 00:53:40.572: Received command SET_SCAN_TYPE swipe 371s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:40.572: Got a new connection! 371s (process:1904): libfprint-virtual_device-DEBUG: 00:53:40.572: Got instructions of length 25 371s (process:1904): libfprint-virtual_device-DEBUG: 00:53:40.572: Received command SET_SCAN_TYPE eye-contact 371s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:40.573: Got a new connection! 371s (process:1904): libfprint-virtual_device-DEBUG: 00:53:40.573: Got instructions of length 5 371s (process:1904): libfprint-virtual_device-DEBUG: 00:53:40.573: Received command CONT 371s (process:1904): libfprint-virtual_device-DEBUG: 00:53:40.573: Processing command CONT 371s (process:1904): libfprint-device-DEBUG: 00:53:40.573: Device reported deletion completion 371s (process:1904): libfprint-device-DEBUG: 00:53:40.573: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 371s (process:1904): libfprint-device-DEBUG: 00:53:40.573: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 371s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:40.573: Got a new connection! 371s (process:1904): libfprint-virtual_device-DEBUG: 00:53:40.573: Got instructions of length 16 371s (process:1904): libfprint-virtual_device-DEBUG: 00:53:40.573: Received command SET_KEEP_ALIVE 0 371s (process:1904): libfprint-virtual_device-DEBUG: 00:53:40.573: Keep alive toggled: 0 371s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:40.573: Got a new connection! 371s (process:1904): libfprint-virtual_device-DEBUG: 00:53:40.573: Got instructions of length 19 371s (process:1904): libfprint-virtual_device-DEBUG: 00:53:40.573: Received command SET_ENROLL_STAGES 5 371s (process:1904): libfprint-device-DEBUG: 00:53:40.573: Device reported close completion 371s (process:1904): libfprint-device-DEBUG: 00:53:40.573: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 371s (process:1904): libfprint-device-DEBUG: 00:53:40.573: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 371s ok 371s test_clear_storage (__main__.VirtualDeviceStorage.test_clear_storage) ... (process:1904): libfprint-virtual_device-DEBUG: 00:53:40.574: 7399788634941: ../libfprint/drivers/virtual-device.c:387 371s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:40.574: 7399788634951: ../libfprint/drivers/virtual-device-listener.c:153 371s (process:1904): libfprint-device-DEBUG: 00:53:40.574: Device reported open completion 371s (process:1904): libfprint-device-DEBUG: 00:53:40.574: Completing action FPI_DEVICE_ACTION_OPEN in idle! 371s (process:1904): libfprint-device-DEBUG: 00:53:40.574: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 371s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:40.574: Got a new connection! 371s (process:1904): libfprint-virtual_device-DEBUG: 00:53:40.574: Got instructions of length 9 371s (process:1904): libfprint-virtual_device-DEBUG: 00:53:40.574: Received command INSERT p1 371s (process:1904): libfprint-virtual_device-DEBUG: 00:53:40.574: Processing command INSERT p1 372s (process:1904): libfprint-device-DEBUG: 00:53:41.075: Device reported listing completion 372s (process:1904): libfprint-device-DEBUG: 00:53:41.075: Completing action FPI_DEVICE_ACTION_LIST in idle! 372s (process:1904): libfprint-device-DEBUG: 00:53:41.075: Updated temperature model after 0.50 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 372s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:41.075: Got a new connection! 372s (process:1904): libfprint-virtual_device-DEBUG: 00:53:41.075: Got instructions of length 5 372s (process:1904): libfprint-virtual_device-DEBUG: 00:53:41.075: Received command CONT 372s (process:1904): libfprint-virtual_device-DEBUG: 00:53:41.075: Processing command CONT 372s (process:1904): libfprint-device-DEBUG: 00:53:41.075: Device reported deletion completion 372s (process:1904): libfprint-device-DEBUG: 00:53:41.075: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 372s (process:1904): libfprint-device-DEBUG: 00:53:41.075: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 372s (process:1904): libfprint-device-DEBUG: 00:53:41.576: Device reported listing completion 372s (process:1904): libfprint-device-DEBUG: 00:53:41.576: Completing action FPI_DEVICE_ACTION_LIST in idle! 372s (process:1904): libfprint-device-DEBUG: 00:53:41.576: Updated temperature model after 0.50 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 372s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:41.577: Got a new connection! 372s (process:1904): libfprint-virtual_device-DEBUG: 00:53:41.577: Got instructions of length 5 372s (process:1904): libfprint-virtual_device-DEBUG: 00:53:41.577: Received command CONT 372s (process:1904): libfprint-virtual_device-DEBUG: 00:53:41.577: Processing command CONT 372s (process:1904): libfprint-device-DEBUG: 00:53:41.577: Device reported deletion completion 372s (process:1904): libfprint-device-DEBUG: 00:53:41.577: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 372s (process:1904): libfprint-device-DEBUG: 00:53:41.577: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 372s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:41.577: Got a new connection! 372s (process:1904): libfprint-virtual_device-DEBUG: 00:53:41.577: Got instructions of length 16 372s (process:1904): libfprint-virtual_device-DEBUG: 00:53:41.577: Received command SET_KEEP_ALIVE 0 372s (process:1904): libfprint-virtual_device-DEBUG: 00:53:41.577: Keep alive toggled: 0 372s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:41.577: Got a new connection! 372s (process:1904): libfprint-virtual_device-DEBUG: 00:53:41.577: Got instructions of length 19 372s (process:1904): libfprint-virtual_device-DEBUG: 00:53:41.577: Received command SET_ENROLL_STAGES 5 372s (process:1904): libfprint-device-DEBUG: 00:53:41.577: Device reported close completion 372s (process:1904): libfprint-device-DEBUG: 00:53:41.577: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 372s (process:1904): libfprint-device-DEBUG: 00:53:41.577: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 372s 372s ok 372s test_clear_storage_error (__main__.VirtualDeviceStorage.test_clear_storage_error) ... (process:1904): libfprint-virtual_device-DEBUG: 00:53:41.578: 7399789639066: ../libfprint/drivers/virtual-device.c:387 372s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:41.578: 7399789639079: ../libfprint/drivers/virtual-device-listener.c:153 372s (process:1904): libfprint-device-DEBUG: 00:53:41.578: Device reported open completion 372s (process:1904): libfprint-device-DEBUG: 00:53:41.578: Completing action FPI_DEVICE_ACTION_OPEN in idle! 372s (process:1904): libfprint-device-DEBUG: 00:53:41.578: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 372s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:41.578: Got a new connection! 372s (process:1904): libfprint-virtual_device-DEBUG: 00:53:41.578: Got instructions of length 9 372s (process:1904): libfprint-virtual_device-DEBUG: 00:53:41.578: Received command INSERT p1 372s (process:1904): libfprint-virtual_device-DEBUG: 00:53:41.578: Processing command INSERT p1 373s Executing: libfprint-2/virtual-device.test 373s (process:1904): libfprint-device-DEBUG: 00:53:42.079: Device reported listing completion 373s (process:1904): libfprint-device-DEBUG: 00:53:42.079: Completing action FPI_DEVICE_ACTION_LIST in idle! 373s (process:1904): libfprint-device-DEBUG: 00:53:42.079: Updated temperature model after 0.50 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 373s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:42.079: Got a new connection! 373s (process:1904): libfprint-virtual_device-DEBUG: 00:53:42.079: Got instructions of length 7 373s (process:1904): libfprint-virtual_device-DEBUG: 00:53:42.079: Received command ERROR 5 373s (process:1904): libfprint-virtual_device-DEBUG: 00:53:42.079: Processing command ERROR 5 373s (process:1904): libfprint-device-DEBUG: 00:53:42.079: Device reported deletion completion 373s (process:1904): libfprint-device-DEBUG: 00:53:42.079: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 373s (process:1904): libfprint-device-DEBUG: 00:53:42.079: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 373s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:42.080: Got a new connection! 373s (process:1904): libfprint-virtual_device-DEBUG: 00:53:42.080: Got instructions of length 5 373s (process:1904): libfprint-virtual_device-DEBUG: 00:53:42.080: Received command CONT 373s (process:1904): libfprint-virtual_device-DEBUG: 00:53:42.080: Processing command CONT 373s (process:1904): libfprint-device-DEBUG: 00:53:42.080: Device reported deletion completion 373s (process:1904): libfprint-device-DEBUG: 00:53:42.080: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 373s (process:1904): libfprint-device-DEBUG: 00:53:42.080: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 373s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:42.080: Got a new connection! 373s (process:1904): libfprint-virtual_device-DEBUG: 00:53:42.080: Got instructions of length 16 373s (process:1904): libfprint-virtual_device-DEBUG: 00:53:42.080: Received command SET_KEEP_ALIVE 0 373s (process:1904): libfprint-virtual_device-DEBUG: 00:53:42.080: Keep alive toggled: 0 373s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:42.080: Got a new connection! 373s (process:1904): libfprint-virtual_device-DEBUG: 00:53:42.080: Got instructions of length 19 373s (process:1904): libfprint-virtual_device-DEBUG: 00:53:42.080: Received command SET_ENROLL_STAGES 5 373s (process:1904): libfprint-device-DEBUG: 00:53:42.080: Device reported close completion 373s (process:1904): libfprint-device-DEBUG: 00:53:42.080: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 373s (process:1904): libfprint-device-DEBUG: 00:53:42.080: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 373s 373s ok 373s test_close_error (__main__.VirtualDeviceStorage.test_close_error) ... (process:1904): libfprint-virtual_device-DEBUG: 00:53:42.080: 7399790141817: ../libfprint/drivers/virtual-device.c:387 373s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:42.080: 7399790141832: ../libfprint/drivers/virtual-device-listener.c:153 373s (process:1904): libfprint-device-DEBUG: 00:53:42.081: Device reported open completion 373s (process:1904): libfprint-device-DEBUG: 00:53:42.081: Completing action FPI_DEVICE_ACTION_OPEN in idle! 373s (process:1904): libfprint-device-DEBUG: 00:53:42.081: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 373s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:42.081: Got a new connection! 373s (process:1904): libfprint-virtual_device-DEBUG: 00:53:42.081: Got instructions of length 9 373s (process:1904): libfprint-virtual_device-DEBUG: 00:53:42.081: Received command SLEEP 100 373s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:42.081: Got a new connection! 373s (process:1904): libfprint-virtual_device-DEBUG: 00:53:42.081: Got instructions of length 7 373s (process:1904): libfprint-virtual_device-DEBUG: 00:53:42.081: Received command ERROR 4 373s (process:1904): libfprint-virtual_device-DEBUG: 00:53:42.081: Processing command SLEEP 100 373s (process:1904): libfprint-virtual_device-DEBUG: 00:53:42.081: Sleeping 100ms 373s (process:1904): libfprint-virtual_device-DEBUG: 00:53:42.181: Sleeping completed 373s (process:1904): libfprint-virtual_device-DEBUG: 00:53:42.181: Processing command ERROR 4 373s (process:1904): libfprint-device-DEBUG: 00:53:42.181: Device reported close completion 373s (process:1904): libfprint-device-DEBUG: 00:53:42.181: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 373s (process:1904): libfprint-device-DEBUG: 00:53:42.181: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 373s ok 373s test_close_while_opening (__main__.VirtualDeviceStorage.test_close_while_opening) ... (process:1904): libfprint-virtual_device-DEBUG: 00:53:42.182: 7399790243141: ../libfprint/drivers/virtual-device.c:387 373s (process:1904): libfprint-device-DEBUG: 00:53:42.182: Device reported open completion 373s (process:1904): libfprint-device-DEBUG: 00:53:42.182: Completing action FPI_DEVICE_ACTION_OPEN in idle! 373s (process:1904): libfprint-device-DEBUG: 00:53:42.182: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 373s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:42.182: Got a new connection! 373s (process:1904): libfprint-virtual_device-DEBUG: 00:53:42.182: Got instructions of length 16 373s (process:1904): libfprint-virtual_device-DEBUG: 00:53:42.182: Received command SET_KEEP_ALIVE 1 373s (process:1904): libfprint-virtual_device-DEBUG: 00:53:42.182: Keep alive toggled: 1 373s (process:1904): libfprint-device-DEBUG: 00:53:42.182: Device reported close completion 373s (process:1904): libfprint-device-DEBUG: 00:53:42.182: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 373s (process:1904): libfprint-device-DEBUG: 00:53:42.182: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 373s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:42.182: Got a new connection! 373s (process:1904): libfprint-virtual_device-DEBUG: 00:53:42.182: Got instructions of length 9 373s (process:1904): libfprint-virtual_device-DEBUG: 00:53:42.182: Received command SLEEP 500 373s (process:1904): libfprint-virtual_device-DEBUG: 00:53:42.182: 7399790243813: ../libfprint/drivers/virtual-device.c:387 373s (process:1904): libfprint-virtual_device-DEBUG: 00:53:42.182: Processing command SLEEP 500 373s (process:1904): libfprint-virtual_device-DEBUG: 00:53:42.182: Sleeping 500ms 373s (process:1904): libfprint-virtual_device-DEBUG: 00:53:42.683: Sleeping completed 373s (process:1904): libfprint-virtual_device-DEBUG: 00:53:42.683: 7399790744171: ../libfprint/drivers/virtual-device.c:387 373s (process:1904): libfprint-device-DEBUG: 00:53:42.683: Device reported open completion 373s (process:1904): libfprint-device-DEBUG: 00:53:42.683: Completing action FPI_DEVICE_ACTION_OPEN in idle! 373s (process:1904): libfprint-device-DEBUG: 00:53:42.683: Updated temperature model after 0.50 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 373s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:42.683: Got a new connection! 373s (process:1904): libfprint-virtual_device-DEBUG: 00:53:42.684: Got instructions of length 5 373s (process:1904): libfprint-virtual_device-DEBUG: 00:53:42.684: Received command CONT 373s (process:1904): libfprint-virtual_device-DEBUG: 00:53:42.684: Processing command CONT 373s (process:1904): libfprint-device-DEBUG: 00:53:42.684: Device reported deletion completion 373s (process:1904): libfprint-device-DEBUG: 00:53:42.684: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 373s (process:1904): libfprint-device-DEBUG: 00:53:42.684: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 373s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:42.684: Got a new connection! 373s (process:1904): libfprint-virtual_device-DEBUG: 00:53:42.684: Got instructions of length 16 373s (process:1904): libfprint-virtual_device-DEBUG: 00:53:42.684: Received command SET_KEEP_ALIVE 0 373s (process:1904): libfprint-virtual_device-DEBUG: 00:53:42.684: Keep alive toggled: 0 373s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:42.684: Got a new connection! 373s (process:1904): libfprint-virtual_device-DEBUG: 00:53:42.684: Got instructions of length 19 373s (process:1904): libfprint-virtual_device-DEBUG: 00:53:42.684: Received command SET_ENROLL_STAGES 5 373s (process:1904): libfprint-device-DEBUG: 00:53:42.684: Device reported close completion 373s (process:1904): libfprint-device-DEBUG: 00:53:42.684: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 373s (process:1904): libfprint-device-DEBUG: 00:53:42.684: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 373s ok 373s test_delayed_open (__main__.VirtualDeviceStorage.test_delayed_open) ... (process:1904): libfprint-virtual_device-DEBUG: 00:53:42.684: 7399790745898: ../libfprint/drivers/virtual-device.c:387 373s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:42.684: 7399790745914: ../libfprint/drivers/virtual-device-listener.c:153 373s (process:1904): libfprint-device-DEBUG: 00:53:42.685: Device reported open completion 373s (process:1904): libfprint-device-DEBUG: 00:53:42.685: Completing action FPI_DEVICE_ACTION_OPEN in idle! 373s (process:1904): libfprint-device-DEBUG: 00:53:42.685: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 373s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:42.685: Got a new connection! 373s (process:1904): libfprint-virtual_device-DEBUG: 00:53:42.685: Got instructions of length 16 373s (process:1904): libfprint-virtual_device-DEBUG: 00:53:42.685: Received command IGNORED_COMMAND 373s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:42.685: Got a new connection! 373s (process:1904): libfprint-virtual_device-DEBUG: 00:53:42.685: Got instructions of length 9 373s (process:1904): libfprint-virtual_device-DEBUG: 00:53:42.685: Received command SLEEP 500 373s (process:1904): libfprint-virtual_device-DEBUG: 00:53:42.685: Processing command IGNORED_COMMAND 373s (process:1904): libfprint-device-DEBUG: 00:53:42.685: Device reported close completion 373s (process:1904): libfprint-device-DEBUG: 00:53:42.685: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 373s (process:1904): libfprint-device-DEBUG: 00:53:42.685: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 373s (process:1904): libfprint-virtual_device-DEBUG: 00:53:42.686: 7399790747094: ../libfprint/drivers/virtual-device.c:387 373s (process:1904): libfprint-virtual_device-DEBUG: 00:53:42.686: Processing command SLEEP 500 373s (process:1904): libfprint-virtual_device-DEBUG: 00:53:42.686: Sleeping 500ms 374s (process:1904): libfprint-virtual_device-DEBUG: 00:53:43.186: Sleeping completed 374s (process:1904): libfprint-virtual_device-DEBUG: 00:53:43.186: 7399791247750: ../libfprint/drivers/virtual-device.c:387 374s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:43.186: 7399791247766: ../libfprint/drivers/virtual-device-listener.c:153 374s (process:1904): libfprint-device-DEBUG: 00:53:43.187: Device reported open completion 374s (process:1904): libfprint-device-DEBUG: 00:53:43.187: Completing action FPI_DEVICE_ACTION_OPEN in idle! 374s (process:1904): libfprint-device-DEBUG: 00:53:43.187: Updated temperature model after 0.50 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 374s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:43.187: Got a new connection! 374s (process:1904): libfprint-virtual_device-DEBUG: 00:53:43.187: Got instructions of length 5 374s (process:1904): libfprint-virtual_device-DEBUG: 00:53:43.187: Received command CONT 374s (process:1904): libfprint-virtual_device-DEBUG: 00:53:43.187: Processing command CONT 374s (process:1904): libfprint-device-DEBUG: 00:53:43.187: Device reported deletion completion 374s (process:1904): libfprint-device-DEBUG: 00:53:43.187: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 374s (process:1904): libfprint-device-DEBUG: 00:53:43.187: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 374s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:43.187: Got a new connection! 374s (process:1904): libfprint-virtual_device-DEBUG: 00:53:43.187: Got instructions of length 16 374s (process:1904): libfprint-virtual_device-DEBUG: 00:53:43.187: Received command SET_KEEP_ALIVE 0 374s (process:1904): libfprint-virtual_device-DEBUG: 00:53:43.187: Keep alive toggled: 0 374s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:43.187: Got a new connection! 374s (process:1904): libfprint-virtual_device-DEBUG: 00:53:43.188: Got instructions of length 19 374s (process:1904): libfprint-virtual_device-DEBUG: 00:53:43.188: Received command SET_ENROLL_STAGES 5 374s (process:1904): libfprint-device-DEBUG: 00:53:43.188: Device reported close completion 374s (process:1904): libfprint-device-DEBUG: 00:53:43.188: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 374s (process:1904): libfprint-device-DEBUG: 00:53:43.188: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 374s ok 374s test_delayed_open_with_keep_alive (__main__.VirtualDeviceStorage.test_delayed_open_with_keep_alive) ... (process:1904): libfprint-virtual_device-DEBUG: 00:53:43.188: 7399791249281: ../libfprint/drivers/virtual-device.c:387 374s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:43.188: 7399791249298: ../libfprint/drivers/virtual-device-listener.c:153 374s (process:1904): libfprint-device-DEBUG: 00:53:43.188: Device reported open completion 374s (process:1904): libfprint-device-DEBUG: 00:53:43.188: Completing action FPI_DEVICE_ACTION_OPEN in idle! 374s (process:1904): libfprint-device-DEBUG: 00:53:43.188: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 374s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:43.188: Got a new connection! 374s (process:1904): libfprint-virtual_device-DEBUG: 00:53:43.188: Got instructions of length 16 374s (process:1904): libfprint-virtual_device-DEBUG: 00:53:43.188: Received command SET_KEEP_ALIVE 1 374s (process:1904): libfprint-virtual_device-DEBUG: 00:53:43.188: Keep alive toggled: 1 374s (process:1904): libfprint-device-DEBUG: 00:53:43.188: Device reported close completion 374s (process:1904): libfprint-device-DEBUG: 00:53:43.188: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 374s (process:1904): libfprint-device-DEBUG: 00:53:43.188: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 374s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:43.189: Got a new connection! 374s (process:1904): libfprint-virtual_device-DEBUG: 00:53:43.189: Got instructions of length 9 374s (process:1904): libfprint-virtual_device-DEBUG: 00:53:43.189: Received command SLEEP 500 374s (process:1904): libfprint-virtual_device-DEBUG: 00:53:43.189: 7399791250097: ../libfprint/drivers/virtual-device.c:387 374s (process:1904): libfprint-virtual_device-DEBUG: 00:53:43.189: Processing command SLEEP 500 374s (process:1904): libfprint-virtual_device-DEBUG: 00:53:43.189: Sleeping 500ms 374s (process:1904): libfprint-virtual_device-DEBUG: 00:53:43.689: Sleeping completed 374s (process:1904): libfprint-virtual_device-DEBUG: 00:53:43.689: 7399791750722: ../libfprint/drivers/virtual-device.c:387 374s (process:1904): libfprint-device-DEBUG: 00:53:43.689: Device reported open completion 374s (process:1904): libfprint-device-DEBUG: 00:53:43.689: Completing action FPI_DEVICE_ACTION_OPEN in idle! 374s (process:1904): libfprint-device-DEBUG: 00:53:43.689: Updated temperature model after 0.50 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 374s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:43.690: Got a new connection! 374s (process:1904): libfprint-virtual_device-DEBUG: 00:53:43.690: Got instructions of length 5 374s (process:1904): libfprint-virtual_device-DEBUG: 00:53:43.690: Received command CONT 374s (process:1904): libfprint-virtual_device-DEBUG: 00:53:43.690: Processing command CONT 374s (process:1904): libfprint-device-DEBUG: 00:53:43.690: Device reported deletion completion 374s (process:1904): libfprint-device-DEBUG: 00:53:43.690: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 374s (process:1904): libfprint-device-DEBUG: 00:53:43.690: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 374s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:43.690: Got a new connection! 374s (process:1904): libfprint-virtual_device-DEBUG: 00:53:43.690: Got instructions of length 16 374s (process:1904): libfprint-virtual_device-DEBUG: 00:53:43.690: Received command SET_KEEP_ALIVE 0 374s (process:1904): libfprint-virtual_device-DEBUG: 00:53:43.690: Keep alive toggled: 0 374s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:43.691: Got a new connection! 374s (process:1904): libfprint-virtual_device-DEBUG: 00:53:43.691: Got instructions of length 19 374s (process:1904): libfprint-virtual_device-DEBUG: 00:53:43.691: Received command SET_ENROLL_STAGES 5 374s (process:1904): libfprint-device-DEBUG: 00:53:43.691: Device reported close completion 374s (process:1904): libfprint-device-DEBUG: 00:53:43.691: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 374s (process:1904): libfprint-device-DEBUG: 00:53:43.691: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 374s ok 374s test_delete_error (__main__.VirtualDeviceStorage.test_delete_error) ... (process:1904): libfprint-virtual_device-DEBUG: 00:53:43.691: 7399791752386: ../libfprint/drivers/virtual-device.c:387 374s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:43.691: 7399791752396: ../libfprint/drivers/virtual-device-listener.c:153 374s (process:1904): libfprint-device-DEBUG: 00:53:43.691: Device reported open completion 374s (process:1904): libfprint-device-DEBUG: 00:53:43.691: Completing action FPI_DEVICE_ACTION_OPEN in idle! 374s (process:1904): libfprint-device-DEBUG: 00:53:43.691: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 374s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:43.692: Got a new connection! 374s (process:1904): libfprint-virtual_device-DEBUG: 00:53:43.692: Got instructions of length 9 374s (process:1904): libfprint-virtual_device-DEBUG: 00:53:43.692: Received command SLEEP 100 374s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:43.692: Got a new connection! 374s (process:1904): libfprint-virtual_device-DEBUG: 00:53:43.692: Got instructions of length 7 374s (process:1904): libfprint-virtual_device-DEBUG: 00:53:43.692: Received command ERROR 7 374s (process:1904): libfprint-virtual_device-DEBUG: 00:53:43.692: Processing command SLEEP 100 374s (process:1904): libfprint-virtual_device-DEBUG: 00:53:43.692: Sleeping 100ms 374s (process:1904): libfprint-virtual_device-DEBUG: 00:53:43.792: Sleeping completed 374s (process:1904): libfprint-virtual_device-DEBUG: 00:53:43.792: Processing command ERROR 7 374s (process:1904): libfprint-device-DEBUG: 00:53:43.792: Device reported deletion completion 374s (process:1904): libfprint-device-DEBUG: 00:53:43.793: Completing action FPI_DEVICE_ACTION_DELETE in idle! 374s (process:1904): libfprint-device-DEBUG: 00:53:43.793: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 374s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:43.793: Got a new connection! 374s (process:1904): libfprint-virtual_device-DEBUG: 00:53:43.793: Got instructions of length 5 374s (process:1904): libfprint-virtual_device-DEBUG: 00:53:43.793: Received command CONT 374s (process:1904): libfprint-virtual_device-DEBUG: 00:53:43.793: Processing command CONT 374s (process:1904): libfprint-device-DEBUG: 00:53:43.793: Device reported deletion completion 374s (process:1904): libfprint-device-DEBUG: 00:53:43.793: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 374s (process:1904): libfprint-device-DEBUG: 00:53:43.793: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 374s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:43.794: Got a new connection! 374s (process:1904): libfprint-virtual_device-DEBUG: 00:53:43.794: Got instructions of length 16 374s (process:1904): libfprint-virtual_device-DEBUG: 00:53:43.794: Received command SET_KEEP_ALIVE 0 374s (process:1904): libfprint-virtual_device-DEBUG: 00:53:43.794: Keep alive toggled: 0 374s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:43.794: Got a new connection! 374s (process:1904): libfprint-virtual_device-DEBUG: 00:53:43.794: Got instructions of length 19 374s (process:1904): libfprint-virtual_device-DEBUG: 00:53:43.794: Received command SET_ENROLL_STAGES 5 374s (process:1904): libfprint-device-DEBUG: 00:53:43.794: Device reported close completion 374s (process:1904): libfprint-device-DEBUG: 00:53:43.794: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 374s (process:1904): libfprint-device-DEBUG: 00:53:43.794: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 374s ok 374s test_delete_multiple_times (__main__.VirtualDeviceStorage.test_delete_multiple_times) ... (process:1904): libfprint-virtual_device-DEBUG: 00:53:43.794: 7399791855833: ../libfprint/drivers/virtual-device.c:387 374s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:43.794: 7399791855845: ../libfprint/drivers/virtual-device-listener.c:153 374s (process:1904): libfprint-device-DEBUG: 00:53:43.795: Device reported open completion 374s (process:1904): libfprint-device-DEBUG: 00:53:43.795: Completing action FPI_DEVICE_ACTION_OPEN in idle! 374s (process:1904): libfprint-device-DEBUG: 00:53:43.795: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 374s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:43.795: Got a new connection! 374s (process:1904): libfprint-virtual_device-DEBUG: 00:53:43.795: Got instructions of length 16 374s (process:1904): libfprint-virtual_device-DEBUG: 00:53:43.795: Received command SCAN right-thumb 374s (process:1904): libfprint-device-DEBUG: 00:53:43.795: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 374s (process:1904): libfprint-virtual_device-DEBUG: 00:53:43.795: Processing command SCAN right-thumb 374s (process:1904): libfprint-device-DEBUG: 00:53:43.795: Device reported finger status change: FP_FINGER_STATUS_NEEDED 374s (process:1904): libfprint-device-DEBUG: 00:53:43.795: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 374s (process:1904): libfprint-device-DEBUG: 00:53:43.795: Device reported finger status change: FP_FINGER_STATUS_NEEDED 374s (process:1904): libfprint-device-DEBUG: 00:53:43.795: Device reported enroll progress, reported 1 of 5 have been completed 374s (process:1904): libfprint-virtual_device-DEBUG: 00:53:43.796: Sleeping completed 374s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:43.796: Got a new connection! 374s (process:1904): libfprint-virtual_device-DEBUG: 00:53:43.796: Got instructions of length 16 374s (process:1904): libfprint-virtual_device-DEBUG: 00:53:43.796: Received command SCAN right-thumb 374s (process:1904): libfprint-virtual_device-DEBUG: 00:53:43.796: Processing command SCAN right-thumb 374s (process:1904): libfprint-device-DEBUG: 00:53:43.796: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 374s (process:1904): libfprint-device-DEBUG: 00:53:43.796: Device reported finger status change: FP_FINGER_STATUS_NEEDED 374s (process:1904): libfprint-device-DEBUG: 00:53:43.796: Device reported enroll progress, reported 2 of 5 have been completed 374s (process:1904): libfprint-virtual_device-DEBUG: 00:53:43.796: Sleeping completed 374s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:43.796: Got a new connection! 374s (process:1904): libfprint-virtual_device-DEBUG: 00:53:43.796: Got instructions of length 16 374s (process:1904): libfprint-virtual_device-DEBUG: 00:53:43.796: Received command SCAN right-thumb 374s (process:1904): libfprint-virtual_device-DEBUG: 00:53:43.796: Processing command SCAN right-thumb 374s (process:1904): libfprint-device-DEBUG: 00:53:43.796: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 374s (process:1904): libfprint-device-DEBUG: 00:53:43.796: Device reported finger status change: FP_FINGER_STATUS_NEEDED 374s (process:1904): libfprint-device-DEBUG: 00:53:43.796: Device reported enroll progress, reported 3 of 5 have been completed 374s (process:1904): libfprint-virtual_device-DEBUG: 00:53:43.796: Sleeping completed 374s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:43.796: Got a new connection! 374s (process:1904): libfprint-virtual_device-DEBUG: 00:53:43.797: Got instructions of length 16 374s (process:1904): libfprint-virtual_device-DEBUG: 00:53:43.797: Received command SCAN right-thumb 374s (process:1904): libfprint-virtual_device-DEBUG: 00:53:43.797: Processing command SCAN right-thumb 374s (process:1904): libfprint-device-DEBUG: 00:53:43.797: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 374s (process:1904): libfprint-device-DEBUG: 00:53:43.797: Device reported finger status change: FP_FINGER_STATUS_NEEDED 374s (process:1904): libfprint-device-DEBUG: 00:53:43.797: Device reported enroll progress, reported 4 of 5 have been completed 374s (process:1904): libfprint-virtual_device-DEBUG: 00:53:43.797: Sleeping completed 374s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:43.797: Got a new connection! 374s (process:1904): libfprint-virtual_device-DEBUG: 00:53:43.797: Got instructions of length 16 374s (process:1904): libfprint-virtual_device-DEBUG: 00:53:43.797: Received command SCAN right-thumb 374s (process:1904): libfprint-virtual_device-DEBUG: 00:53:43.797: Processing command SCAN right-thumb 374s (process:1904): libfprint-device-DEBUG: 00:53:43.797: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 374s (process:1904): libfprint-device-DEBUG: 00:53:43.797: Device reported finger status change: FP_FINGER_STATUS_NEEDED 374s (process:1904): libfprint-device-DEBUG: 00:53:43.797: Device reported enroll progress, reported 5 of 5 have been completed 374s (process:1904): libfprint-device-DEBUG: 00:53:43.797: Device reported enroll completion 374s (process:1904): libfprint-device-DEBUG: 00:53:43.797: Device reported finger status change: FP_FINGER_STATUS_NONE 374s (process:1904): libfprint-device-DEBUG: 00:53:43.797: Print for finger FP_FINGER_RIGHT_THUMB enrolled 374s (process:1904): libfprint-device-DEBUG: 00:53:43.797: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 374s (process:1904): libfprint-device-DEBUG: 00:53:43.797: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 375s (process:1904): libfprint-virtual_device_storage-DEBUG: 00:53:44.298: Deleting print right-thumb for user testuser 375s (process:1904): libfprint-device-DEBUG: 00:53:44.298: Device reported deletion completion 375s (process:1904): libfprint-device-DEBUG: 00:53:44.298: Completing action FPI_DEVICE_ACTION_DELETE in idle! 375s (process:1904): libfprint-device-DEBUG: 00:53:44.298: Updated temperature model after 0.50 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 375s (process:1904): libfprint-virtual_device_storage-DEBUG: 00:53:44.798: Deleting print right-thumb for user testuser 375s (process:1904): libfprint-device-DEBUG: 00:53:44.799: Device reported deletion completion 375s (process:1904): libfprint-device-DEBUG: 00:53:44.799: Completing action FPI_DEVICE_ACTION_DELETE in idle! 375s (process:1904): libfprint-device-DEBUG: 00:53:44.799: Updated temperature model after 0.50 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 375s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:44.799: Got a new connection! 375s (process:1904): libfprint-virtual_device-DEBUG: 00:53:44.799: Got instructions of length 5 375s (process:1904): libfprint-virtual_device-DEBUG: 00:53:44.799: Received command CONT 375s (process:1904): libfprint-virtual_device-DEBUG: 00:53:44.799: Processing command CONT 375s (process:1904): libfprint-device-DEBUG: 00:53:44.799: Device reported deletion completion 375s (process:1904): libfprint-device-DEBUG: 00:53:44.799: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 375s (process:1904): libfprint-device-DEBUG: 00:53:44.799: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 375s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:44.799: Got a new connection! 375s (process:1904): libfprint-virtual_device-DEBUG: 00:53:44.799: Got instructions of length 16 375s (process:1904): libfprint-virtual_device-DEBUG: 00:53:44.799: Received command SET_KEEP_ALIVE 0 375s (process:1904): libfprint-virtual_device-DEBUG: 00:53:44.799: Keep alive toggled: 0 375s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:44.799: Got a new connection! 375s (process:1904): libfprint-virtual_device-DEBUG: 00:53:44.799: Got instructions of length 19 375s (process:1904): libfprint-virtual_device-DEBUG: 00:53:44.799: Received command SET_ENROLL_STAGES 5 375s (process:1904): libfprint-device-DEBUG: 00:53:44.800: Device reported close completion 375s (process:1904): libfprint-device-DEBUG: 00:53:44.800: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 375s (process:1904): libfprint-device-DEBUG: 00:53:44.800: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 375s Enroll done 375s ok 375s test_device_features (__main__.VirtualDeviceStorage.test_device_features) ... (process:1904): libfprint-virtual_device-DEBUG: 00:53:44.800: 7399792861222: ../libfprint/drivers/virtual-device.c:387 375s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:44.800: 7399792861239: ../libfprint/drivers/virtual-device-listener.c:153 375s (process:1904): libfprint-device-DEBUG: 00:53:44.800: Device reported open completion 375s (process:1904): libfprint-device-DEBUG: 00:53:44.800: Completing action FPI_DEVICE_ACTION_OPEN in idle! 375s (process:1904): libfprint-device-DEBUG: 00:53:44.800: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 375s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:44.800: Got a new connection! 375s (process:1904): libfprint-virtual_device-DEBUG: 00:53:44.800: Got instructions of length 5 375s (process:1904): libfprint-virtual_device-DEBUG: 00:53:44.800: Received command CONT 375s (process:1904): libfprint-virtual_device-DEBUG: 00:53:44.800: Processing command CONT 375s (process:1904): libfprint-device-DEBUG: 00:53:44.800: Device reported deletion completion 375s (process:1904): libfprint-device-DEBUG: 00:53:44.800: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 375s (process:1904): libfprint-device-DEBUG: 00:53:44.800: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 375s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:44.800: Got a new connection! 375s (process:1904): libfprint-virtual_device-DEBUG: 00:53:44.800: Got instructions of length 16 375s (process:1904): libfprint-virtual_device-DEBUG: 00:53:44.800: Received command SET_KEEP_ALIVE 0 375s (process:1904): libfprint-virtual_device-DEBUG: 00:53:44.801: Keep alive toggled: 0 375s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:44.801: Got a new connection! 375s (process:1904): libfprint-virtual_device-DEBUG: 00:53:44.801: Got instructions of length 19 375s (process:1904): libfprint-virtual_device-DEBUG: 00:53:44.801: Received command SET_ENROLL_STAGES 5 375s (process:1904): libfprint-device-DEBUG: 00:53:44.801: Device reported close completion 375s (process:1904): libfprint-device-DEBUG: 00:53:44.801: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 375s (process:1904): libfprint-device-DEBUG: 00:53:44.801: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 375s ok 375s test_device_properties (__main__.VirtualDeviceStorage.test_device_properties) ... (process:1904): libfprint-virtual_device-DEBUG: 00:53:44.801: 7399792862333: ../libfprint/drivers/virtual-device.c:387 375s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:44.801: 7399792862346: ../libfprint/drivers/virtual-device-listener.c:153 375s (process:1904): libfprint-device-DEBUG: 00:53:44.801: Device reported open completion 375s (process:1904): libfprint-device-DEBUG: 00:53:44.801: Completing action FPI_DEVICE_ACTION_OPEN in idle! 375s (process:1904): libfprint-device-DEBUG: 00:53:44.801: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 375s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:44.801: Got a new connection! 375s (process:1904): libfprint-virtual_device-DEBUG: 00:53:44.801: Got instructions of length 5 375s (process:1904): libfprint-virtual_device-DEBUG: 00:53:44.801: Received command CONT 375s (process:1904): libfprint-virtual_device-DEBUG: 00:53:44.801: Processing command CONT 375s (process:1904): libfprint-device-DEBUG: 00:53:44.801: Device reported deletion completion 375s (process:1904): libfprint-device-DEBUG: 00:53:44.801: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 375s (process:1904): libfprint-device-DEBUG: 00:53:44.801: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 375s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:44.802: Got a new connection! 375s (process:1904): libfprint-virtual_device-DEBUG: 00:53:44.802: Got instructions of length 16 375s (process:1904): libfprint-virtual_device-DEBUG: 00:53:44.802: Received command SET_KEEP_ALIVE 0 375s (process:1904): libfprint-virtual_device-DEBUG: 00:53:44.802: Keep alive toggled: 0 375s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:44.802: Got a new connection! 375s (process:1904): libfprint-virtual_device-DEBUG: 00:53:44.802: Got instructions of length 19 375s (process:1904): libfprint-virtual_device-DEBUG: 00:53:44.802: Received command SET_ENROLL_STAGES 5 375s (process:1904): libfprint-device-DEBUG: 00:53:44.802: Device reported close completion 375s (process:1904): libfprint-device-DEBUG: 00:53:44.802: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 375s (process:1904): libfprint-device-DEBUG: 00:53:44.802: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 375s ok 375s test_device_sleep (__main__.VirtualDeviceStorage.test_device_sleep) ... (process:1904): libfprint-virtual_device-DEBUG: 00:53:44.802: 7399792863427: ../libfprint/drivers/virtual-device.c:387 375s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:44.802: 7399792863441: ../libfprint/drivers/virtual-device-listener.c:153 375s (process:1904): libfprint-device-DEBUG: 00:53:44.802: Device reported open completion 375s (process:1904): libfprint-device-DEBUG: 00:53:44.802: Completing action FPI_DEVICE_ACTION_OPEN in idle! 375s (process:1904): libfprint-device-DEBUG: 00:53:44.802: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 375s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:44.802: Got a new connection! 375s (process:1904): libfprint-virtual_device-DEBUG: 00:53:44.802: Got instructions of length 10 375s (process:1904): libfprint-virtual_device-DEBUG: 00:53:44.802: Received command SLEEP 1500 375s (process:1904): libfprint-device-DEBUG: 00:53:44.803: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 375s (process:1904): libfprint-virtual_device-DEBUG: 00:53:44.803: Processing command SLEEP 1500 375s (process:1904): libfprint-virtual_device-DEBUG: 00:53:44.803: Sleeping 1500ms 376s (process:1904): libfprint-device-DEBUG: 00:53:45.103: Idle cancelling on ongoing operation! 376s (process:1904): libfprint-virtual_device-DEBUG: 00:53:45.103: Got cancellation! 376s (process:1904): libfprint-device-DEBUG: 00:53:45.103: Device reported finger status change: FP_FINGER_STATUS_NEEDED 376s (process:1904): libfprint-device-DEBUG: 00:53:45.103: Device reported identify completion 376s (process:1904): libfprint-device-DEBUG: 00:53:45.103: Device reported finger status change: FP_FINGER_STATUS_NONE 376s (process:1904): libfprint-device-DEBUG: 00:53:45.103: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 376s (process:1904): libfprint-device-DEBUG: 00:53:45.103: Updated temperature model after 0.30 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 376s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:45.303: Got a new connection! 376s (process:1904): libfprint-virtual_device-DEBUG: 00:53:45.303: Got instructions of length 5 376s (process:1904): libfprint-virtual_device-DEBUG: 00:53:45.303: Received command CONT 376s (process:1904): libfprint-virtual_device-DEBUG: 00:53:45.303: Processing command CONT 376s (process:1904): libfprint-device-DEBUG: 00:53:45.303: Device reported deletion completion 376s (process:1904): libfprint-device-DEBUG: 00:53:45.303: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 376s (process:1904): libfprint-device-DEBUG: 00:53:45.303: Updated temperature model after 0.20 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 376s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:45.303: Got a new connection! 376s (process:1904): libfprint-virtual_device-DEBUG: 00:53:45.304: Got instructions of length 16 376s (process:1904): libfprint-virtual_device-DEBUG: 00:53:45.304: Received command SET_KEEP_ALIVE 0 376s (process:1904): libfprint-virtual_device-DEBUG: 00:53:45.304: Keep alive toggled: 0 376s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:45.304: Got a new connection! 376s (process:1904): libfprint-virtual_device-DEBUG: 00:53:45.304: Got instructions of length 19 376s (process:1904): libfprint-virtual_device-DEBUG: 00:53:45.304: Received command SET_ENROLL_STAGES 5 376s (process:1904): libfprint-device-DEBUG: 00:53:45.304: Device reported close completion 376s (process:1904): libfprint-device-DEBUG: 00:53:45.304: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 376s (process:1904): libfprint-device-DEBUG: 00:53:45.304: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 376s ok 376s test_device_sleep_before_completing_verify (__main__.VirtualDeviceStorage.test_device_sleep_before_completing_verify) ... (process:1904): libfprint-virtual_device-DEBUG: 00:53:45.304: 7399793365436: ../libfprint/drivers/virtual-device.c:387 376s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:45.304: 7399793365451: ../libfprint/drivers/virtual-device-listener.c:153 376s (process:1904): libfprint-device-DEBUG: 00:53:45.304: Device reported open completion 376s (process:1904): libfprint-device-DEBUG: 00:53:45.304: Completing action FPI_DEVICE_ACTION_OPEN in idle! 376s (process:1904): libfprint-device-DEBUG: 00:53:45.304: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 376s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:45.304: Got a new connection! 376s (process:1904): libfprint-virtual_device-DEBUG: 00:53:45.304: Got instructions of length 14 376s (process:1904): libfprint-virtual_device-DEBUG: 00:53:45.304: Received command SCAN foo-print 376s (process:1904): libfprint-device-DEBUG: 00:53:45.305: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 376s (process:1904): libfprint-virtual_device-DEBUG: 00:53:45.305: Processing command SCAN foo-print 376s (process:1904): libfprint-device-DEBUG: 00:53:45.305: Device reported finger status change: FP_FINGER_STATUS_NEEDED 376s (process:1904): libfprint-device-DEBUG: 00:53:45.305: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 376s (process:1904): libfprint-device-DEBUG: 00:53:45.305: Device reported finger status change: FP_FINGER_STATUS_NEEDED 376s (process:1904): libfprint-device-DEBUG: 00:53:45.305: Device reported enroll progress, reported 1 of 5 have been completed 376s (process:1904): libfprint-virtual_device-DEBUG: 00:53:45.305: Sleeping completed 376s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:45.305: Got a new connection! 376s (process:1904): libfprint-virtual_device-DEBUG: 00:53:45.305: Got instructions of length 14 376s (process:1904): libfprint-virtual_device-DEBUG: 00:53:45.305: Received command SCAN foo-print 376s (process:1904): libfprint-virtual_device-DEBUG: 00:53:45.305: Processing command SCAN foo-print 376s (process:1904): libfprint-device-DEBUG: 00:53:45.305: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 376s (process:1904): libfprint-device-DEBUG: 00:53:45.305: Device reported finger status change: FP_FINGER_STATUS_NEEDED 376s (process:1904): libfprint-device-DEBUG: 00:53:45.305: Device reported enroll progress, reported 2 of 5 have been completed 376s (process:1904): libfprint-virtual_device-DEBUG: 00:53:45.305: Sleeping completed 376s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:45.305: Got a new connection! 376s (process:1904): libfprint-virtual_device-DEBUG: 00:53:45.305: Got instructions of length 14 376s (process:1904): libfprint-virtual_device-DEBUG: 00:53:45.305: Received command SCAN foo-print 376s (process:1904): libfprint-virtual_device-DEBUG: 00:53:45.305: Processing command SCAN foo-print 376s (process:1904): libfprint-device-DEBUG: 00:53:45.305: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 376s (process:1904): libfprint-device-DEBUG: 00:53:45.305: Device reported finger status change: FP_FINGER_STATUS_NEEDED 376s (process:1904): libfprint-device-DEBUG: 00:53:45.305: Device reported enroll progress, reported 3 of 5 have been completed 376s (process:1904): libfprint-virtual_device-DEBUG: 00:53:45.305: Sleeping completed 376s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:45.305: Got a new connection! 376s (process:1904): libfprint-virtual_device-DEBUG: 00:53:45.306: Got instructions of length 14 376s (process:1904): libfprint-virtual_device-DEBUG: 00:53:45.306: Received command SCAN foo-print 376s (process:1904): libfprint-virtual_device-DEBUG: 00:53:45.306: Processing command SCAN foo-print 376s (process:1904): libfprint-device-DEBUG: 00:53:45.306: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 376s (process:1904): libfprint-device-DEBUG: 00:53:45.306: Device reported finger status change: FP_FINGER_STATUS_NEEDED 376s (process:1904): libfprint-device-DEBUG: 00:53:45.306: Device reported enroll progress, reported 4 of 5 have been completed 376s (process:1904): libfprint-virtual_device-DEBUG: 00:53:45.306: Sleeping completed 376s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:45.306: Got a new connection! 376s (process:1904): libfprint-virtual_device-DEBUG: 00:53:45.306: Got instructions of length 14 376s (process:1904): libfprint-virtual_device-DEBUG: 00:53:45.306: Received command SCAN foo-print 376s (process:1904): libfprint-virtual_device-DEBUG: 00:53:45.306: Processing command SCAN foo-print 376s (process:1904): libfprint-device-DEBUG: 00:53:45.306: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 376s (process:1904): libfprint-device-DEBUG: 00:53:45.306: Device reported finger status change: FP_FINGER_STATUS_NEEDED 376s (process:1904): libfprint-device-DEBUG: 00:53:45.306: Device reported enroll progress, reported 5 of 5 have been completed 376s (process:1904): libfprint-device-DEBUG: 00:53:45.306: Device reported enroll completion 376s (process:1904): libfprint-device-DEBUG: 00:53:45.306: Device reported finger status change: FP_FINGER_STATUS_NONE 376s (process:1904): libfprint-device-DEBUG: 00:53:45.306: Print for finger FP_FINGER_LEFT_RING enrolled 376s (process:1904): libfprint-device-DEBUG: 00:53:45.306: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 376s (process:1904): libfprint-device-DEBUG: 00:53:45.306: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 376s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:45.306: Got a new connection! 376s (process:1904): libfprint-virtual_device-DEBUG: 00:53:45.306: Got instructions of length 9 376s (process:1904): libfprint-virtual_device-DEBUG: 00:53:45.306: Received command SLEEP 100 376s (process:1904): libfprint-device-DEBUG: 00:53:45.306: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 376s (process:1904): libfprint-virtual_device-DEBUG: 00:53:45.306: Processing command SLEEP 100 376s (process:1904): libfprint-virtual_device-DEBUG: 00:53:45.306: Sleeping 100ms 376s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:45.307: Got a new connection! 376s (process:1904): libfprint-virtual_device-DEBUG: 00:53:45.307: Got instructions of length 14 376s (process:1904): libfprint-virtual_device-DEBUG: 00:53:45.307: Received command SCAN bar-print 376s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:45.307: Got a new connection! 376s (process:1904): libfprint-virtual_device-DEBUG: 00:53:45.307: Got instructions of length 9 376s (process:1904): libfprint-virtual_device-DEBUG: 00:53:45.307: Received command SLEEP 800 376s (process:1904): libfprint-virtual_device-DEBUG: 00:53:45.406: Sleeping completed 376s (process:1904): libfprint-virtual_device-DEBUG: 00:53:45.407: Processing command SCAN bar-print 376s (process:1904): libfprint-device-DEBUG: 00:53:45.407: Device reported finger status change: FP_FINGER_STATUS_NEEDED 376s (process:1904): libfprint-device-DEBUG: 00:53:45.407: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 376s (process:1904): libfprint-virtual_device_storage-DEBUG: 00:53:45.407: Trying to identify print 'bar-print' against a gallery of 1 prints 376s (process:1904): libfprint-device-DEBUG: 00:53:45.407: Device reported identify result 376s (process:1904): libfprint-device-DEBUG: 00:53:45.407: Device reported finger status change: FP_FINGER_STATUS_NEEDED 376s (process:1904): libfprint-virtual_device-DEBUG: 00:53:45.407: Processing command SLEEP 800 376s (process:1904): libfprint-virtual_device-DEBUG: 00:53:45.407: Sleeping 800ms 376s (process:1904): libfprint-virtual_device-DEBUG: 00:53:45.407: Sleeping now, command queued for later: SCAN bar-print 376s (process:1904): libfprint-device-DEBUG: 00:53:45.644: Updated temperature model after 0.34 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 377s (process:1904): libfprint-virtual_device-DEBUG: 00:53:46.207: Sleeping completed 377s (process:1904): libfprint-virtual_device-DEBUG: 00:53:46.208: Processing command SCAN bar-print 377s (process:1904): libfprint-device-DEBUG: 00:53:46.208: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 377s (process:1904): libfprint-virtual_device_storage-DEBUG: 00:53:46.208: Trying to identify print 'bar-print' against a gallery of 1 prints 377s (process:1904): libfprint-device-DEBUG: 00:53:46.208: Device reported finger status change: FP_FINGER_STATUS_NEEDED 377s (process:1904): libfprint-device-DEBUG: 00:53:46.208: Device reported identify completion 377s (process:1904): libfprint-device-DEBUG: 00:53:46.208: Device reported finger status change: FP_FINGER_STATUS_NONE 377s (process:1904): libfprint-device-DEBUG: 00:53:46.208: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 377s (process:1904): libfprint-device-DEBUG: 00:53:46.208: Updated temperature model after 0.56 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 377s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:46.208: Got a new connection! 377s (process:1904): libfprint-virtual_device-DEBUG: 00:53:46.208: Got instructions of length 5 377s (process:1904): libfprint-virtual_device-DEBUG: 00:53:46.208: Received command CONT 377s (process:1904): libfprint-virtual_device-DEBUG: 00:53:46.208: Processing command CONT 377s (process:1904): libfprint-device-DEBUG: 00:53:46.208: Device reported deletion completion 377s (process:1904): libfprint-device-DEBUG: 00:53:46.208: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 377s (process:1904): libfprint-device-DEBUG: 00:53:46.208: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 377s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:46.208: Got a new connection! 377s (process:1904): libfprint-virtual_device-DEBUG: 00:53:46.208: Got instructions of length 16 377s (process:1904): libfprint-virtual_device-DEBUG: 00:53:46.208: Received command SET_KEEP_ALIVE 0 377s (process:1904): libfprint-virtual_device-DEBUG: 00:53:46.208: Keep alive toggled: 0 377s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:46.208: Got a new connection! 377s (process:1904): libfprint-virtual_device-DEBUG: 00:53:46.209: Got instructions of length 19 377s (process:1904): libfprint-virtual_device-DEBUG: 00:53:46.209: Received command SET_ENROLL_STAGES 5 377s (process:1904): libfprint-device-DEBUG: 00:53:46.209: Device reported close completion 377s (process:1904): libfprint-device-DEBUG: 00:53:46.209: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 377s (process:1904): libfprint-device-DEBUG: 00:53:46.209: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 377s Enroll done 377s ok 377s test_device_sleep_on_cancellation (__main__.VirtualDeviceStorage.test_device_sleep_on_cancellation) ... (process:1904): libfprint-virtual_device-DEBUG: 00:53:46.209: 7399794270275: ../libfprint/drivers/virtual-device.c:387 377s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:46.209: 7399794270288: ../libfprint/drivers/virtual-device-listener.c:153 377s (process:1904): libfprint-device-DEBUG: 00:53:46.209: Device reported open completion 377s (process:1904): libfprint-device-DEBUG: 00:53:46.209: Completing action FPI_DEVICE_ACTION_OPEN in idle! 377s (process:1904): libfprint-device-DEBUG: 00:53:46.209: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 377s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:46.209: Got a new connection! 377s (process:1904): libfprint-virtual_device-DEBUG: 00:53:46.209: Got instructions of length 26 377s (process:1904): libfprint-virtual_device-DEBUG: 00:53:46.209: Received command SET_CANCELLATION_ENABLED 0 377s (process:1904): libfprint-virtual_device-DEBUG: 00:53:46.209: Cancellation support toggled: 0 377s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:46.209: Got a new connection! 377s (process:1904): libfprint-virtual_device-DEBUG: 00:53:46.210: Got instructions of length 10 377s (process:1904): libfprint-virtual_device-DEBUG: 00:53:46.210: Received command SLEEP 1500 377s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:46.210: Got a new connection! 377s (process:1904): libfprint-virtual_device-DEBUG: 00:53:46.210: Got instructions of length 14 377s (process:1904): libfprint-virtual_device-DEBUG: 00:53:46.210: Received command SCAN foo-print 377s (process:1904): libfprint-device-DEBUG: 00:53:46.210: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 377s (process:1904): libfprint-virtual_device-DEBUG: 00:53:46.210: Processing command SLEEP 1500 377s (process:1904): libfprint-virtual_device-DEBUG: 00:53:46.210: Sleeping 1500ms 377s (process:1904): libfprint-device-DEBUG: 00:53:46.510: Idle cancelling on ongoing operation! 377s Executing: libfprint-2/virtual-device.test 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.711: Sleeping completed 378s (process:1904): libfprint-device-DEBUG: 00:53:47.711: Device reported finger status change: FP_FINGER_STATUS_NEEDED 378s (process:1904): libfprint-device-DEBUG: 00:53:47.711: Device reported identify completion 378s (process:1904): libfprint-device-DEBUG: 00:53:47.711: Device reported finger status change: FP_FINGER_STATUS_NONE 378s (process:1904): libfprint-device-DEBUG: 00:53:47.711: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 378s (process:1904): libfprint-device-DEBUG: 00:53:47.711: Updated temperature model after 1.50 seconds, ratio 0.27 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.711: Processing command SCAN foo-print 378s (process:1904): libfprint-device-DEBUG: 00:53:47.711: Device reported close completion 378s (process:1904): libfprint-device-DEBUG: 00:53:47.711: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 378s (process:1904): libfprint-device-DEBUG: 00:53:47.711: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 378s ok 378s test_duplicate_enroll (__main__.VirtualDeviceStorage.test_duplicate_enroll) ... (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.711: 7399795772837: ../libfprint/drivers/virtual-device.c:387 378s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:47.711: 7399795772855: ../libfprint/drivers/virtual-device-listener.c:153 378s (process:1904): libfprint-device-DEBUG: 00:53:47.712: Device reported open completion 378s (process:1904): libfprint-device-DEBUG: 00:53:47.712: Completing action FPI_DEVICE_ACTION_OPEN in idle! 378s (process:1904): libfprint-device-DEBUG: 00:53:47.712: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 378s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:47.712: Got a new connection! 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.712: Got instructions of length 14 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.712: Received command SCAN testprint 378s (process:1904): libfprint-device-DEBUG: 00:53:47.712: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.712: Processing command SCAN testprint 378s (process:1904): libfprint-device-DEBUG: 00:53:47.712: Device reported finger status change: FP_FINGER_STATUS_NEEDED 378s (process:1904): libfprint-device-DEBUG: 00:53:47.712: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 378s (process:1904): libfprint-device-DEBUG: 00:53:47.712: Device reported finger status change: FP_FINGER_STATUS_NEEDED 378s (process:1904): libfprint-device-DEBUG: 00:53:47.712: Device reported enroll progress, reported 1 of 5 have been completed 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.712: Sleeping completed 378s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:47.712: Got a new connection! 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.712: Got instructions of length 14 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.712: Received command SCAN testprint 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.712: Processing command SCAN testprint 378s (process:1904): libfprint-device-DEBUG: 00:53:47.712: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 378s (process:1904): libfprint-device-DEBUG: 00:53:47.712: Device reported finger status change: FP_FINGER_STATUS_NEEDED 378s (process:1904): libfprint-device-DEBUG: 00:53:47.712: Device reported enroll progress, reported 2 of 5 have been completed 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.712: Sleeping completed 378s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:47.713: Got a new connection! 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.713: Got instructions of length 14 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.713: Received command SCAN testprint 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.713: Processing command SCAN testprint 378s (process:1904): libfprint-device-DEBUG: 00:53:47.713: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 378s (process:1904): libfprint-device-DEBUG: 00:53:47.713: Device reported finger status change: FP_FINGER_STATUS_NEEDED 378s (process:1904): libfprint-device-DEBUG: 00:53:47.713: Device reported enroll progress, reported 3 of 5 have been completed 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.713: Sleeping completed 378s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:47.713: Got a new connection! 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.713: Got instructions of length 14 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.713: Received command SCAN testprint 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.713: Processing command SCAN testprint 378s (process:1904): libfprint-device-DEBUG: 00:53:47.713: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 378s (process:1904): libfprint-device-DEBUG: 00:53:47.713: Device reported finger status change: FP_FINGER_STATUS_NEEDED 378s (process:1904): libfprint-device-DEBUG: 00:53:47.713: Device reported enroll progress, reported 4 of 5 have been completed 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.713: Sleeping completed 378s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:47.713: Got a new connection! 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.713: Got instructions of length 14 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.713: Received command SCAN testprint 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.713: Processing command SCAN testprint 378s (process:1904): libfprint-device-DEBUG: 00:53:47.713: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 378s (process:1904): libfprint-device-DEBUG: 00:53:47.713: Device reported finger status change: FP_FINGER_STATUS_NEEDED 378s (process:1904): libfprint-device-DEBUG: 00:53:47.713: Device reported enroll progress, reported 5 of 5 have been completed 378s (process:1904): libfprint-device-DEBUG: 00:53:47.713: Device reported enroll completion 378s (process:1904): libfprint-device-DEBUG: 00:53:47.713: Device reported finger status change: FP_FINGER_STATUS_NONE 378s (process:1904): libfprint-device-DEBUG: 00:53:47.713: Print for finger FP_FINGER_LEFT_LITTLE enrolled 378s (process:1904): libfprint-device-DEBUG: 00:53:47.713: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 378s (process:1904): libfprint-device-DEBUG: 00:53:47.713: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 378s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:47.714: Got a new connection! 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.714: Got instructions of length 14 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.714: Received command SCAN testprint 378s (process:1904): libfprint-device-DEBUG: 00:53:47.714: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.714: Processing command SCAN testprint 378s (process:1904): libfprint-device-DEBUG: 00:53:47.714: Device reported finger status change: FP_FINGER_STATUS_NEEDED 378s (process:1904): libfprint-device-DEBUG: 00:53:47.714: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 378s (process:1904): libfprint-device-DEBUG: 00:53:47.714: Device reported enroll completion 378s (process:1904): libfprint-device-DEBUG: 00:53:47.714: Device reported finger status change: FP_FINGER_STATUS_NONE 378s (process:1904): libfprint-device-DEBUG: 00:53:47.714: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 378s (process:1904): libfprint-device-DEBUG: 00:53:47.714: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 378s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:47.714: Got a new connection! 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.714: Got instructions of length 5 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.714: Received command CONT 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.714: Processing command CONT 378s (process:1904): libfprint-device-DEBUG: 00:53:47.714: Device reported deletion completion 378s (process:1904): libfprint-device-DEBUG: 00:53:47.714: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 378s (process:1904): libfprint-device-DEBUG: 00:53:47.714: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 378s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:47.714: Got a new connection! 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.714: Got instructions of length 16 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.714: Received command SET_KEEP_ALIVE 0 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.714: Keep alive toggled: 0 378s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:47.714: Got a new connection! 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.714: Got instructions of length 19 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.714: Received command SET_ENROLL_STAGES 5 378s (process:1904): libfprint-device-DEBUG: 00:53:47.715: Device reported close completion 378s (process:1904): libfprint-device-DEBUG: 00:53:47.715: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 378s (process:1904): libfprint-device-DEBUG: 00:53:47.715: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 378s Enroll done 378s Enroll done 378s ok 378s test_enroll (__main__.VirtualDeviceStorage.test_enroll) ... (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.715: 7399795776148: ../libfprint/drivers/virtual-device.c:387 378s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:47.715: 7399795776164: ../libfprint/drivers/virtual-device-listener.c:153 378s (process:1904): libfprint-device-DEBUG: 00:53:47.715: Device reported open completion 378s (process:1904): libfprint-device-DEBUG: 00:53:47.715: Completing action FPI_DEVICE_ACTION_OPEN in idle! 378s (process:1904): libfprint-device-DEBUG: 00:53:47.715: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 378s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:47.715: Got a new connection! 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.715: Got instructions of length 14 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.715: Received command SCAN testprint 378s (process:1904): libfprint-device-DEBUG: 00:53:47.715: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.715: Processing command SCAN testprint 378s (process:1904): libfprint-device-DEBUG: 00:53:47.715: Device reported finger status change: FP_FINGER_STATUS_NEEDED 378s (process:1904): libfprint-device-DEBUG: 00:53:47.715: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 378s (process:1904): libfprint-device-DEBUG: 00:53:47.715: Device reported finger status change: FP_FINGER_STATUS_NEEDED 378s (process:1904): libfprint-device-DEBUG: 00:53:47.715: Device reported enroll progress, reported 1 of 5 have been completed 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.715: Sleeping completed 378s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:47.715: Got a new connection! 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.716: Got instructions of length 14 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.716: Received command SCAN testprint 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.716: Processing command SCAN testprint 378s (process:1904): libfprint-device-DEBUG: 00:53:47.716: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 378s (process:1904): libfprint-device-DEBUG: 00:53:47.716: Device reported finger status change: FP_FINGER_STATUS_NEEDED 378s (process:1904): libfprint-device-DEBUG: 00:53:47.716: Device reported enroll progress, reported 2 of 5 have been completed 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.716: Sleeping completed 378s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:47.716: Got a new connection! 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.716: Got instructions of length 14 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.716: Received command SCAN testprint 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.716: Processing command SCAN testprint 378s (process:1904): libfprint-device-DEBUG: 00:53:47.716: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 378s (process:1904): libfprint-device-DEBUG: 00:53:47.716: Device reported finger status change: FP_FINGER_STATUS_NEEDED 378s (process:1904): libfprint-device-DEBUG: 00:53:47.716: Device reported enroll progress, reported 3 of 5 have been completed 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.716: Sleeping completed 378s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:47.716: Got a new connection! 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.716: Got instructions of length 14 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.716: Received command SCAN testprint 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.716: Processing command SCAN testprint 378s (process:1904): libfprint-device-DEBUG: 00:53:47.716: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 378s (process:1904): libfprint-device-DEBUG: 00:53:47.716: Device reported finger status change: FP_FINGER_STATUS_NEEDED 378s (process:1904): libfprint-device-DEBUG: 00:53:47.716: Device reported enroll progress, reported 4 of 5 have been completed 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.716: Sleeping completed 378s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:47.716: Got a new connection! 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.716: Got instructions of length 14 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.716: Received command SCAN testprint 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.716: Processing command SCAN testprint 378s (process:1904): libfprint-device-DEBUG: 00:53:47.716: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 378s (process:1904): libfprint-device-DEBUG: 00:53:47.716: Device reported finger status change: FP_FINGER_STATUS_NEEDED 378s (process:1904): libfprint-device-DEBUG: 00:53:47.716: Device reported enroll progress, reported 5 of 5 have been completed 378s (process:1904): libfprint-device-DEBUG: 00:53:47.716: Device reported enroll completion 378s (process:1904): libfprint-device-DEBUG: 00:53:47.716: Device reported finger status change: FP_FINGER_STATUS_NONE 378s (process:1904): libfprint-device-DEBUG: 00:53:47.716: Print for finger FP_FINGER_LEFT_LITTLE enrolled 378s (process:1904): libfprint-device-DEBUG: 00:53:47.716: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 378s (process:1904): libfprint-device-DEBUG: 00:53:47.716: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 378s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:47.717: Got a new connection! 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.717: Got instructions of length 5 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.717: Received command CONT 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.717: Processing command CONT 378s (process:1904): libfprint-device-DEBUG: 00:53:47.717: Device reported deletion completion 378s (process:1904): libfprint-device-DEBUG: 00:53:47.717: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 378s (process:1904): libfprint-device-DEBUG: 00:53:47.717: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 378s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:47.717: Got a new connection! 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.717: Got instructions of length 16 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.717: Received command SET_KEEP_ALIVE 0 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.717: Keep alive toggled: 0 378s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:47.717: Got a new connection! 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.717: Got instructions of length 19 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.717: Received command SET_ENROLL_STAGES 5 378s (process:1904): libfprint-device-DEBUG: 00:53:47.717: Device reported close completion 378s (process:1904): libfprint-device-DEBUG: 00:53:47.717: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 378s (process:1904): libfprint-device-DEBUG: 00:53:47.717: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 378s Enroll done 378s ok 378s test_enroll_script (__main__.VirtualDeviceStorage.test_enroll_script) ... (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.717: 7399795778766: ../libfprint/drivers/virtual-device.c:387 378s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:47.717: 7399795778777: ../libfprint/drivers/virtual-device-listener.c:153 378s (process:1904): libfprint-device-DEBUG: 00:53:47.718: Device reported open completion 378s (process:1904): libfprint-device-DEBUG: 00:53:47.718: Completing action FPI_DEVICE_ACTION_OPEN in idle! 378s (process:1904): libfprint-device-DEBUG: 00:53:47.718: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 378s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:47.718: Got a new connection! 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.718: Got instructions of length 19 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.718: Received command SET_ENROLL_STAGES 8 378s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:47.718: Got a new connection! 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.718: Got instructions of length 13 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.718: Received command SCAN print-id 378s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:47.718: Got a new connection! 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.718: Got instructions of length 13 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.718: Received command SCAN print-id 378s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:47.718: Got a new connection! 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.718: Got instructions of length 7 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.718: Received command RETRY 1 378s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:47.718: Got a new connection! 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.718: Got instructions of length 13 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.718: Received command SCAN print-id 378s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:47.718: Got a new connection! 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.719: Got instructions of length 7 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.719: Received command RETRY 3 378s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:47.719: Got a new connection! 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.719: Got instructions of length 13 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.719: Received command SCAN print-id 378s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:47.719: Got a new connection! 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.719: Got instructions of length 7 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.719: Received command RETRY 2 378s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:47.719: Got a new connection! 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.719: Got instructions of length 13 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.719: Received command SCAN print-id 378s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:47.719: Got a new connection! 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.719: Got instructions of length 8 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.719: Received command SLEEP 10 378s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:47.719: Got a new connection! 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.719: Got instructions of length 8 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.719: Received command SLEEP 20 378s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:47.720: Got a new connection! 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.720: Got instructions of length 7 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.720: Received command RETRY 0 378s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:47.720: Got a new connection! 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.720: Got instructions of length 7 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.720: Received command RETRY 3 378s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:47.720: Got a new connection! 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.720: Got instructions of length 13 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.720: Received command SCAN print-id 378s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:47.720: Got a new connection! 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.720: Got instructions of length 15 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.720: Received command SCAN another-id 378s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:47.720: Got a new connection! 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.720: Got instructions of length 13 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.720: Received command SCAN print-id 378s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:47.720: Got a new connection! 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.720: Got instructions of length 13 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.720: Received command SCAN print-id 378s (process:1904): libfprint-device-DEBUG: 00:53:47.720: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.720: Processing command SCAN print-id 378s (process:1904): libfprint-device-DEBUG: 00:53:47.720: Device reported finger status change: FP_FINGER_STATUS_NEEDED 378s (process:1904): libfprint-device-DEBUG: 00:53:47.720: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 378s (process:1904): libfprint-device-DEBUG: 00:53:47.721: Device reported finger status change: FP_FINGER_STATUS_NEEDED 378s (process:1904): libfprint-device-DEBUG: 00:53:47.721: Device reported enroll progress, reported 1 of 8 have been completed 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.721: Sleeping completed 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.721: Processing command SCAN print-id 378s (process:1904): libfprint-device-DEBUG: 00:53:47.721: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 378s (process:1904): libfprint-device-DEBUG: 00:53:47.721: Device reported finger status change: FP_FINGER_STATUS_NEEDED 378s (process:1904): libfprint-device-DEBUG: 00:53:47.721: Device reported enroll progress, reported 2 of 8 have been completed 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.721: Sleeping completed 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.721: Processing command RETRY 1 378s (process:1904): libfprint-device-DEBUG: 00:53:47.721: Device reported enroll progress, reported 2 of 8 have been completed 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.721: Sleeping completed 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.721: Processing command SCAN print-id 378s (process:1904): libfprint-device-DEBUG: 00:53:47.721: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 378s (process:1904): libfprint-device-DEBUG: 00:53:47.721: Device reported finger status change: FP_FINGER_STATUS_NEEDED 378s (process:1904): libfprint-device-DEBUG: 00:53:47.721: Device reported enroll progress, reported 3 of 8 have been completed 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.721: Sleeping completed 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.721: Processing command RETRY 3 378s (process:1904): libfprint-device-DEBUG: 00:53:47.721: Device reported enroll progress, reported 3 of 8 have been completed 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.721: Sleeping completed 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.721: Processing command SCAN print-id 378s (process:1904): libfprint-device-DEBUG: 00:53:47.721: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 378s (process:1904): libfprint-device-DEBUG: 00:53:47.721: Device reported finger status change: FP_FINGER_STATUS_NEEDED 378s (process:1904): libfprint-device-DEBUG: 00:53:47.721: Device reported enroll progress, reported 4 of 8 have been completed 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.721: Sleeping completed 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.721: Processing command RETRY 2 378s (process:1904): libfprint-device-DEBUG: 00:53:47.721: Device reported enroll progress, reported 4 of 8 have been completed 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.721: Sleeping completed 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.721: Processing command SCAN print-id 378s (process:1904): libfprint-device-DEBUG: 00:53:47.721: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 378s (process:1904): libfprint-device-DEBUG: 00:53:47.721: Device reported finger status change: FP_FINGER_STATUS_NEEDED 378s (process:1904): libfprint-device-DEBUG: 00:53:47.721: Device reported enroll progress, reported 5 of 8 have been completed 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.721: Processing command SLEEP 10 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.721: Sleeping 10ms 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.731: Sleeping completed 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.731: Processing command SLEEP 20 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.731: Sleeping 20ms 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.751: Sleeping completed 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.751: Processing command RETRY 0 378s (process:1904): libfprint-device-DEBUG: 00:53:47.751: Device reported enroll progress, reported 5 of 8 have been completed 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.751: Sleeping completed 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.751: Processing command RETRY 3 378s (process:1904): libfprint-device-DEBUG: 00:53:47.751: Device reported enroll progress, reported 5 of 8 have been completed 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.751: Sleeping completed 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.751: Processing command SCAN print-id 378s (process:1904): libfprint-device-DEBUG: 00:53:47.751: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 378s (process:1904): libfprint-device-DEBUG: 00:53:47.751: Device reported finger status change: FP_FINGER_STATUS_NEEDED 378s (process:1904): libfprint-device-DEBUG: 00:53:47.751: Device reported enroll progress, reported 6 of 8 have been completed 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.751: Sleeping completed 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.751: Processing command SCAN another-id 378s (process:1904): libfprint-device-DEBUG: 00:53:47.751: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 378s (process:1904): libfprint-device-DEBUG: 00:53:47.751: Device reported enroll progress, reported 6 of 8 have been completed 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.751: Sleeping completed 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.751: Processing command SCAN print-id 378s (process:1904): libfprint-device-DEBUG: 00:53:47.751: Device reported finger status change: FP_FINGER_STATUS_NEEDED 378s (process:1904): libfprint-device-DEBUG: 00:53:47.751: Device reported enroll progress, reported 7 of 8 have been completed 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.751: Sleeping completed 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.751: Processing command SCAN print-id 378s (process:1904): libfprint-device-DEBUG: 00:53:47.751: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 378s (process:1904): libfprint-device-DEBUG: 00:53:47.751: Device reported finger status change: FP_FINGER_STATUS_NEEDED 378s (process:1904): libfprint-device-DEBUG: 00:53:47.751: Device reported enroll progress, reported 8 of 8 have been completed 378s (process:1904): libfprint-device-DEBUG: 00:53:47.751: Device reported enroll completion 378s (process:1904): libfprint-device-DEBUG: 00:53:47.751: Device reported finger status change: FP_FINGER_STATUS_NONE 378s (process:1904): libfprint-device-DEBUG: 00:53:47.751: Print for finger FP_FINGER_UNKNOWN enrolled 378s (process:1904): libfprint-device-DEBUG: 00:53:47.751: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 378s (process:1904): libfprint-device-DEBUG: 00:53:47.751: Updated temperature model after 0.03 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 378s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:47.752: Got a new connection! 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.752: Got instructions of length 5 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.752: Received command CONT 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.752: Processing command CONT 378s (process:1904): libfprint-device-DEBUG: 00:53:47.752: Device reported deletion completion 378s (process:1904): libfprint-device-DEBUG: 00:53:47.752: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 378s (process:1904): libfprint-device-DEBUG: 00:53:47.752: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 378s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:47.752: Got a new connection! 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.752: Got instructions of length 16 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.752: Received command SET_KEEP_ALIVE 0 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.752: Keep alive toggled: 0 378s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:47.752: Got a new connection! 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.752: Got instructions of length 19 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.752: Received command SET_ENROLL_STAGES 5 378s (process:1904): libfprint-device-DEBUG: 00:53:47.752: Device reported close completion 378s (process:1904): libfprint-device-DEBUG: 00:53:47.752: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 378s (process:1904): libfprint-device-DEBUG: 00:53:47.752: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 378s ok 378s test_enroll_script_interactive (__main__.VirtualDeviceStorage.test_enroll_script_interactive) ... (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.752: 7399795813758: ../libfprint/drivers/virtual-device.c:387 378s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:47.752: 7399795813767: ../libfprint/drivers/virtual-device-listener.c:153 378s (process:1904): libfprint-device-DEBUG: 00:53:47.753: Device reported open completion 378s (process:1904): libfprint-device-DEBUG: 00:53:47.753: Completing action FPI_DEVICE_ACTION_OPEN in idle! 378s (process:1904): libfprint-device-DEBUG: 00:53:47.753: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 378s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:47.753: Got a new connection! 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.753: Got instructions of length 8 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.753: Received command SLEEP 50 378s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:47.753: Got a new connection! 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.753: Got instructions of length 13 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.753: Received command SCAN print-id 378s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:47.753: Got a new connection! 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.753: Got instructions of length 13 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.753: Received command SCAN print-id 378s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:47.753: Got a new connection! 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.753: Got instructions of length 7 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.753: Received command RETRY 1 378s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:47.753: Got a new connection! 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.753: Got instructions of length 13 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.753: Received command SCAN print-id 378s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:47.754: Got a new connection! 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.754: Got instructions of length 8 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.754: Received command SLEEP 50 378s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:47.754: Got a new connection! 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.754: Got instructions of length 13 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.754: Received command SCAN print-id 378s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:47.754: Got a new connection! 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.754: Got instructions of length 7 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.754: Received command RETRY 2 378s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:47.754: Got a new connection! 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.754: Got instructions of length 15 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.754: Received command SCAN another-id 378s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:47.754: Got a new connection! 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.754: Got instructions of length 13 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.754: Received command SCAN print-id 378s (process:1904): libfprint-device-DEBUG: 00:53:47.754: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.754: Processing command SLEEP 50 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.754: Sleeping 50ms 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.804: Sleeping completed 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.805: Processing command SCAN print-id 378s (process:1904): libfprint-device-DEBUG: 00:53:47.805: Device reported finger status change: FP_FINGER_STATUS_NEEDED 378s (process:1904): libfprint-device-DEBUG: 00:53:47.805: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 378s (process:1904): libfprint-device-DEBUG: 00:53:47.805: Device reported finger status change: FP_FINGER_STATUS_NEEDED 378s (process:1904): libfprint-device-DEBUG: 00:53:47.805: Device reported enroll progress, reported 1 of 5 have been completed 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.805: Sleeping completed 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.805: Processing command SCAN print-id 378s (process:1904): libfprint-device-DEBUG: 00:53:47.805: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 378s (process:1904): libfprint-device-DEBUG: 00:53:47.805: Device reported finger status change: FP_FINGER_STATUS_NEEDED 378s (process:1904): libfprint-device-DEBUG: 00:53:47.805: Device reported enroll progress, reported 2 of 5 have been completed 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.805: Sleeping completed 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.805: Processing command RETRY 1 378s (process:1904): libfprint-device-DEBUG: 00:53:47.805: Device reported enroll progress, reported 2 of 5 have been completed 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.805: Sleeping completed 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.805: Processing command SCAN print-id 378s (process:1904): libfprint-device-DEBUG: 00:53:47.805: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 378s (process:1904): libfprint-device-DEBUG: 00:53:47.805: Device reported finger status change: FP_FINGER_STATUS_NEEDED 378s (process:1904): libfprint-device-DEBUG: 00:53:47.805: Device reported enroll progress, reported 3 of 5 have been completed 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.805: Processing command SLEEP 50 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.805: Sleeping 50ms 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.855: Sleeping completed 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.855: Processing command SCAN print-id 378s (process:1904): libfprint-device-DEBUG: 00:53:47.855: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 378s (process:1904): libfprint-device-DEBUG: 00:53:47.855: Device reported finger status change: FP_FINGER_STATUS_NEEDED 378s (process:1904): libfprint-device-DEBUG: 00:53:47.855: Device reported enroll progress, reported 4 of 5 have been completed 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.855: Sleeping completed 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.855: Processing command RETRY 2 378s (process:1904): libfprint-device-DEBUG: 00:53:47.855: Device reported enroll progress, reported 4 of 5 have been completed 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.855: Sleeping completed 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.855: Processing command SCAN another-id 378s (process:1904): libfprint-device-DEBUG: 00:53:47.855: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 378s (process:1904): libfprint-device-DEBUG: 00:53:47.855: Device reported enroll progress, reported 4 of 5 have been completed 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.855: Sleeping completed 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.855: Processing command SCAN print-id 378s (process:1904): libfprint-device-DEBUG: 00:53:47.855: Device reported finger status change: FP_FINGER_STATUS_NEEDED 378s (process:1904): libfprint-device-DEBUG: 00:53:47.855: Device reported enroll progress, reported 5 of 5 have been completed 378s (process:1904): libfprint-device-DEBUG: 00:53:47.856: Device reported enroll completion 378s (process:1904): libfprint-device-DEBUG: 00:53:47.856: Device reported finger status change: FP_FINGER_STATUS_NONE 378s (process:1904): libfprint-device-DEBUG: 00:53:47.856: Print for finger FP_FINGER_UNKNOWN enrolled 378s (process:1904): libfprint-device-DEBUG: 00:53:47.856: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 378s (process:1904): libfprint-device-DEBUG: 00:53:47.856: Updated temperature model after 0.10 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 378s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:47.857: Got a new connection! 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.858: Got instructions of length 5 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.858: Received command CONT 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.858: Processing command CONT 378s (process:1904): libfprint-device-DEBUG: 00:53:47.858: Device reported deletion completion 378s (process:1904): libfprint-device-DEBUG: 00:53:47.858: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 378s (process:1904): libfprint-device-DEBUG: 00:53:47.858: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 378s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:47.858: Got a new connection! 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.858: Got instructions of length 16 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.858: Received command SET_KEEP_ALIVE 0 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.858: Keep alive toggled: 0 378s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:47.859: Got a new connection! 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.859: Got instructions of length 19 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.860: Received command SET_ENROLL_STAGES 5 378s (process:1904): libfprint-device-DEBUG: 00:53:47.860: Device reported close completion 378s (process:1904): libfprint-device-DEBUG: 00:53:47.860: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 378s (process:1904): libfprint-device-DEBUG: 00:53:47.860: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 378s ok 378s test_enroll_verify_error (__main__.VirtualDeviceStorage.test_enroll_verify_error) ... (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.860: 7399795921680: ../libfprint/drivers/virtual-device.c:387 378s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:47.860: 7399795921706: ../libfprint/drivers/virtual-device-listener.c:153 378s (process:1904): libfprint-device-DEBUG: 00:53:47.861: Device reported open completion 378s (process:1904): libfprint-device-DEBUG: 00:53:47.861: Completing action FPI_DEVICE_ACTION_OPEN in idle! 378s (process:1904): libfprint-device-DEBUG: 00:53:47.861: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 378s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:47.863: Got a new connection! 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.863: Got instructions of length 14 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.863: Received command SCAN testprint 378s (process:1904): libfprint-device-DEBUG: 00:53:47.863: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.863: Processing command SCAN testprint 378s (process:1904): libfprint-device-DEBUG: 00:53:47.863: Device reported finger status change: FP_FINGER_STATUS_NEEDED 378s (process:1904): libfprint-device-DEBUG: 00:53:47.863: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 378s (process:1904): libfprint-device-DEBUG: 00:53:47.863: Device reported finger status change: FP_FINGER_STATUS_NEEDED 378s (process:1904): libfprint-device-DEBUG: 00:53:47.863: Device reported enroll progress, reported 1 of 5 have been completed 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.864: Sleeping completed 378s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:47.864: Got a new connection! 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.864: Got instructions of length 14 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.864: Received command SCAN testprint 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.864: Processing command SCAN testprint 378s (process:1904): libfprint-device-DEBUG: 00:53:47.864: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 378s (process:1904): libfprint-device-DEBUG: 00:53:47.864: Device reported finger status change: FP_FINGER_STATUS_NEEDED 378s (process:1904): libfprint-device-DEBUG: 00:53:47.864: Device reported enroll progress, reported 2 of 5 have been completed 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.864: Sleeping completed 378s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:47.865: Got a new connection! 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.865: Got instructions of length 14 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.865: Received command SCAN testprint 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.865: Processing command SCAN testprint 378s (process:1904): libfprint-device-DEBUG: 00:53:47.865: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 378s (process:1904): libfprint-device-DEBUG: 00:53:47.865: Device reported finger status change: FP_FINGER_STATUS_NEEDED 378s (process:1904): libfprint-device-DEBUG: 00:53:47.865: Device reported enroll progress, reported 3 of 5 have been completed 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.866: Sleeping completed 378s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:47.866: Got a new connection! 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.867: Got instructions of length 14 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.867: Received command SCAN testprint 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.867: Processing command SCAN testprint 378s (process:1904): libfprint-device-DEBUG: 00:53:47.867: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 378s (process:1904): libfprint-device-DEBUG: 00:53:47.867: Device reported finger status change: FP_FINGER_STATUS_NEEDED 378s (process:1904): libfprint-device-DEBUG: 00:53:47.867: Device reported enroll progress, reported 4 of 5 have been completed 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.867: Sleeping completed 378s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:47.868: Got a new connection! 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.868: Got instructions of length 14 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.868: Received command SCAN testprint 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.868: Processing command SCAN testprint 378s (process:1904): libfprint-device-DEBUG: 00:53:47.868: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 378s (process:1904): libfprint-device-DEBUG: 00:53:47.868: Device reported finger status change: FP_FINGER_STATUS_NEEDED 378s (process:1904): libfprint-device-DEBUG: 00:53:47.868: Device reported enroll progress, reported 5 of 5 have been completed 378s (process:1904): libfprint-device-DEBUG: 00:53:47.868: Device reported enroll completion 378s (process:1904): libfprint-device-DEBUG: 00:53:47.868: Device reported finger status change: FP_FINGER_STATUS_NONE 378s (process:1904): libfprint-device-DEBUG: 00:53:47.868: Print for finger FP_FINGER_LEFT_RING enrolled 378s (process:1904): libfprint-device-DEBUG: 00:53:47.868: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 378s (process:1904): libfprint-device-DEBUG: 00:53:47.868: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 378s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:47.869: Got a new connection! 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.869: Got instructions of length 7 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.869: Received command ERROR 0 378s (process:1904): libfprint-device-DEBUG: 00:53:47.870: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.870: Processing command ERROR 0 378s (process:1904): libfprint-device-DEBUG: 00:53:47.870: Device reported finger status change: FP_FINGER_STATUS_NEEDED 378s (process:1904): libfprint-device-DEBUG: 00:53:47.870: Device reported identify completion 378s (process:1904): libfprint-device-DEBUG: 00:53:47.870: Device reported finger status change: FP_FINGER_STATUS_NONE 378s (process:1904): libfprint-device-DEBUG: 00:53:47.870: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 378s (process:1904): libfprint-device-DEBUG: 00:53:47.870: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 378s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:47.870: Got a new connection! 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.870: Got instructions of length 5 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.870: Received command CONT 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.870: Processing command CONT 378s (process:1904): libfprint-device-DEBUG: 00:53:47.870: Device reported deletion completion 378s (process:1904): libfprint-device-DEBUG: 00:53:47.871: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 378s (process:1904): libfprint-device-DEBUG: 00:53:47.871: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 378s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:47.871: Got a new connection! 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.871: Got instructions of length 16 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.871: Received command SET_KEEP_ALIVE 0 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.871: Keep alive toggled: 0 378s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:47.871: Got a new connection! 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.871: Got instructions of length 19 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.871: Received command SET_ENROLL_STAGES 5 378s (process:1904): libfprint-device-DEBUG: 00:53:47.872: Device reported close completion 378s (process:1904): libfprint-device-DEBUG: 00:53:47.872: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 378s (process:1904): libfprint-device-DEBUG: 00:53:47.872: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 378s Enroll done 378s ok 378s test_enroll_verify_match (__main__.VirtualDeviceStorage.test_enroll_verify_match) ... (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.872: 7399795933527: ../libfprint/drivers/virtual-device.c:387 378s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:47.872: 7399795933576: ../libfprint/drivers/virtual-device-listener.c:153 378s (process:1904): libfprint-device-DEBUG: 00:53:47.873: Device reported open completion 378s (process:1904): libfprint-device-DEBUG: 00:53:47.873: Completing action FPI_DEVICE_ACTION_OPEN in idle! 378s (process:1904): libfprint-device-DEBUG: 00:53:47.873: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 378s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:47.873: Got a new connection! 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.873: Got instructions of length 14 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.874: Received command SCAN testprint 378s (process:1904): libfprint-device-DEBUG: 00:53:47.874: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.874: Processing command SCAN testprint 378s (process:1904): libfprint-device-DEBUG: 00:53:47.874: Device reported finger status change: FP_FINGER_STATUS_NEEDED 378s (process:1904): libfprint-device-DEBUG: 00:53:47.874: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 378s (process:1904): libfprint-device-DEBUG: 00:53:47.874: Device reported finger status change: FP_FINGER_STATUS_NEEDED 378s (process:1904): libfprint-device-DEBUG: 00:53:47.874: Device reported enroll progress, reported 1 of 5 have been completed 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.874: Sleeping completed 378s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:47.875: Got a new connection! 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.875: Got instructions of length 14 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.875: Received command SCAN testprint 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.875: Processing command SCAN testprint 378s (process:1904): libfprint-device-DEBUG: 00:53:47.875: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 378s (process:1904): libfprint-device-DEBUG: 00:53:47.875: Device reported finger status change: FP_FINGER_STATUS_NEEDED 378s (process:1904): libfprint-device-DEBUG: 00:53:47.875: Device reported enroll progress, reported 2 of 5 have been completed 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.875: Sleeping completed 378s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:47.875: Got a new connection! 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.875: Got instructions of length 14 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.875: Received command SCAN testprint 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.875: Processing command SCAN testprint 378s (process:1904): libfprint-device-DEBUG: 00:53:47.876: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 378s (process:1904): libfprint-device-DEBUG: 00:53:47.876: Device reported finger status change: FP_FINGER_STATUS_NEEDED 378s (process:1904): libfprint-device-DEBUG: 00:53:47.876: Device reported enroll progress, reported 3 of 5 have been completed 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.876: Sleeping completed 378s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:47.876: Got a new connection! 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.876: Got instructions of length 14 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.876: Received command SCAN testprint 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.876: Processing command SCAN testprint 378s (process:1904): libfprint-device-DEBUG: 00:53:47.876: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 378s (process:1904): libfprint-device-DEBUG: 00:53:47.876: Device reported finger status change: FP_FINGER_STATUS_NEEDED 378s (process:1904): libfprint-device-DEBUG: 00:53:47.876: Device reported enroll progress, reported 4 of 5 have been completed 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.876: Sleeping completed 378s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:47.877: Got a new connection! 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.877: Got instructions of length 14 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.877: Received command SCAN testprint 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.877: Processing command SCAN testprint 378s (process:1904): libfprint-device-DEBUG: 00:53:47.877: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 378s (process:1904): libfprint-device-DEBUG: 00:53:47.877: Device reported finger status change: FP_FINGER_STATUS_NEEDED 378s (process:1904): libfprint-device-DEBUG: 00:53:47.877: Device reported enroll progress, reported 5 of 5 have been completed 378s (process:1904): libfprint-device-DEBUG: 00:53:47.877: Device reported enroll completion 378s (process:1904): libfprint-device-DEBUG: 00:53:47.877: Device reported finger status change: FP_FINGER_STATUS_NONE 378s (process:1904): libfprint-device-DEBUG: 00:53:47.877: Print for finger FP_FINGER_LEFT_THUMB enrolled 378s (process:1904): libfprint-device-DEBUG: 00:53:47.877: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 378s (process:1904): libfprint-device-DEBUG: 00:53:47.877: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 378s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:47.878: Got a new connection! 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.878: Got instructions of length 14 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.878: Received command SCAN testprint 378s (process:1904): libfprint-device-DEBUG: 00:53:47.878: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.878: Processing command SCAN testprint 378s (process:1904): libfprint-device-DEBUG: 00:53:47.878: Device reported finger status change: FP_FINGER_STATUS_NEEDED 378s (process:1904): libfprint-device-DEBUG: 00:53:47.878: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 378s (process:1904): libfprint-virtual_device_storage-DEBUG: 00:53:47.878: Trying to identify print 'testprint' against a gallery of 1 prints 378s (process:1904): libfprint-device-DEBUG: 00:53:47.878: Device reported identify result 378s (process:1904): libfprint-device-DEBUG: 00:53:47.878: Device reported finger status change: FP_FINGER_STATUS_NEEDED 378s (process:1904): libfprint-device-DEBUG: 00:53:47.878: Device reported identify completion 378s (process:1904): libfprint-device-DEBUG: 00:53:47.878: Device reported finger status change: FP_FINGER_STATUS_NONE 378s (process:1904): libfprint-device-DEBUG: 00:53:47.878: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 378s (process:1904): libfprint-device-DEBUG: 00:53:47.878: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 378s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:47.879: Got a new connection! 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.879: Got instructions of length 5 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.879: Received command CONT 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.879: Processing command CONT 378s (process:1904): libfprint-device-DEBUG: 00:53:47.879: Device reported deletion completion 378s (process:1904): libfprint-device-DEBUG: 00:53:47.879: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 378s (process:1904): libfprint-device-DEBUG: 00:53:47.879: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 378s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:47.879: Got a new connection! 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.880: Got instructions of length 16 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.880: Received command SET_KEEP_ALIVE 0 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.880: Keep alive toggled: 0 378s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:47.880: Got a new connection! 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.880: Got instructions of length 19 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.880: Received command SET_ENROLL_STAGES 5 378s (process:1904): libfprint-device-DEBUG: 00:53:47.880: Device reported close completion 378s (process:1904): libfprint-device-DEBUG: 00:53:47.880: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 378s (process:1904): libfprint-device-DEBUG: 00:53:47.880: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 378s Enroll done 378s ok 378s test_enroll_verify_no_match (__main__.VirtualDeviceStorage.test_enroll_verify_no_match) ... (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.881: 7399795942092: ../libfprint/drivers/virtual-device.c:387 378s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:47.881: 7399795942152: ../libfprint/drivers/virtual-device-listener.c:153 378s (process:1904): libfprint-device-DEBUG: 00:53:47.881: Device reported open completion 378s (process:1904): libfprint-device-DEBUG: 00:53:47.881: Completing action FPI_DEVICE_ACTION_OPEN in idle! 378s (process:1904): libfprint-device-DEBUG: 00:53:47.881: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 378s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:47.882: Got a new connection! 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.882: Got instructions of length 14 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.882: Received command SCAN testprint 378s (process:1904): libfprint-device-DEBUG: 00:53:47.882: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.882: Processing command SCAN testprint 378s (process:1904): libfprint-device-DEBUG: 00:53:47.882: Device reported finger status change: FP_FINGER_STATUS_NEEDED 378s (process:1904): libfprint-device-DEBUG: 00:53:47.882: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 378s (process:1904): libfprint-device-DEBUG: 00:53:47.882: Device reported finger status change: FP_FINGER_STATUS_NEEDED 378s (process:1904): libfprint-device-DEBUG: 00:53:47.882: Device reported enroll progress, reported 1 of 5 have been completed 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.882: Sleeping completed 378s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:47.883: Got a new connection! 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.883: Got instructions of length 14 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.883: Received command SCAN testprint 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.883: Processing command SCAN testprint 378s (process:1904): libfprint-device-DEBUG: 00:53:47.883: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 378s (process:1904): libfprint-device-DEBUG: 00:53:47.883: Device reported finger status change: FP_FINGER_STATUS_NEEDED 378s (process:1904): libfprint-device-DEBUG: 00:53:47.883: Device reported enroll progress, reported 2 of 5 have been completed 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.883: Sleeping completed 378s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:47.884: Got a new connection! 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.884: Got instructions of length 14 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.884: Received command SCAN testprint 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.884: Processing command SCAN testprint 378s (process:1904): libfprint-device-DEBUG: 00:53:47.884: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 378s (process:1904): libfprint-device-DEBUG: 00:53:47.884: Device reported finger status change: FP_FINGER_STATUS_NEEDED 378s (process:1904): libfprint-device-DEBUG: 00:53:47.884: Device reported enroll progress, reported 3 of 5 have been completed 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.884: Sleeping completed 378s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:47.884: Got a new connection! 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.884: Got instructions of length 14 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.884: Received command SCAN testprint 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.884: Processing command SCAN testprint 378s (process:1904): libfprint-device-DEBUG: 00:53:47.884: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 378s (process:1904): libfprint-device-DEBUG: 00:53:47.884: Device reported finger status change: FP_FINGER_STATUS_NEEDED 378s (process:1904): libfprint-device-DEBUG: 00:53:47.884: Device reported enroll progress, reported 4 of 5 have been completed 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.884: Sleeping completed 378s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:47.885: Got a new connection! 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.885: Got instructions of length 14 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.885: Received command SCAN testprint 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.885: Processing command SCAN testprint 378s (process:1904): libfprint-device-DEBUG: 00:53:47.885: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 378s (process:1904): libfprint-device-DEBUG: 00:53:47.885: Device reported finger status change: FP_FINGER_STATUS_NEEDED 378s (process:1904): libfprint-device-DEBUG: 00:53:47.885: Device reported enroll progress, reported 5 of 5 have been completed 378s (process:1904): libfprint-device-DEBUG: 00:53:47.885: Device reported enroll completion 378s (process:1904): libfprint-device-DEBUG: 00:53:47.885: Device reported finger status change: FP_FINGER_STATUS_NONE 378s (process:1904): libfprint-device-DEBUG: 00:53:47.885: Print for finger FP_FINGER_LEFT_RING enrolled 378s (process:1904): libfprint-device-DEBUG: 00:53:47.885: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 378s (process:1904): libfprint-device-DEBUG: 00:53:47.885: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 378s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:47.886: Got a new connection! 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.886: Got instructions of length 18 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.886: Received command SCAN not-testprint 378s (process:1904): libfprint-device-DEBUG: 00:53:47.886: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.886: Processing command SCAN not-testprint 378s (process:1904): libfprint-device-DEBUG: 00:53:47.886: Device reported finger status change: FP_FINGER_STATUS_NEEDED 378s (process:1904): libfprint-device-DEBUG: 00:53:47.886: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 378s (process:1904): libfprint-virtual_device_storage-DEBUG: 00:53:47.887: Trying to identify print 'not-testprint' against a gallery of 1 prints 378s (process:1904): libfprint-device-DEBUG: 00:53:47.887: Device reported identify result 378s (process:1904): libfprint-device-DEBUG: 00:53:47.887: Device reported finger status change: FP_FINGER_STATUS_NEEDED 378s (process:1904): libfprint-device-DEBUG: 00:53:47.887: Device reported identify completion 378s (process:1904): libfprint-device-DEBUG: 00:53:47.887: Device reported finger status change: FP_FINGER_STATUS_NONE 378s (process:1904): libfprint-device-DEBUG: 00:53:47.887: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 378s (process:1904): libfprint-device-DEBUG: 00:53:47.887: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 378s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:47.887: Got a new connection! 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.887: Got instructions of length 5 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.887: Received command CONT 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.887: Processing command CONT 378s (process:1904): libfprint-device-DEBUG: 00:53:47.887: Device reported deletion completion 378s (process:1904): libfprint-device-DEBUG: 00:53:47.887: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 378s (process:1904): libfprint-device-DEBUG: 00:53:47.887: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 378s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:47.888: Got a new connection! 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.888: Got instructions of length 16 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.888: Received command SET_KEEP_ALIVE 0 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.888: Keep alive toggled: 0 378s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:47.888: Got a new connection! 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.888: Got instructions of length 19 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.888: Received command SET_ENROLL_STAGES 5 378s (process:1904): libfprint-device-DEBUG: 00:53:47.888: Device reported close completion 378s (process:1904): libfprint-device-DEBUG: 00:53:47.889: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 378s (process:1904): libfprint-device-DEBUG: 00:53:47.889: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 378s Enroll done 378s ok 378s test_enroll_verify_retry (__main__.VirtualDeviceStorage.test_enroll_verify_retry) ... (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.889: 7399795950328: ../libfprint/drivers/virtual-device.c:387 378s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:47.889: 7399795950371: ../libfprint/drivers/virtual-device-listener.c:153 378s (process:1904): libfprint-device-DEBUG: 00:53:47.889: Device reported open completion 378s (process:1904): libfprint-device-DEBUG: 00:53:47.890: Completing action FPI_DEVICE_ACTION_OPEN in idle! 378s (process:1904): libfprint-device-DEBUG: 00:53:47.890: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 378s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:47.890: Got a new connection! 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.890: Got instructions of length 7 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.890: Received command RETRY 1 378s (process:1904): libfprint-device-DEBUG: 00:53:47.891: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.891: Processing command RETRY 1 378s (process:1904): libfprint-device-DEBUG: 00:53:47.891: Device reported finger status change: FP_FINGER_STATUS_NEEDED 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.891: Virtual device scan failed with error: The swipe was too short, please try again. 378s (process:1904): libfprint-device-DEBUG: 00:53:47.891: Device reported verify result 378s (process:1904): libfprint-device-DEBUG: 00:53:47.891: Device reported verify completion 378s (process:1904): libfprint-device-DEBUG: 00:53:47.891: Device reported finger status change: FP_FINGER_STATUS_NONE 378s (process:1904): libfprint-device-DEBUG: 00:53:47.891: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 378s (process:1904): libfprint-device-DEBUG: 00:53:47.891: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 378s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:47.892: Got a new connection! 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.892: Got instructions of length 5 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.892: Received command CONT 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.892: Processing command CONT 378s (process:1904): libfprint-device-DEBUG: 00:53:47.892: Device reported deletion completion 378s (process:1904): libfprint-device-DEBUG: 00:53:47.892: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 378s (process:1904): libfprint-device-DEBUG: 00:53:47.892: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 378s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:47.892: Got a new connection! 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.892: Got instructions of length 16 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.892: Received command SET_KEEP_ALIVE 0 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.892: Keep alive toggled: 0 378s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:47.893: Got a new connection! 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.893: Got instructions of length 19 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.893: Received command SET_ENROLL_STAGES 5 378s (process:1904): libfprint-device-DEBUG: 00:53:47.893: Device reported close completion 378s (process:1904): libfprint-device-DEBUG: 00:53:47.893: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 378s (process:1904): libfprint-device-DEBUG: 00:53:47.893: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 378s ok 378s test_enroll_verify_script (__main__.VirtualDeviceStorage.test_enroll_verify_script) ... (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.893: 7399795954840: ../libfprint/drivers/virtual-device.c:387 378s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:47.893: 7399795954868: ../libfprint/drivers/virtual-device-listener.c:153 378s (process:1904): libfprint-device-DEBUG: 00:53:47.894: Device reported open completion 378s (process:1904): libfprint-device-DEBUG: 00:53:47.894: Completing action FPI_DEVICE_ACTION_OPEN in idle! 378s (process:1904): libfprint-device-DEBUG: 00:53:47.894: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 378s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:47.894: Got a new connection! 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.895: Got instructions of length 19 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.895: Received command SET_ENROLL_STAGES 8 378s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:47.895: Got a new connection! 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.895: Got instructions of length 13 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.895: Received command SCAN print-id 378s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:47.896: Got a new connection! 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.896: Got instructions of length 13 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.896: Received command SCAN print-id 378s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:47.896: Got a new connection! 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.896: Got instructions of length 7 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.896: Received command RETRY 1 378s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:47.896: Got a new connection! 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.896: Got instructions of length 13 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.896: Received command SCAN print-id 378s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:47.897: Got a new connection! 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.897: Got instructions of length 7 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.897: Received command RETRY 3 378s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:47.897: Got a new connection! 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.897: Got instructions of length 13 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.897: Received command SCAN print-id 378s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:47.897: Got a new connection! 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.897: Got instructions of length 7 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.897: Received command RETRY 2 378s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:47.898: Got a new connection! 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.898: Got instructions of length 13 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.898: Received command SCAN print-id 378s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:47.898: Got a new connection! 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.898: Got instructions of length 8 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.898: Received command SLEEP 10 378s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:47.898: Got a new connection! 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.898: Got instructions of length 8 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.898: Received command SLEEP 20 378s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:47.899: Got a new connection! 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.899: Got instructions of length 7 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.899: Received command RETRY 0 378s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:47.899: Got a new connection! 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.899: Got instructions of length 7 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.899: Received command RETRY 3 378s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:47.899: Got a new connection! 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.899: Got instructions of length 13 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.899: Received command SCAN print-id 378s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:47.900: Got a new connection! 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.900: Got instructions of length 15 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.900: Received command SCAN another-id 378s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:47.900: Got a new connection! 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.900: Got instructions of length 13 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.900: Received command SCAN print-id 378s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:47.900: Got a new connection! 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.900: Got instructions of length 13 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.900: Received command SCAN print-id 378s (process:1904): libfprint-device-DEBUG: 00:53:47.900: Updated temperature model after 0.01 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.900: Processing command SCAN print-id 378s (process:1904): libfprint-device-DEBUG: 00:53:47.900: Device reported finger status change: FP_FINGER_STATUS_NEEDED 378s (process:1904): libfprint-device-DEBUG: 00:53:47.900: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 378s (process:1904): libfprint-device-DEBUG: 00:53:47.901: Device reported finger status change: FP_FINGER_STATUS_NEEDED 378s (process:1904): libfprint-device-DEBUG: 00:53:47.901: Device reported enroll progress, reported 1 of 8 have been completed 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.901: Sleeping completed 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.901: Processing command SCAN print-id 378s (process:1904): libfprint-device-DEBUG: 00:53:47.901: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 378s (process:1904): libfprint-device-DEBUG: 00:53:47.901: Device reported finger status change: FP_FINGER_STATUS_NEEDED 378s (process:1904): libfprint-device-DEBUG: 00:53:47.901: Device reported enroll progress, reported 2 of 8 have been completed 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.901: Sleeping completed 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.901: Processing command RETRY 1 378s (process:1904): libfprint-device-DEBUG: 00:53:47.901: Device reported enroll progress, reported 2 of 8 have been completed 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.901: Sleeping completed 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.901: Processing command SCAN print-id 378s (process:1904): libfprint-device-DEBUG: 00:53:47.901: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 378s (process:1904): libfprint-device-DEBUG: 00:53:47.901: Device reported finger status change: FP_FINGER_STATUS_NEEDED 378s (process:1904): libfprint-device-DEBUG: 00:53:47.901: Device reported enroll progress, reported 3 of 8 have been completed 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.901: Sleeping completed 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.901: Processing command RETRY 3 378s (process:1904): libfprint-device-DEBUG: 00:53:47.901: Device reported enroll progress, reported 3 of 8 have been completed 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.901: Sleeping completed 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.901: Processing command SCAN print-id 378s (process:1904): libfprint-device-DEBUG: 00:53:47.901: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 378s (process:1904): libfprint-device-DEBUG: 00:53:47.901: Device reported finger status change: FP_FINGER_STATUS_NEEDED 378s (process:1904): libfprint-device-DEBUG: 00:53:47.901: Device reported enroll progress, reported 4 of 8 have been completed 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.901: Sleeping completed 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.901: Processing command RETRY 2 378s (process:1904): libfprint-device-DEBUG: 00:53:47.901: Device reported enroll progress, reported 4 of 8 have been completed 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.901: Sleeping completed 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.901: Processing command SCAN print-id 378s (process:1904): libfprint-device-DEBUG: 00:53:47.901: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 378s (process:1904): libfprint-device-DEBUG: 00:53:47.901: Device reported finger status change: FP_FINGER_STATUS_NEEDED 378s (process:1904): libfprint-device-DEBUG: 00:53:47.901: Device reported enroll progress, reported 5 of 8 have been completed 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.901: Processing command SLEEP 10 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.901: Sleeping 10ms 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.911: Sleeping completed 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.911: Processing command SLEEP 20 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.911: Sleeping 20ms 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.931: Sleeping completed 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.931: Processing command RETRY 0 378s (process:1904): libfprint-device-DEBUG: 00:53:47.931: Device reported enroll progress, reported 5 of 8 have been completed 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.931: Sleeping completed 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.931: Processing command RETRY 3 378s (process:1904): libfprint-device-DEBUG: 00:53:47.931: Device reported enroll progress, reported 5 of 8 have been completed 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.931: Sleeping completed 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.931: Processing command SCAN print-id 378s (process:1904): libfprint-device-DEBUG: 00:53:47.931: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 378s (process:1904): libfprint-device-DEBUG: 00:53:47.931: Device reported finger status change: FP_FINGER_STATUS_NEEDED 378s (process:1904): libfprint-device-DEBUG: 00:53:47.931: Device reported enroll progress, reported 6 of 8 have been completed 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.931: Sleeping completed 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.931: Processing command SCAN another-id 378s (process:1904): libfprint-device-DEBUG: 00:53:47.932: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 378s (process:1904): libfprint-device-DEBUG: 00:53:47.932: Device reported enroll progress, reported 6 of 8 have been completed 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.932: Sleeping completed 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.932: Processing command SCAN print-id 378s (process:1904): libfprint-device-DEBUG: 00:53:47.932: Device reported finger status change: FP_FINGER_STATUS_NEEDED 378s (process:1904): libfprint-device-DEBUG: 00:53:47.932: Device reported enroll progress, reported 7 of 8 have been completed 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.932: Sleeping completed 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.932: Processing command SCAN print-id 378s (process:1904): libfprint-device-DEBUG: 00:53:47.932: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 378s (process:1904): libfprint-device-DEBUG: 00:53:47.932: Device reported finger status change: FP_FINGER_STATUS_NEEDED 378s (process:1904): libfprint-device-DEBUG: 00:53:47.932: Device reported enroll progress, reported 8 of 8 have been completed 378s (process:1904): libfprint-device-DEBUG: 00:53:47.932: Device reported enroll completion 378s (process:1904): libfprint-device-DEBUG: 00:53:47.932: Device reported finger status change: FP_FINGER_STATUS_NONE 378s (process:1904): libfprint-device-DEBUG: 00:53:47.932: Print for finger FP_FINGER_UNKNOWN enrolled 378s (process:1904): libfprint-device-DEBUG: 00:53:47.932: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 378s (process:1904): libfprint-device-DEBUG: 00:53:47.932: Updated temperature model after 0.03 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 378s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:47.932: Got a new connection! 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.932: Got instructions of length 7 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.932: Received command RETRY 2 378s (process:1904): libfprint-device-DEBUG: 00:53:47.932: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.932: Processing command RETRY 2 378s (process:1904): libfprint-device-DEBUG: 00:53:47.932: Device reported finger status change: FP_FINGER_STATUS_NEEDED 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.932: Virtual device scan failed with error: The finger was not centered properly, please try again. 378s (process:1904): libfprint-device-DEBUG: 00:53:47.932: Device reported verify result 378s (process:1904): libfprint-device-DEBUG: 00:53:47.932: Device reported verify completion 378s (process:1904): libfprint-device-DEBUG: 00:53:47.932: Device reported finger status change: FP_FINGER_STATUS_NONE 378s (process:1904): libfprint-device-DEBUG: 00:53:47.932: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 378s (process:1904): libfprint-device-DEBUG: 00:53:47.932: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 378s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:47.932: Got a new connection! 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.933: Got instructions of length 8 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.933: Received command SLEEP 50 378s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:47.933: Got a new connection! 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.933: Got instructions of length 7 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.933: Received command RETRY 1 378s (process:1904): libfprint-device-DEBUG: 00:53:47.933: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.933: Processing command SLEEP 50 378s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.933: Sleeping 50ms 379s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.983: Sleeping completed 379s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.983: Processing command RETRY 1 379s (process:1904): libfprint-device-DEBUG: 00:53:47.983: Device reported finger status change: FP_FINGER_STATUS_NEEDED 379s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.983: Virtual device scan failed with error: The swipe was too short, please try again. 379s (process:1904): libfprint-device-DEBUG: 00:53:47.983: Device reported verify result 379s (process:1904): libfprint-device-DEBUG: 00:53:47.983: Device reported verify completion 379s (process:1904): libfprint-device-DEBUG: 00:53:47.983: Device reported finger status change: FP_FINGER_STATUS_NONE 379s (process:1904): libfprint-device-DEBUG: 00:53:47.983: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 379s (process:1904): libfprint-device-DEBUG: 00:53:47.983: Updated temperature model after 0.05 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 379s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:47.983: Got a new connection! 379s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.984: Got instructions of length 15 379s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.984: Received command SCAN another-id 379s (process:1904): libfprint-device-DEBUG: 00:53:47.984: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 379s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.984: Processing command SCAN another-id 379s (process:1904): libfprint-device-DEBUG: 00:53:47.984: Device reported finger status change: FP_FINGER_STATUS_NEEDED 379s (process:1904): libfprint-device-DEBUG: 00:53:47.984: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 379s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.984: Virtual device scanned print another-id 379s (process:1904): libfprint-device-DEBUG: 00:53:47.984: Device reported verify result 379s (process:1904): libfprint-device-DEBUG: 00:53:47.984: Device reported finger status change: FP_FINGER_STATUS_NEEDED 379s (process:1904): libfprint-device-DEBUG: 00:53:47.984: Device reported verify completion 379s (process:1904): libfprint-device-DEBUG: 00:53:47.984: Device reported finger status change: FP_FINGER_STATUS_NONE 379s (process:1904): libfprint-device-DEBUG: 00:53:47.984: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 379s (process:1904): libfprint-device-DEBUG: 00:53:47.984: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 379s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:47.984: Got a new connection! 379s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.984: Got instructions of length 13 379s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.984: Received command SCAN print-id 379s (process:1904): libfprint-device-DEBUG: 00:53:47.984: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 379s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.984: Processing command SCAN print-id 379s (process:1904): libfprint-device-DEBUG: 00:53:47.984: Device reported finger status change: FP_FINGER_STATUS_NEEDED 379s (process:1904): libfprint-device-DEBUG: 00:53:47.984: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 379s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.984: Virtual device scanned print print-id 379s (process:1904): libfprint-device-DEBUG: 00:53:47.984: Device reported verify result 379s (process:1904): libfprint-device-DEBUG: 00:53:47.984: Device reported finger status change: FP_FINGER_STATUS_NEEDED 379s (process:1904): libfprint-device-DEBUG: 00:53:47.984: Device reported verify completion 379s (process:1904): libfprint-device-DEBUG: 00:53:47.984: Device reported finger status change: FP_FINGER_STATUS_NONE 379s (process:1904): libfprint-device-DEBUG: 00:53:47.984: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 379s (process:1904): libfprint-device-DEBUG: 00:53:47.984: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 379s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:47.984: Got a new connection! 379s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.984: Got instructions of length 5 379s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.984: Received command CONT 379s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.984: Processing command CONT 379s (process:1904): libfprint-device-DEBUG: 00:53:47.984: Device reported deletion completion 379s (process:1904): libfprint-device-DEBUG: 00:53:47.984: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 379s (process:1904): libfprint-device-DEBUG: 00:53:47.984: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 379s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:47.985: Got a new connection! 379s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.985: Got instructions of length 16 379s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.985: Received command SET_KEEP_ALIVE 0 379s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.985: Keep alive toggled: 0 379s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:47.985: Got a new connection! 379s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.985: Got instructions of length 19 379s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.985: Received command SET_ENROLL_STAGES 5 379s (process:1904): libfprint-device-DEBUG: 00:53:47.985: Device reported close completion 379s (process:1904): libfprint-device-DEBUG: 00:53:47.985: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 379s (process:1904): libfprint-device-DEBUG: 00:53:47.985: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 379s ok 379s test_enroll_with_retry (__main__.VirtualDeviceStorage.test_enroll_with_retry) ... (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.985: 7399796046433: ../libfprint/drivers/virtual-device.c:387 379s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:47.985: 7399796046448: ../libfprint/drivers/virtual-device-listener.c:153 379s (process:1904): libfprint-device-DEBUG: 00:53:47.985: Device reported open completion 379s (process:1904): libfprint-device-DEBUG: 00:53:47.985: Completing action FPI_DEVICE_ACTION_OPEN in idle! 379s (process:1904): libfprint-device-DEBUG: 00:53:47.985: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 379s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:47.985: Got a new connection! 379s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.986: Got instructions of length 14 379s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.986: Received command SCAN testprint 379s (process:1904): libfprint-device-DEBUG: 00:53:47.986: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 379s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.986: Processing command SCAN testprint 379s (process:1904): libfprint-device-DEBUG: 00:53:47.986: Device reported finger status change: FP_FINGER_STATUS_NEEDED 379s (process:1904): libfprint-device-DEBUG: 00:53:47.986: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 379s (process:1904): libfprint-device-DEBUG: 00:53:47.986: Device reported finger status change: FP_FINGER_STATUS_NEEDED 379s (process:1904): libfprint-device-DEBUG: 00:53:47.986: Device reported enroll progress, reported 1 of 5 have been completed 379s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.986: Sleeping completed 379s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:47.986: Got a new connection! 379s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.986: Got instructions of length 14 379s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.986: Received command SCAN testprint 379s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.986: Processing command SCAN testprint 379s (process:1904): libfprint-device-DEBUG: 00:53:47.986: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 379s (process:1904): libfprint-device-DEBUG: 00:53:47.986: Device reported finger status change: FP_FINGER_STATUS_NEEDED 379s (process:1904): libfprint-device-DEBUG: 00:53:47.986: Device reported enroll progress, reported 2 of 5 have been completed 379s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.986: Sleeping completed 379s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:47.986: Got a new connection! 379s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.986: Got instructions of length 7 379s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.986: Received command RETRY 1 379s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.986: Processing command RETRY 1 379s (process:1904): libfprint-device-DEBUG: 00:53:47.986: Device reported enroll progress, reported 2 of 5 have been completed 379s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.986: Sleeping completed 379s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:47.986: Got a new connection! 379s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.987: Got instructions of length 14 379s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.987: Received command SCAN testprint 379s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.987: Processing command SCAN testprint 379s (process:1904): libfprint-device-DEBUG: 00:53:47.987: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 379s (process:1904): libfprint-device-DEBUG: 00:53:47.987: Device reported finger status change: FP_FINGER_STATUS_NEEDED 379s (process:1904): libfprint-device-DEBUG: 00:53:47.987: Device reported enroll progress, reported 3 of 5 have been completed 379s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.987: Sleeping completed 379s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:47.987: Got a new connection! 379s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.987: Got instructions of length 14 379s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.987: Received command SCAN testprint 379s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.987: Processing command SCAN testprint 379s (process:1904): libfprint-device-DEBUG: 00:53:47.987: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 379s (process:1904): libfprint-device-DEBUG: 00:53:47.987: Device reported finger status change: FP_FINGER_STATUS_NEEDED 379s (process:1904): libfprint-device-DEBUG: 00:53:47.987: Device reported enroll progress, reported 4 of 5 have been completed 379s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.987: Sleeping completed 379s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:47.987: Got a new connection! 379s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.987: Got instructions of length 14 379s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.987: Received command SCAN testprint 379s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.987: Processing command SCAN testprint 379s (process:1904): libfprint-device-DEBUG: 00:53:47.987: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 379s (process:1904): libfprint-device-DEBUG: 00:53:47.987: Device reported finger status change: FP_FINGER_STATUS_NEEDED 379s (process:1904): libfprint-device-DEBUG: 00:53:47.987: Device reported enroll progress, reported 5 of 5 have been completed 379s (process:1904): libfprint-device-DEBUG: 00:53:47.987: Device reported enroll completion 379s (process:1904): libfprint-device-DEBUG: 00:53:47.987: Device reported finger status change: FP_FINGER_STATUS_NONE 379s (process:1904): libfprint-device-DEBUG: 00:53:47.987: Print for finger FP_FINGER_LEFT_LITTLE enrolled 379s (process:1904): libfprint-device-DEBUG: 00:53:47.987: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 379s (process:1904): libfprint-device-DEBUG: 00:53:47.987: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 379s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:47.988: Got a new connection! 379s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.988: Got instructions of length 5 379s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.988: Received command CONT 379s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.988: Processing command CONT 379s (process:1904): libfprint-device-DEBUG: 00:53:47.988: Device reported deletion completion 379s (process:1904): libfprint-device-DEBUG: 00:53:47.988: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 379s (process:1904): libfprint-device-DEBUG: 00:53:47.988: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 379s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:47.988: Got a new connection! 379s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.988: Got instructions of length 16 379s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.988: Received command SET_KEEP_ALIVE 0 379s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.988: Keep alive toggled: 0 379s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:47.988: Got a new connection! 379s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.988: Got instructions of length 19 379s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.988: Received command SET_ENROLL_STAGES 5 379s (process:1904): libfprint-device-DEBUG: 00:53:47.988: Device reported close completion 379s (process:1904): libfprint-device-DEBUG: 00:53:47.988: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 379s (process:1904): libfprint-device-DEBUG: 00:53:47.988: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 379s Enroll done 379s ok 379s test_finger_status (__main__.VirtualDeviceStorage.test_finger_status) ... (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.988: 7399796049769: ../libfprint/drivers/virtual-device.c:387 379s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:47.988: 7399796049783: ../libfprint/drivers/virtual-device-listener.c:153 379s (process:1904): libfprint-device-DEBUG: 00:53:47.989: Device reported open completion 379s (process:1904): libfprint-device-DEBUG: 00:53:47.989: Completing action FPI_DEVICE_ACTION_OPEN in idle! 379s (process:1904): libfprint-device-DEBUG: 00:53:47.989: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 379s (process:1904): libfprint-device-DEBUG: 00:53:47.989: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 379s (process:1904): libfprint-device-DEBUG: 00:53:47.989: Device reported finger status change: FP_FINGER_STATUS_NEEDED 379s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:47.989: Got a new connection! 379s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.989: Got instructions of length 8 379s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.989: Received command FINGER 1 379s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.989: Processing command FINGER 1 379s (process:1904): libfprint-device-DEBUG: 00:53:47.989: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 379s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:47.989: Got a new connection! 379s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.989: Got instructions of length 8 379s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.989: Received command FINGER 0 379s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.989: Processing command FINGER 0 379s (process:1904): libfprint-device-DEBUG: 00:53:47.989: Device reported finger status change: FP_FINGER_STATUS_NEEDED 379s (process:1904): libfprint-device-DEBUG: 00:53:47.989: Idle cancelling on ongoing operation! 379s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.989: Got cancellation! 379s (process:1904): libfprint-device-DEBUG: 00:53:47.989: Device reported identify completion 379s (process:1904): libfprint-device-DEBUG: 00:53:47.989: Device reported finger status change: FP_FINGER_STATUS_NONE 379s (process:1904): libfprint-device-DEBUG: 00:53:47.989: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 379s (process:1904): libfprint-device-DEBUG: 00:53:47.989: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 379s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:47.990: Got a new connection! 379s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.990: Got instructions of length 5 379s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.990: Received command CONT 379s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.990: Processing command CONT 379s (process:1904): libfprint-device-DEBUG: 00:53:47.990: Device reported deletion completion 379s (process:1904): libfprint-device-DEBUG: 00:53:47.990: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 379s (process:1904): libfprint-device-DEBUG: 00:53:47.990: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 379s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:47.990: Got a new connection! 379s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.990: Got instructions of length 16 379s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.990: Received command SET_KEEP_ALIVE 0 379s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.990: Keep alive toggled: 0 379s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:47.990: Got a new connection! 379s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.990: Got instructions of length 19 379s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.990: Received command SET_ENROLL_STAGES 5 379s (process:1904): libfprint-device-DEBUG: 00:53:47.990: Device reported close completion 379s (process:1904): libfprint-device-DEBUG: 00:53:47.990: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 379s (process:1904): libfprint-device-DEBUG: 00:53:47.990: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 379s ok 379s test_finger_status_after_sleep (__main__.VirtualDeviceStorage.test_finger_status_after_sleep) ... (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.991: 7399796051979: ../libfprint/drivers/virtual-device.c:387 379s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:47.991: 7399796051993: ../libfprint/drivers/virtual-device-listener.c:153 379s (process:1904): libfprint-device-DEBUG: 00:53:47.991: Device reported open completion 379s (process:1904): libfprint-device-DEBUG: 00:53:47.991: Completing action FPI_DEVICE_ACTION_OPEN in idle! 379s (process:1904): libfprint-device-DEBUG: 00:53:47.991: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 379s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:47.991: Got a new connection! 379s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.991: Got instructions of length 8 379s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.991: Received command SLEEP 10 379s (process:1904): libfprint-device-DEBUG: 00:53:47.991: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 379s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.991: Processing command SLEEP 10 379s (process:1904): libfprint-virtual_device-DEBUG: 00:53:47.991: Sleeping 10ms 379s (process:1904): libfprint-virtual_device-DEBUG: 00:53:48.001: Sleeping completed 379s (process:1904): libfprint-device-DEBUG: 00:53:48.001: Device reported finger status change: FP_FINGER_STATUS_NEEDED 379s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:48.002: Got a new connection! 379s (process:1904): libfprint-virtual_device-DEBUG: 00:53:48.002: Got instructions of length 8 379s (process:1904): libfprint-virtual_device-DEBUG: 00:53:48.002: Received command FINGER 1 379s (process:1904): libfprint-virtual_device-DEBUG: 00:53:48.002: Processing command FINGER 1 379s (process:1904): libfprint-device-DEBUG: 00:53:48.002: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 379s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:48.002: Got a new connection! 379s (process:1904): libfprint-virtual_device-DEBUG: 00:53:48.002: Got instructions of length 8 379s (process:1904): libfprint-virtual_device-DEBUG: 00:53:48.002: Received command FINGER 0 379s (process:1904): libfprint-virtual_device-DEBUG: 00:53:48.002: Processing command FINGER 0 379s (process:1904): libfprint-device-DEBUG: 00:53:48.002: Device reported finger status change: FP_FINGER_STATUS_NEEDED 379s (process:1904): libfprint-device-DEBUG: 00:53:48.002: Idle cancelling on ongoing operation! 379s (process:1904): libfprint-virtual_device-DEBUG: 00:53:48.002: Got cancellation! 379s (process:1904): libfprint-device-DEBUG: 00:53:48.002: Device reported identify completion 379s (process:1904): libfprint-device-DEBUG: 00:53:48.002: Device reported finger status change: FP_FINGER_STATUS_NONE 379s (process:1904): libfprint-device-DEBUG: 00:53:48.002: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 379s (process:1904): libfprint-device-DEBUG: 00:53:48.002: Updated temperature model after 0.01 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 379s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:48.002: Got a new connection! 379s (process:1904): libfprint-virtual_device-DEBUG: 00:53:48.002: Got instructions of length 5 379s (process:1904): libfprint-virtual_device-DEBUG: 00:53:48.002: Received command CONT 379s (process:1904): libfprint-virtual_device-DEBUG: 00:53:48.002: Processing command CONT 379s (process:1904): libfprint-device-DEBUG: 00:53:48.002: Device reported deletion completion 379s (process:1904): libfprint-device-DEBUG: 00:53:48.002: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 379s (process:1904): libfprint-device-DEBUG: 00:53:48.002: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 379s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:48.003: Got a new connection! 379s (process:1904): libfprint-virtual_device-DEBUG: 00:53:48.003: Got instructions of length 16 379s (process:1904): libfprint-virtual_device-DEBUG: 00:53:48.003: Received command SET_KEEP_ALIVE 0 379s (process:1904): libfprint-virtual_device-DEBUG: 00:53:48.003: Keep alive toggled: 0 379s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:48.003: Got a new connection! 379s (process:1904): libfprint-virtual_device-DEBUG: 00:53:48.003: Got instructions of length 19 379s (process:1904): libfprint-virtual_device-DEBUG: 00:53:48.003: Received command SET_ENROLL_STAGES 5 379s (process:1904): libfprint-device-DEBUG: 00:53:48.003: Device reported close completion 379s (process:1904): libfprint-device-DEBUG: 00:53:48.003: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 379s (process:1904): libfprint-device-DEBUG: 00:53:48.003: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 379s ok 379s test_identify_match (__main__.VirtualDeviceStorage.test_identify_match) ... (process:1904): libfprint-virtual_device-DEBUG: 00:53:48.003: 7399796064506: ../libfprint/drivers/virtual-device.c:387 379s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:48.003: 7399796064517: ../libfprint/drivers/virtual-device-listener.c:153 379s (process:1904): libfprint-device-DEBUG: 00:53:48.003: Device reported open completion 379s (process:1904): libfprint-device-DEBUG: 00:53:48.003: Completing action FPI_DEVICE_ACTION_OPEN in idle! 379s (process:1904): libfprint-device-DEBUG: 00:53:48.003: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 379s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:48.003: Got a new connection! 379s (process:1904): libfprint-virtual_device-DEBUG: 00:53:48.004: Got instructions of length 16 379s (process:1904): libfprint-virtual_device-DEBUG: 00:53:48.004: Received command SCAN right-thumb 379s (process:1904): libfprint-device-DEBUG: 00:53:48.004: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 379s (process:1904): libfprint-virtual_device-DEBUG: 00:53:48.004: Processing command SCAN right-thumb 379s (process:1904): libfprint-device-DEBUG: 00:53:48.004: Device reported finger status change: FP_FINGER_STATUS_NEEDED 379s (process:1904): libfprint-device-DEBUG: 00:53:48.004: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 379s (process:1904): libfprint-device-DEBUG: 00:53:48.004: Device reported finger status change: FP_FINGER_STATUS_NEEDED 379s (process:1904): libfprint-device-DEBUG: 00:53:48.004: Device reported enroll progress, reported 1 of 5 have been completed 379s (process:1904): libfprint-virtual_device-DEBUG: 00:53:48.004: Sleeping completed 379s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:48.004: Got a new connection! 379s (process:1904): libfprint-virtual_device-DEBUG: 00:53:48.004: Got instructions of length 16 379s (process:1904): libfprint-virtual_device-DEBUG: 00:53:48.004: Received command SCAN right-thumb 379s (process:1904): libfprint-virtual_device-DEBUG: 00:53:48.004: Processing command SCAN right-thumb 379s (process:1904): libfprint-device-DEBUG: 00:53:48.004: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 379s (process:1904): libfprint-device-DEBUG: 00:53:48.004: Device reported finger status change: FP_FINGER_STATUS_NEEDED 379s (process:1904): libfprint-device-DEBUG: 00:53:48.004: Device reported enroll progress, reported 2 of 5 have been completed 379s (process:1904): libfprint-virtual_device-DEBUG: 00:53:48.004: Sleeping completed 379s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:48.004: Got a new connection! 379s (process:1904): libfprint-virtual_device-DEBUG: 00:53:48.004: Got instructions of length 16 379s (process:1904): libfprint-virtual_device-DEBUG: 00:53:48.004: Received command SCAN right-thumb 379s (process:1904): libfprint-virtual_device-DEBUG: 00:53:48.004: Processing command SCAN right-thumb 379s (process:1904): libfprint-device-DEBUG: 00:53:48.004: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 379s (process:1904): libfprint-device-DEBUG: 00:53:48.004: Device reported finger status change: FP_FINGER_STATUS_NEEDED 379s (process:1904): libfprint-device-DEBUG: 00:53:48.004: Device reported enroll progress, reported 3 of 5 have been completed 379s (process:1904): libfprint-virtual_device-DEBUG: 00:53:48.004: Sleeping completed 379s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:48.004: Got a new connection! 379s (process:1904): libfprint-virtual_device-DEBUG: 00:53:48.005: Got instructions of length 16 379s (process:1904): libfprint-virtual_device-DEBUG: 00:53:48.005: Received command SCAN right-thumb 379s (process:1904): libfprint-virtual_device-DEBUG: 00:53:48.005: Processing command SCAN right-thumb 379s (process:1904): libfprint-device-DEBUG: 00:53:48.005: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 379s (process:1904): libfprint-device-DEBUG: 00:53:48.005: Device reported finger status change: FP_FINGER_STATUS_NEEDED 379s (process:1904): libfprint-device-DEBUG: 00:53:48.005: Device reported enroll progress, reported 4 of 5 have been completed 379s (process:1904): libfprint-virtual_device-DEBUG: 00:53:48.005: Sleeping completed 379s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:48.005: Got a new connection! 379s (process:1904): libfprint-virtual_device-DEBUG: 00:53:48.005: Got instructions of length 16 379s (process:1904): libfprint-virtual_device-DEBUG: 00:53:48.005: Received command SCAN right-thumb 379s (process:1904): libfprint-virtual_device-DEBUG: 00:53:48.005: Processing command SCAN right-thumb 379s (process:1904): libfprint-device-DEBUG: 00:53:48.005: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 379s (process:1904): libfprint-device-DEBUG: 00:53:48.005: Device reported finger status change: FP_FINGER_STATUS_NEEDED 379s (process:1904): libfprint-device-DEBUG: 00:53:48.005: Device reported enroll progress, reported 5 of 5 have been completed 379s (process:1904): libfprint-device-DEBUG: 00:53:48.005: Device reported enroll completion 379s (process:1904): libfprint-device-DEBUG: 00:53:48.005: Device reported finger status change: FP_FINGER_STATUS_NONE 379s (process:1904): libfprint-device-DEBUG: 00:53:48.005: Print for finger FP_FINGER_RIGHT_THUMB enrolled 379s (process:1904): libfprint-device-DEBUG: 00:53:48.005: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 379s (process:1904): libfprint-device-DEBUG: 00:53:48.005: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 379s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:48.005: Got a new connection! 379s (process:1904): libfprint-virtual_device-DEBUG: 00:53:48.005: Got instructions of length 15 379s (process:1904): libfprint-virtual_device-DEBUG: 00:53:48.005: Received command SCAN left-thumb 379s (process:1904): libfprint-device-DEBUG: 00:53:48.005: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 379s (process:1904): libfprint-virtual_device-DEBUG: 00:53:48.005: Processing command SCAN left-thumb 379s (process:1904): libfprint-device-DEBUG: 00:53:48.005: Device reported finger status change: FP_FINGER_STATUS_NEEDED 379s (process:1904): libfprint-device-DEBUG: 00:53:48.005: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 379s (process:1904): libfprint-device-DEBUG: 00:53:48.005: Device reported finger status change: FP_FINGER_STATUS_NEEDED 379s (process:1904): libfprint-device-DEBUG: 00:53:48.005: Device reported enroll progress, reported 1 of 5 have been completed 379s (process:1904): libfprint-virtual_device-DEBUG: 00:53:48.005: Sleeping completed 379s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:48.005: Got a new connection! 379s (process:1904): libfprint-virtual_device-DEBUG: 00:53:48.006: Got instructions of length 15 379s (process:1904): libfprint-virtual_device-DEBUG: 00:53:48.006: Received command SCAN left-thumb 379s (process:1904): libfprint-virtual_device-DEBUG: 00:53:48.006: Processing command SCAN left-thumb 379s (process:1904): libfprint-device-DEBUG: 00:53:48.006: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 379s (process:1904): libfprint-device-DEBUG: 00:53:48.006: Device reported finger status change: FP_FINGER_STATUS_NEEDED 379s (process:1904): libfprint-device-DEBUG: 00:53:48.006: Device reported enroll progress, reported 2 of 5 have been completed 379s (process:1904): libfprint-virtual_device-DEBUG: 00:53:48.006: Sleeping completed 379s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:48.006: Got a new connection! 379s (process:1904): libfprint-virtual_device-DEBUG: 00:53:48.006: Got instructions of length 15 379s (process:1904): libfprint-virtual_device-DEBUG: 00:53:48.006: Received command SCAN left-thumb 379s (process:1904): libfprint-virtual_device-DEBUG: 00:53:48.006: Processing command SCAN left-thumb 379s (process:1904): libfprint-device-DEBUG: 00:53:48.006: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 379s (process:1904): libfprint-device-DEBUG: 00:53:48.006: Device reported finger status change: FP_FINGER_STATUS_NEEDED 379s (process:1904): libfprint-device-DEBUG: 00:53:48.006: Device reported enroll progress, reported 3 of 5 have been completed 379s (process:1904): libfprint-virtual_device-DEBUG: 00:53:48.006: Sleeping completed 379s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:48.006: Got a new connection! 379s (process:1904): libfprint-virtual_device-DEBUG: 00:53:48.006: Got instructions of length 15 379s (process:1904): libfprint-virtual_device-DEBUG: 00:53:48.006: Received command SCAN left-thumb 379s (process:1904): libfprint-virtual_device-DEBUG: 00:53:48.006: Processing command SCAN left-thumb 379s (process:1904): libfprint-device-DEBUG: 00:53:48.006: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 379s (process:1904): libfprint-device-DEBUG: 00:53:48.006: Device reported finger status change: FP_FINGER_STATUS_NEEDED 379s (process:1904): libfprint-device-DEBUG: 00:53:48.006: Device reported enroll progress, reported 4 of 5 have been completed 379s (process:1904): libfprint-virtual_device-DEBUG: 00:53:48.006: Sleeping completed 379s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:48.006: Got a new connection! 379s (process:1904): libfprint-virtual_device-DEBUG: 00:53:48.006: Got instructions of length 15 379s (process:1904): libfprint-virtual_device-DEBUG: 00:53:48.006: Received command SCAN left-thumb 379s (process:1904): libfprint-virtual_device-DEBUG: 00:53:48.006: Processing command SCAN left-thumb 379s (process:1904): libfprint-device-DEBUG: 00:53:48.006: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 379s (process:1904): libfprint-device-DEBUG: 00:53:48.007: Device reported finger status change: FP_FINGER_STATUS_NEEDED 379s (process:1904): libfprint-device-DEBUG: 00:53:48.007: Device reported enroll progress, reported 5 of 5 have been completed 379s (process:1904): libfprint-device-DEBUG: 00:53:48.007: Device reported enroll completion 379s (process:1904): libfprint-device-DEBUG: 00:53:48.007: Device reported finger status change: FP_FINGER_STATUS_NONE 379s (process:1904): libfprint-device-DEBUG: 00:53:48.007: Print for finger FP_FINGER_LEFT_THUMB enrolled 379s (process:1904): libfprint-device-DEBUG: 00:53:48.007: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 379s (process:1904): libfprint-device-DEBUG: 00:53:48.007: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 379s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:48.007: Got a new connection! 379s (process:1904): libfprint-virtual_device-DEBUG: 00:53:48.007: Got instructions of length 16 379s (process:1904): libfprint-virtual_device-DEBUG: 00:53:48.007: Received command SCAN right-thumb 379s (process:1904): libfprint-device-DEBUG: 00:53:48.007: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 379s (process:1904): libfprint-virtual_device-DEBUG: 00:53:48.007: Processing command SCAN right-thumb 379s (process:1904): libfprint-device-DEBUG: 00:53:48.007: Device reported finger status change: FP_FINGER_STATUS_NEEDED 379s (process:1904): libfprint-device-DEBUG: 00:53:48.007: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 379s (process:1904): libfprint-virtual_device_storage-DEBUG: 00:53:48.007: Trying to identify print 'right-thumb' against a gallery of 2 prints 379s (process:1904): libfprint-device-DEBUG: 00:53:48.007: Device reported identify result 379s (process:1904): libfprint-device-DEBUG: 00:53:48.007: Device reported finger status change: FP_FINGER_STATUS_NEEDED 379s (process:1904): libfprint-device-DEBUG: 00:53:48.007: Device reported identify completion 379s (process:1904): libfprint-device-DEBUG: 00:53:48.007: Device reported finger status change: FP_FINGER_STATUS_NONE 379s (process:1904): libfprint-device-DEBUG: 00:53:48.007: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 379s (process:1904): libfprint-device-DEBUG: 00:53:48.007: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 379s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:48.007: Got a new connection! 379s (process:1904): libfprint-virtual_device-DEBUG: 00:53:48.007: Got instructions of length 15 379s (process:1904): libfprint-virtual_device-DEBUG: 00:53:48.007: Received command SCAN left-thumb 379s (process:1904): libfprint-device-DEBUG: 00:53:48.007: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 379s (process:1904): libfprint-virtual_device-DEBUG: 00:53:48.007: Processing command SCAN left-thumb 379s (process:1904): libfprint-device-DEBUG: 00:53:48.007: Device reported finger status change: FP_FINGER_STATUS_NEEDED 379s (process:1904): libfprint-device-DEBUG: 00:53:48.007: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 379s (process:1904): libfprint-virtual_device_storage-DEBUG: 00:53:48.007: Trying to identify print 'left-thumb' against a gallery of 2 prints 379s (process:1904): libfprint-device-DEBUG: 00:53:48.007: Device reported identify result 379s (process:1904): libfprint-device-DEBUG: 00:53:48.007: Device reported finger status change: FP_FINGER_STATUS_NEEDED 379s (process:1904): libfprint-device-DEBUG: 00:53:48.007: Device reported identify completion 379s (process:1904): libfprint-device-DEBUG: 00:53:48.007: Device reported finger status change: FP_FINGER_STATUS_NONE 379s (process:1904): libfprint-device-DEBUG: 00:53:48.007: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 379s (process:1904): libfprint-device-DEBUG: 00:53:48.007: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 379s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:48.008: Got a new connection! 379s (process:1904): libfprint-virtual_device-DEBUG: 00:53:48.008: Got instructions of length 5 379s (process:1904): libfprint-virtual_device-DEBUG: 00:53:48.008: Received command CONT 379s (process:1904): libfprint-virtual_device-DEBUG: 00:53:48.008: Processing command CONT 379s (process:1904): libfprint-device-DEBUG: 00:53:48.008: Device reported deletion completion 379s (process:1904): libfprint-device-DEBUG: 00:53:48.008: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 379s (process:1904): libfprint-device-DEBUG: 00:53:48.008: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 379s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:48.008: Got a new connection! 379s (process:1904): libfprint-virtual_device-DEBUG: 00:53:48.008: Got instructions of length 16 379s (process:1904): libfprint-virtual_device-DEBUG: 00:53:48.008: Received command SET_KEEP_ALIVE 0 379s (process:1904): libfprint-virtual_device-DEBUG: 00:53:48.008: Keep alive toggled: 0 379s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:48.008: Got a new connection! 379s (process:1904): libfprint-virtual_device-DEBUG: 00:53:48.008: Got instructions of length 19 379s (process:1904): libfprint-virtual_device-DEBUG: 00:53:48.008: Received command SET_ENROLL_STAGES 5 379s (process:1904): libfprint-device-DEBUG: 00:53:48.008: Device reported close completion 379s (process:1904): libfprint-device-DEBUG: 00:53:48.008: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 379s (process:1904): libfprint-device-DEBUG: 00:53:48.008: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 379s Enroll done 379s Enroll done 379s ok 379s test_identify_missing_print (__main__.VirtualDeviceStorage.test_identify_missing_print) ... (process:1904): libfprint-virtual_device-DEBUG: 00:53:48.008: 7399796069875: ../libfprint/drivers/virtual-device.c:387 379s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:48.008: 7399796069889: ../libfprint/drivers/virtual-device-listener.c:153 379s (process:1904): libfprint-device-DEBUG: 00:53:48.009: Device reported open completion 379s (process:1904): libfprint-device-DEBUG: 00:53:48.009: Completing action FPI_DEVICE_ACTION_OPEN in idle! 379s (process:1904): libfprint-device-DEBUG: 00:53:48.009: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 379s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:48.009: Got a new connection! 379s (process:1904): libfprint-virtual_device-DEBUG: 00:53:48.009: Got instructions of length 23 379s (process:1904): libfprint-virtual_device-DEBUG: 00:53:48.009: Received command SCAN not-existing-print 379s (process:1904): libfprint-device-DEBUG: 00:53:48.009: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 379s (process:1904): libfprint-virtual_device-DEBUG: 00:53:48.009: Processing command SCAN not-existing-print 379s (process:1904): libfprint-device-DEBUG: 00:53:48.009: Device reported finger status change: FP_FINGER_STATUS_NEEDED 379s (process:1904): libfprint-device-DEBUG: 00:53:48.009: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 379s (process:1904): libfprint-virtual_device_storage-DEBUG: 00:53:48.009: Trying to identify print 'not-existing-print' against a gallery of 1 prints 379s (process:1904): libfprint-device-DEBUG: 00:53:48.009: Device reported identify result 379s (process:1904): libfprint-device-DEBUG: 00:53:48.009: Device reported finger status change: FP_FINGER_STATUS_NEEDED 379s (process:1904): libfprint-device-DEBUG: 00:53:48.009: Device reported identify completion 379s (process:1904): libfprint-device-DEBUG: 00:53:48.009: Device reported finger status change: FP_FINGER_STATUS_NONE 379s (process:1904): libfprint-device-DEBUG: 00:53:48.009: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 379s (process:1904): libfprint-device-DEBUG: 00:53:48.009: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 379s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:48.009: Got a new connection! 379s (process:1904): libfprint-virtual_device-DEBUG: 00:53:48.009: Got instructions of length 5 379s (process:1904): libfprint-virtual_device-DEBUG: 00:53:48.009: Received command CONT 379s (process:1904): libfprint-virtual_device-DEBUG: 00:53:48.009: Processing command CONT 379s (process:1904): libfprint-device-DEBUG: 00:53:48.009: Device reported deletion completion 379s (process:1904): libfprint-device-DEBUG: 00:53:48.009: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 379s (process:1904): libfprint-device-DEBUG: 00:53:48.009: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 379s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:48.009: Got a new connection! 379s (process:1904): libfprint-virtual_device-DEBUG: 00:53:48.010: Got instructions of length 16 379s (process:1904): libfprint-virtual_device-DEBUG: 00:53:48.010: Received command SET_KEEP_ALIVE 0 379s (process:1904): libfprint-virtual_device-DEBUG: 00:53:48.010: Keep alive toggled: 0 379s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:48.010: Got a new connection! 379s (process:1904): libfprint-virtual_device-DEBUG: 00:53:48.010: Got instructions of length 19 379s (process:1904): libfprint-virtual_device-DEBUG: 00:53:48.010: Received command SET_ENROLL_STAGES 5 379s (process:1904): libfprint-device-DEBUG: 00:53:48.010: Device reported close completion 379s (process:1904): libfprint-device-DEBUG: 00:53:48.010: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 379s (process:1904): libfprint-device-DEBUG: 00:53:48.010: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 379s ok 379s test_identify_no_match (__main__.VirtualDeviceStorage.test_identify_no_match) ... (process:1904): libfprint-virtual_device-DEBUG: 00:53:48.010: 7399796071352: ../libfprint/drivers/virtual-device.c:387 379s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:48.010: 7399796071365: ../libfprint/drivers/virtual-device-listener.c:153 379s (process:1904): libfprint-device-DEBUG: 00:53:48.010: Device reported open completion 379s (process:1904): libfprint-device-DEBUG: 00:53:48.010: Completing action FPI_DEVICE_ACTION_OPEN in idle! 379s (process:1904): libfprint-device-DEBUG: 00:53:48.010: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 379s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:48.010: Got a new connection! 379s (process:1904): libfprint-virtual_device-DEBUG: 00:53:48.010: Got instructions of length 16 379s (process:1904): libfprint-virtual_device-DEBUG: 00:53:48.010: Received command SCAN right-thumb 379s (process:1904): libfprint-device-DEBUG: 00:53:48.011: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 379s (process:1904): libfprint-virtual_device-DEBUG: 00:53:48.011: Processing command SCAN right-thumb 379s (process:1904): libfprint-device-DEBUG: 00:53:48.011: Device reported finger status change: FP_FINGER_STATUS_NEEDED 379s (process:1904): libfprint-device-DEBUG: 00:53:48.011: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 379s (process:1904): libfprint-device-DEBUG: 00:53:48.011: Device reported finger status change: FP_FINGER_STATUS_NEEDED 379s (process:1904): libfprint-device-DEBUG: 00:53:48.011: Device reported enroll progress, reported 1 of 5 have been completed 379s (process:1904): libfprint-virtual_device-DEBUG: 00:53:48.011: Sleeping completed 379s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:48.011: Got a new connection! 379s (process:1904): libfprint-virtual_device-DEBUG: 00:53:48.011: Got instructions of length 16 379s (process:1904): libfprint-virtual_device-DEBUG: 00:53:48.011: Received command SCAN right-thumb 379s (process:1904): libfprint-virtual_device-DEBUG: 00:53:48.011: Processing command SCAN right-thumb 379s (process:1904): libfprint-device-DEBUG: 00:53:48.011: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 379s (process:1904): libfprint-device-DEBUG: 00:53:48.011: Device reported finger status change: FP_FINGER_STATUS_NEEDED 379s (process:1904): libfprint-device-DEBUG: 00:53:48.011: Device reported enroll progress, reported 2 of 5 have been completed 379s (process:1904): libfprint-virtual_device-DEBUG: 00:53:48.011: Sleeping completed 379s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:48.011: Got a new connection! 379s (process:1904): libfprint-virtual_device-DEBUG: 00:53:48.011: Got instructions of length 16 379s (process:1904): libfprint-virtual_device-DEBUG: 00:53:48.011: Received command SCAN right-thumb 379s (process:1904): libfprint-virtual_device-DEBUG: 00:53:48.011: Processing command SCAN right-thumb 379s (process:1904): libfprint-device-DEBUG: 00:53:48.011: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 379s (process:1904): libfprint-device-DEBUG: 00:53:48.011: Device reported finger status change: FP_FINGER_STATUS_NEEDED 379s (process:1904): libfprint-device-DEBUG: 00:53:48.011: Device reported enroll progress, reported 3 of 5 have been completed 379s (process:1904): libfprint-virtual_device-DEBUG: 00:53:48.011: Sleeping completed 379s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:48.011: Got a new connection! 379s (process:1904): libfprint-virtual_device-DEBUG: 00:53:48.012: Got instructions of length 16 379s (process:1904): libfprint-virtual_device-DEBUG: 00:53:48.012: Received command SCAN right-thumb 379s (process:1904): libfprint-virtual_device-DEBUG: 00:53:48.012: Processing command SCAN right-thumb 379s (process:1904): libfprint-device-DEBUG: 00:53:48.012: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 379s (process:1904): libfprint-device-DEBUG: 00:53:48.012: Device reported finger status change: FP_FINGER_STATUS_NEEDED 379s (process:1904): libfprint-device-DEBUG: 00:53:48.012: Device reported enroll progress, reported 4 of 5 have been completed 379s (process:1904): libfprint-virtual_device-DEBUG: 00:53:48.012: Sleeping completed 379s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:48.012: Got a new connection! 379s (process:1904): libfprint-virtual_device-DEBUG: 00:53:48.012: Got instructions of length 16 379s (process:1904): libfprint-virtual_device-DEBUG: 00:53:48.012: Received command SCAN right-thumb 379s (process:1904): libfprint-virtual_device-DEBUG: 00:53:48.012: Processing command SCAN right-thumb 379s (process:1904): libfprint-device-DEBUG: 00:53:48.012: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 379s (process:1904): libfprint-device-DEBUG: 00:53:48.012: Device reported finger status change: FP_FINGER_STATUS_NEEDED 379s (process:1904): libfprint-device-DEBUG: 00:53:48.012: Device reported enroll progress, reported 5 of 5 have been completed 379s (process:1904): libfprint-device-DEBUG: 00:53:48.012: Device reported enroll completion 379s (process:1904): libfprint-device-DEBUG: 00:53:48.012: Device reported finger status change: FP_FINGER_STATUS_NONE 379s (process:1904): libfprint-device-DEBUG: 00:53:48.012: Print for finger FP_FINGER_RIGHT_THUMB enrolled 379s (process:1904): libfprint-device-DEBUG: 00:53:48.012: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 379s (process:1904): libfprint-device-DEBUG: 00:53:48.012: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 379s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:48.012: Got a new connection! 379s (process:1904): libfprint-virtual_device-DEBUG: 00:53:48.012: Got instructions of length 15 379s (process:1904): libfprint-virtual_device-DEBUG: 00:53:48.012: Received command SCAN left-thumb 379s (process:1904): libfprint-device-DEBUG: 00:53:48.012: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 379s (process:1904): libfprint-virtual_device-DEBUG: 00:53:48.012: Processing command SCAN left-thumb 379s (process:1904): libfprint-device-DEBUG: 00:53:48.012: Device reported finger status change: FP_FINGER_STATUS_NEEDED 379s (process:1904): libfprint-device-DEBUG: 00:53:48.012: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 379s (process:1904): libfprint-device-DEBUG: 00:53:48.012: Device reported finger status change: FP_FINGER_STATUS_NEEDED 379s (process:1904): libfprint-device-DEBUG: 00:53:48.012: Device reported enroll progress, reported 1 of 5 have been completed 379s (process:1904): libfprint-virtual_device-DEBUG: 00:53:48.012: Sleeping completed 379s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:48.013: Got a new connection! 379s (process:1904): libfprint-virtual_device-DEBUG: 00:53:48.013: Got instructions of length 15 379s (process:1904): libfprint-virtual_device-DEBUG: 00:53:48.013: Received command SCAN left-thumb 379s (process:1904): libfprint-virtual_device-DEBUG: 00:53:48.013: Processing command SCAN left-thumb 379s (process:1904): libfprint-device-DEBUG: 00:53:48.013: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 379s (process:1904): libfprint-device-DEBUG: 00:53:48.013: Device reported finger status change: FP_FINGER_STATUS_NEEDED 379s (process:1904): libfprint-device-DEBUG: 00:53:48.013: Device reported enroll progress, reported 2 of 5 have been completed 379s (process:1904): libfprint-virtual_device-DEBUG: 00:53:48.013: Sleeping completed 379s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:48.013: Got a new connection! 379s (process:1904): libfprint-virtual_device-DEBUG: 00:53:48.013: Got instructions of length 15 379s (process:1904): libfprint-virtual_device-DEBUG: 00:53:48.013: Received command SCAN left-thumb 379s (process:1904): libfprint-virtual_device-DEBUG: 00:53:48.013: Processing command SCAN left-thumb 379s (process:1904): libfprint-device-DEBUG: 00:53:48.013: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 379s (process:1904): libfprint-device-DEBUG: 00:53:48.013: Device reported finger status change: FP_FINGER_STATUS_NEEDED 379s (process:1904): libfprint-device-DEBUG: 00:53:48.013: Device reported enroll progress, reported 3 of 5 have been completed 379s (process:1904): libfprint-virtual_device-DEBUG: 00:53:48.013: Sleeping completed 379s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:48.013: Got a new connection! 379s (process:1904): libfprint-virtual_device-DEBUG: 00:53:48.013: Got instructions of length 15 379s (process:1904): libfprint-virtual_device-DEBUG: 00:53:48.014: Received command SCAN left-thumb 379s (process:1904): libfprint-virtual_device-DEBUG: 00:53:48.014: Processing command SCAN left-thumb 379s (process:1904): libfprint-device-DEBUG: 00:53:48.014: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 379s (process:1904): libfprint-device-DEBUG: 00:53:48.014: Device reported finger status change: FP_FINGER_STATUS_NEEDED 379s (process:1904): libfprint-device-DEBUG: 00:53:48.014: Device reported enroll progress, reported 4 of 5 have been completed 379s (process:1904): libfprint-virtual_device-DEBUG: 00:53:48.014: Sleeping completed 379s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:48.014: Got a new connection! 379s (process:1904): libfprint-virtual_device-DEBUG: 00:53:48.014: Got instructions of length 15 379s (process:1904): libfprint-virtual_device-DEBUG: 00:53:48.014: Received command SCAN left-thumb 379s (process:1904): libfprint-virtual_device-DEBUG: 00:53:48.014: Processing command SCAN left-thumb 379s (process:1904): libfprint-device-DEBUG: 00:53:48.014: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 379s (process:1904): libfprint-device-DEBUG: 00:53:48.014: Device reported finger status change: FP_FINGER_STATUS_NEEDED 379s (process:1904): libfprint-device-DEBUG: 00:53:48.014: Device reported enroll progress, reported 5 of 5 have been completed 379s (process:1904): libfprint-device-DEBUG: 00:53:48.014: Device reported enroll completion 379s (process:1904): libfprint-device-DEBUG: 00:53:48.014: Device reported finger status change: FP_FINGER_STATUS_NONE 379s (process:1904): libfprint-device-DEBUG: 00:53:48.014: Print for finger FP_FINGER_LEFT_THUMB enrolled 379s (process:1904): libfprint-device-DEBUG: 00:53:48.014: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 379s (process:1904): libfprint-device-DEBUG: 00:53:48.014: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 379s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:48.014: Got a new connection! 379s (process:1904): libfprint-virtual_device-DEBUG: 00:53:48.014: Got instructions of length 16 379s (process:1904): libfprint-virtual_device-DEBUG: 00:53:48.014: Received command SCAN right-thumb 379s (process:1904): libfprint-device-DEBUG: 00:53:48.014: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 379s (process:1904): libfprint-virtual_device-DEBUG: 00:53:48.014: Processing command SCAN right-thumb 379s (process:1904): libfprint-device-DEBUG: 00:53:48.014: Device reported finger status change: FP_FINGER_STATUS_NEEDED 379s (process:1904): libfprint-device-DEBUG: 00:53:48.014: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 379s (process:1904): libfprint-virtual_device_storage-DEBUG: 00:53:48.014: Trying to identify print 'right-thumb' against a gallery of 1 prints 379s (process:1904): libfprint-device-DEBUG: 00:53:48.014: Device reported identify result 379s (process:1904): libfprint-device-DEBUG: 00:53:48.014: Device reported finger status change: FP_FINGER_STATUS_NEEDED 379s (process:1904): libfprint-device-DEBUG: 00:53:48.014: Device reported identify completion 379s (process:1904): libfprint-device-DEBUG: 00:53:48.014: Device reported finger status change: FP_FINGER_STATUS_NONE 379s (process:1904): libfprint-device-DEBUG: 00:53:48.014: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 379s (process:1904): libfprint-device-DEBUG: 00:53:48.014: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 379s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:48.015: Got a new connection! 379s (process:1904): libfprint-virtual_device-DEBUG: 00:53:48.015: Got instructions of length 15 379s (process:1904): libfprint-virtual_device-DEBUG: 00:53:48.015: Received command SCAN left-thumb 379s (process:1904): libfprint-device-DEBUG: 00:53:48.015: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 379s (process:1904): libfprint-virtual_device-DEBUG: 00:53:48.015: Processing command SCAN left-thumb 379s (process:1904): libfprint-device-DEBUG: 00:53:48.015: Device reported finger status change: FP_FINGER_STATUS_NEEDED 379s (process:1904): libfprint-device-DEBUG: 00:53:48.015: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 379s (process:1904): libfprint-virtual_device_storage-DEBUG: 00:53:48.015: Trying to identify print 'left-thumb' against a gallery of 1 prints 379s (process:1904): libfprint-device-DEBUG: 00:53:48.015: Device reported identify result 379s (process:1904): libfprint-device-DEBUG: 00:53:48.015: Device reported finger status change: FP_FINGER_STATUS_NEEDED 379s (process:1904): libfprint-device-DEBUG: 00:53:48.015: Device reported identify completion 379s (process:1904): libfprint-device-DEBUG: 00:53:48.015: Device reported finger status change: FP_FINGER_STATUS_NONE 379s (process:1904): libfprint-device-DEBUG: 00:53:48.015: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 379s (process:1904): libfprint-device-DEBUG: 00:53:48.015: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 379s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:48.015: Got a new connection! 379s (process:1904): libfprint-virtual_device-DEBUG: 00:53:48.015: Got instructions of length 5 379s (process:1904): libfprint-virtual_device-DEBUG: 00:53:48.015: Received command CONT 379s (process:1904): libfprint-virtual_device-DEBUG: 00:53:48.015: Processing command CONT 379s (process:1904): libfprint-device-DEBUG: 00:53:48.015: Device reported deletion completion 379s (process:1904): libfprint-device-DEBUG: 00:53:48.015: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 379s (process:1904): libfprint-device-DEBUG: 00:53:48.015: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 379s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:48.015: Got a new connection! 379s (process:1904): libfprint-virtual_device-DEBUG: 00:53:48.015: Got instructions of length 16 379s (process:1904): libfprint-virtual_device-DEBUG: 00:53:48.015: Received command SET_KEEP_ALIVE 0 379s (process:1904): libfprint-virtual_device-DEBUG: 00:53:48.015: Keep alive toggled: 0 379s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:48.016: Got a new connection! 379s (process:1904): libfprint-virtual_device-DEBUG: 00:53:48.016: Got instructions of length 19 379s (process:1904): libfprint-virtual_device-DEBUG: 00:53:48.016: Received command SET_ENROLL_STAGES 5 379s (process:1904): libfprint-device-DEBUG: 00:53:48.016: Device reported close completion 379s (process:1904): libfprint-device-DEBUG: 00:53:48.016: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 379s (process:1904): libfprint-device-DEBUG: 00:53:48.016: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 379s Enroll done 379s Enroll done 379s ok 379s test_identify_retry (__main__.VirtualDeviceStorage.test_identify_retry) ... (process:1904): libfprint-virtual_device-DEBUG: 00:53:48.016: 7399796077491: ../libfprint/drivers/virtual-device.c:387 379s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:48.016: 7399796077510: ../libfprint/drivers/virtual-device-listener.c:153 379s (process:1904): libfprint-device-DEBUG: 00:53:48.016: Device reported open completion 379s (process:1904): libfprint-device-DEBUG: 00:53:48.016: Completing action FPI_DEVICE_ACTION_OPEN in idle! 379s (process:1904): libfprint-device-DEBUG: 00:53:48.016: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 379s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:48.017: Got a new connection! 379s (process:1904): libfprint-virtual_device-DEBUG: 00:53:48.017: Got instructions of length 7 379s (process:1904): libfprint-virtual_device-DEBUG: 00:53:48.017: Received command RETRY 1 379s (process:1904): libfprint-device-DEBUG: 00:53:48.017: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 379s (process:1904): libfprint-virtual_device-DEBUG: 00:53:48.017: Processing command RETRY 1 379s (process:1904): libfprint-device-DEBUG: 00:53:48.017: Device reported finger status change: FP_FINGER_STATUS_NEEDED 379s (process:1904): libfprint-device-DEBUG: 00:53:48.017: Device reported identify result 379s (process:1904): libfprint-device-DEBUG: 00:53:48.017: Device reported identify completion 379s (process:1904): libfprint-device-DEBUG: 00:53:48.017: Device reported finger status change: FP_FINGER_STATUS_NONE 379s (process:1904): libfprint-device-DEBUG: 00:53:48.017: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 379s (process:1904): libfprint-device-DEBUG: 00:53:48.017: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 379s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:48.017: Got a new connection! 379s (process:1904): libfprint-virtual_device-DEBUG: 00:53:48.017: Got instructions of length 5 379s (process:1904): libfprint-virtual_device-DEBUG: 00:53:48.017: Received command CONT 379s (process:1904): libfprint-virtual_device-DEBUG: 00:53:48.017: Processing command CONT 379s (process:1904): libfprint-device-DEBUG: 00:53:48.017: Device reported deletion completion 379s (process:1904): libfprint-device-DEBUG: 00:53:48.017: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 379s (process:1904): libfprint-device-DEBUG: 00:53:48.017: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 379s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:48.017: Got a new connection! 379s (process:1904): libfprint-virtual_device-DEBUG: 00:53:48.018: Got instructions of length 16 379s (process:1904): libfprint-virtual_device-DEBUG: 00:53:48.018: Received command SET_KEEP_ALIVE 0 379s (process:1904): libfprint-virtual_device-DEBUG: 00:53:48.018: Keep alive toggled: 0 379s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:48.018: Got a new connection! 379s (process:1904): libfprint-virtual_device-DEBUG: 00:53:48.018: Got instructions of length 19 379s (process:1904): libfprint-virtual_device-DEBUG: 00:53:48.018: Received command SET_ENROLL_STAGES 5 379s (process:1904): libfprint-device-DEBUG: 00:53:48.018: Device reported close completion 379s (process:1904): libfprint-device-DEBUG: 00:53:48.018: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 379s (process:1904): libfprint-device-DEBUG: 00:53:48.018: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 379s ok 379s test_identify_unsupported (__main__.VirtualDeviceStorage.test_identify_unsupported) ... (process:1904): libfprint-virtual_device-DEBUG: 00:53:48.018: 7399796079443: ../libfprint/drivers/virtual-device.c:387 379s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:48.018: 7399796079457: ../libfprint/drivers/virtual-device-listener.c:153 379s (process:1904): libfprint-device-DEBUG: 00:53:48.018: Device reported open completion 379s (process:1904): libfprint-device-DEBUG: 00:53:48.018: Completing action FPI_DEVICE_ACTION_OPEN in idle! 379s (process:1904): libfprint-device-DEBUG: 00:53:48.018: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 379s skipped 'Device supports identification' 379s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:48.018: Got a new connection! 379s (process:1904): libfprint-virtual_device-DEBUG: 00:53:48.019: Got instructions of length 5 379s (process:1904): libfprint-virtual_device-DEBUG: 00:53:48.019: Received command CONT 379s (process:1904): libfprint-virtual_device-DEBUG: 00:53:48.019: Processing command CONT 379s (process:1904): libfprint-device-DEBUG: 00:53:48.019: Device reported deletion completion 379s (process:1904): libfprint-device-DEBUG: 00:53:48.019: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 379s (process:1904): libfprint-device-DEBUG: 00:53:48.019: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 379s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:48.019: Got a new connection! 379s (process:1904): libfprint-virtual_device-DEBUG: 00:53:48.019: Got instructions of length 16 379s (process:1904): libfprint-virtual_device-DEBUG: 00:53:48.019: Received command SET_KEEP_ALIVE 0 379s (process:1904): libfprint-virtual_device-DEBUG: 00:53:48.019: Keep alive toggled: 0 379s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:48.019: Got a new connection! 379s (process:1904): libfprint-virtual_device-DEBUG: 00:53:48.019: Got instructions of length 19 379s (process:1904): libfprint-virtual_device-DEBUG: 00:53:48.019: Received command SET_ENROLL_STAGES 5 379s (process:1904): libfprint-device-DEBUG: 00:53:48.019: Device reported close completion 379s (process:1904): libfprint-device-DEBUG: 00:53:48.019: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 379s (process:1904): libfprint-device-DEBUG: 00:53:48.019: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 379s test_list_delete (__main__.VirtualDeviceStorage.test_list_delete) ... (process:1904): libfprint-virtual_device-DEBUG: 00:53:48.019: 7399796080706: ../libfprint/drivers/virtual-device.c:387 379s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:48.019: 7399796080721: ../libfprint/drivers/virtual-device-listener.c:153 379s (process:1904): libfprint-device-DEBUG: 00:53:48.019: Device reported open completion 379s (process:1904): libfprint-device-DEBUG: 00:53:48.019: Completing action FPI_DEVICE_ACTION_OPEN in idle! 379s (process:1904): libfprint-device-DEBUG: 00:53:48.019: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 379s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:48.020: Got a new connection! 379s (process:1904): libfprint-virtual_device-DEBUG: 00:53:48.020: Got instructions of length 14 379s (process:1904): libfprint-virtual_device-DEBUG: 00:53:48.020: Received command SCAN testprint 379s (process:1904): libfprint-device-DEBUG: 00:53:48.020: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 379s (process:1904): libfprint-virtual_device-DEBUG: 00:53:48.020: Processing command SCAN testprint 379s (process:1904): libfprint-device-DEBUG: 00:53:48.020: Device reported finger status change: FP_FINGER_STATUS_NEEDED 379s (process:1904): libfprint-device-DEBUG: 00:53:48.020: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 379s (process:1904): libfprint-device-DEBUG: 00:53:48.020: Device reported finger status change: FP_FINGER_STATUS_NEEDED 379s (process:1904): libfprint-device-DEBUG: 00:53:48.020: Device reported enroll progress, reported 1 of 5 have been completed 379s (process:1904): libfprint-virtual_device-DEBUG: 00:53:48.020: Sleeping completed 379s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:48.020: Got a new connection! 379s (process:1904): libfprint-virtual_device-DEBUG: 00:53:48.020: Got instructions of length 14 379s (process:1904): libfprint-virtual_device-DEBUG: 00:53:48.020: Received command SCAN testprint 379s (process:1904): libfprint-virtual_device-DEBUG: 00:53:48.020: Processing command SCAN testprint 379s (process:1904): libfprint-device-DEBUG: 00:53:48.020: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 379s (process:1904): libfprint-device-DEBUG: 00:53:48.020: Device reported finger status change: FP_FINGER_STATUS_NEEDED 379s (process:1904): libfprint-device-DEBUG: 00:53:48.020: Device reported enroll progress, reported 2 of 5 have been completed 379s (process:1904): libfprint-virtual_device-DEBUG: 00:53:48.020: Sleeping completed 379s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:48.020: Got a new connection! 379s (process:1904): libfprint-virtual_device-DEBUG: 00:53:48.020: Got instructions of length 14 379s (process:1904): libfprint-virtual_device-DEBUG: 00:53:48.020: Received command SCAN testprint 379s (process:1904): libfprint-virtual_device-DEBUG: 00:53:48.020: Processing command SCAN testprint 379s (process:1904): libfprint-device-DEBUG: 00:53:48.020: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 379s (process:1904): libfprint-device-DEBUG: 00:53:48.020: Device reported finger status change: FP_FINGER_STATUS_NEEDED 379s (process:1904): libfprint-device-DEBUG: 00:53:48.020: Device reported enroll progress, reported 3 of 5 have been completed 379s (process:1904): libfprint-virtual_device-DEBUG: 00:53:48.020: Sleeping completed 379s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:48.021: Got a new connection! 379s (process:1904): libfprint-virtual_device-DEBUG: 00:53:48.021: Got instructions of length 14 379s (process:1904): libfprint-virtual_device-DEBUG: 00:53:48.021: Received command SCAN testprint 379s (process:1904): libfprint-virtual_device-DEBUG: 00:53:48.021: Processing command SCAN testprint 379s (process:1904): libfprint-device-DEBUG: 00:53:48.021: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 379s (process:1904): libfprint-device-DEBUG: 00:53:48.021: Device reported finger status change: FP_FINGER_STATUS_NEEDED 379s (process:1904): libfprint-device-DEBUG: 00:53:48.021: Device reported enroll progress, reported 4 of 5 have been completed 379s (process:1904): libfprint-virtual_device-DEBUG: 00:53:48.021: Sleeping completed 379s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:48.021: Got a new connection! 379s (process:1904): libfprint-virtual_device-DEBUG: 00:53:48.021: Got instructions of length 14 379s (process:1904): libfprint-virtual_device-DEBUG: 00:53:48.021: Received command SCAN testprint 379s (process:1904): libfprint-virtual_device-DEBUG: 00:53:48.021: Processing command SCAN testprint 379s (process:1904): libfprint-device-DEBUG: 00:53:48.021: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 379s (process:1904): libfprint-device-DEBUG: 00:53:48.021: Device reported finger status change: FP_FINGER_STATUS_NEEDED 379s (process:1904): libfprint-device-DEBUG: 00:53:48.021: Device reported enroll progress, reported 5 of 5 have been completed 379s (process:1904): libfprint-device-DEBUG: 00:53:48.021: Device reported enroll completion 379s (process:1904): libfprint-device-DEBUG: 00:53:48.021: Device reported finger status change: FP_FINGER_STATUS_NONE 379s (process:1904): libfprint-device-DEBUG: 00:53:48.021: Print for finger FP_FINGER_RIGHT_THUMB enrolled 379s (process:1904): libfprint-device-DEBUG: 00:53:48.021: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 379s (process:1904): libfprint-device-DEBUG: 00:53:48.021: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 379s (process:1904): libfprint-device-DEBUG: 00:53:48.522: Device reported listing completion 379s (process:1904): libfprint-device-DEBUG: 00:53:48.522: Completing action FPI_DEVICE_ACTION_LIST in idle! 379s (process:1904): libfprint-device-DEBUG: 00:53:48.522: Updated temperature model after 0.50 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 380s (process:1904): libfprint-virtual_device_storage-DEBUG: 00:53:49.023: Deleting print testprint for user testuser 380s (process:1904): libfprint-device-DEBUG: 00:53:49.023: Device reported deletion completion 380s (process:1904): libfprint-device-DEBUG: 00:53:49.023: Completing action FPI_DEVICE_ACTION_DELETE in idle! 380s (process:1904): libfprint-device-DEBUG: 00:53:49.023: Updated temperature model after 0.50 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 380s (process:1904): libfprint-device-DEBUG: 00:53:49.524: Device reported listing completion 380s (process:1904): libfprint-device-DEBUG: 00:53:49.524: Completing action FPI_DEVICE_ACTION_LIST in idle! 380s (process:1904): libfprint-device-DEBUG: 00:53:49.524: Updated temperature model after 0.50 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 380s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:49.524: Got a new connection! 380s (process:1904): libfprint-virtual_device-DEBUG: 00:53:49.524: Got instructions of length 5 380s (process:1904): libfprint-virtual_device-DEBUG: 00:53:49.524: Received command CONT 380s (process:1904): libfprint-virtual_device-DEBUG: 00:53:49.524: Processing command CONT 380s (process:1904): libfprint-device-DEBUG: 00:53:49.524: Device reported deletion completion 380s (process:1904): libfprint-device-DEBUG: 00:53:49.524: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 380s (process:1904): libfprint-device-DEBUG: 00:53:49.524: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 380s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:49.524: Got a new connection! 380s (process:1904): libfprint-virtual_device-DEBUG: 00:53:49.524: Got instructions of length 16 380s (process:1904): libfprint-virtual_device-DEBUG: 00:53:49.524: Received command SET_KEEP_ALIVE 0 380s (process:1904): libfprint-virtual_device-DEBUG: 00:53:49.525: Keep alive toggled: 0 380s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:49.525: Got a new connection! 380s (process:1904): libfprint-virtual_device-DEBUG: 00:53:49.525: Got instructions of length 19 380s (process:1904): libfprint-virtual_device-DEBUG: 00:53:49.525: Received command SET_ENROLL_STAGES 5 380s (process:1904): libfprint-device-DEBUG: 00:53:49.525: Device reported close completion 380s (process:1904): libfprint-device-DEBUG: 00:53:49.525: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 380s (process:1904): libfprint-device-DEBUG: 00:53:49.525: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 380s Enroll done 380s 380s blub 'testprint' 380s ok 380s test_list_delete_missing (__main__.VirtualDeviceStorage.test_list_delete_missing) ... (process:1904): libfprint-virtual_device-DEBUG: 00:53:49.525: 7399797586444: ../libfprint/drivers/virtual-device.c:387 380s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:49.525: 7399797586460: ../libfprint/drivers/virtual-device-listener.c:153 380s (process:1904): libfprint-device-DEBUG: 00:53:49.525: Device reported open completion 380s (process:1904): libfprint-device-DEBUG: 00:53:49.525: Completing action FPI_DEVICE_ACTION_OPEN in idle! 380s (process:1904): libfprint-device-DEBUG: 00:53:49.525: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 380s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:49.526: Got a new connection! 380s (process:1904): libfprint-virtual_device-DEBUG: 00:53:49.526: Got instructions of length 14 380s (process:1904): libfprint-virtual_device-DEBUG: 00:53:49.526: Received command SCAN testprint 380s (process:1904): libfprint-device-DEBUG: 00:53:49.526: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 380s (process:1904): libfprint-virtual_device-DEBUG: 00:53:49.526: Processing command SCAN testprint 380s (process:1904): libfprint-device-DEBUG: 00:53:49.526: Device reported finger status change: FP_FINGER_STATUS_NEEDED 380s (process:1904): libfprint-device-DEBUG: 00:53:49.526: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 380s (process:1904): libfprint-device-DEBUG: 00:53:49.526: Device reported finger status change: FP_FINGER_STATUS_NEEDED 380s (process:1904): libfprint-device-DEBUG: 00:53:49.526: Device reported enroll progress, reported 1 of 5 have been completed 380s (process:1904): libfprint-virtual_device-DEBUG: 00:53:49.526: Sleeping completed 380s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:49.526: Got a new connection! 380s (process:1904): libfprint-virtual_device-DEBUG: 00:53:49.527: Got instructions of length 14 380s (process:1904): libfprint-virtual_device-DEBUG: 00:53:49.527: Received command SCAN testprint 380s (process:1904): libfprint-virtual_device-DEBUG: 00:53:49.527: Processing command SCAN testprint 380s (process:1904): libfprint-device-DEBUG: 00:53:49.527: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 380s (process:1904): libfprint-device-DEBUG: 00:53:49.527: Device reported finger status change: FP_FINGER_STATUS_NEEDED 380s (process:1904): libfprint-device-DEBUG: 00:53:49.527: Device reported enroll progress, reported 2 of 5 have been completed 380s (process:1904): libfprint-virtual_device-DEBUG: 00:53:49.527: Sleeping completed 380s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:49.527: Got a new connection! 380s (process:1904): libfprint-virtual_device-DEBUG: 00:53:49.527: Got instructions of length 14 380s (process:1904): libfprint-virtual_device-DEBUG: 00:53:49.527: Received command SCAN testprint 380s (process:1904): libfprint-virtual_device-DEBUG: 00:53:49.527: Processing command SCAN testprint 380s (process:1904): libfprint-device-DEBUG: 00:53:49.527: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 380s (process:1904): libfprint-device-DEBUG: 00:53:49.527: Device reported finger status change: FP_FINGER_STATUS_NEEDED 380s (process:1904): libfprint-device-DEBUG: 00:53:49.527: Device reported enroll progress, reported 3 of 5 have been completed 380s (process:1904): libfprint-virtual_device-DEBUG: 00:53:49.527: Sleeping completed 380s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:49.528: Got a new connection! 380s (process:1904): libfprint-virtual_device-DEBUG: 00:53:49.528: Got instructions of length 14 380s (process:1904): libfprint-virtual_device-DEBUG: 00:53:49.528: Received command SCAN testprint 380s (process:1904): libfprint-virtual_device-DEBUG: 00:53:49.528: Processing command SCAN testprint 380s (process:1904): libfprint-device-DEBUG: 00:53:49.528: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 380s (process:1904): libfprint-device-DEBUG: 00:53:49.528: Device reported finger status change: FP_FINGER_STATUS_NEEDED 380s (process:1904): libfprint-device-DEBUG: 00:53:49.528: Device reported enroll progress, reported 4 of 5 have been completed 380s (process:1904): libfprint-virtual_device-DEBUG: 00:53:49.528: Sleeping completed 380s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:49.528: Got a new connection! 380s (process:1904): libfprint-virtual_device-DEBUG: 00:53:49.528: Got instructions of length 14 380s (process:1904): libfprint-virtual_device-DEBUG: 00:53:49.528: Received command SCAN testprint 380s (process:1904): libfprint-virtual_device-DEBUG: 00:53:49.528: Processing command SCAN testprint 380s (process:1904): libfprint-device-DEBUG: 00:53:49.528: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 380s (process:1904): libfprint-device-DEBUG: 00:53:49.528: Device reported finger status change: FP_FINGER_STATUS_NEEDED 380s (process:1904): libfprint-device-DEBUG: 00:53:49.528: Device reported enroll progress, reported 5 of 5 have been completed 380s (process:1904): libfprint-device-DEBUG: 00:53:49.529: Device reported enroll completion 380s (process:1904): libfprint-device-DEBUG: 00:53:49.529: Device reported finger status change: FP_FINGER_STATUS_NONE 380s (process:1904): libfprint-device-DEBUG: 00:53:49.529: Print for finger FP_FINGER_RIGHT_THUMB enrolled 380s (process:1904): libfprint-device-DEBUG: 00:53:49.529: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 380s (process:1904): libfprint-device-DEBUG: 00:53:49.529: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 380s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:49.529: Got a new connection! 380s (process:1904): libfprint-virtual_device-DEBUG: 00:53:49.530: Got instructions of length 16 380s (process:1904): libfprint-virtual_device-DEBUG: 00:53:49.530: Received command REMOVE testprint 380s (process:1904): libfprint-virtual_device-DEBUG: 00:53:49.530: Processing command REMOVE testprint 381s (process:1904): libfprint-virtual_device_storage-DEBUG: 00:53:50.030: Deleting print testprint for user testuser 381s (process:1904): libfprint-device-DEBUG: 00:53:50.030: Device reported deletion completion 381s (process:1904): libfprint-device-DEBUG: 00:53:50.030: Completing action FPI_DEVICE_ACTION_DELETE in idle! 381s (process:1904): libfprint-device-DEBUG: 00:53:50.030: Updated temperature model after 0.50 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 381s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:50.031: Got a new connection! 381s (process:1904): libfprint-virtual_device-DEBUG: 00:53:50.031: Got instructions of length 5 381s (process:1904): libfprint-virtual_device-DEBUG: 00:53:50.031: Received command CONT 381s (process:1904): libfprint-virtual_device-DEBUG: 00:53:50.031: Processing command CONT 381s (process:1904): libfprint-device-DEBUG: 00:53:50.031: Device reported deletion completion 381s (process:1904): libfprint-device-DEBUG: 00:53:50.031: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 381s (process:1904): libfprint-device-DEBUG: 00:53:50.031: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 381s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:50.031: Got a new connection! 381s (process:1904): libfprint-virtual_device-DEBUG: 00:53:50.031: Got instructions of length 16 381s (process:1904): libfprint-virtual_device-DEBUG: 00:53:50.031: Received command SET_KEEP_ALIVE 0 381s (process:1904): libfprint-virtual_device-DEBUG: 00:53:50.031: Keep alive toggled: 0 381s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:50.031: Got a new connection! 381s (process:1904): libfprint-virtual_device-DEBUG: 00:53:50.031: Got instructions of length 19 381s (process:1904): libfprint-virtual_device-DEBUG: 00:53:50.031: Received command SET_ENROLL_STAGES 5 381s (process:1904): libfprint-device-DEBUG: 00:53:50.031: Device reported close completion 381s (process:1904): libfprint-device-DEBUG: 00:53:50.031: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 381s (process:1904): libfprint-device-DEBUG: 00:53:50.031: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 381s Enroll done 381s ok 381s test_list_empty (__main__.VirtualDeviceStorage.test_list_empty) ... (process:1904): libfprint-virtual_device-DEBUG: 00:53:50.032: 7399798092934: ../libfprint/drivers/virtual-device.c:387 381s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:50.032: 7399798092950: ../libfprint/drivers/virtual-device-listener.c:153 381s (process:1904): libfprint-device-DEBUG: 00:53:50.032: Device reported open completion 381s (process:1904): libfprint-device-DEBUG: 00:53:50.032: Completing action FPI_DEVICE_ACTION_OPEN in idle! 381s (process:1904): libfprint-device-DEBUG: 00:53:50.032: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 381s (process:1904): libfprint-device-DEBUG: 00:53:50.532: Device reported listing completion 381s (process:1904): libfprint-device-DEBUG: 00:53:50.533: Completing action FPI_DEVICE_ACTION_LIST in idle! 381s (process:1904): libfprint-device-DEBUG: 00:53:50.533: Updated temperature model after 0.50 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 381s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:50.534: Got a new connection! 381s (process:1904): libfprint-virtual_device-DEBUG: 00:53:50.534: Got instructions of length 5 381s (process:1904): libfprint-virtual_device-DEBUG: 00:53:50.534: Received command CONT 381s (process:1904): libfprint-virtual_device-DEBUG: 00:53:50.534: Processing command CONT 381s (process:1904): libfprint-device-DEBUG: 00:53:50.534: Device reported deletion completion 381s (process:1904): libfprint-device-DEBUG: 00:53:50.534: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 381s (process:1904): libfprint-device-DEBUG: 00:53:50.534: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 381s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:50.534: Got a new connection! 381s (process:1904): libfprint-virtual_device-DEBUG: 00:53:50.534: Got instructions of length 16 381s (process:1904): libfprint-virtual_device-DEBUG: 00:53:50.534: Received command SET_KEEP_ALIVE 0 381s (process:1904): libfprint-virtual_device-DEBUG: 00:53:50.534: Keep alive toggled: 0 381s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:50.535: Got a new connection! 381s (process:1904): libfprint-virtual_device-DEBUG: 00:53:50.535: Got instructions of length 19 381s (process:1904): libfprint-virtual_device-DEBUG: 00:53:50.535: Received command SET_ENROLL_STAGES 5 381s (process:1904): libfprint-device-DEBUG: 00:53:50.535: Device reported close completion 381s (process:1904): libfprint-device-DEBUG: 00:53:50.535: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 381s (process:1904): libfprint-device-DEBUG: 00:53:50.535: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 381s ok 381s test_list_error (__main__.VirtualDeviceStorage.test_list_error) ... (process:1904): libfprint-virtual_device-DEBUG: 00:53:50.535: 7399798596696: ../libfprint/drivers/virtual-device.c:387 381s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:50.535: 7399798596725: ../libfprint/drivers/virtual-device-listener.c:153 381s (process:1904): libfprint-device-DEBUG: 00:53:50.536: Device reported open completion 381s (process:1904): libfprint-device-DEBUG: 00:53:50.536: Completing action FPI_DEVICE_ACTION_OPEN in idle! 381s (process:1904): libfprint-device-DEBUG: 00:53:50.536: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 381s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:50.537: Got a new connection! 381s (process:1904): libfprint-virtual_device-DEBUG: 00:53:50.537: Got instructions of length 9 381s (process:1904): libfprint-virtual_device-DEBUG: 00:53:50.537: Received command SLEEP 100 381s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:50.538: Got a new connection! 381s (process:1904): libfprint-virtual_device-DEBUG: 00:53:50.538: Got instructions of length 7 381s (process:1904): libfprint-virtual_device-DEBUG: 00:53:50.538: Received command ERROR 4 381s (process:1904): libfprint-virtual_device-DEBUG: 00:53:50.539: Processing command SLEEP 100 381s (process:1904): libfprint-virtual_device-DEBUG: 00:53:50.539: Sleeping 100ms 381s (process:1904): libfprint-virtual_device-DEBUG: 00:53:50.639: Sleeping completed 381s (process:1904): libfprint-virtual_device-DEBUG: 00:53:50.639: Processing command ERROR 4 381s (process:1904): libfprint-device-DEBUG: 00:53:50.639: Device reported listing completion 381s (process:1904): libfprint-device-DEBUG: 00:53:50.639: Completing action FPI_DEVICE_ACTION_LIST in idle! 381s (process:1904): libfprint-device-DEBUG: 00:53:50.640: Updated temperature model after 0.10 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 381s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:50.641: Got a new connection! 381s (process:1904): libfprint-virtual_device-DEBUG: 00:53:50.641: Got instructions of length 5 381s (process:1904): libfprint-virtual_device-DEBUG: 00:53:50.641: Received command CONT 381s (process:1904): libfprint-virtual_device-DEBUG: 00:53:50.641: Processing command CONT 381s (process:1904): libfprint-device-DEBUG: 00:53:50.641: Device reported deletion completion 381s (process:1904): libfprint-device-DEBUG: 00:53:50.641: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 381s (process:1904): libfprint-device-DEBUG: 00:53:50.641: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 381s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:50.642: Got a new connection! 381s (process:1904): libfprint-virtual_device-DEBUG: 00:53:50.642: Got instructions of length 16 381s (process:1904): libfprint-virtual_device-DEBUG: 00:53:50.642: Received command SET_KEEP_ALIVE 0 381s (process:1904): libfprint-virtual_device-DEBUG: 00:53:50.642: Keep alive toggled: 0 381s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:50.642: Got a new connection! 381s (process:1904): libfprint-virtual_device-DEBUG: 00:53:50.642: Got instructions of length 19 381s (process:1904): libfprint-virtual_device-DEBUG: 00:53:50.642: Received command SET_ENROLL_STAGES 5 381s (process:1904): libfprint-device-DEBUG: 00:53:50.642: Device reported close completion 381s (process:1904): libfprint-device-DEBUG: 00:53:50.642: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 381s (process:1904): libfprint-device-DEBUG: 00:53:50.642: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 381s ok 381s test_list_populated (__main__.VirtualDeviceStorage.test_list_populated) ... (process:1904): libfprint-virtual_device-DEBUG: 00:53:50.643: 7399798704421: ../libfprint/drivers/virtual-device.c:387 381s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:50.643: 7399798704487: ../libfprint/drivers/virtual-device-listener.c:153 381s (process:1904): libfprint-device-DEBUG: 00:53:50.644: Device reported open completion 381s (process:1904): libfprint-device-DEBUG: 00:53:50.644: Completing action FPI_DEVICE_ACTION_OPEN in idle! 381s (process:1904): libfprint-device-DEBUG: 00:53:50.644: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 381s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:50.644: Got a new connection! 381s (process:1904): libfprint-virtual_device-DEBUG: 00:53:50.645: Got instructions of length 9 381s (process:1904): libfprint-virtual_device-DEBUG: 00:53:50.645: Received command INSERT p1 381s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:50.645: Got a new connection! 381s (process:1904): libfprint-virtual_device-DEBUG: 00:53:50.646: Got instructions of length 7 381s (process:1904): libfprint-virtual_device-DEBUG: 00:53:50.646: Received command SCAN p2 381s (process:1904): libfprint-device-DEBUG: 00:53:50.646: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 381s (process:1904): libfprint-virtual_device-DEBUG: 00:53:50.646: Processing command INSERT p1 381s (process:1904): libfprint-virtual_device-DEBUG: 00:53:50.646: Processing command SCAN p2 381s (process:1904): libfprint-device-DEBUG: 00:53:50.646: Device reported finger status change: FP_FINGER_STATUS_NEEDED 381s (process:1904): libfprint-device-DEBUG: 00:53:50.646: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 381s (process:1904): libfprint-device-DEBUG: 00:53:50.646: Device reported finger status change: FP_FINGER_STATUS_NEEDED 381s (process:1904): libfprint-device-DEBUG: 00:53:50.646: Device reported enroll progress, reported 1 of 5 have been completed 381s (process:1904): libfprint-virtual_device-DEBUG: 00:53:50.646: Sleeping completed 381s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:50.647: Got a new connection! 381s (process:1904): libfprint-virtual_device-DEBUG: 00:53:50.647: Got instructions of length 7 381s (process:1904): libfprint-virtual_device-DEBUG: 00:53:50.647: Received command SCAN p2 381s (process:1904): libfprint-virtual_device-DEBUG: 00:53:50.647: Processing command SCAN p2 381s (process:1904): libfprint-device-DEBUG: 00:53:50.647: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 381s (process:1904): libfprint-device-DEBUG: 00:53:50.647: Device reported finger status change: FP_FINGER_STATUS_NEEDED 381s (process:1904): libfprint-device-DEBUG: 00:53:50.647: Device reported enroll progress, reported 2 of 5 have been completed 381s (process:1904): libfprint-virtual_device-DEBUG: 00:53:50.647: Sleeping completed 381s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:50.648: Got a new connection! 381s (process:1904): libfprint-virtual_device-DEBUG: 00:53:50.648: Got instructions of length 7 381s (process:1904): libfprint-virtual_device-DEBUG: 00:53:50.648: Received command SCAN p2 381s (process:1904): libfprint-virtual_device-DEBUG: 00:53:50.648: Processing command SCAN p2 381s (process:1904): libfprint-device-DEBUG: 00:53:50.648: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 381s (process:1904): libfprint-device-DEBUG: 00:53:50.648: Device reported finger status change: FP_FINGER_STATUS_NEEDED 381s (process:1904): libfprint-device-DEBUG: 00:53:50.648: Device reported enroll progress, reported 3 of 5 have been completed 381s (process:1904): libfprint-virtual_device-DEBUG: 00:53:50.648: Sleeping completed 381s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:50.649: Got a new connection! 381s (process:1904): libfprint-virtual_device-DEBUG: 00:53:50.649: Got instructions of length 7 381s (process:1904): libfprint-virtual_device-DEBUG: 00:53:50.649: Received command SCAN p2 381s (process:1904): libfprint-virtual_device-DEBUG: 00:53:50.649: Processing command SCAN p2 381s (process:1904): libfprint-device-DEBUG: 00:53:50.649: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 381s (process:1904): libfprint-device-DEBUG: 00:53:50.649: Device reported finger status change: FP_FINGER_STATUS_NEEDED 381s (process:1904): libfprint-device-DEBUG: 00:53:50.649: Device reported enroll progress, reported 4 of 5 have been completed 381s (process:1904): libfprint-virtual_device-DEBUG: 00:53:50.650: Sleeping completed 381s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:50.650: Got a new connection! 381s (process:1904): libfprint-virtual_device-DEBUG: 00:53:50.650: Got instructions of length 7 381s (process:1904): libfprint-virtual_device-DEBUG: 00:53:50.650: Received command SCAN p2 381s (process:1904): libfprint-virtual_device-DEBUG: 00:53:50.650: Processing command SCAN p2 381s (process:1904): libfprint-device-DEBUG: 00:53:50.650: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 381s (process:1904): libfprint-device-DEBUG: 00:53:50.650: Device reported finger status change: FP_FINGER_STATUS_NEEDED 381s (process:1904): libfprint-device-DEBUG: 00:53:50.650: Device reported enroll progress, reported 5 of 5 have been completed 381s (process:1904): libfprint-device-DEBUG: 00:53:50.650: Device reported enroll completion 381s (process:1904): libfprint-device-DEBUG: 00:53:50.650: Device reported finger status change: FP_FINGER_STATUS_NONE 381s (process:1904): libfprint-device-DEBUG: 00:53:50.650: Print for finger FP_FINGER_LEFT_LITTLE enrolled 381s (process:1904): libfprint-device-DEBUG: 00:53:50.650: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 381s (process:1904): libfprint-device-DEBUG: 00:53:50.651: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 382s (process:1904): libfprint-device-DEBUG: 00:53:51.151: Device reported listing completion 382s (process:1904): libfprint-device-DEBUG: 00:53:51.151: Completing action FPI_DEVICE_ACTION_LIST in idle! 382s (process:1904): libfprint-device-DEBUG: 00:53:51.151: Updated temperature model after 0.50 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 382s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:51.152: Got a new connection! 382s (process:1904): libfprint-virtual_device-DEBUG: 00:53:51.152: Got instructions of length 5 382s (process:1904): libfprint-virtual_device-DEBUG: 00:53:51.152: Received command CONT 382s (process:1904): libfprint-virtual_device-DEBUG: 00:53:51.152: Processing command CONT 382s (process:1904): libfprint-device-DEBUG: 00:53:51.152: Device reported deletion completion 382s (process:1904): libfprint-device-DEBUG: 00:53:51.152: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 382s (process:1904): libfprint-device-DEBUG: 00:53:51.152: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 382s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:51.152: Got a new connection! 382s (process:1904): libfprint-virtual_device-DEBUG: 00:53:51.152: Got instructions of length 16 382s (process:1904): libfprint-virtual_device-DEBUG: 00:53:51.152: Received command SET_KEEP_ALIVE 0 382s (process:1904): libfprint-virtual_device-DEBUG: 00:53:51.152: Keep alive toggled: 0 382s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:51.152: Got a new connection! 382s (process:1904): libfprint-virtual_device-DEBUG: 00:53:51.152: Got instructions of length 19 382s (process:1904): libfprint-virtual_device-DEBUG: 00:53:51.152: Received command SET_ENROLL_STAGES 5 382s (process:1904): libfprint-device-DEBUG: 00:53:51.153: Device reported close completion 382s (process:1904): libfprint-device-DEBUG: 00:53:51.153: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 382s (process:1904): libfprint-device-DEBUG: 00:53:51.153: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 382s Enroll done 382s ok 382s test_open_error (__main__.VirtualDeviceStorage.test_open_error) ... (process:1904): libfprint-virtual_device-DEBUG: 00:53:51.153: 7399799214149: ../libfprint/drivers/virtual-device.c:387 382s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:51.153: 7399799214167: ../libfprint/drivers/virtual-device-listener.c:153 382s (process:1904): libfprint-device-DEBUG: 00:53:51.153: Device reported open completion 382s (process:1904): libfprint-device-DEBUG: 00:53:51.153: Completing action FPI_DEVICE_ACTION_OPEN in idle! 382s (process:1904): libfprint-device-DEBUG: 00:53:51.153: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 382s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:51.153: Got a new connection! 382s (process:1904): libfprint-virtual_device-DEBUG: 00:53:51.153: Got instructions of length 16 382s (process:1904): libfprint-virtual_device-DEBUG: 00:53:51.153: Received command IGNORED_COMMAND 382s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:51.153: Got a new connection! 382s (process:1904): libfprint-virtual_device-DEBUG: 00:53:51.153: Got instructions of length 7 382s (process:1904): libfprint-virtual_device-DEBUG: 00:53:51.153: Received command ERROR 5 382s (process:1904): libfprint-virtual_device-DEBUG: 00:53:51.153: Processing command IGNORED_COMMAND 382s (process:1904): libfprint-device-DEBUG: 00:53:51.153: Device reported close completion 382s (process:1904): libfprint-device-DEBUG: 00:53:51.153: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 382s (process:1904): libfprint-device-DEBUG: 00:53:51.153: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 382s (process:1904): libfprint-virtual_device-DEBUG: 00:53:51.154: 7399799215135: ../libfprint/drivers/virtual-device.c:387 382s (process:1904): libfprint-virtual_device-DEBUG: 00:53:51.154: Processing command ERROR 5 382s (process:1904): libfprint-device-DEBUG: 00:53:51.154: Device reported open completion 382s (process:1904): libfprint-device-DEBUG: 00:53:51.154: Completing action FPI_DEVICE_ACTION_OPEN in idle! 382s (process:1904): libfprint-device-DEBUG: 00:53:51.154: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 382s ok 382s test_open_error_with_keep_alive (__main__.VirtualDeviceStorage.test_open_error_with_keep_alive) ... (process:1904): libfprint-virtual_device-DEBUG: 00:53:51.154: 7399799215353: ../libfprint/drivers/virtual-device.c:387 382s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:51.154: 7399799215364: ../libfprint/drivers/virtual-device-listener.c:153 382s (process:1904): libfprint-device-DEBUG: 00:53:51.154: Device reported open completion 382s (process:1904): libfprint-device-DEBUG: 00:53:51.154: Completing action FPI_DEVICE_ACTION_OPEN in idle! 382s (process:1904): libfprint-device-DEBUG: 00:53:51.154: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 382s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:51.154: Got a new connection! 382s (process:1904): libfprint-virtual_device-DEBUG: 00:53:51.154: Got instructions of length 16 382s (process:1904): libfprint-virtual_device-DEBUG: 00:53:51.154: Received command SET_KEEP_ALIVE 1 382s (process:1904): libfprint-virtual_device-DEBUG: 00:53:51.154: Keep alive toggled: 1 382s (process:1904): libfprint-device-DEBUG: 00:53:51.154: Device reported close completion 382s (process:1904): libfprint-device-DEBUG: 00:53:51.154: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 382s (process:1904): libfprint-device-DEBUG: 00:53:51.154: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 382s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:51.154: Got a new connection! 382s (process:1904): libfprint-virtual_device-DEBUG: 00:53:51.155: Got instructions of length 7 382s (process:1904): libfprint-virtual_device-DEBUG: 00:53:51.155: Received command ERROR 5 382s (process:1904): libfprint-virtual_device-DEBUG: 00:53:51.155: 7399799216033: ../libfprint/drivers/virtual-device.c:387 382s (process:1904): libfprint-virtual_device-DEBUG: 00:53:51.155: Processing command ERROR 5 382s (process:1904): libfprint-device-DEBUG: 00:53:51.155: Device reported open completion 382s (process:1904): libfprint-device-DEBUG: 00:53:51.155: Completing action FPI_DEVICE_ACTION_OPEN in idle! 382s (process:1904): libfprint-device-DEBUG: 00:53:51.155: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 382s ok 382s test_quick_enroll (__main__.VirtualDeviceStorage.test_quick_enroll) ... (process:1904): libfprint-virtual_device-DEBUG: 00:53:51.155: 7399799216202: ../libfprint/drivers/virtual-device.c:387 382s (process:1904): libfprint-device-DEBUG: 00:53:51.155: Device reported open completion 382s (process:1904): libfprint-device-DEBUG: 00:53:51.155: Completing action FPI_DEVICE_ACTION_OPEN in idle! 382s (process:1904): libfprint-device-DEBUG: 00:53:51.155: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 382s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:51.155: Got a new connection! 382s (process:1904): libfprint-virtual_device-DEBUG: 00:53:51.155: Got instructions of length 19 382s (process:1904): libfprint-virtual_device-DEBUG: 00:53:51.155: Received command SET_ENROLL_STAGES 1 382s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:51.155: Got a new connection! 382s (process:1904): libfprint-virtual_device-DEBUG: 00:53:51.155: Got instructions of length 14 382s (process:1904): libfprint-virtual_device-DEBUG: 00:53:51.155: Received command SCAN testprint 382s (process:1904): libfprint-device-DEBUG: 00:53:51.155: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 382s (process:1904): libfprint-virtual_device-DEBUG: 00:53:51.155: Processing command SCAN testprint 382s (process:1904): libfprint-device-DEBUG: 00:53:51.155: Device reported finger status change: FP_FINGER_STATUS_NEEDED 382s (process:1904): libfprint-device-DEBUG: 00:53:51.155: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 382s (process:1904): libfprint-device-DEBUG: 00:53:51.155: Device reported finger status change: FP_FINGER_STATUS_NEEDED 382s (process:1904): libfprint-device-DEBUG: 00:53:51.155: Device reported enroll progress, reported 1 of 1 have been completed 382s (process:1904): libfprint-device-DEBUG: 00:53:51.155: Device reported enroll completion 382s (process:1904): libfprint-device-DEBUG: 00:53:51.155: Device reported finger status change: FP_FINGER_STATUS_NONE 382s (process:1904): libfprint-device-DEBUG: 00:53:51.155: Print for finger FP_FINGER_LEFT_LITTLE enrolled 382s (process:1904): libfprint-device-DEBUG: 00:53:51.155: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 382s (process:1904): libfprint-device-DEBUG: 00:53:51.155: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 382s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:51.156: Got a new connection! 382s (process:1904): libfprint-virtual_device-DEBUG: 00:53:51.156: Got instructions of length 5 382s (process:1904): libfprint-virtual_device-DEBUG: 00:53:51.156: Received command CONT 382s (process:1904): libfprint-virtual_device-DEBUG: 00:53:51.156: Processing command CONT 382s (process:1904): libfprint-device-DEBUG: 00:53:51.156: Device reported deletion completion 382s (process:1904): libfprint-device-DEBUG: 00:53:51.156: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 382s (process:1904): libfprint-device-DEBUG: 00:53:51.156: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 382s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:51.156: Got a new connection! 382s (process:1904): libfprint-virtual_device-DEBUG: 00:53:51.156: Got instructions of length 16 382s (process:1904): libfprint-virtual_device-DEBUG: 00:53:51.156: Received command SET_KEEP_ALIVE 0 382s (process:1904): libfprint-virtual_device-DEBUG: 00:53:51.156: Keep alive toggled: 0 382s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:51.156: Got a new connection! 382s (process:1904): libfprint-virtual_device-DEBUG: 00:53:51.156: Got instructions of length 19 382s (process:1904): libfprint-virtual_device-DEBUG: 00:53:51.156: Received command SET_ENROLL_STAGES 5 382s (process:1904): libfprint-device-DEBUG: 00:53:51.156: Device reported close completion 382s (process:1904): libfprint-device-DEBUG: 00:53:51.156: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 382s (process:1904): libfprint-device-DEBUG: 00:53:51.156: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 382s Enroll done 382s ok 382s test_verify_missing_print (__main__.VirtualDeviceStorage.test_verify_missing_print) ... (process:1904): libfprint-virtual_device-DEBUG: 00:53:51.156: 7399799217806: ../libfprint/drivers/virtual-device.c:387 382s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:51.156: 7399799217816: ../libfprint/drivers/virtual-device-listener.c:153 382s (process:1904): libfprint-device-DEBUG: 00:53:51.157: Device reported open completion 382s (process:1904): libfprint-device-DEBUG: 00:53:51.157: Completing action FPI_DEVICE_ACTION_OPEN in idle! 382s (process:1904): libfprint-device-DEBUG: 00:53:51.157: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 382s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:51.157: Got a new connection! 382s (process:1904): libfprint-virtual_device-DEBUG: 00:53:51.157: Got instructions of length 23 382s (process:1904): libfprint-virtual_device-DEBUG: 00:53:51.157: Received command SCAN not-existing-print 382s (process:1904): libfprint-device-DEBUG: 00:53:51.157: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 382s (process:1904): libfprint-virtual_device-DEBUG: 00:53:51.157: Processing command SCAN not-existing-print 382s (process:1904): libfprint-device-DEBUG: 00:53:51.157: Device reported finger status change: FP_FINGER_STATUS_NEEDED 382s (process:1904): libfprint-device-DEBUG: 00:53:51.157: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 382s (process:1904): libfprint-virtual_device-DEBUG: 00:53:51.157: Virtual device scanned print not-existing-print 382s (process:1904): libfprint-device-DEBUG: 00:53:51.157: Device reported verify result 382s (process:1904): libfprint-device-DEBUG: 00:53:51.157: Device reported finger status change: FP_FINGER_STATUS_NEEDED 382s (process:1904): libfprint-device-DEBUG: 00:53:51.157: Device reported verify completion 382s (process:1904): libfprint-device-DEBUG: 00:53:51.157: Device reported finger status change: FP_FINGER_STATUS_NONE 382s (process:1904): libfprint-device-DEBUG: 00:53:51.157: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 382s (process:1904): libfprint-device-DEBUG: 00:53:51.157: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 382s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:51.157: Got a new connection! 382s (process:1904): libfprint-virtual_device-DEBUG: 00:53:51.157: Got instructions of length 5 382s (process:1904): libfprint-virtual_device-DEBUG: 00:53:51.157: Received command CONT 382s (process:1904): libfprint-virtual_device-DEBUG: 00:53:51.157: Processing command CONT 382s (process:1904): libfprint-device-DEBUG: 00:53:51.157: Device reported deletion completion 382s (process:1904): libfprint-device-DEBUG: 00:53:51.157: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 382s (process:1904): libfprint-device-DEBUG: 00:53:51.157: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 382s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:51.157: Got a new connection! 382s (process:1904): libfprint-virtual_device-DEBUG: 00:53:51.157: Got instructions of length 16 382s (process:1904): libfprint-virtual_device-DEBUG: 00:53:51.157: Received command SET_KEEP_ALIVE 0 382s (process:1904): libfprint-virtual_device-DEBUG: 00:53:51.157: Keep alive toggled: 0 382s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:51.158: Got a new connection! 382s (process:1904): libfprint-virtual_device-DEBUG: 00:53:51.158: Got instructions of length 19 382s (process:1904): libfprint-virtual_device-DEBUG: 00:53:51.158: Received command SET_ENROLL_STAGES 5 382s (process:1904): libfprint-device-DEBUG: 00:53:51.158: Device reported close completion 382s (process:1904): libfprint-device-DEBUG: 00:53:51.158: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 382s (process:1904): libfprint-device-DEBUG: 00:53:51.158: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 382s ok 382s (process:1904): libfprint-virtual_device-DEBUG: 00:53:51.158: 7399799219493: ../libfprint/drivers/virtual-device.c:752 382s test_device_unplug (__main__.VirtualDeviceUnplugging.test_device_unplug) ... (process:1904): libfprint-context-DEBUG: 00:53:51.159: Initializing FpContext (libfprint version 1.94.8+tod1) 382s (process:1904): libfprint-tod-DEBUG: 00:53:51.159: Impossible to load the shared drivers dir Error opening directory “/usr/lib/arm-linux-gnueabihf/libfprint-2/tod-1”: No such file or directory 382s (process:1904): libfprint-context-DEBUG: 00:53:51.161: No driver found for USB device 1D6B:0003 382s (process:1904): libfprint-context-DEBUG: 00:53:51.161: No driver found for USB device 0627:0001 382s (process:1904): libfprint-context-DEBUG: 00:53:51.161: No driver found for USB device 1D6B:0002 382s (process:1904): libfprint-context-DEBUG: 00:53:51.161: Found virtual environment device: FP_VIRTUAL_DEVICE, /tmp/libfprint-jagu0pni/virtual-device.socket 382s (process:1904): libfprint-context-DEBUG: 00:53:51.161: created 382s (process:1904): libfprint-context-DEBUG: 00:53:51.161: Found virtual environment device: FP_VIRTUAL_DEVICE_STORAGE, /tmp/libfprint-nrcvdau3/virtual-device-storage.socket 382s (process:1904): libfprint-context-DEBUG: 00:53:51.161: created 382s (process:1904): libfprint-device-DEBUG: 00:53:51.162: Device reported probe completion 382s (process:1904): libfprint-device-DEBUG: 00:53:51.162: Device reported probe completion 382s (process:1904): libfprint-device-DEBUG: 00:53:51.162: Completing action FPI_DEVICE_ACTION_PROBE in idle! 382s (process:1904): libfprint-device-DEBUG: 00:53:51.162: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 382s (process:1904): libfprint-device-DEBUG: 00:53:51.162: Completing action FPI_DEVICE_ACTION_PROBE in idle! 382s (process:1904): libfprint-device-DEBUG: 00:53:51.162: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 382s (process:1904): libfprint-virtual_device-DEBUG: 00:53:51.162: 7399799223448: ../libfprint/drivers/virtual-device.c:387 382s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:51.162: 7399799223459: ../libfprint/drivers/virtual-device-listener.c:153 382s (process:1904): libfprint-device-DEBUG: 00:53:51.162: Device reported open completion 382s (process:1904): libfprint-device-DEBUG: 00:53:51.162: Completing action FPI_DEVICE_ACTION_OPEN in idle! 382s (process:1904): libfprint-device-DEBUG: 00:53:51.162: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 382s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:51.162: Got a new connection! 382s (process:1904): libfprint-virtual_device-DEBUG: 00:53:51.163: Got instructions of length 7 382s (process:1904): libfprint-virtual_device-DEBUG: 00:53:51.163: Received command UNPLUG 382s (process:1904): libfprint-device-DEBUG: 00:53:51.163: Device reported close completion 382s (process:1904): libfprint-device-DEBUG: 00:53:51.163: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 382s (process:1904): libfprint-device-DEBUG: 00:53:51.163: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 382s (process:1904): libfprint-virtual_device-DEBUG: 00:53:51.163: 7399799224523: ../libfprint/drivers/virtual-device.c:752 382s (process:1904): libfprint-virtual_device_storage-DEBUG: 00:53:51.163: 7399799224552: ../libfprint/drivers/virtual-device-storage.c:253 382s (process:1904): libfprint-virtual_device-DEBUG: 00:53:51.163: 7399799224562: ../libfprint/drivers/virtual-device.c:752 382s ok 382s test_device_unplug_during_verify (__main__.VirtualDeviceUnplugging.test_device_unplug_during_verify) ... (process:1904): libfprint-context-DEBUG: 00:53:51.164: Initializing FpContext (libfprint version 1.94.8+tod1) 382s (process:1904): libfprint-tod-DEBUG: 00:53:51.164: Impossible to load the shared drivers dir Error opening directory “/usr/lib/arm-linux-gnueabihf/libfprint-2/tod-1”: No such file or directory 382s (process:1904): libfprint-context-DEBUG: 00:53:51.166: No driver found for USB device 1D6B:0003 382s (process:1904): libfprint-context-DEBUG: 00:53:51.166: No driver found for USB device 0627:0001 382s (process:1904): libfprint-context-DEBUG: 00:53:51.166: No driver found for USB device 1D6B:0002 382s (process:1904): libfprint-context-DEBUG: 00:53:51.166: Found virtual environment device: FP_VIRTUAL_DEVICE, /tmp/libfprint-jagu0pni/virtual-device.socket 382s (process:1904): libfprint-context-DEBUG: 00:53:51.166: created 382s (process:1904): libfprint-context-DEBUG: 00:53:51.166: Found virtual environment device: FP_VIRTUAL_DEVICE_STORAGE, /tmp/libfprint-nrcvdau3/virtual-device-storage.socket 382s (process:1904): libfprint-context-DEBUG: 00:53:51.166: created 382s (process:1904): libfprint-device-DEBUG: 00:53:51.167: Device reported probe completion 382s (process:1904): libfprint-device-DEBUG: 00:53:51.167: Device reported probe completion 382s (process:1904): libfprint-device-DEBUG: 00:53:51.167: Completing action FPI_DEVICE_ACTION_PROBE in idle! 382s (process:1904): libfprint-device-DEBUG: 00:53:51.167: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 382s (process:1904): libfprint-device-DEBUG: 00:53:51.167: Completing action FPI_DEVICE_ACTION_PROBE in idle! 382s (process:1904): libfprint-device-DEBUG: 00:53:51.167: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 382s (process:1904): libfprint-virtual_device-DEBUG: 00:53:51.167: 7399799228543: ../libfprint/drivers/virtual-device.c:387 382s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:51.167: 7399799228566: ../libfprint/drivers/virtual-device-listener.c:153 382s (process:1904): libfprint-device-DEBUG: 00:53:51.167: Device reported open completion 382s (process:1904): libfprint-device-DEBUG: 00:53:51.167: Completing action FPI_DEVICE_ACTION_OPEN in idle! 382s (process:1904): libfprint-device-DEBUG: 00:53:51.167: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 382s (process:1904): libfprint-device-DEBUG: 00:53:51.168: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 382s (process:1904): libfprint-device-DEBUG: 00:53:51.168: Device reported finger status change: FP_FINGER_STATUS_NEEDED 382s (process:1904): libfprint-virtual_device_connection-DEBUG: 00:53:51.168: Got a new connection! 382s (process:1904): libfprint-virtual_device-DEBUG: 00:53:51.168: Got instructions of length 7 382s (process:1904): libfprint-virtual_device-DEBUG: 00:53:51.168: Received command UNPLUG 382s (process:1904): libfprint-device-DEBUG: 00:53:51.268: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 382s (process:1904): libfprint-device-DEBUG: 00:53:51.668: Device reported generic error (No commands arrived in time to run!) during action; action was: FPI_DEVICE_ACTION_VERIFY 382s (process:1904): libfprint-device-DEBUG: 00:53:51.668: Device reported verify completion 382s (process:1904): libfprint-device-DEBUG: 00:53:51.668: Device reported finger status change: FP_FINGER_STATUS_NONE 382s (process:1904): libfprint-device-DEBUG: 00:53:51.669: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 382s (process:1904): libfprint-device-DEBUG: 00:53:51.669: Updated temperature model after 0.40 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 382s (process:1904): libfprint-device-DEBUG: 00:53:51.669: Device reported close completion 382s (process:1904): libfprint-device-DEBUG: 00:53:51.669: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 382s (process:1904): libfprint-device-DEBUG: 00:53:51.669: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 382s (process:1904): libfprint-virtual_device-DEBUG: 00:53:51.669: 7399799730429: ../libfprint/drivers/virtual-device.c:752 382s (process:1904): libfprint-virtual_device_storage-DEBUG: 00:53:51.669: 7399799730462: ../libfprint/drivers/virtual-device-storage.c:253 382s (process:1904): libfprint-virtual_device-DEBUG: 00:53:51.669: 7399799730473: ../libfprint/drivers/virtual-device.c:752 382s ok 382s 382s ---------------------------------------------------------------------- 382s Ran 86 tests in 17.630s 382s 382s OK (skipped=1) 382s PASS: libfprint-2/virtual-device.test 382s Running test: libfprint-2/driver-egismoc-0586.test 382s ** (umockdev-run:1922): DEBUG: 00:53:51.758: umockdev.vala:127: Created udev test bed /tmp/umockdev.24ME22 382s ** (umockdev-run:1922): DEBUG: 00:53:51.759: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0/usb1/1-7 382s ** (umockdev-run:1922): DEBUG: 00:53:51.761: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0/usb1/1-7 (subsystem usb) 382s ** (umockdev-run:1922): DEBUG: 00:53:51.766: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.24ME22/dev/bus/usb/001/021 382s ** (umockdev-run:1922): DEBUG: 00:53:51.767: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0/usb1 382s ** (umockdev-run:1922): DEBUG: 00:53:51.768: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0/usb1 (subsystem usb) 382s ** (umockdev-run:1922): DEBUG: 00:53:51.772: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.24ME22/dev/bus/usb/001/001 382s ** (umockdev-run:1922): DEBUG: 00:53:51.772: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0 382s ** (umockdev-run:1922): DEBUG: 00:53:51.773: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0 (subsystem pci) 382s Executing: libfprint-2/driver-egismoc-0586.test 383s (process:1926): libfprint-context-DEBUG: 00:53:51.993: Initializing FpContext (libfprint version 1.94.8+tod1) 383s (process:1926): libfprint-tod-DEBUG: 00:53:51.993: Impossible to load the shared drivers dir Error opening directory “/usr/lib/arm-linux-gnueabihf/libfprint-2/tod-1”: No such file or directory 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:51.998: 7399800059654: ../libfprint/drivers/egismoc/egismoc.c:1597 383s (process:1926): libfprint-context-DEBUG: 00:53:51.999: No driver found for USB device 1D6B:0002 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.000: egismoc_probe enter --> 383s (process:1926): libfprint-device-DEBUG: 00:53:52.002: Device reported probe completion 383s (process:1926): libfprint-device-DEBUG: 00:53:52.002: Completing action FPI_DEVICE_ACTION_PROBE in idle! 383s (process:1926): libfprint-device-DEBUG: 00:53:52.002: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.004: Opening device 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.005: [egismoc] DEV_INIT_STATES entering state 0 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.006: [egismoc] DEV_INIT_STATES entering state 1 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.007: [egismoc] DEV_INIT_STATES entering state 2 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.008: [egismoc] DEV_INIT_STATES entering state 3 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.009: [egismoc] DEV_INIT_STATES entering state 4 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.009: [egismoc] DEV_INIT_STATES entering state 5 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.009: Execute command and get response 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.009: Get check bytes 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.009: [egismoc] CMD_STATES entering state 0 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.010: [egismoc] CMD_STATES entering state 1 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.011: Command receive callback 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.011: [egismoc] CMD_STATES completed successfully 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.011: Firmware version callback 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.011: Response suffix valid: yes 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.011: Device firmware version is 9050.6.2.56 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.011: [egismoc] DEV_INIT_STATES completed successfully 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.011: Task SSM done 383s (process:1926): libfprint-device-DEBUG: 00:53:52.011: Device reported open completion 383s (process:1926): libfprint-device-DEBUG: 00:53:52.011: Completing action FPI_DEVICE_ACTION_OPEN in idle! 383s (process:1926): libfprint-device-DEBUG: 00:53:52.011: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.012: List 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.012: [egismoc] LIST_STATES entering state 0 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.012: Execute command and get response 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.012: Get check bytes 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.012: [egismoc] CMD_STATES entering state 0 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.013: [egismoc] CMD_STATES entering state 1 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.014: Command receive callback 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.014: [egismoc] CMD_STATES completed successfully 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.014: List callback 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.014: Device fingerprint 1: FP1-20240417-7-67C37FA4-root 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.014: Number of currently enrolled fingerprints on the device is 1 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.014: [egismoc] LIST_STATES entering state 1 383s (process:1926): libfprint-device-DEBUG: 00:53:52.014: Device reported listing completion 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.014: [egismoc] LIST_STATES completed successfully 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.014: Task SSM done 383s (process:1926): libfprint-device-DEBUG: 00:53:52.014: Completing action FPI_DEVICE_ACTION_LIST in idle! 383s (process:1926): libfprint-device-DEBUG: 00:53:52.014: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.014: Clear storage 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.014: [egismoc] DELETE_STATES entering state 0 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.014: Execute command and get response 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.014: Get check bytes 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.014: [egismoc] CMD_STATES entering state 0 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.015: [egismoc] CMD_STATES entering state 1 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.016: Command receive callback 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.016: [egismoc] CMD_STATES completed successfully 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.016: List callback 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.016: Device fingerprint 1: FP1-20240417-7-67C37FA4-root 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.016: Number of currently enrolled fingerprints on the device is 1 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.016: [egismoc] DELETE_STATES entering state 1 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.016: Get delete command 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.016: Execute command and get response 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.016: Get check bytes 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.016: [egismoc] CMD_STATES entering state 0 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.016: [egismoc] CMD_STATES entering state 1 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.017: Command receive callback 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.017: [egismoc] CMD_STATES completed successfully 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.017: Delete callback 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.017: Response prefix valid: yes 383s (process:1926): libfprint-device-DEBUG: 00:53:52.017: Device reported deletion completion 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.017: [egismoc] DELETE_STATES completed successfully 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.017: Task SSM done 383s (process:1926): libfprint-device-DEBUG: 00:53:52.017: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 383s (process:1926): libfprint-device-DEBUG: 00:53:52.017: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.017: List 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.017: [egismoc] LIST_STATES entering state 0 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.017: Execute command and get response 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.017: Get check bytes 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.017: [egismoc] CMD_STATES entering state 0 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.018: [egismoc] CMD_STATES entering state 1 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.019: Command receive callback 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.019: [egismoc] CMD_STATES completed successfully 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.019: List callback 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.019: Number of currently enrolled fingerprints on the device is 0 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.019: [egismoc] LIST_STATES entering state 1 383s (process:1926): libfprint-device-DEBUG: 00:53:52.019: Device reported listing completion 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.019: [egismoc] LIST_STATES completed successfully 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.019: Task SSM done 383s (process:1926): libfprint-device-DEBUG: 00:53:52.019: Completing action FPI_DEVICE_ACTION_LIST in idle! 383s (process:1926): libfprint-device-DEBUG: 00:53:52.019: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 383s (process:1926): libfprint-device-DEBUG: 00:53:52.021: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.021: Enroll 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.021: [egismoc] ENROLL_STATES entering state 0 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.021: Execute command and get response 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.021: Get check bytes 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.021: [egismoc] CMD_STATES entering state 0 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.021: [egismoc] CMD_STATES entering state 1 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.022: Command receive callback 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.022: [egismoc] CMD_STATES completed successfully 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.022: List callback 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.022: Number of currently enrolled fingerprints on the device is 0 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.022: [egismoc] ENROLL_STATES entering state 1 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.022: [egismoc] ENROLL_STATES entering state 2 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.022: Execute command and get response 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.022: Get check bytes 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.022: [egismoc] CMD_STATES entering state 0 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.023: [egismoc] CMD_STATES entering state 1 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.023: Command receive callback 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.023: [egismoc] CMD_STATES completed successfully 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.023: Task SSM next state callback 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.023: [egismoc] ENROLL_STATES entering state 3 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.023: Execute command and get response 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.023: Get check bytes 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.023: [egismoc] CMD_STATES entering state 0 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.024: [egismoc] CMD_STATES entering state 1 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.025: Command receive callback 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.025: [egismoc] CMD_STATES completed successfully 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.025: Task SSM next state callback 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.025: [egismoc] ENROLL_STATES entering state 4 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.025: Wait for finger on sensor 383s (process:1926): libfprint-device-DEBUG: 00:53:52.025: Device reported finger status change: FP_FINGER_STATUS_NEEDED 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.026: Finger on sensor callback 383s (process:1926): libfprint-device-DEBUG: 00:53:52.026: Device reported finger status change: FP_FINGER_STATUS_PRESENT 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.026: [egismoc] ENROLL_STATES entering state 5 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.026: Execute command and get response 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.026: Get check bytes 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.026: [egismoc] CMD_STATES entering state 0 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.026: [egismoc] CMD_STATES entering state 1 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.027: Command receive callback 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.027: [egismoc] CMD_STATES completed successfully 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.027: Task SSM next state callback 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.027: [egismoc] ENROLL_STATES entering state 6 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.027: Get check command 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.027: Execute command and get response 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.027: Get check bytes 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.027: [egismoc] CMD_STATES entering state 0 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.028: [egismoc] CMD_STATES entering state 1 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.028: Command receive callback 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.028: [egismoc] CMD_STATES completed successfully 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.028: Enroll check callback 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.028: Response suffix valid: yes 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.028: [egismoc] ENROLL_STATES entering state 7 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.029: Execute command and get response 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.029: Get check bytes 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.029: [egismoc] CMD_STATES entering state 0 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.029: [egismoc] CMD_STATES entering state 1 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.030: Command receive callback 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.030: [egismoc] CMD_STATES completed successfully 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.030: Task SSM next state callback 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.030: [egismoc] ENROLL_STATES entering state 8 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.030: Execute command and get response 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.030: Get check bytes 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.030: [egismoc] CMD_STATES entering state 0 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.030: [egismoc] CMD_STATES entering state 1 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.031: Command receive callback 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.031: [egismoc] CMD_STATES completed successfully 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.031: Task SSM next state callback 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.031: [egismoc] ENROLL_STATES entering state 9 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.031: Execute command and get response 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.031: Get check bytes 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.031: [egismoc] CMD_STATES entering state 0 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.032: [egismoc] CMD_STATES entering state 1 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.032: Command receive callback 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.032: [egismoc] CMD_STATES completed successfully 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.032: Task SSM next state callback 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.032: [egismoc] ENROLL_STATES entering state 10 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.032: Wait for finger on sensor 383s (process:1926): libfprint-device-DEBUG: 00:53:52.032: Device reported finger status change: FP_FINGER_STATUS_NEEDED 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.033: Finger on sensor callback 383s (process:1926): libfprint-device-DEBUG: 00:53:52.033: Device reported finger status change: FP_FINGER_STATUS_PRESENT 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.033: [egismoc] ENROLL_STATES entering state 11 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.033: Execute command and get response 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.033: Get check bytes 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.033: [egismoc] CMD_STATES entering state 0 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.034: [egismoc] CMD_STATES entering state 1 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.034: Command receive callback 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.034: [egismoc] CMD_STATES completed successfully 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.034: Read capture callback 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.034: Response prefix valid: yes 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.034: Response suffix valid: yes 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.034: Partial capture successful. Please touch the sensor again (1/20) 383s (process:1926): libfprint-device-DEBUG: 00:53:52.034: Device reported enroll progress, reported 1 of 20 have been completed 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.035: [egismoc] ENROLL_STATES entering state 8 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.035: Execute command and get response 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.035: Get check bytes 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.035: [egismoc] CMD_STATES entering state 0 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.035: [egismoc] CMD_STATES entering state 1 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.036: Command receive callback 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.036: [egismoc] CMD_STATES completed successfully 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.036: Task SSM next state callback 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.036: [egismoc] ENROLL_STATES entering state 9 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.036: Execute command and get response 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.036: Get check bytes 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.036: [egismoc] CMD_STATES entering state 0 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.037: [egismoc] CMD_STATES entering state 1 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.037: Command receive callback 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.037: [egismoc] CMD_STATES completed successfully 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.037: Task SSM next state callback 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.037: [egismoc] ENROLL_STATES entering state 10 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.037: Wait for finger on sensor 383s (process:1926): libfprint-device-DEBUG: 00:53:52.037: Device reported finger status change: FP_FINGER_STATUS_NEEDED 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.038: Finger on sensor callback 383s (process:1926): libfprint-device-DEBUG: 00:53:52.038: Device reported finger status change: FP_FINGER_STATUS_PRESENT 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.038: [egismoc] ENROLL_STATES entering state 11 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.038: Execute command and get response 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.038: Get check bytes 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.038: [egismoc] CMD_STATES entering state 0 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.038: [egismoc] CMD_STATES entering state 1 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.039: Command receive callback 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.039: [egismoc] CMD_STATES completed successfully 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.039: Read capture callback 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.039: Response prefix valid: yes 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.039: Response suffix valid: yes 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.039: Partial capture successful. Please touch the sensor again (2/20) 383s (process:1926): libfprint-device-DEBUG: 00:53:52.039: Device reported enroll progress, reported 2 of 20 have been completed 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.039: [egismoc] ENROLL_STATES entering state 8 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.040: Execute command and get response 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.040: Get check bytes 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.040: [egismoc] CMD_STATES entering state 0 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.040: [egismoc] CMD_STATES entering state 1 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.041: Command receive callback 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.041: [egismoc] CMD_STATES completed successfully 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.041: Task SSM next state callback 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.041: [egismoc] ENROLL_STATES entering state 9 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.041: Execute command and get response 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.041: Get check bytes 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.041: [egismoc] CMD_STATES entering state 0 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.041: [egismoc] CMD_STATES entering state 1 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.042: Command receive callback 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.042: [egismoc] CMD_STATES completed successfully 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.042: Task SSM next state callback 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.042: [egismoc] ENROLL_STATES entering state 10 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.042: Wait for finger on sensor 383s (process:1926): libfprint-device-DEBUG: 00:53:52.042: Device reported finger status change: FP_FINGER_STATUS_NEEDED 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.043: Finger on sensor callback 383s (process:1926): libfprint-device-DEBUG: 00:53:52.043: Device reported finger status change: FP_FINGER_STATUS_PRESENT 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.043: [egismoc] ENROLL_STATES entering state 11 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.043: Execute command and get response 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.043: Get check bytes 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.043: [egismoc] CMD_STATES entering state 0 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.043: [egismoc] CMD_STATES entering state 1 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.044: Command receive callback 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.044: [egismoc] CMD_STATES completed successfully 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.044: Read capture callback 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.044: Response prefix valid: yes 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.044: Response suffix valid: yes 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.044: Partial capture successful. Please touch the sensor again (3/20) 383s (process:1926): libfprint-device-DEBUG: 00:53:52.044: Device reported enroll progress, reported 3 of 20 have been completed 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.044: [egismoc] ENROLL_STATES entering state 8 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.044: Execute command and get response 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.044: Get check bytes 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.044: [egismoc] CMD_STATES entering state 0 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.045: [egismoc] CMD_STATES entering state 1 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.045: Command receive callback 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.045: [egismoc] CMD_STATES completed successfully 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.046: Task SSM next state callback 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.046: [egismoc] ENROLL_STATES entering state 9 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.046: Execute command and get response 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.046: Get check bytes 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.046: [egismoc] CMD_STATES entering state 0 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.046: [egismoc] CMD_STATES entering state 1 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.047: Command receive callback 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.047: [egismoc] CMD_STATES completed successfully 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.047: Task SSM next state callback 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.047: [egismoc] ENROLL_STATES entering state 10 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.047: Wait for finger on sensor 383s (process:1926): libfprint-device-DEBUG: 00:53:52.047: Device reported finger status change: FP_FINGER_STATUS_NEEDED 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.047: Finger on sensor callback 383s (process:1926): libfprint-device-DEBUG: 00:53:52.047: Device reported finger status change: FP_FINGER_STATUS_PRESENT 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.047: [egismoc] ENROLL_STATES entering state 11 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.047: Execute command and get response 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.047: Get check bytes 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.047: [egismoc] CMD_STATES entering state 0 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.048: [egismoc] CMD_STATES entering state 1 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.049: Command receive callback 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.049: [egismoc] CMD_STATES completed successfully 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.049: Read capture callback 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.049: Response prefix valid: yes 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.049: Response suffix valid: yes 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.049: Partial capture successful. Please touch the sensor again (4/20) 383s (process:1926): libfprint-device-DEBUG: 00:53:52.049: Device reported enroll progress, reported 4 of 20 have been completed 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.049: [egismoc] ENROLL_STATES entering state 8 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.049: Execute command and get response 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.049: Get check bytes 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.049: [egismoc] CMD_STATES entering state 0 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.050: [egismoc] CMD_STATES entering state 1 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.050: Command receive callback 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.050: [egismoc] CMD_STATES completed successfully 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.050: Task SSM next state callback 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.050: [egismoc] ENROLL_STATES entering state 9 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.050: Execute command and get response 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.050: Get check bytes 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.050: [egismoc] CMD_STATES entering state 0 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.051: [egismoc] CMD_STATES entering state 1 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.052: Command receive callback 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.052: [egismoc] CMD_STATES completed successfully 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.052: Task SSM next state callback 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.052: [egismoc] ENROLL_STATES entering state 10 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.052: Wait for finger on sensor 383s (process:1926): libfprint-device-DEBUG: 00:53:52.052: Device reported finger status change: FP_FINGER_STATUS_NEEDED 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.052: Finger on sensor callback 383s (process:1926): libfprint-device-DEBUG: 00:53:52.052: Device reported finger status change: FP_FINGER_STATUS_PRESENT 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.052: [egismoc] ENROLL_STATES entering state 11 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.052: Execute command and get response 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.052: Get check bytes 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.052: [egismoc] CMD_STATES entering state 0 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.053: [egismoc] CMD_STATES entering state 1 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.054: Command receive callback 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.054: [egismoc] CMD_STATES completed successfully 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.054: Read capture callback 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.054: Response prefix valid: yes 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.054: Response suffix valid: yes 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.054: Partial capture successful. Please touch the sensor again (5/20) 383s (process:1926): libfprint-device-DEBUG: 00:53:52.054: Device reported enroll progress, reported 5 of 20 have been completed 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.054: [egismoc] ENROLL_STATES entering state 8 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.054: Execute command and get response 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.054: Get check bytes 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.054: [egismoc] CMD_STATES entering state 0 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.055: [egismoc] CMD_STATES entering state 1 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.055: Command receive callback 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.055: [egismoc] CMD_STATES completed successfully 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.055: Task SSM next state callback 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.055: [egismoc] ENROLL_STATES entering state 9 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.055: Execute command and get response 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.055: Get check bytes 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.055: [egismoc] CMD_STATES entering state 0 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.056: [egismoc] CMD_STATES entering state 1 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.056: Command receive callback 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.057: [egismoc] CMD_STATES completed successfully 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.057: Task SSM next state callback 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.057: [egismoc] ENROLL_STATES entering state 10 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.057: Wait for finger on sensor 383s (process:1926): libfprint-device-DEBUG: 00:53:52.057: Device reported finger status change: FP_FINGER_STATUS_NEEDED 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.057: Finger on sensor callback 383s (process:1926): libfprint-device-DEBUG: 00:53:52.057: Device reported finger status change: FP_FINGER_STATUS_PRESENT 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.057: [egismoc] ENROLL_STATES entering state 11 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.057: Execute command and get response 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.057: Get check bytes 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.057: [egismoc] CMD_STATES entering state 0 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.058: [egismoc] CMD_STATES entering state 1 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.058: Command receive callback 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.059: [egismoc] CMD_STATES completed successfully 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.059: Read capture callback 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.059: Response prefix valid: yes 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.059: Response suffix valid: yes 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.059: Partial capture successful. Please touch the sensor again (6/20) 383s (process:1926): libfprint-device-DEBUG: 00:53:52.059: Device reported enroll progress, reported 6 of 20 have been completed 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.059: [egismoc] ENROLL_STATES entering state 8 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.059: Execute command and get response 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.059: Get check bytes 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.059: [egismoc] CMD_STATES entering state 0 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.060: [egismoc] CMD_STATES entering state 1 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.060: Command receive callback 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.060: [egismoc] CMD_STATES completed successfully 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.060: Task SSM next state callback 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.060: [egismoc] ENROLL_STATES entering state 9 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.060: Execute command and get response 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.060: Get check bytes 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.060: [egismoc] CMD_STATES entering state 0 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.061: [egismoc] CMD_STATES entering state 1 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.062: Command receive callback 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.062: [egismoc] CMD_STATES completed successfully 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.062: Task SSM next state callback 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.062: [egismoc] ENROLL_STATES entering state 10 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.062: Wait for finger on sensor 383s (process:1926): libfprint-device-DEBUG: 00:53:52.062: Device reported finger status change: FP_FINGER_STATUS_NEEDED 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.062: Finger on sensor callback 383s (process:1926): libfprint-device-DEBUG: 00:53:52.062: Device reported finger status change: FP_FINGER_STATUS_PRESENT 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.062: [egismoc] ENROLL_STATES entering state 11 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.062: Execute command and get response 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.062: Get check bytes 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.062: [egismoc] CMD_STATES entering state 0 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.063: [egismoc] CMD_STATES entering state 1 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.064: Command receive callback 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.064: [egismoc] CMD_STATES completed successfully 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.064: Read capture callback 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.064: Response prefix valid: yes 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.064: Response suffix valid: yes 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.064: Partial capture successful. Please touch the sensor again (7/20) 383s (process:1926): libfprint-device-DEBUG: 00:53:52.064: Device reported enroll progress, reported 7 of 20 have been completed 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.064: [egismoc] ENROLL_STATES entering state 8 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.064: Execute command and get response 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.064: Get check bytes 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.064: [egismoc] CMD_STATES entering state 0 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.064: [egismoc] CMD_STATES entering state 1 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.065: Command receive callback 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.065: [egismoc] CMD_STATES completed successfully 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.065: Task SSM next state callback 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.065: [egismoc] ENROLL_STATES entering state 9 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.065: Execute command and get response 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.065: Get check bytes 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.065: [egismoc] CMD_STATES entering state 0 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.066: [egismoc] CMD_STATES entering state 1 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.066: Command receive callback 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.066: [egismoc] CMD_STATES completed successfully 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.066: Task SSM next state callback 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.066: [egismoc] ENROLL_STATES entering state 10 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.066: Wait for finger on sensor 383s (process:1926): libfprint-device-DEBUG: 00:53:52.066: Device reported finger status change: FP_FINGER_STATUS_NEEDED 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.067: Finger on sensor callback 383s (process:1926): libfprint-device-DEBUG: 00:53:52.067: Device reported finger status change: FP_FINGER_STATUS_PRESENT 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.067: [egismoc] ENROLL_STATES entering state 11 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.067: Execute command and get response 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.067: Get check bytes 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.067: [egismoc] CMD_STATES entering state 0 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.068: [egismoc] CMD_STATES entering state 1 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.068: Command receive callback 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.068: [egismoc] CMD_STATES completed successfully 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.068: Read capture callback 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.068: Response prefix valid: yes 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.068: Response suffix valid: NO 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.068: Response prefix valid: yes 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.068: Response suffix valid: yes 383s (process:1926): libfprint-device-DEBUG: 00:53:52.068: Device reported enroll progress, reported 7 of 20 have been completed 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.069: [egismoc] ENROLL_STATES entering state 8 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.069: Execute command and get response 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.069: Get check bytes 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.069: [egismoc] CMD_STATES entering state 0 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.069: [egismoc] CMD_STATES entering state 1 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.070: Command receive callback 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.070: [egismoc] CMD_STATES completed successfully 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.070: Task SSM next state callback 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.070: [egismoc] ENROLL_STATES entering state 9 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.070: Execute command and get response 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.070: Get check bytes 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.070: [egismoc] CMD_STATES entering state 0 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.070: [egismoc] CMD_STATES entering state 1 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.071: Command receive callback 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.071: [egismoc] CMD_STATES completed successfully 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.071: Task SSM next state callback 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.071: [egismoc] ENROLL_STATES entering state 10 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.071: Wait for finger on sensor 383s (process:1926): libfprint-device-DEBUG: 00:53:52.071: Device reported finger status change: FP_FINGER_STATUS_NEEDED 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.072: Finger on sensor callback 383s (process:1926): libfprint-device-DEBUG: 00:53:52.072: Device reported finger status change: FP_FINGER_STATUS_PRESENT 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.072: [egismoc] ENROLL_STATES entering state 11 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.072: Execute command and get response 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.072: Get check bytes 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.072: [egismoc] CMD_STATES entering state 0 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.073: [egismoc] CMD_STATES entering state 1 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.074: Command receive callback 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.074: [egismoc] CMD_STATES completed successfully 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.074: Read capture callback 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.074: Response prefix valid: yes 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.074: Response suffix valid: yes 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.074: Partial capture successful. Please touch the sensor again (8/20) 383s (process:1926): libfprint-device-DEBUG: 00:53:52.074: Device reported enroll progress, reported 8 of 20 have been completed 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.074: [egismoc] ENROLL_STATES entering state 8 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.074: Execute command and get response 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.074: Get check bytes 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.074: [egismoc] CMD_STATES entering state 0 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.074: [egismoc] CMD_STATES entering state 1 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.075: Command receive callback 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.075: [egismoc] CMD_STATES completed successfully 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.075: Task SSM next state callback 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.075: [egismoc] ENROLL_STATES entering state 9 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.075: Execute command and get response 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.075: Get check bytes 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.075: [egismoc] CMD_STATES entering state 0 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.076: [egismoc] CMD_STATES entering state 1 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.076: Command receive callback 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.076: [egismoc] CMD_STATES completed successfully 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.076: Task SSM next state callback 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.076: [egismoc] ENROLL_STATES entering state 10 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.076: Wait for finger on sensor 383s (process:1926): libfprint-device-DEBUG: 00:53:52.076: Device reported finger status change: FP_FINGER_STATUS_NEEDED 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.077: Finger on sensor callback 383s (process:1926): libfprint-device-DEBUG: 00:53:52.077: Device reported finger status change: FP_FINGER_STATUS_PRESENT 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.077: [egismoc] ENROLL_STATES entering state 11 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.077: Execute command and get response 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.077: Get check bytes 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.077: [egismoc] CMD_STATES entering state 0 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.078: [egismoc] CMD_STATES entering state 1 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.079: Command receive callback 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.079: [egismoc] CMD_STATES completed successfully 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.079: Read capture callback 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.079: Response prefix valid: yes 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.079: Response suffix valid: NO 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.079: Response prefix valid: yes 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.079: Response suffix valid: yes 383s (process:1926): libfprint-device-DEBUG: 00:53:52.079: Device reported enroll progress, reported 8 of 20 have been completed 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.079: [egismoc] ENROLL_STATES entering state 8 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.079: Execute command and get response 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.079: Get check bytes 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.079: [egismoc] CMD_STATES entering state 0 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.079: [egismoc] CMD_STATES entering state 1 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.080: Command receive callback 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.080: [egismoc] CMD_STATES completed successfully 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.080: Task SSM next state callback 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.080: [egismoc] ENROLL_STATES entering state 9 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.080: Execute command and get response 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.080: Get check bytes 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.080: [egismoc] CMD_STATES entering state 0 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.081: [egismoc] CMD_STATES entering state 1 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.081: Command receive callback 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.081: [egismoc] CMD_STATES completed successfully 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.081: Task SSM next state callback 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.081: [egismoc] ENROLL_STATES entering state 10 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.081: Wait for finger on sensor 383s (process:1926): libfprint-device-DEBUG: 00:53:52.081: Device reported finger status change: FP_FINGER_STATUS_NEEDED 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.082: Finger on sensor callback 383s (process:1926): libfprint-device-DEBUG: 00:53:52.082: Device reported finger status change: FP_FINGER_STATUS_PRESENT 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.082: [egismoc] ENROLL_STATES entering state 11 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.082: Execute command and get response 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.082: Get check bytes 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.082: [egismoc] CMD_STATES entering state 0 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.083: [egismoc] CMD_STATES entering state 1 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.083: Command receive callback 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.083: [egismoc] CMD_STATES completed successfully 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.083: Read capture callback 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.083: Response prefix valid: yes 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.083: Response suffix valid: yes 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.083: Partial capture successful. Please touch the sensor again (9/20) 383s (process:1926): libfprint-device-DEBUG: 00:53:52.083: Device reported enroll progress, reported 9 of 20 have been completed 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.083: [egismoc] ENROLL_STATES entering state 8 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.083: Execute command and get response 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.083: Get check bytes 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.083: [egismoc] CMD_STATES entering state 0 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.084: [egismoc] CMD_STATES entering state 1 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.085: Command receive callback 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.085: [egismoc] CMD_STATES completed successfully 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.085: Task SSM next state callback 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.085: [egismoc] ENROLL_STATES entering state 9 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.085: Execute command and get response 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.085: Get check bytes 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.085: [egismoc] CMD_STATES entering state 0 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.085: [egismoc] CMD_STATES entering state 1 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.086: Command receive callback 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.086: [egismoc] CMD_STATES completed successfully 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.086: Task SSM next state callback 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.086: [egismoc] ENROLL_STATES entering state 10 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.086: Wait for finger on sensor 383s (process:1926): libfprint-device-DEBUG: 00:53:52.086: Device reported finger status change: FP_FINGER_STATUS_NEEDED 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.087: Finger on sensor callback 383s (process:1926): libfprint-device-DEBUG: 00:53:52.087: Device reported finger status change: FP_FINGER_STATUS_PRESENT 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.087: [egismoc] ENROLL_STATES entering state 11 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.087: Execute command and get response 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.087: Get check bytes 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.087: [egismoc] CMD_STATES entering state 0 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.087: [egismoc] CMD_STATES entering state 1 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.088: Command receive callback 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.088: [egismoc] CMD_STATES completed successfully 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.088: Read capture callback 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.088: Response prefix valid: yes 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.088: Response suffix valid: yes 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.088: Partial capture successful. Please touch the sensor again (10/20) 383s (process:1926): libfprint-device-DEBUG: 00:53:52.088: Device reported enroll progress, reported 10 of 20 have been completed 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.088: [egismoc] ENROLL_STATES entering state 8 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.088: Execute command and get response 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.088: Get check bytes 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.088: [egismoc] CMD_STATES entering state 0 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.089: [egismoc] CMD_STATES entering state 1 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.090: Command receive callback 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.090: [egismoc] CMD_STATES completed successfully 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.090: Task SSM next state callback 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.090: [egismoc] ENROLL_STATES entering state 9 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.090: Execute command and get response 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.090: Get check bytes 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.090: [egismoc] CMD_STATES entering state 0 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.090: [egismoc] CMD_STATES entering state 1 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.091: Command receive callback 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.091: [egismoc] CMD_STATES completed successfully 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.091: Task SSM next state callback 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.091: [egismoc] ENROLL_STATES entering state 10 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.091: Wait for finger on sensor 383s (process:1926): libfprint-device-DEBUG: 00:53:52.091: Device reported finger status change: FP_FINGER_STATUS_NEEDED 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.092: Finger on sensor callback 383s (process:1926): libfprint-device-DEBUG: 00:53:52.092: Device reported finger status change: FP_FINGER_STATUS_PRESENT 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.092: [egismoc] ENROLL_STATES entering state 11 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.092: Execute command and get response 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.092: Get check bytes 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.092: [egismoc] CMD_STATES entering state 0 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.092: [egismoc] CMD_STATES entering state 1 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.093: Command receive callback 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.093: [egismoc] CMD_STATES completed successfully 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.093: Read capture callback 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.093: Response prefix valid: yes 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.093: Response suffix valid: yes 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.093: Partial capture successful. Please touch the sensor again (11/20) 383s (process:1926): libfprint-device-DEBUG: 00:53:52.093: Device reported enroll progress, reported 11 of 20 have been completed 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.093: [egismoc] ENROLL_STATES entering state 8 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.093: Execute command and get response 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.093: Get check bytes 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.093: [egismoc] CMD_STATES entering state 0 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.094: [egismoc] CMD_STATES entering state 1 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.095: Command receive callback 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.095: [egismoc] CMD_STATES completed successfully 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.095: Task SSM next state callback 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.095: [egismoc] ENROLL_STATES entering state 9 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.095: Execute command and get response 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.095: Get check bytes 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.095: [egismoc] CMD_STATES entering state 0 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.095: [egismoc] CMD_STATES entering state 1 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.096: Command receive callback 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.096: [egismoc] CMD_STATES completed successfully 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.096: Task SSM next state callback 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.096: [egismoc] ENROLL_STATES entering state 10 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.096: Wait for finger on sensor 383s (process:1926): libfprint-device-DEBUG: 00:53:52.096: Device reported finger status change: FP_FINGER_STATUS_NEEDED 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.097: Finger on sensor callback 383s (process:1926): libfprint-device-DEBUG: 00:53:52.097: Device reported finger status change: FP_FINGER_STATUS_PRESENT 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.097: [egismoc] ENROLL_STATES entering state 11 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.097: Execute command and get response 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.097: Get check bytes 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.097: [egismoc] CMD_STATES entering state 0 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.097: [egismoc] CMD_STATES entering state 1 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.098: Command receive callback 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.098: [egismoc] CMD_STATES completed successfully 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.098: Read capture callback 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.098: Response prefix valid: yes 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.098: Response suffix valid: yes 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.098: Partial capture successful. Please touch the sensor again (12/20) 383s (process:1926): libfprint-device-DEBUG: 00:53:52.098: Device reported enroll progress, reported 12 of 20 have been completed 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.098: [egismoc] ENROLL_STATES entering state 8 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.098: Execute command and get response 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.098: Get check bytes 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.098: [egismoc] CMD_STATES entering state 0 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.099: [egismoc] CMD_STATES entering state 1 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.100: Command receive callback 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.100: [egismoc] CMD_STATES completed successfully 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.100: Task SSM next state callback 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.100: [egismoc] ENROLL_STATES entering state 9 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.100: Execute command and get response 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.100: Get check bytes 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.100: [egismoc] CMD_STATES entering state 0 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.100: [egismoc] CMD_STATES entering state 1 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.101: Command receive callback 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.101: [egismoc] CMD_STATES completed successfully 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.101: Task SSM next state callback 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.101: [egismoc] ENROLL_STATES entering state 10 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.101: Wait for finger on sensor 383s (process:1926): libfprint-device-DEBUG: 00:53:52.101: Device reported finger status change: FP_FINGER_STATUS_NEEDED 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.102: Finger on sensor callback 383s (process:1926): libfprint-device-DEBUG: 00:53:52.102: Device reported finger status change: FP_FINGER_STATUS_PRESENT 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.102: [egismoc] ENROLL_STATES entering state 11 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.102: Execute command and get response 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.102: Get check bytes 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.102: [egismoc] CMD_STATES entering state 0 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.102: [egismoc] CMD_STATES entering state 1 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.103: Command receive callback 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.103: [egismoc] CMD_STATES completed successfully 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.103: Read capture callback 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.103: Response prefix valid: yes 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.103: Response suffix valid: yes 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.103: Partial capture successful. Please touch the sensor again (13/20) 383s (process:1926): libfprint-device-DEBUG: 00:53:52.103: Device reported enroll progress, reported 13 of 20 have been completed 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.103: [egismoc] ENROLL_STATES entering state 8 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.103: Execute command and get response 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.103: Get check bytes 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.103: [egismoc] CMD_STATES entering state 0 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.104: [egismoc] CMD_STATES entering state 1 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.105: Command receive callback 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.105: [egismoc] CMD_STATES completed successfully 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.105: Task SSM next state callback 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.105: [egismoc] ENROLL_STATES entering state 9 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.105: Execute command and get response 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.105: Get check bytes 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.105: [egismoc] CMD_STATES entering state 0 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.105: [egismoc] CMD_STATES entering state 1 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.106: Command receive callback 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.106: [egismoc] CMD_STATES completed successfully 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.106: Task SSM next state callback 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.106: [egismoc] ENROLL_STATES entering state 10 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.106: Wait for finger on sensor 383s (process:1926): libfprint-device-DEBUG: 00:53:52.106: Device reported finger status change: FP_FINGER_STATUS_NEEDED 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.107: Finger on sensor callback 383s (process:1926): libfprint-device-DEBUG: 00:53:52.107: Device reported finger status change: FP_FINGER_STATUS_PRESENT 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.107: [egismoc] ENROLL_STATES entering state 11 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.107: Execute command and get response 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.107: Get check bytes 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.107: [egismoc] CMD_STATES entering state 0 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.107: [egismoc] CMD_STATES entering state 1 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.108: Command receive callback 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.108: [egismoc] CMD_STATES completed successfully 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.108: Read capture callback 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.108: Response prefix valid: yes 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.108: Response suffix valid: yes 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.108: Partial capture successful. Please touch the sensor again (14/20) 383s (process:1926): libfprint-device-DEBUG: 00:53:52.108: Device reported enroll progress, reported 14 of 20 have been completed 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.108: [egismoc] ENROLL_STATES entering state 8 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.108: Execute command and get response 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.108: Get check bytes 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.108: [egismoc] CMD_STATES entering state 0 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.109: [egismoc] CMD_STATES entering state 1 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.110: Command receive callback 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.110: [egismoc] CMD_STATES completed successfully 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.110: Task SSM next state callback 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.110: [egismoc] ENROLL_STATES entering state 9 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.110: Execute command and get response 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.110: Get check bytes 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.110: [egismoc] CMD_STATES entering state 0 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.110: [egismoc] CMD_STATES entering state 1 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.111: Command receive callback 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.111: [egismoc] CMD_STATES completed successfully 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.111: Task SSM next state callback 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.111: [egismoc] ENROLL_STATES entering state 10 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.111: Wait for finger on sensor 383s (process:1926): libfprint-device-DEBUG: 00:53:52.111: Device reported finger status change: FP_FINGER_STATUS_NEEDED 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.112: Finger on sensor callback 383s (process:1926): libfprint-device-DEBUG: 00:53:52.112: Device reported finger status change: FP_FINGER_STATUS_PRESENT 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.112: [egismoc] ENROLL_STATES entering state 11 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.112: Execute command and get response 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.112: Get check bytes 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.112: [egismoc] CMD_STATES entering state 0 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.112: [egismoc] CMD_STATES entering state 1 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.113: Command receive callback 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.113: [egismoc] CMD_STATES completed successfully 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.113: Read capture callback 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.113: Response prefix valid: yes 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.113: Response suffix valid: yes 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.113: Partial capture successful. Please touch the sensor again (15/20) 383s (process:1926): libfprint-device-DEBUG: 00:53:52.113: Device reported enroll progress, reported 15 of 20 have been completed 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.113: [egismoc] ENROLL_STATES entering state 8 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.113: Execute command and get response 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.113: Get check bytes 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.113: [egismoc] CMD_STATES entering state 0 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.114: [egismoc] CMD_STATES entering state 1 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.114: Command receive callback 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.114: [egismoc] CMD_STATES completed successfully 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.115: Task SSM next state callback 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.115: [egismoc] ENROLL_STATES entering state 9 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.115: Execute command and get response 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.115: Get check bytes 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.115: [egismoc] CMD_STATES entering state 0 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.115: [egismoc] CMD_STATES entering state 1 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.116: Command receive callback 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.116: [egismoc] CMD_STATES completed successfully 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.116: Task SSM next state callback 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.116: [egismoc] ENROLL_STATES entering state 10 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.116: Wait for finger on sensor 383s (process:1926): libfprint-device-DEBUG: 00:53:52.116: Device reported finger status change: FP_FINGER_STATUS_NEEDED 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.116: Finger on sensor callback 383s (process:1926): libfprint-device-DEBUG: 00:53:52.116: Device reported finger status change: FP_FINGER_STATUS_PRESENT 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.116: [egismoc] ENROLL_STATES entering state 11 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.116: Execute command and get response 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.116: Get check bytes 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.116: [egismoc] CMD_STATES entering state 0 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.117: [egismoc] CMD_STATES entering state 1 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.118: Command receive callback 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.118: [egismoc] CMD_STATES completed successfully 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.118: Read capture callback 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.118: Response prefix valid: yes 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.118: Response suffix valid: yes 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.118: Partial capture successful. Please touch the sensor again (16/20) 383s (process:1926): libfprint-device-DEBUG: 00:53:52.118: Device reported enroll progress, reported 16 of 20 have been completed 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.118: [egismoc] ENROLL_STATES entering state 8 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.118: Execute command and get response 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.118: Get check bytes 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.118: [egismoc] CMD_STATES entering state 0 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.118: [egismoc] CMD_STATES entering state 1 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.119: Command receive callback 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.119: [egismoc] CMD_STATES completed successfully 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.119: Task SSM next state callback 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.119: [egismoc] ENROLL_STATES entering state 9 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.119: Execute command and get response 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.119: Get check bytes 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.119: [egismoc] CMD_STATES entering state 0 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.120: [egismoc] CMD_STATES entering state 1 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.120: Command receive callback 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.120: [egismoc] CMD_STATES completed successfully 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.120: Task SSM next state callback 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.120: [egismoc] ENROLL_STATES entering state 10 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.120: Wait for finger on sensor 383s (process:1926): libfprint-device-DEBUG: 00:53:52.120: Device reported finger status change: FP_FINGER_STATUS_NEEDED 383s (process:1926): libfprint-device-DEBUG: 00:53:52.121: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.121: Finger on sensor callback 383s (process:1926): libfprint-device-DEBUG: 00:53:52.121: Device reported finger status change: FP_FINGER_STATUS_PRESENT 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.121: [egismoc] ENROLL_STATES entering state 11 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.121: Execute command and get response 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.121: Get check bytes 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.121: [egismoc] CMD_STATES entering state 0 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.122: [egismoc] CMD_STATES entering state 1 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.122: Command receive callback 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.122: [egismoc] CMD_STATES completed successfully 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.122: Read capture callback 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.122: Response prefix valid: yes 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.122: Response suffix valid: yes 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.122: Partial capture successful. Please touch the sensor again (17/20) 383s (process:1926): libfprint-device-DEBUG: 00:53:52.122: Device reported enroll progress, reported 17 of 20 have been completed 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.123: [egismoc] ENROLL_STATES entering state 8 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.123: Execute command and get response 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.123: Get check bytes 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.123: [egismoc] CMD_STATES entering state 0 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.123: [egismoc] CMD_STATES entering state 1 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.124: Command receive callback 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.124: [egismoc] CMD_STATES completed successfully 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.124: Task SSM next state callback 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.124: [egismoc] ENROLL_STATES entering state 9 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.124: Execute command and get response 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.124: Get check bytes 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.124: [egismoc] CMD_STATES entering state 0 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.124: [egismoc] CMD_STATES entering state 1 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.125: Command receive callback 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.125: [egismoc] CMD_STATES completed successfully 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.125: Task SSM next state callback 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.125: [egismoc] ENROLL_STATES entering state 10 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.125: Wait for finger on sensor 383s (process:1926): libfprint-device-DEBUG: 00:53:52.125: Device reported finger status change: FP_FINGER_STATUS_NEEDED 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.126: Finger on sensor callback 383s (process:1926): libfprint-device-DEBUG: 00:53:52.126: Device reported finger status change: FP_FINGER_STATUS_PRESENT 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.126: [egismoc] ENROLL_STATES entering state 11 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.126: Execute command and get response 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.126: Get check bytes 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.126: [egismoc] CMD_STATES entering state 0 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.126: [egismoc] CMD_STATES entering state 1 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.127: Command receive callback 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.127: [egismoc] CMD_STATES completed successfully 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.127: Read capture callback 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.127: Response prefix valid: yes 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.127: Response suffix valid: yes 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.127: Partial capture successful. Please touch the sensor again (18/20) 383s (process:1926): libfprint-device-DEBUG: 00:53:52.127: Device reported enroll progress, reported 18 of 20 have been completed 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.127: [egismoc] ENROLL_STATES entering state 8 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.127: Execute command and get response 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.127: Get check bytes 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.127: [egismoc] CMD_STATES entering state 0 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.128: [egismoc] CMD_STATES entering state 1 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.128: Command receive callback 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.128: [egismoc] CMD_STATES completed successfully 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.128: Task SSM next state callback 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.128: [egismoc] ENROLL_STATES entering state 9 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.128: Execute command and get response 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.128: Get check bytes 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.128: [egismoc] CMD_STATES entering state 0 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.129: [egismoc] CMD_STATES entering state 1 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.130: Command receive callback 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.130: [egismoc] CMD_STATES completed successfully 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.130: Task SSM next state callback 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.130: [egismoc] ENROLL_STATES entering state 10 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.130: Wait for finger on sensor 383s (process:1926): libfprint-device-DEBUG: 00:53:52.130: Device reported finger status change: FP_FINGER_STATUS_NEEDED 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.130: Finger on sensor callback 383s (process:1926): libfprint-device-DEBUG: 00:53:52.130: Device reported finger status change: FP_FINGER_STATUS_PRESENT 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.130: [egismoc] ENROLL_STATES entering state 11 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.130: Execute command and get response 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.130: Get check bytes 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.130: [egismoc] CMD_STATES entering state 0 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.131: [egismoc] CMD_STATES entering state 1 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.132: Command receive callback 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.132: [egismoc] CMD_STATES completed successfully 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.132: Read capture callback 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.132: Response prefix valid: yes 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.132: Response suffix valid: yes 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.132: Partial capture successful. Please touch the sensor again (19/20) 383s (process:1926): libfprint-device-DEBUG: 00:53:52.132: Device reported enroll progress, reported 19 of 20 have been completed 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.132: [egismoc] ENROLL_STATES entering state 8 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.132: Execute command and get response 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.132: Get check bytes 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.132: [egismoc] CMD_STATES entering state 0 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.133: [egismoc] CMD_STATES entering state 1 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.133: Command receive callback 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.133: [egismoc] CMD_STATES completed successfully 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.133: Task SSM next state callback 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.133: [egismoc] ENROLL_STATES entering state 9 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.133: Execute command and get response 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.133: Get check bytes 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.133: [egismoc] CMD_STATES entering state 0 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.134: [egismoc] CMD_STATES entering state 1 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.134: Command receive callback 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.134: [egismoc] CMD_STATES completed successfully 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.134: Task SSM next state callback 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.134: [egismoc] ENROLL_STATES entering state 10 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.134: Wait for finger on sensor 383s (process:1926): libfprint-device-DEBUG: 00:53:52.134: Device reported finger status change: FP_FINGER_STATUS_NEEDED 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.135: Finger on sensor callback 383s (process:1926): libfprint-device-DEBUG: 00:53:52.135: Device reported finger status change: FP_FINGER_STATUS_PRESENT 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.135: [egismoc] ENROLL_STATES entering state 11 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.135: Execute command and get response 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.135: Get check bytes 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.135: [egismoc] CMD_STATES entering state 0 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.136: [egismoc] CMD_STATES entering state 1 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.136: Command receive callback 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.137: [egismoc] CMD_STATES completed successfully 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.137: Read capture callback 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.137: Response prefix valid: yes 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.137: Response suffix valid: yes 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.137: Partial capture successful. Please touch the sensor again (20/20) 383s (process:1926): libfprint-device-DEBUG: 00:53:52.137: Device reported enroll progress, reported 20 of 20 have been completed 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.137: [egismoc] ENROLL_STATES entering state 12 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.137: Execute command and get response 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.137: Get check bytes 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.137: [egismoc] CMD_STATES entering state 0 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.137: [egismoc] CMD_STATES entering state 1 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.138: Command receive callback 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.138: [egismoc] CMD_STATES completed successfully 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.138: Task SSM next state callback 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.138: [egismoc] ENROLL_STATES entering state 13 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.138: New fingerprint ID: FP1-00000000-2-00000000-nobody 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.138: Execute command and get response 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.138: Get check bytes 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.138: [egismoc] CMD_STATES entering state 0 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.139: [egismoc] CMD_STATES entering state 1 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.139: Command receive callback 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.139: [egismoc] CMD_STATES completed successfully 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.139: Task SSM next state callback 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.139: [egismoc] ENROLL_STATES entering state 14 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.139: Execute command and get response 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.139: Get check bytes 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.139: [egismoc] CMD_STATES entering state 0 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.140: [egismoc] CMD_STATES entering state 1 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.141: Command receive callback 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.141: [egismoc] CMD_STATES completed successfully 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.141: Task SSM next state callback 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.141: [egismoc] ENROLL_STATES entering state 15 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.141: Enrollment was successful! 383s (process:1926): libfprint-device-DEBUG: 00:53:52.141: Device reported enroll completion 383s (process:1926): libfprint-device-DEBUG: 00:53:52.141: Device reported finger status change: FP_FINGER_STATUS_NONE 383s (process:1926): libfprint-device-DEBUG: 00:53:52.141: Print for finger FP_FINGER_LEFT_INDEX enrolled 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.141: [egismoc] ENROLL_STATES completed successfully 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.141: Task SSM done 383s (process:1926): libfprint-device-DEBUG: 00:53:52.141: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 383s (process:1926): libfprint-device-DEBUG: 00:53:52.141: Updated temperature model after 0.02 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.141: List 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.141: [egismoc] LIST_STATES entering state 0 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.141: Execute command and get response 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.141: Get check bytes 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.141: [egismoc] CMD_STATES entering state 0 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.142: [egismoc] CMD_STATES entering state 1 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.142: Command receive callback 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.142: [egismoc] CMD_STATES completed successfully 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.142: List callback 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.142: Device fingerprint 1: FP1-00000000-2-00000000-nobody 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.142: Number of currently enrolled fingerprints on the device is 1 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.142: [egismoc] LIST_STATES entering state 1 383s (process:1926): libfprint-device-DEBUG: 00:53:52.142: Device reported listing completion 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.142: [egismoc] LIST_STATES completed successfully 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.142: Task SSM done 383s (process:1926): libfprint-device-DEBUG: 00:53:52.142: Completing action FPI_DEVICE_ACTION_LIST in idle! 383s (process:1926): libfprint-device-DEBUG: 00:53:52.142: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 383s (process:1926): libfprint-device-DEBUG: 00:53:52.143: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.143: Identify or Verify 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.143: [egismoc] IDENTIFY_STATES entering state 0 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.143: Execute command and get response 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.143: Get check bytes 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.143: [egismoc] CMD_STATES entering state 0 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.143: [egismoc] CMD_STATES entering state 1 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.144: Command receive callback 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.144: [egismoc] CMD_STATES completed successfully 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.144: List callback 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.144: Device fingerprint 1: FP1-00000000-2-00000000-nobody 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.144: Number of currently enrolled fingerprints on the device is 1 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.144: [egismoc] IDENTIFY_STATES entering state 1 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.144: [egismoc] IDENTIFY_STATES entering state 2 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.144: Execute command and get response 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.144: Get check bytes 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.144: [egismoc] CMD_STATES entering state 0 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.145: [egismoc] CMD_STATES entering state 1 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.145: Command receive callback 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.145: [egismoc] CMD_STATES completed successfully 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.145: Task SSM next state callback 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.145: [egismoc] IDENTIFY_STATES entering state 3 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.145: Execute command and get response 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.145: Get check bytes 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.145: [egismoc] CMD_STATES entering state 0 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.146: [egismoc] CMD_STATES entering state 1 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.147: Command receive callback 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.147: [egismoc] CMD_STATES completed successfully 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.147: Task SSM next state callback 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.147: [egismoc] IDENTIFY_STATES entering state 4 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.147: Wait for finger on sensor 383s (process:1926): libfprint-device-DEBUG: 00:53:52.147: Device reported finger status change: FP_FINGER_STATUS_NEEDED 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.147: Finger on sensor callback 383s (process:1926): libfprint-device-DEBUG: 00:53:52.147: Device reported finger status change: FP_FINGER_STATUS_PRESENT 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.147: [egismoc] IDENTIFY_STATES entering state 5 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.147: Execute command and get response 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.147: Get check bytes 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.147: [egismoc] CMD_STATES entering state 0 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.148: [egismoc] CMD_STATES entering state 1 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.149: Command receive callback 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.149: [egismoc] CMD_STATES completed successfully 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.149: Task SSM next state callback 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.149: [egismoc] IDENTIFY_STATES entering state 6 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.149: Get check command 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.149: Execute command and get response 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.149: Get check bytes 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.149: [egismoc] CMD_STATES entering state 0 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.149: [egismoc] CMD_STATES entering state 1 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.150: Command receive callback 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.150: [egismoc] CMD_STATES completed successfully 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.150: Identify check callback 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.150: Response suffix valid: yes 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.150: Identify successful for: FP1-00000000-2-00000000-nobody 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.150: Verifying against: FP1-00000000-2-00000000-nobody 383s (process:1926): libfprint-device-DEBUG: 00:53:52.150: Device reported verify result 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.150: [egismoc] IDENTIFY_STATES entering state 7 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.150: Execute command and get response 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.150: Get check bytes 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.150: [egismoc] CMD_STATES entering state 0 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.151: [egismoc] CMD_STATES entering state 1 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.151: Command receive callback 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.151: [egismoc] CMD_STATES completed successfully 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.151: Task SSM next state callback 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.151: [egismoc] IDENTIFY_STATES entering state 8 383s (process:1926): libfprint-device-DEBUG: 00:53:52.151: Device reported verify completion 383s (process:1926): libfprint-device-DEBUG: 00:53:52.151: Device reported finger status change: FP_FINGER_STATUS_NONE 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.151: [egismoc] IDENTIFY_STATES completed successfully 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.151: Task SSM done 383s (process:1926): libfprint-device-DEBUG: 00:53:52.151: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 383s (process:1926): libfprint-device-DEBUG: 00:53:52.151: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 383s (process:1926): libfprint-device-DEBUG: 00:53:52.152: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.153: Identify or Verify 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.153: [egismoc] IDENTIFY_STATES entering state 0 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.153: Execute command and get response 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.153: Get check bytes 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.153: [egismoc] CMD_STATES entering state 0 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.153: [egismoc] CMD_STATES entering state 1 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.154: Command receive callback 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.154: [egismoc] CMD_STATES completed successfully 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.154: List callback 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.154: Device fingerprint 1: FP1-00000000-2-00000000-nobody 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.154: Number of currently enrolled fingerprints on the device is 1 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.154: [egismoc] IDENTIFY_STATES entering state 1 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.154: [egismoc] IDENTIFY_STATES entering state 2 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.154: Execute command and get response 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.154: Get check bytes 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.154: [egismoc] CMD_STATES entering state 0 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.155: [egismoc] CMD_STATES entering state 1 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.155: Command receive callback 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.155: [egismoc] CMD_STATES completed successfully 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.155: Task SSM next state callback 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.155: [egismoc] IDENTIFY_STATES entering state 3 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.155: Execute command and get response 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.155: Get check bytes 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.155: [egismoc] CMD_STATES entering state 0 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.156: [egismoc] CMD_STATES entering state 1 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.157: Command receive callback 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.157: [egismoc] CMD_STATES completed successfully 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.157: Task SSM next state callback 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.157: [egismoc] IDENTIFY_STATES entering state 4 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.157: Wait for finger on sensor 383s (process:1926): libfprint-device-DEBUG: 00:53:52.157: Device reported finger status change: FP_FINGER_STATUS_NEEDED 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.157: Finger on sensor callback 383s (process:1926): libfprint-device-DEBUG: 00:53:52.157: Device reported finger status change: FP_FINGER_STATUS_PRESENT 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.157: [egismoc] IDENTIFY_STATES entering state 5 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.157: Execute command and get response 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.157: Get check bytes 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.157: [egismoc] CMD_STATES entering state 0 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.158: [egismoc] CMD_STATES entering state 1 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.159: Command receive callback 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.159: [egismoc] CMD_STATES completed successfully 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.159: Task SSM next state callback 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.159: [egismoc] IDENTIFY_STATES entering state 6 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.159: Get check command 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.159: Execute command and get response 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.159: Get check bytes 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.159: [egismoc] CMD_STATES entering state 0 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.159: [egismoc] CMD_STATES entering state 1 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.160: Command receive callback 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.160: [egismoc] CMD_STATES completed successfully 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.160: Identify check callback 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.160: Response suffix valid: yes 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.160: Identify successful for: FP1-00000000-2-00000000-nobody 383s (process:1926): libfprint-device-DEBUG: 00:53:52.160: Device reported identify result 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.160: [egismoc] IDENTIFY_STATES entering state 7 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.160: Execute command and get response 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.161: Get check bytes 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.161: [egismoc] CMD_STATES entering state 0 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.161: [egismoc] CMD_STATES entering state 1 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.162: Command receive callback 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.162: [egismoc] CMD_STATES completed successfully 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.162: Task SSM next state callback 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.162: [egismoc] IDENTIFY_STATES entering state 8 383s (process:1926): libfprint-device-DEBUG: 00:53:52.162: Device reported identify completion 383s (process:1926): libfprint-device-DEBUG: 00:53:52.162: Device reported finger status change: FP_FINGER_STATUS_NONE 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.162: [egismoc] IDENTIFY_STATES completed successfully 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.162: Task SSM done 383s (process:1926): libfprint-device-DEBUG: 00:53:52.162: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 383s (process:1926): libfprint-device-DEBUG: 00:53:52.162: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 383s (process:1926): libfprint-device-DEBUG: 00:53:52.163: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.163: Enroll 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.163: [egismoc] ENROLL_STATES entering state 0 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.163: Execute command and get response 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.163: Get check bytes 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.163: [egismoc] CMD_STATES entering state 0 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.164: [egismoc] CMD_STATES entering state 1 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.165: Command receive callback 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.165: [egismoc] CMD_STATES completed successfully 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.165: List callback 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.165: Device fingerprint 1: FP1-00000000-2-00000000-nobody 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.165: Number of currently enrolled fingerprints on the device is 1 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.165: [egismoc] ENROLL_STATES entering state 1 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.165: [egismoc] ENROLL_STATES entering state 2 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.165: Execute command and get response 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.165: Get check bytes 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.165: [egismoc] CMD_STATES entering state 0 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.165: [egismoc] CMD_STATES entering state 1 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.166: Command receive callback 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.166: [egismoc] CMD_STATES completed successfully 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.166: Task SSM next state callback 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.166: [egismoc] ENROLL_STATES entering state 3 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.166: Execute command and get response 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.166: Get check bytes 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.166: [egismoc] CMD_STATES entering state 0 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.167: [egismoc] CMD_STATES entering state 1 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.168: Command receive callback 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.168: [egismoc] CMD_STATES completed successfully 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.168: Task SSM next state callback 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.168: [egismoc] ENROLL_STATES entering state 4 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.168: Wait for finger on sensor 383s (process:1926): libfprint-device-DEBUG: 00:53:52.168: Device reported finger status change: FP_FINGER_STATUS_NEEDED 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.169: Finger on sensor callback 383s (process:1926): libfprint-device-DEBUG: 00:53:52.169: Device reported finger status change: FP_FINGER_STATUS_PRESENT 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.169: [egismoc] ENROLL_STATES entering state 5 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.169: Execute command and get response 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.169: Get check bytes 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.169: [egismoc] CMD_STATES entering state 0 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.169: [egismoc] CMD_STATES entering state 1 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.170: Command receive callback 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.170: [egismoc] CMD_STATES completed successfully 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.170: Task SSM next state callback 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.170: [egismoc] ENROLL_STATES entering state 6 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.170: Get check command 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.170: Execute command and get response 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.170: Get check bytes 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.170: [egismoc] CMD_STATES entering state 0 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.171: [egismoc] CMD_STATES entering state 1 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.171: Command receive callback 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.171: [egismoc] CMD_STATES completed successfully 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.171: Enroll check callback 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.171: Response suffix valid: NO 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.171: [egismoc] SSM ENROLL_STATES failed in state 6 with error: This finger has already enrolled, please try a different finger 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.171: [egismoc] ENROLL_STATES completed with error: This finger has already enrolled, please try a different finger 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.171: Task SSM done 383s (process:1926): libfprint-device-DEBUG: 00:53:52.171: Device reported generic error (This finger has already enrolled, please try a different finger) during action; action was: FPI_DEVICE_ACTION_ENROLL 383s (process:1926): libfprint-device-DEBUG: 00:53:52.171: Device reported enroll completion 383s (process:1926): libfprint-device-DEBUG: 00:53:52.171: Device reported finger status change: FP_FINGER_STATUS_NONE 383s (process:1926): libfprint-device-DEBUG: 00:53:52.171: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 383s (process:1926): libfprint-device-DEBUG: 00:53:52.171: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.172: List 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.172: [egismoc] LIST_STATES entering state 0 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.172: Execute command and get response 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.172: Get check bytes 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.172: [egismoc] CMD_STATES entering state 0 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.173: [egismoc] CMD_STATES entering state 1 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.174: Command receive callback 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.174: [egismoc] CMD_STATES completed successfully 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.174: List callback 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.174: Device fingerprint 1: FP1-00000000-2-00000000-nobody 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.174: Number of currently enrolled fingerprints on the device is 1 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.174: [egismoc] LIST_STATES entering state 1 383s (process:1926): libfprint-device-DEBUG: 00:53:52.174: Device reported listing completion 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.174: [egismoc] LIST_STATES completed successfully 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.174: Task SSM done 383s (process:1926): libfprint-device-DEBUG: 00:53:52.174: Completing action FPI_DEVICE_ACTION_LIST in idle! 383s (process:1926): libfprint-device-DEBUG: 00:53:52.174: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 383s (process:1926): libfprint-device-DEBUG: 00:53:52.174: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.174: Enroll 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.174: [egismoc] ENROLL_STATES entering state 0 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.174: Execute command and get response 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.174: Get check bytes 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.174: [egismoc] CMD_STATES entering state 0 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.175: [egismoc] CMD_STATES entering state 1 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.175: Command receive callback 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.175: [egismoc] CMD_STATES completed successfully 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.175: List callback 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.175: Device fingerprint 1: FP1-00000000-2-00000000-nobody 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.175: Number of currently enrolled fingerprints on the device is 1 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.175: [egismoc] ENROLL_STATES entering state 1 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.175: [egismoc] ENROLL_STATES entering state 2 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.175: Execute command and get response 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.175: Get check bytes 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.175: [egismoc] CMD_STATES entering state 0 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.176: [egismoc] CMD_STATES entering state 1 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.177: Command receive callback 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.177: [egismoc] CMD_STATES completed successfully 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.177: Task SSM next state callback 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.177: [egismoc] ENROLL_STATES entering state 3 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.177: Execute command and get response 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.177: Get check bytes 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.177: [egismoc] CMD_STATES entering state 0 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.177: [egismoc] CMD_STATES entering state 1 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.178: Command receive callback 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.178: [egismoc] CMD_STATES completed successfully 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.178: Task SSM next state callback 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.178: [egismoc] ENROLL_STATES entering state 4 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.178: Wait for finger on sensor 383s (process:1926): libfprint-device-DEBUG: 00:53:52.178: Device reported finger status change: FP_FINGER_STATUS_NEEDED 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.179: Finger on sensor callback 383s (process:1926): libfprint-device-DEBUG: 00:53:52.179: Device reported finger status change: FP_FINGER_STATUS_PRESENT 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.179: [egismoc] ENROLL_STATES entering state 5 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.179: Execute command and get response 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.179: Get check bytes 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.179: [egismoc] CMD_STATES entering state 0 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.179: [egismoc] CMD_STATES entering state 1 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.180: Command receive callback 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.180: [egismoc] CMD_STATES completed successfully 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.180: Task SSM next state callback 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.180: [egismoc] ENROLL_STATES entering state 6 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.180: Get check command 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.180: Execute command and get response 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.180: Get check bytes 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.180: [egismoc] CMD_STATES entering state 0 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.180: [egismoc] CMD_STATES entering state 1 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.181: Command receive callback 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.181: [egismoc] CMD_STATES completed successfully 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.181: Enroll check callback 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.181: Response suffix valid: yes 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.181: [egismoc] ENROLL_STATES entering state 7 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.181: Execute command and get response 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.181: Get check bytes 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.181: [egismoc] CMD_STATES entering state 0 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.182: [egismoc] CMD_STATES entering state 1 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.182: Command receive callback 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.182: [egismoc] CMD_STATES completed successfully 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.182: Task SSM next state callback 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.182: [egismoc] ENROLL_STATES entering state 8 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.182: Execute command and get response 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.182: Get check bytes 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.182: [egismoc] CMD_STATES entering state 0 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.183: [egismoc] CMD_STATES entering state 1 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.184: Command receive callback 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.184: [egismoc] CMD_STATES completed successfully 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.184: Task SSM next state callback 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.184: [egismoc] ENROLL_STATES entering state 9 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.184: Execute command and get response 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.184: Get check bytes 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.184: [egismoc] CMD_STATES entering state 0 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.184: [egismoc] CMD_STATES entering state 1 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.185: Command receive callback 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.185: [egismoc] CMD_STATES completed successfully 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.185: Task SSM next state callback 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.185: [egismoc] ENROLL_STATES entering state 10 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.185: Wait for finger on sensor 383s (process:1926): libfprint-device-DEBUG: 00:53:52.185: Device reported finger status change: FP_FINGER_STATUS_NEEDED 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.185: Finger on sensor callback 383s (process:1926): libfprint-device-DEBUG: 00:53:52.185: Device reported finger status change: FP_FINGER_STATUS_PRESENT 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.185: [egismoc] ENROLL_STATES entering state 11 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.186: Execute command and get response 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.186: Get check bytes 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.186: [egismoc] CMD_STATES entering state 0 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.186: [egismoc] CMD_STATES entering state 1 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.187: Command receive callback 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.187: [egismoc] CMD_STATES completed successfully 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.187: Read capture callback 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.187: Response prefix valid: yes 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.187: Response suffix valid: yes 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.187: Partial capture successful. Please touch the sensor again (1/20) 383s (process:1926): libfprint-device-DEBUG: 00:53:52.187: Device reported enroll progress, reported 1 of 20 have been completed 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.187: [egismoc] ENROLL_STATES entering state 8 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.187: Execute command and get response 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.187: Get check bytes 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.187: [egismoc] CMD_STATES entering state 0 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.188: [egismoc] CMD_STATES entering state 1 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.188: Command receive callback 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.188: [egismoc] CMD_STATES completed successfully 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.188: Task SSM next state callback 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.188: [egismoc] ENROLL_STATES entering state 9 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.188: Execute command and get response 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.188: Get check bytes 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.188: [egismoc] CMD_STATES entering state 0 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.189: [egismoc] CMD_STATES entering state 1 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.189: Command receive callback 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.189: [egismoc] CMD_STATES completed successfully 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.189: Task SSM next state callback 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.189: [egismoc] ENROLL_STATES entering state 10 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.189: Wait for finger on sensor 383s (process:1926): libfprint-device-DEBUG: 00:53:52.189: Device reported finger status change: FP_FINGER_STATUS_NEEDED 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.190: Finger on sensor callback 383s (process:1926): libfprint-device-DEBUG: 00:53:52.190: Device reported finger status change: FP_FINGER_STATUS_PRESENT 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.190: [egismoc] ENROLL_STATES entering state 11 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.190: Execute command and get response 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.190: Get check bytes 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.190: [egismoc] CMD_STATES entering state 0 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.191: [egismoc] CMD_STATES entering state 1 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.191: Command receive callback 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.191: [egismoc] CMD_STATES completed successfully 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.191: Read capture callback 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.191: Response prefix valid: yes 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.191: Response suffix valid: yes 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.191: Partial capture successful. Please touch the sensor again (2/20) 383s (process:1926): libfprint-device-DEBUG: 00:53:52.191: Device reported enroll progress, reported 2 of 20 have been completed 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.191: [egismoc] ENROLL_STATES entering state 8 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.192: Execute command and get response 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.192: Get check bytes 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.192: [egismoc] CMD_STATES entering state 0 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.192: [egismoc] CMD_STATES entering state 1 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.193: Command receive callback 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.193: [egismoc] CMD_STATES completed successfully 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.193: Task SSM next state callback 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.193: [egismoc] ENROLL_STATES entering state 9 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.193: Execute command and get response 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.193: Get check bytes 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.193: [egismoc] CMD_STATES entering state 0 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.193: [egismoc] CMD_STATES entering state 1 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.194: Command receive callback 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.194: [egismoc] CMD_STATES completed successfully 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.194: Task SSM next state callback 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.194: [egismoc] ENROLL_STATES entering state 10 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.194: Wait for finger on sensor 383s (process:1926): libfprint-device-DEBUG: 00:53:52.194: Device reported finger status change: FP_FINGER_STATUS_NEEDED 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.195: Finger on sensor callback 383s (process:1926): libfprint-device-DEBUG: 00:53:52.195: Device reported finger status change: FP_FINGER_STATUS_PRESENT 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.195: [egismoc] ENROLL_STATES entering state 11 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.195: Execute command and get response 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.195: Get check bytes 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.195: [egismoc] CMD_STATES entering state 0 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.195: [egismoc] CMD_STATES entering state 1 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.196: Command receive callback 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.196: [egismoc] CMD_STATES completed successfully 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.196: Read capture callback 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.196: Response prefix valid: yes 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.196: Response suffix valid: yes 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.196: Partial capture successful. Please touch the sensor again (3/20) 383s (process:1926): libfprint-device-DEBUG: 00:53:52.196: Device reported enroll progress, reported 3 of 20 have been completed 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.196: [egismoc] ENROLL_STATES entering state 8 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.196: Execute command and get response 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.196: Get check bytes 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.196: [egismoc] CMD_STATES entering state 0 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.197: [egismoc] CMD_STATES entering state 1 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.197: Command receive callback 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.197: [egismoc] CMD_STATES completed successfully 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.197: Task SSM next state callback 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.197: [egismoc] ENROLL_STATES entering state 9 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.197: Execute command and get response 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.197: Get check bytes 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.197: [egismoc] CMD_STATES entering state 0 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.198: [egismoc] CMD_STATES entering state 1 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.198: Command receive callback 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.198: [egismoc] CMD_STATES completed successfully 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.198: Task SSM next state callback 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.199: [egismoc] ENROLL_STATES entering state 10 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.199: Wait for finger on sensor 383s (process:1926): libfprint-device-DEBUG: 00:53:52.199: Device reported finger status change: FP_FINGER_STATUS_NEEDED 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.199: Finger on sensor callback 383s (process:1926): libfprint-device-DEBUG: 00:53:52.199: Device reported finger status change: FP_FINGER_STATUS_PRESENT 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.199: [egismoc] ENROLL_STATES entering state 11 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.199: Execute command and get response 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.199: Get check bytes 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.199: [egismoc] CMD_STATES entering state 0 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.200: [egismoc] CMD_STATES entering state 1 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.200: Command receive callback 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.200: [egismoc] CMD_STATES completed successfully 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.200: Read capture callback 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.200: Response prefix valid: yes 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.200: Response suffix valid: yes 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.200: Partial capture successful. Please touch the sensor again (4/20) 383s (process:1926): libfprint-device-DEBUG: 00:53:52.200: Device reported enroll progress, reported 4 of 20 have been completed 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.201: [egismoc] ENROLL_STATES entering state 8 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.201: Execute command and get response 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.201: Get check bytes 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.201: [egismoc] CMD_STATES entering state 0 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.201: [egismoc] CMD_STATES entering state 1 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.202: Command receive callback 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.202: [egismoc] CMD_STATES completed successfully 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.202: Task SSM next state callback 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.202: [egismoc] ENROLL_STATES entering state 9 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.202: Execute command and get response 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.202: Get check bytes 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.202: [egismoc] CMD_STATES entering state 0 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.202: [egismoc] CMD_STATES entering state 1 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.203: Command receive callback 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.203: [egismoc] CMD_STATES completed successfully 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.203: Task SSM next state callback 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.203: [egismoc] ENROLL_STATES entering state 10 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.203: Wait for finger on sensor 383s (process:1926): libfprint-device-DEBUG: 00:53:52.203: Device reported finger status change: FP_FINGER_STATUS_NEEDED 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.204: Finger on sensor callback 383s (process:1926): libfprint-device-DEBUG: 00:53:52.204: Device reported finger status change: FP_FINGER_STATUS_PRESENT 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.204: [egismoc] ENROLL_STATES entering state 11 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.204: Execute command and get response 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.204: Get check bytes 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.204: [egismoc] CMD_STATES entering state 0 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.204: [egismoc] CMD_STATES entering state 1 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.205: Command receive callback 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.205: [egismoc] CMD_STATES completed successfully 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.205: Read capture callback 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.205: Response prefix valid: yes 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.205: Response suffix valid: yes 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.205: Partial capture successful. Please touch the sensor again (5/20) 383s (process:1926): libfprint-device-DEBUG: 00:53:52.205: Device reported enroll progress, reported 5 of 20 have been completed 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.205: [egismoc] ENROLL_STATES entering state 8 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.205: Execute command and get response 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.205: Get check bytes 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.205: [egismoc] CMD_STATES entering state 0 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.206: [egismoc] CMD_STATES entering state 1 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.207: Command receive callback 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.207: [egismoc] CMD_STATES completed successfully 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.207: Task SSM next state callback 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.207: [egismoc] ENROLL_STATES entering state 9 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.207: Execute command and get response 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.207: Get check bytes 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.207: [egismoc] CMD_STATES entering state 0 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.208: [egismoc] CMD_STATES entering state 1 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.209: Command receive callback 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.209: [egismoc] CMD_STATES completed successfully 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.209: Task SSM next state callback 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.209: [egismoc] ENROLL_STATES entering state 10 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.209: Wait for finger on sensor 383s (process:1926): libfprint-device-DEBUG: 00:53:52.209: Device reported finger status change: FP_FINGER_STATUS_NEEDED 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.209: Finger on sensor callback 383s (process:1926): libfprint-device-DEBUG: 00:53:52.209: Device reported finger status change: FP_FINGER_STATUS_PRESENT 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.209: [egismoc] ENROLL_STATES entering state 11 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.209: Execute command and get response 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.209: Get check bytes 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.209: [egismoc] CMD_STATES entering state 0 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.210: [egismoc] CMD_STATES entering state 1 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.211: Command receive callback 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.211: [egismoc] CMD_STATES completed successfully 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.211: Read capture callback 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.211: Response prefix valid: yes 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.211: Response suffix valid: yes 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.211: Partial capture successful. Please touch the sensor again (6/20) 383s (process:1926): libfprint-device-DEBUG: 00:53:52.211: Device reported enroll progress, reported 6 of 20 have been completed 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.211: [egismoc] ENROLL_STATES entering state 8 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.211: Execute command and get response 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.211: Get check bytes 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.211: [egismoc] CMD_STATES entering state 0 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.211: [egismoc] CMD_STATES entering state 1 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.212: Command receive callback 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.212: [egismoc] CMD_STATES completed successfully 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.212: Task SSM next state callback 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.212: [egismoc] ENROLL_STATES entering state 9 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.212: Execute command and get response 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.212: Get check bytes 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.212: [egismoc] CMD_STATES entering state 0 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.213: [egismoc] CMD_STATES entering state 1 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.213: Command receive callback 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.213: [egismoc] CMD_STATES completed successfully 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.213: Task SSM next state callback 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.213: [egismoc] ENROLL_STATES entering state 10 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.213: Wait for finger on sensor 383s (process:1926): libfprint-device-DEBUG: 00:53:52.213: Device reported finger status change: FP_FINGER_STATUS_NEEDED 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.214: Finger on sensor callback 383s (process:1926): libfprint-device-DEBUG: 00:53:52.214: Device reported finger status change: FP_FINGER_STATUS_PRESENT 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.214: [egismoc] ENROLL_STATES entering state 11 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.214: Execute command and get response 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.214: Get check bytes 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.214: [egismoc] CMD_STATES entering state 0 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.214: [egismoc] CMD_STATES entering state 1 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.215: Command receive callback 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.215: [egismoc] CMD_STATES completed successfully 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.215: Read capture callback 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.215: Response prefix valid: yes 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.215: Response suffix valid: yes 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.215: Partial capture successful. Please touch the sensor again (7/20) 383s (process:1926): libfprint-device-DEBUG: 00:53:52.215: Device reported enroll progress, reported 7 of 20 have been completed 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.215: [egismoc] ENROLL_STATES entering state 8 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.215: Execute command and get response 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.215: Get check bytes 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.215: [egismoc] CMD_STATES entering state 0 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.216: [egismoc] CMD_STATES entering state 1 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.217: Command receive callback 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.217: [egismoc] CMD_STATES completed successfully 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.217: Task SSM next state callback 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.217: [egismoc] ENROLL_STATES entering state 9 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.217: Execute command and get response 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.217: Get check bytes 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.217: [egismoc] CMD_STATES entering state 0 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.217: [egismoc] CMD_STATES entering state 1 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.218: Command receive callback 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.218: [egismoc] CMD_STATES completed successfully 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.218: Task SSM next state callback 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.218: [egismoc] ENROLL_STATES entering state 10 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.218: Wait for finger on sensor 383s (process:1926): libfprint-device-DEBUG: 00:53:52.218: Device reported finger status change: FP_FINGER_STATUS_NEEDED 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.219: Finger on sensor callback 383s (process:1926): libfprint-device-DEBUG: 00:53:52.219: Device reported finger status change: FP_FINGER_STATUS_PRESENT 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.219: [egismoc] ENROLL_STATES entering state 11 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.219: Execute command and get response 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.219: Get check bytes 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.219: [egismoc] CMD_STATES entering state 0 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.219: [egismoc] CMD_STATES entering state 1 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.220: Command receive callback 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.220: [egismoc] CMD_STATES completed successfully 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.220: Read capture callback 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.220: Response prefix valid: yes 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.220: Response suffix valid: NO 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.220: Response prefix valid: yes 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.220: Response suffix valid: yes 383s (process:1926): libfprint-device-DEBUG: 00:53:52.220: Device reported enroll progress, reported 7 of 20 have been completed 383s listing - device should have prints 383s clear device storage 383s clear done 383s listing - device should be empty 383s enrolling 383s finger status: 383s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xefc8f628 (FpiDeviceEgisMoc at 0x15d2810)>, 1, , None, None) 383s finger status: 383s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xefc8f628 (FpiDeviceEgisMoc at 0x15d2810)>, 2, , None, None) 383s finger status: 383s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xefc8f628 (FpiDeviceEgisMoc at 0x15d2810)>, 3, , None, None) 383s finger status: 383s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xefc8f628 (FpiDeviceEgisMoc at 0x15d2810)>, 4, , None, None) 383s finger status: 383s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xefc8f628 (FpiDeviceEgisMoc at 0x15d2810)>, 5, , None, None) 383s finger status: 383s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xefc8f628 (FpiDeviceEgisMoc at 0x15d2810)>, 6, , None, None) 383s finger status: 383s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xefc8f628 (FpiDeviceEgisMoc at 0x15d2810)>, 7, , None, None) 383s finger status: 383s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xefc8f628 (FpiDeviceEgisMoc at 0x15d2810)>, 7, None, None, GLib.Error('The finger was not centered properly, please try again.', 'fp - device - retry - quark', 2)) 383s finger status: 383s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xefc8f628 (FpiDeviceEgisMoc at 0x15d2810)>, 8, , None, None) 383s finger status: 383s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xefc8f628 (FpiDeviceEgisMoc at 0x15d2810)>, 8, None, None, GLib.Error('The finger was not centered properly, please try again.', 'fp - device - retry - quark', 2)) 383s finger status: 383s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xefc8f628 (FpiDeviceEgisMoc at 0x15d2810)>, 9, , None, None) 383s finger status: 383s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xefc8f628 (FpiDeviceEgisMoc at 0x15d2810)>, 10, , None, None) 383s finger status: 383s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xefc8f628 (FpiDeviceEgisMoc at 0x15d2810)>, 11, , None, None) 383s finger status: 383s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xefc8f628 (FpiDeviceEgisMoc at 0x15d2810)>, 12, , None, None) 383s finger status: 383s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xefc8f628 (FpiDeviceEgisMoc at 0x15d2810)>, 13, , None, None) 383s finger status: 383s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xefc8f628 (FpiDeviceEgisMoc at 0x15d2810)>, 14, , None, None) 383s finger status: 383s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xefc8f628 (FpiDeviceEgisMoc at 0x15d2810)>, 15, , None, None) 383s finger status: 383s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xefc8f628 (FpiDeviceEgisMoc at 0x15d2810)>, 16, , None, None) 383s finger status: 383s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xefc8f628 (FpiDeviceEgisMoc at 0x15d2810)>, 17, , None, None) 383s finger status: 383s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xefc8f628 (FpiDeviceEgisMoc at 0x15d2810)>, 18, , None, None) 383s finger status: 383s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xefc8f628 (FpiDeviceEgisMoc at 0x15d2810)>, 19, , None, None) 383s finger status: 383s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xefc8f628 (FpiDeviceEgisMoc at 0x15d2810)>, 20, , None, None) 383s enroll done 383s listing - device should have 1 print 383s verifying 383s verify done 383s async identifying 383s indentification_done: 383s try to enroll duplicate 383s duplicate enroll attempt done 383s listing - device should still only have 1 print 383s enroll new finger 383s finger status: 383s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xefc8f628 (FpiDeviceEgisMoc at 0x15d2810)>, 1, , None, None) 383s finger status: 383s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xefc8f628 (FpiDeviceEgisMoc at 0x15d2810)>, 2, , None, None) 383s finger status: 383s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xefc8f628 (FpiDeviceEgisMoc at 0x15d2810)>, 3, , None, None) 383s finger status: 383s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xefc8f628 (FpiDeviceEgisMoc at 0x15d2810)>, 4, , None, None) 383s finger status: 383s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xefc8f628 (FpiDeviceEgisMoc at 0x15d2810)>, 5, , None, None) 383s finger status: 383s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xefc8f628 (FpiDeviceEgisMoc at 0x15d2810)>, 6, , None, None) 383s finger status: 383s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xefc8f628 (FpiDeviceEgisMoc at 0x15d2810)>, 7, , None, None) 383s finger status: 383s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xefc8f628 (FpiDeviceEgisMoc at 0x15d2810)>, 7, None, None, GLib.Error('The finger was not centered properly, please try again.', 'fp - device - retry - quark', 2))(process:1926): libfprint-SSM-DEBUG: 00:53:52.220: [egismoc] ENROLL_STATES entering state 8 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.220: Execute command and get response 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.220: Get check bytes 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.220: [egismoc] CMD_STATES entering state 0 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.221: [egismoc] CMD_STATES entering state 1 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.222: Command receive callback 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.222: [egismoc] CMD_STATES completed successfully 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.222: Task SSM next state callback 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.222: [egismoc] ENROLL_STATES entering state 9 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.222: Execute command and get response 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.222: Get check bytes 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.222: [egismoc] CMD_STATES entering state 0 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.222: [egismoc] CMD_STATES entering state 1 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.223: Command receive callback 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.223: [egismoc] CMD_STATES completed successfully 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.223: Task SSM next state callback 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.223: [egismoc] ENROLL_STATES entering state 10 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.223: Wait for finger on sensor 383s (process:1926): libfprint-device-DEBUG: 00:53:52.223: Device reported finger status change: FP_FINGER_STATUS_NEEDED 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.224: Finger on sensor callback 383s (process:1926): libfprint-device-DEBUG: 00:53:52.224: Device reported finger status change: FP_FINGER_STATUS_PRESENT 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.224: [egismoc] ENROLL_STATES entering state 11 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.224: Execute command and get response 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.224: Get check bytes 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.224: [egismoc] CMD_STATES entering state 0 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.224: [egismoc] CMD_STATES entering state 1 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.225: Command receive callback 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.225: [egismoc] CMD_STATES completed successfully 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.225: Read capture callback 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.225: Response prefix valid: yes 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.225: Response suffix valid: yes 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.225: Partial capture successful. Please touch the sensor again (8/20) 383s (process:1926): libfprint-device-DEBUG: 00:53:52.225: Device reported enroll progress, reported 8 of 20 have been completed 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.225: [egismoc] ENROLL_STATES entering state 8 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.225: Execute command and get response 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.225: Get check bytes 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.225: [egismoc] CMD_STATES entering state 0 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.226: [egismoc] CMD_STATES entering state 1 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.227: Command receive callback 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.227: [egismoc] CMD_STATES completed successfully 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.227: Task SSM next state callback 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.227: [egismoc] ENROLL_STATES entering state 9 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.227: Execute command and get response 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.227: Get check bytes 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.227: [egismoc] CMD_STATES entering state 0 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.228: [egismoc] CMD_STATES entering state 1 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.228: Command receive callback 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.228: [egismoc] CMD_STATES completed successfully 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.228: Task SSM next state callback 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.228: [egismoc] ENROLL_STATES entering state 10 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.228: Wait for finger on sensor 383s (process:1926): libfprint-device-DEBUG: 00:53:52.228: Device reported finger status change: FP_FINGER_STATUS_NEEDED 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.229: Finger on sensor callback 383s (process:1926): libfprint-device-DEBUG: 00:53:52.229: Device reported finger status change: FP_FINGER_STATUS_PRESENT 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.229: [egismoc] ENROLL_STATES entering state 11 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.229: Execute command and get response 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.229: Get check bytes 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.229: [egismoc] CMD_STATES entering state 0 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.229: [egismoc] CMD_STATES entering state 1 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.230: Command receive callback 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.230: [egismoc] CMD_STATES completed successfully 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.230: Read capture callback 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.230: Response prefix valid: yes 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.230: Response suffix valid: yes 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.230: Partial capture successful. Please touch the sensor again (9/20) 383s (process:1926): libfprint-device-DEBUG: 00:53:52.230: Device reported enroll progress, reported 9 of 20 have been completed 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.230: [egismoc] ENROLL_STATES entering state 8 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.230: Execute command and get response 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.230: Get check bytes 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.230: [egismoc] CMD_STATES entering state 0 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.231: [egismoc] CMD_STATES entering state 1 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.232: Command receive callback 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.232: [egismoc] CMD_STATES completed successfully 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.232: Task SSM next state callback 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.232: [egismoc] ENROLL_STATES entering state 9 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.232: Execute command and get response 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.232: Get check bytes 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.232: [egismoc] CMD_STATES entering state 0 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.232: [egismoc] CMD_STATES entering state 1 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.233: Command receive callback 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.233: [egismoc] CMD_STATES completed successfully 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.233: Task SSM next state callback 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.233: [egismoc] ENROLL_STATES entering state 10 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.233: Wait for finger on sensor 383s (process:1926): libfprint-device-DEBUG: 00:53:52.233: Device reported finger status change: FP_FINGER_STATUS_NEEDED 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.234: Finger on sensor callback 383s (process:1926): libfprint-device-DEBUG: 00:53:52.234: Device reported finger status change: FP_FINGER_STATUS_PRESENT 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.234: [egismoc] ENROLL_STATES entering state 11 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.234: Execute command and get response 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.234: Get check bytes 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.234: [egismoc] CMD_STATES entering state 0 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.234: [egismoc] CMD_STATES entering state 1 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.235: Command receive callback 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.235: [egismoc] CMD_STATES completed successfully 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.235: Read capture callback 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.235: Response prefix valid: yes 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.235: Response suffix valid: NO 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.235: Response prefix valid: yes 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.235: Response suffix valid: yes 383s (process:1926): libfprint-device-DEBUG: 00:53:52.235: Device reported enroll progress, reported 9 of 20 have been completed 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.235: [egismoc] ENROLL_STATES entering state 8 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.235: Execute command and get response 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.235: Get check bytes 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.235: [egismoc] CMD_STATES entering state 0 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.236: [egismoc] CMD_STATES entering state 1 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.237: Command receive callback 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.237: [egismoc] CMD_STATES completed successfully 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.237: Task SSM next state callback 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.237: [egismoc] ENROLL_STATES entering state 9 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.237: Execute command and get response 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.237: Get check bytes 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.237: [egismoc] CMD_STATES entering state 0 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.237: [egismoc] CMD_STATES entering state 1 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.238: Command receive callback 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.238: [egismoc] CMD_STATES completed successfully 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.238: Task SSM next state callback 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.238: [egismoc] ENROLL_STATES entering state 10 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.238: Wait for finger on sensor 383s (process:1926): libfprint-device-DEBUG: 00:53:52.238: Device reported finger status change: FP_FINGER_STATUS_NEEDED 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.239: Finger on sensor callback 383s (process:1926): libfprint-device-DEBUG: 00:53:52.239: Device reported finger status change: FP_FINGER_STATUS_PRESENT 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.239: [egismoc] ENROLL_STATES entering state 11 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.239: Execute command and get response 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.239: Get check bytes 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.239: [egismoc] CMD_STATES entering state 0 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.239: [egismoc] CMD_STATES entering state 1 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.240: Command receive callback 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.240: [egismoc] CMD_STATES completed successfully 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.240: Read capture callback 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.240: Response prefix valid: yes 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.240: Response suffix valid: yes 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.240: Partial capture successful. Please touch the sensor again (10/20) 383s (process:1926): libfprint-device-DEBUG: 00:53:52.240: Device reported enroll progress, reported 10 of 20 have been completed 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.240: [egismoc] ENROLL_STATES entering state 8 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.240: Execute command and get response 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.240: Get check bytes 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.240: [egismoc] CMD_STATES entering state 0 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.241: [egismoc] CMD_STATES entering state 1 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.242: Command receive callback 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.242: [egismoc] CMD_STATES completed successfully 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.242: Task SSM next state callback 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.242: [egismoc] ENROLL_STATES entering state 9 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.242: Execute command and get response 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.242: Get check bytes 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.242: [egismoc] CMD_STATES entering state 0 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.242: [egismoc] CMD_STATES entering state 1 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.243: Command receive callback 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.243: [egismoc] CMD_STATES completed successfully 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.243: Task SSM next state callback 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.243: [egismoc] ENROLL_STATES entering state 10 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.243: Wait for finger on sensor 383s (process:1926): libfprint-device-DEBUG: 00:53:52.243: Device reported finger status change: FP_FINGER_STATUS_NEEDED 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.244: Finger on sensor callback 383s (process:1926): libfprint-device-DEBUG: 00:53:52.244: Device reported finger status change: FP_FINGER_STATUS_PRESENT 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.244: [egismoc] ENROLL_STATES entering state 11 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.244: Execute command and get response 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.244: Get check bytes 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.244: [egismoc] CMD_STATES entering state 0 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.244: [egismoc] CMD_STATES entering state 1 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.245: Command receive callback 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.245: [egismoc] CMD_STATES completed successfully 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.245: Read capture callback 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.245: Response prefix valid: yes 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.245: Response suffix valid: yes 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.245: Partial capture successful. Please touch the sensor again (11/20) 383s (process:1926): libfprint-device-DEBUG: 00:53:52.245: Device reported enroll progress, reported 11 of 20 have been completed 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.245: [egismoc] ENROLL_STATES entering state 8 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.245: Execute command and get response 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.245: Get check bytes 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.245: [egismoc] CMD_STATES entering state 0 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.246: [egismoc] CMD_STATES entering state 1 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.246: Command receive callback 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.246: [egismoc] CMD_STATES completed successfully 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.246: Task SSM next state callback 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.246: [egismoc] ENROLL_STATES entering state 9 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.246: Execute command and get response 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.246: Get check bytes 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.246: [egismoc] CMD_STATES entering state 0 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.247: [egismoc] CMD_STATES entering state 1 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.247: Command receive callback 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.247: [egismoc] CMD_STATES completed successfully 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.247: Task SSM next state callback 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.248: [egismoc] ENROLL_STATES entering state 10 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.248: Wait for finger on sensor 383s (process:1926): libfprint-device-DEBUG: 00:53:52.248: Device reported finger status change: FP_FINGER_STATUS_NEEDED 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.248: Finger on sensor callback 383s (process:1926): libfprint-device-DEBUG: 00:53:52.248: Device reported finger status change: FP_FINGER_STATUS_PRESENT 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.248: [egismoc] ENROLL_STATES entering state 11 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.248: Execute command and get response 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.248: Get check bytes 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.248: [egismoc] CMD_STATES entering state 0 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.249: [egismoc] CMD_STATES entering state 1 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.249: Command receive callback 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.249: [egismoc] CMD_STATES completed successfully 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.249: Read capture callback 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.249: Response prefix valid: yes 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.249: Response suffix valid: yes 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.249: Partial capture successful. Please touch the sensor again (12/20) 383s (process:1926): libfprint-device-DEBUG: 00:53:52.249: Device reported enroll progress, reported 12 of 20 have been completed 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.249: [egismoc] ENROLL_STATES entering state 8 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.249: Execute command and get response 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.249: Get check bytes 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.249: [egismoc] CMD_STATES entering state 0 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.250: [egismoc] CMD_STATES entering state 1 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.251: Command receive callback 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.251: [egismoc] CMD_STATES completed successfully 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.251: Task SSM next state callback 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.251: [egismoc] ENROLL_STATES entering state 9 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.251: Execute command and get response 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.251: Get check bytes 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.251: [egismoc] CMD_STATES entering state 0 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.251: [egismoc] CMD_STATES entering state 1 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.252: Command receive callback 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.252: [egismoc] CMD_STATES completed successfully 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.252: Task SSM next state callback 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.252: [egismoc] ENROLL_STATES entering state 10 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.252: Wait for finger on sensor 383s (process:1926): libfprint-device-DEBUG: 00:53:52.252: Device reported finger status change: FP_FINGER_STATUS_NEEDED 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.253: Finger on sensor callback 383s (process:1926): libfprint-device-DEBUG: 00:53:52.253: Device reported finger status change: FP_FINGER_STATUS_PRESENT 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.253: [egismoc] ENROLL_STATES entering state 11 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.253: Execute command and get response 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.253: Get check bytes 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.253: [egismoc] CMD_STATES entering state 0 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.253: [egismoc] CMD_STATES entering state 1 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.254: Command receive callback 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.254: [egismoc] CMD_STATES completed successfully 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.254: Read capture callback 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.254: Response prefix valid: yes 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.254: Response suffix valid: yes 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.254: Partial capture successful. Please touch the sensor again (13/20) 383s (process:1926): libfprint-device-DEBUG: 00:53:52.254: Device reported enroll progress, reported 13 of 20 have been completed 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.254: [egismoc] ENROLL_STATES entering state 8 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.254: Execute command and get response 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.254: Get check bytes 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.254: [egismoc] CMD_STATES entering state 0 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.255: [egismoc] CMD_STATES entering state 1 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.255: Command receive callback 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.255: [egismoc] CMD_STATES completed successfully 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.255: Task SSM next state callback 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.256: [egismoc] ENROLL_STATES entering state 9 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.256: Execute command and get response 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.256: Get check bytes 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.256: [egismoc] CMD_STATES entering state 0 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.256: [egismoc] CMD_STATES entering state 1 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.257: Command receive callback 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.257: [egismoc] CMD_STATES completed successfully 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.257: Task SSM next state callback 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.257: [egismoc] ENROLL_STATES entering state 10 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.257: Wait for finger on sensor 383s (process:1926): libfprint-device-DEBUG: 00:53:52.257: Device reported finger status change: FP_FINGER_STATUS_NEEDED 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.258: Finger on sensor callback 383s (process:1926): libfprint-device-DEBUG: 00:53:52.258: Device reported finger status change: FP_FINGER_STATUS_PRESENT 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.258: [egismoc] ENROLL_STATES entering state 11 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.258: Execute command and get response 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.258: Get check bytes 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.258: [egismoc] CMD_STATES entering state 0 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.259: [egismoc] CMD_STATES entering state 1 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.259: Command receive callback 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.259: [egismoc] CMD_STATES completed successfully 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.259: Read capture callback 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.259: Response prefix valid: yes 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.259: Response suffix valid: yes 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.259: Partial capture successful. Please touch the sensor again (14/20) 383s (process:1926): libfprint-device-DEBUG: 00:53:52.259: Device reported enroll progress, reported 14 of 20 have been completed 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.260: [egismoc] ENROLL_STATES entering state 8 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.260: Execute command and get response 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.260: Get check bytes 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.260: [egismoc] CMD_STATES entering state 0 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.260: [egismoc] CMD_STATES entering state 1 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.261: Command receive callback 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.261: [egismoc] CMD_STATES completed successfully 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.261: Task SSM next state callback 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.261: [egismoc] ENROLL_STATES entering state 9 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.261: Execute command and get response 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.261: Get check bytes 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.261: [egismoc] CMD_STATES entering state 0 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.262: [egismoc] CMD_STATES entering state 1 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.262: Command receive callback 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.262: [egismoc] CMD_STATES completed successfully 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.262: Task SSM next state callback 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.262: [egismoc] ENROLL_STATES entering state 10 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.262: Wait for finger on sensor 383s (process:1926): libfprint-device-DEBUG: 00:53:52.262: Device reported finger status change: FP_FINGER_STATUS_NEEDED 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.263: Finger on sensor callback 383s (process:1926): libfprint-device-DEBUG: 00:53:52.263: Device reported finger status change: FP_FINGER_STATUS_PRESENT 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.263: [egismoc] ENROLL_STATES entering state 11 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.263: Execute command and get response 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.263: Get check bytes 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.263: [egismoc] CMD_STATES entering state 0 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.264: [egismoc] CMD_STATES entering state 1 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.264: Command receive callback 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.264: [egismoc] CMD_STATES completed successfully 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.264: Read capture callback 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.264: Response prefix valid: yes 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.264: Response suffix valid: yes 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.264: Partial capture successful. Please touch the sensor again (15/20) 383s (process:1926): libfprint-device-DEBUG: 00:53:52.264: Device reported enroll progress, reported 15 of 20 have been completed 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.265: [egismoc] ENROLL_STATES entering state 8 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.265: Execute command and get response 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.265: Get check bytes 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.265: [egismoc] CMD_STATES entering state 0 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.265: [egismoc] CMD_STATES entering state 1 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.266: Command receive callback 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.266: [egismoc] CMD_STATES completed successfully 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.266: Task SSM next state callback 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.266: [egismoc] ENROLL_STATES entering state 9 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.266: Execute command and get response 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.266: Get check bytes 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.266: [egismoc] CMD_STATES entering state 0 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.267: [egismoc] CMD_STATES entering state 1 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.267: Command receive callback 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.267: [egismoc] CMD_STATES completed successfully 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.267: Task SSM next state callback 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.267: [egismoc] ENROLL_STATES entering state 10 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.267: Wait for finger on sensor 383s (process:1926): libfprint-device-DEBUG: 00:53:52.267: Device reported finger status change: FP_FINGER_STATUS_NEEDED 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.268: Finger on sensor callback 383s (process:1926): libfprint-device-DEBUG: 00:53:52.268: Device reported finger status change: FP_FINGER_STATUS_PRESENT 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.268: [egismoc] ENROLL_STATES entering state 11 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.268: Execute command and get response 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.268: Get check bytes 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.268: [egismoc] CMD_STATES entering state 0 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.269: [egismoc] CMD_STATES entering state 1 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.269: Command receive callback 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.269: [egismoc] CMD_STATES completed successfully 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.269: Read capture callback 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.269: Response prefix valid: yes 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.269: Response suffix valid: yes 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.269: Partial capture successful. Please touch the sensor again (16/20) 383s (process:1926): libfprint-device-DEBUG: 00:53:52.269: Device reported enroll progress, reported 16 of 20 have been completed 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.270: [egismoc] ENROLL_STATES entering state 8 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.270: Execute command and get response 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.270: Get check bytes 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.270: [egismoc] CMD_STATES entering state 0 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.270: [egismoc] CMD_STATES entering state 1 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.271: Command receive callback 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.271: [egismoc] CMD_STATES completed successfully 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.271: Task SSM next state callback 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.271: [egismoc] ENROLL_STATES entering state 9 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.271: Execute command and get response 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.271: Get check bytes 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.271: [egismoc] CMD_STATES entering state 0 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.272: [egismoc] CMD_STATES entering state 1 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.272: Command receive callback 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.272: [egismoc] CMD_STATES completed successfully 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.272: Task SSM next state callback 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.272: [egismoc] ENROLL_STATES entering state 10 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.273: Wait for finger on sensor 383s (process:1926): libfprint-device-DEBUG: 00:53:52.273: Device reported finger status change: FP_FINGER_STATUS_NEEDED 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.273: Finger on sensor callback 383s (process:1926): libfprint-device-DEBUG: 00:53:52.273: Device reported finger status change: FP_FINGER_STATUS_PRESENT 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.273: [egismoc] ENROLL_STATES entering state 11 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.273: Execute command and get response 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.273: Get check bytes 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.273: [egismoc] CMD_STATES entering state 0 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.274: [egismoc] CMD_STATES entering state 1 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.274: Command receive callback 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.275: [egismoc] CMD_STATES completed successfully 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.275: Read capture callback 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.275: Response prefix valid: yes 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.275: Response suffix valid: yes 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.275: Partial capture successful. Please touch the sensor again (17/20) 383s (process:1926): libfprint-device-DEBUG: 00:53:52.275: Device reported enroll progress, reported 17 of 20 have been completed 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.275: [egismoc] ENROLL_STATES entering state 8 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.275: Execute command and get response 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.275: Get check bytes 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.275: [egismoc] CMD_STATES entering state 0 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.275: [egismoc] CMD_STATES entering state 1 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.276: Command receive callback 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.276: [egismoc] CMD_STATES completed successfully 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.276: Task SSM next state callback 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.276: [egismoc] ENROLL_STATES entering state 9 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.276: Execute command and get response 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.276: Get check bytes 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.276: [egismoc] CMD_STATES entering state 0 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.277: [egismoc] CMD_STATES entering state 1 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.277: Command receive callback 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.277: [egismoc] CMD_STATES completed successfully 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.277: Task SSM next state callback 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.277: [egismoc] ENROLL_STATES entering state 10 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.277: Wait for finger on sensor 383s (process:1926): libfprint-device-DEBUG: 00:53:52.277: Device reported finger status change: FP_FINGER_STATUS_NEEDED 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.278: Finger on sensor callback 383s (process:1926): libfprint-device-DEBUG: 00:53:52.278: Device reported finger status change: FP_FINGER_STATUS_PRESENT 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.278: [egismoc] ENROLL_STATES entering state 11 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.278: Execute command and get response 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.278: Get check bytes 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.278: [egismoc] CMD_STATES entering state 0 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.279: [egismoc] CMD_STATES entering state 1 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.279: Command receive callback 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.279: [egismoc] CMD_STATES completed successfully 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.279: Read capture callback 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.279: Response prefix valid: yes 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.279: Response suffix valid: yes 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.279: Partial capture successful. Please touch the sensor again (18/20) 383s (process:1926): libfprint-device-DEBUG: 00:53:52.279: Device reported enroll progress, reported 18 of 20 have been completed 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.280: [egismoc] ENROLL_STATES entering state 8 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.280: Execute command and get response 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.280: Get check bytes 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.280: [egismoc] CMD_STATES entering state 0 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.280: [egismoc] CMD_STATES entering state 1 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.281: Command receive callback 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.281: [egismoc] CMD_STATES completed successfully 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.281: Task SSM next state callback 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.281: [egismoc] ENROLL_STATES entering state 9 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.281: Execute command and get response 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.281: Get check bytes 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.281: [egismoc] CMD_STATES entering state 0 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.282: [egismoc] CMD_STATES entering state 1 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.282: Command receive callback 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.282: [egismoc] CMD_STATES completed successfully 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.282: Task SSM next state callback 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.282: [egismoc] ENROLL_STATES entering state 10 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.282: Wait for finger on sensor 383s (process:1926): libfprint-device-DEBUG: 00:53:52.282: Device reported finger status change: FP_FINGER_STATUS_NEEDED 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.283: Finger on sensor callback 383s (process:1926): libfprint-device-DEBUG: 00:53:52.283: Device reported finger status change: FP_FINGER_STATUS_PRESENT 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.283: [egismoc] ENROLL_STATES entering state 11 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.283: Execute command and get response 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.283: Get check bytes 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.283: [egismoc] CMD_STATES entering state 0 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.284: [egismoc] CMD_STATES entering state 1 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.284: Command receive callback 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.284: [egismoc] CMD_STATES completed successfully 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.284: Read capture callback 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.284: Response prefix valid: yes 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.284: Response suffix valid: yes 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.284: Partial capture successful. Please touch the sensor again (19/20) 383s (process:1926): libfprint-device-DEBUG: 00:53:52.284: Device reported enroll progress, reported 19 of 20 have been completed 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.285: [egismoc] ENROLL_STATES entering state 8 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.285: Execute command and get response 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.285: Get check bytes 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.285: [egismoc] CMD_STATES entering state 0 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.285: [egismoc] CMD_STATES entering state 1 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.286: Command receive callback 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.286: [egismoc] CMD_STATES completed successfully 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.286: Task SSM next state callback 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.286: [egismoc] ENROLL_STATES entering state 9 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.286: Execute command and get response 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.286: Get check bytes 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.286: [egismoc] CMD_STATES entering state 0 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.286: [egismoc] CMD_STATES entering state 1 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.287: Command receive callback 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.287: [egismoc] CMD_STATES completed successfully 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.287: Task SSM next state callback 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.287: [egismoc] ENROLL_STATES entering state 10 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.287: Wait for finger on sensor 383s (process:1926): libfprint-device-DEBUG: 00:53:52.287: Device reported finger status change: FP_FINGER_STATUS_NEEDED 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.288: Finger on sensor callback 383s (process:1926): libfprint-device-DEBUG: 00:53:52.288: Device reported finger status change: FP_FINGER_STATUS_PRESENT 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.288: [egismoc] ENROLL_STATES entering state 11 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.288: Execute command and get response 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.288: Get check bytes 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.288: [egismoc] CMD_STATES entering state 0 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.289: [egismoc] CMD_STATES entering state 1 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.290: Command receive callback 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.290: [egismoc] CMD_STATES completed successfully 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.290: Read capture callback 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.290: Response prefix valid: yes 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.290: Response suffix valid: yes 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.290: Partial capture successful. Please touch the sensor again (20/20) 383s (process:1926): libfprint-device-DEBUG: 00:53:52.290: Device reported enroll progress, reported 20 of 20 have been completed 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.290: [egismoc] ENROLL_STATES entering state 12 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.290: Execute command and get response 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.290: Get check bytes 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.290: [egismoc] CMD_STATES entering state 0 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.291: [egismoc] CMD_STATES entering state 1 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.292: Command receive callback 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.292: [egismoc] CMD_STATES completed successfully 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.292: Task SSM next state callback 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.292: [egismoc] ENROLL_STATES entering state 13 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.292: New fingerprint ID: FP1-00000000-7-00000000-nobody 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.292: Execute command and get response 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.292: Get check bytes 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.292: [egismoc] CMD_STATES entering state 0 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.292: [egismoc] CMD_STATES entering state 1 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.293: Command receive callback 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.293: [egismoc] CMD_STATES completed successfully 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.293: Task SSM next state callback 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.293: [egismoc] ENROLL_STATES entering state 14 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.293: Execute command and get response 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.293: Get check bytes 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.293: [egismoc] CMD_STATES entering state 0 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.294: [egismoc] CMD_STATES entering state 1 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.294: Command receive callback 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.294: [egismoc] CMD_STATES completed successfully 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.294: Task SSM next state callback 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.294: [egismoc] ENROLL_STATES entering state 15 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.294: Enrollment was successful! 383s (process:1926): libfprint-device-DEBUG: 00:53:52.294: Device reported enroll completion 383s (process:1926): libfprint-device-DEBUG: 00:53:52.294: Device reported finger status change: FP_FINGER_STATUS_NONE 383s (process:1926): libfprint-device-DEBUG: 00:53:52.294: Print for finger FP_FINGER_RIGHT_INDEX enrolled 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.294: [egismoc] ENROLL_STATES completed successfully 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.294: Task SSM done 383s (process:1926): libfprint-device-DEBUG: 00:53:52.294: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 383s (process:1926): libfprint-device-DEBUG: 00:53:52.294: Updated temperature model after 0.12 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.295: List 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.295: [egismoc] LIST_STATES entering state 0 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.295: Execute command and get response 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.295: Get check bytes 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.295: [egismoc] CMD_STATES entering state 0 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.295: [egismoc] CMD_STATES entering state 1 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.296: Command receive callback 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.296: [egismoc] CMD_STATES completed successfully 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.296: List callback 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.296: Device fingerprint 1: FP1-00000000-2-00000000-nobody 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.296: Device fingerprint 2: FP1-00000000-7-00000000-nobody 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.296: Number of currently enrolled fingerprints on the device is 2 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.296: [egismoc] LIST_STATES entering state 1 383s (process:1926): libfprint-device-DEBUG: 00:53:52.296: Device reported listing completion 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.296: [egismoc] LIST_STATES completed successfully 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.296: Task SSM done 383s (process:1926): libfprint-device-DEBUG: 00:53:52.296: Completing action FPI_DEVICE_ACTION_LIST in idle! 383s (process:1926): libfprint-device-DEBUG: 00:53:52.296: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.296: Delete 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.296: [egismoc] DELETE_STATES entering state 0 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.296: Execute command and get response 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.296: Get check bytes 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.296: [egismoc] CMD_STATES entering state 0 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.297: [egismoc] CMD_STATES entering state 1 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.298: Command receive callback 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.298: [egismoc] CMD_STATES completed successfully 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.298: List callback 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.298: Device fingerprint 1: FP1-00000000-2-00000000-nobody 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.298: Device fingerprint 2: FP1-00000000-7-00000000-nobody 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.298: Number of currently enrolled fingerprints on the device is 2 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.298: [egismoc] DELETE_STATES entering state 1 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.298: Get delete command 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.298: Delete fingerprint FP1-00000000-2-00000000-nobody (FP1-00000000-2-00000000-nobody) 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.298: Execute command and get response 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.298: Get check bytes 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.298: [egismoc] CMD_STATES entering state 0 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.299: [egismoc] CMD_STATES entering state 1 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.299: Command receive callback 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.299: [egismoc] CMD_STATES completed successfully 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.299: Delete callback 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.299: Response prefix valid: yes 383s (process:1926): libfprint-device-DEBUG: 00:53:52.299: Device reported deletion completion 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.299: [egismoc] DELETE_STATES completed successfully 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.299: Task SSM done 383s (process:1926): libfprint-device-DEBUG: 00:53:52.299: Completing action FPI_DEVICE_ACTION_DELETE in idle! 383s (process:1926): libfprint-device-DEBUG: 00:53:52.299: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.300: List 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.300: [egismoc] LIST_STATES entering state 0 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.300: Execute command and get response 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.300: Get check bytes 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.300: [egismoc] CMD_STATES entering state 0 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.300: [egismoc] CMD_STATES entering state 1 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.301: Command receive callback 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.301: [egismoc] CMD_STATES completed successfully 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.301: List callback 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.301: Device fingerprint 1: FP1-00000000-7-00000000-nobody 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.301: Number of currently enrolled fingerprints on the device is 1 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.301: [egismoc] LIST_STATES entering state 1 383s (process:1926): libfprint-device-DEBUG: 00:53:52.301: Device reported listing completion 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.301: [egismoc] LIST_STATES completed successfully 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.301: Task SSM done 383s (process:1926): libfprint-device-DEBUG: 00:53:52.301: Completing action FPI_DEVICE_ACTION_LIST in idle! 383s (process:1926): libfprint-device-DEBUG: 00:53:52.301: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.301: Clear storage 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.301: [egismoc] DELETE_STATES entering state 0 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.301: Execute command and get response 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.301: Get check bytes 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.301: [egismoc] CMD_STATES entering state 0 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.302: [egismoc] CMD_STATES entering state 1 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.303: Command receive callback 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.303: [egismoc] CMD_STATES completed successfully 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.303: List callback 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.303: Device fingerprint 1: FP1-00000000-7-00000000-nobody 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.303: Number of currently enrolled fingerprints on the device is 1 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.303: [egismoc] DELETE_STATES entering state 1 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.303: Get delete command 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.303: Execute command and get response 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.303: Get check bytes 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.303: [egismoc] CMD_STATES entering state 0 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.303: [egismoc] CMD_STATES entering state 1 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.304: Command receive callback 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.304: [egismoc] CMD_STATES completed successfully 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.304: Delete callback 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.304: Response prefix valid: yes 383s (process:1926): libfprint-device-DEBUG: 00:53:52.304: Device reported deletion completion 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.304: [egismoc] DELETE_STATES completed successfully 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.304: Task SSM done 383s (process:1926): libfprint-device-DEBUG: 00:53:52.304: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 383s (process:1926): libfprint-device-DEBUG: 00:53:52.304: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.304: List 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.304: [egismoc] LIST_STATES entering state 0 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.304: Execute command and get response 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.304: Get check bytes 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.304: [egismoc] CMD_STATES entering state 0 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.305: [egismoc] CMD_STATES entering state 1 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.305: Command receive callback 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.305: [egismoc] CMD_STATES completed successfully 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.305: List callback 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.305: Number of currently enrolled fingerprints on the device is 0 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.305: [egismoc] LIST_STATES entering state 1 383s (process:1926): libfprint-device-DEBUG: 00:53:52.305: Device reported listing completion 383s (process:1926): libfprint-SSM-DEBUG: 00:53:52.305: [egismoc] LIST_STATES completed successfully 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.305: Task SSM done 383s (process:1926): libfprint-device-DEBUG: 00:53:52.305: Completing action FPI_DEVICE_ACTION_LIST in idle! 383s (process:1926): libfprint-device-DEBUG: 00:53:52.305: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.306: Closing device 383s (process:1926): libfprint-egismoc-DEBUG: 00:53:52.306: Cancel 383s (process:1926): libfprint-device-DEBUG: 00:53:52.306: Device reported close completion 383s (process:1926): libfprint-device-DEBUG: 00:53:52.306: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 383s (process:1926): libfprint-device-DEBUG: 00:53:52.306: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 383s 383s finger status: 383s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xefc8f628 (FpiDeviceEgisMoc at 0x15d2810)>, 8, , None, None) 383s finger status: 383s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xefc8f628 (FpiDeviceEgisMoc at 0x15d2810)>, 9, , None, None) 383s finger status: 383s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xefc8f628 (FpiDeviceEgisMoc at 0x15d2810)>, 9, None, None, GLib.Error('The finger was not centered properly, please try again.', 'fp - device - retry - quark', 2)) 383s finger status: 383s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xefc8f628 (FpiDeviceEgisMoc at 0x15d2810)>, 10, , None, None) 383s finger status: 383s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xefc8f628 (FpiDeviceEgisMoc at 0x15d2810)>, 11, , None, None) 383s finger status: 383s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xefc8f628 (FpiDeviceEgisMoc at 0x15d2810)>, 12, , None, None) 383s finger status: 383s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xefc8f628 (FpiDeviceEgisMoc at 0x15d2810)>, 13, , None, None) 383s finger status: 383s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xefc8f628 (FpiDeviceEgisMoc at 0x15d2810)>, 14, , None, None) 383s finger status: 383s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xefc8f628 (FpiDeviceEgisMoc at 0x15d2810)>, 15, , None, None) 383s finger status: 383s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xefc8f628 (FpiDeviceEgisMoc at 0x15d2810)>, 16, , None, None) 383s finger status: 383s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xefc8f628 (FpiDeviceEgisMoc at 0x15d2810)>, 17, , None, None) 383s finger status: 383s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xefc8f628 (FpiDeviceEgisMoc at 0x15d2810)>, 18, , None, None) 383s finger status: 383s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xefc8f628 (FpiDeviceEgisMoc at 0x15d2810)>, 19, , None, None) 383s finger status: 383s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xefc8f628 (FpiDeviceEgisMoc at 0x15d2810)>, 20, , None, None) 383s enroll new finger done 383s listing - device should have 2 prints 383s deleting first print 383s delete done 383s listing - device should only have second print 383s clear device storage 383s clear done 383s listing - device should be empty 383s ** (umockdev-run:1922): DEBUG: 00:53:52.380: umockdev.vala:154: Removing test bed /tmp/umockdev.24ME22 383s (umockdev-run:1922): GLib-DEBUG: 00:53:52.388: unsetenv() is not thread-safe and should not be used after threads are created 383s PASS: libfprint-2/driver-egismoc-0586.test 383s Running test: libfprint-2/driver-uru4000-msv2.test 383s ** (umockdev-run:1934): DEBUG: 00:53:52.491: umockdev.vala:127: Created udev test bed /tmp/umockdev.7OI812 383s ** (umockdev-run:1934): DEBUG: 00:53:52.491: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0/usb1/1-10 383s ** (umockdev-run:1934): DEBUG: 00:53:52.493: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0/usb1/1-10 (subsystem usb) 383s ** (umockdev-run:1934): DEBUG: 00:53:52.497: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.7OI812/dev/bus/usb/001/047 383s ** (umockdev-run:1934): DEBUG: 00:53:52.497: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0/usb1 383s ** (umockdev-run:1934): DEBUG: 00:53:52.498: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0/usb1 (subsystem usb) 383s ** (umockdev-run:1934): DEBUG: 00:53:52.502: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.7OI812/dev/bus/usb/001/001 383s ** (umockdev-run:1934): DEBUG: 00:53:52.502: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0 383s ** (umockdev-run:1934): DEBUG: 00:53:52.503: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0 (subsystem pci) 383s (process:1938): libfprint-context-DEBUG: 00:53:52.632: Initializing FpContext (libfprint version 1.94.8+tod1) 383s (process:1938): libfprint-tod-DEBUG: 00:53:52.632: Impossible to load the shared drivers dir Error opening directory “/usr/lib/arm-linux-gnueabihf/libfprint-2/tod-1”: No such file or directory 383s (process:1938): libfprint-context-DEBUG: 00:53:52.635: No driver found for USB device 1D6B:0002 383s (process:1938): libfprint-device-DEBUG: 00:53:52.636: Device reported probe completion 383s (process:1938): libfprint-device-DEBUG: 00:53:52.636: Completing action FPI_DEVICE_ACTION_PROBE in idle! 383s (process:1938): libfprint-device-DEBUG: 00:53:52.636: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 383s (process:1938): GLib-DEBUG: 00:53:52.638: setenv()/putenv() are not thread-safe and should not be used after threads are created 383s (process:1938): libfprint-image_device-DEBUG: 00:53:52.644: Image device open completed 383s (process:1938): libfprint-device-DEBUG: 00:53:52.644: Device reported open completion 383s (process:1938): libfprint-device-DEBUG: 00:53:52.644: Completing action FPI_DEVICE_ACTION_OPEN in idle! 383s (process:1938): libfprint-device-DEBUG: 00:53:52.644: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 383s (process:1938): libfprint-device-DEBUG: 00:53:52.644: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 383s (process:1938): libfprint-image_device-DEBUG: 00:53:52.644: Activating image device 383s (process:1938): libfprint-image_device-DEBUG: 00:53:52.644: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING 383s (process:1938): libfprint-SSM-DEBUG: 00:53:52.645: [uru4000] INIT_NUM_STATES entering state 0 383s (process:1938): libfprint-uru4000-DEBUG: 00:53:52.645: read 1 regs at 7 383s (process:1938): libfprint-uru4000-DEBUG: 00:53:52.646: reg value 3 383s (process:1938): libfprint-SSM-DEBUG: 00:53:52.646: [uru4000] INIT_NUM_STATES entering state 1 383s (process:1938): libfprint-SSM-DEBUG: 00:53:52.646: [uru4000] INIT_NUM_STATES entering state 3 383s (process:1938): libfprint-uru4000-DEBUG: 00:53:52.646: set 83 383s (process:1938): libfprint-SSM-DEBUG: 00:53:52.646: [uru4000] INIT_NUM_STATES entering state 4 383s (process:1938): libfprint-SSM-DEBUG: 00:53:52.646: [uru4000] POWERUP_NUM_STATES entering state 0 383s (process:1938): libfprint-SSM-DEBUG: 00:53:52.646: [uru4000] POWERUP_NUM_STATES entering state 1 383s (process:1938): libfprint-uru4000-DEBUG: 00:53:52.646: set 03 383s (process:1938): libfprint-SSM-DEBUG: 00:53:52.647: [uru4000] POWERUP_NUM_STATES entering state 2 383s (process:1938): libfprint-uru4000-DEBUG: 00:53:52.647: read 1 regs at 7 383s (process:1938): libfprint-uru4000-DEBUG: 00:53:52.648: reg value 83 383s (process:1938): libfprint-SSM-DEBUG: 00:53:52.648: [uru4000] POWERUP_NUM_STATES entering state 3 383s (process:1938): libfprint-SSM-DEBUG: 00:53:52.648: [uru4000] POWERUP_NUM_STATES entering state 4 383s (process:1938): libfprint-SSM-DEBUG: 00:53:52.658: [uru4000] POWERUP_NUM_STATES entering state 5 383s (process:1938): libfprint-uru4000-DEBUG: 00:53:52.658: 7399800719109: ../libfprint/drivers/uru4000.c:291 383s (process:1938): libfprint-SSM-DEBUG: 00:53:52.660: [uru4000] POWERUP_NUM_STATES entering state 6 383s (process:1938): libfprint-SSM-DEBUG: 00:53:52.660: [uru4000] POWERUP_NUM_STATES entering state 1 383s (process:1938): libfprint-uru4000-DEBUG: 00:53:52.660: set 03 383s (process:1938): libfprint-SSM-DEBUG: 00:53:52.660: [uru4000] POWERUP_NUM_STATES entering state 2 383s (process:1938): libfprint-uru4000-DEBUG: 00:53:52.660: read 1 regs at 7 383s (process:1938): libfprint-uru4000-DEBUG: 00:53:52.661: reg value 3 383s (process:1938): libfprint-SSM-DEBUG: 00:53:52.661: [uru4000] POWERUP_NUM_STATES entering state 3 383s (process:1938): libfprint-SSM-DEBUG: 00:53:52.661: [uru4000] POWERUP_NUM_STATES completed successfully 383s (process:1938): libfprint-SSM-DEBUG: 00:53:52.661: [uru4000] INIT_NUM_STATES entering state 5 383s (process:1938): libfprint-uru4000-DEBUG: 00:53:52.662: recv irq type 56aa 383s (process:1938): libfprint-uru4000-DEBUG: 00:53:52.662: late scanpwr interrupt 383s (process:1938): libfprint-SSM-DEBUG: 00:53:52.662: [uru4000] INIT_NUM_STATES entering state 6 383s (process:1938): libfprint-SSM-DEBUG: 00:53:52.662: [uru4000] INIT_NUM_STATES entering state 7 383s (process:1938): libfprint-uru4000-DEBUG: 00:53:52.662: read 16 regs at f0 383s (process:1938): libfprint-uru4000-DEBUG: 00:53:52.662: reg value 50 383s (process:1938): libfprint-SSM-DEBUG: 00:53:52.663: [uru4000] INIT_NUM_STATES entering state 8 383s (process:1938): libfprint-uru4000-DEBUG: 00:53:52.663: Versions 0059 and 0034 383s (process:1938): libfprint-SSM-DEBUG: 00:53:52.663: [uru4000] INIT_NUM_STATES completed successfully 383s (process:1938): libfprint-image_device-DEBUG: 00:53:52.663: Image device activation completed 383s (process:1938): libfprint-image_device-DEBUG: 00:53:52.663: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE 383s (process:1938): libfprint-image_device-DEBUG: 00:53:52.663: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 383s (process:1938): libfprint-uru4000-DEBUG: 00:53:52.663: wait finger on 383s (process:1938): libfprint-device-DEBUG: 00:53:52.663: Device reported finger status change: FP_FINGER_STATUS_NEEDED 383s (process:1938): libfprint-uru4000-DEBUG: 00:53:52.664: recv irq type 0101 383s (process:1938): libfprint-device-DEBUG: 00:53:52.664: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 383s (process:1938): libfprint-image_device-DEBUG: 00:53:52.664: Image device reported finger status: on 383s (process:1938): libfprint-image_device-DEBUG: 00:53:52.664: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 383s (process:1938): libfprint-uru4000-DEBUG: 00:53:52.664: starting capture 383s (process:1938): libfprint-uru4000-DEBUG: 00:53:52.664: Image encryption seed: 1374298404 383s (process:1938): libfprint-SSM-DEBUG: 00:53:52.664: [uru4000] IMAGING_NUM_STATES entering state 0 383s (process:1938): libfprint-SSM-DEBUG: 00:53:52.667: [uru4000] IMAGING_NUM_STATES entering state 1 383s (process:1938): libfprint-uru4000-DEBUG: 00:53:52.667: hw header lines 289 383s (process:1938): libfprint-uru4000-DEBUG: 00:53:52.667: dev2: 10849 383s (process:1938): libfprint-uru4000-DEBUG: 00:53:52.667: image seems to be encrypted 383s (process:1938): libfprint-SSM-DEBUG: 00:53:52.668: [uru4000] IMAGING_NUM_STATES entering state 2 383s (process:1938): libfprint-uru4000-DEBUG: 00:53:52.668: read 4 regs at 34 383s (process:1938): libfprint-uru4000-DEBUG: 00:53:52.669: reg value 7b 383s (process:1938): libfprint-SSM-DEBUG: 00:53:52.669: [uru4000] IMAGING_NUM_STATES entering state 3 383s (process:1938): libfprint-uru4000-DEBUG: 00:53:52.669: encryption id 05 -> key db896f5f 383s (process:1938): libfprint-uru4000-DEBUG: 00:53:52.669: 0 02 67 383s (process:1938): libfprint-uru4000-DEBUG: 00:53:52.669: decoding 67 lines 383s (process:1938): libfprint-uru4000-DEBUG: 00:53:52.669: 1 00 1 383s (process:1938): libfprint-uru4000-DEBUG: 00:53:52.669: skipping 1 lines 383s (process:1938): libfprint-uru4000-DEBUG: 00:53:52.669: 2 02 49 383s (process:1938): libfprint-uru4000-DEBUG: 00:53:52.669: decoding 49 lines 383s (process:1938): libfprint-uru4000-DEBUG: 00:53:52.669: 3 01 1 383s (process:1938): libfprint-uru4000-DEBUG: 00:53:52.669: skipping 1 lines 383s (process:1938): libfprint-uru4000-DEBUG: 00:53:52.669: 4 00 1 383s (process:1938): libfprint-uru4000-DEBUG: 00:53:52.669: skipping 1 lines 383s (process:1938): libfprint-uru4000-DEBUG: 00:53:52.669: 5 02 49 383s (process:1938): libfprint-uru4000-DEBUG: 00:53:52.669: decoding 49 lines 383s (process:1938): libfprint-uru4000-DEBUG: 00:53:52.669: 6 00 1 383s (process:1938): libfprint-uru4000-DEBUG: 00:53:52.669: skipping 1 lines 383s (process:1938): libfprint-uru4000-DEBUG: 00:53:52.669: 7 02 121 383s (process:1938): libfprint-uru4000-DEBUG: 00:53:52.669: decoding 121 lines 383s (process:1938): libfprint-SSM-DEBUG: 00:53:52.669: [uru4000] IMAGING_NUM_STATES entering state 4 383s (process:1938): libfprint-image_device-DEBUG: 00:53:52.670: Image device captured an image 383s (process:1938): libfprint-image_device-DEBUG: 00:53:52.681: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 383s (process:1938): libfprint-device-DEBUG: 00:53:52.681: Device reported finger status change: FP_FINGER_STATUS_PRESENT 383s (process:1938): libfprint-SSM-DEBUG: 00:53:52.681: [uru4000] IMAGING_NUM_STATES completed successfully 383s (process:1938): libfprint-uru4000-DEBUG: 00:53:52.681: await finger off 383s (process:1938): libfprint-uru4000-DEBUG: 00:53:52.682: recv irq type 0200 383s (process:1938): libfprint-device-DEBUG: 00:53:52.682: Device reported finger status change: FP_FINGER_STATUS_NONE 383s (process:1938): libfprint-image_device-DEBUG: 00:53:52.682: Image device reported finger status: off 383s (process:1938): libfprint-image_device-DEBUG: 00:53:52.682: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 383s (process:1938): libfprint-image_device-DEBUG: 00:53:52.682: Deactivating image device 383s (process:1938): libfprint-image_device-DEBUG: 00:53:52.682: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_DEACTIVATING 383s (process:1938): libfprint-uru4000-DEBUG: 00:53:52.682: deactivating 383s (process:1938): libfprint-uru4000-DEBUG: 00:53:52.683: cancelled 383s (process:1938): libfprint-image_device-DEBUG: 00:53:52.683: Image device deactivation completed 383s (process:1938): libfprint-image_device-DEBUG: 00:53:52.683: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE 383s (process:1938): libfprint-image-DEBUG: 00:53:52.724: Minutiae scan completed in 0.042742 secs 383s (process:1938): libfprint-device-DEBUG: 00:53:52.724: Device reported capture completion 383s (process:1938): libfprint-device-DEBUG: 00:53:52.724: Completing action FPI_DEVICE_ACTION_CAPTURE in idle! 383s (process:1938): libfprint-device-DEBUG: 00:53:52.724: Updated temperature model after 0.08 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 383s (process:1938): libfprint-image_device-DEBUG: 00:53:52.726: Image device close completed 383s (process:1938): libfprint-device-DEBUG: 00:53:52.726: Device reported close completion 383s (process:1938): libfprint-device-DEBUG: 00:53:52.726: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 383s (process:1938): libfprint-device-DEBUG: 00:53:52.726: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 383s ** (umockdev-run:1934): DEBUG: 00:53:52.924: umockdev.vala:154: Removing test bed /tmp/umockdev.7OI812 383s (umockdev-run:1934): GLib-DEBUG: 00:53:52.931: unsetenv() is not thread-safe and should not be used after threads are created 384s Comparing PNGs /tmp/libfprint-umockdev-test-95hn6td5/capture.png and /usr/share/installed-tests/libfprint-2/uru4000-msv2/capture.png 384s PASS: libfprint-2/driver-uru4000-msv2.test 384s Running test: libfprint-2/driver-elan.test 384s ** (umockdev-run:1948): DEBUG: 00:53:53.101: umockdev.vala:127: Created udev test bed /tmp/umockdev.BJQ012 384s ** (umockdev-run:1948): DEBUG: 00:53:53.101: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0/usb1/1-4/1-4.4 384s ** (umockdev-run:1948): DEBUG: 00:53:53.103: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0/usb1/1-4/1-4.4 (subsystem usb) 384s ** (umockdev-run:1948): DEBUG: 00:53:53.107: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.BJQ012/dev/bus/usb/001/094 384s ** (umockdev-run:1948): DEBUG: 00:53:53.107: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0/usb1/1-4 384s ** (umockdev-run:1948): DEBUG: 00:53:53.108: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0/usb1/1-4 (subsystem usb) 384s ** (umockdev-run:1948): DEBUG: 00:53:53.112: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.BJQ012/dev/bus/usb/001/083 384s ** (umockdev-run:1948): DEBUG: 00:53:53.112: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0/usb1 384s ** (umockdev-run:1948): DEBUG: 00:53:53.113: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0/usb1 (subsystem usb) 384s ** (umockdev-run:1948): DEBUG: 00:53:53.117: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.BJQ012/dev/bus/usb/001/001 384s ** (umockdev-run:1948): DEBUG: 00:53:53.117: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0 384s ** (umockdev-run:1948): DEBUG: 00:53:53.117: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0 (subsystem pci) 384s (umockdev-run:1948): GLib-GIO-DEBUG: 00:53:53.120: _g_io_module_get_default: Found default implementation local (GLocalVfs) for ?gio-vfs? 384s (process:1952): libfprint-context-DEBUG: 00:53:53.234: Initializing FpContext (libfprint version 1.94.8+tod1) 384s (process:1952): libfprint-tod-DEBUG: 00:53:53.235: Impossible to load the shared drivers dir Error opening directory “/usr/lib/arm-linux-gnueabihf/libfprint-2/tod-1”: No such file or directory 384s (process:1952): libfprint-context-DEBUG: 00:53:53.239: No driver found for USB device 17EF:1018 384s (process:1952): libfprint-context-DEBUG: 00:53:53.239: No driver found for USB device 1D6B:0002 384s (process:1952): libfprint-device-DEBUG: 00:53:53.239: Device reported probe completion 384s (process:1952): libfprint-device-DEBUG: 00:53:53.239: Completing action FPI_DEVICE_ACTION_PROBE in idle! 384s (process:1952): libfprint-device-DEBUG: 00:53:53.239: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 384s (process:1952): libfprint-elan-DEBUG: 00:53:53.241: 7399801302746: ../libfprint/drivers/elan.c:908 384s (process:1952): libfprint-image_device-DEBUG: 00:53:53.242: Image device open completed 384s (process:1952): libfprint-device-DEBUG: 00:53:53.242: Device reported open completion 384s (process:1952): libfprint-device-DEBUG: 00:53:53.242: Completing action FPI_DEVICE_ACTION_OPEN in idle! 384s (process:1952): libfprint-device-DEBUG: 00:53:53.242: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 384s (process:1952): libfprint-device-DEBUG: 00:53:53.242: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 384s (process:1952): libfprint-image_device-DEBUG: 00:53:53.242: Activating image device 384s (process:1952): libfprint-image_device-DEBUG: 00:53:53.242: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING 384s (process:1952): libfprint-elan-DEBUG: 00:53:53.242: 7399801303682: ../libfprint/drivers/elan.c:960 384s (process:1952): libfprint-elan-DEBUG: 00:53:53.242: 7399801303701: ../libfprint/drivers/elan.c:951 384s (process:1952): libfprint-elan-DEBUG: 00:53:53.242: 7399801303705: ../libfprint/drivers/elan.c:892 384s (process:1952): libfprint-elan-DEBUG: 00:53:53.242: 7399801303708: ../libfprint/drivers/elan.c:100 384s (process:1952): libfprint-SSM-DEBUG: 00:53:53.242: [elan] ACTIVATE_NUM_STATES entering state 0 384s (process:1952): libfprint-elan-DEBUG: 00:53:53.242: 7399801303739: ../libfprint/drivers/elan.c:820 384s (process:1952): libfprint-elan-DEBUG: 00:53:53.243: 7399801304266: ../libfprint/drivers/elan.c:346 384s (process:1952): libfprint-elan-DEBUG: 00:53:53.243: 7399801304298: ../libfprint/drivers/elan.c:366 384s (process:1952): libfprint-elan-DEBUG: 00:53:53.243: 7399801304304: ../libfprint/drivers/elan.c:379 384s (process:1952): libfprint-elan-DEBUG: 00:53:53.243: 7399801304841: ../libfprint/drivers/elan.c:346 384s (process:1952): libfprint-elan-DEBUG: 00:53:53.243: 7399801304858: ../libfprint/drivers/elan.c:335 384s (process:1952): libfprint-SSM-DEBUG: 00:53:53.243: [elan] ACTIVATE_NUM_STATES entering state 1 384s (process:1952): libfprint-elan-DEBUG: 00:53:53.243: 7399801304870: ../libfprint/drivers/elan.c:820 384s (process:1952): libfprint-elan-DEBUG: 00:53:53.243: FW ver 0x0140 384s (process:1952): libfprint-SSM-DEBUG: 00:53:53.243: [elan] ACTIVATE_NUM_STATES entering state 2 384s (process:1952): libfprint-elan-DEBUG: 00:53:53.243: 7399801304880: ../libfprint/drivers/elan.c:820 384s (process:1952): libfprint-elan-DEBUG: 00:53:53.244: 7399801305625: ../libfprint/drivers/elan.c:346 384s (process:1952): libfprint-elan-DEBUG: 00:53:53.244: 7399801305655: ../libfprint/drivers/elan.c:366 384s (process:1952): libfprint-elan-DEBUG: 00:53:53.244: 7399801305661: ../libfprint/drivers/elan.c:379 384s (process:1952): libfprint-elan-DEBUG: 00:53:53.245: 7399801306454: ../libfprint/drivers/elan.c:346 384s (process:1952): libfprint-elan-DEBUG: 00:53:53.245: 7399801306470: ../libfprint/drivers/elan.c:335 384s (process:1952): libfprint-SSM-DEBUG: 00:53:53.245: [elan] ACTIVATE_NUM_STATES entering state 3 384s (process:1952): libfprint-elan-DEBUG: 00:53:53.245: 7399801306482: ../libfprint/drivers/elan.c:820 384s (process:1952): libfprint-elan-DEBUG: 00:53:53.245: sensor dimensions, WxH: 144x64 384s (process:1952): libfprint-SSM-DEBUG: 00:53:53.245: [elan] ACTIVATE_NUM_STATES entering state 4 384s (process:1952): libfprint-elan-DEBUG: 00:53:53.245: 7399801306494: ../libfprint/drivers/elan.c:820 384s (process:1952): libfprint-elan-DEBUG: 00:53:53.245: skipping command 0x40 0x2a for this device (for devices 0x1 but device is 0x0) 384s (process:1952): libfprint-elan-DEBUG: 00:53:53.245: 7399801306502: ../libfprint/drivers/elan.c:335 384s (process:1952): libfprint-SSM-DEBUG: 00:53:53.245: [elan] ACTIVATE_NUM_STATES completed successfully 384s (process:1952): libfprint-elan-DEBUG: 00:53:53.245: 7399801306510: ../libfprint/drivers/elan.c:881 384s (process:1952): libfprint-image_device-DEBUG: 00:53:53.245: Image device activation completed 384s (process:1952): libfprint-image_device-DEBUG: 00:53:53.245: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE 384s (process:1952): libfprint-elan-DEBUG: 00:53:53.245: 7399801306533: ../libfprint/drivers/elan.c:960 384s (process:1952): libfprint-image_device-DEBUG: 00:53:53.245: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 384s (process:1952): libfprint-elan-DEBUG: 00:53:53.245: 7399801306543: ../libfprint/drivers/elan.c:960 384s (process:1952): libfprint-elan-DEBUG: 00:53:53.245: 7399801306547: ../libfprint/drivers/elan.c:792 384s (process:1952): libfprint-elan-DEBUG: 00:53:53.245: 7399801306550: ../libfprint/drivers/elan.c:100 384s (process:1952): libfprint-SSM-DEBUG: 00:53:53.245: [elan] CALIBRATE_NUM_STATES entering state 0 384s (process:1952): libfprint-elan-DEBUG: 00:53:53.245: 7399801306558: ../libfprint/drivers/elan.c:691 384s (process:1952): libfprint-device-DEBUG: 00:53:53.245: Device reported finger status change: FP_FINGER_STATUS_NEEDED 384s (process:1952): libfprint-elan-DEBUG: 00:53:53.246: 7399801307048: ../libfprint/drivers/elan.c:346 384s (process:1952): libfprint-elan-DEBUG: 00:53:53.246: 7399801307064: ../libfprint/drivers/elan.c:366 384s (process:1952): libfprint-elan-DEBUG: 00:53:53.246: 7399801307071: ../libfprint/drivers/elan.c:379 384s (process:1952): libfprint-elan-DEBUG: 00:53:53.246: 7399801307715: ../libfprint/drivers/elan.c:346 384s (process:1952): libfprint-elan-DEBUG: 00:53:53.246: 7399801307741: ../libfprint/drivers/elan.c:335 384s (process:1952): libfprint-SSM-DEBUG: 00:53:53.246: [elan] CALIBRATE_NUM_STATES entering state 1 384s (process:1952): libfprint-elan-DEBUG: 00:53:53.246: 7399801307753: ../libfprint/drivers/elan.c:691 384s (process:1952): libfprint-elan-DEBUG: 00:53:53.246: 7399801307757: ../libfprint/drivers/elan.c:156 384s (process:1952): libfprint-elan-DEBUG: 00:53:53.246: 7399801307763: ../libfprint/drivers/elan.c:118 384s (process:1952): libfprint-SSM-DEBUG: 00:53:53.246: [elan] CALIBRATE_NUM_STATES entering state 2 384s (process:1952): libfprint-elan-DEBUG: 00:53:53.246: 7399801307789: ../libfprint/drivers/elan.c:691 384s (process:1952): libfprint-elan-DEBUG: 00:53:53.247: 7399801308356: ../libfprint/drivers/elan.c:346 384s (process:1952): libfprint-elan-DEBUG: 00:53:53.247: 7399801308371: ../libfprint/drivers/elan.c:366 384s (process:1952): libfprint-elan-DEBUG: 00:53:53.247: 7399801308377: ../libfprint/drivers/elan.c:379 384s (process:1952): libfprint-elan-DEBUG: 00:53:53.248: 7399801309128: ../libfprint/drivers/elan.c:346 384s (process:1952): libfprint-elan-DEBUG: 00:53:53.248: 7399801309146: ../libfprint/drivers/elan.c:335 384s (process:1952): libfprint-SSM-DEBUG: 00:53:53.248: [elan] CALIBRATE_NUM_STATES entering state 3 384s (process:1952): libfprint-elan-DEBUG: 00:53:53.248: 7399801309157: ../libfprint/drivers/elan.c:691 384s (process:1952): libfprint-elan-DEBUG: 00:53:53.248: 7399801309162: ../libfprint/drivers/elan.c:634 384s (process:1952): libfprint-elan-DEBUG: 00:53:53.248: calibration mean: 8421, bg mean: 5805, delta: 2616 384s (process:1952): libfprint-SSM-DEBUG: 00:53:53.248: [elan] CALIBRATE_NUM_STATES entering state 4 384s (process:1952): libfprint-elan-DEBUG: 00:53:53.248: 7399801309180: ../libfprint/drivers/elan.c:691 384s (process:1952): libfprint-elan-DEBUG: 00:53:53.248: 7399801309710: ../libfprint/drivers/elan.c:346 384s (process:1952): libfprint-elan-DEBUG: 00:53:53.248: 7399801309723: ../libfprint/drivers/elan.c:366 384s (process:1952): libfprint-elan-DEBUG: 00:53:53.248: 7399801309729: ../libfprint/drivers/elan.c:379 384s (process:1952): libfprint-elan-DEBUG: 00:53:53.249: 7399801310286: ../libfprint/drivers/elan.c:346 384s (process:1952): libfprint-elan-DEBUG: 00:53:53.249: 7399801310302: ../libfprint/drivers/elan.c:335 384s (process:1952): libfprint-SSM-DEBUG: 00:53:53.249: [elan] CALIBRATE_NUM_STATES entering state 5 384s (process:1952): libfprint-elan-DEBUG: 00:53:53.249: 7399801310314: ../libfprint/drivers/elan.c:691 384s (process:1952): libfprint-elan-DEBUG: 00:53:53.249: calibration status: 0x01 384s (process:1952): libfprint-SSM-DEBUG: 00:53:53.299: [elan] CALIBRATE_NUM_STATES entering state 6 384s (process:1952): libfprint-elan-DEBUG: 00:53:53.299: 7399801360499: ../libfprint/drivers/elan.c:691 384s (process:1952): libfprint-SSM-DEBUG: 00:53:53.299: [elan] CALIBRATE_NUM_STATES entering state 4 384s (process:1952): libfprint-elan-DEBUG: 00:53:53.299: 7399801360521: ../libfprint/drivers/elan.c:691 384s (process:1952): libfprint-elan-DEBUG: 00:53:53.300: 7399801361351: ../libfprint/drivers/elan.c:346 384s (process:1952): libfprint-elan-DEBUG: 00:53:53.300: 7399801361380: ../libfprint/drivers/elan.c:366 384s (process:1952): libfprint-elan-DEBUG: 00:53:53.300: 7399801361386: ../libfprint/drivers/elan.c:379 384s (process:1952): libfprint-elan-DEBUG: 00:53:53.301: 7399801362124: ../libfprint/drivers/elan.c:346 384s (process:1952): libfprint-elan-DEBUG: 00:53:53.301: 7399801362199: ../libfprint/drivers/elan.c:335 384s (process:1952): libfprint-SSM-DEBUG: 00:53:53.301: [elan] CALIBRATE_NUM_STATES entering state 5 384s (process:1952): libfprint-elan-DEBUG: 00:53:53.301: 7399801362260: ../libfprint/drivers/elan.c:691 384s (process:1952): libfprint-elan-DEBUG: 00:53:53.301: calibration status: 0x01 384s (process:1952): libfprint-device-DEBUG: 00:53:53.342: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 384s (process:1952): libfprint-SSM-DEBUG: 00:53:53.351: [elan] CALIBRATE_NUM_STATES entering state 6 384s (process:1952): libfprint-elan-DEBUG: 00:53:53.351: 7399801412321: ../libfprint/drivers/elan.c:691 384s (process:1952): libfprint-SSM-DEBUG: 00:53:53.351: [elan] CALIBRATE_NUM_STATES entering state 4 384s (process:1952): libfprint-elan-DEBUG: 00:53:53.351: 7399801412333: ../libfprint/drivers/elan.c:691 384s (process:1952): libfprint-elan-DEBUG: 00:53:53.351: 7399801412839: ../libfprint/drivers/elan.c:346 384s (process:1952): libfprint-elan-DEBUG: 00:53:53.351: 7399801412856: ../libfprint/drivers/elan.c:366 384s (process:1952): libfprint-elan-DEBUG: 00:53:53.351: 7399801412861: ../libfprint/drivers/elan.c:379 384s (process:1952): libfprint-elan-DEBUG: 00:53:53.352: 7399801413390: ../libfprint/drivers/elan.c:346 384s (process:1952): libfprint-elan-DEBUG: 00:53:53.352: 7399801413411: ../libfprint/drivers/elan.c:335 384s (process:1952): libfprint-SSM-DEBUG: 00:53:53.352: [elan] CALIBRATE_NUM_STATES entering state 5 384s (process:1952): libfprint-elan-DEBUG: 00:53:53.352: 7399801413422: ../libfprint/drivers/elan.c:691 384s (process:1952): libfprint-elan-DEBUG: 00:53:53.352: calibration status: 0x01 384s (process:1952): libfprint-SSM-DEBUG: 00:53:53.402: [elan] CALIBRATE_NUM_STATES entering state 6 384s (process:1952): libfprint-elan-DEBUG: 00:53:53.402: 7399801463615: ../libfprint/drivers/elan.c:691 384s (process:1952): libfprint-SSM-DEBUG: 00:53:53.402: [elan] CALIBRATE_NUM_STATES entering state 4 384s (process:1952): libfprint-elan-DEBUG: 00:53:53.402: 7399801463687: ../libfprint/drivers/elan.c:691 384s (process:1952): libfprint-elan-DEBUG: 00:53:53.403: 7399801464281: ../libfprint/drivers/elan.c:346 384s (process:1952): libfprint-elan-DEBUG: 00:53:53.403: 7399801464348: ../libfprint/drivers/elan.c:366 384s (process:1952): libfprint-elan-DEBUG: 00:53:53.403: 7399801464457: ../libfprint/drivers/elan.c:379 384s (process:1952): libfprint-elan-DEBUG: 00:53:53.404: 7399801464971: ../libfprint/drivers/elan.c:346 384s (process:1952): libfprint-elan-DEBUG: 00:53:53.404: 7399801465046: ../libfprint/drivers/elan.c:335 384s (process:1952): libfprint-SSM-DEBUG: 00:53:53.404: [elan] CALIBRATE_NUM_STATES entering state 5 384s (process:1952): libfprint-elan-DEBUG: 00:53:53.404: 7399801465096: ../libfprint/drivers/elan.c:691 384s (process:1952): libfprint-elan-DEBUG: 00:53:53.404: calibration status: 0x01 384s (process:1952): libfprint-SSM-DEBUG: 00:53:53.454: [elan] CALIBRATE_NUM_STATES entering state 6 384s (process:1952): libfprint-elan-DEBUG: 00:53:53.454: 7399801515092: ../libfprint/drivers/elan.c:691 384s (process:1952): libfprint-SSM-DEBUG: 00:53:53.454: [elan] CALIBRATE_NUM_STATES entering state 4 384s (process:1952): libfprint-elan-DEBUG: 00:53:53.454: 7399801515104: ../libfprint/drivers/elan.c:691 384s (process:1952): libfprint-elan-DEBUG: 00:53:53.454: 7399801515709: ../libfprint/drivers/elan.c:346 384s (process:1952): libfprint-elan-DEBUG: 00:53:53.454: 7399801515729: ../libfprint/drivers/elan.c:366 384s (process:1952): libfprint-elan-DEBUG: 00:53:53.454: 7399801515734: ../libfprint/drivers/elan.c:379 384s (process:1952): libfprint-elan-DEBUG: 00:53:53.455: 7399801516327: ../libfprint/drivers/elan.c:346 384s (process:1952): libfprint-elan-DEBUG: 00:53:53.455: 7399801516354: ../libfprint/drivers/elan.c:335 384s (process:1952): libfprint-SSM-DEBUG: 00:53:53.455: [elan] CALIBRATE_NUM_STATES entering state 5 384s (process:1952): libfprint-elan-DEBUG: 00:53:53.455: 7399801516366: ../libfprint/drivers/elan.c:691 384s (process:1952): libfprint-elan-DEBUG: 00:53:53.455: calibration status: 0x01 384s (process:1952): libfprint-SSM-DEBUG: 00:53:53.505: [elan] CALIBRATE_NUM_STATES entering state 6 384s (process:1952): libfprint-elan-DEBUG: 00:53:53.505: 7399801566599: ../libfprint/drivers/elan.c:691 384s (process:1952): libfprint-SSM-DEBUG: 00:53:53.505: [elan] CALIBRATE_NUM_STATES entering state 4 384s (process:1952): libfprint-elan-DEBUG: 00:53:53.505: 7399801566612: ../libfprint/drivers/elan.c:691 384s (process:1952): libfprint-elan-DEBUG: 00:53:53.506: 7399801567170: ../libfprint/drivers/elan.c:346 384s (process:1952): libfprint-elan-DEBUG: 00:53:53.506: 7399801567200: ../libfprint/drivers/elan.c:366 384s (process:1952): libfprint-elan-DEBUG: 00:53:53.506: 7399801567206: ../libfprint/drivers/elan.c:379 384s (process:1952): libfprint-elan-DEBUG: 00:53:53.506: 7399801567815: ../libfprint/drivers/elan.c:346 384s (process:1952): libfprint-elan-DEBUG: 00:53:53.506: 7399801567833: ../libfprint/drivers/elan.c:335 384s (process:1952): libfprint-SSM-DEBUG: 00:53:53.506: [elan] CALIBRATE_NUM_STATES entering state 5 384s (process:1952): libfprint-elan-DEBUG: 00:53:53.506: 7399801567859: ../libfprint/drivers/elan.c:691 384s (process:1952): libfprint-elan-DEBUG: 00:53:53.506: calibration status: 0x03 384s (process:1952): libfprint-SSM-DEBUG: 00:53:53.506: [elan] CALIBRATE_NUM_STATES entering state 0 384s (process:1952): libfprint-elan-DEBUG: 00:53:53.506: 7399801567871: ../libfprint/drivers/elan.c:691 384s (process:1952): libfprint-elan-DEBUG: 00:53:53.507: 7399801568448: ../libfprint/drivers/elan.c:346 384s (process:1952): libfprint-elan-DEBUG: 00:53:53.507: 7399801568469: ../libfprint/drivers/elan.c:366 384s (process:1952): libfprint-elan-DEBUG: 00:53:53.507: 7399801568476: ../libfprint/drivers/elan.c:379 384s (process:1952): libfprint-elan-DEBUG: 00:53:53.508: 7399801569176: ../libfprint/drivers/elan.c:346 384s (process:1952): libfprint-elan-DEBUG: 00:53:53.508: 7399801569206: ../libfprint/drivers/elan.c:335 384s (process:1952): libfprint-SSM-DEBUG: 00:53:53.508: [elan] CALIBRATE_NUM_STATES entering state 1 384s (process:1952): libfprint-elan-DEBUG: 00:53:53.508: 7399801569219: ../libfprint/drivers/elan.c:691 384s (process:1952): libfprint-elan-DEBUG: 00:53:53.508: 7399801569224: ../libfprint/drivers/elan.c:156 384s (process:1952): libfprint-elan-DEBUG: 00:53:53.508: 7399801569230: ../libfprint/drivers/elan.c:118 384s (process:1952): libfprint-SSM-DEBUG: 00:53:53.508: [elan] CALIBRATE_NUM_STATES entering state 2 384s (process:1952): libfprint-elan-DEBUG: 00:53:53.508: 7399801569246: ../libfprint/drivers/elan.c:691 384s (process:1952): libfprint-elan-DEBUG: 00:53:53.509: 7399801570068: ../libfprint/drivers/elan.c:346 384s (process:1952): libfprint-elan-DEBUG: 00:53:53.509: 7399801570198: ../libfprint/drivers/elan.c:366 384s (process:1952): libfprint-elan-DEBUG: 00:53:53.509: 7399801570211: ../libfprint/drivers/elan.c:379 384s (process:1952): libfprint-elan-DEBUG: 00:53:53.509: 7399801570868: ../libfprint/drivers/elan.c:346 384s (process:1952): libfprint-elan-DEBUG: 00:53:53.510: 7399801570930: ../libfprint/drivers/elan.c:335 384s (process:1952): libfprint-SSM-DEBUG: 00:53:53.510: [elan] CALIBRATE_NUM_STATES entering state 3 384s (process:1952): libfprint-elan-DEBUG: 00:53:53.510: 7399801571073: ../libfprint/drivers/elan.c:691 384s (process:1952): libfprint-elan-DEBUG: 00:53:53.510: 7399801571080: ../libfprint/drivers/elan.c:634 384s (process:1952): libfprint-elan-DEBUG: 00:53:53.510: calibration mean: 8339, bg mean: 8146, delta: 193 384s (process:1952): libfprint-SSM-DEBUG: 00:53:53.510: [elan] CALIBRATE_NUM_STATES completed successfully 384s (process:1952): libfprint-elan-DEBUG: 00:53:53.510: 7399801571124: ../libfprint/drivers/elan.c:776 384s (process:1952): libfprint-elan-DEBUG: 00:53:53.510: 7399801571144: ../libfprint/drivers/elan.c:620 384s (process:1952): libfprint-elan-DEBUG: 00:53:53.510: 7399801571149: ../libfprint/drivers/elan.c:100 384s (process:1952): libfprint-SSM-DEBUG: 00:53:53.510: [elan] CAPTURE_NUM_STATES entering state 0 384s (process:1952): libfprint-elan-DEBUG: 00:53:53.510: 7399801571776: ../libfprint/drivers/elan.c:346 384s (process:1952): libfprint-elan-DEBUG: 00:53:53.510: 7399801571793: ../libfprint/drivers/elan.c:366 384s (process:1952): libfprint-elan-DEBUG: 00:53:53.510: 7399801571798: ../libfprint/drivers/elan.c:379 384s (process:1952): libfprint-elan-DEBUG: 00:53:53.510: skipping read, not expecting anything 384s (process:1952): libfprint-elan-DEBUG: 00:53:53.510: 7399801571806: ../libfprint/drivers/elan.c:335 384s (process:1952): libfprint-SSM-DEBUG: 00:53:53.510: [elan] CAPTURE_NUM_STATES entering state 1 384s (process:1952): libfprint-elan-DEBUG: 00:53:53.511: 7399801572527: ../libfprint/drivers/elan.c:346 384s (process:1952): libfprint-elan-DEBUG: 00:53:53.511: 7399801572552: ../libfprint/drivers/elan.c:366 384s (process:1952): libfprint-elan-DEBUG: 00:53:53.511: 7399801572558: ../libfprint/drivers/elan.c:379 384s (process:1952): libfprint-elan-DEBUG: 00:53:53.512: 7399801573146: ../libfprint/drivers/elan.c:346 384s (process:1952): libfprint-elan-DEBUG: 00:53:53.512: 7399801573168: ../libfprint/drivers/elan.c:335 384s (process:1952): libfprint-SSM-DEBUG: 00:53:53.512: [elan] CAPTURE_NUM_STATES entering state 2 384s (process:1952): libfprint-device-DEBUG: 00:53:53.512: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 384s (process:1952): libfprint-image_device-DEBUG: 00:53:53.512: Image device reported finger status: on 384s (process:1952): libfprint-image_device-DEBUG: 00:53:53.512: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 384s (process:1952): libfprint-elan-DEBUG: 00:53:53.512: 7399801573211: ../libfprint/drivers/elan.c:960 384s (process:1952): libfprint-elan-DEBUG: 00:53:53.512: 7399801573770: ../libfprint/drivers/elan.c:346 384s (process:1952): libfprint-elan-DEBUG: 00:53:53.512: 7399801573788: ../libfprint/drivers/elan.c:366 384s (process:1952): libfprint-elan-DEBUG: 00:53:53.512: 7399801573793: ../libfprint/drivers/elan.c:379 384s (process:1952): libfprint-elan-DEBUG: 00:53:53.513: 7399801574401: ../libfprint/drivers/elan.c:346 384s (process:1952): libfprint-elan-DEBUG: 00:53:53.513: 7399801574427: ../libfprint/drivers/elan.c:335 384s (process:1952): libfprint-SSM-DEBUG: 00:53:53.513: [elan] CAPTURE_NUM_STATES entering state 3 384s (process:1952): libfprint-elan-DEBUG: 00:53:53.513: 7399801574439: ../libfprint/drivers/elan.c:203 384s (process:1952): libfprint-elan-DEBUG: 00:53:53.513: 7399801574459: ../libfprint/drivers/elan.c:118 384s (process:1952): libfprint-SSM-DEBUG: 00:53:53.513: [elan] CAPTURE_NUM_STATES entering state 1 384s (process:1952): libfprint-elan-DEBUG: 00:53:53.514: 7399801575087: ../libfprint/drivers/elan.c:346 384s (process:1952): libfprint-elan-DEBUG: 00:53:53.514: 7399801575111: ../libfprint/drivers/elan.c:366 384s (process:1952): libfprint-elan-DEBUG: 00:53:53.514: 7399801575117: ../libfprint/drivers/elan.c:379 384s (process:1952): libfprint-elan-DEBUG: 00:53:53.514: 7399801575647: ../libfprint/drivers/elan.c:346 384s (process:1952): libfprint-elan-DEBUG: 00:53:53.514: 7399801575680: ../libfprint/drivers/elan.c:335 384s (process:1952): libfprint-SSM-DEBUG: 00:53:53.514: [elan] CAPTURE_NUM_STATES entering state 2 384s (process:1952): libfprint-image_device-DEBUG: 00:53:53.514: Image device reported finger status: on 384s (process:1952): libfprint-elan-DEBUG: 00:53:53.515: 7399801576412: ../libfprint/drivers/elan.c:346 384s (process:1952): libfprint-elan-DEBUG: 00:53:53.515: 7399801576434: ../libfprint/drivers/elan.c:366 384s (process:1952): libfprint-elan-DEBUG: 00:53:53.515: 7399801576440: ../libfprint/drivers/elan.c:379 384s (process:1952): libfprint-elan-DEBUG: 00:53:53.516: 7399801577042: ../libfprint/drivers/elan.c:346 384s (process:1952): libfprint-elan-DEBUG: 00:53:53.516: 7399801577068: ../libfprint/drivers/elan.c:335 384s (process:1952): libfprint-SSM-DEBUG: 00:53:53.516: [elan] CAPTURE_NUM_STATES entering state 3 384s (process:1952): libfprint-elan-DEBUG: 00:53:53.516: 7399801577080: ../libfprint/drivers/elan.c:203 384s (process:1952): libfprint-elan-DEBUG: 00:53:53.516: 7399801577101: ../libfprint/drivers/elan.c:118 384s (process:1952): libfprint-SSM-DEBUG: 00:53:53.516: [elan] CAPTURE_NUM_STATES entering state 1 384s (process:1952): libfprint-elan-DEBUG: 00:53:53.517: 7399801577916: ../libfprint/drivers/elan.c:346 384s (process:1952): libfprint-elan-DEBUG: 00:53:53.517: 7399801577942: ../libfprint/drivers/elan.c:366 384s (process:1952): libfprint-elan-DEBUG: 00:53:53.517: 7399801577949: ../libfprint/drivers/elan.c:379 384s (process:1952): libfprint-elan-DEBUG: 00:53:53.517: 7399801578560: ../libfprint/drivers/elan.c:346 384s (process:1952): libfprint-elan-DEBUG: 00:53:53.517: 7399801578583: ../libfprint/drivers/elan.c:335 384s (process:1952): libfprint-SSM-DEBUG: 00:53:53.517: [elan] CAPTURE_NUM_STATES entering state 2 384s (process:1952): libfprint-image_device-DEBUG: 00:53:53.517: Image device reported finger status: on 384s (process:1952): libfprint-elan-DEBUG: 00:53:53.518: 7399801579187: ../libfprint/drivers/elan.c:346 384s (process:1952): libfprint-elan-DEBUG: 00:53:53.518: 7399801579207: ../libfprint/drivers/elan.c:366 384s (process:1952): libfprint-elan-DEBUG: 00:53:53.518: 7399801579213: ../libfprint/drivers/elan.c:379 384s (process:1952): libfprint-elan-DEBUG: 00:53:53.518: 7399801579801: ../libfprint/drivers/elan.c:346 384s (process:1952): libfprint-elan-DEBUG: 00:53:53.518: 7399801579821: ../libfprint/drivers/elan.c:335 384s (process:1952): libfprint-SSM-DEBUG: 00:53:53.518: [elan] CAPTURE_NUM_STATES entering state 3 384s (process:1952): libfprint-elan-DEBUG: 00:53:53.518: 7399801579832: ../libfprint/drivers/elan.c:203 384s (process:1952): libfprint-elan-DEBUG: 00:53:53.518: 7399801579863: ../libfprint/drivers/elan.c:118 384s (process:1952): libfprint-SSM-DEBUG: 00:53:53.518: [elan] CAPTURE_NUM_STATES entering state 1 384s (process:1952): libfprint-elan-DEBUG: 00:53:53.519: 7399801580417: ../libfprint/drivers/elan.c:346 384s (process:1952): libfprint-elan-DEBUG: 00:53:53.519: 7399801580439: ../libfprint/drivers/elan.c:366 384s (process:1952): libfprint-elan-DEBUG: 00:53:53.519: 7399801580445: ../libfprint/drivers/elan.c:379 384s (process:1952): libfprint-elan-DEBUG: 00:53:53.520: 7399801580977: ../libfprint/drivers/elan.c:346 384s (process:1952): libfprint-elan-DEBUG: 00:53:53.520: 7399801580993: ../libfprint/drivers/elan.c:335 384s (process:1952): libfprint-SSM-DEBUG: 00:53:53.520: [elan] CAPTURE_NUM_STATES entering state 2 384s (process:1952): libfprint-image_device-DEBUG: 00:53:53.520: Image device reported finger status: on 384s (process:1952): libfprint-elan-DEBUG: 00:53:53.520: 7399801581692: ../libfprint/drivers/elan.c:346 384s (process:1952): libfprint-elan-DEBUG: 00:53:53.520: 7399801581712: ../libfprint/drivers/elan.c:366 384s (process:1952): libfprint-elan-DEBUG: 00:53:53.520: 7399801581718: ../libfprint/drivers/elan.c:379 384s (process:1952): libfprint-elan-DEBUG: 00:53:53.521: 7399801582348: ../libfprint/drivers/elan.c:346 384s (process:1952): libfprint-elan-DEBUG: 00:53:53.521: 7399801582375: ../libfprint/drivers/elan.c:335 384s (process:1952): libfprint-SSM-DEBUG: 00:53:53.521: [elan] CAPTURE_NUM_STATES entering state 3 384s (process:1952): libfprint-elan-DEBUG: 00:53:53.521: 7399801582386: ../libfprint/drivers/elan.c:203 384s (process:1952): libfprint-elan-DEBUG: 00:53:53.521: 7399801582405: ../libfprint/drivers/elan.c:118 384s (process:1952): libfprint-SSM-DEBUG: 00:53:53.521: [elan] CAPTURE_NUM_STATES entering state 1 384s (process:1952): libfprint-elan-DEBUG: 00:53:53.522: 7399801583043: ../libfprint/drivers/elan.c:346 384s (process:1952): libfprint-elan-DEBUG: 00:53:53.522: 7399801583067: ../libfprint/drivers/elan.c:366 384s (process:1952): libfprint-elan-DEBUG: 00:53:53.522: 7399801583073: ../libfprint/drivers/elan.c:379 384s (process:1952): libfprint-elan-DEBUG: 00:53:53.522: 7399801583601: ../libfprint/drivers/elan.c:346 384s (process:1952): libfprint-elan-DEBUG: 00:53:53.522: 7399801583618: ../libfprint/drivers/elan.c:335 384s (process:1952): libfprint-SSM-DEBUG: 00:53:53.522: [elan] CAPTURE_NUM_STATES entering state 2 384s (process:1952): libfprint-image_device-DEBUG: 00:53:53.522: Image device reported finger status: on 384s (process:1952): libfprint-elan-DEBUG: 00:53:53.523: 7399801584169: ../libfprint/drivers/elan.c:346 384s (process:1952): libfprint-elan-DEBUG: 00:53:53.523: 7399801584193: ../libfprint/drivers/elan.c:366 384s (process:1952): libfprint-elan-DEBUG: 00:53:53.523: 7399801584199: ../libfprint/drivers/elan.c:379 384s (process:1952): libfprint-elan-DEBUG: 00:53:53.523: 7399801584803: ../libfprint/drivers/elan.c:346 384s (process:1952): libfprint-elan-DEBUG: 00:53:53.523: 7399801584824: ../libfprint/drivers/elan.c:335 384s (process:1952): libfprint-SSM-DEBUG: 00:53:53.523: [elan] CAPTURE_NUM_STATES entering state 3 384s (process:1952): libfprint-elan-DEBUG: 00:53:53.523: 7399801584833: ../libfprint/drivers/elan.c:203 384s (process:1952): libfprint-elan-DEBUG: 00:53:53.523: 7399801584849: ../libfprint/drivers/elan.c:118 384s (process:1952): libfprint-SSM-DEBUG: 00:53:53.523: [elan] CAPTURE_NUM_STATES entering state 1 384s (process:1952): libfprint-elan-DEBUG: 00:53:53.524: 7399801585425: ../libfprint/drivers/elan.c:346 384s (process:1952): libfprint-elan-DEBUG: 00:53:53.524: 7399801585448: ../libfprint/drivers/elan.c:366 384s (process:1952): libfprint-elan-DEBUG: 00:53:53.524: 7399801585454: ../libfprint/drivers/elan.c:379 384s (process:1952): libfprint-elan-DEBUG: 00:53:53.525: 7399801586045: ../libfprint/drivers/elan.c:346 384s (process:1952): libfprint-elan-DEBUG: 00:53:53.525: 7399801586070: ../libfprint/drivers/elan.c:335 384s (process:1952): libfprint-SSM-DEBUG: 00:53:53.525: [elan] CAPTURE_NUM_STATES entering state 2 384s (process:1952): libfprint-image_device-DEBUG: 00:53:53.525: Image device reported finger status: on 384s (process:1952): libfprint-elan-DEBUG: 00:53:53.525: 7399801586574: ../libfprint/drivers/elan.c:346 384s (process:1952): libfprint-elan-DEBUG: 00:53:53.525: 7399801586592: ../libfprint/drivers/elan.c:366 384s (process:1952): libfprint-elan-DEBUG: 00:53:53.525: 7399801586596: ../libfprint/drivers/elan.c:379 384s (process:1952): libfprint-elan-DEBUG: 00:53:53.526: 7399801587210: ../libfprint/drivers/elan.c:346 384s (process:1952): libfprint-elan-DEBUG: 00:53:53.526: 7399801587238: ../libfprint/drivers/elan.c:335 384s (process:1952): libfprint-SSM-DEBUG: 00:53:53.526: [elan] CAPTURE_NUM_STATES entering state 3 384s (process:1952): libfprint-elan-DEBUG: 00:53:53.526: 7399801587249: ../libfprint/drivers/elan.c:203 384s (process:1952): libfprint-elan-DEBUG: 00:53:53.526: 7399801587265: ../libfprint/drivers/elan.c:118 384s (process:1952): libfprint-SSM-DEBUG: 00:53:53.526: [elan] CAPTURE_NUM_STATES entering state 1 384s (process:1952): libfprint-elan-DEBUG: 00:53:53.526: 7399801587822: ../libfprint/drivers/elan.c:346 384s (process:1952): libfprint-elan-DEBUG: 00:53:53.526: 7399801587839: ../libfprint/drivers/elan.c:366 384s (process:1952): libfprint-elan-DEBUG: 00:53:53.526: 7399801587846: ../libfprint/drivers/elan.c:379 384s (process:1952): libfprint-elan-DEBUG: 00:53:53.527: 7399801588374: ../libfprint/drivers/elan.c:346 384s (process:1952): libfprint-elan-DEBUG: 00:53:53.527: 7399801588396: ../libfprint/drivers/elan.c:335 384s (process:1952): libfprint-SSM-DEBUG: 00:53:53.527: [elan] CAPTURE_NUM_STATES entering state 2 384s (process:1952): libfprint-image_device-DEBUG: 00:53:53.527: Image device reported finger status: on 384s (process:1952): libfprint-elan-DEBUG: 00:53:53.528: 7399801588946: ../libfprint/drivers/elan.c:346 384s (process:1952): libfprint-elan-DEBUG: 00:53:53.528: 7399801588963: ../libfprint/drivers/elan.c:366 384s (process:1952): libfprint-elan-DEBUG: 00:53:53.528: 7399801588969: ../libfprint/drivers/elan.c:379 384s (process:1952): libfprint-elan-DEBUG: 00:53:53.528: 7399801589585: ../libfprint/drivers/elan.c:346 384s (process:1952): libfprint-elan-DEBUG: 00:53:53.528: 7399801589612: ../libfprint/drivers/elan.c:335 384s (process:1952): libfprint-SSM-DEBUG: 00:53:53.528: [elan] CAPTURE_NUM_STATES entering state 3 384s (process:1952): libfprint-elan-DEBUG: 00:53:53.528: 7399801589624: ../libfprint/drivers/elan.c:203 384s (process:1952): libfprint-elan-DEBUG: 00:53:53.528: 7399801589641: ../libfprint/drivers/elan.c:118 384s (process:1952): libfprint-SSM-DEBUG: 00:53:53.528: [elan] CAPTURE_NUM_STATES entering state 1 384s (process:1952): libfprint-elan-DEBUG: 00:53:53.529: 7399801590410: ../libfprint/drivers/elan.c:346 384s (process:1952): libfprint-elan-DEBUG: 00:53:53.529: 7399801590434: ../libfprint/drivers/elan.c:366 384s (process:1952): libfprint-elan-DEBUG: 00:53:53.529: 7399801590440: ../libfprint/drivers/elan.c:379 384s (process:1952): libfprint-elan-DEBUG: 00:53:53.530: 7399801590991: ../libfprint/drivers/elan.c:346 384s (process:1952): libfprint-elan-DEBUG: 00:53:53.530: 7399801591028: ../libfprint/drivers/elan.c:335 384s (process:1952): libfprint-SSM-DEBUG: 00:53:53.530: [elan] CAPTURE_NUM_STATES entering state 2 384s (process:1952): libfprint-image_device-DEBUG: 00:53:53.530: Image device reported finger status: on 384s (process:1952): libfprint-elan-DEBUG: 00:53:53.530: 7399801591560: ../libfprint/drivers/elan.c:346 384s (process:1952): libfprint-elan-DEBUG: 00:53:53.530: 7399801591576: ../libfprint/drivers/elan.c:366 384s (process:1952): libfprint-elan-DEBUG: 00:53:53.530: 7399801591581: ../libfprint/drivers/elan.c:379 384s (process:1952): libfprint-elan-DEBUG: 00:53:53.531: 7399801592194: ../libfprint/drivers/elan.c:346 384s (process:1952): libfprint-elan-DEBUG: 00:53:53.531: 7399801592225: ../libfprint/drivers/elan.c:335 384s (process:1952): libfprint-SSM-DEBUG: 00:53:53.531: [elan] CAPTURE_NUM_STATES entering state 3 384s (process:1952): libfprint-elan-DEBUG: 00:53:53.531: 7399801592236: ../libfprint/drivers/elan.c:203 384s (process:1952): libfprint-elan-DEBUG: 00:53:53.531: 7399801592252: ../libfprint/drivers/elan.c:118 384s (process:1952): libfprint-SSM-DEBUG: 00:53:53.531: [elan] CAPTURE_NUM_STATES entering state 1 384s (process:1952): libfprint-elan-DEBUG: 00:53:53.532: 7399801593262: ../libfprint/drivers/elan.c:346 384s (process:1952): libfprint-elan-DEBUG: 00:53:53.532: 7399801593295: ../libfprint/drivers/elan.c:366 384s (process:1952): libfprint-elan-DEBUG: 00:53:53.532: 7399801593301: ../libfprint/drivers/elan.c:379 384s (process:1952): libfprint-elan-DEBUG: 00:53:53.533: 7399801594056: ../libfprint/drivers/elan.c:346 384s (process:1952): libfprint-elan-DEBUG: 00:53:53.533: 7399801594097: ../libfprint/drivers/elan.c:335 384s (process:1952): libfprint-SSM-DEBUG: 00:53:53.533: [elan] CAPTURE_NUM_STATES entering state 2 384s (process:1952): libfprint-image_device-DEBUG: 00:53:53.533: Image device reported finger status: on 384s (process:1952): libfprint-elan-DEBUG: 00:53:53.533: 7399801594691: ../libfprint/drivers/elan.c:346 384s (process:1952): libfprint-elan-DEBUG: 00:53:53.533: 7399801594716: ../libfprint/drivers/elan.c:366 384s (process:1952): libfprint-elan-DEBUG: 00:53:53.533: 7399801594722: ../libfprint/drivers/elan.c:379 384s (process:1952): libfprint-elan-DEBUG: 00:53:53.534: 7399801595383: ../libfprint/drivers/elan.c:346 384s (process:1952): libfprint-elan-DEBUG: 00:53:53.534: 7399801595409: ../libfprint/drivers/elan.c:335 384s (process:1952): libfprint-SSM-DEBUG: 00:53:53.534: [elan] CAPTURE_NUM_STATES entering state 3 384s (process:1952): libfprint-elan-DEBUG: 00:53:53.534: 7399801595439: ../libfprint/drivers/elan.c:203 384s (process:1952): libfprint-elan-DEBUG: 00:53:53.534: 7399801595459: ../libfprint/drivers/elan.c:118 384s (process:1952): libfprint-SSM-DEBUG: 00:53:53.534: [elan] CAPTURE_NUM_STATES entering state 1 384s (process:1952): libfprint-elan-DEBUG: 00:53:53.535: 7399801596177: ../libfprint/drivers/elan.c:346 384s (process:1952): libfprint-elan-DEBUG: 00:53:53.535: 7399801596208: ../libfprint/drivers/elan.c:366 384s (process:1952): libfprint-elan-DEBUG: 00:53:53.535: 7399801596215: ../libfprint/drivers/elan.c:379 384s (process:1952): libfprint-elan-DEBUG: 00:53:53.535: 7399801596863: ../libfprint/drivers/elan.c:346 384s (process:1952): libfprint-elan-DEBUG: 00:53:53.535: 7399801596881: ../libfprint/drivers/elan.c:335 384s (process:1952): libfprint-SSM-DEBUG: 00:53:53.535: [elan] CAPTURE_NUM_STATES entering state 2 384s (process:1952): libfprint-image_device-DEBUG: 00:53:53.535: Image device reported finger status: on 384s (process:1952): libfprint-elan-DEBUG: 00:53:53.536: 7399801597536: ../libfprint/drivers/elan.c:346 384s (process:1952): libfprint-elan-DEBUG: 00:53:53.536: 7399801597615: ../libfprint/drivers/elan.c:366 384s (process:1952): libfprint-elan-DEBUG: 00:53:53.536: 7399801597622: ../libfprint/drivers/elan.c:379 384s (process:1952): libfprint-elan-DEBUG: 00:53:53.537: 7399801598327: ../libfprint/drivers/elan.c:346 384s (process:1952): libfprint-elan-DEBUG: 00:53:53.537: 7399801598372: ../libfprint/drivers/elan.c:335 384s (process:1952): libfprint-SSM-DEBUG: 00:53:53.537: [elan] CAPTURE_NUM_STATES entering state 3 384s (process:1952): libfprint-elan-DEBUG: 00:53:53.537: 7399801598388: ../libfprint/drivers/elan.c:203 384s (process:1952): libfprint-elan-DEBUG: 00:53:53.537: 7399801598405: ../libfprint/drivers/elan.c:118 384s (process:1952): libfprint-SSM-DEBUG: 00:53:53.537: [elan] CAPTURE_NUM_STATES entering state 1 384s (process:1952): libfprint-elan-DEBUG: 00:53:53.538: 7399801599140: ../libfprint/drivers/elan.c:346 384s (process:1952): libfprint-elan-DEBUG: 00:53:53.538: 7399801599164: ../libfprint/drivers/elan.c:366 384s (process:1952): libfprint-elan-DEBUG: 00:53:53.538: 7399801599175: ../libfprint/drivers/elan.c:379 384s (process:1952): libfprint-elan-DEBUG: 00:53:53.539: 7399801599919: ../libfprint/drivers/elan.c:346 384s (process:1952): libfprint-elan-DEBUG: 00:53:53.539: 7399801599943: ../libfprint/drivers/elan.c:335 384s (process:1952): libfprint-SSM-DEBUG: 00:53:53.539: [elan] CAPTURE_NUM_STATES entering state 2 384s (process:1952): libfprint-image_device-DEBUG: 00:53:53.539: Image device reported finger status: on 384s (process:1952): libfprint-elan-DEBUG: 00:53:53.539: 7399801600533: ../libfprint/drivers/elan.c:346 384s (process:1952): libfprint-elan-DEBUG: 00:53:53.539: 7399801600558: ../libfprint/drivers/elan.c:366 384s (process:1952): libfprint-elan-DEBUG: 00:53:53.539: 7399801600565: ../libfprint/drivers/elan.c:379 384s (process:1952): libfprint-elan-DEBUG: 00:53:53.540: 7399801601231: ../libfprint/drivers/elan.c:346 384s (process:1952): libfprint-elan-DEBUG: 00:53:53.540: 7399801601257: ../libfprint/drivers/elan.c:335 384s (process:1952): libfprint-SSM-DEBUG: 00:53:53.540: [elan] CAPTURE_NUM_STATES entering state 3 384s (process:1952): libfprint-elan-DEBUG: 00:53:53.540: 7399801601269: ../libfprint/drivers/elan.c:203 384s (process:1952): libfprint-elan-DEBUG: 00:53:53.540: 7399801601445: ../libfprint/drivers/elan.c:118 384s (process:1952): libfprint-SSM-DEBUG: 00:53:53.540: [elan] CAPTURE_NUM_STATES entering state 1 384s (process:1952): libfprint-elan-DEBUG: 00:53:53.541: 7399801601927: ../libfprint/drivers/elan.c:346 384s (process:1952): libfprint-elan-DEBUG: 00:53:53.541: 7399801601943: ../libfprint/drivers/elan.c:366 384s (process:1952): libfprint-elan-DEBUG: 00:53:53.541: 7399801601951: ../libfprint/drivers/elan.c:379 384s (process:1952): libfprint-elan-DEBUG: 00:53:53.541: 7399801602529: ../libfprint/drivers/elan.c:346 384s (process:1952): libfprint-elan-DEBUG: 00:53:53.541: 7399801602550: ../libfprint/drivers/elan.c:335 384s (process:1952): libfprint-SSM-DEBUG: 00:53:53.541: [elan] CAPTURE_NUM_STATES entering state 2 384s (process:1952): libfprint-image_device-DEBUG: 00:53:53.541: Image device reported finger status: on 384s (process:1952): libfprint-elan-DEBUG: 00:53:53.542: 7399801603144: ../libfprint/drivers/elan.c:346 384s (process:1952): libfprint-elan-DEBUG: 00:53:53.542: 7399801603166: ../libfprint/drivers/elan.c:366 384s (process:1952): libfprint-elan-DEBUG: 00:53:53.542: 7399801603171: ../libfprint/drivers/elan.c:379 384s (process:1952): libfprint-elan-DEBUG: 00:53:53.542: 7399801603806: ../libfprint/drivers/elan.c:346 384s (process:1952): libfprint-elan-DEBUG: 00:53:53.542: 7399801603828: ../libfprint/drivers/elan.c:335 384s (process:1952): libfprint-SSM-DEBUG: 00:53:53.542: [elan] CAPTURE_NUM_STATES entering state 3 384s (process:1952): libfprint-elan-DEBUG: 00:53:53.542: 7399801603837: ../libfprint/drivers/elan.c:203 384s (process:1952): libfprint-elan-DEBUG: 00:53:53.542: 7399801603856: ../libfprint/drivers/elan.c:118 384s (process:1952): libfprint-SSM-DEBUG: 00:53:53.542: [elan] CAPTURE_NUM_STATES entering state 1 384s (process:1952): libfprint-elan-DEBUG: 00:53:53.543: 7399801604452: ../libfprint/drivers/elan.c:346 384s (process:1952): libfprint-elan-DEBUG: 00:53:53.543: 7399801604476: ../libfprint/drivers/elan.c:366 384s (process:1952): libfprint-elan-DEBUG: 00:53:53.543: 7399801604481: ../libfprint/drivers/elan.c:379 384s (process:1952): libfprint-elan-DEBUG: 00:53:53.544: 7399801605018: ../libfprint/drivers/elan.c:346 384s (process:1952): libfprint-elan-DEBUG: 00:53:53.544: 7399801605037: ../libfprint/drivers/elan.c:335 384s (process:1952): libfprint-SSM-DEBUG: 00:53:53.544: [elan] CAPTURE_NUM_STATES entering state 2 384s (process:1952): libfprint-SSM-DEBUG: 00:53:53.544: [elan] CAPTURE_NUM_STATES completed successfully 384s (process:1952): libfprint-elan-DEBUG: 00:53:53.544: 7399801605059: ../libfprint/drivers/elan.c:586 384s (process:1952): libfprint-elan-DEBUG: 00:53:53.544: 7399801605064: ../libfprint/drivers/elan.c:315 384s (process:1952): libfprint-elan-DEBUG: 00:53:53.544: 7399801605073: ../libfprint/drivers/elan.c:272 384s (process:1952): libfprint-elan-DEBUG: 00:53:53.544: 7399801605885: ../libfprint/drivers/elan.c:272 384s (process:1952): libfprint-elan-DEBUG: 00:53:53.545: 7399801606717: ../libfprint/drivers/elan.c:272 384s (process:1952): libfprint-elan-DEBUG: 00:53:53.546: 7399801607488: ../libfprint/drivers/elan.c:272 384s (process:1952): libfprint-elan-DEBUG: 00:53:53.547: 7399801608274: ../libfprint/drivers/elan.c:272 384s (process:1952): libfprint-elan-DEBUG: 00:53:53.548: 7399801609070: ../libfprint/drivers/elan.c:272 384s (process:1952): libfprint-elan-DEBUG: 00:53:53.548: 7399801609851: ../libfprint/drivers/elan.c:272 384s (process:1952): libfprint-elan-DEBUG: 00:53:53.549: 7399801610625: ../libfprint/drivers/elan.c:272 384s (process:1952): libfprint-elan-DEBUG: 00:53:53.550: 7399801611418: ../libfprint/drivers/elan.c:272 384s (process:1952): libfprint-elan-DEBUG: 00:53:53.551: 7399801612205: ../libfprint/drivers/elan.c:272 384s (process:1952): libfprint-assembling-DEBUG: 00:53:53.694: calc delta completed in 0.142831 secs 384s (process:1952): libfprint-assembling-DEBUG: 00:53:53.838: calc delta completed in 0.143651 secs 384s (process:1952): libfprint-assembling-DEBUG: 00:53:53.838: errors: 233151 rev: 207411 384s (process:1952): libfprint-assembling-DEBUG: 00:53:53.838: height is -185 384s (process:1952): libfprint-image_device-DEBUG: 00:53:53.839: Image device captured an image 384s (process:1952): libfprint-image_device-DEBUG: 00:53:53.840: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 384s (process:1952): libfprint-elan-DEBUG: 00:53:53.840: 7399801901869: ../libfprint/drivers/elan.c:960 384s (process:1952): libfprint-device-DEBUG: 00:53:53.840: Device reported finger status change: FP_FINGER_STATUS_PRESENT 384s (process:1952): libfprint-elan-DEBUG: 00:53:53.840: 7399801901892: ../libfprint/drivers/elan.c:507 384s (process:1952): libfprint-elan-DEBUG: 00:53:53.840: 7399801901897: ../libfprint/drivers/elan.c:100 384s (process:1952): libfprint-SSM-DEBUG: 00:53:53.840: [elan] STOP_CAPTURE_NUM_STATES entering state 0 384s (process:1952): libfprint-elan-DEBUG: 00:53:53.840: 7399801901910: ../libfprint/drivers/elan.c:466 384s (process:1952): libfprint-elan-DEBUG: 00:53:53.841: 7399801902586: ../libfprint/drivers/elan.c:346 384s (process:1952): libfprint-elan-DEBUG: 00:53:53.841: 7399801902613: ../libfprint/drivers/elan.c:366 384s (process:1952): libfprint-elan-DEBUG: 00:53:53.841: 7399801902620: ../libfprint/drivers/elan.c:379 384s (process:1952): libfprint-elan-DEBUG: 00:53:53.841: skipping read, not expecting anything 384s (process:1952): libfprint-elan-DEBUG: 00:53:53.841: 7399801902627: ../libfprint/drivers/elan.c:335 384s (process:1952): libfprint-SSM-DEBUG: 00:53:53.841: [elan] STOP_CAPTURE_NUM_STATES completed successfully 384s (process:1952): libfprint-elan-DEBUG: 00:53:53.841: 7399801902637: ../libfprint/drivers/elan.c:483 384s (process:1952): libfprint-device-DEBUG: 00:53:53.841: Device reported finger status change: FP_FINGER_STATUS_NONE 384s (process:1952): libfprint-image_device-DEBUG: 00:53:53.841: Image device reported finger status: off 384s (process:1952): libfprint-image_device-DEBUG: 00:53:53.841: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 384s (process:1952): libfprint-elan-DEBUG: 00:53:53.841: 7399801902680: ../libfprint/drivers/elan.c:960 384s (process:1952): libfprint-image_device-DEBUG: 00:53:53.841: Deactivating image device 384s (process:1952): libfprint-image_device-DEBUG: 00:53:53.841: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_DEACTIVATING 384s (process:1952): libfprint-elan-DEBUG: 00:53:53.841: 7399801902696: ../libfprint/drivers/elan.c:960 384s (process:1952): libfprint-elan-DEBUG: 00:53:53.841: 7399801902700: ../libfprint/drivers/elan.c:975 384s (process:1952): libfprint-image_device-DEBUG: 00:53:53.841: Image device deactivation completed 384s (process:1952): libfprint-image_device-DEBUG: 00:53:53.841: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE 384s (process:1952): libfprint-elan-DEBUG: 00:53:53.841: 7399801902719: ../libfprint/drivers/elan.c:960 384s (process:1952): libfprint-image-DEBUG: 00:53:53.856: Minutiae scan completed in 0.015504 secs 384s (process:1952): libfprint-device-DEBUG: 00:53:53.856: Device reported capture completion 384s (process:1952): libfprint-device-DEBUG: 00:53:53.856: Completing action FPI_DEVICE_ACTION_CAPTURE in idle! 384s (process:1952): libfprint-device-DEBUG: 00:53:53.856: Updated temperature model after 0.51 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 384s (process:1952): libfprint-elan-DEBUG: 00:53:53.856: 7399801917812: ../libfprint/drivers/elan.c:939 384s (process:1952): libfprint-elan-DEBUG: 00:53:53.856: 7399801917820: ../libfprint/drivers/elan.c:100 384s (process:1952): libfprint-image_device-DEBUG: 00:53:53.857: Image device close completed 384s (process:1952): libfprint-device-DEBUG: 00:53:53.857: Device reported close completion 384s (process:1952): libfprint-device-DEBUG: 00:53:53.857: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 384s (process:1952): libfprint-device-DEBUG: 00:53:53.857: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 385s ** (umockdev-run:1948): DEBUG: 00:53:53.962: umockdev.vala:154: Removing test bed /tmp/umockdev.BJQ012 385s (umockdev-run:1948): GLib-DEBUG: 00:53:53.971: unsetenv() is not thread-safe and should not be used after threads are created 385s Comparing PNGs /tmp/libfprint-umockdev-test-hwjdlfxr/capture.png and /usr/share/installed-tests/libfprint-2/elan/capture.png 385s PASS: libfprint-2/driver-elan.test 385s Running test: libfprint-2/virtual-image.test 385s (process:1959): libfprint-context-DEBUG: 00:53:54.165: Initializing FpContext (libfprint version 1.94.8+tod1) 385s (process:1959): libfprint-tod-DEBUG: 00:53:54.165: Impossible to load the shared drivers dir Error opening directory “/usr/lib/arm-linux-gnueabihf/libfprint-2/tod-1”: No such file or directory 385s (process:1959): libfprint-context-DEBUG: 00:53:54.169: No driver found for USB device 1D6B:0003 385s (process:1959): libfprint-context-DEBUG: 00:53:54.169: No driver found for USB device 0627:0001 385s (process:1959): libfprint-context-DEBUG: 00:53:54.169: No driver found for USB device 1D6B:0002 385s (process:1959): libfprint-context-DEBUG: 00:53:54.169: Found virtual environment device: FP_VIRTUAL_IMAGE, /tmp/libfprint-44_fazov/virtual-image.socket 385s (process:1959): libfprint-context-DEBUG: 00:53:54.169: created 385s (process:1959): libfprint-device-DEBUG: 00:53:54.170: Device reported probe completion 385s (process:1959): libfprint-device-DEBUG: 00:53:54.170: Completing action FPI_DEVICE_ACTION_PROBE in idle! 385s (process:1959): libfprint-device-DEBUG: 00:53:54.170: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 385s test_capture_prevents_close (__main__.VirtualImage.test_capture_prevents_close) ... (process:1959): libfprint-virtual_image-DEBUG: 00:53:54.177: 7399802238728: ../libfprint/drivers/virtual-image.c:216 385s (process:1959): libfprint-virtual_device_connection-DEBUG: 00:53:54.177: 7399802238847: ../libfprint/drivers/virtual-device-listener.c:153 385s (process:1959): libfprint-image_device-DEBUG: 00:53:54.278: Image device open completed 385s (process:1959): libfprint-device-DEBUG: 00:53:54.278: Device reported open completion 385s (process:1959): libfprint-device-DEBUG: 00:53:54.278: Completing action FPI_DEVICE_ACTION_OPEN in idle! 385s (process:1959): libfprint-device-DEBUG: 00:53:54.278: Updated temperature model after 0.11 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 385s (process:1959): libfprint-device-DEBUG: 00:53:54.279: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 385s (process:1959): libfprint-image_device-DEBUG: 00:53:54.279: Activating image device 385s (process:1959): libfprint-image_device-DEBUG: 00:53:54.279: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING 385s (process:1959): libfprint-image_device-DEBUG: 00:53:54.279: Image device activation completed 385s (process:1959): libfprint-image_device-DEBUG: 00:53:54.279: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE 385s (process:1959): libfprint-image_device-DEBUG: 00:53:54.279: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 385s (process:1959): libfprint-device-DEBUG: 00:53:54.279: Device reported finger status change: FP_FINGER_STATUS_NEEDED 385s (process:1959): libfprint-virtual_device_connection-DEBUG: 00:53:54.279: Got a new connection! 385s (process:1959): libfprint-device-DEBUG: 00:53:54.280: Idle cancelling on ongoing operation! 385s (process:1959): libfprint-image_device-DEBUG: 00:53:54.280: Deactivating image device 385s (process:1959): libfprint-image_device-DEBUG: 00:53:54.280: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_DEACTIVATING 385s (process:1959): libfprint-image_device-DEBUG: 00:53:54.280: Image device deactivation completed 385s (process:1959): libfprint-image_device-DEBUG: 00:53:54.280: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE 385s (process:1959): libfprint-device-DEBUG: 00:53:54.280: Device reported generic error (Operation was cancelled) during action; action was: FPI_DEVICE_ACTION_CAPTURE 385s (process:1959): libfprint-device-DEBUG: 00:53:54.280: Device reported capture completion 385s (process:1959): libfprint-device-DEBUG: 00:53:54.280: Device reported finger status change: FP_FINGER_STATUS_NONE 385s (process:1959): libfprint-device-DEBUG: 00:53:54.280: Completing action FPI_DEVICE_ACTION_CAPTURE in idle! 385s (process:1959): libfprint-device-DEBUG: 00:53:54.280: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 385s (process:1959): libfprint-virtual_image-DEBUG: 00:53:54.281: 7399802342392: ../libfprint/drivers/virtual-image.c:244 385s (process:1959): libfprint-image_device-DEBUG: 00:53:54.381: Image device close completed 385s (process:1959): libfprint-device-DEBUG: 00:53:54.381: Device reported close completion 385s (process:1959): libfprint-device-DEBUG: 00:53:54.381: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 385s (process:1959): libfprint-device-DEBUG: 00:53:54.381: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 385s Capture operation finished 385s Capture cancelled as expected 385s ok 385s test_enroll_verify (__main__.VirtualImage.test_enroll_verify) ... (process:1959): libfprint-virtual_image-DEBUG: 00:53:54.382: 7399802443030: ../libfprint/drivers/virtual-image.c:216 385s (process:1959): libfprint-virtual_device_connection-DEBUG: 00:53:54.382: 7399802443055: ../libfprint/drivers/virtual-device-listener.c:153 385s (process:1959): libfprint-image_device-DEBUG: 00:53:54.482: Image device open completed 385s (process:1959): libfprint-device-DEBUG: 00:53:54.482: Device reported open completion 385s (process:1959): libfprint-device-DEBUG: 00:53:54.482: Completing action FPI_DEVICE_ACTION_OPEN in idle! 385s (process:1959): libfprint-device-DEBUG: 00:53:54.482: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 385s (process:1959): libfprint-device-DEBUG: 00:53:54.483: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 385s (process:1959): libfprint-image_device-DEBUG: 00:53:54.483: Activating image device 385s (process:1959): libfprint-image_device-DEBUG: 00:53:54.483: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING 385s (process:1959): libfprint-image_device-DEBUG: 00:53:54.484: Image device activation completed 385s (process:1959): libfprint-image_device-DEBUG: 00:53:54.484: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE 385s (process:1959): libfprint-image_device-DEBUG: 00:53:54.484: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 385s (process:1959): libfprint-device-DEBUG: 00:53:54.484: Device reported finger status change: FP_FINGER_STATUS_NEEDED 385s (process:1959): libfprint-virtual_device_connection-DEBUG: 00:53:54.484: Got a new connection! 385s (process:1959): libfprint-virtual_image-DEBUG: 00:53:54.484: image data: 0x176a198 385s (process:1959): libfprint-device-DEBUG: 00:53:54.484: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 385s (process:1959): libfprint-image_device-DEBUG: 00:53:54.484: Image device reported finger status: on 385s (process:1959): libfprint-image_device-DEBUG: 00:53:54.484: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 385s (process:1959): libfprint-image_device-DEBUG: 00:53:54.484: Image device captured an image 385s (process:1959): libfprint-image_device-DEBUG: 00:53:54.485: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 385s (process:1959): libfprint-device-DEBUG: 00:53:54.485: Device reported finger status change: FP_FINGER_STATUS_PRESENT 385s (process:1959): libfprint-device-DEBUG: 00:53:54.485: Device reported finger status change: FP_FINGER_STATUS_NONE 385s (process:1959): libfprint-image_device-DEBUG: 00:53:54.485: Image device reported finger status: off 385s (process:1959): libfprint-image_device-DEBUG: 00:53:54.485: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 385s (process:1959): libfprint-image-DEBUG: 00:53:54.511: Minutiae scan completed in 0.025735 secs 385s (process:1959): libfprint-device-DEBUG: 00:53:54.511: Device reported enroll progress, reported 1 of 5 have been completed 385s (process:1959): libfprint-image_device-DEBUG: 00:53:54.511: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 385s (process:1959): libfprint-device-DEBUG: 00:53:54.511: Device reported finger status change: FP_FINGER_STATUS_NEEDED 385s (process:1959): libfprint-device-DEBUG: 00:53:54.511: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 385s (process:1959): libfprint-image_device-DEBUG: 00:53:54.511: Image device reported finger status: on 385s (process:1959): libfprint-image_device-DEBUG: 00:53:54.511: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 385s (process:1959): libfprint-virtual_image-DEBUG: 00:53:54.512: image data: 0x175b930 385s (process:1959): libfprint-image_device-DEBUG: 00:53:54.512: Image device captured an image 385s (process:1959): libfprint-image_device-DEBUG: 00:53:54.512: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 385s (process:1959): libfprint-device-DEBUG: 00:53:54.512: Device reported finger status change: FP_FINGER_STATUS_PRESENT 385s (process:1959): libfprint-image-DEBUG: 00:53:54.537: Minutiae scan completed in 0.025687 secs 385s (process:1959): libfprint-device-DEBUG: 00:53:54.538: Device reported enroll progress, reported 2 of 5 have been completed 385s (process:1959): libfprint-device-DEBUG: 00:53:54.538: Device reported finger status change: FP_FINGER_STATUS_NONE 385s (process:1959): libfprint-image_device-DEBUG: 00:53:54.538: Image device reported finger status: off 385s (process:1959): libfprint-image_device-DEBUG: 00:53:54.538: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 385s (process:1959): libfprint-image_device-DEBUG: 00:53:54.538: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 385s (process:1959): libfprint-device-DEBUG: 00:53:54.538: Device reported finger status change: FP_FINGER_STATUS_NEEDED 385s (process:1959): libfprint-virtual_image-DEBUG: 00:53:54.538: image data: 0x175cc00 385s (process:1959): libfprint-device-DEBUG: 00:53:54.538: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 385s (process:1959): libfprint-image_device-DEBUG: 00:53:54.538: Image device reported finger status: on 385s (process:1959): libfprint-image_device-DEBUG: 00:53:54.538: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 385s (process:1959): libfprint-image_device-DEBUG: 00:53:54.538: Image device captured an image 385s (process:1959): libfprint-image_device-DEBUG: 00:53:54.538: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 385s (process:1959): libfprint-device-DEBUG: 00:53:54.538: Device reported finger status change: FP_FINGER_STATUS_PRESENT 385s (process:1959): libfprint-device-DEBUG: 00:53:54.538: Device reported finger status change: FP_FINGER_STATUS_NONE 385s (process:1959): libfprint-image_device-DEBUG: 00:53:54.538: Image device reported finger status: off 385s (process:1959): libfprint-image_device-DEBUG: 00:53:54.538: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 385s (process:1959): libfprint-image-DEBUG: 00:53:54.564: Minutiae scan completed in 0.025400 secs 385s (process:1959): libfprint-device-DEBUG: 00:53:54.564: Device reported enroll progress, reported 3 of 5 have been completed 385s (process:1959): libfprint-image_device-DEBUG: 00:53:54.564: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 385s (process:1959): libfprint-device-DEBUG: 00:53:54.564: Device reported finger status change: FP_FINGER_STATUS_NEEDED 385s (process:1959): libfprint-virtual_image-DEBUG: 00:53:54.564: image data: 0x175cc00 385s (process:1959): libfprint-device-DEBUG: 00:53:54.564: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 385s (process:1959): libfprint-image_device-DEBUG: 00:53:54.564: Image device reported finger status: on 385s (process:1959): libfprint-image_device-DEBUG: 00:53:54.564: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 385s (process:1959): libfprint-image_device-DEBUG: 00:53:54.564: Image device captured an image 385s (process:1959): libfprint-image_device-DEBUG: 00:53:54.565: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 385s (process:1959): libfprint-device-DEBUG: 00:53:54.565: Device reported finger status change: FP_FINGER_STATUS_PRESENT 385s (process:1959): libfprint-device-DEBUG: 00:53:54.565: Device reported finger status change: FP_FINGER_STATUS_NONE 385s (process:1959): libfprint-image_device-DEBUG: 00:53:54.565: Image device reported finger status: off 385s (process:1959): libfprint-image_device-DEBUG: 00:53:54.565: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 385s (process:1959): libfprint-image-DEBUG: 00:53:54.590: Minutiae scan completed in 0.025377 secs 385s (process:1959): libfprint-device-DEBUG: 00:53:54.590: Device reported enroll progress, reported 4 of 5 have been completed 385s (process:1959): libfprint-image_device-DEBUG: 00:53:54.590: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 385s (process:1959): libfprint-device-DEBUG: 00:53:54.590: Device reported finger status change: FP_FINGER_STATUS_NEEDED 385s (process:1959): libfprint-virtual_image-DEBUG: 00:53:54.590: image data: 0x175cc00 385s (process:1959): libfprint-device-DEBUG: 00:53:54.591: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 385s (process:1959): libfprint-image_device-DEBUG: 00:53:54.591: Image device reported finger status: on 385s (process:1959): libfprint-image_device-DEBUG: 00:53:54.591: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 385s (process:1959): libfprint-image_device-DEBUG: 00:53:54.591: Image device captured an image 385s (process:1959): libfprint-image_device-DEBUG: 00:53:54.591: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 385s (process:1959): libfprint-device-DEBUG: 00:53:54.591: Device reported finger status change: FP_FINGER_STATUS_PRESENT 385s (process:1959): libfprint-device-DEBUG: 00:53:54.591: Device reported finger status change: FP_FINGER_STATUS_NONE 385s (process:1959): libfprint-image_device-DEBUG: 00:53:54.591: Image device reported finger status: off 385s (process:1959): libfprint-image_device-DEBUG: 00:53:54.591: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 385s (process:1959): libfprint-image-DEBUG: 00:53:54.616: Minutiae scan completed in 0.025579 secs 385s (process:1959): libfprint-device-DEBUG: 00:53:54.616: Device reported enroll progress, reported 5 of 5 have been completed 385s (process:1959): libfprint-image_device-DEBUG: 00:53:54.616: Deactivating image device 385s (process:1959): libfprint-image_device-DEBUG: 00:53:54.616: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_DEACTIVATING 385s (process:1959): libfprint-image_device-DEBUG: 00:53:54.616: Image device deactivation completed 385s (process:1959): libfprint-image_device-DEBUG: 00:53:54.617: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE 385s (process:1959): libfprint-device-DEBUG: 00:53:54.617: Device reported enroll completion 385s (process:1959): libfprint-device-DEBUG: 00:53:54.617: Print for finger FP_FINGER_LEFT_THUMB enrolled 385s (process:1959): libfprint-device-DEBUG: 00:53:54.617: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 385s (process:1959): libfprint-device-DEBUG: 00:53:54.617: Updated temperature model after 0.13 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 385s (process:1959): libfprint-device-DEBUG: 00:53:54.617: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 385s (process:1959): libfprint-image_device-DEBUG: 00:53:54.617: Activating image device 385s (process:1959): libfprint-image_device-DEBUG: 00:53:54.617: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING 385s (process:1959): libfprint-image_device-DEBUG: 00:53:54.617: Image device activation completed 385s (process:1959): libfprint-image_device-DEBUG: 00:53:54.617: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE 385s (process:1959): libfprint-image_device-DEBUG: 00:53:54.617: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 385s (process:1959): libfprint-device-DEBUG: 00:53:54.617: Device reported finger status change: FP_FINGER_STATUS_NEEDED 385s (process:1959): libfprint-virtual_image-DEBUG: 00:53:54.617: image data: 0x175cc00 385s (process:1959): libfprint-device-DEBUG: 00:53:54.618: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 385s (process:1959): libfprint-image_device-DEBUG: 00:53:54.618: Image device reported finger status: on 385s (process:1959): libfprint-image_device-DEBUG: 00:53:54.618: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 385s (process:1959): libfprint-image_device-DEBUG: 00:53:54.618: Image device captured an image 385s (process:1959): libfprint-image_device-DEBUG: 00:53:54.618: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 385s (process:1959): libfprint-device-DEBUG: 00:53:54.618: Device reported finger status change: FP_FINGER_STATUS_PRESENT 385s (process:1959): libfprint-device-DEBUG: 00:53:54.618: Device reported finger status change: FP_FINGER_STATUS_NONE 385s (process:1959): libfprint-image_device-DEBUG: 00:53:54.618: Image device reported finger status: off 385s (process:1959): libfprint-image_device-DEBUG: 00:53:54.618: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 385s (process:1959): libfprint-image_device-DEBUG: 00:53:54.618: Deactivating image device 385s (process:1959): libfprint-image_device-DEBUG: 00:53:54.618: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_DEACTIVATING 385s (process:1959): libfprint-image_device-DEBUG: 00:53:54.618: Image device deactivation completed 385s (process:1959): libfprint-image_device-DEBUG: 00:53:54.618: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE 385s (process:1959): libfprint-image-DEBUG: 00:53:54.643: Minutiae scan completed in 0.025289 secs 386s (process:1959): libfprint-print-DEBUG: 00:53:55.802: score 1093/40 386s (process:1959): libfprint-device-DEBUG: 00:53:55.802: Device reported verify result 386s (process:1959): libfprint-device-DEBUG: 00:53:55.802: Device reported verify completion 386s (process:1959): libfprint-device-DEBUG: 00:53:55.802: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 386s (process:1959): libfprint-device-DEBUG: 00:53:55.802: Updated temperature model after 1.18 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 386s (process:1959): libfprint-device-DEBUG: 00:53:55.802: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 386s (process:1959): libfprint-image_device-DEBUG: 00:53:55.802: Activating image device 386s (process:1959): libfprint-image_device-DEBUG: 00:53:55.802: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING 386s (process:1959): libfprint-image_device-DEBUG: 00:53:55.802: Image device activation completed 386s (process:1959): libfprint-image_device-DEBUG: 00:53:55.802: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE 386s (process:1959): libfprint-image_device-DEBUG: 00:53:55.802: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 386s (process:1959): libfprint-device-DEBUG: 00:53:55.802: Device reported finger status change: FP_FINGER_STATUS_NEEDED 386s (process:1959): libfprint-virtual_image-DEBUG: 00:53:55.803: image data: 0x17c4950 386s (process:1959): libfprint-device-DEBUG: 00:53:55.803: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 386s (process:1959): libfprint-image_device-DEBUG: 00:53:55.803: Image device reported finger status: on 386s (process:1959): libfprint-image_device-DEBUG: 00:53:55.803: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 386s (process:1959): libfprint-image_device-DEBUG: 00:53:55.803: Image device captured an image 386s (process:1959): libfprint-image_device-DEBUG: 00:53:55.803: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 386s (process:1959): libfprint-device-DEBUG: 00:53:55.803: Device reported finger status change: FP_FINGER_STATUS_PRESENT 386s (process:1959): libfprint-device-DEBUG: 00:53:55.803: Device reported finger status change: FP_FINGER_STATUS_NONE 386s (process:1959): libfprint-image_device-DEBUG: 00:53:55.803: Image device reported finger status: off 386s (process:1959): libfprint-image_device-DEBUG: 00:53:55.803: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 386s (process:1959): libfprint-image_device-DEBUG: 00:53:55.803: Deactivating image device 386s (process:1959): libfprint-image_device-DEBUG: 00:53:55.803: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_DEACTIVATING 386s (process:1959): libfprint-image_device-DEBUG: 00:53:55.803: Image device deactivation completed 386s (process:1959): libfprint-image_device-DEBUG: 00:53:55.803: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE 386s (process:1959): libfprint-image-DEBUG: 00:53:55.826: Minutiae scan completed in 0.023515 secs 386s (process:1959): libfprint-print-DEBUG: 00:53:55.833: score 10/40 386s (process:1959): libfprint-print-DEBUG: 00:53:55.840: score 10/40 386s (process:1959): libfprint-print-DEBUG: 00:53:55.846: score 10/40 386s (process:1959): libfprint-print-DEBUG: 00:53:55.853: score 10/40 386s (process:1959): libfprint-print-DEBUG: 00:53:55.859: score 10/40 386s (process:1959): libfprint-device-DEBUG: 00:53:55.859: Device reported verify result 386s (process:1959): libfprint-device-DEBUG: 00:53:55.859: Device reported verify completion 386s (process:1959): libfprint-device-DEBUG: 00:53:55.859: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 386s (process:1959): libfprint-device-DEBUG: 00:53:55.859: Updated temperature model after 0.06 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 386s (process:1959): libfprint-device-DEBUG: 00:53:55.859: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 386s (process:1959): libfprint-image_device-DEBUG: 00:53:55.859: Activating image device 386s (process:1959): libfprint-image_device-DEBUG: 00:53:55.859: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING 386s (process:1959): libfprint-image_device-DEBUG: 00:53:55.859: Image device activation completed 386s (process:1959): libfprint-image_device-DEBUG: 00:53:55.859: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE 386s (process:1959): libfprint-image_device-DEBUG: 00:53:55.859: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 386s (process:1959): libfprint-device-DEBUG: 00:53:55.859: Device reported finger status change: FP_FINGER_STATUS_NEEDED 386s (process:1959): libfprint-virtual_image-DEBUG: 00:53:55.859: image data: 0x17d3958 386s (process:1959): libfprint-device-DEBUG: 00:53:55.860: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 386s (process:1959): libfprint-image_device-DEBUG: 00:53:55.860: Image device reported finger status: on 386s (process:1959): libfprint-image_device-DEBUG: 00:53:55.860: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 386s (process:1959): libfprint-image_device-DEBUG: 00:53:55.860: Image device captured an image 386s (process:1959): libfprint-image_device-DEBUG: 00:53:55.860: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 386s (process:1959): libfprint-device-DEBUG: 00:53:55.860: Device reported finger status change: FP_FINGER_STATUS_PRESENT 386s (process:1959): libfprint-device-DEBUG: 00:53:55.860: Device reported finger status change: FP_FINGER_STATUS_NONE 386s (process:1959): libfprint-image_device-DEBUG: 00:53:55.860: Image device reported finger status: off 386s (process:1959): libfprint-image_device-DEBUG: 00:53:55.860: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 386s (process:1959): libfprint-image-DEBUG: 00:53:55.882: Minutiae scan completed in 0.022576 secs 386s (process:1959): libfprint-device-DEBUG: 00:53:55.882: Device reported enroll progress, reported 1 of 5 have been completed 386s (process:1959): libfprint-image_device-DEBUG: 00:53:55.883: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 386s (process:1959): libfprint-device-DEBUG: 00:53:55.883: Device reported finger status change: FP_FINGER_STATUS_NEEDED 386s (process:1959): libfprint-device-DEBUG: 00:53:55.883: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 386s (process:1959): libfprint-image_device-DEBUG: 00:53:55.883: Image device reported finger status: on 386s (process:1959): libfprint-image_device-DEBUG: 00:53:55.883: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 386s (process:1959): libfprint-virtual_image-DEBUG: 00:53:55.883: image data: 0x17d3958 386s (process:1959): libfprint-image_device-DEBUG: 00:53:55.883: Image device captured an image 386s (process:1959): libfprint-image_device-DEBUG: 00:53:55.883: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 386s (process:1959): libfprint-device-DEBUG: 00:53:55.883: Device reported finger status change: FP_FINGER_STATUS_PRESENT 386s (process:1959): libfprint-image-DEBUG: 00:53:55.907: Minutiae scan completed in 0.023696 secs 386s (process:1959): libfprint-device-DEBUG: 00:53:55.907: Device reported enroll progress, reported 2 of 5 have been completed 386s (process:1959): libfprint-device-DEBUG: 00:53:55.907: Device reported finger status change: FP_FINGER_STATUS_NONE 386s (process:1959): libfprint-image_device-DEBUG: 00:53:55.907: Image device reported finger status: off 386s (process:1959): libfprint-image_device-DEBUG: 00:53:55.907: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 386s (process:1959): libfprint-image_device-DEBUG: 00:53:55.907: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 386s (process:1959): libfprint-device-DEBUG: 00:53:55.907: Device reported finger status change: FP_FINGER_STATUS_NEEDED 386s (process:1959): libfprint-virtual_image-DEBUG: 00:53:55.907: image data: 0x17d3958 386s (process:1959): libfprint-device-DEBUG: 00:53:55.908: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 386s (process:1959): libfprint-image_device-DEBUG: 00:53:55.908: Image device reported finger status: on 386s (process:1959): libfprint-image_device-DEBUG: 00:53:55.908: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 386s (process:1959): libfprint-image_device-DEBUG: 00:53:55.908: Image device captured an image 386s (process:1959): libfprint-image_device-DEBUG: 00:53:55.908: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 386s (process:1959): libfprint-device-DEBUG: 00:53:55.908: Device reported finger status change: FP_FINGER_STATUS_PRESENT 386s (process:1959): libfprint-device-DEBUG: 00:53:55.908: Device reported finger status change: FP_FINGER_STATUS_NONE 386s (process:1959): libfprint-image_device-DEBUG: 00:53:55.908: Image device reported finger status: off 386s (process:1959): libfprint-image_device-DEBUG: 00:53:55.908: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 386s (process:1959): libfprint-image-DEBUG: 00:53:55.931: Minutiae scan completed in 0.023431 secs 386s (process:1959): libfprint-device-DEBUG: 00:53:55.931: Device reported enroll progress, reported 3 of 5 have been completed 386s (process:1959): libfprint-image_device-DEBUG: 00:53:55.931: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 386s (process:1959): libfprint-device-DEBUG: 00:53:55.931: Device reported finger status change: FP_FINGER_STATUS_NEEDED 386s (process:1959): libfprint-virtual_image-DEBUG: 00:53:55.932: image data: 0x17d3958 386s (process:1959): libfprint-device-DEBUG: 00:53:55.932: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 386s (process:1959): libfprint-image_device-DEBUG: 00:53:55.932: Image device reported finger status: on 386s (process:1959): libfprint-image_device-DEBUG: 00:53:55.932: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 386s (process:1959): libfprint-image_device-DEBUG: 00:53:55.932: Image device captured an image 386s (process:1959): libfprint-image_device-DEBUG: 00:53:55.932: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 386s (process:1959): libfprint-device-DEBUG: 00:53:55.932: Device reported finger status change: FP_FINGER_STATUS_PRESENT 386s (process:1959): libfprint-device-DEBUG: 00:53:55.932: Device reported finger status change: FP_FINGER_STATUS_NONE 386s (process:1959): libfprint-image_device-DEBUG: 00:53:55.932: Image device reported finger status: off 386s (process:1959): libfprint-image_device-DEBUG: 00:53:55.932: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 386s (process:1959): libfprint-image-DEBUG: 00:53:55.955: Minutiae scan completed in 0.023292 secs 386s (process:1959): libfprint-device-DEBUG: 00:53:55.955: Device reported enroll progress, reported 4 of 5 have been completed 386s (process:1959): libfprint-image_device-DEBUG: 00:53:55.955: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 386s (process:1959): libfprint-device-DEBUG: 00:53:55.955: Device reported finger status change: FP_FINGER_STATUS_NEEDED 386s (process:1959): libfprint-virtual_image-DEBUG: 00:53:55.956: image data: 0x17d3958 386s (process:1959): libfprint-device-DEBUG: 00:53:55.956: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 386s (process:1959): libfprint-image_device-DEBUG: 00:53:55.956: Image device reported finger status: on 386s (process:1959): libfprint-image_device-DEBUG: 00:53:55.956: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 386s (process:1959): libfprint-image_device-DEBUG: 00:53:55.956: Image device captured an image 386s (process:1959): libfprint-image_device-DEBUG: 00:53:55.956: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 386s (process:1959): libfprint-device-DEBUG: 00:53:55.956: Device reported finger status change: FP_FINGER_STATUS_PRESENT 386s (process:1959): libfprint-device-DEBUG: 00:53:55.956: Device reported finger status change: FP_FINGER_STATUS_NONE 386s (process:1959): libfprint-image_device-DEBUG: 00:53:55.956: Image device reported finger status: off 386s (process:1959): libfprint-image_device-DEBUG: 00:53:55.956: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 387s (process:1959): libfprint-image-DEBUG: 00:53:55.978: Minutiae scan completed in 0.022346 secs 387s (process:1959): libfprint-device-DEBUG: 00:53:55.978: Device reported enroll progress, reported 5 of 5 have been completed 387s (process:1959): libfprint-image_device-DEBUG: 00:53:55.978: Deactivating image device 387s (process:1959): libfprint-image_device-DEBUG: 00:53:55.978: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_DEACTIVATING 387s (process:1959): libfprint-image_device-DEBUG: 00:53:55.978: Image device deactivation completed 387s (process:1959): libfprint-image_device-DEBUG: 00:53:55.978: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE 387s (process:1959): libfprint-device-DEBUG: 00:53:55.978: Device reported enroll completion 387s (process:1959): libfprint-device-DEBUG: 00:53:55.978: Print for finger FP_FINGER_LEFT_THUMB enrolled 387s (process:1959): libfprint-device-DEBUG: 00:53:55.979: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 387s (process:1959): libfprint-device-DEBUG: 00:53:55.979: Updated temperature model after 0.12 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 387s (process:1959): libfprint-device-DEBUG: 00:53:55.979: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 387s (process:1959): libfprint-image_device-DEBUG: 00:53:55.979: Activating image device 387s (process:1959): libfprint-image_device-DEBUG: 00:53:55.979: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING 387s (process:1959): libfprint-image_device-DEBUG: 00:53:55.979: Image device activation completed 387s (process:1959): libfprint-image_device-DEBUG: 00:53:55.979: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE 387s (process:1959): libfprint-image_device-DEBUG: 00:53:55.979: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 387s (process:1959): libfprint-device-DEBUG: 00:53:55.979: Device reported finger status change: FP_FINGER_STATUS_NEEDED 387s (process:1959): libfprint-virtual_image-DEBUG: 00:53:55.979: image data: 0x175cc00 387s (process:1959): libfprint-device-DEBUG: 00:53:55.979: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 387s (process:1959): libfprint-image_device-DEBUG: 00:53:55.979: Image device reported finger status: on 387s (process:1959): libfprint-image_device-DEBUG: 00:53:55.979: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 387s (process:1959): libfprint-image_device-DEBUG: 00:53:55.979: Image device captured an image 387s (process:1959): libfprint-image_device-DEBUG: 00:53:55.979: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 387s (process:1959): libfprint-device-DEBUG: 00:53:55.979: Device reported finger status change: FP_FINGER_STATUS_PRESENT 387s (process:1959): libfprint-device-DEBUG: 00:53:55.979: Device reported finger status change: FP_FINGER_STATUS_NONE 387s (process:1959): libfprint-image_device-DEBUG: 00:53:55.979: Image device reported finger status: off 387s (process:1959): libfprint-image_device-DEBUG: 00:53:55.979: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 387s (process:1959): libfprint-image_device-DEBUG: 00:53:55.979: Deactivating image device 387s (process:1959): libfprint-image_device-DEBUG: 00:53:55.979: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_DEACTIVATING 387s (process:1959): libfprint-image_device-DEBUG: 00:53:55.979: Image device deactivation completed 387s (process:1959): libfprint-image_device-DEBUG: 00:53:55.979: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE 387s (process:1959): libfprint-image-DEBUG: 00:53:56.004: Minutiae scan completed in 0.025254 secs 387s Executing: libfprint-2/virtual-image.test 388s (process:1959): libfprint-print-DEBUG: 00:53:57.150: score 1093/40 388s (process:1959): libfprint-device-DEBUG: 00:53:57.150: Device reported verify result 388s (process:1959): libfprint-device-DEBUG: 00:53:57.150: Device reported verify completion 388s (process:1959): libfprint-device-DEBUG: 00:53:57.150: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 388s (process:1959): libfprint-device-DEBUG: 00:53:57.150: Updated temperature model after 1.17 seconds, ratio 0.27 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 388s (process:1959): libfprint-device-DEBUG: 00:53:57.151: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 388s (process:1959): libfprint-image_device-DEBUG: 00:53:57.151: Activating image device 388s (process:1959): libfprint-image_device-DEBUG: 00:53:57.151: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING 388s (process:1959): libfprint-image_device-DEBUG: 00:53:57.151: Image device activation completed 388s (process:1959): libfprint-image_device-DEBUG: 00:53:57.151: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE 388s (process:1959): libfprint-image_device-DEBUG: 00:53:57.151: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 388s (process:1959): libfprint-device-DEBUG: 00:53:57.151: Device reported finger status change: FP_FINGER_STATUS_NEEDED 388s (process:1959): libfprint-virtual_image-DEBUG: 00:53:57.151: image data: 0x17c4950 388s (process:1959): libfprint-device-DEBUG: 00:53:57.151: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 388s (process:1959): libfprint-image_device-DEBUG: 00:53:57.151: Image device reported finger status: on 388s (process:1959): libfprint-image_device-DEBUG: 00:53:57.151: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 388s (process:1959): libfprint-image_device-DEBUG: 00:53:57.151: Image device captured an image 388s (process:1959): libfprint-image_device-DEBUG: 00:53:57.151: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 388s (process:1959): libfprint-device-DEBUG: 00:53:57.151: Device reported finger status change: FP_FINGER_STATUS_PRESENT 388s (process:1959): libfprint-device-DEBUG: 00:53:57.151: Device reported finger status change: FP_FINGER_STATUS_NONE 388s (process:1959): libfprint-image_device-DEBUG: 00:53:57.151: Image device reported finger status: off 388s (process:1959): libfprint-image_device-DEBUG: 00:53:57.151: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 388s (process:1959): libfprint-image_device-DEBUG: 00:53:57.151: Deactivating image device 388s (process:1959): libfprint-image_device-DEBUG: 00:53:57.151: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_DEACTIVATING 388s (process:1959): libfprint-image_device-DEBUG: 00:53:57.151: Image device deactivation completed 388s (process:1959): libfprint-image_device-DEBUG: 00:53:57.151: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE 388s (process:1959): libfprint-image-DEBUG: 00:53:57.174: Minutiae scan completed in 0.023143 secs 388s (process:1959): libfprint-print-DEBUG: 00:53:57.181: score 10/40 388s (process:1959): libfprint-print-DEBUG: 00:53:57.188: score 10/40 388s (process:1959): libfprint-print-DEBUG: 00:53:57.194: score 10/40 388s (process:1959): libfprint-print-DEBUG: 00:53:57.200: score 10/40 388s (process:1959): libfprint-print-DEBUG: 00:53:57.207: score 10/40 388s (process:1959): libfprint-print-DEBUG: 00:53:57.437: score 855/40 388s (process:1959): libfprint-device-DEBUG: 00:53:57.437: Device reported verify result 388s (process:1959): libfprint-device-DEBUG: 00:53:57.437: Device reported verify completion 388s (process:1959): libfprint-device-DEBUG: 00:53:57.437: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 388s (process:1959): libfprint-device-DEBUG: 00:53:57.437: Updated temperature model after 0.29 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 388s (process:1959): libfprint-device-DEBUG: 00:53:57.437: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 388s (process:1959): libfprint-image_device-DEBUG: 00:53:57.437: Activating image device 388s (process:1959): libfprint-image_device-DEBUG: 00:53:57.437: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING 388s (process:1959): libfprint-image_device-DEBUG: 00:53:57.437: Image device activation completed 388s (process:1959): libfprint-image_device-DEBUG: 00:53:57.437: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE 388s (process:1959): libfprint-image_device-DEBUG: 00:53:57.437: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 388s (process:1959): libfprint-device-DEBUG: 00:53:57.437: Device reported finger status change: FP_FINGER_STATUS_NEEDED 388s (process:1959): libfprint-device-DEBUG: 00:53:57.438: Device reported verify result 388s (process:1959): libfprint-image_device-DEBUG: 00:53:57.438: Deactivating image device 388s (process:1959): libfprint-image_device-DEBUG: 00:53:57.438: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_DEACTIVATING 388s (process:1959): libfprint-image_device-DEBUG: 00:53:57.438: Image device deactivation completed 388s (process:1959): libfprint-image_device-DEBUG: 00:53:57.438: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE 388s (process:1959): libfprint-device-DEBUG: 00:53:57.438: Device reported verify completion 388s (process:1959): libfprint-device-DEBUG: 00:53:57.438: Device reported finger status change: FP_FINGER_STATUS_NONE 388s (process:1959): libfprint-device-DEBUG: 00:53:57.438: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 388s (process:1959): libfprint-device-DEBUG: 00:53:57.438: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 388s (process:1959): libfprint-device-DEBUG: 00:53:57.438: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 388s (process:1959): libfprint-image_device-DEBUG: 00:53:57.438: Activating image device 388s (process:1959): libfprint-image_device-DEBUG: 00:53:57.438: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING 388s (process:1959): libfprint-image_device-DEBUG: 00:53:57.438: Image device activation completed 388s (process:1959): libfprint-image_device-DEBUG: 00:53:57.438: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE 388s (process:1959): libfprint-image_device-DEBUG: 00:53:57.438: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 388s (process:1959): libfprint-device-DEBUG: 00:53:57.438: Device reported finger status change: FP_FINGER_STATUS_NEEDED 388s (process:1959): libfprint-image_device-DEBUG: 00:53:57.438: Deactivating image device 388s (process:1959): libfprint-image_device-DEBUG: 00:53:57.438: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_DEACTIVATING 388s (process:1959): libfprint-image_device-DEBUG: 00:53:57.438: Image device deactivation completed 388s (process:1959): libfprint-image_device-DEBUG: 00:53:57.438: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE 388s (process:1959): libfprint-device-DEBUG: 00:53:57.438: Device reported generic error (An unspecified error occurred!) during action; action was: FPI_DEVICE_ACTION_VERIFY 388s (process:1959): libfprint-device-DEBUG: 00:53:57.438: Device reported verify completion 388s (process:1959): libfprint-device-DEBUG: 00:53:57.438: Device reported finger status change: FP_FINGER_STATUS_NONE 388s (process:1959): libfprint-device-DEBUG: 00:53:57.438: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 388s (process:1959): libfprint-device-DEBUG: 00:53:57.438: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 388s (process:1959): libfprint-virtual_image-DEBUG: 00:53:57.438: 7399805499538: ../libfprint/drivers/virtual-image.c:244 388s (process:1959): libfprint-image_device-DEBUG: 00:53:57.538: Image device close completed 388s (process:1959): libfprint-device-DEBUG: 00:53:57.538: Device reported close completion 388s (process:1959): libfprint-device-DEBUG: 00:53:57.538: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 388s (process:1959): libfprint-device-DEBUG: 00:53:57.538: Updated temperature model after 0.10 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 388s Print was processed, continuing 388s Print was processed, continuing 388s Print was processed, continuing 388s Print was processed, continuing 388s Print was processed, continuing 388s Enroll done 388s Print was processed, continuing 388s Print was processed, continuing 388s Print was processed, continuing 388s Print was processed, continuing 388s Print was processed, continuing 388s Enroll done 388s fp - device - error - quark: An unspecified error occurred! (0) 388s ok 388s test_features (__main__.VirtualImage.test_features) ... (process:1959): libfprint-virtual_image-DEBUG: 00:53:57.539: 7399805599937: ../libfprint/drivers/virtual-image.c:216 388s (process:1959): libfprint-virtual_device_connection-DEBUG: 00:53:57.539: 7399805599950: ../libfprint/drivers/virtual-device-listener.c:153 388s (process:1959): libfprint-image_device-DEBUG: 00:53:57.639: Image device open completed 388s (process:1959): libfprint-device-DEBUG: 00:53:57.639: Device reported open completion 388s (process:1959): libfprint-device-DEBUG: 00:53:57.639: Completing action FPI_DEVICE_ACTION_OPEN in idle! 388s (process:1959): libfprint-device-DEBUG: 00:53:57.639: Updated temperature model after 0.10 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 388s (process:1959): libfprint-virtual_image-DEBUG: 00:53:57.639: 7399805700320: ../libfprint/drivers/virtual-image.c:244 388s (process:1959): libfprint-image_device-DEBUG: 00:53:57.739: Image device close completed 388s (process:1959): libfprint-device-DEBUG: 00:53:57.739: Device reported close completion 388s (process:1959): libfprint-device-DEBUG: 00:53:57.739: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 388s (process:1959): libfprint-device-DEBUG: 00:53:57.739: Updated temperature model after 0.10 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 388s ok 388s test_identify (__main__.VirtualImage.test_identify) ... (process:1959): libfprint-virtual_image-DEBUG: 00:53:57.739: 7399805800473: ../libfprint/drivers/virtual-image.c:216 388s (process:1959): libfprint-virtual_device_connection-DEBUG: 00:53:57.739: 7399805800484: ../libfprint/drivers/virtual-device-listener.c:153 388s (process:1959): libfprint-image_device-DEBUG: 00:53:57.839: Image device open completed 388s (process:1959): libfprint-device-DEBUG: 00:53:57.839: Device reported open completion 388s (process:1959): libfprint-device-DEBUG: 00:53:57.839: Completing action FPI_DEVICE_ACTION_OPEN in idle! 388s (process:1959): libfprint-device-DEBUG: 00:53:57.839: Updated temperature model after 0.10 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 388s (process:1959): libfprint-device-DEBUG: 00:53:57.840: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 388s (process:1959): libfprint-image_device-DEBUG: 00:53:57.840: Activating image device 388s (process:1959): libfprint-image_device-DEBUG: 00:53:57.840: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING 388s (process:1959): libfprint-image_device-DEBUG: 00:53:57.840: Image device activation completed 388s (process:1959): libfprint-image_device-DEBUG: 00:53:57.840: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE 388s (process:1959): libfprint-image_device-DEBUG: 00:53:57.840: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 388s (process:1959): libfprint-device-DEBUG: 00:53:57.840: Device reported finger status change: FP_FINGER_STATUS_NEEDED 388s (process:1959): libfprint-virtual_device_connection-DEBUG: 00:53:57.840: Got a new connection! 388s (process:1959): libfprint-virtual_image-DEBUG: 00:53:57.840: image data: 0x175cc00 388s (process:1959): libfprint-device-DEBUG: 00:53:57.840: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 388s (process:1959): libfprint-image_device-DEBUG: 00:53:57.840: Image device reported finger status: on 388s (process:1959): libfprint-image_device-DEBUG: 00:53:57.840: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 388s (process:1959): libfprint-image_device-DEBUG: 00:53:57.840: Image device captured an image 388s (process:1959): libfprint-image_device-DEBUG: 00:53:57.840: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 388s (process:1959): libfprint-device-DEBUG: 00:53:57.840: Device reported finger status change: FP_FINGER_STATUS_PRESENT 388s (process:1959): libfprint-device-DEBUG: 00:53:57.840: Device reported finger status change: FP_FINGER_STATUS_NONE 388s (process:1959): libfprint-image_device-DEBUG: 00:53:57.840: Image device reported finger status: off 388s (process:1959): libfprint-image_device-DEBUG: 00:53:57.840: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 388s (process:1959): libfprint-image-DEBUG: 00:53:57.866: Minutiae scan completed in 0.026101 secs 388s (process:1959): libfprint-device-DEBUG: 00:53:57.866: Device reported enroll progress, reported 1 of 5 have been completed 388s (process:1959): libfprint-image_device-DEBUG: 00:53:57.866: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 388s (process:1959): libfprint-device-DEBUG: 00:53:57.866: Device reported finger status change: FP_FINGER_STATUS_NEEDED 388s (process:1959): libfprint-device-DEBUG: 00:53:57.867: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 388s (process:1959): libfprint-image_device-DEBUG: 00:53:57.867: Image device reported finger status: on 388s (process:1959): libfprint-image_device-DEBUG: 00:53:57.867: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 388s (process:1959): libfprint-virtual_image-DEBUG: 00:53:57.867: image data: 0x175cc00 388s (process:1959): libfprint-image_device-DEBUG: 00:53:57.867: Image device captured an image 388s (process:1959): libfprint-image_device-DEBUG: 00:53:57.867: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 388s (process:1959): libfprint-device-DEBUG: 00:53:57.867: Device reported finger status change: FP_FINGER_STATUS_PRESENT 388s (process:1959): libfprint-image-DEBUG: 00:53:57.892: Minutiae scan completed in 0.025221 secs 388s (process:1959): libfprint-device-DEBUG: 00:53:57.892: Device reported enroll progress, reported 2 of 5 have been completed 388s (process:1959): libfprint-device-DEBUG: 00:53:57.893: Device reported finger status change: FP_FINGER_STATUS_NONE 388s (process:1959): libfprint-image_device-DEBUG: 00:53:57.893: Image device reported finger status: off 388s (process:1959): libfprint-image_device-DEBUG: 00:53:57.893: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 388s (process:1959): libfprint-image_device-DEBUG: 00:53:57.893: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 388s (process:1959): libfprint-device-DEBUG: 00:53:57.893: Device reported finger status change: FP_FINGER_STATUS_NEEDED 388s (process:1959): libfprint-virtual_image-DEBUG: 00:53:57.893: image data: 0x175cc00 388s (process:1959): libfprint-device-DEBUG: 00:53:57.893: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 388s (process:1959): libfprint-image_device-DEBUG: 00:53:57.893: Image device reported finger status: on 388s (process:1959): libfprint-image_device-DEBUG: 00:53:57.893: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 388s (process:1959): libfprint-image_device-DEBUG: 00:53:57.893: Image device captured an image 388s (process:1959): libfprint-image_device-DEBUG: 00:53:57.893: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 388s (process:1959): libfprint-device-DEBUG: 00:53:57.893: Device reported finger status change: FP_FINGER_STATUS_PRESENT 388s (process:1959): libfprint-device-DEBUG: 00:53:57.893: Device reported finger status change: FP_FINGER_STATUS_NONE 388s (process:1959): libfprint-image_device-DEBUG: 00:53:57.893: Image device reported finger status: off 388s (process:1959): libfprint-image_device-DEBUG: 00:53:57.893: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 388s (process:1959): libfprint-image-DEBUG: 00:53:57.919: Minutiae scan completed in 0.025801 secs 388s (process:1959): libfprint-device-DEBUG: 00:53:57.919: Device reported enroll progress, reported 3 of 5 have been completed 388s (process:1959): libfprint-image_device-DEBUG: 00:53:57.919: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 388s (process:1959): libfprint-device-DEBUG: 00:53:57.919: Device reported finger status change: FP_FINGER_STATUS_NEEDED 388s (process:1959): libfprint-virtual_image-DEBUG: 00:53:57.920: image data: 0x175cc00 388s (process:1959): libfprint-device-DEBUG: 00:53:57.920: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 388s (process:1959): libfprint-image_device-DEBUG: 00:53:57.920: Image device reported finger status: on 388s (process:1959): libfprint-image_device-DEBUG: 00:53:57.920: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 388s (process:1959): libfprint-image_device-DEBUG: 00:53:57.920: Image device captured an image 388s (process:1959): libfprint-image_device-DEBUG: 00:53:57.920: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 388s (process:1959): libfprint-device-DEBUG: 00:53:57.920: Device reported finger status change: FP_FINGER_STATUS_PRESENT 388s (process:1959): libfprint-device-DEBUG: 00:53:57.920: Device reported finger status change: FP_FINGER_STATUS_NONE 388s (process:1959): libfprint-image_device-DEBUG: 00:53:57.920: Image device reported finger status: off 388s (process:1959): libfprint-image_device-DEBUG: 00:53:57.920: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 388s (process:1959): libfprint-image-DEBUG: 00:53:57.945: Minutiae scan completed in 0.025300 secs 388s (process:1959): libfprint-device-DEBUG: 00:53:57.945: Device reported enroll progress, reported 4 of 5 have been completed 388s (process:1959): libfprint-image_device-DEBUG: 00:53:57.945: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 388s (process:1959): libfprint-device-DEBUG: 00:53:57.945: Device reported finger status change: FP_FINGER_STATUS_NEEDED 388s (process:1959): libfprint-virtual_image-DEBUG: 00:53:57.946: image data: 0x175cc00 388s (process:1959): libfprint-device-DEBUG: 00:53:57.946: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 388s (process:1959): libfprint-image_device-DEBUG: 00:53:57.946: Image device reported finger status: on 388s (process:1959): libfprint-image_device-DEBUG: 00:53:57.946: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 388s (process:1959): libfprint-image_device-DEBUG: 00:53:57.946: Image device captured an image 388s (process:1959): libfprint-image_device-DEBUG: 00:53:57.946: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 388s (process:1959): libfprint-device-DEBUG: 00:53:57.946: Device reported finger status change: FP_FINGER_STATUS_PRESENT 388s (process:1959): libfprint-device-DEBUG: 00:53:57.946: Device reported finger status change: FP_FINGER_STATUS_NONE 388s (process:1959): libfprint-image_device-DEBUG: 00:53:57.946: Image device reported finger status: off 388s (process:1959): libfprint-image_device-DEBUG: 00:53:57.946: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 389s (process:1959): libfprint-image-DEBUG: 00:53:57.971: Minutiae scan completed in 0.025250 secs 389s (process:1959): libfprint-device-DEBUG: 00:53:57.971: Device reported enroll progress, reported 5 of 5 have been completed 389s (process:1959): libfprint-image_device-DEBUG: 00:53:57.971: Deactivating image device 389s (process:1959): libfprint-image_device-DEBUG: 00:53:57.971: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_DEACTIVATING 389s (process:1959): libfprint-image_device-DEBUG: 00:53:57.971: Image device deactivation completed 389s (process:1959): libfprint-image_device-DEBUG: 00:53:57.971: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE 389s (process:1959): libfprint-device-DEBUG: 00:53:57.971: Device reported enroll completion 389s (process:1959): libfprint-device-DEBUG: 00:53:57.971: Print for finger FP_FINGER_LEFT_THUMB enrolled 389s (process:1959): libfprint-device-DEBUG: 00:53:57.972: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 389s (process:1959): libfprint-device-DEBUG: 00:53:57.972: Updated temperature model after 0.13 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 389s (process:1959): libfprint-device-DEBUG: 00:53:57.972: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 389s (process:1959): libfprint-image_device-DEBUG: 00:53:57.972: Activating image device 389s (process:1959): libfprint-image_device-DEBUG: 00:53:57.972: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING 389s (process:1959): libfprint-image_device-DEBUG: 00:53:57.972: Image device activation completed 389s (process:1959): libfprint-image_device-DEBUG: 00:53:57.972: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE 389s (process:1959): libfprint-image_device-DEBUG: 00:53:57.972: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 389s (process:1959): libfprint-device-DEBUG: 00:53:57.972: Device reported finger status change: FP_FINGER_STATUS_NEEDED 389s (process:1959): libfprint-virtual_image-DEBUG: 00:53:57.973: image data: 0x17c4950 389s (process:1959): libfprint-device-DEBUG: 00:53:57.973: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 389s (process:1959): libfprint-image_device-DEBUG: 00:53:57.973: Image device reported finger status: on 389s (process:1959): libfprint-image_device-DEBUG: 00:53:57.973: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 389s (process:1959): libfprint-image_device-DEBUG: 00:53:57.973: Image device captured an image 389s (process:1959): libfprint-image_device-DEBUG: 00:53:57.973: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 389s (process:1959): libfprint-device-DEBUG: 00:53:57.973: Device reported finger status change: FP_FINGER_STATUS_PRESENT 389s (process:1959): libfprint-device-DEBUG: 00:53:57.973: Device reported finger status change: FP_FINGER_STATUS_NONE 389s (process:1959): libfprint-image_device-DEBUG: 00:53:57.973: Image device reported finger status: off 389s (process:1959): libfprint-image_device-DEBUG: 00:53:57.973: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 389s (process:1959): libfprint-image-DEBUG: 00:53:57.995: Minutiae scan completed in 0.022475 secs 389s (process:1959): libfprint-device-DEBUG: 00:53:57.996: Device reported enroll progress, reported 1 of 5 have been completed 389s (process:1959): libfprint-image_device-DEBUG: 00:53:57.996: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 389s (process:1959): libfprint-device-DEBUG: 00:53:57.996: Device reported finger status change: FP_FINGER_STATUS_NEEDED 389s (process:1959): libfprint-device-DEBUG: 00:53:57.996: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 389s (process:1959): libfprint-image_device-DEBUG: 00:53:57.996: Image device reported finger status: on 389s (process:1959): libfprint-image_device-DEBUG: 00:53:57.996: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 389s (process:1959): libfprint-virtual_image-DEBUG: 00:53:57.996: image data: 0x17c4950 389s (process:1959): libfprint-image_device-DEBUG: 00:53:57.996: Image device captured an image 389s (process:1959): libfprint-image_device-DEBUG: 00:53:57.996: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 389s (process:1959): libfprint-device-DEBUG: 00:53:57.996: Device reported finger status change: FP_FINGER_STATUS_PRESENT 389s (process:1959): libfprint-image-DEBUG: 00:53:58.019: Minutiae scan completed in 0.022601 secs 389s (process:1959): libfprint-device-DEBUG: 00:53:58.019: Device reported enroll progress, reported 2 of 5 have been completed 389s (process:1959): libfprint-device-DEBUG: 00:53:58.020: Device reported finger status change: FP_FINGER_STATUS_NONE 389s (process:1959): libfprint-image_device-DEBUG: 00:53:58.020: Image device reported finger status: off 389s (process:1959): libfprint-image_device-DEBUG: 00:53:58.020: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 389s (process:1959): libfprint-image_device-DEBUG: 00:53:58.020: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 389s (process:1959): libfprint-device-DEBUG: 00:53:58.020: Device reported finger status change: FP_FINGER_STATUS_NEEDED 389s (process:1959): libfprint-virtual_image-DEBUG: 00:53:58.020: image data: 0x17c4950 389s (process:1959): libfprint-device-DEBUG: 00:53:58.020: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 389s (process:1959): libfprint-image_device-DEBUG: 00:53:58.020: Image device reported finger status: on 389s (process:1959): libfprint-image_device-DEBUG: 00:53:58.020: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 389s (process:1959): libfprint-image_device-DEBUG: 00:53:58.020: Image device captured an image 389s (process:1959): libfprint-image_device-DEBUG: 00:53:58.020: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 389s (process:1959): libfprint-device-DEBUG: 00:53:58.020: Device reported finger status change: FP_FINGER_STATUS_PRESENT 389s (process:1959): libfprint-device-DEBUG: 00:53:58.020: Device reported finger status change: FP_FINGER_STATUS_NONE 389s (process:1959): libfprint-image_device-DEBUG: 00:53:58.020: Image device reported finger status: off 389s (process:1959): libfprint-image_device-DEBUG: 00:53:58.020: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 389s (process:1959): libfprint-image-DEBUG: 00:53:58.043: Minutiae scan completed in 0.022582 secs 389s (process:1959): libfprint-device-DEBUG: 00:53:58.043: Device reported enroll progress, reported 3 of 5 have been completed 389s (process:1959): libfprint-image_device-DEBUG: 00:53:58.043: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 389s (process:1959): libfprint-device-DEBUG: 00:53:58.043: Device reported finger status change: FP_FINGER_STATUS_NEEDED 389s (process:1959): libfprint-virtual_image-DEBUG: 00:53:58.043: image data: 0x17c4950 389s (process:1959): libfprint-device-DEBUG: 00:53:58.043: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 389s (process:1959): libfprint-image_device-DEBUG: 00:53:58.043: Image device reported finger status: on 389s (process:1959): libfprint-image_device-DEBUG: 00:53:58.043: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 389s (process:1959): libfprint-image_device-DEBUG: 00:53:58.043: Image device captured an image 389s (process:1959): libfprint-image_device-DEBUG: 00:53:58.043: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 389s (process:1959): libfprint-device-DEBUG: 00:53:58.043: Device reported finger status change: FP_FINGER_STATUS_PRESENT 389s (process:1959): libfprint-device-DEBUG: 00:53:58.043: Device reported finger status change: FP_FINGER_STATUS_NONE 389s (process:1959): libfprint-image_device-DEBUG: 00:53:58.043: Image device reported finger status: off 389s (process:1959): libfprint-image_device-DEBUG: 00:53:58.043: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 389s (process:1959): libfprint-image-DEBUG: 00:53:58.066: Minutiae scan completed in 0.022484 secs 389s (process:1959): libfprint-device-DEBUG: 00:53:58.066: Device reported enroll progress, reported 4 of 5 have been completed 389s (process:1959): libfprint-image_device-DEBUG: 00:53:58.066: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 389s (process:1959): libfprint-device-DEBUG: 00:53:58.066: Device reported finger status change: FP_FINGER_STATUS_NEEDED 389s (process:1959): libfprint-virtual_image-DEBUG: 00:53:58.066: image data: 0x17c4950 389s (process:1959): libfprint-device-DEBUG: 00:53:58.067: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 389s (process:1959): libfprint-image_device-DEBUG: 00:53:58.067: Image device reported finger status: on 389s (process:1959): libfprint-image_device-DEBUG: 00:53:58.067: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 389s (process:1959): libfprint-image_device-DEBUG: 00:53:58.067: Image device captured an image 389s (process:1959): libfprint-image_device-DEBUG: 00:53:58.067: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 389s (process:1959): libfprint-device-DEBUG: 00:53:58.067: Device reported finger status change: FP_FINGER_STATUS_PRESENT 389s (process:1959): libfprint-device-DEBUG: 00:53:58.067: Device reported finger status change: FP_FINGER_STATUS_NONE 389s (process:1959): libfprint-image_device-DEBUG: 00:53:58.067: Image device reported finger status: off 389s (process:1959): libfprint-image_device-DEBUG: 00:53:58.067: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 389s (process:1959): libfprint-image-DEBUG: 00:53:58.089: Minutiae scan completed in 0.022519 secs 389s (process:1959): libfprint-device-DEBUG: 00:53:58.089: Device reported enroll progress, reported 5 of 5 have been completed 389s (process:1959): libfprint-image_device-DEBUG: 00:53:58.090: Deactivating image device 389s (process:1959): libfprint-image_device-DEBUG: 00:53:58.090: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_DEACTIVATING 389s (process:1959): libfprint-image_device-DEBUG: 00:53:58.090: Image device deactivation completed 389s (process:1959): libfprint-image_device-DEBUG: 00:53:58.090: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE 389s (process:1959): libfprint-device-DEBUG: 00:53:58.090: Device reported enroll completion 389s (process:1959): libfprint-device-DEBUG: 00:53:58.090: Print for finger FP_FINGER_LEFT_THUMB enrolled 389s (process:1959): libfprint-device-DEBUG: 00:53:58.090: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 389s (process:1959): libfprint-device-DEBUG: 00:53:58.090: Updated temperature model after 0.12 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 389s (process:1959): libfprint-device-DEBUG: 00:53:58.090: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 389s (process:1959): libfprint-image_device-DEBUG: 00:53:58.090: Activating image device 389s (process:1959): libfprint-image_device-DEBUG: 00:53:58.090: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING 389s (process:1959): libfprint-image_device-DEBUG: 00:53:58.090: Image device activation completed 389s (process:1959): libfprint-image_device-DEBUG: 00:53:58.090: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE 389s (process:1959): libfprint-image_device-DEBUG: 00:53:58.090: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 389s (process:1959): libfprint-device-DEBUG: 00:53:58.090: Device reported finger status change: FP_FINGER_STATUS_NEEDED 389s (process:1959): libfprint-virtual_image-DEBUG: 00:53:58.090: image data: 0x17c4950 389s (process:1959): libfprint-device-DEBUG: 00:53:58.090: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 389s (process:1959): libfprint-image_device-DEBUG: 00:53:58.090: Image device reported finger status: on 389s (process:1959): libfprint-image_device-DEBUG: 00:53:58.090: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 389s (process:1959): libfprint-image_device-DEBUG: 00:53:58.090: Image device captured an image 389s (process:1959): libfprint-image_device-DEBUG: 00:53:58.090: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 389s (process:1959): libfprint-device-DEBUG: 00:53:58.090: Device reported finger status change: FP_FINGER_STATUS_PRESENT 389s (process:1959): libfprint-device-DEBUG: 00:53:58.090: Device reported finger status change: FP_FINGER_STATUS_NONE 389s (process:1959): libfprint-image_device-DEBUG: 00:53:58.090: Image device reported finger status: off 389s (process:1959): libfprint-image_device-DEBUG: 00:53:58.090: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 389s (process:1959): libfprint-image_device-DEBUG: 00:53:58.090: Deactivating image device 389s (process:1959): libfprint-image_device-DEBUG: 00:53:58.090: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_DEACTIVATING 389s (process:1959): libfprint-image_device-DEBUG: 00:53:58.090: Image device deactivation completed 389s (process:1959): libfprint-image_device-DEBUG: 00:53:58.090: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE 389s (process:1959): libfprint-image-DEBUG: 00:53:58.114: Minutiae scan completed in 0.023048 secs 389s (process:1959): libfprint-print-DEBUG: 00:53:58.121: score 10/40 389s (process:1959): libfprint-print-DEBUG: 00:53:58.127: score 10/40 389s (process:1959): libfprint-print-DEBUG: 00:53:58.133: score 10/40 389s (process:1959): libfprint-print-DEBUG: 00:53:58.140: score 10/40 389s (process:1959): libfprint-print-DEBUG: 00:53:58.146: score 10/40 389s (process:1959): libfprint-print-DEBUG: 00:53:58.378: score 855/40 389s (process:1959): libfprint-device-DEBUG: 00:53:58.378: Device reported identify result 389s (process:1959): libfprint-device-DEBUG: 00:53:58.378: Device reported identify completion 389s (process:1959): libfprint-device-DEBUG: 00:53:58.378: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 389s (process:1959): libfprint-device-DEBUG: 00:53:58.378: Updated temperature model after 0.29 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 389s (process:1959): libfprint-device-DEBUG: 00:53:58.378: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 389s (process:1959): libfprint-image_device-DEBUG: 00:53:58.378: Activating image device 389s (process:1959): libfprint-image_device-DEBUG: 00:53:58.378: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING 389s (process:1959): libfprint-image_device-DEBUG: 00:53:58.378: Image device activation completed 389s (process:1959): libfprint-image_device-DEBUG: 00:53:58.378: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE 389s (process:1959): libfprint-image_device-DEBUG: 00:53:58.378: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 389s (process:1959): libfprint-device-DEBUG: 00:53:58.378: Device reported finger status change: FP_FINGER_STATUS_NEEDED 389s (process:1959): libfprint-virtual_image-DEBUG: 00:53:58.379: image data: 0x175cbf8 389s (process:1959): libfprint-device-DEBUG: 00:53:58.379: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 389s (process:1959): libfprint-image_device-DEBUG: 00:53:58.379: Image device reported finger status: on 389s (process:1959): libfprint-image_device-DEBUG: 00:53:58.379: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 389s (process:1959): libfprint-image_device-DEBUG: 00:53:58.379: Image device captured an image 389s (process:1959): libfprint-image_device-DEBUG: 00:53:58.379: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 389s (process:1959): libfprint-device-DEBUG: 00:53:58.379: Device reported finger status change: FP_FINGER_STATUS_PRESENT 389s (process:1959): libfprint-device-DEBUG: 00:53:58.379: Device reported finger status change: FP_FINGER_STATUS_NONE 389s (process:1959): libfprint-image_device-DEBUG: 00:53:58.379: Image device reported finger status: off 389s (process:1959): libfprint-image_device-DEBUG: 00:53:58.379: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 389s (process:1959): libfprint-image_device-DEBUG: 00:53:58.379: Deactivating image device 389s (process:1959): libfprint-image_device-DEBUG: 00:53:58.379: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_DEACTIVATING 389s (process:1959): libfprint-image_device-DEBUG: 00:53:58.379: Image device deactivation completed 389s (process:1959): libfprint-image_device-DEBUG: 00:53:58.379: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE 389s (process:1959): libfprint-image-DEBUG: 00:53:58.404: Minutiae scan completed in 0.025322 secs 390s (process:1959): libfprint-print-DEBUG: 00:53:59.550: score 1093/40 390s (process:1959): libfprint-device-DEBUG: 00:53:59.550: Device reported identify result 390s (process:1959): libfprint-device-DEBUG: 00:53:59.550: Device reported identify completion 390s (process:1959): libfprint-device-DEBUG: 00:53:59.550: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 390s (process:1959): libfprint-device-DEBUG: 00:53:59.550: Updated temperature model after 1.17 seconds, ratio 0.28 -> 0.29, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 390s (process:1959): libfprint-device-DEBUG: 00:53:59.550: Updated temperature model after 0.00 seconds, ratio 0.29 -> 0.29, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 390s (process:1959): libfprint-image_device-DEBUG: 00:53:59.550: Activating image device 390s (process:1959): libfprint-image_device-DEBUG: 00:53:59.550: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING 390s (process:1959): libfprint-image_device-DEBUG: 00:53:59.550: Image device activation completed 390s (process:1959): libfprint-image_device-DEBUG: 00:53:59.550: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE 390s (process:1959): libfprint-image_device-DEBUG: 00:53:59.550: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 390s (process:1959): libfprint-device-DEBUG: 00:53:59.550: Device reported finger status change: FP_FINGER_STATUS_NEEDED 390s (process:1959): libfprint-device-DEBUG: 00:53:59.550: Device reported identify result 390s (process:1959): libfprint-image_device-DEBUG: 00:53:59.550: Deactivating image device 390s (process:1959): libfprint-image_device-DEBUG: 00:53:59.550: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_DEACTIVATING 390s (process:1959): libfprint-image_device-DEBUG: 00:53:59.550: Image device deactivation completed 390s (process:1959): libfprint-image_device-DEBUG: 00:53:59.550: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE 390s (process:1959): libfprint-device-DEBUG: 00:53:59.550: Device reported identify completion 390s (process:1959): libfprint-device-DEBUG: 00:53:59.550: Device reported finger status change: FP_FINGER_STATUS_NONE 390s (process:1959): libfprint-device-DEBUG: 00:53:59.550: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 390s (process:1959): libfprint-device-DEBUG: 00:53:59.550: Updated temperature model after 0.00 seconds, ratio 0.29 -> 0.29, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 390s (process:1959): libfprint-device-DEBUG: 00:53:59.551: Updated temperature model after 0.00 seconds, ratio 0.29 -> 0.29, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 390s (process:1959): libfprint-image_device-DEBUG: 00:53:59.551: Activating image device 390s (process:1959): libfprint-image_device-DEBUG: 00:53:59.551: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING 390s (process:1959): libfprint-image_device-DEBUG: 00:53:59.551: Image device activation completed 390s (process:1959): libfprint-image_device-DEBUG: 00:53:59.551: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE 390s (process:1959): libfprint-image_device-DEBUG: 00:53:59.551: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 390s (process:1959): libfprint-device-DEBUG: 00:53:59.551: Device reported finger status change: FP_FINGER_STATUS_NEEDED 390s (process:1959): libfprint-image_device-DEBUG: 00:53:59.551: Deactivating image device 390s (process:1959): libfprint-image_device-DEBUG: 00:53:59.551: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_DEACTIVATING 390s (process:1959): libfprint-image_device-DEBUG: 00:53:59.551: Image device deactivation completed 390s (process:1959): libfprint-image_device-DEBUG: 00:53:59.551: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE 390s (process:1959): libfprint-device-DEBUG: 00:53:59.551: Device reported generic error (An unspecified error occurred!) during action; action was: FPI_DEVICE_ACTION_IDENTIFY 390s (process:1959): libfprint-device-DEBUG: 00:53:59.551: Device reported identify completion 390s (process:1959): libfprint-device-DEBUG: 00:53:59.551: Device reported finger status change: FP_FINGER_STATUS_NONE 390s (process:1959): libfprint-device-DEBUG: 00:53:59.551: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 390s (process:1959): libfprint-device-DEBUG: 00:53:59.551: Updated temperature model after 0.00 seconds, ratio 0.29 -> 0.29, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 390s (process:1959): libfprint-virtual_image-DEBUG: 00:53:59.551: 7399807612315: ../libfprint/drivers/virtual-image.c:244 390s (process:1959): libfprint-image_device-DEBUG: 00:53:59.651: Image device close completed 390s (process:1959): libfprint-device-DEBUG: 00:53:59.651: Device reported close completion 390s (process:1959): libfprint-device-DEBUG: 00:53:59.651: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 390s (process:1959): libfprint-device-DEBUG: 00:53:59.651: Updated temperature model after 0.10 seconds, ratio 0.29 -> 0.29, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 390s Print was processed, continuing 390s Print was processed, continuing 390s Print was processed, continuing 390s Print was processed, continuing 390s Print was processed, continuing 390s Enroll done 390s Print was processed, continuing 390s Print was processed, continuing 390s Print was processed, continuing 390s Print was processed, continuing 390s Print was processed, continuing 390s Enroll done 390s Identify finished 390s Identify finished 390s Identify finished 390s fp - device - retry - quark: The swipe was too short, please try again. (1) 390s Identify finished 390s fp - device - error - quark: An unspecified error occurred! (0) 390s ok 390s test_verify_serialized (__main__.VirtualImage.test_verify_serialized) ... (process:1959): libfprint-virtual_image-DEBUG: 00:53:59.651: 7399807712698: ../libfprint/drivers/virtual-image.c:216 390s (process:1959): libfprint-virtual_device_connection-DEBUG: 00:53:59.651: 7399807712717: ../libfprint/drivers/virtual-device-listener.c:153 390s (process:1959): libfprint-image_device-DEBUG: 00:53:59.751: Image device open completed 390s (process:1959): libfprint-device-DEBUG: 00:53:59.751: Device reported open completion 390s (process:1959): libfprint-device-DEBUG: 00:53:59.751: Completing action FPI_DEVICE_ACTION_OPEN in idle! 390s (process:1959): libfprint-device-DEBUG: 00:53:59.751: Updated temperature model after 0.10 seconds, ratio 0.29 -> 0.29, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 390s (process:1959): libfprint-device-DEBUG: 00:53:59.752: Updated temperature model after 0.00 seconds, ratio 0.29 -> 0.29, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 390s (process:1959): libfprint-image_device-DEBUG: 00:53:59.752: Activating image device 390s (process:1959): libfprint-image_device-DEBUG: 00:53:59.752: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING 390s (process:1959): libfprint-image_device-DEBUG: 00:53:59.752: Image device activation completed 390s (process:1959): libfprint-image_device-DEBUG: 00:53:59.752: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE 390s (process:1959): libfprint-image_device-DEBUG: 00:53:59.752: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 390s (process:1959): libfprint-device-DEBUG: 00:53:59.752: Device reported finger status change: FP_FINGER_STATUS_NEEDED 390s (process:1959): libfprint-virtual_device_connection-DEBUG: 00:53:59.752: Got a new connection! 390s (process:1959): libfprint-virtual_image-DEBUG: 00:53:59.752: image data: 0x175cbf8 390s (process:1959): libfprint-device-DEBUG: 00:53:59.752: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 390s (process:1959): libfprint-image_device-DEBUG: 00:53:59.752: Image device reported finger status: on 390s (process:1959): libfprint-image_device-DEBUG: 00:53:59.752: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 390s (process:1959): libfprint-image_device-DEBUG: 00:53:59.752: Image device captured an image 390s (process:1959): libfprint-image_device-DEBUG: 00:53:59.752: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 390s (process:1959): libfprint-device-DEBUG: 00:53:59.752: Device reported finger status change: FP_FINGER_STATUS_PRESENT 390s (process:1959): libfprint-device-DEBUG: 00:53:59.752: Device reported finger status change: FP_FINGER_STATUS_NONE 390s (process:1959): libfprint-image_device-DEBUG: 00:53:59.752: Image device reported finger status: off 390s (process:1959): libfprint-image_device-DEBUG: 00:53:59.752: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 390s (process:1959): libfprint-image-DEBUG: 00:53:59.778: Minutiae scan completed in 0.026216 secs 390s (process:1959): libfprint-device-DEBUG: 00:53:59.779: Device reported enroll progress, reported 1 of 5 have been completed 390s (process:1959): libfprint-image_device-DEBUG: 00:53:59.779: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 390s (process:1959): libfprint-device-DEBUG: 00:53:59.779: Device reported finger status change: FP_FINGER_STATUS_NEEDED 390s (process:1959): libfprint-device-DEBUG: 00:53:59.779: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 390s (process:1959): libfprint-image_device-DEBUG: 00:53:59.779: Image device reported finger status: on 390s (process:1959): libfprint-image_device-DEBUG: 00:53:59.779: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 390s (process:1959): libfprint-virtual_image-DEBUG: 00:53:59.779: image data: 0x175cbf8 390s (process:1959): libfprint-image_device-DEBUG: 00:53:59.779: Image device captured an image 390s (process:1959): libfprint-image_device-DEBUG: 00:53:59.779: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 390s (process:1959): libfprint-device-DEBUG: 00:53:59.779: Device reported finger status change: FP_FINGER_STATUS_PRESENT 390s (process:1959): libfprint-image-DEBUG: 00:53:59.805: Minutiae scan completed in 0.026226 secs 390s (process:1959): libfprint-device-DEBUG: 00:53:59.806: Device reported enroll progress, reported 2 of 5 have been completed 390s (process:1959): libfprint-device-DEBUG: 00:53:59.806: Device reported finger status change: FP_FINGER_STATUS_NONE 390s (process:1959): libfprint-image_device-DEBUG: 00:53:59.806: Image device reported finger status: off 390s (process:1959): libfprint-image_device-DEBUG: 00:53:59.806: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 390s (process:1959): libfprint-image_device-DEBUG: 00:53:59.806: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 390s (process:1959): libfprint-device-DEBUG: 00:53:59.806: Device reported finger status change: FP_FINGER_STATUS_NEEDED 390s (process:1959): libfprint-virtual_image-DEBUG: 00:53:59.806: image data: 0x175cbf8 390s (process:1959): libfprint-device-DEBUG: 00:53:59.806: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 390s (process:1959): libfprint-image_device-DEBUG: 00:53:59.806: Image device reported finger status: on 390s (process:1959): libfprint-image_device-DEBUG: 00:53:59.806: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 390s (process:1959): libfprint-image_device-DEBUG: 00:53:59.806: Image device captured an image 390s (process:1959): libfprint-image_device-DEBUG: 00:53:59.806: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 390s (process:1959): libfprint-device-DEBUG: 00:53:59.806: Device reported finger status change: FP_FINGER_STATUS_PRESENT 390s (process:1959): libfprint-device-DEBUG: 00:53:59.806: Device reported finger status change: FP_FINGER_STATUS_NONE 390s (process:1959): libfprint-image_device-DEBUG: 00:53:59.806: Image device reported finger status: off 390s (process:1959): libfprint-image_device-DEBUG: 00:53:59.806: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 390s (process:1959): libfprint-image-DEBUG: 00:53:59.833: Minutiae scan completed in 0.026396 secs 390s (process:1959): libfprint-device-DEBUG: 00:53:59.833: Device reported enroll progress, reported 3 of 5 have been completed 390s (process:1959): libfprint-image_device-DEBUG: 00:53:59.833: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 390s (process:1959): libfprint-device-DEBUG: 00:53:59.833: Device reported finger status change: FP_FINGER_STATUS_NEEDED 390s (process:1959): libfprint-virtual_image-DEBUG: 00:53:59.833: image data: 0x175cbf8 390s (process:1959): libfprint-device-DEBUG: 00:53:59.833: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 390s (process:1959): libfprint-image_device-DEBUG: 00:53:59.833: Image device reported finger status: on 390s (process:1959): libfprint-image_device-DEBUG: 00:53:59.833: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 390s (process:1959): libfprint-image_device-DEBUG: 00:53:59.833: Image device captured an image 390s (process:1959): libfprint-image_device-DEBUG: 00:53:59.833: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 390s (process:1959): libfprint-device-DEBUG: 00:53:59.833: Device reported finger status change: FP_FINGER_STATUS_PRESENT 390s (process:1959): libfprint-device-DEBUG: 00:53:59.833: Device reported finger status change: FP_FINGER_STATUS_NONE 390s (process:1959): libfprint-image_device-DEBUG: 00:53:59.833: Image device reported finger status: off 390s (process:1959): libfprint-image_device-DEBUG: 00:53:59.833: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 390s (process:1959): libfprint-image-DEBUG: 00:53:59.859: Minutiae scan completed in 0.025721 secs 390s (process:1959): libfprint-device-DEBUG: 00:53:59.859: Device reported enroll progress, reported 4 of 5 have been completed 390s (process:1959): libfprint-image_device-DEBUG: 00:53:59.859: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 390s (process:1959): libfprint-device-DEBUG: 00:53:59.859: Device reported finger status change: FP_FINGER_STATUS_NEEDED 390s (process:1959): libfprint-virtual_image-DEBUG: 00:53:59.859: image data: 0x175cbf8 390s (process:1959): libfprint-device-DEBUG: 00:53:59.860: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 390s (process:1959): libfprint-image_device-DEBUG: 00:53:59.860: Image device reported finger status: on 390s (process:1959): libfprint-image_device-DEBUG: 00:53:59.860: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 390s (process:1959): libfprint-image_device-DEBUG: 00:53:59.860: Image device captured an image 390s (process:1959): libfprint-image_device-DEBUG: 00:53:59.860: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 390s (process:1959): libfprint-device-DEBUG: 00:53:59.860: Device reported finger status change: FP_FINGER_STATUS_PRESENT 390s (process:1959): libfprint-device-DEBUG: 00:53:59.860: Device reported finger status change: FP_FINGER_STATUS_NONE 390s (process:1959): libfprint-image_device-DEBUG: 00:53:59.860: Image device reported finger status: off 390s (process:1959): libfprint-image_device-DEBUG: 00:53:59.860: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 390s (process:1959): libfprint-image-DEBUG: 00:53:59.887: Minutiae scan completed in 0.027163 secs 390s (process:1959): libfprint-device-DEBUG: 00:53:59.887: Device reported enroll progress, reported 5 of 5 have been completed 390s (process:1959): libfprint-image_device-DEBUG: 00:53:59.887: Deactivating image device 390s (process:1959): libfprint-image_device-DEBUG: 00:53:59.887: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_DEACTIVATING 390s (process:1959): libfprint-image_device-DEBUG: 00:53:59.887: Image device deactivation completed 390s (process:1959): libfprint-image_device-DEBUG: 00:53:59.887: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE 390s (process:1959): libfprint-device-DEBUG: 00:53:59.887: Device reported enroll completion 390s (process:1959): libfprint-device-DEBUG: 00:53:59.887: Print for finger FP_FINGER_LEFT_THUMB enrolled 390s (process:1959): libfprint-device-DEBUG: 00:53:59.887: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 390s (process:1959): libfprint-device-DEBUG: 00:53:59.887: Updated temperature model after 0.14 seconds, ratio 0.29 -> 0.29, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 390s (process:1959): libfprint-device-DEBUG: 00:53:59.888: Updated temperature model after 0.00 seconds, ratio 0.29 -> 0.29, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 390s (process:1959): libfprint-image_device-DEBUG: 00:53:59.888: Activating image device 390s (process:1959): libfprint-image_device-DEBUG: 00:53:59.888: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING 390s (process:1959): libfprint-image_device-DEBUG: 00:53:59.888: Image device activation completed 390s (process:1959): libfprint-image_device-DEBUG: 00:53:59.888: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE 390s (process:1959): libfprint-image_device-DEBUG: 00:53:59.888: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 390s (process:1959): libfprint-device-DEBUG: 00:53:59.888: Device reported finger status change: FP_FINGER_STATUS_NEEDED 390s (process:1959): libfprint-virtual_image-DEBUG: 00:53:59.888: image data: 0x175cbf8 390s (process:1959): libfprint-device-DEBUG: 00:53:59.888: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 390s (process:1959): libfprint-image_device-DEBUG: 00:53:59.888: Image device reported finger status: on 390s (process:1959): libfprint-image_device-DEBUG: 00:53:59.888: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 390s (process:1959): libfprint-image_device-DEBUG: 00:53:59.888: Image device captured an image 390s (process:1959): libfprint-image_device-DEBUG: 00:53:59.888: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 390s (process:1959): libfprint-device-DEBUG: 00:53:59.888: Device reported finger status change: FP_FINGER_STATUS_PRESENT 390s (process:1959): libfprint-device-DEBUG: 00:53:59.888: Device reported finger status change: FP_FINGER_STATUS_NONE 390s (process:1959): libfprint-image_device-DEBUG: 00:53:59.888: Image device reported finger status: off 390s (process:1959): libfprint-image_device-DEBUG: 00:53:59.888: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 390s (process:1959): libfprint-image_device-DEBUG: 00:53:59.888: Deactivating image device 390s (process:1959): libfprint-image_device-DEBUG: 00:53:59.888: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_DEACTIVATING 390s (process:1959): libfprint-image_device-DEBUG: 00:53:59.888: Image device deactivation completed 390s (process:1959): libfprint-image_device-DEBUG: 00:53:59.888: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE 390s (process:1959): libfprint-image-DEBUG: 00:53:59.914: Minutiae scan completed in 0.025599 secs 392s (process:1959): libfprint-print-DEBUG: 00:54:01.062: score 1093/40 392s (process:1959): libfprint-device-DEBUG: 00:54:01.062: Device reported verify result 392s (process:1959): libfprint-device-DEBUG: 00:54:01.062: Device reported verify completion 392s (process:1959): libfprint-device-DEBUG: 00:54:01.062: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 392s (process:1959): libfprint-device-DEBUG: 00:54:01.062: Updated temperature model after 1.17 seconds, ratio 0.29 -> 0.29, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 392s (process:1959): libfprint-device-DEBUG: 00:54:01.062: Updated temperature model after 0.00 seconds, ratio 0.29 -> 0.29, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 392s (process:1959): libfprint-image_device-DEBUG: 00:54:01.062: Activating image device 392s (process:1959): libfprint-image_device-DEBUG: 00:54:01.062: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING 392s (process:1959): libfprint-image_device-DEBUG: 00:54:01.062: Image device activation completed 392s (process:1959): libfprint-image_device-DEBUG: 00:54:01.062: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE 392s (process:1959): libfprint-image_device-DEBUG: 00:54:01.062: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 392s (process:1959): libfprint-device-DEBUG: 00:54:01.062: Device reported finger status change: FP_FINGER_STATUS_NEEDED 392s (process:1959): libfprint-virtual_image-DEBUG: 00:54:01.062: image data: 0x17c4950 392s (process:1959): libfprint-device-DEBUG: 00:54:01.062: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 392s (process:1959): libfprint-image_device-DEBUG: 00:54:01.062: Image device reported finger status: on 392s (process:1959): libfprint-image_device-DEBUG: 00:54:01.063: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 392s (process:1959): libfprint-image_device-DEBUG: 00:54:01.063: Image device captured an image 392s (process:1959): libfprint-image_device-DEBUG: 00:54:01.063: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 392s (process:1959): libfprint-device-DEBUG: 00:54:01.063: Device reported finger status change: FP_FINGER_STATUS_PRESENT 392s (process:1959): libfprint-device-DEBUG: 00:54:01.063: Device reported finger status change: FP_FINGER_STATUS_NONE 392s (process:1959): libfprint-image_device-DEBUG: 00:54:01.063: Image device reported finger status: off 392s (process:1959): libfprint-image_device-DEBUG: 00:54:01.063: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 392s (process:1959): libfprint-image_device-DEBUG: 00:54:01.063: Deactivating image device 392s (process:1959): libfprint-image_device-DEBUG: 00:54:01.063: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_DEACTIVATING 392s (process:1959): libfprint-image_device-DEBUG: 00:54:01.063: Image device deactivation completed 392s (process:1959): libfprint-image_device-DEBUG: 00:54:01.063: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE 392s (process:1959): libfprint-image-DEBUG: 00:54:01.085: Minutiae scan completed in 0.022498 secs 392s (process:1959): libfprint-print-DEBUG: 00:54:01.092: score 10/40 392s (process:1959): libfprint-print-DEBUG: 00:54:01.099: score 10/40 392s (process:1959): libfprint-print-DEBUG: 00:54:01.105: score 10/40 392s (process:1959): libfprint-print-DEBUG: 00:54:01.112: score 10/40 392s (process:1959): libfprint-print-DEBUG: 00:54:01.118: score 10/40 392s (process:1959): libfprint-device-DEBUG: 00:54:01.118: Device reported verify result 392s (process:1959): libfprint-device-DEBUG: 00:54:01.118: Device reported verify completion 392s (process:1959): libfprint-device-DEBUG: 00:54:01.118: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 392s (process:1959): libfprint-device-DEBUG: 00:54:01.118: Updated temperature model after 0.06 seconds, ratio 0.29 -> 0.29, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 392s (process:1959): libfprint-virtual_image-DEBUG: 00:54:01.118: 7399809179587: ../libfprint/drivers/virtual-image.c:244 392s (process:1959): libfprint-image_device-DEBUG: 00:54:01.218: Image device close completed 392s (process:1959): libfprint-device-DEBUG: 00:54:01.218: Device reported close completion 392s (process:1959): libfprint-device-DEBUG: 00:54:01.218: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 392s (process:1959): libfprint-device-DEBUG: 00:54:01.218: Updated temperature model after 0.10 seconds, ratio 0.29 -> 0.29, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 392s Print was processed, continuing 392s Print was processed, continuing 392s Print was processed, continuing 392s Print was processed, continuing 392s Print was processed, continuing 392s Enroll done 392s ok 392s 392s ---------------------------------------------------------------------- 392s Ran 5 tests in 7.057s 392s 392s OK 392s PASS: libfprint-2/virtual-image.test 392s Running test: libfprint-2/fpi-ssm.test 392s TAP version 14 392s # random seed: R02Sb7e3de2676e84ed281f4e618e9759e81 392s 1..42 392s # Start of ssm tests 392s ok 1 /ssm/new 392s ok 2 /ssm/set_data 392s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 0 392s ok 3 /ssm/start 392s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 0 392s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 1 392s ok 4 /ssm/next 392s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 0 392s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 2 392s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 1 392s ok 5 /ssm/jump_to_state 392s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 0 392s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM completed successfully 392s ok 6 /ssm/mark_completed 392s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 0 392s # 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. 392s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM completed with error: The driver encountered a protocol error with the device. 392s ok 7 /ssm/mark_failed 392s # Start of new tests 392s ok 8 /ssm/new/full 392s ok 9 /ssm/new/no_handler 392s ok 10 /ssm/new/wrong_states 392s # End of new tests 392s # Start of set_data tests 392s ok 11 /ssm/set_data/cleanup 392s # End of set_data tests 392s # Start of start tests 392s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM_SINGLE_STATE entering state 0 392s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM_SINGLE_STATE completed successfully 392s ok 12 /ssm/start/single 392s # End of start tests 392s # Start of next tests 392s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 0 392s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 1 392s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 2 392s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 3 392s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM completed successfully 392s ok 13 /ssm/next/complete 392s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 1 392s ok 14 /ssm/next/not_started 392s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 0 392s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 1 392s ok 15 /ssm/next/with_delayed 392s # End of next tests 392s # Start of jump_to_state tests 392s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 2 392s ok 16 /ssm/jump_to_state/not_started 392s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 0 392s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 2 392s ok 17 /ssm/jump_to_state/with_delayed 392s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 0 392s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 3 392s ok 18 /ssm/jump_to_state/last 392s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 0 392s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 14 392s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state -10 392s ok 19 /ssm/jump_to_state/wrong 392s # End of jump_to_state tests 392s # Start of mark_completed tests 392s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM completed successfully 392s ok 20 /ssm/mark_completed/not_started 392s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 0 392s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM completed successfully 392s ok 21 /ssm/mark_completed/with_delayed 392s # End of mark_completed tests 392s # Start of mark_failed tests 392s # 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. 392s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM completed with error: The driver encountered a protocol error with the device. 392s ok 22 /ssm/mark_failed/not_started 392s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 0 392s # 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. 392s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM completed with error: The driver encountered a protocol error with the device. 392s ok 23 /ssm/mark_failed/with_delayed 392s # End of mark_failed tests 392s # Start of delayed tests 392s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 0 392s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 1 392s ok 24 /ssm/delayed/next 392s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 0 392s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 2 392s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 1 392s ok 25 /ssm/delayed/jump_to_state 392s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 0 392s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM completed successfully 392s ok 26 /ssm/delayed/mark_completed 392s # Start of next tests 392s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 0 392s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM cancelled delayed state change 392s ok 27 /ssm/delayed/next/cancel 392s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 1 392s ok 28 /ssm/delayed/next/not_started 392s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 0 392s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 1 392s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 2 392s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 3 392s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM completed successfully 392s ok 29 /ssm/delayed/next/complete 392s # End of next tests 392s # Start of jump_to_state tests 392s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 0 392s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM cancelled delayed state change 392s Executing: libfprint-2/fpi-ssm.test 393s ok 30 /ssm/delayed/jump_to_state/cancel 393s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 2 393s ok 31 /ssm/delayed/jump_to_state/not_started 393s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 0 393s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 3 393s ok 32 /ssm/delayed/jump_to_state/last 393s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 0 393s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 14 393s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state -10 393s ok 33 /ssm/delayed/jump_to_state/wrong 393s # End of jump_to_state tests 393s # Start of mark_completed tests 393s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 0 393s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM cancelled delayed state change 393s ok 34 /ssm/delayed/mark_completed/cancel 393s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM completed successfully 393s ok 35 /ssm/delayed/mark_completed/not_started 393s # End of mark_completed tests 393s # Start of cancel tests 393s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM cancelled delayed state change 393s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 0 393s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM cancelled delayed state change 393s ok 36 /ssm/delayed/cancel/error 393s # End of cancel tests 393s # End of delayed tests 393s # Start of subssm tests 393s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 0 393s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SUB_SSM entering state 0 393s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SUB_SSM entering state 1 393s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SUB_SSM completed successfully 393s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 1 393s ok 37 /ssm/subssm/start 393s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 0 393s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SUB_SSM entering state 0 393s # 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. 393s # 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. 393s # 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. 393s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM completed with error: The device is still busy with another operation, please try again later. 393s ok 38 /ssm/subssm/mark_failed 393s # Start of start tests 393s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 0 393s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SUB_SSM entering state 0 393s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SUB_SSM entering state 0 393s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SUB_SSM completed successfully 393s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 1 393s ok 39 /ssm/subssm/start/with_started 393s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 0 393s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SUB_SSM entering state 0 393s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SUB_SSM completed successfully 393s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 1 393s ok 40 /ssm/subssm/start/with_delayed 393s # End of start tests 393s # End of subssm tests 393s # Start of cleanup tests 393s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 0 393s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 2 393s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 3 393s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM completed successfully 393s ok 41 /ssm/cleanup/complete 393s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 0 393s # libfprint-SSM-DEBUG: [fake_test_dev] SSM FPI_TEST_SSM failed in state 0 with error: non-cleanup 393s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 2 393s # libfprint-SSM-DEBUG: [fake_test_dev] SSM FPI_TEST_SSM failed in state 2 (cleanup) with error: cleanup 1 393s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 3 393s # libfprint-SSM-DEBUG: [fake_test_dev] SSM FPI_TEST_SSM failed in state 3 (cleanup) with error: cleanup 2 393s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM completed with error: non-cleanup 393s ok 42 /ssm/cleanup/fail 393s # End of cleanup tests 393s # End of ssm tests 393s PASS: libfprint-2/fpi-ssm.test 393s Running test: libfprint-2/driver-egismoc.test 393s ** (umockdev-run:1970): DEBUG: 00:54:02.391: umockdev.vala:127: Created udev test bed /tmp/umockdev.XZC612 393s ** (umockdev-run:1970): DEBUG: 00:54:02.392: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0/usb3/3-5 393s ** (umockdev-run:1970): DEBUG: 00:54:02.394: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0/usb3/3-5 (subsystem usb) 393s ** (umockdev-run:1970): DEBUG: 00:54:02.399: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.XZC612/dev/bus/usb/003/012 393s ** (umockdev-run:1970): DEBUG: 00:54:02.399: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0/usb3 393s ** (umockdev-run:1970): DEBUG: 00:54:02.401: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0/usb3 (subsystem usb) 393s ** (umockdev-run:1970): DEBUG: 00:54:02.405: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.XZC612/dev/bus/usb/003/001 393s ** (umockdev-run:1970): DEBUG: 00:54:02.406: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0 393s ** (umockdev-run:1970): DEBUG: 00:54:02.406: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0 (subsystem pci) 393s (process:1974): libfprint-context-DEBUG: 00:54:02.528: Initializing FpContext (libfprint version 1.94.8+tod1) 393s (process:1974): libfprint-tod-DEBUG: 00:54:02.528: Impossible to load the shared drivers dir Error opening directory “/usr/lib/arm-linux-gnueabihf/libfprint-2/tod-1”: No such file or directory 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.531: 7399810592410: ../libfprint/drivers/egismoc/egismoc.c:1597 393s (process:1974): libfprint-context-DEBUG: 00:54:02.531: No driver found for USB device 1D6B:0002 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.532: egismoc_probe enter --> 393s (process:1974): libfprint-device-DEBUG: 00:54:02.533: Device reported probe completion 393s (process:1974): libfprint-device-DEBUG: 00:54:02.533: Completing action FPI_DEVICE_ACTION_PROBE in idle! 393s (process:1974): libfprint-device-DEBUG: 00:54:02.533: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.535: Opening device 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.535: [egismoc] DEV_INIT_STATES entering state 0 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.536: [egismoc] DEV_INIT_STATES entering state 1 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.537: [egismoc] DEV_INIT_STATES entering state 2 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.538: [egismoc] DEV_INIT_STATES entering state 3 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.539: [egismoc] DEV_INIT_STATES entering state 4 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.540: [egismoc] DEV_INIT_STATES entering state 5 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.540: Execute command and get response 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.540: Get check bytes 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.540: [egismoc] CMD_STATES entering state 0 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.541: [egismoc] CMD_STATES entering state 1 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.542: Command receive callback 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.542: [egismoc] CMD_STATES completed successfully 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.542: Firmware version callback 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.542: Response suffix valid: yes 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.542: Device firmware version is 9050.1.1.81 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.542: [egismoc] DEV_INIT_STATES completed successfully 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.542: Task SSM done 393s (process:1974): libfprint-device-DEBUG: 00:54:02.542: Device reported open completion 393s (process:1974): libfprint-device-DEBUG: 00:54:02.542: Completing action FPI_DEVICE_ACTION_OPEN in idle! 393s (process:1974): libfprint-device-DEBUG: 00:54:02.542: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.543: List 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.543: [egismoc] LIST_STATES entering state 0 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.543: Execute command and get response 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.543: Get check bytes 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.543: [egismoc] CMD_STATES entering state 0 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.544: [egismoc] CMD_STATES entering state 1 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.544: Command receive callback 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.544: [egismoc] CMD_STATES completed successfully 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.544: List callback 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.544: Device fingerprint 1: FP1-20231016-1-AAA9163E-root 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.544: Device fingerprint 2: FP1-20231016-2-5102A0A3-root 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.544: Device fingerprint 3: FP1-20231016-3-5159A026-root 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.544: Device fingerprint 4: FP1-20231016-4-A25C1212-root 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.544: Device fingerprint 5: FP1-20231016-5-EC893AA9-root 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.544: Device fingerprint 6: \u0006\u001d\xcbc$ir%\xa22U֨\o\xff\x8ddY\x84\u0003\xbac\xcfO\xde\xc2!L\u001eN( 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.544: Device fingerprint 7: \xd7pܖsT3\xf6>\xd9\u0002"/[\xf8\u0017Iqpz\u000c\xfa,M\xdfm5\u007fq\xc6\xdew 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.544: Number of currently enrolled fingerprints on the device is 7 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.544: [egismoc] LIST_STATES entering state 1 393s (process:1974): libfprint-device-DEBUG: 00:54:02.545: Device reported listing completion 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.545: [egismoc] LIST_STATES completed successfully 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.545: Task SSM done 393s (process:1974): libfprint-device-DEBUG: 00:54:02.545: Completing action FPI_DEVICE_ACTION_LIST in idle! 393s (process:1974): libfprint-device-DEBUG: 00:54:02.545: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.545: Clear storage 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.545: [egismoc] DELETE_STATES entering state 0 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.545: Execute command and get response 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.545: Get check bytes 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.545: [egismoc] CMD_STATES entering state 0 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.546: [egismoc] CMD_STATES entering state 1 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.547: Command receive callback 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.547: [egismoc] CMD_STATES completed successfully 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.547: List callback 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.547: Device fingerprint 1: FP1-20231016-1-AAA9163E-root 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.547: Device fingerprint 2: FP1-20231016-2-5102A0A3-root 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.547: Device fingerprint 3: FP1-20231016-3-5159A026-root 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.547: Device fingerprint 4: FP1-20231016-4-A25C1212-root 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.547: Device fingerprint 5: FP1-20231016-5-EC893AA9-root 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.547: Device fingerprint 6: \u0006\u001d\xcbc$ir%\xa22U֨\o\xff\x8ddY\x84\u0003\xbac\xcfO\xde\xc2!L\u001eN( 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.547: Device fingerprint 7: \xd7pܖsT3\xf6>\xd9\u0002"/[\xf8\u0017Iqpz\u000c\xfa,M\xdfm5\u007fq\xc6\xdew 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.547: Number of currently enrolled fingerprints on the device is 7 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.547: [egismoc] DELETE_STATES entering state 1 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.547: Get delete command 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.547: Execute command and get response 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.547: Get check bytes 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.547: [egismoc] CMD_STATES entering state 0 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.548: [egismoc] CMD_STATES entering state 1 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.549: Command receive callback 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.549: [egismoc] CMD_STATES completed successfully 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.549: Delete callback 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.549: Response prefix valid: yes 393s (process:1974): libfprint-device-DEBUG: 00:54:02.549: Device reported deletion completion 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.549: [egismoc] DELETE_STATES completed successfully 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.549: Task SSM done 393s (process:1974): libfprint-device-DEBUG: 00:54:02.549: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 393s (process:1974): libfprint-device-DEBUG: 00:54:02.549: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.549: List 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.549: [egismoc] LIST_STATES entering state 0 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.549: Execute command and get response 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.549: Get check bytes 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.549: [egismoc] CMD_STATES entering state 0 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.550: [egismoc] CMD_STATES entering state 1 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.551: Command receive callback 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.551: [egismoc] CMD_STATES completed successfully 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.551: List callback 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.551: Number of currently enrolled fingerprints on the device is 0 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.551: [egismoc] LIST_STATES entering state 1 393s (process:1974): libfprint-device-DEBUG: 00:54:02.551: Device reported listing completion 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.551: [egismoc] LIST_STATES completed successfully 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.551: Task SSM done 393s (process:1974): libfprint-device-DEBUG: 00:54:02.551: Completing action FPI_DEVICE_ACTION_LIST in idle! 393s (process:1974): libfprint-device-DEBUG: 00:54:02.551: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 393s (process:1974): libfprint-device-DEBUG: 00:54:02.552: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.552: Enroll 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.552: [egismoc] ENROLL_STATES entering state 0 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.552: Execute command and get response 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.552: Get check bytes 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.552: [egismoc] CMD_STATES entering state 0 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.553: [egismoc] CMD_STATES entering state 1 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.553: Command receive callback 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.553: [egismoc] CMD_STATES completed successfully 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.553: List callback 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.553: Number of currently enrolled fingerprints on the device is 0 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.553: [egismoc] ENROLL_STATES entering state 1 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.553: [egismoc] ENROLL_STATES entering state 2 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.553: Execute command and get response 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.553: Get check bytes 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.553: [egismoc] CMD_STATES entering state 0 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.554: [egismoc] CMD_STATES entering state 1 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.555: Command receive callback 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.555: [egismoc] CMD_STATES completed successfully 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.555: Task SSM next state callback 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.555: [egismoc] ENROLL_STATES entering state 3 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.555: Execute command and get response 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.555: Get check bytes 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.555: [egismoc] CMD_STATES entering state 0 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.555: [egismoc] CMD_STATES entering state 1 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.556: Command receive callback 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.556: [egismoc] CMD_STATES completed successfully 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.556: Task SSM next state callback 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.556: [egismoc] ENROLL_STATES entering state 4 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.556: Wait for finger on sensor 393s (process:1974): libfprint-device-DEBUG: 00:54:02.556: Device reported finger status change: FP_FINGER_STATUS_NEEDED 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.556: Finger on sensor callback 393s (process:1974): libfprint-device-DEBUG: 00:54:02.556: Device reported finger status change: FP_FINGER_STATUS_PRESENT 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.556: [egismoc] ENROLL_STATES entering state 5 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.556: Execute command and get response 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.556: Get check bytes 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.556: [egismoc] CMD_STATES entering state 0 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.557: [egismoc] CMD_STATES entering state 1 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.558: Command receive callback 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.558: [egismoc] CMD_STATES completed successfully 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.558: Task SSM next state callback 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.558: [egismoc] ENROLL_STATES entering state 6 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.558: Get check command 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.558: Execute command and get response 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.558: Get check bytes 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.558: [egismoc] CMD_STATES entering state 0 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.559: [egismoc] CMD_STATES entering state 1 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.559: Command receive callback 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.559: [egismoc] CMD_STATES completed successfully 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.559: Enroll check callback 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.559: Response suffix valid: yes 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.559: [egismoc] ENROLL_STATES entering state 7 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.559: Execute command and get response 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.559: Get check bytes 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.559: [egismoc] CMD_STATES entering state 0 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.560: [egismoc] CMD_STATES entering state 1 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.560: Command receive callback 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.560: [egismoc] CMD_STATES completed successfully 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.560: Task SSM next state callback 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.560: [egismoc] ENROLL_STATES entering state 8 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.560: Execute command and get response 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.560: Get check bytes 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.560: [egismoc] CMD_STATES entering state 0 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.561: [egismoc] CMD_STATES entering state 1 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.562: Command receive callback 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.562: [egismoc] CMD_STATES completed successfully 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.562: Task SSM next state callback 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.562: [egismoc] ENROLL_STATES entering state 9 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.562: Execute command and get response 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.562: Get check bytes 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.562: [egismoc] CMD_STATES entering state 0 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.562: [egismoc] CMD_STATES entering state 1 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.563: Command receive callback 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.563: [egismoc] CMD_STATES completed successfully 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.563: Task SSM next state callback 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.563: [egismoc] ENROLL_STATES entering state 10 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.563: Wait for finger on sensor 393s (process:1974): libfprint-device-DEBUG: 00:54:02.563: Device reported finger status change: FP_FINGER_STATUS_NEEDED 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.564: Finger on sensor callback 393s (process:1974): libfprint-device-DEBUG: 00:54:02.564: Device reported finger status change: FP_FINGER_STATUS_PRESENT 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.564: [egismoc] ENROLL_STATES entering state 11 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.564: Execute command and get response 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.564: Get check bytes 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.564: [egismoc] CMD_STATES entering state 0 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.564: [egismoc] CMD_STATES entering state 1 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.565: Command receive callback 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.565: [egismoc] CMD_STATES completed successfully 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.565: Read capture callback 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.565: Response prefix valid: yes 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.565: Response suffix valid: yes 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.565: Partial capture successful. Please touch the sensor again (1/10) 393s (process:1974): libfprint-device-DEBUG: 00:54:02.565: Device reported enroll progress, reported 1 of 10 have been completed 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.565: [egismoc] ENROLL_STATES entering state 8 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.565: Execute command and get response 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.565: Get check bytes 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.565: [egismoc] CMD_STATES entering state 0 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.566: [egismoc] CMD_STATES entering state 1 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.566: Command receive callback 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.566: [egismoc] CMD_STATES completed successfully 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.566: Task SSM next state callback 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.567: [egismoc] ENROLL_STATES entering state 9 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.567: Execute command and get response 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.567: Get check bytes 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.567: [egismoc] CMD_STATES entering state 0 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.568: [egismoc] CMD_STATES entering state 1 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.569: Command receive callback 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.569: [egismoc] CMD_STATES completed successfully 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.569: Task SSM next state callback 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.569: [egismoc] ENROLL_STATES entering state 10 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.569: Wait for finger on sensor 393s (process:1974): libfprint-device-DEBUG: 00:54:02.569: Device reported finger status change: FP_FINGER_STATUS_NEEDED 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.569: Finger on sensor callback 393s (process:1974): libfprint-device-DEBUG: 00:54:02.569: Device reported finger status change: FP_FINGER_STATUS_PRESENT 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.569: [egismoc] ENROLL_STATES entering state 11 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.569: Execute command and get response 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.569: Get check bytes 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.569: [egismoc] CMD_STATES entering state 0 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.570: [egismoc] CMD_STATES entering state 1 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.571: Command receive callback 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.571: [egismoc] CMD_STATES completed successfully 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.571: Read capture callback 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.571: Response prefix valid: yes 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.571: Response suffix valid: yes 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.571: Partial capture successful. Please touch the sensor again (2/10) 393s (process:1974): libfprint-device-DEBUG: 00:54:02.571: Device reported enroll progress, reported 2 of 10 have been completed 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.571: [egismoc] ENROLL_STATES entering state 8 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.571: Execute command and get response 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.571: Get check bytes 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.571: [egismoc] CMD_STATES entering state 0 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.572: [egismoc] CMD_STATES entering state 1 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.573: Command receive callback 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.573: [egismoc] CMD_STATES completed successfully 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.573: Task SSM next state callback 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.573: [egismoc] ENROLL_STATES entering state 9 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.573: Execute command and get response 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.573: Get check bytes 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.573: [egismoc] CMD_STATES entering state 0 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.573: [egismoc] CMD_STATES entering state 1 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.574: Command receive callback 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.574: [egismoc] CMD_STATES completed successfully 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.574: Task SSM next state callback 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.574: [egismoc] ENROLL_STATES entering state 10 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.574: Wait for finger on sensor 393s (process:1974): libfprint-device-DEBUG: 00:54:02.574: Device reported finger status change: FP_FINGER_STATUS_NEEDED 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.575: Finger on sensor callback 393s (process:1974): libfprint-device-DEBUG: 00:54:02.575: Device reported finger status change: FP_FINGER_STATUS_PRESENT 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.575: [egismoc] ENROLL_STATES entering state 11 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.575: Execute command and get response 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.575: Get check bytes 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.575: [egismoc] CMD_STATES entering state 0 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.575: [egismoc] CMD_STATES entering state 1 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.576: Command receive callback 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.576: [egismoc] CMD_STATES completed successfully 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.576: Read capture callback 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.576: Response prefix valid: yes 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.576: Response suffix valid: NO 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.576: Response prefix valid: yes 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.576: Response suffix valid: yes 393s (process:1974): libfprint-device-DEBUG: 00:54:02.576: Device reported enroll progress, reported 2 of 10 have been completed 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.576: [egismoc] ENROLL_STATES entering state 8 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.576: Execute command and get response 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.576: Get check bytes 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.576: [egismoc] CMD_STATES entering state 0 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.577: [egismoc] CMD_STATES entering state 1 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.578: Command receive callback 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.578: [egismoc] CMD_STATES completed successfully 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.578: Task SSM next state callback 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.578: [egismoc] ENROLL_STATES entering state 9 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.578: Execute command and get response 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.578: Get check bytes 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.578: [egismoc] CMD_STATES entering state 0 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.578: [egismoc] CMD_STATES entering state 1 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.579: Command receive callback 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.579: [egismoc] CMD_STATES completed successfully 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.579: Task SSM next state callback 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.579: [egismoc] ENROLL_STATES entering state 10 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.579: Wait for finger on sensor 393s (process:1974): libfprint-device-DEBUG: 00:54:02.579: Device reported finger status change: FP_FINGER_STATUS_NEEDED 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.580: Finger on sensor callback 393s (process:1974): libfprint-device-DEBUG: 00:54:02.580: Device reported finger status change: FP_FINGER_STATUS_PRESENT 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.580: [egismoc] ENROLL_STATES entering state 11 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.580: Execute command and get response 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.580: Get check bytes 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.580: [egismoc] CMD_STATES entering state 0 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.580: [egismoc] CMD_STATES entering state 1 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.581: Command receive callback 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.581: [egismoc] CMD_STATES completed successfully 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.581: Read capture callback 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.581: Response prefix valid: yes 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.581: Response suffix valid: yes 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.581: Partial capture successful. Please touch the sensor again (3/10) 393s (process:1974): libfprint-device-DEBUG: 00:54:02.581: Device reported enroll progress, reported 3 of 10 have been completed 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.581: [egismoc] ENROLL_STATES entering state 8 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.581: Execute command and get response 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.581: Get check bytes 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.581: [egismoc] CMD_STATES entering state 0 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.582: [egismoc] CMD_STATES entering state 1 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.583: Command receive callback 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.583: [egismoc] CMD_STATES completed successfully 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.583: Task SSM next state callback 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.583: [egismoc] ENROLL_STATES entering state 9 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.583: Execute command and get response 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.583: Get check bytes 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.583: [egismoc] CMD_STATES entering state 0 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.584: [egismoc] CMD_STATES entering state 1 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.584: Command receive callback 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.584: [egismoc] CMD_STATES completed successfully 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.584: Task SSM next state callback 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.584: [egismoc] ENROLL_STATES entering state 10 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.584: Wait for finger on sensor 393s (process:1974): libfprint-device-DEBUG: 00:54:02.584: Device reported finger status change: FP_FINGER_STATUS_NEEDED 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.585: Finger on sensor callback 393s (process:1974): libfprint-device-DEBUG: 00:54:02.585: Device reported finger status change: FP_FINGER_STATUS_PRESENT 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.585: [egismoc] ENROLL_STATES entering state 11 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.585: Execute command and get response 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.585: Get check bytes 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.585: [egismoc] CMD_STATES entering state 0 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.586: [egismoc] CMD_STATES entering state 1 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.587: Command receive callback 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.587: [egismoc] CMD_STATES completed successfully 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.587: Read capture callback 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.587: Response prefix valid: yes 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.587: Response suffix valid: yes 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.587: Partial capture successful. Please touch the sensor again (4/10) 393s (process:1974): libfprint-device-DEBUG: 00:54:02.587: Device reported enroll progress, reported 4 of 10 have been completed 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.587: [egismoc] ENROLL_STATES entering state 8 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.587: Execute command and get response 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.587: Get check bytes 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.587: [egismoc] CMD_STATES entering state 0 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.588: [egismoc] CMD_STATES entering state 1 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.588: Command receive callback 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.588: [egismoc] CMD_STATES completed successfully 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.588: Task SSM next state callback 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.588: [egismoc] ENROLL_STATES entering state 9 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.588: Execute command and get response 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.588: Get check bytes 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.588: [egismoc] CMD_STATES entering state 0 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.589: [egismoc] CMD_STATES entering state 1 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.590: Command receive callback 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.590: [egismoc] CMD_STATES completed successfully 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.590: Task SSM next state callback 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.590: [egismoc] ENROLL_STATES entering state 10 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.590: Wait for finger on sensor 393s (process:1974): libfprint-device-DEBUG: 00:54:02.590: Device reported finger status change: FP_FINGER_STATUS_NEEDED 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.590: Finger on sensor callback 393s (process:1974): libfprint-device-DEBUG: 00:54:02.590: Device reported finger status change: FP_FINGER_STATUS_PRESENT 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.590: [egismoc] ENROLL_STATES entering state 11 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.590: Execute command and get response 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.590: Get check bytes 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.590: [egismoc] CMD_STATES entering state 0 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.591: [egismoc] CMD_STATES entering state 1 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.592: Command receive callback 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.592: [egismoc] CMD_STATES completed successfully 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.592: Read capture callback 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.592: Response prefix valid: yes 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.592: Response suffix valid: NO 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.592: Response prefix valid: yes 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.592: Response suffix valid: yes 393s (process:1974): libfprint-device-DEBUG: 00:54:02.592: Device reported enroll progress, reported 4 of 10 have been completed 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.592: [egismoc] ENROLL_STATES entering state 8 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.592: Execute command and get response 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.592: Get check bytes 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.592: [egismoc] CMD_STATES entering state 0 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.593: [egismoc] CMD_STATES entering state 1 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.594: Command receive callback 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.594: [egismoc] CMD_STATES completed successfully 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.594: Task SSM next state callback 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.594: [egismoc] ENROLL_STATES entering state 9 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.594: Execute command and get response 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.594: Get check bytes 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.594: [egismoc] CMD_STATES entering state 0 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.594: [egismoc] CMD_STATES entering state 1 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.595: Command receive callback 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.595: [egismoc] CMD_STATES completed successfully 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.595: Task SSM next state callback 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.595: [egismoc] ENROLL_STATES entering state 10 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.595: Wait for finger on sensor 393s (process:1974): libfprint-device-DEBUG: 00:54:02.595: Device reported finger status change: FP_FINGER_STATUS_NEEDED 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.596: Finger on sensor callback 393s (process:1974): libfprint-device-DEBUG: 00:54:02.596: Device reported finger status change: FP_FINGER_STATUS_PRESENT 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.596: [egismoc] ENROLL_STATES entering state 11 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.596: Execute command and get response 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.596: Get check bytes 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.596: [egismoc] CMD_STATES entering state 0 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.596: [egismoc] CMD_STATES entering state 1 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.597: Command receive callback 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.597: [egismoc] CMD_STATES completed successfully 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.597: Read capture callback 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.597: Response prefix valid: yes 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.597: Response suffix valid: yes 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.597: Partial capture successful. Please touch the sensor again (5/10) 393s (process:1974): libfprint-device-DEBUG: 00:54:02.597: Device reported enroll progress, reported 5 of 10 have been completed 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.597: [egismoc] ENROLL_STATES entering state 8 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.597: Execute command and get response 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.597: Get check bytes 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.597: [egismoc] CMD_STATES entering state 0 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.598: [egismoc] CMD_STATES entering state 1 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.599: Command receive callback 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.599: [egismoc] CMD_STATES completed successfully 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.599: Task SSM next state callback 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.599: [egismoc] ENROLL_STATES entering state 9 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.599: Execute command and get response 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.599: Get check bytes 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.599: [egismoc] CMD_STATES entering state 0 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.599: [egismoc] CMD_STATES entering state 1 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.600: Command receive callback 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.600: [egismoc] CMD_STATES completed successfully 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.600: Task SSM next state callback 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.600: [egismoc] ENROLL_STATES entering state 10 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.600: Wait for finger on sensor 393s (process:1974): libfprint-device-DEBUG: 00:54:02.600: Device reported finger status change: FP_FINGER_STATUS_NEEDED 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.601: Finger on sensor callback 393s (process:1974): libfprint-device-DEBUG: 00:54:02.601: Device reported finger status change: FP_FINGER_STATUS_PRESENT 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.601: [egismoc] ENROLL_STATES entering state 11 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.601: Execute command and get response 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.601: Get check bytes 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.601: [egismoc] CMD_STATES entering state 0 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.601: [egismoc] CMD_STATES entering state 1 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.602: Command receive callback 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.602: [egismoc] CMD_STATES completed successfully 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.602: Read capture callback 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.602: Response prefix valid: yes 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.602: Response suffix valid: yes 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.602: Partial capture successful. Please touch the sensor again (6/10) 393s (process:1974): libfprint-device-DEBUG: 00:54:02.602: Device reported enroll progress, reported 6 of 10 have been completed 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.602: [egismoc] ENROLL_STATES entering state 8 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.602: Execute command and get response 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.602: Get check bytes 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.602: [egismoc] CMD_STATES entering state 0 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.603: [egismoc] CMD_STATES entering state 1 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.604: Command receive callback 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.604: [egismoc] CMD_STATES completed successfully 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.604: Task SSM next state callback 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.604: [egismoc] ENROLL_STATES entering state 9 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.604: Execute command and get response 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.604: Get check bytes 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.604: [egismoc] CMD_STATES entering state 0 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.604: [egismoc] CMD_STATES entering state 1 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.605: Command receive callback 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.605: [egismoc] CMD_STATES completed successfully 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.605: Task SSM next state callback 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.605: [egismoc] ENROLL_STATES entering state 10 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.605: Wait for finger on sensor 393s (process:1974): libfprint-device-DEBUG: 00:54:02.605: Device reported finger status change: FP_FINGER_STATUS_NEEDED 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.606: Finger on sensor callback 393s (process:1974): libfprint-device-DEBUG: 00:54:02.606: Device reported finger status change: FP_FINGER_STATUS_PRESENT 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.606: [egismoc] ENROLL_STATES entering state 11 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.606: Execute command and get response 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.606: Get check bytes 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.606: [egismoc] CMD_STATES entering state 0 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.606: [egismoc] CMD_STATES entering state 1 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.607: Command receive callback 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.607: [egismoc] CMD_STATES completed successfully 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.607: Read capture callback 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.607: Response prefix valid: yes 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.607: Response suffix valid: NO 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.607: Response prefix valid: yes 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.607: Response suffix valid: yes 393s (process:1974): libfprint-device-DEBUG: 00:54:02.607: Device reported enroll progress, reported 6 of 10 have been completed 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.607: [egismoc] ENROLL_STATES entering state 8 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.607: Execute command and get response 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.607: Get check bytes 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.607: [egismoc] CMD_STATES entering state 0 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.608: [egismoc] CMD_STATES entering state 1 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.609: Command receive callback 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.609: [egismoc] CMD_STATES completed successfully 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.609: Task SSM next state callback 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.609: [egismoc] ENROLL_STATES entering state 9 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.609: Execute command and get response 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.609: Get check bytes 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.609: [egismoc] CMD_STATES entering state 0 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.610: [egismoc] CMD_STATES entering state 1 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.610: Command receive callback 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.610: [egismoc] CMD_STATES completed successfully 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.610: Task SSM next state callback 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.610: [egismoc] ENROLL_STATES entering state 10 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.610: Wait for finger on sensor 393s (process:1974): libfprint-device-DEBUG: 00:54:02.610: Device reported finger status change: FP_FINGER_STATUS_NEEDED 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.611: Finger on sensor callback 393s (process:1974): libfprint-device-DEBUG: 00:54:02.611: Device reported finger status change: FP_FINGER_STATUS_PRESENT 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.611: [egismoc] ENROLL_STATES entering state 11 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.611: Execute command and get response 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.611: Get check bytes 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.611: [egismoc] CMD_STATES entering state 0 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.612: [egismoc] CMD_STATES entering state 1 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.612: Command receive callback 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.613: [egismoc] CMD_STATES completed successfully 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.613: Read capture callback 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.613: Response prefix valid: yes 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.613: Response suffix valid: NO 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.613: Response prefix valid: yes 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.613: Response suffix valid: yes 393s (process:1974): libfprint-device-DEBUG: 00:54:02.613: Device reported enroll progress, reported 6 of 10 have been completed 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.613: [egismoc] ENROLL_STATES entering state 8 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.613: Execute command and get response 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.613: Get check bytes 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.613: [egismoc] CMD_STATES entering state 0 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.614: [egismoc] CMD_STATES entering state 1 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.614: Command receive callback 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.614: [egismoc] CMD_STATES completed successfully 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.614: Task SSM next state callback 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.614: [egismoc] ENROLL_STATES entering state 9 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.614: Execute command and get response 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.614: Get check bytes 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.614: [egismoc] CMD_STATES entering state 0 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.615: [egismoc] CMD_STATES entering state 1 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.616: Command receive callback 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.616: [egismoc] CMD_STATES completed successfully 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.616: Task SSM next state callback 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.616: [egismoc] ENROLL_STATES entering state 10 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.616: Wait for finger on sensor 393s (process:1974): libfprint-device-DEBUG: 00:54:02.616: Device reported finger status change: FP_FINGER_STATUS_NEEDED 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.616: Finger on sensor callback 393s (process:1974): libfprint-device-DEBUG: 00:54:02.616: Device reported finger status change: FP_FINGER_STATUS_PRESENT 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.616: [egismoc] ENROLL_STATES entering state 11 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.616: Execute command and get response 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.616: Get check bytes 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.616: [egismoc] CMD_STATES entering state 0 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.617: [egismoc] CMD_STATES entering state 1 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.618: Command receive callback 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.618: [egismoc] CMD_STATES completed successfully 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.618: Read capture callback 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.618: Response prefix valid: yes 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.618: Response suffix valid: yes 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.618: Partial capture successful. Please touch the sensor again (7/10) 393s (process:1974): libfprint-device-DEBUG: 00:54:02.618: Device reported enroll progress, reported 7 of 10 have been completed 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.618: [egismoc] ENROLL_STATES entering state 8 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.618: Execute command and get response 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.618: Get check bytes 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.618: [egismoc] CMD_STATES entering state 0 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.619: [egismoc] CMD_STATES entering state 1 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.619: Command receive callback 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.619: [egismoc] CMD_STATES completed successfully 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.619: Task SSM next state callback 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.619: [egismoc] ENROLL_STATES entering state 9 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.619: Execute command and get response 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.619: Get check bytes 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.619: [egismoc] CMD_STATES entering state 0 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.620: [egismoc] CMD_STATES entering state 1 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.621: Command receive callback 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.621: [egismoc] CMD_STATES completed successfully 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.621: Task SSM next state callback 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.621: [egismoc] ENROLL_STATES entering state 10 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.621: Wait for finger on sensor 393s (process:1974): libfprint-device-DEBUG: 00:54:02.621: Device reported finger status change: FP_FINGER_STATUS_NEEDED 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.621: Finger on sensor callback 393s (process:1974): libfprint-device-DEBUG: 00:54:02.621: Device reported finger status change: FP_FINGER_STATUS_PRESENT 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.621: [egismoc] ENROLL_STATES entering state 11 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.621: Execute command and get response 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.621: Get check bytes 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.621: [egismoc] CMD_STATES entering state 0 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.622: [egismoc] CMD_STATES entering state 1 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.623: Command receive callback 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.623: [egismoc] CMD_STATES completed successfully 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.623: Read capture callback 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.623: Response prefix valid: yes 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.623: Response suffix valid: yes 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.623: Partial capture successful. Please touch the sensor again (8/10) 393s (process:1974): libfprint-device-DEBUG: 00:54:02.623: Device reported enroll progress, reported 8 of 10 have been completed 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.623: [egismoc] ENROLL_STATES entering state 8 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.623: Execute command and get response 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.623: Get check bytes 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.623: [egismoc] CMD_STATES entering state 0 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.623: [egismoc] CMD_STATES entering state 1 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.624: Command receive callback 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.624: [egismoc] CMD_STATES completed successfully 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.624: Task SSM next state callback 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.624: [egismoc] ENROLL_STATES entering state 9 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.624: Execute command and get response 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.624: Get check bytes 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.624: [egismoc] CMD_STATES entering state 0 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.625: [egismoc] CMD_STATES entering state 1 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.625: Command receive callback 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.625: [egismoc] CMD_STATES completed successfully 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.625: Task SSM next state callback 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.625: [egismoc] ENROLL_STATES entering state 10 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.625: Wait for finger on sensor 393s (process:1974): libfprint-device-DEBUG: 00:54:02.625: Device reported finger status change: FP_FINGER_STATUS_NEEDED 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.626: Finger on sensor callback 393s (process:1974): libfprint-device-DEBUG: 00:54:02.626: Device reported finger status change: FP_FINGER_STATUS_PRESENT 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.626: [egismoc] ENROLL_STATES entering state 11 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.626: Execute command and get response 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.626: Get check bytes 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.626: [egismoc] CMD_STATES entering state 0 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.627: [egismoc] CMD_STATES entering state 1 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.628: Command receive callback 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.628: [egismoc] CMD_STATES completed successfully 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.628: Read capture callback 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.628: Response prefix valid: yes 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.628: Response suffix valid: yes 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.628: Partial capture successful. Please touch the sensor again (9/10) 393s (process:1974): libfprint-device-DEBUG: 00:54:02.628: Device reported enroll progress, reported 9 of 10 have been completed 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.628: [egismoc] ENROLL_STATES entering state 8 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.628: Execute command and get response 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.628: Get check bytes 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.628: [egismoc] CMD_STATES entering state 0 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.628: [egismoc] CMD_STATES entering state 1 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.629: Command receive callback 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.629: [egismoc] CMD_STATES completed successfully 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.629: Task SSM next state callback 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.629: [egismoc] ENROLL_STATES entering state 9 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.629: Execute command and get response 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.629: Get check bytes 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.629: [egismoc] CMD_STATES entering state 0 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.630: [egismoc] CMD_STATES entering state 1 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.631: Command receive callback 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.631: [egismoc] CMD_STATES completed successfully 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.631: Task SSM next state callback 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.631: [egismoc] ENROLL_STATES entering state 10 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.631: Wait for finger on sensor 393s (process:1974): libfprint-device-DEBUG: 00:54:02.631: Device reported finger status change: FP_FINGER_STATUS_NEEDED 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.631: Finger on sensor callback 393s (process:1974): libfprint-device-DEBUG: 00:54:02.631: Device reported finger status change: FP_FINGER_STATUS_PRESENT 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.631: [egismoc] ENROLL_STATES entering state 11 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.631: Execute command and get response 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.631: Get check bytes 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.631: [egismoc] CMD_STATES entering state 0 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.632: [egismoc] CMD_STATES entering state 1 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.633: Command receive callback 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.633: [egismoc] CMD_STATES completed successfully 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.633: Read capture callback 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.633: Response prefix valid: yes 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.633: Response suffix valid: NO 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.633: Response prefix valid: yes 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.633: Response suffix valid: yes 393s (process:1974): libfprint-device-DEBUG: 00:54:02.633: Device reported enroll progress, reported 9 of 10 have been completed 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.633: [egismoc] ENROLL_STATES entering state 8 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.633: Execute command and get response 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.633: Get check bytes 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.633: [egismoc] CMD_STATES entering state 0 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.633: [egismoc] CMD_STATES entering state 1 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.634: Command receive callback 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.634: [egismoc] CMD_STATES completed successfully 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.634: Task SSM next state callback 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.634: [egismoc] ENROLL_STATES entering state 9 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.634: Execute command and get response 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.634: Get check bytes 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.634: [egismoc] CMD_STATES entering state 0 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.635: [egismoc] CMD_STATES entering state 1 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.636: Command receive callback 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.636: [egismoc] CMD_STATES completed successfully 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.636: Task SSM next state callback 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.636: [egismoc] ENROLL_STATES entering state 10 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.636: Wait for finger on sensor 393s (process:1974): libfprint-device-DEBUG: 00:54:02.636: Device reported finger status change: FP_FINGER_STATUS_NEEDED 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.636: Finger on sensor callback 393s (process:1974): libfprint-device-DEBUG: 00:54:02.636: Device reported finger status change: FP_FINGER_STATUS_PRESENT 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.636: [egismoc] ENROLL_STATES entering state 11 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.636: Execute command and get response 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.636: Get check bytes 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.636: [egismoc] CMD_STATES entering state 0 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.638: [egismoc] CMD_STATES entering state 1 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.639: Command receive callback 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.639: [egismoc] CMD_STATES completed successfully 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.639: Read capture callback 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.639: Response prefix valid: yes 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.639: Response suffix valid: yes 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.639: Partial capture successful. Please touch the sensor again (10/10) 393s (process:1974): libfprint-device-DEBUG: 00:54:02.639: Device reported enroll progress, reported 10 of 10 have been completed 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.639: [egismoc] ENROLL_STATES entering state 12 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.639: Execute command and get response 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.639: Get check bytes 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.639: [egismoc] CMD_STATES entering state 0 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.640: [egismoc] CMD_STATES entering state 1 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.640: Command receive callback 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.641: [egismoc] CMD_STATES completed successfully 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.641: Task SSM next state callback 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.641: [egismoc] ENROLL_STATES entering state 13 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.641: New fingerprint ID: FP1-00000000-2-00000000-nobody 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.641: Execute command and get response 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.641: Get check bytes 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.641: [egismoc] CMD_STATES entering state 0 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.641: [egismoc] CMD_STATES entering state 1 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.642: Command receive callback 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.642: [egismoc] CMD_STATES completed successfully 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.642: Task SSM next state callback 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.642: [egismoc] ENROLL_STATES entering state 14 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.642: Execute command and get response 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.642: Get check bytes 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.642: [egismoc] CMD_STATES entering state 0 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.643: [egismoc] CMD_STATES entering state 1 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.643: Command receive callback 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.643: [egismoc] CMD_STATES completed successfully 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.643: Task SSM next state callback 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.643: [egismoc] ENROLL_STATES entering state 15 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.643: Enrollment was successful! 393s (process:1974): libfprint-device-DEBUG: 00:54:02.643: Device reported enroll completion 393s (process:1974): libfprint-device-DEBUG: 00:54:02.644: Device reported finger status change: FP_FINGER_STATUS_NONE 393s (process:1974): libfprint-device-DEBUG: 00:54:02.644: Print for finger FP_FINGER_LEFT_INDEX enrolled 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.644: [egismoc] ENROLL_STATES completed successfully 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.644: Task SSM done 393s (process:1974): libfprint-device-DEBUG: 00:54:02.644: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 393s (process:1974): libfprint-device-DEBUG: 00:54:02.644: Updated temperature model after 0.09 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.644: List 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.644: [egismoc] LIST_STATES entering state 0 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.644: Execute command and get response 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.644: Get check bytes 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.644: [egismoc] CMD_STATES entering state 0 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.644: [egismoc] CMD_STATES entering state 1 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.645: Command receive callback 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.645: [egismoc] CMD_STATES completed successfully 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.645: List callback 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.645: Device fingerprint 1: FP1-00000000-2-00000000-nobody 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.645: Number of currently enrolled fingerprints on the device is 1 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.645: [egismoc] LIST_STATES entering state 1 393s (process:1974): libfprint-device-DEBUG: 00:54:02.645: Device reported listing completion 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.645: [egismoc] LIST_STATES completed successfully 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.645: Task SSM done 393s (process:1974): libfprint-device-DEBUG: 00:54:02.645: Completing action FPI_DEVICE_ACTION_LIST in idle! 393s (process:1974): libfprint-device-DEBUG: 00:54:02.645: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 393s (process:1974): libfprint-device-DEBUG: 00:54:02.646: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.646: Identify or Verify 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.646: [egismoc] IDENTIFY_STATES entering state 0 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.646: Execute command and get response 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.646: Get check bytes 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.646: [egismoc] CMD_STATES entering state 0 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.647: [egismoc] CMD_STATES entering state 1 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.647: Command receive callback 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.647: [egismoc] CMD_STATES completed successfully 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.647: List callback 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.647: Device fingerprint 1: FP1-00000000-2-00000000-nobody 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.647: Number of currently enrolled fingerprints on the device is 1 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.647: [egismoc] IDENTIFY_STATES entering state 1 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.647: [egismoc] IDENTIFY_STATES entering state 2 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.647: Execute command and get response 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.647: Get check bytes 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.647: [egismoc] CMD_STATES entering state 0 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.648: [egismoc] CMD_STATES entering state 1 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.649: Command receive callback 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.649: [egismoc] CMD_STATES completed successfully 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.649: Task SSM next state callback 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.649: [egismoc] IDENTIFY_STATES entering state 3 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.649: Execute command and get response 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.649: Get check bytes 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.649: [egismoc] CMD_STATES entering state 0 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.649: [egismoc] CMD_STATES entering state 1 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.650: Command receive callback 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.650: [egismoc] CMD_STATES completed successfully 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.650: Task SSM next state callback 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.650: [egismoc] IDENTIFY_STATES entering state 4 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.650: Wait for finger on sensor 393s (process:1974): libfprint-device-DEBUG: 00:54:02.650: Device reported finger status change: FP_FINGER_STATUS_NEEDED 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.651: Finger on sensor callback 393s (process:1974): libfprint-device-DEBUG: 00:54:02.651: Device reported finger status change: FP_FINGER_STATUS_PRESENT 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.651: [egismoc] IDENTIFY_STATES entering state 5 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.651: Execute command and get response 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.651: Get check bytes 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.651: [egismoc] CMD_STATES entering state 0 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.652: [egismoc] CMD_STATES entering state 1 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.652: Command receive callback 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.652: [egismoc] CMD_STATES completed successfully 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.652: Task SSM next state callback 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.652: [egismoc] IDENTIFY_STATES entering state 6 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.652: Get check command 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.652: Execute command and get response 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.652: Get check bytes 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.652: [egismoc] CMD_STATES entering state 0 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.653: [egismoc] CMD_STATES entering state 1 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.654: Command receive callback 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.654: [egismoc] CMD_STATES completed successfully 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.654: Identify check callback 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.654: Response suffix valid: yes 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.654: Identify successful for: FP1-00000000-2-00000000-nobody 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.654: Verifying against: FP1-00000000-2-00000000-nobody 393s (process:1974): libfprint-device-DEBUG: 00:54:02.654: Device reported verify result 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.654: [egismoc] IDENTIFY_STATES entering state 7 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.654: Execute command and get response 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.654: Get check bytes 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.654: [egismoc] CMD_STATES entering state 0 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.654: [egismoc] CMD_STATES entering state 1 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.655: Command receive callback 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.655: [egismoc] CMD_STATES completed successfully 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.655: Task SSM next state callback 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.655: [egismoc] IDENTIFY_STATES entering state 8 393s (process:1974): libfprint-device-DEBUG: 00:54:02.655: Device reported verify completion 393s (process:1974): libfprint-device-DEBUG: 00:54:02.655: Device reported finger status change: FP_FINGER_STATUS_NONE 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.655: [egismoc] IDENTIFY_STATES completed successfully 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.655: Task SSM done 393s (process:1974): libfprint-device-DEBUG: 00:54:02.655: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 393s (process:1974): libfprint-device-DEBUG: 00:54:02.655: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 393s (process:1974): libfprint-device-DEBUG: 00:54:02.656: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.657: Identify or Verify 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.657: [egismoc] IDENTIFY_STATES entering state 0 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.657: Execute command and get response 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.657: Get check bytes 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.657: [egismoc] CMD_STATES entering state 0 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.657: [egismoc] CMD_STATES entering state 1 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.658: Command receive callback 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.658: [egismoc] CMD_STATES completed successfully 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.658: List callback 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.658: Device fingerprint 1: FP1-00000000-2-00000000-nobody 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.658: Number of currently enrolled fingerprints on the device is 1 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.658: [egismoc] IDENTIFY_STATES entering state 1 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.658: [egismoc] IDENTIFY_STATES entering state 2 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.658: Execute command and get response 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.658: Get check bytes 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.658: [egismoc] CMD_STATES entering state 0 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.659: [egismoc] CMD_STATES entering state 1 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.660: Command receive callback 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.660: [egismoc] CMD_STATES completed successfully 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.660: Task SSM next state callback 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.660: [egismoc] IDENTIFY_STATES entering state 3 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.660: Execute command and get response 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.660: Get check bytes 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.660: [egismoc] CMD_STATES entering state 0 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.661: [egismoc] CMD_STATES entering state 1 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.661: Command receive callback 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.661: [egismoc] CMD_STATES completed successfully 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.661: Task SSM next state callback 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.661: [egismoc] IDENTIFY_STATES entering state 4 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.661: Wait for finger on sensor 393s (process:1974): libfprint-device-DEBUG: 00:54:02.661: Device reported finger status change: FP_FINGER_STATUS_NEEDED 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.662: Finger on sensor callback 393s (process:1974): libfprint-device-DEBUG: 00:54:02.662: Device reported finger status change: FP_FINGER_STATUS_PRESENT 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.662: [egismoc] IDENTIFY_STATES entering state 5 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.662: Execute command and get response 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.662: Get check bytes 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.662: [egismoc] CMD_STATES entering state 0 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.663: [egismoc] CMD_STATES entering state 1 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.664: Command receive callback 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.664: [egismoc] CMD_STATES completed successfully 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.664: Task SSM next state callback 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.664: [egismoc] IDENTIFY_STATES entering state 6 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.664: Get check command 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.664: Execute command and get response 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.664: Get check bytes 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.664: [egismoc] CMD_STATES entering state 0 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.664: [egismoc] CMD_STATES entering state 1 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.665: Command receive callback 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.665: [egismoc] CMD_STATES completed successfully 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.665: Identify check callback 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.665: Response suffix valid: yes 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.665: Identify successful for: FP1-00000000-2-00000000-nobody 393s (process:1974): libfprint-device-DEBUG: 00:54:02.665: Device reported identify result 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.665: [egismoc] IDENTIFY_STATES entering state 7 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.665: Execute command and get response 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.665: Get check bytes 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.665: [egismoc] CMD_STATES entering state 0 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.666: [egismoc] CMD_STATES entering state 1 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.667: Command receive callback 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.667: [egismoc] CMD_STATES completed successfully 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.667: Task SSM next state callback 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.667: [egismoc] IDENTIFY_STATES entering state 8 393s (process:1974): libfprint-device-DEBUG: 00:54:02.667: Device reported identify completion 393s (process:1974): libfprint-device-DEBUG: 00:54:02.667: Device reported finger status change: FP_FINGER_STATUS_NONE 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.667: [egismoc] IDENTIFY_STATES completed successfully 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.667: Task SSM done 393s (process:1974): libfprint-device-DEBUG: 00:54:02.667: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 393s (process:1974): libfprint-device-DEBUG: 00:54:02.667: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 393s (process:1974): libfprint-device-DEBUG: 00:54:02.669: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.669: Enroll 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.669: [egismoc] ENROLL_STATES entering state 0 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.669: Execute command and get response 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.669: Get check bytes 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.669: [egismoc] CMD_STATES entering state 0 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.669: [egismoc] CMD_STATES entering state 1 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.670: Command receive callback 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.670: [egismoc] CMD_STATES completed successfully 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.670: List callback 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.670: Device fingerprint 1: FP1-00000000-2-00000000-nobody 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.670: Number of currently enrolled fingerprints on the device is 1 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.670: [egismoc] ENROLL_STATES entering state 1 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.670: [egismoc] ENROLL_STATES entering state 2 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.670: Execute command and get response 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.670: Get check bytes 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.670: [egismoc] CMD_STATES entering state 0 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.671: [egismoc] CMD_STATES entering state 1 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.672: Command receive callback 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.672: [egismoc] CMD_STATES completed successfully 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.672: Task SSM next state callback 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.672: [egismoc] ENROLL_STATES entering state 3 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.672: Execute command and get response 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.672: Get check bytes 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.672: [egismoc] CMD_STATES entering state 0 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.672: [egismoc] CMD_STATES entering state 1 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.673: Command receive callback 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.673: [egismoc] CMD_STATES completed successfully 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.673: Task SSM next state callback 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.673: [egismoc] ENROLL_STATES entering state 4 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.673: Wait for finger on sensor 393s (process:1974): libfprint-device-DEBUG: 00:54:02.673: Device reported finger status change: FP_FINGER_STATUS_NEEDED 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.674: Finger on sensor callback 393s (process:1974): libfprint-device-DEBUG: 00:54:02.674: Device reported finger status change: FP_FINGER_STATUS_PRESENT 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.674: [egismoc] ENROLL_STATES entering state 5 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.674: Execute command and get response 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.674: Get check bytes 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.674: [egismoc] CMD_STATES entering state 0 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.674: [egismoc] CMD_STATES entering state 1 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.675: Command receive callback 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.675: [egismoc] CMD_STATES completed successfully 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.675: Task SSM next state callback 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.675: [egismoc] ENROLL_STATES entering state 6 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.675: Get check command 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.675: Execute command and get response 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.675: Get check bytes 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.675: [egismoc] CMD_STATES entering state 0 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.676: [egismoc] CMD_STATES entering state 1 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.676: Command receive callback 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.676: [egismoc] CMD_STATES completed successfully 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.676: Enroll check callback 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.676: Response suffix valid: NO 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.677: [egismoc] SSM ENROLL_STATES failed in state 6 with error: This finger has already enrolled, please try a different finger 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.677: [egismoc] ENROLL_STATES completed with error: This finger has already enrolled, please try a different finger 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.677: Task SSM done 393s (process:1974): libfprint-device-DEBUG: 00:54:02.677: Device reported generic error (This finger has already enrolled, please try a different finger) during action; action was: FPI_DEVICE_ACTION_ENROLL 393s (process:1974): libfprint-device-DEBUG: 00:54:02.677: Device reported enroll completion 393s (process:1974): libfprint-device-DEBUG: 00:54:02.677: Device reported finger status change: FP_FINGER_STATUS_NONE 393s (process:1974): libfprint-device-DEBUG: 00:54:02.677: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 393s (process:1974): libfprint-device-DEBUG: 00:54:02.677: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.678: List 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.678: [egismoc] LIST_STATES entering state 0 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.678: Execute command and get response 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.678: Get check bytes 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.678: [egismoc] CMD_STATES entering state 0 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.678: [egismoc] CMD_STATES entering state 1 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.679: Command receive callback 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.679: [egismoc] CMD_STATES completed successfully 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.679: List callback 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.679: Device fingerprint 1: FP1-00000000-2-00000000-nobody 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.679: Number of currently enrolled fingerprints on the device is 1 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.679: [egismoc] LIST_STATES entering state 1 393s (process:1974): libfprint-device-DEBUG: 00:54:02.679: Device reported listing completion 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.679: [egismoc] LIST_STATES completed successfully 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.679: Task SSM done 393s (process:1974): libfprint-device-DEBUG: 00:54:02.679: Completing action FPI_DEVICE_ACTION_LIST in idle! 393s (process:1974): libfprint-device-DEBUG: 00:54:02.679: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 393s (process:1974): libfprint-device-DEBUG: 00:54:02.680: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.680: Enroll 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.680: [egismoc] ENROLL_STATES entering state 0 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.680: Execute command and get response 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.680: Get check bytes 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.680: [egismoc] CMD_STATES entering state 0 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.681: [egismoc] CMD_STATES entering state 1 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.682: Command receive callback 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.682: [egismoc] CMD_STATES completed successfully 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.682: List callback 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.682: Device fingerprint 1: FP1-00000000-2-00000000-nobody 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.682: Number of currently enrolled fingerprints on the device is 1 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.682: [egismoc] ENROLL_STATES entering state 1 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.682: [egismoc] ENROLL_STATES entering state 2 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.682: Execute command and get response 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.682: Get check bytes 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.682: [egismoc] CMD_STATES entering state 0 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.682: [egismoc] CMD_STATES entering state 1 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.683: Command receive callback 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.683: [egismoc] CMD_STATES completed successfully 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.683: Task SSM next state callback 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.683: [egismoc] ENROLL_STATES entering state 3 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.683: Execute command and get response 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.683: Get check bytes 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.683: [egismoc] CMD_STATES entering state 0 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.683: [egismoc] CMD_STATES entering state 1 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.684: Command receive callback 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.684: [egismoc] CMD_STATES completed successfully 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.684: Task SSM next state callback 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.684: [egismoc] ENROLL_STATES entering state 4 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.684: Wait for finger on sensor 393s (process:1974): libfprint-device-DEBUG: 00:54:02.684: Device reported finger status change: FP_FINGER_STATUS_NEEDED 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.685: Finger on sensor callback 393s (process:1974): libfprint-device-DEBUG: 00:54:02.685: Device reported finger status change: FP_FINGER_STATUS_PRESENT 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.685: [egismoc] ENROLL_STATES entering state 5 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.685: Execute command and get response 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.685: Get check bytes 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.685: [egismoc] CMD_STATES entering state 0 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.685: [egismoc] CMD_STATES entering state 1 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.686: Command receive callback 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.686: [egismoc] CMD_STATES completed successfully 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.686: Task SSM next state callback 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.686: [egismoc] ENROLL_STATES entering state 6 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.686: Get check command 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.686: Execute command and get response 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.686: Get check bytes 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.686: [egismoc] CMD_STATES entering state 0 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.687: [egismoc] CMD_STATES entering state 1 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.688: Command receive callback 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.688: [egismoc] CMD_STATES completed successfully 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.688: Enroll check callback 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.688: Response suffix valid: yes 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.688: [egismoc] ENROLL_STATES entering state 7 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.688: Execute command and get response 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.688: Get check bytes 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.688: [egismoc] CMD_STATES entering state 0 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.690: [egismoc] CMD_STATES entering state 1 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.691: Command receive callback 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.691: [egismoc] CMD_STATES completed successfully 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.691: Task SSM next state callback 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.691: [egismoc] ENROLL_STATES entering state 8 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.691: Execute command and get response 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.691: Get check bytes 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.691: [egismoc] CMD_STATES entering state 0 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.693: [egismoc] CMD_STATES entering state 1 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.694: Command receive callback 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.694: [egismoc] CMD_STATES completed successfully 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.694: Task SSM next state callback 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.694: [egismoc] ENROLL_STATES entering state 9 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.694: Execute command and get response 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.694: Get check bytes 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.694: [egismoc] CMD_STATES entering state 0 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.694: [egismoc] CMD_STATES entering state 1 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.695: Command receive callback 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.695: [egismoc] CMD_STATES completed successfully 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.695: Task SSM next state callback 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.695: [egismoc] ENROLL_STATES entering state 10 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.695: Wait for finger on sensor 393s (process:1974): libfprint-device-DEBUG: 00:54:02.695: Device reported finger status change: FP_FINGER_STATUS_NEEDED 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.696: Finger on sensor callback 393s (process:1974): libfprint-device-DEBUG: 00:54:02.696: Device reported finger status change: FP_FINGER_STATUS_PRESENT 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.696: [egismoc] ENROLL_STATES entering state 11 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.696: Execute command and get response 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.696: Get check bytes 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.696: [egismoc] CMD_STATES entering state 0 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.700: [egismoc] CMD_STATES entering state 1 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.701: Command receive callback 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.701: [egismoc] CMD_STATES completed successfully 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.701: Read capture callback 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.701: Response prefix valid: yes 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.701: Response suffix valid: yes 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.701: Partial capture successful. Please touch the sensor again (1/10) 393s (process:1974): libfprint-device-DEBUG: 00:54:02.701: Device reported enroll progress, reported 1 of 10 have been completed 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.701: [egismoc] ENROLL_STATES entering state 8 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.701: Execute command and get response 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.701: Get check bytes 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.701: [egismoc] CMD_STATES entering state 0 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.702: [egismoc] CMD_STATES entering state 1 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.703: Command receive callback 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.703: [egismoc] CMD_STATES completed successfully 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.703: Task SSM next state callback 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.703: [egismoc] ENROLL_STATES entering state 9 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.703: Execute command and get response 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.703: Get check bytes 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.703: [egismoc] CMD_STATES entering state 0 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.703: [egismoc] CMD_STATES entering state 1 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.705: Command receive callback 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.705: [egismoc] CMD_STATES completed successfully 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.705: Task SSM next state callback 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.705: [egismoc] ENROLL_STATES entering state 10 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.705: Wait for finger on sensor 393s (process:1974): libfprint-device-DEBUG: 00:54:02.705: Device reported finger status change: FP_FINGER_STATUS_NEEDED 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.708: Finger on sensor callback 393s (process:1974): libfprint-device-DEBUG: 00:54:02.709: Device reported finger status change: FP_FINGER_STATUS_PRESENT 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.709: [egismoc] ENROLL_STATES entering state 11 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.709: Execute command and get response 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.709: Get check bytes 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.709: [egismoc] CMD_STATES entering state 0 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.709: [egismoc] CMD_STATES entering state 1 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.710: Command receive callback 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.710: [egismoc] CMD_STATES completed successfully 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.710: Read capture callback 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.710: Response prefix valid: yes 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.710: Response suffix valid: NO 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.710: Response prefix valid: yes 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.710: Response suffix valid: yes 393s (process:1974): libfprint-device-DEBUG: 00:54:02.710: Device reported enroll progress, reported 1 of 10 have been completed 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.711: [egismoc] ENROLL_STATES entering state 8 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.711: Execute command and get response 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.711: Get check bytes 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.711: [egismoc] CMD_STATES entering state 0 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.711: [egismoc] CMD_STATES entering state 1 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.714: Command receive callback 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.714: [egismoc] CMD_STATES completed successfully 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.714: Task SSM next state callback 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.714: [egismoc] ENROLL_STATES entering state 9 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.714: Execute command and get response 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.714: Get check bytes 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.714: [egismoc] CMD_STATES entering state 0 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.715: [egismoc] CMD_STATES entering state 1 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.716: Command receive callback 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.716: [egismoc] CMD_STATES completed successfully 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.716: Task SSM next state callback 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.716: [egismoc] ENROLL_STATES entering state 10 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.716: Wait for finger on sensor 393s (process:1974): libfprint-device-DEBUG: 00:54:02.716: Device reported finger status change: FP_FINGER_STATUS_NEEDED 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.717: Finger on sensor callback 393s (process:1974): libfprint-device-DEBUG: 00:54:02.717: Device reported finger status change: FP_FINGER_STATUS_PRESENT 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.717: [egismoc] ENROLL_STATES entering state 11 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.717: Execute command and get response 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.717: Get check bytes 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.717: [egismoc] CMD_STATES entering state 0 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.718: [egismoc] CMD_STATES entering state 1 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.720: Command receive callback 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.721: [egismoc] CMD_STATES completed successfully 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.721: Read capture callback 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.721: Response prefix valid: yes 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.721: Response suffix valid: yes 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.721: Partial capture successful. Please touch the sensor again (2/10) 393s (process:1974): libfprint-device-DEBUG: 00:54:02.721: Device reported enroll progress, reported 2 of 10 have been completed 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.721: [egismoc] ENROLL_STATES entering state 8 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.721: Execute command and get response 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.721: Get check bytes 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.721: [egismoc] CMD_STATES entering state 0 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.722: [egismoc] CMD_STATES entering state 1 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.722: Command receive callback 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.722: [egismoc] CMD_STATES completed successfully 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.722: Task SSM next state callback 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.722: [egismoc] ENROLL_STATES entering state 9 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.722: Execute command and get response 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.722: Get check bytes 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.722: [egismoc] CMD_STATES entering state 0 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.723: [egismoc] CMD_STATES entering state 1 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.724: Command receive callback 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.724: [egismoc] CMD_STATES completed successfully 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.724: Task SSM next state callback 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.724: [egismoc] ENROLL_STATES entering state 10 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.724: Wait for finger on sensor 393s (process:1974): libfprint-device-DEBUG: 00:54:02.724: Device reported finger status change: FP_FINGER_STATUS_NEEDED 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.724: Finger on sensor callback 393s (process:1974): libfprint-device-DEBUG: 00:54:02.725: Device reported finger status change: FP_FINGER_STATUS_PRESENT 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.725: [egismoc] ENROLL_STATES entering state 11 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.725: Execute command and get response 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.725: Get check bytes 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.725: [egismoc] CMD_STATES entering state 0 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.725: [egismoc] CMD_STATES entering state 1 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.726: Command receive callback 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.726: [egismoc] CMD_STATES completed successfully 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.726: Read capture callback 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.726: Response prefix valid: yes 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.726: Response suffix valid: yes 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.726: Partial capture successful. Please touch the sensor again (3/10) 393s (process:1974): libfprint-device-DEBUG: 00:54:02.726: Device reported enroll progress, reported 3 of 10 have been completed 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.726: [egismoc] ENROLL_STATES entering state 8 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.726: Execute command and get response 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.726: Get check bytes 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.726: [egismoc] CMD_STATES entering state 0 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.727: [egismoc] CMD_STATES entering state 1 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.727: Command receive callback 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.727: [egismoc] CMD_STATES completed successfully 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.727: Task SSM next state callback 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.727: [egismoc] ENROLL_STATES entering state 9 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.727: Execute command and get response 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.727: Get check bytes 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.727: [egismoc] CMD_STATES entering state 0 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.728: [egismoc] CMD_STATES entering state 1 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.728: Command receive callback 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.728: [egismoc] CMD_STATES completed successfully 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.728: Task SSM next state callback 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.728: [egismoc] ENROLL_STATES entering state 10 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.728: Wait for finger on sensor 393s (process:1974): libfprint-device-DEBUG: 00:54:02.728: Device reported finger status change: FP_FINGER_STATUS_NEEDED 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.729: Finger on sensor callback 393s (process:1974): libfprint-device-DEBUG: 00:54:02.729: Device reported finger status change: FP_FINGER_STATUS_PRESENT 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.729: [egismoc] ENROLL_STATES entering state 11 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.729: Execute command and get response 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.729: Get check bytes 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.729: [egismoc] CMD_STATES entering state 0 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.730: [egismoc] CMD_STATES entering state 1 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.730: Command receive callback 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.730: [egismoc] CMD_STATES completed successfully 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.730: Read capture callback 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.730: Response prefix valid: yes 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.730: Response suffix valid: NO 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.730: Response prefix valid: yes 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.730: Response suffix valid: yes 393s (process:1974): libfprint-device-DEBUG: 00:54:02.730: Device reported enroll progress, reported 3 of 10 have been completed 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.730: [egismoc] ENROLL_STATES entering state 8 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.730: Execute command and get response 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.730: Get check bytes 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.731: [egismoc] CMD_STATES entering state 0 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.731: [egismoc] CMD_STATES entering state 1 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.732: Command receive callback 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.732: [egismoc] CMD_STATES completed successfully 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.732: Task SSM next state callback 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.732: [egismoc] ENROLL_STATES entering state 9 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.732: Execute command and get response 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.732: Get check bytes 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.732: [egismoc] CMD_STATES entering state 0 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.732: [egismoc] CMD_STATES entering state 1 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.733: Command receive callback 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.733: [egismoc] CMD_STATES completed successfully 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.733: Task SSM next state callback 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.733: [egismoc] ENROLL_STATES entering state 10 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.733: Wait for finger on sensor 393s (process:1974): libfprint-device-DEBUG: 00:54:02.733: Device reported finger status change: FP_FINGER_STATUS_NEEDED 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.733: Finger on sensor callback 393s (process:1974): libfprint-device-DEBUG: 00:54:02.733: Device reported finger status change: FP_FINGER_STATUS_PRESENT 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.733: [egismoc] ENROLL_STATES entering state 11 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.733: Execute command and get response 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.733: Get check bytes 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.733: [egismoc] CMD_STATES entering state 0 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.734: [egismoc] CMD_STATES entering state 1 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.734: Command receive callback 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.734: [egismoc] CMD_STATES completed successfully 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.734: Read capture callback 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.734: Response prefix valid: yes 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.734: Response suffix valid: NO 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.734: Response prefix valid: yes 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.734: Response suffix valid: yes 393s (process:1974): libfprint-device-DEBUG: 00:54:02.734: Device reported enroll progress, reported 3 of 10 have been completed 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.735: [egismoc] ENROLL_STATES entering state 8 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.735: Execute command and get response 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.735: Get check bytes 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.735: [egismoc] CMD_STATES entering state 0 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.735: [egismoc] CMD_STATES entering state 1 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.736: Command receive callback 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.736: [egismoc] CMD_STATES completed successfully 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.736: Task SSM next state callback 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.736: [egismoc] ENROLL_STATES entering state 9 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.736: Execute command and get response 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.736: Get check bytes 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.736: [egismoc] CMD_STATES entering state 0 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.736: [egismoc] CMD_STATES entering state 1 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.737: Command receive callback 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.737: [egismoc] CMD_STATES completed successfully 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.737: Task SSM next state callback 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.737: [egismoc] ENROLL_STATES entering state 10 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.737: Wait for finger on sensor 393s (process:1974): libfprint-device-DEBUG: 00:54:02.737: Device reported finger status change: FP_FINGER_STATUS_NEEDED 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.737: Finger on sensor callback 393s (process:1974): libfprint-device-DEBUG: 00:54:02.737: Device reported finger status change: FP_FINGER_STATUS_PRESENT 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.737: [egismoc] ENROLL_STATES entering state 11 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.737: Execute command and get response 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.737: Get check bytes 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.737: [egismoc] CMD_STATES entering state 0 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.738: [egismoc] CMD_STATES entering state 1 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.739: Command receive callback 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.739: [egismoc] CMD_STATES completed successfully 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.739: Read capture callback 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.739: Response prefix valid: yes 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.739: Response suffix valid: yes 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.739: Partial capture successful. Please touch the sensor again (4/10) 393s (process:1974): libfprint-device-DEBUG: 00:54:02.739: Device reported enroll progress, reported 4 of 10 have been completed 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.739: [egismoc] ENROLL_STATES entering state 8 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.739: Execute command and get response 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.739: Get check bytes 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.739: [egismoc] CMD_STATES entering state 0 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.739: [egismoc] CMD_STATES entering state 1 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.740: Command receive callback 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.740: [egismoc] CMD_STATES completed successfully 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.740: Task SSM next state callback 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.740: [egismoc] ENROLL_STATES entering state 9 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.740: Execute command and get response 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.740: Get check bytes 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.740: [egismoc] CMD_STATES entering state 0 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.740: [egismoc] CMD_STATES entering state 1 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.741: Command receive callback 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.741: [egismoc] CMD_STATES completed successfully 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.741: Task SSM next state callback 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.741: [egismoc] ENROLL_STATES entering state 10 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.741: Wait for finger on sensor 393s (process:1974): libfprint-device-DEBUG: 00:54:02.741: Device reported finger status change: FP_FINGER_STATUS_NEEDED 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.742: Finger on sensor callback 393s (process:1974): libfprint-device-DEBUG: 00:54:02.742: Device reported finger status change: FP_FINGER_STATUS_PRESENT 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.742: [egismoc] ENROLL_STATES entering state 11 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.742: Execute command and get response 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.742: Get check bytes 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.742: [egismoc] CMD_STATES entering state 0 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.742: [egismoc] CMD_STATES entering state 1 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.743: Command receive callback 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.743: [egismoc] CMD_STATES completed successfully 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.743: Read capture callback 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.743: Response prefix valid: yes 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.743: Response suffix valid: yes 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.743: Partial capture successful. Please touch the sensor again (5/10) 393s (process:1974): libfprint-device-DEBUG: 00:54:02.743: Device reported enroll progress, reported 5 of 10 have been completed 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.743: [egismoc] ENROLL_STATES entering state 8 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.743: Execute command and get response 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.743: Get check bytes 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.743: [egismoc] CMD_STATES entering state 0 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.743: [egismoc] CMD_STATES entering state 1 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.744: Command receive callback 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.744: [egismoc] CMD_STATES completed successfully 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.744: Task SSM next state callback 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.744: [egismoc] ENROLL_STATES entering state 9 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.744: Execute command and get response 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.744: Get check bytes 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.744: [egismoc] CMD_STATES entering state 0 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.744: [egismoc] CMD_STATES entering state 1 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.745: Command receive callback 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.745: [egismoc] CMD_STATES completed successfully 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.745: Task SSM next state callback 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.745: [egismoc] ENROLL_STATES entering state 10 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.745: Wait for finger on sensor 393s (process:1974): libfprint-device-DEBUG: 00:54:02.745: Device reported finger status change: FP_FINGER_STATUS_NEEDED 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.745: Finger on sensor callback 393s (process:1974): libfprint-device-DEBUG: 00:54:02.745: Device reported finger status change: FP_FINGER_STATUS_PRESENT 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.745: [egismoc] ENROLL_STATES entering state 11 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.745: Execute command and get response 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.745: Get check bytes 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.745: [egismoc] CMD_STATES entering state 0 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.746: [egismoc] CMD_STATES entering state 1 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.748: Command receive callback 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.748: [egismoc] CMD_STATES completed successfully 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.748: Read capture callback 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.748: Response prefix valid: yes 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.748: Response suffix valid: yes 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.748: Partial capture successful. Please touch the sensor again (6/10) 393s (process:1974): libfprint-device-DEBUG: 00:54:02.748: Device reported enroll progress, reported 6 of 10 have been completed 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.748: [egismoc] ENROLL_STATES entering state 8 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.748: Execute command and get response 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.748: Get check bytes 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.748: [egismoc] CMD_STATES entering state 0 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.750: [egismoc] CMD_STATES entering state 1 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.751: Command receive callback 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.751: [egismoc] CMD_STATES completed successfully 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.751: Task SSM next state callback 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.751: [egismoc] ENROLL_STATES entering state 9 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.751: Execute command and get response 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.751: Get check bytes 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.751: [egismoc] CMD_STATES entering state 0 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.752: [egismoc] CMD_STATES entering state 1 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.753: Command receive callback 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.753: [egismoc] CMD_STATES completed successfully 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.753: Task SSM next state callback 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.753: [egismoc] ENROLL_STATES entering state 10 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.753: Wait for finger on sensor 393s (process:1974): libfprint-device-DEBUG: 00:54:02.753: Device reported finger status change: FP_FINGER_STATUS_NEEDED 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.754: Finger on sensor callback 393s (process:1974): libfprint-device-DEBUG: 00:54:02.754: Device reported finger status change: FP_FINGER_STATUS_PRESENT 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.754: [egismoc] ENROLL_STATES entering state 11 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.754: Execute command and get response 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.754: Get check bytes 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.754: [egismoc] CMD_STATES entering state 0 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.755: [egismoc] CMD_STATES entering state 1 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.755: Command receive callback 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.755: [egismoc] CMD_STATES completed successfully 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.755: Read capture callback 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.755: Response prefix valid: yes 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.755: Response suffix valid: yes 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.755: Partial capture successful. Please touch the sensor again (7/10) 393s (process:1974): libfprint-device-DEBUG: 00:54:02.755: Device reported enroll progress, reported 7 of 10 have been completed 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.756: [egismoc] ENROLL_STATES entering state 8 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.756: Execute command and get response 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.756: Get check bytes 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.756: [egismoc] CMD_STATES entering state 0 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.756: [egismoc] CMD_STATES entering state 1 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.757: Command receive callback 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.757: [egismoc] CMD_STATES completed successfully 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.757: Task SSM next state callback 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.757: [egismoc] ENROLL_STATES entering state 9 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.757: Execute command and get response 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.757: Get check bytes 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.757: [egismoc] CMD_STATES entering state 0 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.758: [egismoc] CMD_STATES entering state 1 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.759: Command receive callback 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.759: [egismoc] CMD_STATES completed successfully 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.759: Task SSM next state callback 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.759: [egismoc] ENROLL_STATES entering state 10 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.759: Wait for finger on sensor 393s (process:1974): libfprint-device-DEBUG: 00:54:02.759: Device reported finger status change: FP_FINGER_STATUS_NEEDED 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.760: Finger on sensor callback 393s (process:1974): libfprint-device-DEBUG: 00:54:02.760: Device reported finger status change: FP_FINGER_STATUS_PRESENT 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.760: [egismoc] ENROLL_STATES entering state 11 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.760: Execute command and get response 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.760: Get check bytes 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.760: [egismoc] CMD_STATES entering state 0 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.761: [egismoc] CMD_STATES entering state 1 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.762: Command receive callback 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.762: [egismoc] CMD_STATES completed successfully 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.762: Read capture callback 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.762: Response prefix valid: yes 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.762: Response suffix valid: yes 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.762: Partial capture successful. Please touch the sensor again (8/10) 393s (process:1974): libfprint-device-DEBUG: 00:54:02.762: Device reported enroll progress, reported 8 of 10 have been completed 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.762: [egismoc] ENROLL_STATES entering state 8 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.762: Execute command and get response 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.762: Get check bytes 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.762: [egismoc] CMD_STATES entering state 0 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.763: [egismoc] CMD_STATES entering state 1 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.763: Command receive callback 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.763: [egismoc] CMD_STATES completed successfully 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.763: Task SSM next state callback 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.763: [egismoc] ENROLL_STATES entering state 9 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.763: Execute command and get response 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.764: Get check bytes 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.764: [egismoc] CMD_STATES entering state 0 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.764: [egismoc] CMD_STATES entering state 1 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.765: Command receive callback 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.765: [egismoc] CMD_STATES completed successfully 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.765: Task SSM next state callback 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.765: [egismoc] ENROLL_STATES entering state 10 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.765: Wait for finger on sensor 393s (process:1974): libfprint-device-DEBUG: 00:54:02.765: Device reported finger status change: FP_FINGER_STATUS_NEEDED 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.766: Finger on sensor callback 393s (process:1974): libfprint-device-DEBUG: 00:54:02.766: Device reported finger status change: FP_FINGER_STATUS_PRESENT 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.766: [egismoc] ENROLL_STATES entering state 11 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.766: Execute command and get response 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.766: Get check bytes 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.766: [egismoc] CMD_STATES entering state 0 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.766: [egismoc] CMD_STATES entering state 1 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.767: Command receive callback 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.767: [egismoc] CMD_STATES completed successfully 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.767: Read capture callback 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.767: Response prefix valid: yes 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.767: Response suffix valid: yes 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.767: Partial capture successful. Please touch the sensor again (9/10) 393s (process:1974): libfprint-device-DEBUG: 00:54:02.767: Device reported enroll progress, reported 9 of 10 have been completed 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.767: [egismoc] ENROLL_STATES entering state 8 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.767: Execute command and get response 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.767: Get check bytes 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.767: [egismoc] CMD_STATES entering state 0 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.768: [egismoc] CMD_STATES entering state 1 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.769: Command receive callback 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.769: [egismoc] CMD_STATES completed successfully 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.769: Task SSM next state callback 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.769: [egismoc] ENROLL_STATES entering state 9 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.769: Execute command and get response 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.769: Get check bytes 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.769: [egismoc] CMD_STATES entering state 0 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.769: [egismoc] CMD_STATES entering state 1 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.770: Command receive callback 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.770: [egismoc] CMD_STATES completed successfully 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.770: Task SSM next state callback 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.770: [egismoc] ENROLL_STATES entering state 10 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.770: Wait for finger on sensor 393s (process:1974): libfprint-device-DEBUG: 00:54:02.770: Device reported finger status change: FP_FINGER_STATUS_NEEDED 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.771: Finger on sensor callback 393s (process:1974): libfprint-device-DEBUG: 00:54:02.771: Device reported finger status change: FP_FINGER_STATUS_PRESENT 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.771: [egismoc] ENROLL_STATES entering state 11 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.771: Execute command and get response 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.771: Get check bytes 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.771: [egismoc] CMD_STATES entering state 0 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.772: [egismoc] CMD_STATES entering state 1 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.772: Command receive callback 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.772: [egismoc] CMD_STATES completed successfully 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.772: Read capture callback 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.772: Response prefix valid: yes 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.772: Response suffix valid: NO 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.772: Response prefix valid: yes 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.772: Response suffix valid: yes 393s (process:1974): libfprint-device-DEBUG: 00:54:02.772: Device reported enroll progress, reported 9 of 10 have been completed 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.773: [egismoc] ENROLL_STATES entering state 8 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.773: Execute command and get response 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.773: Get check bytes 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.773: [egismoc] CMD_STATES entering state 0 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.773: [egismoc] CMD_STATES entering state 1 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.774: Command receive callback 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.774: [egismoc] CMD_STATES completed successfully 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.774: Task SSM next state callback 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.774: [egismoc] ENROLL_STATES entering state 9 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.774: Execute command and get response 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.774: Get check bytes 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.774: [egismoc] CMD_STATES entering state 0 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.775: [egismoc] CMD_STATES entering state 1 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.776: Command receive callback 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.776: [egismoc] CMD_STATES completed successfully 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.776: Task SSM next state callback 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.776: [egismoc] ENROLL_STATES entering state 10 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.776: Wait for finger on sensor 393s (process:1974): libfprint-device-DEBUG: 00:54:02.776: Device reported finger status change: FP_FINGER_STATUS_NEEDED 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.777: Finger on sensor callback 393s (process:1974): libfprint-device-DEBUG: 00:54:02.777: Device reported finger status change: FP_FINGER_STATUS_PRESENT 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.777: [egismoc] ENROLL_STATES entering state 11 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.777: Execute command and get response 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.777: Get check bytes 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.777: [egismoc] CMD_STATES entering state 0 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.777: [egismoc] CMD_STATES entering state 1 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.778: Command receive callback 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.778: [egismoc] CMD_STATES completed successfully 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.778: Read capture callback 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.778: Response prefix valid: yes 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.778: Response suffix valid: NO 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.778: Response prefix valid: yes 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.778: Response suffix valid: yes 393s (process:1974): libfprint-device-DEBUG: 00:54:02.778: Device reported enroll progress, reported 9 of 10 have been completed 393s listing - device should have prints 393s clear device storage 393s clear done 393s listing - device should be empty 393s enrolling 393s finger status: 393s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xea4cf2e8 (FpiDeviceEgisMoc at 0x71f5e8)>, 1, , None, None) 393s finger status: 393s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xea4cf2e8 (FpiDeviceEgisMoc at 0x71f5e8)>, 2, , None, None) 393s finger status: 393s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xea4cf2e8 (FpiDeviceEgisMoc at 0x71f5e8)>, 2, None, None, GLib.Error('The finger was not centered properly, please try again.', 'fp - device - retry - quark', 2)) 393s finger status: 393s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xea4cf2e8 (FpiDeviceEgisMoc at 0x71f5e8)>, 3, , None, None) 393s finger status: 393s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xea4cf2e8 (FpiDeviceEgisMoc at 0x71f5e8)>, 4, , None, None) 393s finger status: 393s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xea4cf2e8 (FpiDeviceEgisMoc at 0x71f5e8)>, 4, None, None, GLib.Error('The finger was not centered properly, please try again.', 'fp - device - retry - quark', 2)) 393s finger status: 393s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xea4cf2e8 (FpiDeviceEgisMoc at 0x71f5e8)>, 5, , None, None) 393s finger status: 393s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xea4cf2e8 (FpiDeviceEgisMoc at 0x71f5e8)>, 6, , None, None) 393s finger status: 393s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xea4cf2e8 (FpiDeviceEgisMoc at 0x71f5e8)>, 6, None, None, GLib.Error('The finger was not centered properly, please try again.', 'fp - device - retry - quark', 2)) 393s finger status: 393s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xea4cf2e8 (FpiDeviceEgisMoc at 0x71f5e8)>, 6, None, None, GLib.Error('The finger was not centered properly, please try again.', 'fp - device - retry - quark', 2)) 393s finger status: 393s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xea4cf2e8 (FpiDeviceEgisMoc at 0x71f5e8)>, 7, , None, None) 393s finger status: 393s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xea4cf2e8 (FpiDeviceEgisMoc at 0x71f5e8)>, 8, , None, None) 393s finger status: 393s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xea4cf2e8 (FpiDeviceEgisMoc at 0x71f5e8)>, 9, , None, None) 393s finger status: 393s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xea4cf2e8 (FpiDeviceEgisMoc at 0x71f5e8)>, 9, None, None, GLib.Error('The finger was not centered properly, please try again.', 'fp - device - retry - quark', 2)) 393s finger status: 393s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xea4cf2e8 (FpiDeviceEgisMoc at 0x71f5e8)>, 10, , None, None) 393s enroll done 393s listing - device should have 1 print 393s verifying 393s verify done 393s async identifying 393s indentification_done: 393s try to enroll duplicate 393s duplicate enroll attempt done 393s listing - device should still only have 1 print 393s enroll new finger 393s finger status: 393s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xea4cf2e8 (FpiDeviceEgisMoc at 0x71f5e8)>, 1, , None, None) 393s finger status: 393s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xea4cf2e8 (FpiDeviceEgisMoc at 0x71f5e8)>, 1, None, None, GLib.Error('The finger was not centered properly, please try again.', 'fp - device - retry - quark', 2)) 393s finger status: 393s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xea4cf2e8 (FpiDeviceEgisMoc at 0x71f5e8)>, 2, , None, None) 393s finger status: 393s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xea4cf2e8 (FpiDeviceEgisMoc at 0x71f5e8)>, 3, , None, None) 393s finger status: 393s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xea4cf2e8 (FpiDeviceEgisMoc at 0x71f5e8)>, 3, None, None, GLib.Error('The finger was not centered properly, please try again.', 'fp - device - retry - quark', 2)) 393s finger status: 393s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xea4cf2e8 (FpiDeviceEgisMoc at 0x71f5e8)>, 3, None, None, GLib.Error('The finger was not centered properly, please try again.', 'fp - device - retry - quark', 2)) 393s finger status: 393s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xea4cf2e8 (FpiDeviceEgisMoc at 0x71f5e8)>, 4, , None, None) 393s finger status: 393s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xea4cf2e8 (FpiDeviceEgisMoc at 0x71f5e8)>, 5, , None, None) 393s finger status: 393s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xea4cf2e8 (FpiDeviceEgisMoc at 0x71f5e8)>, 6, , None, None) 393s finger status: 393s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xea4cf2e8 (FpiDeviceEgisMoc at 0x71f5e8)>, 7, , None, None) 393s finger status: 393s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xea4cf2e8 (FpiDeviceEgisMoc at 0x71f5e8)>, 8, , None, None) 393s finger status: 393s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xea4cf2e8 (FpiDeviceEgisMoc at 0x71f5e8)>, 9, , None, None) 393s finger status: 393s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xea4cf2e8 (FpiDeviceEgisMoc at 0x71f5e8)>, 9, None, None, GLib.Error('The finger was not centered properly, please try again.', 'fp - device - retry - quark', 2)) 393s finger status: 393s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xea4cf2e8 (FpiDeviceEgisMoc at 0x71f5e8)>, 9, None, None, GLib.Error('The finger was not centered properly, please try again.', 'fp - device - retry - quark', 2))(process:1974): libfprint-SSM-DEBUG: 00:54:02.778: [egismoc] ENROLL_STATES entering state 8 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.778: Execute command and get response 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.778: Get check bytes 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.778: [egismoc] CMD_STATES entering state 0 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.779: [egismoc] CMD_STATES entering state 1 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.780: Command receive callback 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.780: [egismoc] CMD_STATES completed successfully 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.780: Task SSM next state callback 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.780: [egismoc] ENROLL_STATES entering state 9 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.780: Execute command and get response 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.780: Get check bytes 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.780: [egismoc] CMD_STATES entering state 0 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.780: [egismoc] CMD_STATES entering state 1 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.781: Command receive callback 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.781: [egismoc] CMD_STATES completed successfully 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.781: Task SSM next state callback 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.781: [egismoc] ENROLL_STATES entering state 10 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.781: Wait for finger on sensor 393s (process:1974): libfprint-device-DEBUG: 00:54:02.781: Device reported finger status change: FP_FINGER_STATUS_NEEDED 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.782: Finger on sensor callback 393s (process:1974): libfprint-device-DEBUG: 00:54:02.782: Device reported finger status change: FP_FINGER_STATUS_PRESENT 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.782: [egismoc] ENROLL_STATES entering state 11 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.782: Execute command and get response 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.782: Get check bytes 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.782: [egismoc] CMD_STATES entering state 0 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.782: [egismoc] CMD_STATES entering state 1 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.784: Command receive callback 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.784: [egismoc] CMD_STATES completed successfully 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.784: Read capture callback 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.784: Response prefix valid: yes 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.784: Response suffix valid: NO 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.784: Response prefix valid: yes 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.784: Response suffix valid: yes 393s (process:1974): libfprint-device-DEBUG: 00:54:02.784: Device reported enroll progress, reported 9 of 10 have been completed 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.784: [egismoc] ENROLL_STATES entering state 8 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.784: Execute command and get response 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.784: Get check bytes 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.784: [egismoc] CMD_STATES entering state 0 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.785: [egismoc] CMD_STATES entering state 1 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.786: Command receive callback 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.786: [egismoc] CMD_STATES completed successfully 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.786: Task SSM next state callback 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.786: [egismoc] ENROLL_STATES entering state 9 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.786: Execute command and get response 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.786: Get check bytes 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.786: [egismoc] CMD_STATES entering state 0 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.786: [egismoc] CMD_STATES entering state 1 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.787: Command receive callback 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.787: [egismoc] CMD_STATES completed successfully 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.787: Task SSM next state callback 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.787: [egismoc] ENROLL_STATES entering state 10 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.787: Wait for finger on sensor 393s (process:1974): libfprint-device-DEBUG: 00:54:02.787: Device reported finger status change: FP_FINGER_STATUS_NEEDED 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.787: Finger on sensor callback 393s (process:1974): libfprint-device-DEBUG: 00:54:02.788: Device reported finger status change: FP_FINGER_STATUS_PRESENT 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.788: [egismoc] ENROLL_STATES entering state 11 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.788: Execute command and get response 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.788: Get check bytes 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.788: [egismoc] CMD_STATES entering state 0 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.789: [egismoc] CMD_STATES entering state 1 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.790: Command receive callback 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.790: [egismoc] CMD_STATES completed successfully 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.790: Read capture callback 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.790: Response prefix valid: yes 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.790: Response suffix valid: yes 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.790: Partial capture successful. Please touch the sensor again (10/10) 393s (process:1974): libfprint-device-DEBUG: 00:54:02.790: Device reported enroll progress, reported 10 of 10 have been completed 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.790: [egismoc] ENROLL_STATES entering state 12 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.790: Execute command and get response 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.790: Get check bytes 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.790: [egismoc] CMD_STATES entering state 0 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.791: [egismoc] CMD_STATES entering state 1 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.792: Command receive callback 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.792: [egismoc] CMD_STATES completed successfully 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.792: Task SSM next state callback 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.792: [egismoc] ENROLL_STATES entering state 13 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.792: New fingerprint ID: FP1-00000000-7-00000000-nobody 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.792: Execute command and get response 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.792: Get check bytes 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.792: [egismoc] CMD_STATES entering state 0 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.793: [egismoc] CMD_STATES entering state 1 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.793: Command receive callback 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.793: [egismoc] CMD_STATES completed successfully 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.793: Task SSM next state callback 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.793: [egismoc] ENROLL_STATES entering state 14 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.793: Execute command and get response 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.793: Get check bytes 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.793: [egismoc] CMD_STATES entering state 0 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.794: [egismoc] CMD_STATES entering state 1 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.795: Command receive callback 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.795: [egismoc] CMD_STATES completed successfully 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.795: Task SSM next state callback 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.795: [egismoc] ENROLL_STATES entering state 15 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.795: Enrollment was successful! 393s (process:1974): libfprint-device-DEBUG: 00:54:02.795: Device reported enroll completion 393s (process:1974): libfprint-device-DEBUG: 00:54:02.795: Device reported finger status change: FP_FINGER_STATUS_NONE 393s (process:1974): libfprint-device-DEBUG: 00:54:02.795: Print for finger FP_FINGER_RIGHT_INDEX enrolled 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.795: [egismoc] ENROLL_STATES completed successfully 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.795: Task SSM done 393s (process:1974): libfprint-device-DEBUG: 00:54:02.795: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 393s (process:1974): libfprint-device-DEBUG: 00:54:02.795: Updated temperature model after 0.12 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.796: List 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.796: [egismoc] LIST_STATES entering state 0 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.796: Execute command and get response 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.796: Get check bytes 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.796: [egismoc] CMD_STATES entering state 0 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.796: [egismoc] CMD_STATES entering state 1 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.797: Command receive callback 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.797: [egismoc] CMD_STATES completed successfully 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.797: List callback 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.797: Device fingerprint 1: FP1-00000000-2-00000000-nobody 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.797: Device fingerprint 2: FP1-00000000-7-00000000-nobody 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.797: Number of currently enrolled fingerprints on the device is 2 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.797: [egismoc] LIST_STATES entering state 1 393s (process:1974): libfprint-device-DEBUG: 00:54:02.797: Device reported listing completion 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.797: [egismoc] LIST_STATES completed successfully 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.797: Task SSM done 393s (process:1974): libfprint-device-DEBUG: 00:54:02.797: Completing action FPI_DEVICE_ACTION_LIST in idle! 393s (process:1974): libfprint-device-DEBUG: 00:54:02.797: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.798: Delete 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.798: [egismoc] DELETE_STATES entering state 0 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.798: Execute command and get response 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.798: Get check bytes 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.798: [egismoc] CMD_STATES entering state 0 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.799: [egismoc] CMD_STATES entering state 1 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.800: Command receive callback 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.800: [egismoc] CMD_STATES completed successfully 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.800: List callback 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.800: Device fingerprint 1: FP1-00000000-2-00000000-nobody 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.800: Device fingerprint 2: FP1-00000000-7-00000000-nobody 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.800: Number of currently enrolled fingerprints on the device is 2 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.800: [egismoc] DELETE_STATES entering state 1 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.800: Get delete command 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.800: Delete fingerprint FP1-00000000-2-00000000-nobody (FP1-00000000-2-00000000-nobody) 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.800: Execute command and get response 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.800: Get check bytes 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.800: [egismoc] CMD_STATES entering state 0 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.800: [egismoc] CMD_STATES entering state 1 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.801: Command receive callback 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.801: [egismoc] CMD_STATES completed successfully 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.801: Delete callback 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.801: Response prefix valid: yes 393s (process:1974): libfprint-device-DEBUG: 00:54:02.801: Device reported deletion completion 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.801: [egismoc] DELETE_STATES completed successfully 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.801: Task SSM done 393s (process:1974): libfprint-device-DEBUG: 00:54:02.801: Completing action FPI_DEVICE_ACTION_DELETE in idle! 393s (process:1974): libfprint-device-DEBUG: 00:54:02.801: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.801: List 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.801: [egismoc] LIST_STATES entering state 0 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.801: Execute command and get response 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.801: Get check bytes 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.801: [egismoc] CMD_STATES entering state 0 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.802: [egismoc] CMD_STATES entering state 1 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.803: Command receive callback 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.803: [egismoc] CMD_STATES completed successfully 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.803: List callback 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.803: Device fingerprint 1: FP1-00000000-7-00000000-nobody 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.803: Number of currently enrolled fingerprints on the device is 1 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.803: [egismoc] LIST_STATES entering state 1 393s (process:1974): libfprint-device-DEBUG: 00:54:02.803: Device reported listing completion 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.803: [egismoc] LIST_STATES completed successfully 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.803: Task SSM done 393s (process:1974): libfprint-device-DEBUG: 00:54:02.803: Completing action FPI_DEVICE_ACTION_LIST in idle! 393s (process:1974): libfprint-device-DEBUG: 00:54:02.803: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.803: Clear storage 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.803: [egismoc] DELETE_STATES entering state 0 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.803: Execute command and get response 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.803: Get check bytes 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.803: [egismoc] CMD_STATES entering state 0 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.804: [egismoc] CMD_STATES entering state 1 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.805: Command receive callback 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.805: [egismoc] CMD_STATES completed successfully 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.805: List callback 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.805: Device fingerprint 1: FP1-00000000-7-00000000-nobody 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.805: Number of currently enrolled fingerprints on the device is 1 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.805: [egismoc] DELETE_STATES entering state 1 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.805: Get delete command 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.805: Execute command and get response 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.805: Get check bytes 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.805: [egismoc] CMD_STATES entering state 0 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.805: [egismoc] CMD_STATES entering state 1 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.806: Command receive callback 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.806: [egismoc] CMD_STATES completed successfully 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.806: Delete callback 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.806: Response prefix valid: yes 393s (process:1974): libfprint-device-DEBUG: 00:54:02.806: Device reported deletion completion 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.806: [egismoc] DELETE_STATES completed successfully 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.806: Task SSM done 393s (process:1974): libfprint-device-DEBUG: 00:54:02.806: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 393s (process:1974): libfprint-device-DEBUG: 00:54:02.806: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.806: List 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.806: [egismoc] LIST_STATES entering state 0 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.806: Execute command and get response 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.806: Get check bytes 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.806: [egismoc] CMD_STATES entering state 0 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.807: [egismoc] CMD_STATES entering state 1 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.808: Command receive callback 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.808: [egismoc] CMD_STATES completed successfully 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.808: List callback 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.808: Number of currently enrolled fingerprints on the device is 0 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.808: [egismoc] LIST_STATES entering state 1 393s (process:1974): libfprint-device-DEBUG: 00:54:02.808: Device reported listing completion 393s (process:1974): libfprint-SSM-DEBUG: 00:54:02.808: [egismoc] LIST_STATES completed successfully 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.808: Task SSM done 393s (process:1974): libfprint-device-DEBUG: 00:54:02.808: Completing action FPI_DEVICE_ACTION_LIST in idle! 393s (process:1974): libfprint-device-DEBUG: 00:54:02.808: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.808: Closing device 393s (process:1974): libfprint-egismoc-DEBUG: 00:54:02.808: Cancel 393s (process:1974): libfprint-device-DEBUG: 00:54:02.809: Device reported close completion 393s (process:1974): libfprint-device-DEBUG: 00:54:02.809: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 393s (process:1974): libfprint-device-DEBUG: 00:54:02.809: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 393s 393s finger status: 393s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xea4cf2e8 (FpiDeviceEgisMoc at 0x71f5e8)>, 9, None, None, GLib.Error('The finger was not centered properly, please try again.', 'fp - device - retry - quark', 2)) 393s finger status: 393s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xea4cf2e8 (FpiDeviceEgisMoc at 0x71f5e8)>, 10, , None, None) 393s enroll new finger done 393s listing - device should have 2 prints 393s deleting first print 393s delete done 393s listing - device should only have second print 393s clear device storage 393s clear done 393s listing - device should be empty 393s ** (umockdev-run:1970): DEBUG: 00:54:02.889: umockdev.vala:154: Removing test bed /tmp/umockdev.XZC612 393s (umockdev-run:1970): GLib-DEBUG: 00:54:02.896: unsetenv() is not thread-safe and should not be used after threads are created 393s PASS: libfprint-2/driver-egismoc.test 393s Running test: libfprint-2/driver-elanspi.test 394s ** (umockdev-run:1982): DEBUG: 00:54:02.977: umockdev.vala:127: Created udev test bed /tmp/umockdev.GTWL22 394s ** (umockdev-run:1982): DEBUG: 00:54:02.978: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:15.1/i2c_designware.1/i2c-1/i2c-ELAN1300:00/0018:04F3:3057.0001/hidraw/hidraw0 394s ** (umockdev-run:1982): DEBUG: 00:54:02.978: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:15.1/i2c_designware.1/i2c-1/i2c-ELAN1300:00/0018:04F3:3057.0001/hidraw/hidraw0 (subsystem hidraw) 394s ** (umockdev-run:1982): DEBUG: 00:54:02.980: umockdev.vala:1558: create_node_for_device: creating pty device /tmp/umockdev.GTWL22/dev/hidraw0: got pty /dev/pts/1 394s ** (umockdev-run:1982): DEBUG: 00:54:02.981: umockdev.vala:1579: create_node_for_device: creating ptymap symlink /tmp/umockdev.GTWL22/dev/.ptymap/_dev_pts_1 394s ** (umockdev-run:1982): DEBUG: 00:54:02.981: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:15.1/i2c_designware.1/i2c-1/i2c-ELAN1300:00/0018:04F3:3057.0001 394s ** (umockdev-run:1982): DEBUG: 00:54:02.981: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:15.1/i2c_designware.1/i2c-1/i2c-ELAN1300:00/0018:04F3:3057.0001 (subsystem hid) 394s ** (umockdev-run:1982): DEBUG: 00:54:02.983: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:15.1/i2c_designware.1/i2c-1/i2c-ELAN1300:00 394s ** (umockdev-run:1982): DEBUG: 00:54:02.983: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:15.1/i2c_designware.1/i2c-1/i2c-ELAN1300:00 (subsystem i2c) 394s ** (umockdev-run:1982): DEBUG: 00:54:02.985: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:15.1/i2c_designware.1/i2c-1 394s ** (umockdev-run:1982): DEBUG: 00:54:02.985: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:15.1/i2c_designware.1/i2c-1 (subsystem i2c) 394s ** (umockdev-run:1982): DEBUG: 00:54:02.987: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:15.1/i2c_designware.1 394s ** (umockdev-run:1982): DEBUG: 00:54:02.987: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:15.1/i2c_designware.1 (subsystem platform) 394s ** (umockdev-run:1982): DEBUG: 00:54:02.989: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:15.1 394s ** (umockdev-run:1982): DEBUG: 00:54:02.990: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:15.1 (subsystem pci) 394s ** (umockdev-run:1982): DEBUG: 00:54:02.994: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:1e.2/pxa2xx-spi.3/spi_master/spi0/spi-ELAN7001:00/spidev/spidev0.0 394s ** (umockdev-run:1982): DEBUG: 00:54:02.994: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:1e.2/pxa2xx-spi.3/spi_master/spi0/spi-ELAN7001:00/spidev/spidev0.0 (subsystem spidev) 394s ** (umockdev-run:1982): DEBUG: 00:54:02.997: umockdev.vala:1558: create_node_for_device: creating pty device /tmp/umockdev.GTWL22/dev/spidev0.0: got pty /dev/pts/2 394s ** (umockdev-run:1982): DEBUG: 00:54:02.997: umockdev.vala:1579: create_node_for_device: creating ptymap symlink /tmp/umockdev.GTWL22/dev/.ptymap/_dev_pts_2 394s ** (umockdev-run:1982): DEBUG: 00:54:02.997: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:1e.2/pxa2xx-spi.3/spi_master/spi0/spi-ELAN7001:00 394s ** (umockdev-run:1982): DEBUG: 00:54:02.998: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:1e.2/pxa2xx-spi.3/spi_master/spi0/spi-ELAN7001:00 (subsystem spi) 394s ** (umockdev-run:1982): DEBUG: 00:54:03.003: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:1e.2/pxa2xx-spi.3/spi_master/spi0 394s ** (umockdev-run:1982): DEBUG: 00:54:03.003: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:1e.2/pxa2xx-spi.3/spi_master/spi0 (subsystem spi_master) 394s ** (umockdev-run:1982): DEBUG: 00:54:03.009: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:1e.2/pxa2xx-spi.3 394s ** (umockdev-run:1982): DEBUG: 00:54:03.009: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:1e.2/pxa2xx-spi.3 (subsystem platform) 394s ** (umockdev-run:1982): DEBUG: 00:54:03.010: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:1e.2 394s ** (umockdev-run:1982): DEBUG: 00:54:03.011: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:1e.2 (subsystem pci) 394s (umockdev-run:1982): GLib-GIO-DEBUG: 00:54:03.015: _g_io_module_get_default: Found default implementation local (GLocalVfs) for ?gio-vfs? 394s (process:1986): libfprint-context-DEBUG: 00:54:03.209: Initializing FpContext (libfprint version 1.94.8+tod1) 394s (process:1986): libfprint-tod-DEBUG: 00:54:03.210: Impossible to load the shared drivers dir Error opening directory “/usr/lib/arm-linux-gnueabihf/libfprint-2/tod-1”: No such file or directory 394s (process:1986): libfprint-device-DEBUG: 00:54:03.214: Device reported probe completion 394s (process:1986): libfprint-device-DEBUG: 00:54:03.214: Completing action FPI_DEVICE_ACTION_PROBE in idle! 394s (process:1986): libfprint-device-DEBUG: 00:54:03.214: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 394s (process:1986): libfprint-elanspi-DEBUG: 00:54:03.215: 7399811276594: ../libfprint/drivers/elanspi.c:1562 394s libfprint-Message: 00:54:03.216: Failed to read spidev block size, using 4096 394s (process:1986): libfprint-image_device-DEBUG: 00:54:03.215: Image device open completed 394s (process:1986): libfprint-device-DEBUG: 00:54:03.215: Device reported open completion 394s (process:1986): libfprint-device-DEBUG: 00:54:03.215: Completing action FPI_DEVICE_ACTION_OPEN in idle! 394s (process:1986): libfprint-device-DEBUG: 00:54:03.215: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 394s (process:1986): libfprint-device-DEBUG: 00:54:03.216: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 394s (process:1986): libfprint-image_device-DEBUG: 00:54:03.216: Activating image device 394s (process:1986): libfprint-image_device-DEBUG: 00:54:03.216: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING 394s (process:1986): libfprint-SSM-DEBUG: 00:54:03.216: [elanspi] ELANSPI_INIT_NSTATES entering state 0 394s (process:1986): libfprint-SSM-DEBUG: 00:54:03.218: [elanspi] ELANSPI_INIT_NSTATES entering state 1 394s (process:1986): libfprint-elanspi-DEBUG: 00:54:03.218: got status 81 394s (process:1986): libfprint-elanspi-DEBUG: 00:54:03.218: sync hw reset 394s (process:1986): libfprint-SSM-DEBUG: 00:54:03.219: [elanspi] ELANSPI_INIT_NSTATES entering state 2 394s (process:1986): libfprint-SSM-DEBUG: 00:54:03.223: [elanspi] ELANSPI_INIT_NSTATES entering state 3 394s (process:1986): libfprint-elanspi-DEBUG: 00:54:03.223: sw reset ok 394s (process:1986): libfprint-SSM-DEBUG: 00:54:03.224: [elanspi] ELANSPI_INIT_NSTATES entering state 4 394s (process:1986): libfprint-elanspi-DEBUG: 00:54:03.224: raw height = 96 394s (process:1986): libfprint-SSM-DEBUG: 00:54:03.225: [elanspi] ELANSPI_INIT_NSTATES entering state 5 394s (process:1986): libfprint-elanspi-DEBUG: 00:54:03.225: raw width = 96 394s (process:1986): libfprint-SSM-DEBUG: 00:54:03.225: [elanspi] ELANSPI_INIT_NSTATES entering state 6 394s (process:1986): libfprint-elanspi-DEBUG: 00:54:03.225: raw reg17 = 175 394s (process:1986): libfprint-SSM-DEBUG: 00:54:03.226: [elanspi] ELANSPI_INIT_NSTATES entering state 7 394s (process:1986): libfprint-elanspi-DEBUG: 00:54:03.226: raw version = 09 394s (process:1986): libfprint-elanspi-DEBUG: 00:54:03.226: after hardcoded lookup; 96x96, version 1 394s (process:1986): libfprint-elanspi-DEBUG: 00:54:03.226: found sensor ID 6 => [eFSA96SA] (96 x 96) 394s (process:1986): libfprint-SSM-DEBUG: 00:54:03.226: [elanspi] ELANSPI_INIT_NSTATES entering state 8 394s (process:1986): libfprint-SSM-DEBUG: 00:54:03.230: [elanspi] ELANSPI_INIT_NSTATES entering state 9 394s (process:1986): libfprint-SSM-DEBUG: 00:54:03.231: [elanspi] ELANSPI_INIT_NSTATES entering state 10 394s (process:1986): libfprint-SSM-DEBUG: 00:54:03.232: [elanspi] ELANSPI_INIT_NSTATES entering state 11 394s (process:1986): libfprint-SSM-DEBUG: 00:54:03.232: [elanspi] ELANSPI_INIT_NSTATES entering state 12 394s (process:1986): libfprint-SSM-DEBUG: 00:54:03.233: [elanspi] ELANSPI_INIT_NSTATES entering state 13 394s (process:1986): libfprint-SSM-DEBUG: 00:54:03.233: [elanspi] ELANSPI_INIT_NSTATES entering state 14 394s (process:1986): libfprint-SSM-DEBUG: 00:54:03.233: [elanspi] ELANSPI_INIT_NSTATES entering state 17 394s (process:1986): libfprint-elanspi-DEBUG: 00:54:03.233: got vcm mode = 2 394s (process:1986): libfprint-SSM-DEBUG: 00:54:03.234: [elanspi] ELANSPI_INIT_NSTATES entering state 18 394s (process:1986): libfprint-SSM-DEBUG: 00:54:03.234: [elanspi] ELANSPI_INIT_NSTATES entering state 19 394s (process:1986): libfprint-elanspi-DEBUG: 00:54:03.234: starting calibrate 394s (process:1986): libfprint-SSM-DEBUG: 00:54:03.234: [elanspi] old calibrate entering state 0 394s (process:1986): libfprint-SSM-DEBUG: 00:54:03.236: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0 394s (process:1986): libfprint-SSM-DEBUG: 00:54:03.237: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1 394s (process:1986): libfprint-SSM-DEBUG: 00:54:03.237: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0 394s (process:1986): libfprint-SSM-DEBUG: 00:54:03.237: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1 394s (process:1986): libfprint-SSM-DEBUG: 00:54:03.237: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0 394s (process:1986): libfprint-SSM-DEBUG: 00:54:03.237: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1 394s (process:1986): libfprint-SSM-DEBUG: 00:54:03.237: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0 394s (process:1986): libfprint-SSM-DEBUG: 00:54:03.238: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1 394s (process:1986): libfprint-SSM-DEBUG: 00:54:03.238: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0 394s (process:1986): libfprint-SSM-DEBUG: 00:54:03.238: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1 394s (process:1986): libfprint-SSM-DEBUG: 00:54:03.238: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0 394s (process:1986): libfprint-SSM-DEBUG: 00:54:03.239: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1 394s (process:1986): libfprint-SSM-DEBUG: 00:54:03.239: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0 394s (process:1986): libfprint-SSM-DEBUG: 00:54:03.239: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1 394s (process:1986): libfprint-SSM-DEBUG: 00:54:03.239: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0 394s (process:1986): libfprint-SSM-DEBUG: 00:54:03.240: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1 394s (process:1986): libfprint-SSM-DEBUG: 00:54:03.240: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0 394s (process:1986): libfprint-SSM-DEBUG: 00:54:03.240: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1 394s (process:1986): libfprint-SSM-DEBUG: 00:54:03.240: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0 394s (process:1986): libfprint-SSM-DEBUG: 00:54:03.241: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1 394s (process:1986): libfprint-SSM-DEBUG: 00:54:03.241: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0 394s (process:1986): libfprint-SSM-DEBUG: 00:54:03.241: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1 394s (process:1986): libfprint-SSM-DEBUG: 00:54:03.241: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0 394s (process:1986): libfprint-SSM-DEBUG: 00:54:03.241: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1 394s (process:1986): libfprint-SSM-DEBUG: 00:54:03.241: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0 394s (process:1986): libfprint-SSM-DEBUG: 00:54:03.242: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1 394s (process:1986): libfprint-SSM-DEBUG: 00:54:03.242: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0 394s (process:1986): libfprint-SSM-DEBUG: 00:54:03.242: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1 394s (process:1986): libfprint-SSM-DEBUG: 00:54:03.242: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0 394s (process:1986): libfprint-SSM-DEBUG: 00:54:03.243: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1 394s (process:1986): libfprint-SSM-DEBUG: 00:54:03.243: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0 394s (process:1986): libfprint-SSM-DEBUG: 00:54:03.243: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1 394s (process:1986): libfprint-SSM-DEBUG: 00:54:03.243: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0 394s (process:1986): libfprint-SSM-DEBUG: 00:54:03.243: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1 394s (process:1986): libfprint-SSM-DEBUG: 00:54:03.243: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0 394s (process:1986): libfprint-SSM-DEBUG: 00:54:03.244: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1 394s (process:1986): libfprint-SSM-DEBUG: 00:54:03.244: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0 394s (process:1986): libfprint-SSM-DEBUG: 00:54:03.244: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1 394s (process:1986): libfprint-SSM-DEBUG: 00:54:03.244: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0 394s (process:1986): libfprint-SSM-DEBUG: 00:54:03.244: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1 394s (process:1986): libfprint-SSM-DEBUG: 00:54:03.244: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0 394s (process:1986): libfprint-SSM-DEBUG: 00:54:03.245: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1 394s (process:1986): libfprint-SSM-DEBUG: 00:54:03.245: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0 394s (process:1986): libfprint-SSM-DEBUG: 00:54:03.245: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1 394s (process:1986): libfprint-SSM-DEBUG: 00:54:03.245: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0 394s (process:1986): libfprint-SSM-DEBUG: 00:54:03.246: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1 394s (process:1986): libfprint-SSM-DEBUG: 00:54:03.246: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0 394s (process:1986): libfprint-SSM-DEBUG: 00:54:03.246: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1 394s (process:1986): libfprint-SSM-DEBUG: 00:54:03.246: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0 394s (process:1986): libfprint-SSM-DEBUG: 00:54:03.246: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1 394s (process:1986): libfprint-SSM-DEBUG: 00:54:03.246: [elanspi] ELANSPI_WRTABLE_NSTATES completed successfully 394s (process:1986): libfprint-SSM-DEBUG: 00:54:03.246: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 394s (process:1986): libfprint-SSM-DEBUG: 00:54:03.299: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 394s (process:1986): libfprint-elanspi-DEBUG: 00:54:03.299: dac init is 0x29 394s (process:1986): libfprint-SSM-DEBUG: 00:54:03.299: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 394s (process:1986): libfprint-device-DEBUG: 00:54:03.316: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 394s (process:1986): libfprint-SSM-DEBUG: 00:54:03.350: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 394s (process:1986): libfprint-SSM-DEBUG: 00:54:03.350: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 394s (process:1986): libfprint-SSM-DEBUG: 00:54:03.418: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 394s (process:1986): libfprint-elanspi-DEBUG: 00:54:03.418: calibration ok, saving bg image 394s (process:1986): libfprint-SSM-DEBUG: 00:54:03.418: [elanspi] old calibrate completed successfully 394s (process:1986): libfprint-SSM-DEBUG: 00:54:03.418: [elanspi] ELANSPI_INIT_NSTATES entering state 20 394s (process:1986): libfprint-SSM-DEBUG: 00:54:03.418: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 394s (process:1986): libfprint-SSM-DEBUG: 00:54:03.505: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 394s (process:1986): libfprint-SSM-DEBUG: 00:54:03.505: [elanspi] ELANSPI_INIT_NSTATES entering state 21 394s (process:1986): libfprint-SSM-DEBUG: 00:54:03.505: [elanspi] ELANSPI_INIT_NSTATES completed successfully 394s (process:1986): libfprint-elanspi-DEBUG: 00:54:03.505: 7399811566454: ../libfprint/drivers/elanspi.c:1596 394s (process:1986): libfprint-image_device-DEBUG: 00:54:03.505: Image device activation completed 394s (process:1986): libfprint-image_device-DEBUG: 00:54:03.505: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE 394s (process:1986): libfprint-image_device-DEBUG: 00:54:03.505: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 394s (process:1986): libfprint-SSM-DEBUG: 00:54:03.505: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 0 394s (process:1986): libfprint-SSM-DEBUG: 00:54:03.505: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 1 394s (process:1986): libfprint-SSM-DEBUG: 00:54:03.505: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 394s (process:1986): libfprint-elanspi-DEBUG: 00:54:03.505: started capturer 394s (process:1986): libfprint-device-DEBUG: 00:54:03.505: Device reported finger status change: FP_FINGER_STATUS_NEEDED 394s (process:1986): libfprint-SSM-DEBUG: 00:54:03.588: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 394s (process:1986): libfprint-SSM-DEBUG: 00:54:03.588: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 2 394s (process:1986): libfprint-elanspi-DEBUG: 00:54:03.588: stddev=933d, ip=40, is_fp=0, is_empty=2 394s (process:1986): libfprint-SSM-DEBUG: 00:54:03.588: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 1 394s (process:1986): libfprint-SSM-DEBUG: 00:54:03.588: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 394s (process:1986): libfprint-SSM-DEBUG: 00:54:03.651: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 394s (process:1986): libfprint-SSM-DEBUG: 00:54:03.652: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 2 394s (process:1986): libfprint-elanspi-DEBUG: 00:54:03.652: stddev=829d, ip=48, is_fp=0, is_empty=2 394s (process:1986): libfprint-SSM-DEBUG: 00:54:03.652: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 1 394s (process:1986): libfprint-SSM-DEBUG: 00:54:03.652: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 394s (process:1986): libfprint-SSM-DEBUG: 00:54:03.714: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 394s (process:1986): libfprint-SSM-DEBUG: 00:54:03.714: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 2 394s (process:1986): libfprint-elanspi-DEBUG: 00:54:03.715: stddev=1307d, ip=37, is_fp=0, is_empty=2 394s (process:1986): libfprint-SSM-DEBUG: 00:54:03.715: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 1 394s (process:1986): libfprint-SSM-DEBUG: 00:54:03.715: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 394s (process:1986): libfprint-SSM-DEBUG: 00:54:03.773: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 394s (process:1986): libfprint-SSM-DEBUG: 00:54:03.773: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 2 394s (process:1986): libfprint-elanspi-DEBUG: 00:54:03.773: stddev=1163d, ip=38, is_fp=0, is_empty=2 394s (process:1986): libfprint-SSM-DEBUG: 00:54:03.773: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 1 394s (process:1986): libfprint-SSM-DEBUG: 00:54:03.773: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 394s (process:1986): libfprint-SSM-DEBUG: 00:54:03.857: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 394s (process:1986): libfprint-SSM-DEBUG: 00:54:03.857: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 2 394s (process:1986): libfprint-elanspi-DEBUG: 00:54:03.857: stddev=960d, ip=43, is_fp=0, is_empty=2 394s (process:1986): libfprint-SSM-DEBUG: 00:54:03.857: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 1 394s (process:1986): libfprint-SSM-DEBUG: 00:54:03.857: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 394s (process:1986): libfprint-SSM-DEBUG: 00:54:03.918: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 394s (process:1986): libfprint-SSM-DEBUG: 00:54:03.918: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 2 394s (process:1986): libfprint-elanspi-DEBUG: 00:54:03.918: stddev=879d, ip=41, is_fp=0, is_empty=2 394s (process:1986): libfprint-SSM-DEBUG: 00:54:03.918: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 1 394s (process:1986): libfprint-SSM-DEBUG: 00:54:03.918: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 395s (process:1986): libfprint-SSM-DEBUG: 00:54:03.976: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 395s (process:1986): libfprint-SSM-DEBUG: 00:54:03.976: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 2 395s (process:1986): libfprint-elanspi-DEBUG: 00:54:03.976: stddev=925d, ip=44, is_fp=0, is_empty=2 395s (process:1986): libfprint-SSM-DEBUG: 00:54:03.976: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 1 395s (process:1986): libfprint-SSM-DEBUG: 00:54:03.976: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 395s (process:1986): libfprint-SSM-DEBUG: 00:54:04.037: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 395s (process:1986): libfprint-SSM-DEBUG: 00:54:04.037: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 2 395s (process:1986): libfprint-elanspi-DEBUG: 00:54:04.037: stddev=1244d, ip=37, is_fp=0, is_empty=2 395s (process:1986): libfprint-SSM-DEBUG: 00:54:04.037: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 1 395s (process:1986): libfprint-SSM-DEBUG: 00:54:04.037: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 395s (process:1986): libfprint-SSM-DEBUG: 00:54:04.097: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 395s (process:1986): libfprint-SSM-DEBUG: 00:54:04.097: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 2 395s (process:1986): libfprint-elanspi-DEBUG: 00:54:04.097: stddev=709d, ip=48, is_fp=0, is_empty=2 395s (process:1986): libfprint-SSM-DEBUG: 00:54:04.097: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 1 395s (process:1986): libfprint-SSM-DEBUG: 00:54:04.097: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 395s (process:1986): libfprint-SSM-DEBUG: 00:54:04.151: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 395s (process:1986): libfprint-SSM-DEBUG: 00:54:04.152: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 2 395s (process:1986): libfprint-elanspi-DEBUG: 00:54:04.152: stddev=553d, ip=54, is_fp=0, is_empty=2 395s (process:1986): libfprint-SSM-DEBUG: 00:54:04.152: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 1 395s (process:1986): libfprint-SSM-DEBUG: 00:54:04.152: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 395s (process:1986): libfprint-SSM-DEBUG: 00:54:04.208: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 395s (process:1986): libfprint-SSM-DEBUG: 00:54:04.208: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 2 395s (process:1986): libfprint-elanspi-DEBUG: 00:54:04.208: stddev=904d, ip=44, is_fp=0, is_empty=2 395s (process:1986): libfprint-SSM-DEBUG: 00:54:04.208: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 1 395s (process:1986): libfprint-SSM-DEBUG: 00:54:04.208: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 395s (process:1986): libfprint-SSM-DEBUG: 00:54:04.265: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 395s (process:1986): libfprint-SSM-DEBUG: 00:54:04.265: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 2 395s (process:1986): libfprint-elanspi-DEBUG: 00:54:04.265: stddev=951d, ip=46, is_fp=0, is_empty=2 395s (process:1986): libfprint-SSM-DEBUG: 00:54:04.265: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 1 395s (process:1986): libfprint-SSM-DEBUG: 00:54:04.265: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 395s (process:1986): libfprint-SSM-DEBUG: 00:54:04.339: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 395s (process:1986): libfprint-SSM-DEBUG: 00:54:04.339: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 2 395s (process:1986): libfprint-elanspi-DEBUG: 00:54:04.340: stddev=795d, ip=44, is_fp=0, is_empty=2 395s (process:1986): libfprint-SSM-DEBUG: 00:54:04.340: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 1 395s (process:1986): libfprint-SSM-DEBUG: 00:54:04.340: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 395s (process:1986): libfprint-SSM-DEBUG: 00:54:04.394: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 395s (process:1986): libfprint-SSM-DEBUG: 00:54:04.394: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 2 395s (process:1986): libfprint-elanspi-DEBUG: 00:54:04.394: stddev=985d, ip=41, is_fp=0, is_empty=2 395s (process:1986): libfprint-SSM-DEBUG: 00:54:04.394: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 1 395s (process:1986): libfprint-SSM-DEBUG: 00:54:04.394: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 395s (process:1986): libfprint-SSM-DEBUG: 00:54:04.446: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 395s (process:1986): libfprint-SSM-DEBUG: 00:54:04.446: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 2 395s (process:1986): libfprint-elanspi-DEBUG: 00:54:04.447: stddev=938d, ip=40, is_fp=0, is_empty=2 395s (process:1986): libfprint-SSM-DEBUG: 00:54:04.447: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 1 395s (process:1986): libfprint-SSM-DEBUG: 00:54:04.447: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 395s (process:1986): libfprint-SSM-DEBUG: 00:54:04.499: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 395s (process:1986): libfprint-SSM-DEBUG: 00:54:04.500: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 2 395s (process:1986): libfprint-elanspi-DEBUG: 00:54:04.500: stddev=846d, ip=40, is_fp=0, is_empty=2 395s (process:1986): libfprint-SSM-DEBUG: 00:54:04.500: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 1 395s (process:1986): libfprint-SSM-DEBUG: 00:54:04.500: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 395s (process:1986): libfprint-SSM-DEBUG: 00:54:04.553: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 395s (process:1986): libfprint-SSM-DEBUG: 00:54:04.553: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 2 395s (process:1986): libfprint-elanspi-DEBUG: 00:54:04.553: stddev=693d, ip=56, is_fp=0, is_empty=2 395s (process:1986): libfprint-SSM-DEBUG: 00:54:04.553: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 1 395s (process:1986): libfprint-SSM-DEBUG: 00:54:04.553: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 395s (process:1986): libfprint-SSM-DEBUG: 00:54:04.609: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 395s (process:1986): libfprint-SSM-DEBUG: 00:54:04.609: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 2 395s (process:1986): libfprint-elanspi-DEBUG: 00:54:04.610: stddev=777d, ip=50, is_fp=0, is_empty=2 395s (process:1986): libfprint-SSM-DEBUG: 00:54:04.610: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 1 395s (process:1986): libfprint-SSM-DEBUG: 00:54:04.610: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 395s (process:1986): libfprint-SSM-DEBUG: 00:54:04.662: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 395s (process:1986): libfprint-SSM-DEBUG: 00:54:04.662: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 2 395s (process:1986): libfprint-elanspi-DEBUG: 00:54:04.663: stddev=824d, ip=45, is_fp=0, is_empty=2 395s (process:1986): libfprint-SSM-DEBUG: 00:54:04.663: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 1 395s (process:1986): libfprint-SSM-DEBUG: 00:54:04.663: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 395s (process:1986): libfprint-SSM-DEBUG: 00:54:04.715: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 395s (process:1986): libfprint-SSM-DEBUG: 00:54:04.715: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 2 395s (process:1986): libfprint-elanspi-DEBUG: 00:54:04.715: stddev=521d, ip=50, is_fp=0, is_empty=2 395s (process:1986): libfprint-SSM-DEBUG: 00:54:04.715: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 1 395s (process:1986): libfprint-SSM-DEBUG: 00:54:04.715: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 395s (process:1986): libfprint-SSM-DEBUG: 00:54:04.767: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 395s (process:1986): libfprint-SSM-DEBUG: 00:54:04.767: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 2 395s (process:1986): libfprint-elanspi-DEBUG: 00:54:04.767: stddev=670d, ip=47, is_fp=0, is_empty=2 395s (process:1986): libfprint-SSM-DEBUG: 00:54:04.767: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 1 395s (process:1986): libfprint-SSM-DEBUG: 00:54:04.767: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 395s (process:1986): libfprint-SSM-DEBUG: 00:54:04.823: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 395s (process:1986): libfprint-SSM-DEBUG: 00:54:04.823: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 2 395s (process:1986): libfprint-elanspi-DEBUG: 00:54:04.823: stddev=1262d, ip=39, is_fp=0, is_empty=2 395s (process:1986): libfprint-SSM-DEBUG: 00:54:04.823: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 1 395s (process:1986): libfprint-SSM-DEBUG: 00:54:04.823: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 395s (process:1986): libfprint-SSM-DEBUG: 00:54:04.879: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 395s (process:1986): libfprint-SSM-DEBUG: 00:54:04.879: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 2 395s (process:1986): libfprint-elanspi-DEBUG: 00:54:04.880: stddev=912d, ip=42, is_fp=0, is_empty=2 395s (process:1986): libfprint-SSM-DEBUG: 00:54:04.880: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 1 395s (process:1986): libfprint-SSM-DEBUG: 00:54:04.880: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 395s (process:1986): libfprint-SSM-DEBUG: 00:54:04.936: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 395s (process:1986): libfprint-SSM-DEBUG: 00:54:04.936: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 2 395s (process:1986): libfprint-elanspi-DEBUG: 00:54:04.936: stddev=1402d, ip=37, is_fp=0, is_empty=2 395s (process:1986): libfprint-SSM-DEBUG: 00:54:04.936: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 1 395s (process:1986): libfprint-SSM-DEBUG: 00:54:04.936: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 396s (process:1986): libfprint-SSM-DEBUG: 00:54:04.990: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 396s (process:1986): libfprint-SSM-DEBUG: 00:54:04.990: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 2 396s (process:1986): libfprint-elanspi-DEBUG: 00:54:04.990: stddev=1530d, ip=32, is_fp=0, is_empty=2 396s (process:1986): libfprint-SSM-DEBUG: 00:54:04.990: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 1 396s (process:1986): libfprint-SSM-DEBUG: 00:54:04.990: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 396s (process:1986): libfprint-SSM-DEBUG: 00:54:05.041: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 396s (process:1986): libfprint-SSM-DEBUG: 00:54:05.041: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 2 396s (process:1986): libfprint-elanspi-DEBUG: 00:54:05.041: stddev=718159d, ip=6, is_fp=1, is_empty=0 396s (process:1986): libfprint-SSM-DEBUG: 00:54:05.041: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 1 396s (process:1986): libfprint-SSM-DEBUG: 00:54:05.041: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 396s (process:1986): libfprint-SSM-DEBUG: 00:54:05.097: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 396s (process:1986): libfprint-SSM-DEBUG: 00:54:05.097: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 2 396s (process:1986): libfprint-elanspi-DEBUG: 00:54:05.098: stddev=400929d, ip=0, is_fp=2, is_empty=0 396s (process:1986): libfprint-device-DEBUG: 00:54:05.098: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 396s (process:1986): libfprint-image_device-DEBUG: 00:54:05.098: Image device reported finger status: on 396s (process:1986): libfprint-image_device-DEBUG: 00:54:05.098: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 396s (process:1986): libfprint-SSM-DEBUG: 00:54:05.098: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 3 396s (process:1986): libfprint-SSM-DEBUG: 00:54:05.098: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 396s (process:1986): libfprint-SSM-DEBUG: 00:54:05.155: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 396s (process:1986): libfprint-SSM-DEBUG: 00:54:05.155: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 4 396s (process:1986): libfprint-elanspi-DEBUG: 00:54:05.156: stddev=346514d, ip=0, is_fp=1, is_empty=0 396s (process:1986): libfprint-SSM-DEBUG: 00:54:05.157: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 3 396s (process:1986): libfprint-SSM-DEBUG: 00:54:05.157: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 396s (process:1986): libfprint-SSM-DEBUG: 00:54:05.211: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 396s (process:1986): libfprint-SSM-DEBUG: 00:54:05.211: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 4 396s (process:1986): libfprint-elanspi-DEBUG: 00:54:05.212: stddev=324160d, ip=0, is_fp=1, is_empty=0 396s (process:1986): libfprint-elanspi-DEBUG: 00:54:05.213: diff = 107344 396s (process:1986): libfprint-SSM-DEBUG: 00:54:05.213: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 3 396s (process:1986): libfprint-SSM-DEBUG: 00:54:05.213: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 396s (process:1986): libfprint-SSM-DEBUG: 00:54:05.266: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 396s (process:1986): libfprint-SSM-DEBUG: 00:54:05.266: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 4 396s (process:1986): libfprint-elanspi-DEBUG: 00:54:05.266: stddev=339430d, ip=0, is_fp=1, is_empty=0 396s (process:1986): libfprint-elanspi-DEBUG: 00:54:05.267: diff = 246471 396s (process:1986): libfprint-SSM-DEBUG: 00:54:05.267: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 3 396s (process:1986): libfprint-SSM-DEBUG: 00:54:05.267: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 396s (process:1986): libfprint-SSM-DEBUG: 00:54:05.318: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 396s (process:1986): libfprint-SSM-DEBUG: 00:54:05.318: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 4 396s (process:1986): libfprint-elanspi-DEBUG: 00:54:05.318: stddev=334711d, ip=0, is_fp=1, is_empty=0 396s (process:1986): libfprint-elanspi-DEBUG: 00:54:05.319: diff = 73010 396s (process:1986): libfprint-SSM-DEBUG: 00:54:05.319: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 3 396s (process:1986): libfprint-SSM-DEBUG: 00:54:05.319: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 396s (process:1986): libfprint-SSM-DEBUG: 00:54:05.369: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 396s (process:1986): libfprint-SSM-DEBUG: 00:54:05.369: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 4 396s (process:1986): libfprint-elanspi-DEBUG: 00:54:05.370: stddev=317574d, ip=0, is_fp=1, is_empty=0 396s (process:1986): libfprint-elanspi-DEBUG: 00:54:05.371: diff = 58831 396s (process:1986): libfprint-elanspi-DEBUG: 00:54:05.371: ignoring b.c. difference is too small 396s (process:1986): libfprint-SSM-DEBUG: 00:54:05.371: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 3 396s (process:1986): libfprint-SSM-DEBUG: 00:54:05.371: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 396s (process:1986): libfprint-SSM-DEBUG: 00:54:05.424: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 396s (process:1986): libfprint-SSM-DEBUG: 00:54:05.424: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 4 396s (process:1986): libfprint-elanspi-DEBUG: 00:54:05.425: stddev=285577d, ip=0, is_fp=1, is_empty=0 396s (process:1986): libfprint-elanspi-DEBUG: 00:54:05.425: diff = 241923 396s (process:1986): libfprint-SSM-DEBUG: 00:54:05.425: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 3 396s (process:1986): libfprint-SSM-DEBUG: 00:54:05.425: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 396s (process:1986): libfprint-SSM-DEBUG: 00:54:05.477: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 396s (process:1986): libfprint-SSM-DEBUG: 00:54:05.477: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 4 396s (process:1986): libfprint-elanspi-DEBUG: 00:54:05.477: stddev=417772d, ip=0, is_fp=2, is_empty=0 396s (process:1986): libfprint-elanspi-DEBUG: 00:54:05.478: diff = 254823 396s (process:1986): libfprint-SSM-DEBUG: 00:54:05.478: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 3 396s (process:1986): libfprint-SSM-DEBUG: 00:54:05.478: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 396s (process:1986): libfprint-SSM-DEBUG: 00:54:05.530: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 396s (process:1986): libfprint-SSM-DEBUG: 00:54:05.530: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 4 396s (process:1986): libfprint-elanspi-DEBUG: 00:54:05.531: stddev=541148d, ip=0, is_fp=2, is_empty=0 396s (process:1986): libfprint-elanspi-DEBUG: 00:54:05.532: diff = 290922 396s (process:1986): libfprint-SSM-DEBUG: 00:54:05.532: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 3 396s (process:1986): libfprint-SSM-DEBUG: 00:54:05.532: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 396s (process:1986): libfprint-SSM-DEBUG: 00:54:05.586: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 396s (process:1986): libfprint-SSM-DEBUG: 00:54:05.586: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 4 396s (process:1986): libfprint-elanspi-DEBUG: 00:54:05.586: stddev=580192d, ip=0, is_fp=2, is_empty=0 396s (process:1986): libfprint-elanspi-DEBUG: 00:54:05.587: diff = 332283 396s (process:1986): libfprint-SSM-DEBUG: 00:54:05.587: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 3 396s (process:1986): libfprint-SSM-DEBUG: 00:54:05.587: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 396s (process:1986): libfprint-SSM-DEBUG: 00:54:05.641: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 396s (process:1986): libfprint-SSM-DEBUG: 00:54:05.641: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 4 396s (process:1986): libfprint-elanspi-DEBUG: 00:54:05.641: stddev=484527d, ip=0, is_fp=2, is_empty=0 396s (process:1986): libfprint-elanspi-DEBUG: 00:54:05.642: diff = 325141 396s (process:1986): libfprint-SSM-DEBUG: 00:54:05.642: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 3 396s (process:1986): libfprint-SSM-DEBUG: 00:54:05.642: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 396s (process:1986): libfprint-SSM-DEBUG: 00:54:05.695: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 396s (process:1986): libfprint-SSM-DEBUG: 00:54:05.695: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 4 396s (process:1986): libfprint-elanspi-DEBUG: 00:54:05.696: stddev=482100d, ip=0, is_fp=2, is_empty=0 396s (process:1986): libfprint-elanspi-DEBUG: 00:54:05.697: diff = 337412 396s (process:1986): libfprint-SSM-DEBUG: 00:54:05.697: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 3 396s (process:1986): libfprint-SSM-DEBUG: 00:54:05.697: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 396s (process:1986): libfprint-SSM-DEBUG: 00:54:05.752: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 396s (process:1986): libfprint-SSM-DEBUG: 00:54:05.752: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 4 396s (process:1986): libfprint-elanspi-DEBUG: 00:54:05.752: stddev=558238d, ip=0, is_fp=2, is_empty=0 396s (process:1986): libfprint-elanspi-DEBUG: 00:54:05.753: diff = 342841 396s (process:1986): libfprint-SSM-DEBUG: 00:54:05.753: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 3 396s (process:1986): libfprint-SSM-DEBUG: 00:54:05.753: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 396s (process:1986): libfprint-SSM-DEBUG: 00:54:05.808: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 396s (process:1986): libfprint-SSM-DEBUG: 00:54:05.808: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 4 396s (process:1986): libfprint-elanspi-DEBUG: 00:54:05.808: stddev=572990d, ip=0, is_fp=2, is_empty=0 396s (process:1986): libfprint-elanspi-DEBUG: 00:54:05.809: diff = 352690 396s (process:1986): libfprint-SSM-DEBUG: 00:54:05.809: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 3 396s (process:1986): libfprint-SSM-DEBUG: 00:54:05.809: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 396s (process:1986): libfprint-SSM-DEBUG: 00:54:05.871: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 396s (process:1986): libfprint-SSM-DEBUG: 00:54:05.871: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 4 396s (process:1986): libfprint-elanspi-DEBUG: 00:54:05.871: stddev=575411d, ip=0, is_fp=2, is_empty=0 396s (process:1986): libfprint-elanspi-DEBUG: 00:54:05.872: diff = 365537 396s (process:1986): libfprint-SSM-DEBUG: 00:54:05.872: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 3 396s (process:1986): libfprint-SSM-DEBUG: 00:54:05.872: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 396s (process:1986): libfprint-SSM-DEBUG: 00:54:05.950: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 396s (process:1986): libfprint-SSM-DEBUG: 00:54:05.950: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 4 396s (process:1986): libfprint-elanspi-DEBUG: 00:54:05.951: stddev=578482d, ip=0, is_fp=2, is_empty=0 396s (process:1986): libfprint-elanspi-DEBUG: 00:54:05.951: diff = 342041 396s (process:1986): libfprint-SSM-DEBUG: 00:54:05.952: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 3 396s (process:1986): libfprint-SSM-DEBUG: 00:54:05.952: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 397s (process:1986): libfprint-SSM-DEBUG: 00:54:06.006: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 397s (process:1986): libfprint-SSM-DEBUG: 00:54:06.006: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 4 397s (process:1986): libfprint-elanspi-DEBUG: 00:54:06.007: stddev=572686d, ip=0, is_fp=2, is_empty=0 397s (process:1986): libfprint-elanspi-DEBUG: 00:54:06.007: diff = 421037 397s (process:1986): libfprint-SSM-DEBUG: 00:54:06.007: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 3 397s (process:1986): libfprint-SSM-DEBUG: 00:54:06.007: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 397s (process:1986): libfprint-SSM-DEBUG: 00:54:06.060: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 397s (process:1986): libfprint-SSM-DEBUG: 00:54:06.060: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 4 397s (process:1986): libfprint-elanspi-DEBUG: 00:54:06.060: stddev=465498d, ip=0, is_fp=2, is_empty=0 397s (process:1986): libfprint-elanspi-DEBUG: 00:54:06.061: diff = 404640 397s (process:1986): libfprint-SSM-DEBUG: 00:54:06.061: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 3 397s (process:1986): libfprint-SSM-DEBUG: 00:54:06.061: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 397s (process:1986): libfprint-SSM-DEBUG: 00:54:06.116: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 397s (process:1986): libfprint-SSM-DEBUG: 00:54:06.116: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 4 397s (process:1986): libfprint-elanspi-DEBUG: 00:54:06.117: stddev=410135d, ip=0, is_fp=2, is_empty=0 397s (process:1986): libfprint-elanspi-DEBUG: 00:54:06.118: diff = 347658 397s (process:1986): libfprint-SSM-DEBUG: 00:54:06.118: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 3 397s (process:1986): libfprint-SSM-DEBUG: 00:54:06.118: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 397s (process:1986): libfprint-SSM-DEBUG: 00:54:06.183: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 397s (process:1986): libfprint-SSM-DEBUG: 00:54:06.183: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 4 397s (process:1986): libfprint-elanspi-DEBUG: 00:54:06.183: stddev=493239d, ip=0, is_fp=2, is_empty=0 397s (process:1986): libfprint-elanspi-DEBUG: 00:54:06.184: diff = 344237 397s (process:1986): libfprint-SSM-DEBUG: 00:54:06.184: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 3 397s (process:1986): libfprint-SSM-DEBUG: 00:54:06.184: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 397s (process:1986): libfprint-SSM-DEBUG: 00:54:06.245: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 397s (process:1986): libfprint-SSM-DEBUG: 00:54:06.245: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 4 397s (process:1986): libfprint-elanspi-DEBUG: 00:54:06.246: stddev=553028d, ip=0, is_fp=2, is_empty=0 397s (process:1986): libfprint-elanspi-DEBUG: 00:54:06.247: diff = 419597 397s (process:1986): libfprint-SSM-DEBUG: 00:54:06.247: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 3 397s (process:1986): libfprint-SSM-DEBUG: 00:54:06.247: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 397s (process:1986): libfprint-SSM-DEBUG: 00:54:06.297: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 397s (process:1986): libfprint-SSM-DEBUG: 00:54:06.297: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 4 397s (process:1986): libfprint-elanspi-DEBUG: 00:54:06.297: stddev=574502d, ip=0, is_fp=2, is_empty=0 397s (process:1986): libfprint-elanspi-DEBUG: 00:54:06.298: diff = 408934 397s (process:1986): libfprint-SSM-DEBUG: 00:54:06.299: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 3 397s (process:1986): libfprint-SSM-DEBUG: 00:54:06.299: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 397s (process:1986): libfprint-SSM-DEBUG: 00:54:06.348: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 397s (process:1986): libfprint-SSM-DEBUG: 00:54:06.348: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 4 397s (process:1986): libfprint-elanspi-DEBUG: 00:54:06.349: stddev=645815d, ip=0, is_fp=2, is_empty=0 397s (process:1986): libfprint-elanspi-DEBUG: 00:54:06.349: diff = 409198 397s (process:1986): libfprint-SSM-DEBUG: 00:54:06.349: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 3 397s (process:1986): libfprint-SSM-DEBUG: 00:54:06.349: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 397s (process:1986): libfprint-SSM-DEBUG: 00:54:06.399: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 397s (process:1986): libfprint-SSM-DEBUG: 00:54:06.399: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 4 397s (process:1986): libfprint-elanspi-DEBUG: 00:54:06.400: stddev=677451d, ip=0, is_fp=2, is_empty=0 397s (process:1986): libfprint-elanspi-DEBUG: 00:54:06.401: diff = 429666 397s (process:1986): libfprint-SSM-DEBUG: 00:54:06.401: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 3 397s (process:1986): libfprint-SSM-DEBUG: 00:54:06.401: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 397s (process:1986): libfprint-SSM-DEBUG: 00:54:06.459: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 397s (process:1986): libfprint-SSM-DEBUG: 00:54:06.459: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 4 397s (process:1986): libfprint-elanspi-DEBUG: 00:54:06.460: stddev=634407d, ip=0, is_fp=2, is_empty=0 397s (process:1986): libfprint-elanspi-DEBUG: 00:54:06.460: have enough frames, exiting now 397s (process:1986): libfprint-assembling-DEBUG: 00:54:06.627: calc delta completed in 0.166971 secs 397s (process:1986): libfprint-assembling-DEBUG: 00:54:06.793: calc delta completed in 0.165976 secs 397s (process:1986): libfprint-assembling-DEBUG: 00:54:06.793: errors: 86516 rev: 170625 397s Executing: libfprint-2/driver-elanspi.test 397s (process:1986): libfprint-assembling-DEBUG: 00:54:06.958: calc delta completed in 0.165500 secs 397s (process:1986): libfprint-assembling-DEBUG: 00:54:06.958: height is 246 398s (process:1986): libfprint-image_device-DEBUG: 00:54:06.961: Image device captured an image 398s (process:1986): libfprint-image_device-DEBUG: 00:54:06.961: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 398s (process:1986): libfprint-device-DEBUG: 00:54:06.961: Device reported finger status change: FP_FINGER_STATUS_PRESENT 398s (process:1986): libfprint-SSM-DEBUG: 00:54:06.961: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 5 398s (process:1986): libfprint-SSM-DEBUG: 00:54:06.961: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 398s (process:1986): libfprint-image-DEBUG: 00:54:07.016: Minutiae scan completed in 0.055166 secs 398s (process:1986): libfprint-SSM-DEBUG: 00:54:07.018: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 398s (process:1986): libfprint-SSM-DEBUG: 00:54:07.018: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 6 398s (process:1986): libfprint-elanspi-DEBUG: 00:54:07.018: stddev=593525d, ip=0, is_fp=2, is_empty=0 398s (process:1986): libfprint-SSM-DEBUG: 00:54:07.018: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 5 398s (process:1986): libfprint-SSM-DEBUG: 00:54:07.018: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 398s (process:1986): libfprint-SSM-DEBUG: 00:54:07.088: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 398s (process:1986): libfprint-SSM-DEBUG: 00:54:07.088: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 6 398s (process:1986): libfprint-elanspi-DEBUG: 00:54:07.088: stddev=610651d, ip=0, is_fp=2, is_empty=0 398s (process:1986): libfprint-SSM-DEBUG: 00:54:07.088: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 5 398s (process:1986): libfprint-SSM-DEBUG: 00:54:07.088: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 398s (process:1986): libfprint-SSM-DEBUG: 00:54:07.149: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 398s (process:1986): libfprint-SSM-DEBUG: 00:54:07.149: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 6 398s (process:1986): libfprint-elanspi-DEBUG: 00:54:07.149: stddev=505673d, ip=0, is_fp=2, is_empty=0 398s (process:1986): libfprint-SSM-DEBUG: 00:54:07.149: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 5 398s (process:1986): libfprint-SSM-DEBUG: 00:54:07.149: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 398s (process:1986): libfprint-SSM-DEBUG: 00:54:07.216: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 398s (process:1986): libfprint-SSM-DEBUG: 00:54:07.216: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 6 398s (process:1986): libfprint-elanspi-DEBUG: 00:54:07.216: stddev=537580d, ip=0, is_fp=2, is_empty=0 398s (process:1986): libfprint-SSM-DEBUG: 00:54:07.216: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 5 398s (process:1986): libfprint-SSM-DEBUG: 00:54:07.216: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 398s (process:1986): libfprint-SSM-DEBUG: 00:54:07.277: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 398s (process:1986): libfprint-SSM-DEBUG: 00:54:07.277: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 6 398s (process:1986): libfprint-elanspi-DEBUG: 00:54:07.277: stddev=520750d, ip=0, is_fp=2, is_empty=0 398s (process:1986): libfprint-SSM-DEBUG: 00:54:07.277: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 5 398s (process:1986): libfprint-SSM-DEBUG: 00:54:07.277: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 398s (process:1986): libfprint-SSM-DEBUG: 00:54:07.336: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 398s (process:1986): libfprint-SSM-DEBUG: 00:54:07.336: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 6 398s (process:1986): libfprint-elanspi-DEBUG: 00:54:07.337: stddev=468008d, ip=0, is_fp=2, is_empty=0 398s (process:1986): libfprint-SSM-DEBUG: 00:54:07.337: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 5 398s (process:1986): libfprint-SSM-DEBUG: 00:54:07.337: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 398s (process:1986): libfprint-SSM-DEBUG: 00:54:07.392: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 398s (process:1986): libfprint-SSM-DEBUG: 00:54:07.392: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 6 398s (process:1986): libfprint-elanspi-DEBUG: 00:54:07.393: stddev=477058d, ip=0, is_fp=2, is_empty=0 398s (process:1986): libfprint-SSM-DEBUG: 00:54:07.393: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 5 398s (process:1986): libfprint-SSM-DEBUG: 00:54:07.393: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 398s (process:1986): libfprint-SSM-DEBUG: 00:54:07.453: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 398s (process:1986): libfprint-SSM-DEBUG: 00:54:07.453: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 6 398s (process:1986): libfprint-elanspi-DEBUG: 00:54:07.453: stddev=460178d, ip=0, is_fp=2, is_empty=0 398s (process:1986): libfprint-SSM-DEBUG: 00:54:07.453: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 5 398s (process:1986): libfprint-SSM-DEBUG: 00:54:07.453: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 398s (process:1986): libfprint-SSM-DEBUG: 00:54:07.511: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 398s (process:1986): libfprint-SSM-DEBUG: 00:54:07.511: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 6 398s (process:1986): libfprint-elanspi-DEBUG: 00:54:07.512: stddev=538508d, ip=0, is_fp=2, is_empty=0 398s (process:1986): libfprint-SSM-DEBUG: 00:54:07.512: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 5 398s (process:1986): libfprint-SSM-DEBUG: 00:54:07.512: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 398s (process:1986): libfprint-SSM-DEBUG: 00:54:07.573: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 398s (process:1986): libfprint-SSM-DEBUG: 00:54:07.573: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 6 398s (process:1986): libfprint-elanspi-DEBUG: 00:54:07.573: stddev=661673d, ip=0, is_fp=2, is_empty=0 398s (process:1986): libfprint-SSM-DEBUG: 00:54:07.573: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 5 398s (process:1986): libfprint-SSM-DEBUG: 00:54:07.573: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 398s (process:1986): libfprint-SSM-DEBUG: 00:54:07.632: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 398s (process:1986): libfprint-SSM-DEBUG: 00:54:07.632: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 6 398s (process:1986): libfprint-elanspi-DEBUG: 00:54:07.632: stddev=764706d, ip=0, is_fp=2, is_empty=0 398s (process:1986): libfprint-SSM-DEBUG: 00:54:07.632: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 5 398s (process:1986): libfprint-SSM-DEBUG: 00:54:07.632: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 398s (process:1986): libfprint-SSM-DEBUG: 00:54:07.732: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 398s (process:1986): libfprint-SSM-DEBUG: 00:54:07.732: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 6 398s (process:1986): libfprint-elanspi-DEBUG: 00:54:07.732: stddev=806415d, ip=0, is_fp=2, is_empty=0 398s (process:1986): libfprint-SSM-DEBUG: 00:54:07.732: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 5 398s (process:1986): libfprint-SSM-DEBUG: 00:54:07.732: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 398s (process:1986): libfprint-SSM-DEBUG: 00:54:07.793: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 398s (process:1986): libfprint-SSM-DEBUG: 00:54:07.793: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 6 398s (process:1986): libfprint-elanspi-DEBUG: 00:54:07.793: stddev=806649d, ip=0, is_fp=2, is_empty=0 398s (process:1986): libfprint-SSM-DEBUG: 00:54:07.793: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 5 398s (process:1986): libfprint-SSM-DEBUG: 00:54:07.793: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 398s (process:1986): libfprint-SSM-DEBUG: 00:54:07.855: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 398s (process:1986): libfprint-SSM-DEBUG: 00:54:07.855: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 6 398s (process:1986): libfprint-elanspi-DEBUG: 00:54:07.855: stddev=822567d, ip=0, is_fp=2, is_empty=0 398s (process:1986): libfprint-SSM-DEBUG: 00:54:07.855: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 5 398s (process:1986): libfprint-SSM-DEBUG: 00:54:07.855: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 398s (process:1986): libfprint-SSM-DEBUG: 00:54:07.913: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 398s (process:1986): libfprint-SSM-DEBUG: 00:54:07.913: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 6 398s (process:1986): libfprint-elanspi-DEBUG: 00:54:07.913: stddev=1017068d, ip=0, is_fp=2, is_empty=0 398s (process:1986): libfprint-SSM-DEBUG: 00:54:07.913: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 5 398s (process:1986): libfprint-SSM-DEBUG: 00:54:07.913: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 399s (process:1986): libfprint-SSM-DEBUG: 00:54:07.974: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 399s (process:1986): libfprint-SSM-DEBUG: 00:54:07.974: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 6 399s (process:1986): libfprint-elanspi-DEBUG: 00:54:07.975: stddev=1004196d, ip=0, is_fp=2, is_empty=0 399s (process:1986): libfprint-SSM-DEBUG: 00:54:07.975: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 5 399s (process:1986): libfprint-SSM-DEBUG: 00:54:07.975: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 399s (process:1986): libfprint-SSM-DEBUG: 00:54:08.042: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 399s (process:1986): libfprint-SSM-DEBUG: 00:54:08.042: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 6 399s (process:1986): libfprint-elanspi-DEBUG: 00:54:08.043: stddev=963655d, ip=0, is_fp=2, is_empty=0 399s (process:1986): libfprint-SSM-DEBUG: 00:54:08.043: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 5 399s (process:1986): libfprint-SSM-DEBUG: 00:54:08.043: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 399s (process:1986): libfprint-SSM-DEBUG: 00:54:08.101: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 399s (process:1986): libfprint-SSM-DEBUG: 00:54:08.101: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 6 399s (process:1986): libfprint-elanspi-DEBUG: 00:54:08.102: stddev=880521d, ip=0, is_fp=2, is_empty=0 399s (process:1986): libfprint-SSM-DEBUG: 00:54:08.102: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 5 399s (process:1986): libfprint-SSM-DEBUG: 00:54:08.102: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 399s (process:1986): libfprint-SSM-DEBUG: 00:54:08.157: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 399s (process:1986): libfprint-SSM-DEBUG: 00:54:08.157: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 6 399s (process:1986): libfprint-elanspi-DEBUG: 00:54:08.157: stddev=1135372d, ip=0, is_fp=2, is_empty=0 399s (process:1986): libfprint-SSM-DEBUG: 00:54:08.157: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 5 399s (process:1986): libfprint-SSM-DEBUG: 00:54:08.157: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 399s (process:1986): libfprint-SSM-DEBUG: 00:54:08.220: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 399s (process:1986): libfprint-SSM-DEBUG: 00:54:08.220: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 6 399s (process:1986): libfprint-elanspi-DEBUG: 00:54:08.220: stddev=1093450d, ip=3, is_fp=1, is_empty=0 399s (process:1986): libfprint-SSM-DEBUG: 00:54:08.220: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 5 399s (process:1986): libfprint-SSM-DEBUG: 00:54:08.220: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 399s (process:1986): libfprint-SSM-DEBUG: 00:54:08.277: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 399s (process:1986): libfprint-SSM-DEBUG: 00:54:08.278: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 6 399s (process:1986): libfprint-elanspi-DEBUG: 00:54:08.278: stddev=41090d, ip=8, is_fp=0, is_empty=2 399s (process:1986): libfprint-SSM-DEBUG: 00:54:08.278: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 5 399s (process:1986): libfprint-SSM-DEBUG: 00:54:08.278: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 399s (process:1986): libfprint-SSM-DEBUG: 00:54:08.329: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 399s (process:1986): libfprint-SSM-DEBUG: 00:54:08.329: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 6 399s (process:1986): libfprint-elanspi-DEBUG: 00:54:08.329: stddev=6836d, ip=13, is_fp=0, is_empty=2 399s (process:1986): libfprint-device-DEBUG: 00:54:08.329: Device reported finger status change: FP_FINGER_STATUS_NONE 399s (process:1986): libfprint-image_device-DEBUG: 00:54:08.329: Image device reported finger status: off 399s (process:1986): libfprint-image_device-DEBUG: 00:54:08.329: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 399s (process:1986): libfprint-image_device-DEBUG: 00:54:08.329: Deactivating image device 399s (process:1986): libfprint-image_device-DEBUG: 00:54:08.329: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_DEACTIVATING 399s (process:1986): libfprint-image_device-DEBUG: 00:54:08.329: Image device deactivation completed 399s (process:1986): libfprint-image_device-DEBUG: 00:54:08.329: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE 399s (process:1986): libfprint-device-DEBUG: 00:54:08.329: Device reported capture completion 399s (process:1986): libfprint-SSM-DEBUG: 00:54:08.329: [elanspi] ELANSPI_FPCAPT_NSTATES completed successfully 399s (process:1986): libfprint-device-DEBUG: 00:54:08.329: Completing action FPI_DEVICE_ACTION_CAPTURE in idle! 399s (process:1986): libfprint-device-DEBUG: 00:54:08.329: Updated temperature model after 5.01 seconds, ratio 0.27 -> 0.29, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 399s (process:1986): libfprint-image_device-DEBUG: 00:54:08.329: Image device close completed 399s (process:1986): libfprint-device-DEBUG: 00:54:08.329: Device reported close completion 399s (process:1986): libfprint-device-DEBUG: 00:54:08.329: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 399s (process:1986): libfprint-device-DEBUG: 00:54:08.329: Updated temperature model after 0.00 seconds, ratio 0.29 -> 0.29, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 399s ** (umockdev-run:1982): DEBUG: 00:54:08.598: umockdev.vala:154: Removing test bed /tmp/umockdev.GTWL22 399s (umockdev-run:1982): GLib-DEBUG: 00:54:08.609: unsetenv() is not thread-safe and should not be used after threads are created 399s Comparing PNGs /tmp/libfprint-umockdev-test-kt5uejjw/capture.png and /usr/share/installed-tests/libfprint-2/elanspi/capture.png 399s PASS: libfprint-2/driver-elanspi.test 399s Running test: libfprint-2/driver-realtek.test 399s ** (umockdev-run:1996): DEBUG: 00:54:08.732: umockdev.vala:127: Created udev test bed /tmp/umockdev.JFWD22 399s ** (umockdev-run:1996): DEBUG: 00:54:08.732: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0/usb1/1-8 399s ** (umockdev-run:1996): DEBUG: 00:54:08.734: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0/usb1/1-8 (subsystem usb) 399s ** (umockdev-run:1996): DEBUG: 00:54:08.739: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.JFWD22/dev/bus/usb/001/025 399s ** (umockdev-run:1996): DEBUG: 00:54:08.739: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0/usb1 399s ** (umockdev-run:1996): DEBUG: 00:54:08.741: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0/usb1 (subsystem usb) 399s ** (umockdev-run:1996): DEBUG: 00:54:08.745: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.JFWD22/dev/bus/usb/001/001 399s ** (umockdev-run:1996): DEBUG: 00:54:08.745: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0 399s ** (umockdev-run:1996): DEBUG: 00:54:08.745: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0 (subsystem pci) 399s (process:2000): libfprint-context-DEBUG: 00:54:08.856: Initializing FpContext (libfprint version 1.94.8+tod1) 399s (process:2000): libfprint-tod-DEBUG: 00:54:08.856: Impossible to load the shared drivers dir Error opening directory “/usr/lib/arm-linux-gnueabihf/libfprint-2/tod-1”: No such file or directory 399s (process:2000): libfprint-context-DEBUG: 00:54:08.860: No driver found for USB device 1D6B:0002 399s (process:2000): libfprint-realtek-DEBUG: 00:54:08.860: 7399816921478: ../libfprint/drivers/realtek/realtek.c:1225 399s (process:2000): libfprint-realtek-DEBUG: 00:54:08.863: Device name: Realtek USB2.0 Finger Print Bridge 399s (process:2000): libfprint-device-DEBUG: 00:54:08.863: Device reported probe completion 399s (process:2000): libfprint-device-DEBUG: 00:54:08.863: Completing action FPI_DEVICE_ACTION_PROBE in idle! 399s (process:2000): libfprint-device-DEBUG: 00:54:08.863: Not updating temperature model, device can run continuously! 399s (process:2000): libfprint-realtek-DEBUG: 00:54:08.865: 7399816926032: ../libfprint/drivers/realtek/realtek.c:1270 399s (process:2000): libfprint-SSM-DEBUG: 00:54:08.865: [realtek] Init entering state 0 399s (process:2000): libfprint-SSM-DEBUG: 00:54:08.866: [realtek] Init entering state 1 399s (process:2000): libfprint-SSM-DEBUG: 00:54:08.866: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 399s (process:2000): libfprint-SSM-DEBUG: 00:54:08.866: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 399s (process:2000): libfprint-SSM-DEBUG: 00:54:08.866: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 399s (process:2000): libfprint-SSM-DEBUG: 00:54:08.867: [realtek] Init entering state 2 399s (process:2000): libfprint-SSM-DEBUG: 00:54:08.867: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 399s (process:2000): libfprint-SSM-DEBUG: 00:54:08.867: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 399s (process:2000): libfprint-SSM-DEBUG: 00:54:08.868: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 399s (process:2000): libfprint-SSM-DEBUG: 00:54:08.868: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 399s (process:2000): libfprint-SSM-DEBUG: 00:54:08.869: [realtek] Init completed successfully 399s (process:2000): libfprint-realtek-DEBUG: 00:54:08.869: Init complete! 399s (process:2000): libfprint-device-DEBUG: 00:54:08.869: Device reported open completion 399s (process:2000): libfprint-SSM-DEBUG: 00:54:08.869: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 399s (process:2000): libfprint-device-DEBUG: 00:54:08.869: Completing action FPI_DEVICE_ACTION_OPEN in idle! 399s (process:2000): libfprint-device-DEBUG: 00:54:08.869: Not updating temperature model, device can run continuously! 399s (process:2000): libfprint-realtek-DEBUG: 00:54:08.869: 7399816930599: ../libfprint/drivers/realtek/realtek.c:1333 399s (process:2000): libfprint-SSM-DEBUG: 00:54:08.869: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 399s (process:2000): libfprint-SSM-DEBUG: 00:54:08.870: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 399s (process:2000): libfprint-SSM-DEBUG: 00:54:08.870: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 399s (process:2000): libfprint-realtek-DEBUG: 00:54:08.870: Successfully cleared storage 399s (process:2000): libfprint-device-DEBUG: 00:54:08.870: Device reported deletion completion 399s (process:2000): libfprint-SSM-DEBUG: 00:54:08.870: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 399s (process:2000): libfprint-device-DEBUG: 00:54:08.870: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 399s (process:2000): libfprint-device-DEBUG: 00:54:08.870: Not updating temperature model, device can run continuously! 399s (process:2000): libfprint-device-DEBUG: 00:54:08.871: Not updating temperature model, device can run continuously! 399s (process:2000): libfprint-realtek-DEBUG: 00:54:08.872: 7399816932979: ../libfprint/drivers/realtek/realtek.c:1202 399s (process:2000): libfprint-SSM-DEBUG: 00:54:08.872: [realtek] Enroll entering state 0 399s (process:2000): libfprint-SSM-DEBUG: 00:54:08.872: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 399s (process:2000): libfprint-SSM-DEBUG: 00:54:08.872: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 399s (process:2000): libfprint-SSM-DEBUG: 00:54:08.873: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 399s (process:2000): libfprint-SSM-DEBUG: 00:54:08.873: [realtek] Enroll entering state 1 399s (process:2000): libfprint-SSM-DEBUG: 00:54:08.873: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 399s (process:2000): libfprint-SSM-DEBUG: 00:54:08.874: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 399s (process:2000): libfprint-SSM-DEBUG: 00:54:08.874: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 399s (process:2000): libfprint-SSM-DEBUG: 00:54:08.874: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 399s (process:2000): libfprint-SSM-DEBUG: 00:54:08.875: [realtek] Enroll entering state 2 399s (process:2000): libfprint-device-DEBUG: 00:54:08.875: Device reported finger status change: FP_FINGER_STATUS_NEEDED 399s (process:2000): libfprint-SSM-DEBUG: 00:54:08.875: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 399s (process:2000): libfprint-SSM-DEBUG: 00:54:08.875: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 399s (process:2000): libfprint-SSM-DEBUG: 00:54:08.875: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 399s (process:2000): libfprint-SSM-DEBUG: 00:54:08.875: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 399s (process:2000): libfprint-SSM-DEBUG: 00:54:08.876: [realtek] Enroll entering state 3 399s (process:2000): libfprint-SSM-DEBUG: 00:54:08.876: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 399s (process:2000): libfprint-SSM-DEBUG: 00:54:08.876: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 399s (process:2000): libfprint-SSM-DEBUG: 00:54:08.876: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 399s (process:2000): libfprint-SSM-DEBUG: 00:54:08.880: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 399s (process:2000): libfprint-device-DEBUG: 00:54:08.881: Device reported finger status change: FP_FINGER_STATUS_PRESENT 399s (process:2000): libfprint-SSM-DEBUG: 00:54:08.881: [realtek] Enroll entering state 4 399s (process:2000): libfprint-SSM-DEBUG: 00:54:08.881: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 399s (process:2000): libfprint-SSM-DEBUG: 00:54:08.881: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 399s (process:2000): libfprint-SSM-DEBUG: 00:54:08.881: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 399s (process:2000): libfprint-SSM-DEBUG: 00:54:08.882: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 399s (process:2000): libfprint-device-DEBUG: 00:54:08.882: Device reported finger status change: FP_FINGER_STATUS_NONE 399s (process:2000): libfprint-device-DEBUG: 00:54:08.882: Device reported enroll progress, reported 1 of 8 have been completed 399s (process:2000): libfprint-SSM-DEBUG: 00:54:08.882: [realtek] Enroll entering state 2 399s (process:2000): libfprint-device-DEBUG: 00:54:08.882: Device reported finger status change: FP_FINGER_STATUS_NEEDED 399s (process:2000): libfprint-SSM-DEBUG: 00:54:08.882: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 399s (process:2000): libfprint-SSM-DEBUG: 00:54:08.883: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 399s (process:2000): libfprint-SSM-DEBUG: 00:54:08.883: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 399s (process:2000): libfprint-SSM-DEBUG: 00:54:08.883: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 399s (process:2000): libfprint-SSM-DEBUG: 00:54:08.884: [realtek] Enroll entering state 3 399s (process:2000): libfprint-SSM-DEBUG: 00:54:08.884: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 399s (process:2000): libfprint-SSM-DEBUG: 00:54:08.884: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 399s (process:2000): libfprint-SSM-DEBUG: 00:54:08.884: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 399s (process:2000): libfprint-SSM-DEBUG: 00:54:08.885: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 399s (process:2000): libfprint-device-DEBUG: 00:54:08.885: Device reported finger status change: FP_FINGER_STATUS_PRESENT 399s (process:2000): libfprint-SSM-DEBUG: 00:54:08.885: [realtek] Enroll entering state 4 399s (process:2000): libfprint-SSM-DEBUG: 00:54:08.885: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 399s (process:2000): libfprint-SSM-DEBUG: 00:54:08.886: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 399s (process:2000): libfprint-SSM-DEBUG: 00:54:08.886: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 399s (process:2000): libfprint-SSM-DEBUG: 00:54:08.887: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 399s (process:2000): libfprint-device-DEBUG: 00:54:08.887: Device reported finger status change: FP_FINGER_STATUS_NONE 399s (process:2000): libfprint-device-DEBUG: 00:54:08.887: Device reported enroll progress, reported 2 of 8 have been completed 399s (process:2000): libfprint-SSM-DEBUG: 00:54:08.887: [realtek] Enroll entering state 2 399s (process:2000): libfprint-device-DEBUG: 00:54:08.887: Device reported finger status change: FP_FINGER_STATUS_NEEDED 399s (process:2000): libfprint-SSM-DEBUG: 00:54:08.887: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 399s (process:2000): libfprint-SSM-DEBUG: 00:54:08.888: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 399s (process:2000): libfprint-SSM-DEBUG: 00:54:08.888: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 399s (process:2000): libfprint-SSM-DEBUG: 00:54:08.888: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 399s (process:2000): libfprint-SSM-DEBUG: 00:54:08.888: [realtek] Enroll entering state 3 399s (process:2000): libfprint-SSM-DEBUG: 00:54:08.888: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 399s (process:2000): libfprint-SSM-DEBUG: 00:54:08.889: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 399s (process:2000): libfprint-SSM-DEBUG: 00:54:08.889: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 399s (process:2000): libfprint-SSM-DEBUG: 00:54:08.889: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 399s (process:2000): libfprint-device-DEBUG: 00:54:08.890: Device reported finger status change: FP_FINGER_STATUS_PRESENT 399s (process:2000): libfprint-SSM-DEBUG: 00:54:08.890: [realtek] Enroll entering state 4 399s (process:2000): libfprint-SSM-DEBUG: 00:54:08.890: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 399s (process:2000): libfprint-SSM-DEBUG: 00:54:08.890: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 399s (process:2000): libfprint-SSM-DEBUG: 00:54:08.891: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 399s (process:2000): libfprint-SSM-DEBUG: 00:54:08.891: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 399s (process:2000): libfprint-device-DEBUG: 00:54:08.892: Device reported finger status change: FP_FINGER_STATUS_NONE 399s (process:2000): libfprint-device-DEBUG: 00:54:08.892: Device reported enroll progress, reported 3 of 8 have been completed 399s (process:2000): libfprint-SSM-DEBUG: 00:54:08.892: [realtek] Enroll entering state 2 399s (process:2000): libfprint-device-DEBUG: 00:54:08.892: Device reported finger status change: FP_FINGER_STATUS_NEEDED 399s (process:2000): libfprint-SSM-DEBUG: 00:54:08.892: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 399s (process:2000): libfprint-SSM-DEBUG: 00:54:08.892: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 399s (process:2000): libfprint-SSM-DEBUG: 00:54:08.892: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 399s (process:2000): libfprint-SSM-DEBUG: 00:54:08.892: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 399s (process:2000): libfprint-SSM-DEBUG: 00:54:08.893: [realtek] Enroll entering state 3 399s (process:2000): libfprint-SSM-DEBUG: 00:54:08.893: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 399s (process:2000): libfprint-SSM-DEBUG: 00:54:08.893: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 399s (process:2000): libfprint-SSM-DEBUG: 00:54:08.893: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 399s (process:2000): libfprint-SSM-DEBUG: 00:54:08.894: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 399s (process:2000): libfprint-device-DEBUG: 00:54:08.895: Device reported finger status change: FP_FINGER_STATUS_PRESENT 399s (process:2000): libfprint-SSM-DEBUG: 00:54:08.895: [realtek] Enroll entering state 4 399s (process:2000): libfprint-SSM-DEBUG: 00:54:08.895: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 399s (process:2000): libfprint-SSM-DEBUG: 00:54:08.895: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 399s (process:2000): libfprint-SSM-DEBUG: 00:54:08.895: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 399s (process:2000): libfprint-SSM-DEBUG: 00:54:08.896: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 399s (process:2000): libfprint-device-DEBUG: 00:54:08.896: Device reported finger status change: FP_FINGER_STATUS_NONE 399s (process:2000): libfprint-device-DEBUG: 00:54:08.897: Device reported enroll progress, reported 4 of 8 have been completed 399s (process:2000): libfprint-SSM-DEBUG: 00:54:08.897: [realtek] Enroll entering state 2 399s (process:2000): libfprint-device-DEBUG: 00:54:08.897: Device reported finger status change: FP_FINGER_STATUS_NEEDED 399s (process:2000): libfprint-SSM-DEBUG: 00:54:08.897: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 399s (process:2000): libfprint-SSM-DEBUG: 00:54:08.897: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 399s (process:2000): libfprint-SSM-DEBUG: 00:54:08.897: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 399s (process:2000): libfprint-SSM-DEBUG: 00:54:08.897: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 399s (process:2000): libfprint-SSM-DEBUG: 00:54:08.898: [realtek] Enroll entering state 3 399s (process:2000): libfprint-SSM-DEBUG: 00:54:08.898: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 399s (process:2000): libfprint-SSM-DEBUG: 00:54:08.898: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 399s (process:2000): libfprint-SSM-DEBUG: 00:54:08.898: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 399s (process:2000): libfprint-SSM-DEBUG: 00:54:08.899: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 399s (process:2000): libfprint-device-DEBUG: 00:54:08.899: Device reported finger status change: FP_FINGER_STATUS_PRESENT 399s (process:2000): libfprint-SSM-DEBUG: 00:54:08.899: [realtek] Enroll entering state 4 399s (process:2000): libfprint-SSM-DEBUG: 00:54:08.899: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 399s (process:2000): libfprint-SSM-DEBUG: 00:54:08.900: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 399s (process:2000): libfprint-SSM-DEBUG: 00:54:08.900: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 399s (process:2000): libfprint-SSM-DEBUG: 00:54:08.900: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 399s (process:2000): libfprint-device-DEBUG: 00:54:08.901: Device reported finger status change: FP_FINGER_STATUS_NONE 399s (process:2000): libfprint-device-DEBUG: 00:54:08.901: Device reported enroll progress, reported 5 of 8 have been completed 399s (process:2000): libfprint-SSM-DEBUG: 00:54:08.901: [realtek] Enroll entering state 2 399s (process:2000): libfprint-device-DEBUG: 00:54:08.901: Device reported finger status change: FP_FINGER_STATUS_NEEDED 399s (process:2000): libfprint-SSM-DEBUG: 00:54:08.901: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 399s (process:2000): libfprint-SSM-DEBUG: 00:54:08.901: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 399s (process:2000): libfprint-SSM-DEBUG: 00:54:08.901: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 399s (process:2000): libfprint-SSM-DEBUG: 00:54:08.901: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 399s (process:2000): libfprint-SSM-DEBUG: 00:54:08.902: [realtek] Enroll entering state 3 399s (process:2000): libfprint-SSM-DEBUG: 00:54:08.902: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 399s (process:2000): libfprint-SSM-DEBUG: 00:54:08.902: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 399s (process:2000): libfprint-SSM-DEBUG: 00:54:08.902: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 399s (process:2000): libfprint-SSM-DEBUG: 00:54:08.903: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 399s (process:2000): libfprint-device-DEBUG: 00:54:08.903: Device reported finger status change: FP_FINGER_STATUS_PRESENT 399s (process:2000): libfprint-SSM-DEBUG: 00:54:08.903: [realtek] Enroll entering state 4 399s (process:2000): libfprint-SSM-DEBUG: 00:54:08.903: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 399s (process:2000): libfprint-SSM-DEBUG: 00:54:08.904: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 399s (process:2000): libfprint-SSM-DEBUG: 00:54:08.904: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 399s (process:2000): libfprint-SSM-DEBUG: 00:54:08.905: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 399s (process:2000): libfprint-device-DEBUG: 00:54:08.905: Device reported finger status change: FP_FINGER_STATUS_NONE 399s (process:2000): libfprint-device-DEBUG: 00:54:08.905: Device reported enroll progress, reported 6 of 8 have been completed 399s (process:2000): libfprint-SSM-DEBUG: 00:54:08.905: [realtek] Enroll entering state 2 399s (process:2000): libfprint-device-DEBUG: 00:54:08.905: Device reported finger status change: FP_FINGER_STATUS_NEEDED 399s (process:2000): libfprint-SSM-DEBUG: 00:54:08.905: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 399s (process:2000): libfprint-SSM-DEBUG: 00:54:08.905: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 399s (process:2000): libfprint-SSM-DEBUG: 00:54:08.906: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 399s (process:2000): libfprint-SSM-DEBUG: 00:54:08.906: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 399s (process:2000): libfprint-SSM-DEBUG: 00:54:08.906: [realtek] Enroll entering state 3 399s (process:2000): libfprint-SSM-DEBUG: 00:54:08.906: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 399s (process:2000): libfprint-SSM-DEBUG: 00:54:08.906: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 399s (process:2000): libfprint-SSM-DEBUG: 00:54:08.907: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 399s (process:2000): libfprint-SSM-DEBUG: 00:54:08.907: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 399s (process:2000): libfprint-device-DEBUG: 00:54:08.908: Device reported finger status change: FP_FINGER_STATUS_PRESENT 399s (process:2000): libfprint-SSM-DEBUG: 00:54:08.908: [realtek] Enroll entering state 4 399s (process:2000): libfprint-SSM-DEBUG: 00:54:08.908: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 399s (process:2000): libfprint-SSM-DEBUG: 00:54:08.908: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 399s (process:2000): libfprint-SSM-DEBUG: 00:54:08.908: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 399s (process:2000): libfprint-SSM-DEBUG: 00:54:08.909: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 399s (process:2000): libfprint-device-DEBUG: 00:54:08.909: Device reported finger status change: FP_FINGER_STATUS_NONE 399s (process:2000): libfprint-device-DEBUG: 00:54:08.909: Device reported enroll progress, reported 7 of 8 have been completed 399s (process:2000): libfprint-SSM-DEBUG: 00:54:08.909: [realtek] Enroll entering state 2 399s (process:2000): libfprint-device-DEBUG: 00:54:08.909: Device reported finger status change: FP_FINGER_STATUS_NEEDED 399s (process:2000): libfprint-SSM-DEBUG: 00:54:08.909: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 399s (process:2000): libfprint-SSM-DEBUG: 00:54:08.910: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 399s (process:2000): libfprint-SSM-DEBUG: 00:54:08.910: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 399s (process:2000): libfprint-SSM-DEBUG: 00:54:08.910: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 399s (process:2000): libfprint-SSM-DEBUG: 00:54:08.910: [realtek] Enroll entering state 3 399s (process:2000): libfprint-SSM-DEBUG: 00:54:08.910: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 399s (process:2000): libfprint-SSM-DEBUG: 00:54:08.911: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 399s (process:2000): libfprint-SSM-DEBUG: 00:54:08.911: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 399s (process:2000): libfprint-SSM-DEBUG: 00:54:08.912: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 399s (process:2000): libfprint-device-DEBUG: 00:54:08.912: Device reported finger status change: FP_FINGER_STATUS_PRESENT 399s (process:2000): libfprint-SSM-DEBUG: 00:54:08.912: [realtek] Enroll entering state 4 399s (process:2000): libfprint-SSM-DEBUG: 00:54:08.912: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 399s (process:2000): libfprint-SSM-DEBUG: 00:54:08.912: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 399s (process:2000): libfprint-SSM-DEBUG: 00:54:08.913: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 399s (process:2000): libfprint-SSM-DEBUG: 00:54:08.913: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 399s (process:2000): libfprint-device-DEBUG: 00:54:08.914: Device reported finger status change: FP_FINGER_STATUS_NONE 399s (process:2000): libfprint-device-DEBUG: 00:54:08.914: Device reported enroll progress, reported 8 of 8 have been completed 399s (process:2000): libfprint-SSM-DEBUG: 00:54:08.914: [realtek] Enroll entering state 2 399s (process:2000): libfprint-device-DEBUG: 00:54:08.914: Device reported finger status change: FP_FINGER_STATUS_NEEDED 399s (process:2000): libfprint-SSM-DEBUG: 00:54:08.914: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 399s (process:2000): libfprint-SSM-DEBUG: 00:54:08.914: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 399s (process:2000): libfprint-SSM-DEBUG: 00:54:08.915: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 399s (process:2000): libfprint-SSM-DEBUG: 00:54:08.915: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 399s (process:2000): libfprint-SSM-DEBUG: 00:54:08.915: [realtek] Enroll entering state 3 399s (process:2000): libfprint-SSM-DEBUG: 00:54:08.915: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 399s (process:2000): libfprint-SSM-DEBUG: 00:54:08.915: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 399s (process:2000): libfprint-SSM-DEBUG: 00:54:08.916: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 399s (process:2000): libfprint-SSM-DEBUG: 00:54:08.916: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 399s (process:2000): libfprint-device-DEBUG: 00:54:08.917: Device reported finger status change: FP_FINGER_STATUS_PRESENT 399s (process:2000): libfprint-SSM-DEBUG: 00:54:08.917: [realtek] Enroll entering state 4 399s (process:2000): libfprint-SSM-DEBUG: 00:54:08.917: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 399s (process:2000): libfprint-SSM-DEBUG: 00:54:08.917: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 399s (process:2000): libfprint-SSM-DEBUG: 00:54:08.917: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 399s (process:2000): libfprint-SSM-DEBUG: 00:54:08.918: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 399s (process:2000): libfprint-device-DEBUG: 00:54:08.918: Device reported finger status change: FP_FINGER_STATUS_NONE 399s (process:2000): libfprint-SSM-DEBUG: 00:54:08.918: [realtek] Enroll entering state 5 399s (process:2000): libfprint-SSM-DEBUG: 00:54:08.918: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 399s (process:2000): libfprint-SSM-DEBUG: 00:54:08.919: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 399s (process:2000): libfprint-SSM-DEBUG: 00:54:08.919: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 399s (process:2000): libfprint-SSM-DEBUG: 00:54:08.919: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 399s (process:2000): libfprint-SSM-DEBUG: 00:54:08.920: [realtek] Enroll entering state 6 399s (process:2000): libfprint-realtek-DEBUG: 00:54:08.920: user_id: FP1-00000000-0-00000000-nobody, finger: 0xff 399s (process:2000): libfprint-SSM-DEBUG: 00:54:08.920: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 399s (process:2000): libfprint-SSM-DEBUG: 00:54:08.920: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 399s (process:2000): libfprint-SSM-DEBUG: 00:54:08.921: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 399s (process:2000): libfprint-SSM-DEBUG: 00:54:08.921: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 399s (process:2000): libfprint-SSM-DEBUG: 00:54:08.922: [realtek] Enroll completed successfully 399s (process:2000): libfprint-realtek-DEBUG: 00:54:08.922: Enrollment complete! 399s (process:2000): libfprint-device-DEBUG: 00:54:08.922: Device reported enroll completion 399s (process:2000): libfprint-device-DEBUG: 00:54:08.922: Print for finger FP_FINGER_UNKNOWN enrolled 399s (process:2000): libfprint-SSM-DEBUG: 00:54:08.922: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 399s (process:2000): libfprint-device-DEBUG: 00:54:08.922: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 399s (process:2000): libfprint-device-DEBUG: 00:54:08.922: Not updating temperature model, device can run continuously! 399s (process:2000): libfprint-realtek-DEBUG: 00:54:08.922: 7399816983271: ../libfprint/drivers/realtek/realtek.c:1345 399s (process:2000): libfprint-SSM-DEBUG: 00:54:08.922: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 399s (process:2000): libfprint-SSM-DEBUG: 00:54:08.922: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 399s (process:2000): libfprint-SSM-DEBUG: 00:54:08.923: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 399s (process:2000): libfprint-realtek-DEBUG: 00:54:08.923: Query templates complete! 399s (process:2000): libfprint-device-DEBUG: 00:54:08.923: Device reported listing completion 399s (process:2000): libfprint-SSM-DEBUG: 00:54:08.923: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 399s (process:2000): libfprint-device-DEBUG: 00:54:08.923: Completing action FPI_DEVICE_ACTION_LIST in idle! 399s (process:2000): libfprint-device-DEBUG: 00:54:08.923: Not updating temperature model, device can run continuously! 399s (process:2000): libfprint-device-DEBUG: 00:54:08.924: Not updating temperature model, device can run continuously! 399s (process:2000): libfprint-realtek-DEBUG: 00:54:08.924: 7399816985053: ../libfprint/drivers/realtek/realtek.c:1178 399s (process:2000): libfprint-SSM-DEBUG: 00:54:08.924: [realtek] Verify & Identify entering state 0 399s (process:2000): libfprint-SSM-DEBUG: 00:54:08.924: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 399s (process:2000): libfprint-SSM-DEBUG: 00:54:08.924: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 399s (process:2000): libfprint-SSM-DEBUG: 00:54:08.925: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 399s (process:2000): libfprint-SSM-DEBUG: 00:54:08.925: [realtek] Verify & Identify entering state 1 399s (process:2000): libfprint-device-DEBUG: 00:54:08.925: Device reported finger status change: FP_FINGER_STATUS_NEEDED 399s (process:2000): libfprint-SSM-DEBUG: 00:54:08.925: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 399s (process:2000): libfprint-SSM-DEBUG: 00:54:08.925: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 399s (process:2000): libfprint-SSM-DEBUG: 00:54:08.926: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 399s (process:2000): libfprint-SSM-DEBUG: 00:54:08.926: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 399s (process:2000): libfprint-SSM-DEBUG: 00:54:08.926: [realtek] Verify & Identify entering state 2 399s (process:2000): libfprint-SSM-DEBUG: 00:54:08.926: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 399s (process:2000): libfprint-SSM-DEBUG: 00:54:08.926: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 399s (process:2000): libfprint-SSM-DEBUG: 00:54:08.927: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 399s (process:2000): libfprint-SSM-DEBUG: 00:54:08.927: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 399s (process:2000): libfprint-device-DEBUG: 00:54:08.927: Device reported finger status change: FP_FINGER_STATUS_PRESENT 399s (process:2000): libfprint-SSM-DEBUG: 00:54:08.928: [realtek] Verify & Identify entering state 3 399s (process:2000): libfprint-SSM-DEBUG: 00:54:08.928: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 399s (process:2000): libfprint-SSM-DEBUG: 00:54:08.928: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 399s (process:2000): libfprint-SSM-DEBUG: 00:54:08.928: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 399s (process:2000): libfprint-SSM-DEBUG: 00:54:08.928: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 399s (process:2000): libfprint-device-DEBUG: 00:54:08.929: Device reported finger status change: FP_FINGER_STATUS_NONE 399s (process:2000): libfprint-SSM-DEBUG: 00:54:08.929: [realtek] Verify & Identify entering state 4 399s (process:2000): libfprint-SSM-DEBUG: 00:54:08.929: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 399s (process:2000): libfprint-SSM-DEBUG: 00:54:08.929: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 399s (process:2000): libfprint-SSM-DEBUG: 00:54:08.930: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 399s (process:2000): libfprint-SSM-DEBUG: 00:54:08.930: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 399s (process:2000): libfprint-device-DEBUG: 00:54:08.931: Device reported verify result 399s (process:2000): libfprint-SSM-DEBUG: 00:54:08.931: [realtek] Verify & Identify entering state 5 399s (process:2000): libfprint-SSM-DEBUG: 00:54:08.931: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 399s (process:2000): libfprint-SSM-DEBUG: 00:54:08.931: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 399s (process:2000): libfprint-SSM-DEBUG: 00:54:08.931: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 399s (process:2000): libfprint-SSM-DEBUG: 00:54:08.931: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 399s (process:2000): libfprint-SSM-DEBUG: 00:54:08.932: [realtek] Verify & Identify completed successfully 399s (process:2000): libfprint-realtek-DEBUG: 00:54:08.932: Verify complete! 399s (process:2000): libfprint-device-DEBUG: 00:54:08.932: Device reported verify completion 399s (process:2000): libfprint-SSM-DEBUG: 00:54:08.932: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 399s (process:2000): libfprint-device-DEBUG: 00:54:08.932: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 399s (process:2000): libfprint-device-DEBUG: 00:54:08.932: Not updating temperature model, device can run continuously! 399s (process:2000): libfprint-device-DEBUG: 00:54:08.932: Not updating temperature model, device can run continuously! 399s (process:2000): libfprint-realtek-DEBUG: 00:54:08.932: 7399816993683: ../libfprint/drivers/realtek/realtek.c:1178 399s (process:2000): libfprint-SSM-DEBUG: 00:54:08.932: [realtek] Verify & Identify entering state 0 399s (process:2000): libfprint-SSM-DEBUG: 00:54:08.932: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 399s (process:2000): libfprint-SSM-DEBUG: 00:54:08.933: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 399s (process:2000): libfprint-SSM-DEBUG: 00:54:08.933: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 399s (process:2000): libfprint-SSM-DEBUG: 00:54:08.934: [realtek] Verify & Identify entering state 1 399s (process:2000): libfprint-device-DEBUG: 00:54:08.934: Device reported finger status change: FP_FINGER_STATUS_NEEDED 399s (process:2000): libfprint-SSM-DEBUG: 00:54:08.934: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 399s (process:2000): libfprint-SSM-DEBUG: 00:54:08.934: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 399s (process:2000): libfprint-SSM-DEBUG: 00:54:08.934: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 399s (process:2000): libfprint-SSM-DEBUG: 00:54:08.934: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 399s (process:2000): libfprint-SSM-DEBUG: 00:54:08.935: [realtek] Verify & Identify entering state 2 399s (process:2000): libfprint-SSM-DEBUG: 00:54:08.935: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 399s (process:2000): libfprint-SSM-DEBUG: 00:54:08.935: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 399s (process:2000): libfprint-SSM-DEBUG: 00:54:08.935: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 399s (process:2000): libfprint-SSM-DEBUG: 00:54:08.936: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 399s (process:2000): libfprint-device-DEBUG: 00:54:08.936: Device reported finger status change: FP_FINGER_STATUS_PRESENT 399s (process:2000): libfprint-SSM-DEBUG: 00:54:08.936: [realtek] Verify & Identify entering state 3 399s (process:2000): libfprint-SSM-DEBUG: 00:54:08.936: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 399s (process:2000): libfprint-SSM-DEBUG: 00:54:08.936: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 399s (process:2000): libfprint-SSM-DEBUG: 00:54:08.936: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 399s (process:2000): libfprint-SSM-DEBUG: 00:54:08.937: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 399s (process:2000): libfprint-device-DEBUG: 00:54:08.937: Device reported finger status change: FP_FINGER_STATUS_NONE 399s (process:2000): libfprint-SSM-DEBUG: 00:54:08.937: [realtek] Verify & Identify entering state 4 399s (process:2000): libfprint-SSM-DEBUG: 00:54:08.937: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 399s (process:2000): libfprint-SSM-DEBUG: 00:54:08.938: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 399s (process:2000): libfprint-SSM-DEBUG: 00:54:08.938: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 399s (process:2000): libfprint-SSM-DEBUG: 00:54:08.938: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 399s (process:2000): libfprint-device-DEBUG: 00:54:08.939: Device reported identify result 399s (process:2000): libfprint-SSM-DEBUG: 00:54:08.939: [realtek] Verify & Identify completed successfully 399s (process:2000): libfprint-realtek-DEBUG: 00:54:08.939: Verify complete! 399s (process:2000): libfprint-device-DEBUG: 00:54:08.939: Device reported identify completion 399s (process:2000): libfprint-SSM-DEBUG: 00:54:08.939: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 399s (process:2000): libfprint-device-DEBUG: 00:54:08.939: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 399s (process:2000): libfprint-device-DEBUG: 00:54:08.939: Not updating temperature model, device can run continuously! 399s (process:2000): libfprint-realtek-DEBUG: 00:54:08.939: 7399817000789: ../libfprint/drivers/realtek/realtek.c:1314 399s (process:2000): libfprint-SSM-DEBUG: 00:54:08.939: [realtek] Delete print entering state 0 399s (process:2000): libfprint-SSM-DEBUG: 00:54:08.939: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 399s (process:2000): libfprint-SSM-DEBUG: 00:54:08.940: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 399s (process:2000): libfprint-SSM-DEBUG: 00:54:08.940: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 399s (process:2000): libfprint-SSM-DEBUG: 00:54:08.941: [realtek] Delete print entering state 1 399s (process:2000): libfprint-SSM-DEBUG: 00:54:08.941: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 399s (process:2000): libfprint-SSM-DEBUG: 00:54:08.941: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 399s (process:2000): libfprint-SSM-DEBUG: 00:54:08.941: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 399s (process:2000): libfprint-SSM-DEBUG: 00:54:08.941: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 399s (process:2000): libfprint-SSM-DEBUG: 00:54:08.942: [realtek] Delete print completed successfully 399s (process:2000): libfprint-realtek-DEBUG: 00:54:08.942: Delete print complete! 399s (process:2000): libfprint-device-DEBUG: 00:54:08.942: Device reported deletion completion 399s (process:2000): libfprint-SSM-DEBUG: 00:54:08.942: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 399s (process:2000): libfprint-device-DEBUG: 00:54:08.942: Completing action FPI_DEVICE_ACTION_DELETE in idle! 399s (process:2000): libfprint-device-DEBUG: 00:54:08.942: Not updating temperature model, device can run continuously! 399s (process:2000): libfprint-realtek-DEBUG: 00:54:08.942: 7399817003320: ../libfprint/drivers/realtek/realtek.c:1302 399s (process:2000): libfprint-device-DEBUG: 00:54:08.942: Device reported close completion 399s (process:2000): libfprint-device-DEBUG: 00:54:08.942: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 399s (process:2000): libfprint-device-DEBUG: 00:54:08.942: Not updating temperature model, device can run continuously! 399s enrolling 399s enroll progress: (<__gi__.FpiDeviceRealtek object at 0xf4891b08 (FpiDeviceRealtek at 0x238f760)>, 1, None, None, None) 399s enroll progress: (<__gi__.FpiDeviceRealtek object at 0xf4891b08 (FpiDeviceRealtek at 0x238f760)>, 2, None, None, None) 399s enroll progress: (<__gi__.FpiDeviceRealtek object at 0xf4891b08 (FpiDeviceRealtek at 0x238f760)>, 3, None, None, None) 399s enroll progress: (<__gi__.FpiDeviceRealtek object at 0xf4891b08 (FpiDeviceRealtek at 0x238f760)>, 4, None, None, None) 399s enroll progress: (<__gi__.FpiDeviceRealtek object at 0xf4891b08 (FpiDeviceRealtek at 0x238f760)>, 5, None, None, None) 399s enroll progress: (<__gi__.FpiDeviceRealtek object at 0xf4891b08 (FpiDeviceRealtek at 0x238f760)>, 6, None, None, None) 399s enroll progress: (<__gi__.FpiDeviceRealtek object at 0xf4891b08 (FpiDeviceRealtek at 0x238f760)>, 7, None, None, None) 399s enroll progress: (<__gi__.FpiDeviceRealtek object at 0xf4891b08 (FpiDeviceRealtek at 0x238f760)>, 8, None, None, None) 399s enroll done 399s listing 399s listing done 399s verifying 399s verify done 399s async identifying 399s indentification_done: 399s deleting 399s delete done 400s ** (umockdev-run:1996): DEBUG: 00:54:08.971: umockdev.vala:154: Removing test bed /tmp/umockdev.JFWD22 400s (umockdev-run:1996): GLib-DEBUG: 00:54:08.978: unsetenv() is not thread-safe and should not be used after threads are created 400s PASS: libfprint-2/driver-realtek.test 400s Running test: libfprint-2/driver-upektc_img-tcs1s.test 400s ** (umockdev-run:2008): DEBUG: 00:54:09.039: umockdev.vala:127: Created udev test bed /tmp/umockdev.KEZ112 400s ** (umockdev-run:2008): DEBUG: 00:54:09.039: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:08.1/0000:05:00.4/usb3/3-2 400s ** (umockdev-run:2008): DEBUG: 00:54:09.045: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:08.1/0000:05:00.4/usb3/3-2 (subsystem usb) 400s ** (umockdev-run:2008): DEBUG: 00:54:09.050: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.KEZ112/dev/bus/usb/003/004 400s ** (umockdev-run:2008): DEBUG: 00:54:09.050: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:08.1/0000:05:00.4/usb3 400s ** (umockdev-run:2008): DEBUG: 00:54:09.056: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:08.1/0000:05:00.4/usb3 (subsystem usb) 400s ** (umockdev-run:2008): DEBUG: 00:54:09.060: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.KEZ112/dev/bus/usb/003/001 400s ** (umockdev-run:2008): DEBUG: 00:54:09.061: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:08.1/0000:05:00.4 400s ** (umockdev-run:2008): DEBUG: 00:54:09.064: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:08.1/0000:05:00.4 (subsystem pci) 400s ** (umockdev-run:2008): DEBUG: 00:54:09.068: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:08.1 400s ** (umockdev-run:2008): DEBUG: 00:54:09.069: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:08.1 (subsystem pci) 400s (process:2012): libfprint-context-DEBUG: 00:54:09.183: Initializing FpContext (libfprint version 1.94.8+tod1) 400s (process:2012): libfprint-tod-DEBUG: 00:54:09.184: Impossible to load the shared drivers dir Error opening directory “/usr/lib/arm-linux-gnueabihf/libfprint-2/tod-1”: No such file or directory 400s (process:2012): libfprint-context-DEBUG: 00:54:09.187: No driver found for USB device 1D6B:0002 400s (process:2012): libfprint-device-DEBUG: 00:54:09.187: Device reported probe completion 400s (process:2012): libfprint-device-DEBUG: 00:54:09.187: Completing action FPI_DEVICE_ACTION_PROBE in idle! 400s (process:2012): libfprint-device-DEBUG: 00:54:09.187: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 400s (process:2012): libfprint-image_device-DEBUG: 00:54:09.189: Image device open completed 400s (process:2012): libfprint-device-DEBUG: 00:54:09.189: Device reported open completion 400s (process:2012): libfprint-device-DEBUG: 00:54:09.189: Completing action FPI_DEVICE_ACTION_OPEN in idle! 400s (process:2012): libfprint-device-DEBUG: 00:54:09.189: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 400s (process:2012): libfprint-device-DEBUG: 00:54:09.189: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 400s (process:2012): libfprint-image_device-DEBUG: 00:54:09.189: Activating image device 400s (process:2012): libfprint-image_device-DEBUG: 00:54:09.189: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING 400s (process:2012): libfprint-SSM-DEBUG: 00:54:09.189: [upektc_img] ACTIVATE_NUM_STATES entering state 0 400s (process:2012): libfprint-SSM-DEBUG: 00:54:09.190: [upektc_img] ACTIVATE_NUM_STATES entering state 1 400s (process:2012): libfprint-SSM-DEBUG: 00:54:09.191: [upektc_img] ACTIVATE_NUM_STATES entering state 2 400s (process:2012): libfprint-SSM-DEBUG: 00:54:09.192: [upektc_img] ACTIVATE_NUM_STATES entering state 3 400s (process:2012): libfprint-SSM-DEBUG: 00:54:09.192: [upektc_img] ACTIVATE_NUM_STATES entering state 4 400s (process:2012): libfprint-SSM-DEBUG: 00:54:09.193: [upektc_img] ACTIVATE_NUM_STATES entering state 5 400s (process:2012): libfprint-SSM-DEBUG: 00:54:09.193: [upektc_img] ACTIVATE_NUM_STATES entering state 6 400s (process:2012): libfprint-SSM-DEBUG: 00:54:09.194: [upektc_img] ACTIVATE_NUM_STATES entering state 7 400s (process:2012): libfprint-SSM-DEBUG: 00:54:09.194: [upektc_img] ACTIVATE_NUM_STATES entering state 8 400s (process:2012): libfprint-SSM-DEBUG: 00:54:09.195: [upektc_img] ACTIVATE_NUM_STATES entering state 9 400s (process:2012): libfprint-SSM-DEBUG: 00:54:09.196: [upektc_img] ACTIVATE_NUM_STATES entering state 10 400s (process:2012): libfprint-SSM-DEBUG: 00:54:09.196: [upektc_img] ACTIVATE_NUM_STATES entering state 11 400s (process:2012): libfprint-upektc_img-DEBUG: 00:54:09.197: Sensor type : TCS1x, width x height: 256 x 360 400s (process:2012): libfprint-SSM-DEBUG: 00:54:09.197: [upektc_img] ACTIVATE_NUM_STATES completed successfully 400s (process:2012): libfprint-image_device-DEBUG: 00:54:09.197: Image device activation completed 400s (process:2012): libfprint-image_device-DEBUG: 00:54:09.197: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE 400s (process:2012): libfprint-image_device-DEBUG: 00:54:09.197: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 400s (process:2012): libfprint-device-DEBUG: 00:54:09.197: Device reported finger status change: FP_FINGER_STATUS_NEEDED 400s (process:2012): libfprint-SSM-DEBUG: 00:54:09.197: [upektc_img] CAPTURE_NUM_STATES entering state 0 400s (process:2012): libfprint-SSM-DEBUG: 00:54:09.197: [upektc_img] CAPTURE_NUM_STATES entering state 1 400s (process:2012): libfprint-upektc_img-DEBUG: 00:54:09.198: request completed, len: 0000 400s (process:2012): libfprint-SSM-DEBUG: 00:54:09.198: [upektc_img] CAPTURE_NUM_STATES entering state 1 400s (process:2012): libfprint-upektc_img-DEBUG: 00:54:09.198: request completed, len: 0040 400s (process:2012): libfprint-upektc_img-DEBUG: 00:54:09.198: 18th byte is 0c 400s (process:2012): libfprint-SSM-DEBUG: 00:54:09.198: [upektc_img] CAPTURE_NUM_STATES entering state 3 400s (process:2012): libfprint-SSM-DEBUG: 00:54:09.199: [upektc_img] CAPTURE_NUM_STATES entering state 1 400s (process:2012): libfprint-upektc_img-DEBUG: 00:54:09.199: request completed, len: 0000 400s (process:2012): libfprint-SSM-DEBUG: 00:54:09.199: [upektc_img] CAPTURE_NUM_STATES entering state 1 400s (process:2012): libfprint-upektc_img-DEBUG: 00:54:09.200: request completed, len: 0040 400s (process:2012): libfprint-upektc_img-DEBUG: 00:54:09.200: 18th byte is 13 400s (process:2012): libfprint-SSM-DEBUG: 00:54:09.200: [upektc_img] CAPTURE_NUM_STATES entering state 3 400s (process:2012): libfprint-SSM-DEBUG: 00:54:09.200: [upektc_img] CAPTURE_NUM_STATES entering state 1 400s (process:2012): libfprint-upektc_img-DEBUG: 00:54:09.201: request completed, len: 0000 400s (process:2012): libfprint-SSM-DEBUG: 00:54:09.201: [upektc_img] CAPTURE_NUM_STATES entering state 1 400s (process:2012): libfprint-upektc_img-DEBUG: 00:54:09.201: request completed, len: 0040 400s (process:2012): libfprint-upektc_img-DEBUG: 00:54:09.201: 18th byte is 00 400s (process:2012): libfprint-device-DEBUG: 00:54:09.201: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 400s (process:2012): libfprint-SSM-DEBUG: 00:54:09.201: [upektc_img] CAPTURE_NUM_STATES entering state 3 400s (process:2012): libfprint-SSM-DEBUG: 00:54:09.202: [upektc_img] CAPTURE_NUM_STATES entering state 1 400s (process:2012): libfprint-upektc_img-DEBUG: 00:54:09.202: request completed, len: 0000 400s (process:2012): libfprint-SSM-DEBUG: 00:54:09.202: [upektc_img] CAPTURE_NUM_STATES entering state 1 400s (process:2012): libfprint-upektc_img-DEBUG: 00:54:09.203: request completed, len: 0040 400s (process:2012): libfprint-upektc_img-DEBUG: 00:54:09.203: response_size is 2052, actual_length is 64 400s (process:2012): libfprint-upektc_img-DEBUG: 00:54:09.203: Waiting for rest of transfer 400s (process:2012): libfprint-SSM-DEBUG: 00:54:09.203: [upektc_img] CAPTURE_NUM_STATES entering state 1 400s (process:2012): libfprint-upektc_img-DEBUG: 00:54:09.203: request completed, len: 07c4 400s (process:2012): libfprint-image_device-DEBUG: 00:54:09.203: Image device reported finger status: on 400s (process:2012): libfprint-image_device-DEBUG: 00:54:09.203: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 400s (process:2012): libfprint-SSM-DEBUG: 00:54:09.203: [upektc_img] CAPTURE_NUM_STATES entering state 5 400s (process:2012): libfprint-SSM-DEBUG: 00:54:09.204: [upektc_img] CAPTURE_NUM_STATES entering state 1 400s (process:2012): libfprint-upektc_img-DEBUG: 00:54:09.204: request completed, len: 0040 400s (process:2012): libfprint-upektc_img-DEBUG: 00:54:09.204: response_size is 2052, actual_length is 64 400s (process:2012): libfprint-upektc_img-DEBUG: 00:54:09.204: Waiting for rest of transfer 400s (process:2012): libfprint-SSM-DEBUG: 00:54:09.204: [upektc_img] CAPTURE_NUM_STATES entering state 1 400s (process:2012): libfprint-upektc_img-DEBUG: 00:54:09.205: request completed, len: 07c4 400s (process:2012): libfprint-SSM-DEBUG: 00:54:09.205: [upektc_img] CAPTURE_NUM_STATES entering state 5 400s (process:2012): libfprint-SSM-DEBUG: 00:54:09.206: [upektc_img] CAPTURE_NUM_STATES entering state 1 400s (process:2012): libfprint-upektc_img-DEBUG: 00:54:09.206: request completed, len: 0040 400s (process:2012): libfprint-upektc_img-DEBUG: 00:54:09.206: response_size is 2052, actual_length is 64 400s (process:2012): libfprint-upektc_img-DEBUG: 00:54:09.206: Waiting for rest of transfer 400s (process:2012): libfprint-SSM-DEBUG: 00:54:09.206: [upektc_img] CAPTURE_NUM_STATES entering state 1 400s (process:2012): libfprint-upektc_img-DEBUG: 00:54:09.207: request completed, len: 07c4 400s (process:2012): libfprint-SSM-DEBUG: 00:54:09.207: [upektc_img] CAPTURE_NUM_STATES entering state 5 400s (process:2012): libfprint-SSM-DEBUG: 00:54:09.207: [upektc_img] CAPTURE_NUM_STATES entering state 1 400s (process:2012): libfprint-upektc_img-DEBUG: 00:54:09.208: request completed, len: 0040 400s (process:2012): libfprint-upektc_img-DEBUG: 00:54:09.208: response_size is 2052, actual_length is 64 400s (process:2012): libfprint-upektc_img-DEBUG: 00:54:09.208: Waiting for rest of transfer 400s (process:2012): libfprint-SSM-DEBUG: 00:54:09.208: [upektc_img] CAPTURE_NUM_STATES entering state 1 400s (process:2012): libfprint-upektc_img-DEBUG: 00:54:09.209: request completed, len: 07c4 400s (process:2012): libfprint-SSM-DEBUG: 00:54:09.209: [upektc_img] CAPTURE_NUM_STATES entering state 5 400s (process:2012): libfprint-SSM-DEBUG: 00:54:09.209: [upektc_img] CAPTURE_NUM_STATES entering state 1 400s (process:2012): libfprint-upektc_img-DEBUG: 00:54:09.210: request completed, len: 0040 400s (process:2012): libfprint-upektc_img-DEBUG: 00:54:09.210: response_size is 2052, actual_length is 64 400s (process:2012): libfprint-upektc_img-DEBUG: 00:54:09.210: Waiting for rest of transfer 400s (process:2012): libfprint-SSM-DEBUG: 00:54:09.210: [upektc_img] CAPTURE_NUM_STATES entering state 1 400s (process:2012): libfprint-upektc_img-DEBUG: 00:54:09.210: request completed, len: 07c4 400s (process:2012): libfprint-SSM-DEBUG: 00:54:09.210: [upektc_img] CAPTURE_NUM_STATES entering state 5 400s (process:2012): libfprint-SSM-DEBUG: 00:54:09.211: [upektc_img] CAPTURE_NUM_STATES entering state 1 400s (process:2012): libfprint-upektc_img-DEBUG: 00:54:09.211: request completed, len: 0040 400s (process:2012): libfprint-upektc_img-DEBUG: 00:54:09.211: response_size is 2052, actual_length is 64 400s (process:2012): libfprint-upektc_img-DEBUG: 00:54:09.211: Waiting for rest of transfer 400s (process:2012): libfprint-SSM-DEBUG: 00:54:09.211: [upektc_img] CAPTURE_NUM_STATES entering state 1 400s (process:2012): libfprint-upektc_img-DEBUG: 00:54:09.212: request completed, len: 07c4 400s (process:2012): libfprint-SSM-DEBUG: 00:54:09.212: [upektc_img] CAPTURE_NUM_STATES entering state 5 400s (process:2012): libfprint-SSM-DEBUG: 00:54:09.213: [upektc_img] CAPTURE_NUM_STATES entering state 1 400s (process:2012): libfprint-upektc_img-DEBUG: 00:54:09.213: request completed, len: 0040 400s (process:2012): libfprint-upektc_img-DEBUG: 00:54:09.213: response_size is 2052, actual_length is 64 400s (process:2012): libfprint-upektc_img-DEBUG: 00:54:09.213: Waiting for rest of transfer 400s (process:2012): libfprint-SSM-DEBUG: 00:54:09.213: [upektc_img] CAPTURE_NUM_STATES entering state 1 400s (process:2012): libfprint-upektc_img-DEBUG: 00:54:09.214: request completed, len: 07c4 400s (process:2012): libfprint-SSM-DEBUG: 00:54:09.214: [upektc_img] CAPTURE_NUM_STATES entering state 5 400s (process:2012): libfprint-SSM-DEBUG: 00:54:09.215: [upektc_img] CAPTURE_NUM_STATES entering state 1 400s (process:2012): libfprint-upektc_img-DEBUG: 00:54:09.215: request completed, len: 0040 400s (process:2012): libfprint-upektc_img-DEBUG: 00:54:09.215: response_size is 2052, actual_length is 64 400s (process:2012): libfprint-upektc_img-DEBUG: 00:54:09.215: Waiting for rest of transfer 400s (process:2012): libfprint-SSM-DEBUG: 00:54:09.215: [upektc_img] CAPTURE_NUM_STATES entering state 1 400s (process:2012): libfprint-upektc_img-DEBUG: 00:54:09.216: request completed, len: 07c4 400s (process:2012): libfprint-SSM-DEBUG: 00:54:09.216: [upektc_img] CAPTURE_NUM_STATES entering state 5 400s (process:2012): libfprint-SSM-DEBUG: 00:54:09.216: [upektc_img] CAPTURE_NUM_STATES entering state 1 400s (process:2012): libfprint-upektc_img-DEBUG: 00:54:09.217: request completed, len: 0040 400s (process:2012): libfprint-upektc_img-DEBUG: 00:54:09.217: response_size is 2052, actual_length is 64 400s (process:2012): libfprint-upektc_img-DEBUG: 00:54:09.217: Waiting for rest of transfer 400s (process:2012): libfprint-SSM-DEBUG: 00:54:09.217: [upektc_img] CAPTURE_NUM_STATES entering state 1 400s (process:2012): libfprint-upektc_img-DEBUG: 00:54:09.217: request completed, len: 07c4 400s (process:2012): libfprint-SSM-DEBUG: 00:54:09.217: [upektc_img] CAPTURE_NUM_STATES entering state 5 400s (process:2012): libfprint-SSM-DEBUG: 00:54:09.218: [upektc_img] CAPTURE_NUM_STATES entering state 1 400s (process:2012): libfprint-upektc_img-DEBUG: 00:54:09.218: request completed, len: 0040 400s (process:2012): libfprint-upektc_img-DEBUG: 00:54:09.218: response_size is 2052, actual_length is 64 400s (process:2012): libfprint-upektc_img-DEBUG: 00:54:09.218: Waiting for rest of transfer 400s (process:2012): libfprint-SSM-DEBUG: 00:54:09.218: [upektc_img] CAPTURE_NUM_STATES entering state 1 400s (process:2012): libfprint-upektc_img-DEBUG: 00:54:09.219: request completed, len: 07c4 400s (process:2012): libfprint-SSM-DEBUG: 00:54:09.219: [upektc_img] CAPTURE_NUM_STATES entering state 5 400s (process:2012): libfprint-SSM-DEBUG: 00:54:09.219: [upektc_img] CAPTURE_NUM_STATES entering state 1 400s (process:2012): libfprint-upektc_img-DEBUG: 00:54:09.220: request completed, len: 0040 400s (process:2012): libfprint-upektc_img-DEBUG: 00:54:09.220: response_size is 2052, actual_length is 64 400s (process:2012): libfprint-upektc_img-DEBUG: 00:54:09.220: Waiting for rest of transfer 400s (process:2012): libfprint-SSM-DEBUG: 00:54:09.220: [upektc_img] CAPTURE_NUM_STATES entering state 1 400s (process:2012): libfprint-upektc_img-DEBUG: 00:54:09.222: request completed, len: 07c4 400s (process:2012): libfprint-SSM-DEBUG: 00:54:09.222: [upektc_img] CAPTURE_NUM_STATES entering state 5 400s (process:2012): libfprint-SSM-DEBUG: 00:54:09.222: [upektc_img] CAPTURE_NUM_STATES entering state 1 400s (process:2012): libfprint-upektc_img-DEBUG: 00:54:09.223: request completed, len: 0040 400s (process:2012): libfprint-upektc_img-DEBUG: 00:54:09.223: response_size is 2052, actual_length is 64 400s (process:2012): libfprint-upektc_img-DEBUG: 00:54:09.223: Waiting for rest of transfer 400s (process:2012): libfprint-SSM-DEBUG: 00:54:09.223: [upektc_img] CAPTURE_NUM_STATES entering state 1 400s (process:2012): libfprint-upektc_img-DEBUG: 00:54:09.224: request completed, len: 07c4 400s (process:2012): libfprint-SSM-DEBUG: 00:54:09.224: [upektc_img] CAPTURE_NUM_STATES entering state 5 400s (process:2012): libfprint-SSM-DEBUG: 00:54:09.224: [upektc_img] CAPTURE_NUM_STATES entering state 1 400s (process:2012): libfprint-upektc_img-DEBUG: 00:54:09.225: request completed, len: 0040 400s (process:2012): libfprint-upektc_img-DEBUG: 00:54:09.225: response_size is 2052, actual_length is 64 400s (process:2012): libfprint-upektc_img-DEBUG: 00:54:09.225: Waiting for rest of transfer 400s (process:2012): libfprint-SSM-DEBUG: 00:54:09.225: [upektc_img] CAPTURE_NUM_STATES entering state 1 400s (process:2012): libfprint-upektc_img-DEBUG: 00:54:09.225: request completed, len: 07c4 400s (process:2012): libfprint-SSM-DEBUG: 00:54:09.225: [upektc_img] CAPTURE_NUM_STATES entering state 5 400s (process:2012): libfprint-SSM-DEBUG: 00:54:09.226: [upektc_img] CAPTURE_NUM_STATES entering state 1 400s (process:2012): libfprint-upektc_img-DEBUG: 00:54:09.226: request completed, len: 0040 400s (process:2012): libfprint-upektc_img-DEBUG: 00:54:09.226: response_size is 2052, actual_length is 64 400s (process:2012): libfprint-upektc_img-DEBUG: 00:54:09.226: Waiting for rest of transfer 400s (process:2012): libfprint-SSM-DEBUG: 00:54:09.226: [upektc_img] CAPTURE_NUM_STATES entering state 1 400s (process:2012): libfprint-upektc_img-DEBUG: 00:54:09.227: request completed, len: 07c4 400s (process:2012): libfprint-SSM-DEBUG: 00:54:09.227: [upektc_img] CAPTURE_NUM_STATES entering state 5 400s (process:2012): libfprint-SSM-DEBUG: 00:54:09.227: [upektc_img] CAPTURE_NUM_STATES entering state 1 400s (process:2012): libfprint-upektc_img-DEBUG: 00:54:09.228: request completed, len: 0040 400s (process:2012): libfprint-upektc_img-DEBUG: 00:54:09.228: response_size is 2052, actual_length is 64 400s (process:2012): libfprint-upektc_img-DEBUG: 00:54:09.228: Waiting for rest of transfer 400s (process:2012): libfprint-SSM-DEBUG: 00:54:09.228: [upektc_img] CAPTURE_NUM_STATES entering state 1 400s (process:2012): libfprint-upektc_img-DEBUG: 00:54:09.228: request completed, len: 07c4 400s (process:2012): libfprint-SSM-DEBUG: 00:54:09.228: [upektc_img] CAPTURE_NUM_STATES entering state 5 400s (process:2012): libfprint-SSM-DEBUG: 00:54:09.228: [upektc_img] CAPTURE_NUM_STATES entering state 1 400s (process:2012): libfprint-upektc_img-DEBUG: 00:54:09.229: request completed, len: 0040 400s (process:2012): libfprint-upektc_img-DEBUG: 00:54:09.229: response_size is 2052, actual_length is 64 400s (process:2012): libfprint-upektc_img-DEBUG: 00:54:09.229: Waiting for rest of transfer 400s (process:2012): libfprint-SSM-DEBUG: 00:54:09.229: [upektc_img] CAPTURE_NUM_STATES entering state 1 400s (process:2012): libfprint-upektc_img-DEBUG: 00:54:09.230: request completed, len: 07c4 400s (process:2012): libfprint-SSM-DEBUG: 00:54:09.230: [upektc_img] CAPTURE_NUM_STATES entering state 5 400s (process:2012): libfprint-SSM-DEBUG: 00:54:09.230: [upektc_img] CAPTURE_NUM_STATES entering state 1 400s (process:2012): libfprint-upektc_img-DEBUG: 00:54:09.230: request completed, len: 0040 400s (process:2012): libfprint-upektc_img-DEBUG: 00:54:09.230: response_size is 2052, actual_length is 64 400s (process:2012): libfprint-upektc_img-DEBUG: 00:54:09.230: Waiting for rest of transfer 400s (process:2012): libfprint-SSM-DEBUG: 00:54:09.230: [upektc_img] CAPTURE_NUM_STATES entering state 1 400s (process:2012): libfprint-upektc_img-DEBUG: 00:54:09.231: request completed, len: 07c4 400s (process:2012): libfprint-SSM-DEBUG: 00:54:09.231: [upektc_img] CAPTURE_NUM_STATES entering state 5 400s (process:2012): libfprint-SSM-DEBUG: 00:54:09.231: [upektc_img] CAPTURE_NUM_STATES entering state 1 400s (process:2012): libfprint-upektc_img-DEBUG: 00:54:09.232: request completed, len: 0040 400s (process:2012): libfprint-upektc_img-DEBUG: 00:54:09.232: response_size is 2052, actual_length is 64 400s (process:2012): libfprint-upektc_img-DEBUG: 00:54:09.232: Waiting for rest of transfer 400s (process:2012): libfprint-SSM-DEBUG: 00:54:09.232: [upektc_img] CAPTURE_NUM_STATES entering state 1 400s (process:2012): libfprint-upektc_img-DEBUG: 00:54:09.232: request completed, len: 07c4 400s (process:2012): libfprint-SSM-DEBUG: 00:54:09.232: [upektc_img] CAPTURE_NUM_STATES entering state 5 400s (process:2012): libfprint-SSM-DEBUG: 00:54:09.233: [upektc_img] CAPTURE_NUM_STATES entering state 1 400s (process:2012): libfprint-upektc_img-DEBUG: 00:54:09.233: request completed, len: 0040 400s (process:2012): libfprint-upektc_img-DEBUG: 00:54:09.233: response_size is 2052, actual_length is 64 400s (process:2012): libfprint-upektc_img-DEBUG: 00:54:09.233: Waiting for rest of transfer 400s (process:2012): libfprint-SSM-DEBUG: 00:54:09.233: [upektc_img] CAPTURE_NUM_STATES entering state 1 400s (process:2012): libfprint-upektc_img-DEBUG: 00:54:09.234: request completed, len: 07c4 400s (process:2012): libfprint-SSM-DEBUG: 00:54:09.234: [upektc_img] CAPTURE_NUM_STATES entering state 5 400s (process:2012): libfprint-SSM-DEBUG: 00:54:09.234: [upektc_img] CAPTURE_NUM_STATES entering state 1 400s (process:2012): libfprint-upektc_img-DEBUG: 00:54:09.235: request completed, len: 0040 400s (process:2012): libfprint-upektc_img-DEBUG: 00:54:09.235: response_size is 2052, actual_length is 64 400s (process:2012): libfprint-upektc_img-DEBUG: 00:54:09.235: Waiting for rest of transfer 400s (process:2012): libfprint-SSM-DEBUG: 00:54:09.235: [upektc_img] CAPTURE_NUM_STATES entering state 1 400s (process:2012): libfprint-upektc_img-DEBUG: 00:54:09.235: request completed, len: 07c4 400s (process:2012): libfprint-SSM-DEBUG: 00:54:09.235: [upektc_img] CAPTURE_NUM_STATES entering state 5 400s (process:2012): libfprint-SSM-DEBUG: 00:54:09.236: [upektc_img] CAPTURE_NUM_STATES entering state 1 400s (process:2012): libfprint-upektc_img-DEBUG: 00:54:09.236: request completed, len: 0040 400s (process:2012): libfprint-upektc_img-DEBUG: 00:54:09.236: response_size is 2052, actual_length is 64 400s (process:2012): libfprint-upektc_img-DEBUG: 00:54:09.236: Waiting for rest of transfer 400s (process:2012): libfprint-SSM-DEBUG: 00:54:09.236: [upektc_img] CAPTURE_NUM_STATES entering state 1 400s (process:2012): libfprint-upektc_img-DEBUG: 00:54:09.237: request completed, len: 07c4 400s (process:2012): libfprint-SSM-DEBUG: 00:54:09.237: [upektc_img] CAPTURE_NUM_STATES entering state 5 400s (process:2012): libfprint-SSM-DEBUG: 00:54:09.237: [upektc_img] CAPTURE_NUM_STATES entering state 1 400s (process:2012): libfprint-upektc_img-DEBUG: 00:54:09.238: request completed, len: 0040 400s (process:2012): libfprint-upektc_img-DEBUG: 00:54:09.238: response_size is 2052, actual_length is 64 400s (process:2012): libfprint-upektc_img-DEBUG: 00:54:09.238: Waiting for rest of transfer 400s (process:2012): libfprint-SSM-DEBUG: 00:54:09.238: [upektc_img] CAPTURE_NUM_STATES entering state 1 400s (process:2012): libfprint-upektc_img-DEBUG: 00:54:09.238: request completed, len: 07c4 400s (process:2012): libfprint-SSM-DEBUG: 00:54:09.238: [upektc_img] CAPTURE_NUM_STATES entering state 5 400s (process:2012): libfprint-SSM-DEBUG: 00:54:09.239: [upektc_img] CAPTURE_NUM_STATES entering state 1 400s (process:2012): libfprint-upektc_img-DEBUG: 00:54:09.239: request completed, len: 0040 400s (process:2012): libfprint-upektc_img-DEBUG: 00:54:09.239: response_size is 2052, actual_length is 64 400s (process:2012): libfprint-upektc_img-DEBUG: 00:54:09.239: Waiting for rest of transfer 400s (process:2012): libfprint-SSM-DEBUG: 00:54:09.239: [upektc_img] CAPTURE_NUM_STATES entering state 1 400s (process:2012): libfprint-upektc_img-DEBUG: 00:54:09.240: request completed, len: 07c4 400s (process:2012): libfprint-SSM-DEBUG: 00:54:09.240: [upektc_img] CAPTURE_NUM_STATES entering state 5 400s (process:2012): libfprint-SSM-DEBUG: 00:54:09.240: [upektc_img] CAPTURE_NUM_STATES entering state 1 400s (process:2012): libfprint-upektc_img-DEBUG: 00:54:09.241: request completed, len: 0040 400s (process:2012): libfprint-upektc_img-DEBUG: 00:54:09.241: response_size is 2052, actual_length is 64 400s (process:2012): libfprint-upektc_img-DEBUG: 00:54:09.241: Waiting for rest of transfer 400s (process:2012): libfprint-SSM-DEBUG: 00:54:09.241: [upektc_img] CAPTURE_NUM_STATES entering state 1 400s (process:2012): libfprint-upektc_img-DEBUG: 00:54:09.241: request completed, len: 07c4 400s (process:2012): libfprint-SSM-DEBUG: 00:54:09.241: [upektc_img] CAPTURE_NUM_STATES entering state 5 400s (process:2012): libfprint-SSM-DEBUG: 00:54:09.242: [upektc_img] CAPTURE_NUM_STATES entering state 1 400s (process:2012): libfprint-upektc_img-DEBUG: 00:54:09.242: request completed, len: 0040 400s (process:2012): libfprint-upektc_img-DEBUG: 00:54:09.242: response_size is 2052, actual_length is 64 400s (process:2012): libfprint-upektc_img-DEBUG: 00:54:09.242: Waiting for rest of transfer 400s (process:2012): libfprint-SSM-DEBUG: 00:54:09.242: [upektc_img] CAPTURE_NUM_STATES entering state 1 400s (process:2012): libfprint-upektc_img-DEBUG: 00:54:09.243: request completed, len: 07c4 400s (process:2012): libfprint-SSM-DEBUG: 00:54:09.243: [upektc_img] CAPTURE_NUM_STATES entering state 5 400s (process:2012): libfprint-SSM-DEBUG: 00:54:09.243: [upektc_img] CAPTURE_NUM_STATES entering state 1 400s (process:2012): libfprint-upektc_img-DEBUG: 00:54:09.244: request completed, len: 0040 400s (process:2012): libfprint-upektc_img-DEBUG: 00:54:09.244: response_size is 814, actual_length is 64 400s (process:2012): libfprint-upektc_img-DEBUG: 00:54:09.244: Waiting for rest of transfer 400s (process:2012): libfprint-SSM-DEBUG: 00:54:09.244: [upektc_img] CAPTURE_NUM_STATES entering state 1 400s (process:2012): libfprint-upektc_img-DEBUG: 00:54:09.244: request completed, len: 02ee 400s (process:2012): libfprint-upektc_img-DEBUG: 00:54:09.244: Image size is 51840 400s (process:2012): libfprint-image_device-DEBUG: 00:54:09.244: Image device captured an image 400s (process:2012): libfprint-image_device-DEBUG: 00:54:09.245: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 400s (process:2012): libfprint-device-DEBUG: 00:54:09.245: Device reported finger status change: FP_FINGER_STATUS_PRESENT 400s (process:2012): libfprint-device-DEBUG: 00:54:09.245: Device reported finger status change: FP_FINGER_STATUS_NONE 400s (process:2012): libfprint-image_device-DEBUG: 00:54:09.245: Image device reported finger status: off 400s (process:2012): libfprint-image_device-DEBUG: 00:54:09.245: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 400s (process:2012): libfprint-image_device-DEBUG: 00:54:09.245: Deactivating image device 400s (process:2012): libfprint-image_device-DEBUG: 00:54:09.245: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_DEACTIVATING 400s (process:2012): libfprint-SSM-DEBUG: 00:54:09.245: [upektc_img] CAPTURE_NUM_STATES completed successfully 400s (process:2012): libfprint-SSM-DEBUG: 00:54:09.245: [upektc_img] DEACTIVATE_NUM_STATES entering state 0 400s (process:2012): libfprint-SSM-DEBUG: 00:54:09.246: [upektc_img] DEACTIVATE_NUM_STATES entering state 1 400s (process:2012): libfprint-SSM-DEBUG: 00:54:09.251: [upektc_img] DEACTIVATE_NUM_STATES completed successfully 400s (process:2012): libfprint-upektc_img-DEBUG: 00:54:09.251: Deactivate completed 400s (process:2012): libfprint-image_device-DEBUG: 00:54:09.251: Image device deactivation completed 400s (process:2012): libfprint-image_device-DEBUG: 00:54:09.251: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE 400s (process:2012): libfprint-image-DEBUG: 00:54:09.275: Minutiae scan completed in 0.029443 secs 400s (process:2012): libfprint-device-DEBUG: 00:54:09.275: Device reported capture completion 400s (process:2012): libfprint-device-DEBUG: 00:54:09.275: Completing action FPI_DEVICE_ACTION_CAPTURE in idle! 400s (process:2012): libfprint-device-DEBUG: 00:54:09.275: Updated temperature model after 0.09 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 400s (process:2012): libfprint-image_device-DEBUG: 00:54:09.275: Image device close completed 400s (process:2012): libfprint-device-DEBUG: 00:54:09.275: Device reported close completion 400s (process:2012): libfprint-device-DEBUG: 00:54:09.276: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 400s (process:2012): libfprint-device-DEBUG: 00:54:09.276: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 400s ** (umockdev-run:2008): DEBUG: 00:54:09.386: umockdev.vala:154: Removing test bed /tmp/umockdev.KEZ112 400s (umockdev-run:2008): GLib-DEBUG: 00:54:09.396: unsetenv() is not thread-safe and should not be used after threads are created 400s Comparing PNGs /tmp/libfprint-umockdev-test-ny9bbuqf/capture.png and /usr/share/installed-tests/libfprint-2/upektc_img-tcs1s/capture.png 400s PASS: libfprint-2/driver-upektc_img-tcs1s.test 400s Running test: libfprint-2/fp-device.test 400s TAP version 14 400s # random seed: R02Sc4231f92034c0dcbb0c8fede6940d3da 400s 1..17 400s # Start of device tests 400s # Start of async tests 400s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 400s # libfprint-tod-DEBUG: Impossible to load the shared drivers dir Error opening directory ?/usr/lib/arm-linux-gnueabihf/libfprint-2/tod-1?: No such file or directory 400s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0003 400s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 400s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0002 400s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_IMAGE, /tmp/libfprint-NYDA22/virtual_image.socket 400s # libfprint-context-DEBUG: created 400s # libfprint-device-DEBUG: Device reported probe completion 400s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 400s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 400s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:2019): libfprint-virtual_image-DEBUG: 00:54:09.440: 7399817501602: ../libfprint/drivers/virtual-image.c:216 400s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:2019): libfprint-virtual_device_connection-DEBUG: 00:54:09.440: 7399817501705: ../libfprint/drivers/virtual-device-listener.c:153 400s # libfprint-image_device-DEBUG: Image device open completed 400s # libfprint-device-DEBUG: Device reported open completion 400s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 400s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 400s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:2019): libfprint-virtual_image-DEBUG: 00:54:09.541: 7399817602171: ../libfprint/drivers/virtual-image.c:244 400s # libfprint-image_device-DEBUG: Image device close completed 400s # libfprint-device-DEBUG: Device reported close completion 400s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 400s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 400s # GLib-DEBUG: unsetenv() is not thread-safe and should not be used after threads are created 400s ok 1 /device/async/open 400s # GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used after threads are created 400s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 400s # libfprint-tod-DEBUG: Impossible to load the shared drivers dir Error opening directory ?/usr/lib/arm-linux-gnueabihf/libfprint-2/tod-1?: No such file or directory 400s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0003 400s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 400s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0002 400s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_IMAGE, /tmp/libfprint-S4AC22/virtual_image.socket 400s # libfprint-context-DEBUG: created 400s # libfprint-device-DEBUG: Device reported probe completion 400s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 400s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 400s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:2019): libfprint-virtual_image-DEBUG: 00:54:09.645: 7399817706047: ../libfprint/drivers/virtual-image.c:216 400s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:2019): libfprint-virtual_device_connection-DEBUG: 00:54:09.645: 7399817706076: ../libfprint/drivers/virtual-device-listener.c:153 400s # libfprint-image_device-DEBUG: Image device open completed 400s # libfprint-device-DEBUG: Device reported open completion 400s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 400s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 400s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:2019): libfprint-virtual_image-DEBUG: 00:54:09.745: 7399817806490: ../libfprint/drivers/virtual-image.c:244 400s # libfprint-image_device-DEBUG: Image device close completed 400s # libfprint-device-DEBUG: Device reported close completion 400s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 400s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 400s # GLib-DEBUG: unsetenv() is not thread-safe and should not be used after threads are created 400s ok 2 /device/async/close 400s # End of async tests 400s # Start of sync tests 400s # GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used after threads are created 400s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 400s # libfprint-tod-DEBUG: Impossible to load the shared drivers dir Error opening directory ?/usr/lib/arm-linux-gnueabihf/libfprint-2/tod-1?: No such file or directory 400s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0003 400s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 400s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0002 400s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_IMAGE, /tmp/libfprint-MM5I22/virtual_image.socket 400s # libfprint-context-DEBUG: created 400s # libfprint-device-DEBUG: Device reported probe completion 400s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 400s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 400s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:2019): libfprint-virtual_image-DEBUG: 00:54:09.849: 7399817910673: ../libfprint/drivers/virtual-image.c:216 400s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:2019): libfprint-virtual_device_connection-DEBUG: 00:54:09.849: 7399817910698: ../libfprint/drivers/virtual-device-listener.c:153 400s # libfprint-image_device-DEBUG: Image device open completed 400s # libfprint-device-DEBUG: Device reported open completion 400s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 400s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 400s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:2019): libfprint-virtual_image-DEBUG: 00:54:09.950: 7399818011163: ../libfprint/drivers/virtual-image.c:244 401s # libfprint-image_device-DEBUG: Image device close completed 401s # libfprint-device-DEBUG: Device reported close completion 401s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 401s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 401s # GLib-DEBUG: unsetenv() is not thread-safe and should not be used after threads are created 401s ok 3 /device/sync/open 401s # GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used after threads are created 401s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 401s # libfprint-tod-DEBUG: Impossible to load the shared drivers dir Error opening directory ?/usr/lib/arm-linux-gnueabihf/libfprint-2/tod-1?: No such file or directory 401s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0003 401s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 401s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0002 401s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_IMAGE, /tmp/libfprint-0OE212/virtual_image.socket 401s # libfprint-context-DEBUG: created 401s # libfprint-device-DEBUG: Device reported probe completion 401s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 401s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 401s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:2019): libfprint-virtual_image-DEBUG: 00:54:10.053: 7399818114880: ../libfprint/drivers/virtual-image.c:216 401s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:2019): libfprint-virtual_device_connection-DEBUG: 00:54:10.053: 7399818114902: ../libfprint/drivers/virtual-device-listener.c:153 401s # libfprint-image_device-DEBUG: Image device open completed 401s # libfprint-device-DEBUG: Device reported open completion 401s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 401s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 401s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:2019): libfprint-virtual_image-DEBUG: 00:54:10.154: 7399818215330: ../libfprint/drivers/virtual-image.c:244 401s # libfprint-image_device-DEBUG: Image device close completed 401s # libfprint-device-DEBUG: Device reported close completion 401s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 401s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 401s # GLib-DEBUG: unsetenv() is not thread-safe and should not be used after threads are created 401s ok 4 /device/sync/close 401s # GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used after threads are created 401s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 401s # libfprint-tod-DEBUG: Impossible to load the shared drivers dir Error opening directory ?/usr/lib/arm-linux-gnueabihf/libfprint-2/tod-1?: No such file or directory 401s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0003 401s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 401s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0002 401s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_IMAGE, /tmp/libfprint-3YP312/virtual_image.socket 401s # libfprint-context-DEBUG: created 401s # libfprint-device-DEBUG: Device reported probe completion 401s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 401s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 401s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:2019): libfprint-virtual_image-DEBUG: 00:54:10.264: 7399818325651: ../libfprint/drivers/virtual-image.c:216 401s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:2019): libfprint-virtual_device_connection-DEBUG: 00:54:10.264: 7399818325670: ../libfprint/drivers/virtual-device-listener.c:153 401s # libfprint-image_device-DEBUG: Image device open completed 401s # libfprint-device-DEBUG: Device reported open completion 401s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 401s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 401s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:2019): libfprint-virtual_image-DEBUG: 00:54:10.365: 7399818426436: ../libfprint/drivers/virtual-image.c:244 401s # libfprint-image_device-DEBUG: Image device close completed 401s # libfprint-device-DEBUG: Device reported close completion 401s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 401s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 401s # GLib-DEBUG: unsetenv() is not thread-safe and should not be used after threads are created 401s ok 5 /device/sync/get_driver 401s # GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used after threads are created 401s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 401s # libfprint-tod-DEBUG: Impossible to load the shared drivers dir Error opening directory ?/usr/lib/arm-linux-gnueabihf/libfprint-2/tod-1?: No such file or directory 401s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0003 401s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 401s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0002 401s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_IMAGE, /tmp/libfprint-F3B812/virtual_image.socket 401s # libfprint-context-DEBUG: created 401s # libfprint-device-DEBUG: Device reported probe completion 401s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 401s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 401s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:2019): libfprint-virtual_image-DEBUG: 00:54:10.472: 7399818533464: ../libfprint/drivers/virtual-image.c:216 401s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:2019): libfprint-virtual_device_connection-DEBUG: 00:54:10.472: 7399818533509: ../libfprint/drivers/virtual-device-listener.c:153 401s # libfprint-image_device-DEBUG: Image device open completed 401s # libfprint-device-DEBUG: Device reported open completion 401s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 401s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 401s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:2019): libfprint-virtual_image-DEBUG: 00:54:10.573: 7399818634375: ../libfprint/drivers/virtual-image.c:244 401s # libfprint-image_device-DEBUG: Image device close completed 401s # libfprint-device-DEBUG: Device reported close completion 401s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 401s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 401s # GLib-DEBUG: unsetenv() is not thread-safe and should not be used after threads are created 401s ok 6 /device/sync/get_device_id 401s # GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used after threads are created 401s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 401s # libfprint-tod-DEBUG: Impossible to load the shared drivers dir Error opening directory ?/usr/lib/arm-linux-gnueabihf/libfprint-2/tod-1?: No such file or directory 401s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0003 401s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 401s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0002 401s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_IMAGE, /tmp/libfprint-QKTF22/virtual_image.socket 401s # libfprint-context-DEBUG: created 401s # libfprint-device-DEBUG: Device reported probe completion 401s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 401s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 401s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:2019): libfprint-virtual_image-DEBUG: 00:54:10.679: 7399818740582: ../libfprint/drivers/virtual-image.c:216 401s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:2019): libfprint-virtual_device_connection-DEBUG: 00:54:10.679: 7399818740629: ../libfprint/drivers/virtual-device-listener.c:153 401s # libfprint-image_device-DEBUG: Image device open completed 401s # libfprint-device-DEBUG: Device reported open completion 401s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 401s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 401s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:2019): libfprint-virtual_image-DEBUG: 00:54:10.780: 7399818841397: ../libfprint/drivers/virtual-image.c:244 401s # libfprint-image_device-DEBUG: Image device close completed 401s # libfprint-device-DEBUG: Device reported close completion 401s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 401s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 401s # GLib-DEBUG: unsetenv() is not thread-safe and should not be used after threads are created 401s ok 7 /device/sync/get_name 401s # GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used after threads are created 401s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 401s # libfprint-tod-DEBUG: Impossible to load the shared drivers dir Error opening directory ?/usr/lib/arm-linux-gnueabihf/libfprint-2/tod-1?: No such file or directory 401s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0003 401s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 401s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0002 401s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_IMAGE, /tmp/libfprint-M4WG22/virtual_image.socket 401s # libfprint-context-DEBUG: created 401s # libfprint-device-DEBUG: Device reported probe completion 401s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 401s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 401s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:2019): libfprint-virtual_image-DEBUG: 00:54:10.884: 7399818945712: ../libfprint/drivers/virtual-image.c:216 401s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:2019): libfprint-virtual_device_connection-DEBUG: 00:54:10.884: 7399818945738: ../libfprint/drivers/virtual-device-listener.c:153 402s # libfprint-image_device-DEBUG: Image device open completed 402s # libfprint-device-DEBUG: Device reported open completion 402s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 402s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 402s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:2019): libfprint-virtual_image-DEBUG: 00:54:10.985: 7399819046176: ../libfprint/drivers/virtual-image.c:244 402s # libfprint-image_device-DEBUG: Image device close completed 402s # libfprint-device-DEBUG: Device reported close completion 402s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 402s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 402s # GLib-DEBUG: unsetenv() is not thread-safe and should not be used after threads are created 402s ok 8 /device/sync/get_scan_type 402s # GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used after threads are created 402s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 402s # libfprint-tod-DEBUG: Impossible to load the shared drivers dir Error opening directory ?/usr/lib/arm-linux-gnueabihf/libfprint-2/tod-1?: No such file or directory 402s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0003 402s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 402s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0002 402s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_IMAGE, /tmp/libfprint-OX8Z12/virtual_image.socket 402s # libfprint-context-DEBUG: created 402s # libfprint-device-DEBUG: Device reported probe completion 402s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 402s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 402s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:2019): libfprint-virtual_image-DEBUG: 00:54:11.089: 7399819150456: ../libfprint/drivers/virtual-image.c:216 402s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:2019): libfprint-virtual_device_connection-DEBUG: 00:54:11.089: 7399819150482: ../libfprint/drivers/virtual-device-listener.c:153 402s # libfprint-image_device-DEBUG: Image device open completed 402s # libfprint-device-DEBUG: Device reported open completion 402s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 402s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 402s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:2019): libfprint-virtual_image-DEBUG: 00:54:11.191: 7399819252421: ../libfprint/drivers/virtual-image.c:244 402s # libfprint-image_device-DEBUG: Image device close completed 402s # libfprint-device-DEBUG: Device reported close completion 402s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 402s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 402s # GLib-DEBUG: unsetenv() is not thread-safe and should not be used after threads are created 402s ok 9 /device/sync/get_finger_status 402s # GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used after threads are created 402s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 402s # libfprint-tod-DEBUG: Impossible to load the shared drivers dir Error opening directory ?/usr/lib/arm-linux-gnueabihf/libfprint-2/tod-1?: No such file or directory 402s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0003 402s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 402s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0002 402s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_IMAGE, /tmp/libfprint-2I2612/virtual_image.socket 402s # libfprint-context-DEBUG: created 402s # libfprint-device-DEBUG: Device reported probe completion 402s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 402s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 402s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:2019): libfprint-virtual_image-DEBUG: 00:54:11.295: 7399819356653: ../libfprint/drivers/virtual-image.c:216 402s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:2019): libfprint-virtual_device_connection-DEBUG: 00:54:11.295: 7399819356685: ../libfprint/drivers/virtual-device-listener.c:153 402s # libfprint-image_device-DEBUG: Image device open completed 402s # libfprint-device-DEBUG: Device reported open completion 402s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 402s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 402s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:2019): libfprint-virtual_image-DEBUG: 00:54:11.396: 7399819457193: ../libfprint/drivers/virtual-image.c:244 402s # libfprint-image_device-DEBUG: Image device close completed 402s # libfprint-device-DEBUG: Device reported close completion 402s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 402s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 402s # GLib-DEBUG: unsetenv() is not thread-safe and should not be used after threads are created 402s ok 10 /device/sync/get_nr_enroll_stages 402s # GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used after threads are created 402s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 402s # libfprint-tod-DEBUG: Impossible to load the shared drivers dir Error opening directory ?/usr/lib/arm-linux-gnueabihf/libfprint-2/tod-1?: No such file or directory 402s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0003 402s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 402s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0002 402s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_IMAGE, /tmp/libfprint-RR2812/virtual_image.socket 402s # libfprint-context-DEBUG: created 402s # libfprint-device-DEBUG: Device reported probe completion 402s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 402s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 402s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:2019): libfprint-virtual_image-DEBUG: 00:54:11.503: 7399819564226: ../libfprint/drivers/virtual-image.c:216 402s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:2019): libfprint-virtual_device_connection-DEBUG: 00:54:11.503: 7399819564302: ../libfprint/drivers/virtual-device-listener.c:153 402s # libfprint-image_device-DEBUG: Image device open completed 402s # libfprint-device-DEBUG: Device reported open completion 402s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 402s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 402s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:2019): libfprint-virtual_image-DEBUG: 00:54:11.604: 7399819665227: ../libfprint/drivers/virtual-image.c:244 402s # libfprint-image_device-DEBUG: Image device close completed 402s # libfprint-device-DEBUG: Device reported close completion 402s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 402s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 402s # GLib-DEBUG: unsetenv() is not thread-safe and should not be used after threads are created 402s ok 11 /device/sync/supports_identify 402s # GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used after threads are created 402s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 402s # libfprint-tod-DEBUG: Impossible to load the shared drivers dir Error opening directory ?/usr/lib/arm-linux-gnueabihf/libfprint-2/tod-1?: No such file or directory 402s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0003 402s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 402s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0002 402s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_IMAGE, /tmp/libfprint-ZWGG22/virtual_image.socket 402s # libfprint-context-DEBUG: created 402s # libfprint-device-DEBUG: Device reported probe completion 402s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 402s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 402s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:2019): libfprint-virtual_image-DEBUG: 00:54:11.710: 7399819771894: ../libfprint/drivers/virtual-image.c:216 402s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:2019): libfprint-virtual_device_connection-DEBUG: 00:54:11.711: 7399819771959: ../libfprint/drivers/virtual-device-listener.c:153 402s # libfprint-image_device-DEBUG: Image device open completed 402s # libfprint-device-DEBUG: Device reported open completion 402s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 402s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 402s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:2019): libfprint-virtual_image-DEBUG: 00:54:11.812: 7399819873376: ../libfprint/drivers/virtual-image.c:244 402s Executing: libfprint-2/fp-device.test 402s # libfprint-image_device-DEBUG: Image device close completed 402s # libfprint-device-DEBUG: Device reported close completion 402s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 402s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 402s # GLib-DEBUG: unsetenv() is not thread-safe and should not be used after threads are created 402s ok 12 /device/sync/supports_capture 402s # GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used after threads are created 402s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 402s # libfprint-tod-DEBUG: Impossible to load the shared drivers dir Error opening directory ?/usr/lib/arm-linux-gnueabihf/libfprint-2/tod-1?: No such file or directory 402s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0003 402s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 402s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0002 402s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_IMAGE, /tmp/libfprint-R2LH22/virtual_image.socket 402s # libfprint-context-DEBUG: created 402s # libfprint-device-DEBUG: Device reported probe completion 402s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 402s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 402s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:2019): libfprint-virtual_image-DEBUG: 00:54:11.920: 7399819981083: ../libfprint/drivers/virtual-image.c:216 402s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:2019): libfprint-virtual_device_connection-DEBUG: 00:54:11.920: 7399819981161: ../libfprint/drivers/virtual-device-listener.c:153 403s # libfprint-image_device-DEBUG: Image device open completed 403s # libfprint-device-DEBUG: Device reported open completion 403s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 403s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 403s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:2019): libfprint-virtual_image-DEBUG: 00:54:12.021: 7399820082153: ../libfprint/drivers/virtual-image.c:244 403s # libfprint-image_device-DEBUG: Image device close completed 403s # libfprint-device-DEBUG: Device reported close completion 403s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 403s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 403s # GLib-DEBUG: unsetenv() is not thread-safe and should not be used after threads are created 403s ok 13 /device/sync/has_storage 403s # Start of open tests 403s # GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used after threads are created 403s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 403s # libfprint-tod-DEBUG: Impossible to load the shared drivers dir Error opening directory ?/usr/lib/arm-linux-gnueabihf/libfprint-2/tod-1?: No such file or directory 403s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0003 403s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 403s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0002 403s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_IMAGE, /tmp/libfprint-KMY012/virtual_image.socket 403s # libfprint-context-DEBUG: created 403s # libfprint-device-DEBUG: Device reported probe completion 403s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 403s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 403s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:2019): libfprint-virtual_image-DEBUG: 00:54:12.128: 7399820189195: ../libfprint/drivers/virtual-image.c:216 403s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:2019): libfprint-virtual_device_connection-DEBUG: 00:54:12.128: 7399820189240: ../libfprint/drivers/virtual-device-listener.c:153 403s # libfprint-image_device-DEBUG: Image device open completed 403s # libfprint-device-DEBUG: Device reported open completion 403s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 403s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 403s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:2019): libfprint-virtual_image-DEBUG: 00:54:12.229: 7399820290201: ../libfprint/drivers/virtual-image.c:244 403s # libfprint-image_device-DEBUG: Image device close completed 403s # libfprint-device-DEBUG: Device reported close completion 403s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 403s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 403s # GLib-DEBUG: unsetenv() is not thread-safe and should not be used after threads are created 403s ok 14 /device/sync/open/notify 403s # End of open tests 403s # Start of close tests 403s # GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used after threads are created 403s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 403s # libfprint-tod-DEBUG: Impossible to load the shared drivers dir Error opening directory ?/usr/lib/arm-linux-gnueabihf/libfprint-2/tod-1?: No such file or directory 403s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0003 403s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 403s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0002 403s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_IMAGE, /tmp/libfprint-JYM512/virtual_image.socket 403s # libfprint-context-DEBUG: created 403s # libfprint-device-DEBUG: Device reported probe completion 403s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 403s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 403s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:2019): libfprint-virtual_image-DEBUG: 00:54:12.336: 7399820397534: ../libfprint/drivers/virtual-image.c:216 403s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:2019): libfprint-virtual_device_connection-DEBUG: 00:54:12.336: 7399820397579: ../libfprint/drivers/virtual-device-listener.c:153 403s # libfprint-image_device-DEBUG: Image device open completed 403s # libfprint-device-DEBUG: Device reported open completion 403s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 403s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 403s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:2019): libfprint-virtual_image-DEBUG: 00:54:12.437: 7399820498816: ../libfprint/drivers/virtual-image.c:244 403s # libfprint-image_device-DEBUG: Image device close completed 403s # libfprint-device-DEBUG: Device reported close completion 403s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 403s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 403s # GLib-DEBUG: unsetenv() is not thread-safe and should not be used after threads are created 403s ok 15 /device/sync/close/notify 403s # End of close tests 403s # Start of identify tests 403s # GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used after threads are created 403s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 403s # libfprint-tod-DEBUG: Impossible to load the shared drivers dir Error opening directory ?/usr/lib/arm-linux-gnueabihf/libfprint-2/tod-1?: No such file or directory 403s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0003 403s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 403s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0002 403s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_IMAGE, /tmp/libfprint-CYDC22/virtual_image.socket 403s # libfprint-context-DEBUG: created 403s # libfprint-device-DEBUG: Device reported probe completion 403s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 403s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 403s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:2019): libfprint-virtual_image-DEBUG: 00:54:12.544: 7399820605831: ../libfprint/drivers/virtual-image.c:216 403s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:2019): libfprint-virtual_device_connection-DEBUG: 00:54:12.544: 7399820605874: ../libfprint/drivers/virtual-device-listener.c:153 403s # libfprint-image_device-DEBUG: Image device open completed 403s # libfprint-device-DEBUG: Device reported open completion 403s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 403s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 403s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:2019): libfprint-virtual_image-DEBUG: 00:54:12.646: 7399820707153: ../libfprint/drivers/virtual-image.c:244 403s # libfprint-image_device-DEBUG: Image device close completed 403s # libfprint-device-DEBUG: Device reported close completion 403s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 403s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 403s # GLib-DEBUG: unsetenv() is not thread-safe and should not be used after threads are created 403s ok 16 /device/sync/identify/cancelled 403s # GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used after threads are created 403s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 403s # libfprint-tod-DEBUG: Impossible to load the shared drivers dir Error opening directory ?/usr/lib/arm-linux-gnueabihf/libfprint-2/tod-1?: No such file or directory 403s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0003 403s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 403s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0002 403s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_IMAGE, /tmp/libfprint-HQ8D22/virtual_image.socket 403s # libfprint-context-DEBUG: created 403s # libfprint-device-DEBUG: Device reported probe completion 403s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 403s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 403s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:2019): libfprint-virtual_image-DEBUG: 00:54:12.753: 7399820814568: ../libfprint/drivers/virtual-image.c:216 403s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:2019): libfprint-virtual_device_connection-DEBUG: 00:54:12.753: 7399820814616: ../libfprint/drivers/virtual-device-listener.c:153 403s # libfprint-image_device-DEBUG: Image device open completed 403s # libfprint-device-DEBUG: Device reported open completion 403s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 403s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 403s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:2019): libfprint-virtual_image-DEBUG: 00:54:12.854: 7399820915481: ../libfprint/drivers/virtual-image.c:244 403s # libfprint-image_device-DEBUG: Image device close completed 403s # libfprint-device-DEBUG: Device reported close completion 403s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 403s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 403s # GLib-DEBUG: unsetenv() is not thread-safe and should not be used after threads are created 403s ok 17 /device/sync/identify/null-prints 403s # End of identify tests 403s # End of sync tests 403s # End of device tests 404s PASS: libfprint-2/fp-device.test 404s Running test: libfprint-2/driver-vfs5011.test 404s ** (umockdev-run:2059): DEBUG: 00:54:13.010: umockdev.vala:127: Created udev test bed /tmp/umockdev.V26012 404s ** (umockdev-run:2059): DEBUG: 00:54:13.010: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0/usb2/2-6 404s ** (umockdev-run:2059): DEBUG: 00:54:13.012: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0/usb2/2-6 (subsystem usb) 404s ** (umockdev-run:2059): DEBUG: 00:54:13.015: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.V26012/dev/bus/usb/002/017 404s ** (umockdev-run:2059): DEBUG: 00:54:13.016: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0/usb2 404s ** (umockdev-run:2059): DEBUG: 00:54:13.017: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0/usb2 (subsystem usb) 404s ** (umockdev-run:2059): DEBUG: 00:54:13.021: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.V26012/dev/bus/usb/002/001 404s ** (umockdev-run:2059): DEBUG: 00:54:13.021: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0 404s ** (umockdev-run:2059): DEBUG: 00:54:13.022: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0 (subsystem pci) 404s (umockdev-run:2059): GLib-GIO-DEBUG: 00:54:13.025: _g_io_module_get_default: Found default implementation local (GLocalVfs) for ?gio-vfs? 404s (process:2063): libfprint-context-DEBUG: 00:54:13.150: Initializing FpContext (libfprint version 1.94.8+tod1) 404s (process:2063): libfprint-tod-DEBUG: 00:54:13.151: Impossible to load the shared drivers dir Error opening directory “/usr/lib/arm-linux-gnueabihf/libfprint-2/tod-1”: No such file or directory 404s (process:2063): libfprint-context-DEBUG: 00:54:13.154: No driver found for USB device 1D6B:0002 404s (process:2063): libfprint-device-DEBUG: 00:54:13.155: Device reported probe completion 404s (process:2063): libfprint-device-DEBUG: 00:54:13.155: Completing action FPI_DEVICE_ACTION_PROBE in idle! 404s (process:2063): libfprint-device-DEBUG: 00:54:13.155: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 404s (process:2063): libfprint-SSM-DEBUG: 00:54:13.158: [vfs5011] DEV_OPEN_NUM_STATES entering state 0 404s (process:2063): libfprint-SSM-DEBUG: 00:54:13.158: [vfs5011] DEVICE OPEN entering state 0 404s (process:2063): libfprint-vfs5011-DEBUG: 00:54:13.158: Sending vfs5011_cmd_01 404s (process:2063): libfprint-SSM-DEBUG: 00:54:13.159: [vfs5011] DEVICE OPEN entering state 1 404s (process:2063): libfprint-vfs5011-DEBUG: 00:54:13.159: Receiving 64 bytes 404s (process:2063): libfprint-vfs5011-DEBUG: 00:54:13.160: Got 38 bytes out of 64 404s (process:2063): libfprint-SSM-DEBUG: 00:54:13.160: [vfs5011] DEVICE OPEN entering state 2 404s (process:2063): libfprint-vfs5011-DEBUG: 00:54:13.160: Sending vfs5011_cmd_19 404s (process:2063): libfprint-SSM-DEBUG: 00:54:13.161: [vfs5011] DEVICE OPEN entering state 3 404s (process:2063): libfprint-vfs5011-DEBUG: 00:54:13.161: Receiving 64 bytes 404s (process:2063): libfprint-vfs5011-DEBUG: 00:54:13.161: Got 64 bytes out of 64 404s (process:2063): libfprint-SSM-DEBUG: 00:54:13.161: [vfs5011] DEVICE OPEN entering state 4 404s (process:2063): libfprint-vfs5011-DEBUG: 00:54:13.161: Receiving 64 bytes 404s (process:2063): libfprint-vfs5011-DEBUG: 00:54:13.162: Got 4 bytes out of 64 404s (process:2063): libfprint-SSM-DEBUG: 00:54:13.162: [vfs5011] DEVICE OPEN entering state 5 404s (process:2063): libfprint-vfs5011-DEBUG: 00:54:13.162: Sending vfs5011_init_00 404s (process:2063): libfprint-SSM-DEBUG: 00:54:13.165: [vfs5011] DEVICE OPEN entering state 6 404s (process:2063): libfprint-vfs5011-DEBUG: 00:54:13.165: Receiving 64 bytes 404s (process:2063): libfprint-vfs5011-DEBUG: 00:54:13.165: Got 6 bytes out of 64 404s (process:2063): libfprint-SSM-DEBUG: 00:54:13.165: [vfs5011] DEVICE OPEN entering state 7 404s (process:2063): libfprint-vfs5011-DEBUG: 00:54:13.165: Sending vfs5011_init_01 404s (process:2063): libfprint-SSM-DEBUG: 00:54:13.166: [vfs5011] DEVICE OPEN entering state 8 404s (process:2063): libfprint-vfs5011-DEBUG: 00:54:13.166: Receiving 64 bytes 404s (process:2063): libfprint-vfs5011-DEBUG: 00:54:13.167: Got 7 bytes out of 64 404s (process:2063): libfprint-SSM-DEBUG: 00:54:13.167: [vfs5011] DEVICE OPEN entering state 9 404s (process:2063): libfprint-vfs5011-DEBUG: 00:54:13.167: Sending vfs5011_init_02 404s (process:2063): libfprint-SSM-DEBUG: 00:54:13.167: [vfs5011] DEVICE OPEN entering state 10 404s (process:2063): libfprint-vfs5011-DEBUG: 00:54:13.167: Receiving 64 bytes 404s (process:2063): libfprint-SSM-DEBUG: 00:54:13.168: [vfs5011] DEVICE OPEN entering state 11 404s (process:2063): libfprint-vfs5011-DEBUG: 00:54:13.168: Sending vfs5011_cmd_01 404s (process:2063): libfprint-SSM-DEBUG: 00:54:13.168: [vfs5011] DEVICE OPEN entering state 12 404s (process:2063): libfprint-vfs5011-DEBUG: 00:54:13.168: Receiving 64 bytes 404s (process:2063): libfprint-vfs5011-DEBUG: 00:54:13.169: Got 38 bytes out of 64 404s (process:2063): libfprint-SSM-DEBUG: 00:54:13.169: [vfs5011] DEVICE OPEN entering state 13 404s (process:2063): libfprint-vfs5011-DEBUG: 00:54:13.169: Sending vfs5011_cmd_1A 404s (process:2063): libfprint-SSM-DEBUG: 00:54:13.169: [vfs5011] DEVICE OPEN entering state 14 404s (process:2063): libfprint-vfs5011-DEBUG: 00:54:13.169: Receiving 64 bytes 404s (process:2063): libfprint-SSM-DEBUG: 00:54:13.170: [vfs5011] DEVICE OPEN entering state 15 404s (process:2063): libfprint-vfs5011-DEBUG: 00:54:13.170: Sending vfs5011_init_03 404s (process:2063): libfprint-SSM-DEBUG: 00:54:13.172: [vfs5011] DEVICE OPEN entering state 16 404s (process:2063): libfprint-vfs5011-DEBUG: 00:54:13.172: Receiving 64 bytes 404s (process:2063): libfprint-SSM-DEBUG: 00:54:13.173: [vfs5011] DEVICE OPEN entering state 17 404s (process:2063): libfprint-vfs5011-DEBUG: 00:54:13.173: Sending vfs5011_init_04 404s (process:2063): libfprint-SSM-DEBUG: 00:54:13.174: [vfs5011] DEVICE OPEN entering state 18 404s (process:2063): libfprint-vfs5011-DEBUG: 00:54:13.174: Receiving 64 bytes 404s (process:2063): libfprint-SSM-DEBUG: 00:54:13.174: [vfs5011] DEVICE OPEN entering state 19 404s (process:2063): libfprint-vfs5011-DEBUG: 00:54:13.174: Receiving 256 bytes 404s (process:2063): libfprint-vfs5011-DEBUG: 00:54:13.175: Got 256 bytes out of 256 404s (process:2063): libfprint-SSM-DEBUG: 00:54:13.175: [vfs5011] DEVICE OPEN entering state 20 404s (process:2063): libfprint-vfs5011-DEBUG: 00:54:13.175: Receiving 64 bytes 404s (process:2063): libfprint-vfs5011-DEBUG: 00:54:13.175: Got 32 bytes out of 64 404s (process:2063): libfprint-SSM-DEBUG: 00:54:13.175: [vfs5011] DEVICE OPEN entering state 21 404s (process:2063): libfprint-vfs5011-DEBUG: 00:54:13.175: Sending vfs5011_cmd_1A 404s (process:2063): libfprint-SSM-DEBUG: 00:54:13.176: [vfs5011] DEVICE OPEN entering state 22 404s (process:2063): libfprint-vfs5011-DEBUG: 00:54:13.176: Receiving 64 bytes 404s (process:2063): libfprint-SSM-DEBUG: 00:54:13.176: [vfs5011] DEVICE OPEN entering state 23 404s (process:2063): libfprint-vfs5011-DEBUG: 00:54:13.176: Sending vfs5011_init_05 404s (process:2063): libfprint-SSM-DEBUG: 00:54:13.177: [vfs5011] DEVICE OPEN entering state 24 404s (process:2063): libfprint-vfs5011-DEBUG: 00:54:13.177: Receiving 64 bytes 404s (process:2063): libfprint-SSM-DEBUG: 00:54:13.177: [vfs5011] DEVICE OPEN entering state 25 404s (process:2063): libfprint-vfs5011-DEBUG: 00:54:13.177: Sending vfs5011_cmd_01 404s (process:2063): libfprint-SSM-DEBUG: 00:54:13.178: [vfs5011] DEVICE OPEN entering state 26 404s (process:2063): libfprint-vfs5011-DEBUG: 00:54:13.178: Receiving 64 bytes 404s (process:2063): libfprint-vfs5011-DEBUG: 00:54:13.179: Got 38 bytes out of 64 404s (process:2063): libfprint-SSM-DEBUG: 00:54:13.179: [vfs5011] DEVICE OPEN entering state 27 404s (process:2063): libfprint-vfs5011-DEBUG: 00:54:13.179: Sending vfs5011_init_06 404s (process:2063): libfprint-SSM-DEBUG: 00:54:13.179: [vfs5011] DEVICE OPEN entering state 28 404s (process:2063): libfprint-vfs5011-DEBUG: 00:54:13.179: Receiving 64 bytes 404s (process:2063): libfprint-SSM-DEBUG: 00:54:13.180: [vfs5011] DEVICE OPEN entering state 29 404s (process:2063): libfprint-vfs5011-DEBUG: 00:54:13.180: Receiving 17216 bytes 404s (process:2063): libfprint-vfs5011-DEBUG: 00:54:13.181: Got 17216 bytes out of 17216 404s (process:2063): libfprint-SSM-DEBUG: 00:54:13.181: [vfs5011] DEVICE OPEN entering state 30 404s (process:2063): libfprint-vfs5011-DEBUG: 00:54:13.181: Receiving 32 bytes 404s (process:2063): libfprint-vfs5011-DEBUG: 00:54:13.181: Got 32 bytes out of 32 404s (process:2063): libfprint-SSM-DEBUG: 00:54:13.181: [vfs5011] DEVICE OPEN entering state 31 404s (process:2063): libfprint-vfs5011-DEBUG: 00:54:13.181: Sending vfs5011_init_07 404s (process:2063): libfprint-SSM-DEBUG: 00:54:13.182: [vfs5011] DEVICE OPEN entering state 32 404s (process:2063): libfprint-vfs5011-DEBUG: 00:54:13.182: Receiving 64 bytes 404s (process:2063): libfprint-SSM-DEBUG: 00:54:13.183: [vfs5011] DEVICE OPEN entering state 33 404s (process:2063): libfprint-vfs5011-DEBUG: 00:54:13.183: Receiving 45056 bytes 404s (process:2063): libfprint-vfs5011-DEBUG: 00:54:13.183: Got 45056 bytes out of 45056 404s (process:2063): libfprint-SSM-DEBUG: 00:54:13.183: [vfs5011] DEVICE OPEN entering state 34 404s (process:2063): libfprint-vfs5011-DEBUG: 00:54:13.183: Sending vfs5011_init_08 404s (process:2063): libfprint-SSM-DEBUG: 00:54:13.184: [vfs5011] DEVICE OPEN entering state 35 404s (process:2063): libfprint-vfs5011-DEBUG: 00:54:13.184: Receiving 64 bytes 404s (process:2063): libfprint-SSM-DEBUG: 00:54:13.184: [vfs5011] DEVICE OPEN entering state 36 404s (process:2063): libfprint-vfs5011-DEBUG: 00:54:13.184: Receiving 16896 bytes 404s (process:2063): libfprint-vfs5011-DEBUG: 00:54:13.185: Got 16896 bytes out of 16896 404s (process:2063): libfprint-SSM-DEBUG: 00:54:13.185: [vfs5011] DEVICE OPEN entering state 37 404s (process:2063): libfprint-vfs5011-DEBUG: 00:54:13.185: Sending vfs5011_init_09 404s (process:2063): libfprint-SSM-DEBUG: 00:54:13.186: [vfs5011] DEVICE OPEN entering state 38 404s (process:2063): libfprint-vfs5011-DEBUG: 00:54:13.186: Receiving 64 bytes 404s (process:2063): libfprint-SSM-DEBUG: 00:54:13.186: [vfs5011] DEVICE OPEN entering state 39 404s (process:2063): libfprint-vfs5011-DEBUG: 00:54:13.186: Receiving 4928 bytes 404s (process:2063): libfprint-vfs5011-DEBUG: 00:54:13.187: Got 4928 bytes out of 4928 404s (process:2063): libfprint-SSM-DEBUG: 00:54:13.187: [vfs5011] DEVICE OPEN entering state 40 404s (process:2063): libfprint-vfs5011-DEBUG: 00:54:13.187: Sending vfs5011_init_10 404s (process:2063): libfprint-SSM-DEBUG: 00:54:13.187: [vfs5011] DEVICE OPEN entering state 41 404s (process:2063): libfprint-vfs5011-DEBUG: 00:54:13.187: Receiving 64 bytes 404s (process:2063): libfprint-SSM-DEBUG: 00:54:13.188: [vfs5011] DEVICE OPEN entering state 42 404s (process:2063): libfprint-vfs5011-DEBUG: 00:54:13.188: Receiving 5632 bytes 404s (process:2063): libfprint-vfs5011-DEBUG: 00:54:13.189: Got 5632 bytes out of 5632 404s (process:2063): libfprint-SSM-DEBUG: 00:54:13.189: [vfs5011] DEVICE OPEN entering state 43 404s (process:2063): libfprint-vfs5011-DEBUG: 00:54:13.189: Sending vfs5011_init_11 404s (process:2063): libfprint-SSM-DEBUG: 00:54:13.189: [vfs5011] DEVICE OPEN entering state 44 404s (process:2063): libfprint-vfs5011-DEBUG: 00:54:13.189: Receiving 64 bytes 404s (process:2063): libfprint-SSM-DEBUG: 00:54:13.190: [vfs5011] DEVICE OPEN entering state 45 404s (process:2063): libfprint-vfs5011-DEBUG: 00:54:13.190: Receiving 5632 bytes 404s (process:2063): libfprint-vfs5011-DEBUG: 00:54:13.190: Got 5632 bytes out of 5632 404s (process:2063): libfprint-SSM-DEBUG: 00:54:13.190: [vfs5011] DEVICE OPEN entering state 46 404s (process:2063): libfprint-vfs5011-DEBUG: 00:54:13.190: Sending vfs5011_init_12 404s (process:2063): libfprint-SSM-DEBUG: 00:54:13.191: [vfs5011] DEVICE OPEN entering state 47 404s (process:2063): libfprint-vfs5011-DEBUG: 00:54:13.191: Receiving 64 bytes 404s (process:2063): libfprint-SSM-DEBUG: 00:54:13.191: [vfs5011] DEVICE OPEN entering state 48 404s (process:2063): libfprint-vfs5011-DEBUG: 00:54:13.191: Receiving 3328 bytes 404s (process:2063): libfprint-vfs5011-DEBUG: 00:54:13.192: Got 3328 bytes out of 3328 404s (process:2063): libfprint-SSM-DEBUG: 00:54:13.192: [vfs5011] DEVICE OPEN entering state 49 404s (process:2063): libfprint-vfs5011-DEBUG: 00:54:13.192: Receiving 64 bytes 404s (process:2063): libfprint-vfs5011-DEBUG: 00:54:13.192: Got 32 bytes out of 64 404s (process:2063): libfprint-SSM-DEBUG: 00:54:13.192: [vfs5011] DEVICE OPEN entering state 50 404s (process:2063): libfprint-vfs5011-DEBUG: 00:54:13.192: Sending vfs5011_init_13 404s (process:2063): libfprint-SSM-DEBUG: 00:54:13.193: [vfs5011] DEVICE OPEN entering state 51 404s (process:2063): libfprint-vfs5011-DEBUG: 00:54:13.193: Receiving 64 bytes 404s (process:2063): libfprint-SSM-DEBUG: 00:54:13.193: [vfs5011] DEVICE OPEN entering state 52 404s (process:2063): libfprint-vfs5011-DEBUG: 00:54:13.193: Sending vfs5011_cmd_1A 404s (process:2063): libfprint-SSM-DEBUG: 00:54:13.194: [vfs5011] DEVICE OPEN entering state 53 404s (process:2063): libfprint-vfs5011-DEBUG: 00:54:13.194: Receiving 64 bytes 404s (process:2063): libfprint-SSM-DEBUG: 00:54:13.194: [vfs5011] DEVICE OPEN entering state 54 404s (process:2063): libfprint-vfs5011-DEBUG: 00:54:13.194: Sending vfs5011_init_03 404s (process:2063): libfprint-SSM-DEBUG: 00:54:13.195: [vfs5011] DEVICE OPEN entering state 55 404s (process:2063): libfprint-vfs5011-DEBUG: 00:54:13.195: Receiving 64 bytes 404s (process:2063): libfprint-SSM-DEBUG: 00:54:13.196: [vfs5011] DEVICE OPEN entering state 56 404s (process:2063): libfprint-vfs5011-DEBUG: 00:54:13.196: Sending vfs5011_init_14 404s (process:2063): libfprint-SSM-DEBUG: 00:54:13.196: [vfs5011] DEVICE OPEN entering state 57 404s (process:2063): libfprint-vfs5011-DEBUG: 00:54:13.196: Receiving 64 bytes 404s (process:2063): libfprint-SSM-DEBUG: 00:54:13.198: [vfs5011] DEVICE OPEN entering state 58 404s (process:2063): libfprint-vfs5011-DEBUG: 00:54:13.198: Receiving 4800 bytes 404s (process:2063): libfprint-vfs5011-DEBUG: 00:54:13.198: Got 4800 bytes out of 4800 404s (process:2063): libfprint-SSM-DEBUG: 00:54:13.198: [vfs5011] DEVICE OPEN entering state 59 404s (process:2063): libfprint-vfs5011-DEBUG: 00:54:13.198: Sending vfs5011_cmd_1A 404s (process:2063): libfprint-SSM-DEBUG: 00:54:13.199: [vfs5011] DEVICE OPEN entering state 60 404s (process:2063): libfprint-vfs5011-DEBUG: 00:54:13.199: Receiving 64 bytes 404s (process:2063): libfprint-SSM-DEBUG: 00:54:13.200: [vfs5011] DEVICE OPEN entering state 61 404s (process:2063): libfprint-vfs5011-DEBUG: 00:54:13.200: Sending vfs5011_init_02 404s (process:2063): libfprint-SSM-DEBUG: 00:54:13.200: [vfs5011] DEVICE OPEN entering state 62 404s (process:2063): libfprint-vfs5011-DEBUG: 00:54:13.200: Receiving 64 bytes 404s (process:2063): libfprint-SSM-DEBUG: 00:54:13.201: [vfs5011] DEVICE OPEN entering state 63 404s (process:2063): libfprint-vfs5011-DEBUG: 00:54:13.201: Sending vfs5011_cmd_27 404s (process:2063): libfprint-SSM-DEBUG: 00:54:13.201: [vfs5011] DEVICE OPEN entering state 64 404s (process:2063): libfprint-vfs5011-DEBUG: 00:54:13.201: Receiving 64 bytes 404s (process:2063): libfprint-vfs5011-DEBUG: 00:54:13.202: Got 22 bytes out of 64 404s (process:2063): libfprint-SSM-DEBUG: 00:54:13.202: [vfs5011] DEVICE OPEN entering state 65 404s (process:2063): libfprint-vfs5011-DEBUG: 00:54:13.202: Sending vfs5011_cmd_1A 404s (process:2063): libfprint-SSM-DEBUG: 00:54:13.203: [vfs5011] DEVICE OPEN entering state 66 404s (process:2063): libfprint-vfs5011-DEBUG: 00:54:13.203: Receiving 64 bytes 404s (process:2063): libfprint-SSM-DEBUG: 00:54:13.203: [vfs5011] DEVICE OPEN entering state 67 404s (process:2063): libfprint-vfs5011-DEBUG: 00:54:13.203: Sending vfs5011_init_15 404s (process:2063): libfprint-SSM-DEBUG: 00:54:13.204: [vfs5011] DEVICE OPEN entering state 68 404s (process:2063): libfprint-vfs5011-DEBUG: 00:54:13.204: Receiving 64 bytes 404s (process:2063): libfprint-SSM-DEBUG: 00:54:13.204: [vfs5011] DEVICE OPEN entering state 69 404s (process:2063): libfprint-vfs5011-DEBUG: 00:54:13.204: Sending vfs5011_init_16 404s (process:2063): libfprint-SSM-DEBUG: 00:54:13.205: [vfs5011] DEVICE OPEN entering state 70 404s (process:2063): libfprint-vfs5011-DEBUG: 00:54:13.205: Receiving 2368 bytes 404s (process:2063): libfprint-vfs5011-DEBUG: 00:54:13.206: Got 2368 bytes out of 2368 404s (process:2063): libfprint-SSM-DEBUG: 00:54:13.206: [vfs5011] DEVICE OPEN entering state 71 404s (process:2063): libfprint-vfs5011-DEBUG: 00:54:13.206: Receiving 64 bytes 404s (process:2063): libfprint-vfs5011-DEBUG: 00:54:13.207: Got 36 bytes out of 64 404s (process:2063): libfprint-SSM-DEBUG: 00:54:13.207: [vfs5011] DEVICE OPEN entering state 72 404s (process:2063): libfprint-vfs5011-DEBUG: 00:54:13.207: Receiving 4800 bytes 404s (process:2063): libfprint-vfs5011-DEBUG: 00:54:13.207: Got 4800 bytes out of 4800 404s (process:2063): libfprint-SSM-DEBUG: 00:54:13.207: [vfs5011] DEVICE OPEN entering state 73 404s (process:2063): libfprint-vfs5011-DEBUG: 00:54:13.207: Sending vfs5011_init_17 404s (process:2063): libfprint-SSM-DEBUG: 00:54:13.208: [vfs5011] DEVICE OPEN entering state 74 404s (process:2063): libfprint-vfs5011-DEBUG: 00:54:13.208: Receiving 64 bytes 404s (process:2063): libfprint-SSM-DEBUG: 00:54:13.208: [vfs5011] DEVICE OPEN entering state 75 404s (process:2063): libfprint-vfs5011-DEBUG: 00:54:13.208: Sending vfs5011_init_18 404s (process:2063): libfprint-SSM-DEBUG: 00:54:13.209: [vfs5011] DEVICE OPEN entering state 76 404s (process:2063): libfprint-vfs5011-DEBUG: 00:54:13.209: Receiving 64 bytes 404s (process:2063): libfprint-SSM-DEBUG: 00:54:13.210: [vfs5011] DEVICE OPEN completed successfully 404s (process:2063): libfprint-SSM-DEBUG: 00:54:13.210: [vfs5011] DEV_OPEN_NUM_STATES completed successfully 404s (process:2063): libfprint-image_device-DEBUG: 00:54:13.210: Image device open completed 404s (process:2063): libfprint-device-DEBUG: 00:54:13.210: Device reported open completion 404s (process:2063): libfprint-device-DEBUG: 00:54:13.210: Completing action FPI_DEVICE_ACTION_OPEN in idle! 404s (process:2063): libfprint-device-DEBUG: 00:54:13.210: Updated temperature model after 0.06 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 404s (process:2063): libfprint-device-DEBUG: 00:54:13.210: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 404s (process:2063): libfprint-image_device-DEBUG: 00:54:13.210: Activating image device 404s (process:2063): libfprint-image_device-DEBUG: 00:54:13.210: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING 404s (process:2063): libfprint-vfs5011-DEBUG: 00:54:13.210: device initialized 404s (process:2063): libfprint-vfs5011-DEBUG: 00:54:13.210: creating ssm 404s (process:2063): libfprint-vfs5011-DEBUG: 00:54:13.210: starting ssm 404s (process:2063): libfprint-SSM-DEBUG: 00:54:13.210: [vfs5011] DEV_ACTIVATE_NUM_STATES entering state 0 404s (process:2063): libfprint-vfs5011-DEBUG: 00:54:13.210: main_loop: state 0 404s (process:2063): libfprint-SSM-DEBUG: 00:54:13.210: [vfs5011] ACTIVATE REQUEST entering state 0 404s (process:2063): libfprint-vfs5011-DEBUG: 00:54:13.210: Sending vfs5011_cmd_04 404s (process:2063): libfprint-vfs5011-DEBUG: 00:54:13.211: ssm done, getting out 404s (process:2063): libfprint-SSM-DEBUG: 00:54:13.211: [vfs5011] ACTIVATE REQUEST entering state 1 404s (process:2063): libfprint-vfs5011-DEBUG: 00:54:13.211: Receiving 64 bytes 404s (process:2063): libfprint-vfs5011-DEBUG: 00:54:13.211: Got 64 bytes out of 64 404s (process:2063): libfprint-SSM-DEBUG: 00:54:13.211: [vfs5011] ACTIVATE REQUEST entering state 2 404s (process:2063): libfprint-vfs5011-DEBUG: 00:54:13.211: Receiving 84032 bytes 404s (process:2063): libfprint-vfs5011-DEBUG: 00:54:13.212: Got 176 bytes out of 84032 404s (process:2063): libfprint-SSM-DEBUG: 00:54:13.212: [vfs5011] ACTIVATE REQUEST entering state 3 404s (process:2063): libfprint-vfs5011-DEBUG: 00:54:13.212: Receiving 64 bytes 404s (process:2063): libfprint-SSM-DEBUG: 00:54:13.212: [vfs5011] ACTIVATE REQUEST entering state 4 404s (process:2063): libfprint-vfs5011-DEBUG: 00:54:13.212: Sending vfs5011_cmd_1A 404s (process:2063): libfprint-SSM-DEBUG: 00:54:13.213: [vfs5011] ACTIVATE REQUEST entering state 5 404s (process:2063): libfprint-vfs5011-DEBUG: 00:54:13.213: Receiving 64 bytes 404s (process:2063): libfprint-SSM-DEBUG: 00:54:13.213: [vfs5011] ACTIVATE REQUEST entering state 6 404s (process:2063): libfprint-vfs5011-DEBUG: 00:54:13.213: Sending vfs5011_prepare_00 404s (process:2063): libfprint-SSM-DEBUG: 00:54:13.214: [vfs5011] ACTIVATE REQUEST entering state 7 404s (process:2063): libfprint-vfs5011-DEBUG: 00:54:13.214: Receiving 64 bytes 404s (process:2063): libfprint-SSM-DEBUG: 00:54:13.214: [vfs5011] ACTIVATE REQUEST entering state 8 404s (process:2063): libfprint-vfs5011-DEBUG: 00:54:13.214: Sending vfs5011_cmd_1A 404s (process:2063): libfprint-SSM-DEBUG: 00:54:13.215: [vfs5011] ACTIVATE REQUEST entering state 9 404s (process:2063): libfprint-vfs5011-DEBUG: 00:54:13.215: Receiving 64 bytes 404s (process:2063): libfprint-SSM-DEBUG: 00:54:13.217: [vfs5011] ACTIVATE REQUEST entering state 10 404s (process:2063): libfprint-vfs5011-DEBUG: 00:54:13.217: Sending vfs5011_prepare_01 404s (process:2063): libfprint-SSM-DEBUG: 00:54:13.218: [vfs5011] ACTIVATE REQUEST entering state 11 404s (process:2063): libfprint-vfs5011-DEBUG: 00:54:13.218: Receiving 64 bytes 404s (process:2063): libfprint-SSM-DEBUG: 00:54:13.218: [vfs5011] ACTIVATE REQUEST entering state 12 404s (process:2063): libfprint-vfs5011-DEBUG: 00:54:13.218: Sending vfs5011_prepare_02 404s (process:2063): libfprint-SSM-DEBUG: 00:54:13.219: [vfs5011] ACTIVATE REQUEST entering state 13 404s (process:2063): libfprint-vfs5011-DEBUG: 00:54:13.219: Receiving 2368 bytes 404s (process:2063): libfprint-vfs5011-DEBUG: 00:54:13.219: Got 2368 bytes out of 2368 404s (process:2063): libfprint-SSM-DEBUG: 00:54:13.219: [vfs5011] ACTIVATE REQUEST entering state 14 404s (process:2063): libfprint-vfs5011-DEBUG: 00:54:13.219: Receiving 64 bytes 404s (process:2063): libfprint-vfs5011-DEBUG: 00:54:13.220: Got 36 bytes out of 64 404s (process:2063): libfprint-SSM-DEBUG: 00:54:13.220: [vfs5011] ACTIVATE REQUEST entering state 15 404s (process:2063): libfprint-vfs5011-DEBUG: 00:54:13.220: Receiving 4800 bytes 404s (process:2063): libfprint-vfs5011-DEBUG: 00:54:13.220: Got 4800 bytes out of 4800 404s (process:2063): libfprint-SSM-DEBUG: 00:54:13.220: [vfs5011] ACTIVATE REQUEST entering state 16 404s (process:2063): libfprint-vfs5011-DEBUG: 00:54:13.220: Sending vfs5011_prepare_03 404s (process:2063): libfprint-SSM-DEBUG: 00:54:13.221: [vfs5011] ACTIVATE REQUEST entering state 17 404s (process:2063): libfprint-vfs5011-DEBUG: 00:54:13.221: Receiving 64 bytes 404s (process:2063): libfprint-SSM-DEBUG: 00:54:13.221: [vfs5011] ACTIVATE REQUEST entering state 18 404s (process:2063): libfprint-vfs5011-DEBUG: 00:54:13.221: Sending vfs5011_prepare_04 404s (process:2063): libfprint-SSM-DEBUG: 00:54:13.222: [vfs5011] ACTIVATE REQUEST entering state 19 404s (process:2063): libfprint-vfs5011-DEBUG: 00:54:13.222: Receiving 2368 bytes 404s (process:2063): libfprint-SSM-DEBUG: 00:54:13.223: [vfs5011] ACTIVATE REQUEST completed successfully 404s (process:2063): libfprint-SSM-DEBUG: 00:54:13.223: [vfs5011] DEV_ACTIVATE_NUM_STATES entering state 1 404s (process:2063): libfprint-vfs5011-DEBUG: 00:54:13.223: main_loop: state 1 404s (process:2063): libfprint-vfs5011-DEBUG: 00:54:13.223: capture_init 404s (process:2063): libfprint-image_device-DEBUG: 00:54:13.223: Image device activation completed 404s (process:2063): libfprint-image_device-DEBUG: 00:54:13.223: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE 404s (process:2063): libfprint-image_device-DEBUG: 00:54:13.223: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 404s (process:2063): libfprint-device-DEBUG: 00:54:13.223: Device reported finger status change: FP_FINGER_STATUS_NEEDED 404s (process:2063): libfprint-SSM-DEBUG: 00:54:13.223: [vfs5011] DEV_ACTIVATE_NUM_STATES entering state 2 404s (process:2063): libfprint-vfs5011-DEBUG: 00:54:13.223: main_loop: state 2 404s (process:2063): libfprint-vfs5011-DEBUG: 00:54:13.223: capture_chunk_async: capture 256 lines, already have 0 404s (process:2063): libfprint-device-DEBUG: 00:54:13.223: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 404s (process:2063): libfprint-image_device-DEBUG: 00:54:13.223: Image device reported finger status: on 404s (process:2063): libfprint-image_device-DEBUG: 00:54:13.223: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 404s (process:2063): libfprint-vfs5011-DEBUG: 00:54:13.223: process_chunk: got 61440 bytes 404s (process:2063): libfprint-SSM-DEBUG: 00:54:13.224: [vfs5011] DEV_ACTIVATE_NUM_STATES entering state 2 404s (process:2063): libfprint-vfs5011-DEBUG: 00:54:13.224: main_loop: state 2 404s (process:2063): libfprint-vfs5011-DEBUG: 00:54:13.224: capture_chunk_async: capture 256 lines, already have 6 404s (process:2063): libfprint-image_device-DEBUG: 00:54:13.224: Image device reported finger status: on 404s (process:2063): libfprint-vfs5011-DEBUG: 00:54:13.224: process_chunk: got 61440 bytes 404s (process:2063): libfprint-SSM-DEBUG: 00:54:13.224: [vfs5011] DEV_ACTIVATE_NUM_STATES entering state 2 404s (process:2063): libfprint-vfs5011-DEBUG: 00:54:13.224: main_loop: state 2 404s (process:2063): libfprint-vfs5011-DEBUG: 00:54:13.224: capture_chunk_async: capture 256 lines, already have 25 404s (process:2063): libfprint-image_device-DEBUG: 00:54:13.225: Image device reported finger status: on 404s (process:2063): libfprint-vfs5011-DEBUG: 00:54:13.225: process_chunk: got 61440 bytes 404s (process:2063): libfprint-SSM-DEBUG: 00:54:13.225: [vfs5011] DEV_ACTIVATE_NUM_STATES entering state 2 404s (process:2063): libfprint-vfs5011-DEBUG: 00:54:13.225: main_loop: state 2 404s (process:2063): libfprint-vfs5011-DEBUG: 00:54:13.225: capture_chunk_async: capture 256 lines, already have 54 404s (process:2063): libfprint-image_device-DEBUG: 00:54:13.226: Image device reported finger status: on 404s (process:2063): libfprint-vfs5011-DEBUG: 00:54:13.226: process_chunk: got 61440 bytes 404s (process:2063): libfprint-SSM-DEBUG: 00:54:13.226: [vfs5011] DEV_ACTIVATE_NUM_STATES entering state 2 404s (process:2063): libfprint-vfs5011-DEBUG: 00:54:13.226: main_loop: state 2 404s (process:2063): libfprint-vfs5011-DEBUG: 00:54:13.226: capture_chunk_async: capture 256 lines, already have 89 404s (process:2063): libfprint-image_device-DEBUG: 00:54:13.226: Image device reported finger status: on 404s (process:2063): libfprint-vfs5011-DEBUG: 00:54:13.226: process_chunk: got 61440 bytes 404s (process:2063): libfprint-SSM-DEBUG: 00:54:13.227: [vfs5011] DEV_ACTIVATE_NUM_STATES entering state 2 404s (process:2063): libfprint-vfs5011-DEBUG: 00:54:13.227: main_loop: state 2 404s (process:2063): libfprint-vfs5011-DEBUG: 00:54:13.227: capture_chunk_async: capture 256 lines, already have 117 404s (process:2063): libfprint-image_device-DEBUG: 00:54:13.227: Image device reported finger status: on 404s (process:2063): libfprint-vfs5011-DEBUG: 00:54:13.227: process_chunk: got 61440 bytes 404s (process:2063): libfprint-SSM-DEBUG: 00:54:13.227: [vfs5011] DEV_ACTIVATE_NUM_STATES entering state 2 404s (process:2063): libfprint-vfs5011-DEBUG: 00:54:13.227: main_loop: state 2 404s (process:2063): libfprint-vfs5011-DEBUG: 00:54:13.227: capture_chunk_async: capture 256 lines, already have 144 404s (process:2063): libfprint-image_device-DEBUG: 00:54:13.228: Image device reported finger status: on 404s (process:2063): libfprint-vfs5011-DEBUG: 00:54:13.228: process_chunk: got 61440 bytes 404s (process:2063): libfprint-SSM-DEBUG: 00:54:13.228: [vfs5011] DEV_ACTIVATE_NUM_STATES entering state 2 404s (process:2063): libfprint-vfs5011-DEBUG: 00:54:13.228: main_loop: state 2 404s (process:2063): libfprint-vfs5011-DEBUG: 00:54:13.228: capture_chunk_async: capture 256 lines, already have 180 404s (process:2063): libfprint-image_device-DEBUG: 00:54:13.229: Image device reported finger status: on 404s (process:2063): libfprint-vfs5011-DEBUG: 00:54:13.229: process_chunk: got 61440 bytes 404s (process:2063): libfprint-SSM-DEBUG: 00:54:13.229: [vfs5011] DEV_ACTIVATE_NUM_STATES entering state 2 404s (process:2063): libfprint-vfs5011-DEBUG: 00:54:13.229: main_loop: state 2 404s (process:2063): libfprint-vfs5011-DEBUG: 00:54:13.229: capture_chunk_async: capture 256 lines, already have 273 404s (process:2063): libfprint-image_device-DEBUG: 00:54:13.229: Image device reported finger status: on 404s (process:2063): libfprint-vfs5011-DEBUG: 00:54:13.229: process_chunk: got 61440 bytes 404s (process:2063): libfprint-vfs5011-DEBUG: 00:54:13.229: process_chunk: got 50 empty lines, finishing 404s (process:2063): libfprint-SSM-DEBUG: 00:54:13.229: [vfs5011] DEV_ACTIVATE_NUM_STATES entering state 3 404s (process:2063): libfprint-vfs5011-DEBUG: 00:54:13.229: main_loop: state 3 404s (process:2063): libfprint-SSM-DEBUG: 00:54:13.231: [vfs5011] DEV_ACTIVATE_NUM_STATES entering state 4 404s (process:2063): libfprint-vfs5011-DEBUG: 00:54:13.231: main_loop: state 4 404s (process:2063): libfprint-SSM-DEBUG: 00:54:13.231: [vfs5011] PREPARE CAPTURE entering state 0 404s (process:2063): libfprint-vfs5011-DEBUG: 00:54:13.231: Sending vfs5011_cmd_04 404s (process:2063): libfprint-SSM-DEBUG: 00:54:13.231: [vfs5011] PREPARE CAPTURE entering state 1 404s (process:2063): libfprint-vfs5011-DEBUG: 00:54:13.231: Receiving 64 bytes 404s (process:2063): libfprint-vfs5011-DEBUG: 00:54:13.232: Got 64 bytes out of 64 404s (process:2063): libfprint-SSM-DEBUG: 00:54:13.232: [vfs5011] PREPARE CAPTURE entering state 2 404s (process:2063): libfprint-vfs5011-DEBUG: 00:54:13.232: Receiving 84032 bytes 404s (process:2063): libfprint-vfs5011-DEBUG: 00:54:13.232: Got 176 bytes out of 84032 404s (process:2063): libfprint-SSM-DEBUG: 00:54:13.232: [vfs5011] PREPARE CAPTURE entering state 3 404s (process:2063): libfprint-vfs5011-DEBUG: 00:54:13.232: Receiving 64 bytes 404s (process:2063): libfprint-SSM-DEBUG: 00:54:13.233: [vfs5011] PREPARE CAPTURE entering state 4 404s (process:2063): libfprint-vfs5011-DEBUG: 00:54:13.233: Sending vfs5011_cmd_1A 404s (process:2063): libfprint-SSM-DEBUG: 00:54:13.233: [vfs5011] PREPARE CAPTURE entering state 5 404s (process:2063): libfprint-vfs5011-DEBUG: 00:54:13.233: Receiving 64 bytes 404s (process:2063): libfprint-SSM-DEBUG: 00:54:13.234: [vfs5011] PREPARE CAPTURE entering state 6 404s (process:2063): libfprint-vfs5011-DEBUG: 00:54:13.234: Sending vfs5011_prepare_00 404s (process:2063): libfprint-SSM-DEBUG: 00:54:13.234: [vfs5011] PREPARE CAPTURE entering state 7 404s (process:2063): libfprint-vfs5011-DEBUG: 00:54:13.234: Receiving 64 bytes 404s (process:2063): libfprint-SSM-DEBUG: 00:54:13.235: [vfs5011] PREPARE CAPTURE entering state 8 404s (process:2063): libfprint-vfs5011-DEBUG: 00:54:13.235: Sending vfs5011_cmd_1A 404s (process:2063): libfprint-SSM-DEBUG: 00:54:13.235: [vfs5011] PREPARE CAPTURE entering state 9 404s (process:2063): libfprint-vfs5011-DEBUG: 00:54:13.235: Receiving 64 bytes 404s (process:2063): libfprint-SSM-DEBUG: 00:54:13.236: [vfs5011] PREPARE CAPTURE entering state 10 404s (process:2063): libfprint-vfs5011-DEBUG: 00:54:13.236: Sending vfs5011_prepare_01 404s (process:2063): libfprint-SSM-DEBUG: 00:54:13.236: [vfs5011] PREPARE CAPTURE entering state 11 404s (process:2063): libfprint-vfs5011-DEBUG: 00:54:13.236: Receiving 64 bytes 404s (process:2063): libfprint-SSM-DEBUG: 00:54:13.237: [vfs5011] PREPARE CAPTURE entering state 12 404s (process:2063): libfprint-vfs5011-DEBUG: 00:54:13.237: Sending vfs5011_prepare_02 404s (process:2063): libfprint-SSM-DEBUG: 00:54:13.237: [vfs5011] PREPARE CAPTURE entering state 13 404s (process:2063): libfprint-vfs5011-DEBUG: 00:54:13.237: Receiving 2368 bytes 404s (process:2063): libfprint-vfs5011-DEBUG: 00:54:13.238: Got 2368 bytes out of 2368 404s (process:2063): libfprint-SSM-DEBUG: 00:54:13.238: [vfs5011] PREPARE CAPTURE entering state 14 404s (process:2063): libfprint-vfs5011-DEBUG: 00:54:13.238: Receiving 64 bytes 404s (process:2063): libfprint-vfs5011-DEBUG: 00:54:13.238: Got 36 bytes out of 64 404s (process:2063): libfprint-SSM-DEBUG: 00:54:13.238: [vfs5011] PREPARE CAPTURE entering state 15 404s (process:2063): libfprint-vfs5011-DEBUG: 00:54:13.238: Receiving 4800 bytes 404s (process:2063): libfprint-vfs5011-DEBUG: 00:54:13.239: Got 4800 bytes out of 4800 404s (process:2063): libfprint-SSM-DEBUG: 00:54:13.239: [vfs5011] PREPARE CAPTURE entering state 16 404s (process:2063): libfprint-vfs5011-DEBUG: 00:54:13.239: Sending vfs5011_prepare_03 404s (process:2063): libfprint-SSM-DEBUG: 00:54:13.240: [vfs5011] PREPARE CAPTURE entering state 17 404s (process:2063): libfprint-vfs5011-DEBUG: 00:54:13.240: Receiving 64 bytes 404s (process:2063): libfprint-SSM-DEBUG: 00:54:13.240: [vfs5011] PREPARE CAPTURE entering state 18 404s (process:2063): libfprint-vfs5011-DEBUG: 00:54:13.240: Sending vfs5011_prepare_04 404s (process:2063): libfprint-SSM-DEBUG: 00:54:13.240: [vfs5011] PREPARE CAPTURE entering state 19 404s (process:2063): libfprint-vfs5011-DEBUG: 00:54:13.240: Receiving 2368 bytes 404s (process:2063): libfprint-SSM-DEBUG: 00:54:13.241: [vfs5011] PREPARE CAPTURE completed successfully 404s (process:2063): libfprint-SSM-DEBUG: 00:54:13.241: [vfs5011] DEV_ACTIVATE_NUM_STATES completed successfully 404s (process:2063): libfprint-vfs5011-DEBUG: 00:54:13.241: finishing 404s (process:2063): libfprint-assembling-DEBUG: 00:54:13.241: 1739667253241509 404s (process:2063): libfprint-assembling-DEBUG: 00:54:13.241: 1 404s (process:2063): libfprint-assembling-DEBUG: 00:54:13.241: 6 404s (process:2063): libfprint-assembling-DEBUG: 00:54:13.241: 5 404s (process:2063): libfprint-assembling-DEBUG: 00:54:13.241: 4 404s (process:2063): libfprint-assembling-DEBUG: 00:54:13.241: 4 404s (process:2063): libfprint-assembling-DEBUG: 00:54:13.241: 3 404s (process:2063): libfprint-assembling-DEBUG: 00:54:13.241: 3 404s (process:2063): libfprint-assembling-DEBUG: 00:54:13.241: 5 404s (process:2063): libfprint-assembling-DEBUG: 00:54:13.241: 4 404s (process:2063): libfprint-assembling-DEBUG: 00:54:13.241: 27 404s (process:2063): libfprint-assembling-DEBUG: 00:54:13.241: 27 404s (process:2063): libfprint-assembling-DEBUG: 00:54:13.241: 27 404s (process:2063): libfprint-assembling-DEBUG: 00:54:13.241: 27 404s (process:2063): libfprint-assembling-DEBUG: 00:54:13.241: 28 404s (process:2063): libfprint-assembling-DEBUG: 00:54:13.241: 5 404s (process:2063): libfprint-assembling-DEBUG: 00:54:13.241: 28 404s (process:2063): libfprint-assembling-DEBUG: 00:54:13.241: 29 404s (process:2063): libfprint-assembling-DEBUG: 00:54:13.241: 29 404s (process:2063): libfprint-assembling-DEBUG: 00:54:13.241: 29 404s (process:2063): libfprint-assembling-DEBUG: 00:54:13.241: 29 404s (process:2063): libfprint-assembling-DEBUG: 00:54:13.241: 28 404s (process:2063): libfprint-assembling-DEBUG: 00:54:13.241: 28 404s (process:2063): libfprint-assembling-DEBUG: 00:54:13.241: 29 404s (process:2063): libfprint-assembling-DEBUG: 00:54:13.241: 28 404s (process:2063): libfprint-assembling-DEBUG: 00:54:13.241: 30 404s (process:2063): libfprint-assembling-DEBUG: 00:54:13.241: 29 404s (process:2063): libfprint-assembling-DEBUG: 00:54:13.241: 30 404s (process:2063): libfprint-assembling-DEBUG: 00:54:13.241: 5 404s (process:2063): libfprint-assembling-DEBUG: 00:54:13.241: 5 404s (process:2063): libfprint-assembling-DEBUG: 00:54:13.241: 6 404s (process:2063): libfprint-assembling-DEBUG: 00:54:13.241: 6 404s (process:2063): libfprint-assembling-DEBUG: 00:54:13.241: 30 404s (process:2063): libfprint-assembling-DEBUG: 00:54:13.241: 30 404s (process:2063): libfprint-assembling-DEBUG: 00:54:13.241: 30 404s (process:2063): libfprint-assembling-DEBUG: 00:54:13.241: 30 404s (process:2063): libfprint-assembling-DEBUG: 00:54:13.241: 30 404s (process:2063): libfprint-assembling-DEBUG: 00:54:13.241: 7 404s (process:2063): libfprint-assembling-DEBUG: 00:54:13.241: 7 404s (process:2063): libfprint-assembling-DEBUG: 00:54:13.241: 6 404s (process:2063): libfprint-assembling-DEBUG: 00:54:13.241: 6 404s (process:2063): libfprint-assembling-DEBUG: 00:54:13.241: 6 404s (process:2063): libfprint-assembling-DEBUG: 00:54:13.241: 7 404s (process:2063): libfprint-assembling-DEBUG: 00:54:13.241: 6 404s (process:2063): libfprint-assembling-DEBUG: 00:54:13.241: 6 404s (process:2063): libfprint-assembling-DEBUG: 00:54:13.241: 6 404s (process:2063): libfprint-assembling-DEBUG: 00:54:13.241: 6 404s (process:2063): libfprint-assembling-DEBUG: 00:54:13.241: 6 404s (process:2063): libfprint-assembling-DEBUG: 00:54:13.241: 6 404s (process:2063): libfprint-assembling-DEBUG: 00:54:13.241: 4 404s (process:2063): libfprint-assembling-DEBUG: 00:54:13.241: 4 404s (process:2063): libfprint-assembling-DEBUG: 00:54:13.241: 6 404s (process:2063): libfprint-assembling-DEBUG: 00:54:13.241: 6 404s (process:2063): libfprint-assembling-DEBUG: 00:54:13.241: 29 404s (process:2063): libfprint-assembling-DEBUG: 00:54:13.241: 7 404s (process:2063): libfprint-assembling-DEBUG: 00:54:13.241: 7 404s (process:2063): libfprint-assembling-DEBUG: 00:54:13.241: 6 404s (process:2063): libfprint-assembling-DEBUG: 00:54:13.241: 6 404s (process:2063): libfprint-assembling-DEBUG: 00:54:13.241: 30 404s (process:2063): libfprint-assembling-DEBUG: 00:54:13.241: 29 404s (process:2063): libfprint-assembling-DEBUG: 00:54:13.241: 7 404s (process:2063): libfprint-assembling-DEBUG: 00:54:13.241: 7 404s (process:2063): libfprint-assembling-DEBUG: 00:54:13.241: 9 404s (process:2063): libfprint-assembling-DEBUG: 00:54:13.241: 30 404s (process:2063): libfprint-assembling-DEBUG: 00:54:13.241: 30 404s (process:2063): libfprint-assembling-DEBUG: 00:54:13.241: 30 404s (process:2063): libfprint-assembling-DEBUG: 00:54:13.241: 8 404s (process:2063): libfprint-assembling-DEBUG: 00:54:13.241: 8 404s (process:2063): libfprint-assembling-DEBUG: 00:54:13.241: 8 404s (process:2063): libfprint-assembling-DEBUG: 00:54:13.241: 8 404s (process:2063): libfprint-assembling-DEBUG: 00:54:13.241: 7 404s (process:2063): libfprint-assembling-DEBUG: 00:54:13.241: 6 404s (process:2063): libfprint-assembling-DEBUG: 00:54:13.241: 7 404s (process:2063): libfprint-assembling-DEBUG: 00:54:13.241: 30 404s (process:2063): libfprint-assembling-DEBUG: 00:54:13.241: 30 404s (process:2063): libfprint-assembling-DEBUG: 00:54:13.241: 8 404s (process:2063): libfprint-assembling-DEBUG: 00:54:13.241: 7 404s (process:2063): libfprint-assembling-DEBUG: 00:54:13.242: 8 404s (process:2063): libfprint-assembling-DEBUG: 00:54:13.242: 9 404s (process:2063): libfprint-assembling-DEBUG: 00:54:13.242: 8 404s (process:2063): libfprint-assembling-DEBUG: 00:54:13.242: 8 404s (process:2063): libfprint-assembling-DEBUG: 00:54:13.242: 8 404s (process:2063): libfprint-assembling-DEBUG: 00:54:13.242: 9 404s (process:2063): libfprint-assembling-DEBUG: 00:54:13.242: 9 404s (process:2063): libfprint-assembling-DEBUG: 00:54:13.242: 8 404s (process:2063): libfprint-assembling-DEBUG: 00:54:13.242: 9 404s (process:2063): libfprint-assembling-DEBUG: 00:54:13.242: 9 404s (process:2063): libfprint-assembling-DEBUG: 00:54:13.242: 8 404s (process:2063): libfprint-assembling-DEBUG: 00:54:13.242: 8 404s (process:2063): libfprint-assembling-DEBUG: 00:54:13.242: 9 404s (process:2063): libfprint-assembling-DEBUG: 00:54:13.242: 9 404s (process:2063): libfprint-assembling-DEBUG: 00:54:13.242: 8 404s (process:2063): libfprint-assembling-DEBUG: 00:54:13.242: 8 404s (process:2063): libfprint-assembling-DEBUG: 00:54:13.242: 8 404s (process:2063): libfprint-assembling-DEBUG: 00:54:13.242: 8 404s (process:2063): libfprint-assembling-DEBUG: 00:54:13.242: 8 404s (process:2063): libfprint-assembling-DEBUG: 00:54:13.242: 7 404s (process:2063): libfprint-assembling-DEBUG: 00:54:13.242: 29 404s (process:2063): libfprint-assembling-DEBUG: 00:54:13.242: 29 404s (process:2063): libfprint-assembling-DEBUG: 00:54:13.242: 11 404s (process:2063): libfprint-assembling-DEBUG: 00:54:13.242: 9 404s (process:2063): libfprint-assembling-DEBUG: 00:54:13.242: 9 404s (process:2063): libfprint-assembling-DEBUG: 00:54:13.242: 9 404s (process:2063): libfprint-assembling-DEBUG: 00:54:13.242: 9 404s (process:2063): libfprint-assembling-DEBUG: 00:54:13.242: 8 404s (process:2063): libfprint-assembling-DEBUG: 00:54:13.242: 9 404s (process:2063): libfprint-assembling-DEBUG: 00:54:13.242: 8 404s (process:2063): libfprint-assembling-DEBUG: 00:54:13.242: 30 404s (process:2063): libfprint-assembling-DEBUG: 00:54:13.242: 9 404s (process:2063): libfprint-assembling-DEBUG: 00:54:13.242: 7 404s (process:2063): libfprint-assembling-DEBUG: 00:54:13.242: 8 404s (process:2063): libfprint-assembling-DEBUG: 00:54:13.242: 8 404s (process:2063): libfprint-assembling-DEBUG: 00:54:13.242: 27 404s (process:2063): libfprint-assembling-DEBUG: 00:54:13.242: 26 404s (process:2063): libfprint-assembling-DEBUG: 00:54:13.242: 8 404s (process:2063): libfprint-assembling-DEBUG: 00:54:13.242: 7 404s (process:2063): libfprint-assembling-DEBUG: 00:54:13.242: 8 404s (process:2063): libfprint-assembling-DEBUG: 00:54:13.242: 7 404s (process:2063): libfprint-assembling-DEBUG: 00:54:13.242: 8 404s (process:2063): libfprint-assembling-DEBUG: 00:54:13.242: 7 404s (process:2063): libfprint-assembling-DEBUG: 00:54:13.242: 7 404s (process:2063): libfprint-assembling-DEBUG: 00:54:13.242: 8 404s (process:2063): libfprint-assembling-DEBUG: 00:54:13.242: 6 404s (process:2063): libfprint-assembling-DEBUG: 00:54:13.242: 7 404s (process:2063): libfprint-assembling-DEBUG: 00:54:13.242: 6 404s (process:2063): libfprint-assembling-DEBUG: 00:54:13.242: 8 404s (process:2063): libfprint-assembling-DEBUG: 00:54:13.242: 8 404s (process:2063): libfprint-assembling-DEBUG: 00:54:13.242: 8 404s (process:2063): libfprint-assembling-DEBUG: 00:54:13.242: 8 404s (process:2063): libfprint-assembling-DEBUG: 00:54:13.242: 7 404s (process:2063): libfprint-assembling-DEBUG: 00:54:13.242: 6 404s (process:2063): libfprint-assembling-DEBUG: 00:54:13.242: 6 404s (process:2063): libfprint-assembling-DEBUG: 00:54:13.242: 7 404s (process:2063): libfprint-assembling-DEBUG: 00:54:13.242: 7 404s (process:2063): libfprint-assembling-DEBUG: 00:54:13.242: 5 404s (process:2063): libfprint-assembling-DEBUG: 00:54:13.242: 4 404s (process:2063): libfprint-assembling-DEBUG: 00:54:13.242: 2 404s (process:2063): libfprint-assembling-DEBUG: 00:54:13.242: offsets_filtered: 1739667253242493 404s (process:2063): libfprint-assembling-DEBUG: 00:54:13.242: 5 404s (process:2063): libfprint-assembling-DEBUG: 00:54:13.242: 5 404s (process:2063): libfprint-assembling-DEBUG: 00:54:13.242: 5 404s (process:2063): libfprint-assembling-DEBUG: 00:54:13.242: 5 404s (process:2063): libfprint-assembling-DEBUG: 00:54:13.242: 5 404s (process:2063): libfprint-assembling-DEBUG: 00:54:13.242: 6 404s (process:2063): libfprint-assembling-DEBUG: 00:54:13.242: 6 404s (process:2063): libfprint-assembling-DEBUG: 00:54:13.242: 27 404s (process:2063): libfprint-assembling-DEBUG: 00:54:13.242: 27 404s (process:2063): libfprint-assembling-DEBUG: 00:54:13.242: 27 404s (process:2063): libfprint-assembling-DEBUG: 00:54:13.242: 27 404s (process:2063): libfprint-assembling-DEBUG: 00:54:13.242: 27 404s (process:2063): libfprint-assembling-DEBUG: 00:54:13.242: 27 404s (process:2063): libfprint-assembling-DEBUG: 00:54:13.242: 27 404s (process:2063): libfprint-assembling-DEBUG: 00:54:13.242: 28 404s (process:2063): libfprint-assembling-DEBUG: 00:54:13.242: 28 404s (process:2063): libfprint-assembling-DEBUG: 00:54:13.242: 28 404s (process:2063): libfprint-assembling-DEBUG: 00:54:13.242: 28 404s (process:2063): libfprint-assembling-DEBUG: 00:54:13.242: 28 404s (process:2063): libfprint-assembling-DEBUG: 00:54:13.242: 28 404s (process:2063): libfprint-assembling-DEBUG: 00:54:13.242: 28 404s (process:2063): libfprint-assembling-DEBUG: 00:54:13.242: 28 404s (process:2063): libfprint-assembling-DEBUG: 00:54:13.242: 28 404s (process:2063): libfprint-assembling-DEBUG: 00:54:13.242: 29 404s (process:2063): libfprint-assembling-DEBUG: 00:54:13.242: 29 404s (process:2063): libfprint-assembling-DEBUG: 00:54:13.242: 29 404s (process:2063): libfprint-assembling-DEBUG: 00:54:13.242: 29 404s (process:2063): libfprint-assembling-DEBUG: 00:54:13.242: 29 404s (process:2063): libfprint-assembling-DEBUG: 00:54:13.242: 29 404s (process:2063): libfprint-assembling-DEBUG: 00:54:13.242: 28 404s (process:2063): libfprint-assembling-DEBUG: 00:54:13.242: 28 404s (process:2063): libfprint-assembling-DEBUG: 00:54:13.242: 28 404s (process:2063): libfprint-assembling-DEBUG: 00:54:13.242: 7 404s (process:2063): libfprint-assembling-DEBUG: 00:54:13.242: 7 404s (process:2063): libfprint-assembling-DEBUG: 00:54:13.242: 7 404s (process:2063): libfprint-assembling-DEBUG: 00:54:13.242: 6 404s (process:2063): libfprint-assembling-DEBUG: 00:54:13.242: 6 404s (process:2063): libfprint-assembling-DEBUG: 00:54:13.242: 6 404s (process:2063): libfprint-assembling-DEBUG: 00:54:13.242: 6 404s (process:2063): libfprint-assembling-DEBUG: 00:54:13.242: 6 404s (process:2063): libfprint-assembling-DEBUG: 00:54:13.242: 6 404s (process:2063): libfprint-assembling-DEBUG: 00:54:13.242: 6 404s (process:2063): libfprint-assembling-DEBUG: 00:54:13.242: 6 404s (process:2063): libfprint-assembling-DEBUG: 00:54:13.242: 6 404s (process:2063): libfprint-assembling-DEBUG: 00:54:13.242: 6 404s (process:2063): libfprint-assembling-DEBUG: 00:54:13.242: 6 404s (process:2063): libfprint-assembling-DEBUG: 00:54:13.242: 6 404s (process:2063): libfprint-assembling-DEBUG: 00:54:13.242: 6 404s (process:2063): libfprint-assembling-DEBUG: 00:54:13.242: 6 404s (process:2063): libfprint-assembling-DEBUG: 00:54:13.242: 6 404s (process:2063): libfprint-assembling-DEBUG: 00:54:13.242: 6 404s (process:2063): libfprint-assembling-DEBUG: 00:54:13.242: 6 404s (process:2063): libfprint-assembling-DEBUG: 00:54:13.242: 6 404s (process:2063): libfprint-assembling-DEBUG: 00:54:13.242: 7 404s (process:2063): libfprint-assembling-DEBUG: 00:54:13.242: 7 404s (process:2063): libfprint-assembling-DEBUG: 00:54:13.242: 7 404s (process:2063): libfprint-assembling-DEBUG: 00:54:13.242: 7 404s (process:2063): libfprint-assembling-DEBUG: 00:54:13.242: 7 404s (process:2063): libfprint-assembling-DEBUG: 00:54:13.242: 7 404s (process:2063): libfprint-assembling-DEBUG: 00:54:13.242: 7 404s (process:2063): libfprint-assembling-DEBUG: 00:54:13.242: 7 404s (process:2063): libfprint-assembling-DEBUG: 00:54:13.242: 8 404s (process:2063): libfprint-assembling-DEBUG: 00:54:13.242: 8 404s (process:2063): libfprint-assembling-DEBUG: 00:54:13.242: 8 404s (process:2063): libfprint-assembling-DEBUG: 00:54:13.242: 8 404s (process:2063): libfprint-assembling-DEBUG: 00:54:13.242: 8 404s (process:2063): libfprint-assembling-DEBUG: 00:54:13.242: 8 404s (process:2063): libfprint-assembling-DEBUG: 00:54:13.242: 8 404s (process:2063): libfprint-assembling-DEBUG: 00:54:13.242: 8 404s (process:2063): libfprint-assembling-DEBUG: 00:54:13.242: 8 404s (process:2063): libfprint-assembling-DEBUG: 00:54:13.242: 8 404s (process:2063): libfprint-assembling-DEBUG: 00:54:13.242: 8 404s (process:2063): libfprint-assembling-DEBUG: 00:54:13.242: 8 404s (process:2063): libfprint-assembling-DEBUG: 00:54:13.242: 8 404s (process:2063): libfprint-assembling-DEBUG: 00:54:13.242: 8 404s (process:2063): libfprint-assembling-DEBUG: 00:54:13.242: 8 404s (process:2063): libfprint-assembling-DEBUG: 00:54:13.242: 8 404s (process:2063): libfprint-assembling-DEBUG: 00:54:13.242: 8 404s (process:2063): libfprint-assembling-DEBUG: 00:54:13.242: 8 404s (process:2063): libfprint-assembling-DEBUG: 00:54:13.242: 8 404s (process:2063): libfprint-assembling-DEBUG: 00:54:13.242: 8 404s (process:2063): libfprint-assembling-DEBUG: 00:54:13.242: 8 404s (process:2063): libfprint-assembling-DEBUG: 00:54:13.242: 8 404s (process:2063): libfprint-assembling-DEBUG: 00:54:13.242: 8 404s (process:2063): libfprint-assembling-DEBUG: 00:54:13.242: 8 404s (process:2063): libfprint-assembling-DEBUG: 00:54:13.242: 8 404s (process:2063): libfprint-assembling-DEBUG: 00:54:13.242: 8 404s (process:2063): libfprint-assembling-DEBUG: 00:54:13.242: 8 404s (process:2063): libfprint-assembling-DEBUG: 00:54:13.242: 8 404s (process:2063): libfprint-assembling-DEBUG: 00:54:13.242: 9 404s (process:2063): libfprint-assembling-DEBUG: 00:54:13.242: 9 404s (process:2063): libfprint-assembling-DEBUG: 00:54:13.242: 9 404s (process:2063): libfprint-assembling-DEBUG: 00:54:13.242: 9 404s (process:2063): libfprint-assembling-DEBUG: 00:54:13.242: 9 404s (process:2063): libfprint-assembling-DEBUG: 00:54:13.242: 9 404s (process:2063): libfprint-assembling-DEBUG: 00:54:13.242: 9 404s (process:2063): libfprint-assembling-DEBUG: 00:54:13.242: 9 404s (process:2063): libfprint-assembling-DEBUG: 00:54:13.242: 9 404s (process:2063): libfprint-assembling-DEBUG: 00:54:13.242: 8 404s (process:2063): libfprint-assembling-DEBUG: 00:54:13.242: 9 404s (process:2063): libfprint-assembling-DEBUG: 00:54:13.242: 9 404s (process:2063): libfprint-assembling-DEBUG: 00:54:13.242: 9 404s (process:2063): libfprint-assembling-DEBUG: 00:54:13.242: 8 404s (process:2063): libfprint-assembling-DEBUG: 00:54:13.242: 8 404s (process:2063): libfprint-assembling-DEBUG: 00:54:13.242: 8 404s (process:2063): libfprint-assembling-DEBUG: 00:54:13.242: 8 404s (process:2063): libfprint-assembling-DEBUG: 00:54:13.242: 8 404s (process:2063): libfprint-assembling-DEBUG: 00:54:13.242: 8 404s (process:2063): libfprint-assembling-DEBUG: 00:54:13.242: 8 404s (process:2063): libfprint-assembling-DEBUG: 00:54:13.242: 8 404s (process:2063): libfprint-assembling-DEBUG: 00:54:13.242: 8 404s (process:2063): libfprint-assembling-DEBUG: 00:54:13.242: 8 404s (process:2063): libfprint-assembling-DEBUG: 00:54:13.242: 8 404s (process:2063): libfprint-assembling-DEBUG: 00:54:13.242: 8 404s (process:2063): libfprint-assembling-DEBUG: 00:54:13.242: 8 404s (process:2063): libfprint-assembling-DEBUG: 00:54:13.242: 8 404s (process:2063): libfprint-assembling-DEBUG: 00:54:13.242: 8 404s (process:2063): libfprint-assembling-DEBUG: 00:54:13.242: 8 404s (process:2063): libfprint-assembling-DEBUG: 00:54:13.242: 8 404s (process:2063): libfprint-assembling-DEBUG: 00:54:13.242: 8 404s (process:2063): libfprint-assembling-DEBUG: 00:54:13.242: 7 404s (process:2063): libfprint-assembling-DEBUG: 00:54:13.242: 7 404s (process:2063): libfprint-assembling-DEBUG: 00:54:13.242: 7 404s (process:2063): libfprint-assembling-DEBUG: 00:54:13.242: 7 404s (process:2063): libfprint-assembling-DEBUG: 00:54:13.242: 7 404s (process:2063): libfprint-assembling-DEBUG: 00:54:13.242: 7 404s (process:2063): libfprint-assembling-DEBUG: 00:54:13.242: 7 404s (process:2063): libfprint-assembling-DEBUG: 00:54:13.242: 7 404s (process:2063): libfprint-assembling-DEBUG: 00:54:13.242: 7 404s (process:2063): libfprint-assembling-DEBUG: 00:54:13.242: 7 404s (process:2063): libfprint-assembling-DEBUG: 00:54:13.242: 7 404s (process:2063): libfprint-assembling-DEBUG: 00:54:13.242: 7 404s (process:2063): libfprint-assembling-DEBUG: 00:54:13.242: 7 404s (process:2063): libfprint-assembling-DEBUG: 00:54:13.242: 7 404s (process:2063): libfprint-assembling-DEBUG: 00:54:13.242: 7 404s (process:2063): libfprint-assembling-DEBUG: 00:54:13.242: 2 404s (process:2063): libfprint-vfs5011-DEBUG: 00:54:13.243: Image captured, committing 404s (process:2063): libfprint-image_device-DEBUG: 00:54:13.243: Image device captured an image 404s (process:2063): libfprint-image_device-DEBUG: 00:54:13.245: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 404s (process:2063): libfprint-device-DEBUG: 00:54:13.245: Device reported finger status change: FP_FINGER_STATUS_PRESENT 404s (process:2063): libfprint-device-DEBUG: 00:54:13.245: Device reported finger status change: FP_FINGER_STATUS_NONE 404s (process:2063): libfprint-image_device-DEBUG: 00:54:13.245: Image device reported finger status: off 404s (process:2063): libfprint-image_device-DEBUG: 00:54:13.245: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 404s (process:2063): libfprint-image_device-DEBUG: 00:54:13.245: Deactivating image device 404s (process:2063): libfprint-image_device-DEBUG: 00:54:13.245: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_DEACTIVATING 404s (process:2063): libfprint-image_device-DEBUG: 00:54:13.245: Image device deactivation completed 404s (process:2063): libfprint-image_device-DEBUG: 00:54:13.245: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE 404s (process:2063): libfprint-image-DEBUG: 00:54:13.261: Minutiae scan completed in 0.015449 secs 404s (process:2063): libfprint-device-DEBUG: 00:54:13.261: Device reported capture completion 404s (process:2063): libfprint-device-DEBUG: 00:54:13.261: Completing action FPI_DEVICE_ACTION_CAPTURE in idle! 404s (process:2063): libfprint-device-DEBUG: 00:54:13.261: Updated temperature model after 0.05 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 404s (process:2063): libfprint-image_device-DEBUG: 00:54:13.261: Image device close completed 404s (process:2063): libfprint-device-DEBUG: 00:54:13.261: Device reported close completion 404s (process:2063): libfprint-device-DEBUG: 00:54:13.262: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 404s (process:2063): libfprint-device-DEBUG: 00:54:13.262: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 404s ** (umockdev-run:2059): DEBUG: 00:54:13.370: umockdev.vala:154: Removing test bed /tmp/umockdev.V26012 404s (umockdev-run:2059): GLib-DEBUG: 00:54:13.377: unsetenv() is not thread-safe and should not be used after threads are created 404s Comparing PNGs /tmp/libfprint-umockdev-test-por0tgn0/capture.png and /usr/share/installed-tests/libfprint-2/vfs5011/capture.png 404s PASS: libfprint-2/driver-vfs5011.test 404s Running test: libfprint-2/driver-upektc_img.test 404s ** (umockdev-run:2072): DEBUG: 00:54:13.457: umockdev.vala:127: Created udev test bed /tmp/umockdev.3CNA22 404s ** (umockdev-run:2072): DEBUG: 00:54:13.457: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.3 404s ** (umockdev-run:2072): DEBUG: 00:54:13.460: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.3 (subsystem usb) 404s ** (umockdev-run:2072): DEBUG: 00:54:13.464: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.3CNA22/dev/bus/usb/001/003 404s ** (umockdev-run:2072): DEBUG: 00:54:13.465: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:1a.0/usb1/1-1 404s ** (umockdev-run:2072): DEBUG: 00:54:13.466: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:1a.0/usb1/1-1 (subsystem usb) 404s ** (umockdev-run:2072): DEBUG: 00:54:13.470: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.3CNA22/dev/bus/usb/001/002 404s ** (umockdev-run:2072): DEBUG: 00:54:13.470: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:1a.0/usb1 404s ** (umockdev-run:2072): DEBUG: 00:54:13.471: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:1a.0/usb1 (subsystem usb) 404s ** (umockdev-run:2072): DEBUG: 00:54:13.475: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.3CNA22/dev/bus/usb/001/001 404s ** (umockdev-run:2072): DEBUG: 00:54:13.475: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:1a.0 404s ** (umockdev-run:2072): DEBUG: 00:54:13.476: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:1a.0 (subsystem pci) 404s (process:2076): libfprint-context-DEBUG: 00:54:13.593: Initializing FpContext (libfprint version 1.94.8+tod1) 404s (process:2076): libfprint-tod-DEBUG: 00:54:13.593: Impossible to load the shared drivers dir Error opening directory “/usr/lib/arm-linux-gnueabihf/libfprint-2/tod-1”: No such file or directory 404s (process:2076): libfprint-context-DEBUG: 00:54:13.597: No driver found for USB device 8087:0020 404s (process:2076): libfprint-context-DEBUG: 00:54:13.597: No driver found for USB device 1D6B:0002 404s (process:2076): libfprint-device-DEBUG: 00:54:13.598: Device reported probe completion 404s (process:2076): libfprint-device-DEBUG: 00:54:13.598: Completing action FPI_DEVICE_ACTION_PROBE in idle! 404s (process:2076): libfprint-device-DEBUG: 00:54:13.598: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 404s (process:2076): libfprint-image_device-DEBUG: 00:54:13.600: Image device open completed 404s (process:2076): libfprint-device-DEBUG: 00:54:13.600: Device reported open completion 404s (process:2076): libfprint-device-DEBUG: 00:54:13.600: Completing action FPI_DEVICE_ACTION_OPEN in idle! 404s (process:2076): libfprint-device-DEBUG: 00:54:13.600: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 404s (process:2076): libfprint-device-DEBUG: 00:54:13.600: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 404s (process:2076): libfprint-image_device-DEBUG: 00:54:13.600: Activating image device 404s (process:2076): libfprint-image_device-DEBUG: 00:54:13.600: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING 404s (process:2076): libfprint-SSM-DEBUG: 00:54:13.600: [upektc_img] ACTIVATE_NUM_STATES entering state 0 404s (process:2076): libfprint-SSM-DEBUG: 00:54:13.601: [upektc_img] ACTIVATE_NUM_STATES entering state 1 404s (process:2076): libfprint-SSM-DEBUG: 00:54:13.601: [upektc_img] ACTIVATE_NUM_STATES entering state 2 404s (process:2076): libfprint-SSM-DEBUG: 00:54:13.602: [upektc_img] ACTIVATE_NUM_STATES entering state 3 404s (process:2076): libfprint-SSM-DEBUG: 00:54:13.602: [upektc_img] ACTIVATE_NUM_STATES entering state 4 404s (process:2076): libfprint-SSM-DEBUG: 00:54:13.602: [upektc_img] ACTIVATE_NUM_STATES entering state 5 404s (process:2076): libfprint-SSM-DEBUG: 00:54:13.603: [upektc_img] ACTIVATE_NUM_STATES entering state 6 404s (process:2076): libfprint-SSM-DEBUG: 00:54:13.603: [upektc_img] ACTIVATE_NUM_STATES entering state 7 404s (process:2076): libfprint-SSM-DEBUG: 00:54:13.604: [upektc_img] ACTIVATE_NUM_STATES entering state 8 404s (process:2076): libfprint-SSM-DEBUG: 00:54:13.604: [upektc_img] ACTIVATE_NUM_STATES entering state 9 404s (process:2076): libfprint-SSM-DEBUG: 00:54:13.605: [upektc_img] ACTIVATE_NUM_STATES entering state 10 404s (process:2076): libfprint-SSM-DEBUG: 00:54:13.605: [upektc_img] ACTIVATE_NUM_STATES entering state 11 404s (process:2076): libfprint-upektc_img-DEBUG: 00:54:13.606: Sensor type : TCS4x, width x height: 192 x 512 404s (process:2076): libfprint-SSM-DEBUG: 00:54:13.606: [upektc_img] ACTIVATE_NUM_STATES completed successfully 404s (process:2076): libfprint-image_device-DEBUG: 00:54:13.606: Image device activation completed 404s (process:2076): libfprint-image_device-DEBUG: 00:54:13.606: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE 404s (process:2076): libfprint-image_device-DEBUG: 00:54:13.606: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 404s (process:2076): libfprint-device-DEBUG: 00:54:13.606: Device reported finger status change: FP_FINGER_STATUS_NEEDED 404s (process:2076): libfprint-SSM-DEBUG: 00:54:13.606: [upektc_img] CAPTURE_NUM_STATES entering state 0 404s (process:2076): libfprint-SSM-DEBUG: 00:54:13.606: [upektc_img] CAPTURE_NUM_STATES entering state 1 404s (process:2076): libfprint-upektc_img-DEBUG: 00:54:13.607: request completed, len: 0040 404s (process:2076): libfprint-upektc_img-DEBUG: 00:54:13.607: 18th byte is 0c 404s (process:2076): libfprint-SSM-DEBUG: 00:54:13.607: [upektc_img] CAPTURE_NUM_STATES entering state 3 404s (process:2076): libfprint-SSM-DEBUG: 00:54:13.607: [upektc_img] CAPTURE_NUM_STATES entering state 1 404s (process:2076): libfprint-upektc_img-DEBUG: 00:54:13.608: request completed, len: 0040 404s (process:2076): libfprint-SSM-DEBUG: 00:54:13.608: [upektc_img] CAPTURE_NUM_STATES entering state 4 404s (process:2076): libfprint-SSM-DEBUG: 00:54:13.608: [upektc_img] CAPTURE_NUM_STATES entering state 1 404s (process:2076): libfprint-upektc_img-DEBUG: 00:54:13.609: request completed, len: 0040 404s (process:2076): libfprint-upektc_img-DEBUG: 00:54:13.609: 18th byte is 00 404s (process:2076): libfprint-device-DEBUG: 00:54:13.609: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 404s (process:2076): libfprint-SSM-DEBUG: 00:54:13.609: [upektc_img] CAPTURE_NUM_STATES entering state 3 404s (process:2076): libfprint-SSM-DEBUG: 00:54:13.609: [upektc_img] CAPTURE_NUM_STATES entering state 1 404s (process:2076): libfprint-upektc_img-DEBUG: 00:54:13.610: request completed, len: 0040 404s (process:2076): libfprint-upektc_img-DEBUG: 00:54:13.610: response_size is 2052, actual_length is 64 404s (process:2076): libfprint-upektc_img-DEBUG: 00:54:13.610: Waiting for rest of transfer 404s (process:2076): libfprint-SSM-DEBUG: 00:54:13.610: [upektc_img] CAPTURE_NUM_STATES entering state 1 404s (process:2076): libfprint-upektc_img-DEBUG: 00:54:13.610: request completed, len: 07c4 404s (process:2076): libfprint-image_device-DEBUG: 00:54:13.610: Image device reported finger status: on 404s (process:2076): libfprint-image_device-DEBUG: 00:54:13.610: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 404s (process:2076): libfprint-SSM-DEBUG: 00:54:13.610: [upektc_img] CAPTURE_NUM_STATES entering state 5 404s (process:2076): libfprint-SSM-DEBUG: 00:54:13.611: [upektc_img] CAPTURE_NUM_STATES entering state 1 404s (process:2076): libfprint-upektc_img-DEBUG: 00:54:13.612: request completed, len: 0040 404s (process:2076): libfprint-upektc_img-DEBUG: 00:54:13.612: response_size is 2052, actual_length is 64 404s (process:2076): libfprint-upektc_img-DEBUG: 00:54:13.612: Waiting for rest of transfer 404s (process:2076): libfprint-SSM-DEBUG: 00:54:13.612: [upektc_img] CAPTURE_NUM_STATES entering state 1 404s (process:2076): libfprint-upektc_img-DEBUG: 00:54:13.612: request completed, len: 07c4 404s (process:2076): libfprint-SSM-DEBUG: 00:54:13.612: [upektc_img] CAPTURE_NUM_STATES entering state 5 404s (process:2076): libfprint-SSM-DEBUG: 00:54:13.613: [upektc_img] CAPTURE_NUM_STATES entering state 1 404s (process:2076): libfprint-upektc_img-DEBUG: 00:54:13.613: request completed, len: 0040 404s (process:2076): libfprint-upektc_img-DEBUG: 00:54:13.613: response_size is 2052, actual_length is 64 404s (process:2076): libfprint-upektc_img-DEBUG: 00:54:13.613: Waiting for rest of transfer 404s (process:2076): libfprint-SSM-DEBUG: 00:54:13.613: [upektc_img] CAPTURE_NUM_STATES entering state 1 404s (process:2076): libfprint-upektc_img-DEBUG: 00:54:13.614: request completed, len: 07c4 404s (process:2076): libfprint-SSM-DEBUG: 00:54:13.614: [upektc_img] CAPTURE_NUM_STATES entering state 5 404s (process:2076): libfprint-SSM-DEBUG: 00:54:13.614: [upektc_img] CAPTURE_NUM_STATES entering state 1 404s (process:2076): libfprint-upektc_img-DEBUG: 00:54:13.615: request completed, len: 0040 404s (process:2076): libfprint-upektc_img-DEBUG: 00:54:13.615: response_size is 2052, actual_length is 64 404s (process:2076): libfprint-upektc_img-DEBUG: 00:54:13.615: Waiting for rest of transfer 404s (process:2076): libfprint-SSM-DEBUG: 00:54:13.615: [upektc_img] CAPTURE_NUM_STATES entering state 1 404s (process:2076): libfprint-upektc_img-DEBUG: 00:54:13.615: request completed, len: 07c4 404s (process:2076): libfprint-SSM-DEBUG: 00:54:13.615: [upektc_img] CAPTURE_NUM_STATES entering state 5 404s (process:2076): libfprint-SSM-DEBUG: 00:54:13.616: [upektc_img] CAPTURE_NUM_STATES entering state 1 404s (process:2076): libfprint-upektc_img-DEBUG: 00:54:13.616: request completed, len: 0040 404s (process:2076): libfprint-upektc_img-DEBUG: 00:54:13.616: response_size is 2052, actual_length is 64 404s (process:2076): libfprint-upektc_img-DEBUG: 00:54:13.616: Waiting for rest of transfer 404s (process:2076): libfprint-SSM-DEBUG: 00:54:13.616: [upektc_img] CAPTURE_NUM_STATES entering state 1 404s (process:2076): libfprint-upektc_img-DEBUG: 00:54:13.617: request completed, len: 07c4 404s (process:2076): libfprint-SSM-DEBUG: 00:54:13.617: [upektc_img] CAPTURE_NUM_STATES entering state 5 404s (process:2076): libfprint-SSM-DEBUG: 00:54:13.617: [upektc_img] CAPTURE_NUM_STATES entering state 1 404s (process:2076): libfprint-upektc_img-DEBUG: 00:54:13.618: request completed, len: 0040 404s (process:2076): libfprint-upektc_img-DEBUG: 00:54:13.618: response_size is 2052, actual_length is 64 404s (process:2076): libfprint-upektc_img-DEBUG: 00:54:13.618: Waiting for rest of transfer 404s (process:2076): libfprint-SSM-DEBUG: 00:54:13.618: [upektc_img] CAPTURE_NUM_STATES entering state 1 404s (process:2076): libfprint-upektc_img-DEBUG: 00:54:13.618: request completed, len: 07c4 404s (process:2076): libfprint-SSM-DEBUG: 00:54:13.618: [upektc_img] CAPTURE_NUM_STATES entering state 5 404s (process:2076): libfprint-SSM-DEBUG: 00:54:13.619: [upektc_img] CAPTURE_NUM_STATES entering state 1 404s (process:2076): libfprint-upektc_img-DEBUG: 00:54:13.619: request completed, len: 0040 404s (process:2076): libfprint-upektc_img-DEBUG: 00:54:13.619: response_size is 2052, actual_length is 64 404s (process:2076): libfprint-upektc_img-DEBUG: 00:54:13.619: Waiting for rest of transfer 404s (process:2076): libfprint-SSM-DEBUG: 00:54:13.619: [upektc_img] CAPTURE_NUM_STATES entering state 1 404s (process:2076): libfprint-upektc_img-DEBUG: 00:54:13.620: request completed, len: 07c4 404s (process:2076): libfprint-SSM-DEBUG: 00:54:13.620: [upektc_img] CAPTURE_NUM_STATES entering state 5 404s (process:2076): libfprint-SSM-DEBUG: 00:54:13.620: [upektc_img] CAPTURE_NUM_STATES entering state 1 404s (process:2076): libfprint-upektc_img-DEBUG: 00:54:13.621: request completed, len: 0040 404s (process:2076): libfprint-upektc_img-DEBUG: 00:54:13.621: response_size is 2052, actual_length is 64 404s (process:2076): libfprint-upektc_img-DEBUG: 00:54:13.621: Waiting for rest of transfer 404s (process:2076): libfprint-SSM-DEBUG: 00:54:13.621: [upektc_img] CAPTURE_NUM_STATES entering state 1 404s (process:2076): libfprint-upektc_img-DEBUG: 00:54:13.621: request completed, len: 07c4 404s (process:2076): libfprint-SSM-DEBUG: 00:54:13.621: [upektc_img] CAPTURE_NUM_STATES entering state 5 404s (process:2076): libfprint-SSM-DEBUG: 00:54:13.622: [upektc_img] CAPTURE_NUM_STATES entering state 1 404s (process:2076): libfprint-upektc_img-DEBUG: 00:54:13.622: request completed, len: 0040 404s (process:2076): libfprint-upektc_img-DEBUG: 00:54:13.622: response_size is 2052, actual_length is 64 404s (process:2076): libfprint-upektc_img-DEBUG: 00:54:13.622: Waiting for rest of transfer 404s (process:2076): libfprint-SSM-DEBUG: 00:54:13.622: [upektc_img] CAPTURE_NUM_STATES entering state 1 404s (process:2076): libfprint-upektc_img-DEBUG: 00:54:13.623: request completed, len: 07c4 404s (process:2076): libfprint-SSM-DEBUG: 00:54:13.623: [upektc_img] CAPTURE_NUM_STATES entering state 5 404s (process:2076): libfprint-SSM-DEBUG: 00:54:13.623: [upektc_img] CAPTURE_NUM_STATES entering state 1 404s (process:2076): libfprint-upektc_img-DEBUG: 00:54:13.624: request completed, len: 0040 404s (process:2076): libfprint-upektc_img-DEBUG: 00:54:13.624: response_size is 2052, actual_length is 64 404s (process:2076): libfprint-upektc_img-DEBUG: 00:54:13.624: Waiting for rest of transfer 404s (process:2076): libfprint-SSM-DEBUG: 00:54:13.624: [upektc_img] CAPTURE_NUM_STATES entering state 1 404s (process:2076): libfprint-upektc_img-DEBUG: 00:54:13.624: request completed, len: 07c4 404s (process:2076): libfprint-SSM-DEBUG: 00:54:13.624: [upektc_img] CAPTURE_NUM_STATES entering state 5 404s (process:2076): libfprint-SSM-DEBUG: 00:54:13.625: [upektc_img] CAPTURE_NUM_STATES entering state 1 404s (process:2076): libfprint-upektc_img-DEBUG: 00:54:13.625: request completed, len: 0040 404s (process:2076): libfprint-upektc_img-DEBUG: 00:54:13.625: response_size is 2052, actual_length is 64 404s (process:2076): libfprint-upektc_img-DEBUG: 00:54:13.625: Waiting for rest of transfer 404s (process:2076): libfprint-SSM-DEBUG: 00:54:13.625: [upektc_img] CAPTURE_NUM_STATES entering state 1 404s (process:2076): libfprint-upektc_img-DEBUG: 00:54:13.626: request completed, len: 07c4 404s (process:2076): libfprint-SSM-DEBUG: 00:54:13.626: [upektc_img] CAPTURE_NUM_STATES entering state 5 404s (process:2076): libfprint-SSM-DEBUG: 00:54:13.626: [upektc_img] CAPTURE_NUM_STATES entering state 1 404s (process:2076): libfprint-upektc_img-DEBUG: 00:54:13.627: request completed, len: 0040 404s (process:2076): libfprint-upektc_img-DEBUG: 00:54:13.627: response_size is 2052, actual_length is 64 404s (process:2076): libfprint-upektc_img-DEBUG: 00:54:13.627: Waiting for rest of transfer 404s (process:2076): libfprint-SSM-DEBUG: 00:54:13.627: [upektc_img] CAPTURE_NUM_STATES entering state 1 404s (process:2076): libfprint-upektc_img-DEBUG: 00:54:13.627: request completed, len: 07c4 404s (process:2076): libfprint-SSM-DEBUG: 00:54:13.627: [upektc_img] CAPTURE_NUM_STATES entering state 5 404s (process:2076): libfprint-SSM-DEBUG: 00:54:13.628: [upektc_img] CAPTURE_NUM_STATES entering state 1 404s (process:2076): libfprint-upektc_img-DEBUG: 00:54:13.628: request completed, len: 0040 404s (process:2076): libfprint-upektc_img-DEBUG: 00:54:13.628: response_size is 2052, actual_length is 64 404s (process:2076): libfprint-upektc_img-DEBUG: 00:54:13.628: Waiting for rest of transfer 404s (process:2076): libfprint-SSM-DEBUG: 00:54:13.628: [upektc_img] CAPTURE_NUM_STATES entering state 1 404s (process:2076): libfprint-upektc_img-DEBUG: 00:54:13.629: request completed, len: 07c4 404s (process:2076): libfprint-SSM-DEBUG: 00:54:13.629: [upektc_img] CAPTURE_NUM_STATES entering state 5 404s (process:2076): libfprint-SSM-DEBUG: 00:54:13.629: [upektc_img] CAPTURE_NUM_STATES entering state 1 404s (process:2076): libfprint-upektc_img-DEBUG: 00:54:13.630: request completed, len: 0040 404s (process:2076): libfprint-upektc_img-DEBUG: 00:54:13.630: response_size is 2052, actual_length is 64 404s (process:2076): libfprint-upektc_img-DEBUG: 00:54:13.630: Waiting for rest of transfer 404s (process:2076): libfprint-SSM-DEBUG: 00:54:13.630: [upektc_img] CAPTURE_NUM_STATES entering state 1 404s (process:2076): libfprint-upektc_img-DEBUG: 00:54:13.630: request completed, len: 07c4 404s (process:2076): libfprint-SSM-DEBUG: 00:54:13.630: [upektc_img] CAPTURE_NUM_STATES entering state 5 404s (process:2076): libfprint-SSM-DEBUG: 00:54:13.631: [upektc_img] CAPTURE_NUM_STATES entering state 1 404s (process:2076): libfprint-upektc_img-DEBUG: 00:54:13.631: request completed, len: 0040 404s (process:2076): libfprint-upektc_img-DEBUG: 00:54:13.631: response_size is 2052, actual_length is 64 404s (process:2076): libfprint-upektc_img-DEBUG: 00:54:13.631: Waiting for rest of transfer 404s (process:2076): libfprint-SSM-DEBUG: 00:54:13.631: [upektc_img] CAPTURE_NUM_STATES entering state 1 404s (process:2076): libfprint-upektc_img-DEBUG: 00:54:13.632: request completed, len: 07c4 404s (process:2076): libfprint-SSM-DEBUG: 00:54:13.632: [upektc_img] CAPTURE_NUM_STATES entering state 5 404s (process:2076): libfprint-SSM-DEBUG: 00:54:13.632: [upektc_img] CAPTURE_NUM_STATES entering state 1 404s (process:2076): libfprint-upektc_img-DEBUG: 00:54:13.633: request completed, len: 0040 404s (process:2076): libfprint-upektc_img-DEBUG: 00:54:13.633: response_size is 2052, actual_length is 64 404s (process:2076): libfprint-upektc_img-DEBUG: 00:54:13.633: Waiting for rest of transfer 404s (process:2076): libfprint-SSM-DEBUG: 00:54:13.633: [upektc_img] CAPTURE_NUM_STATES entering state 1 404s (process:2076): libfprint-upektc_img-DEBUG: 00:54:13.634: request completed, len: 07c4 404s (process:2076): libfprint-SSM-DEBUG: 00:54:13.634: [upektc_img] CAPTURE_NUM_STATES entering state 5 404s (process:2076): libfprint-SSM-DEBUG: 00:54:13.634: [upektc_img] CAPTURE_NUM_STATES entering state 1 404s (process:2076): libfprint-upektc_img-DEBUG: 00:54:13.635: request completed, len: 0040 404s (process:2076): libfprint-upektc_img-DEBUG: 00:54:13.635: response_size is 2052, actual_length is 64 404s (process:2076): libfprint-upektc_img-DEBUG: 00:54:13.635: Waiting for rest of transfer 404s (process:2076): libfprint-SSM-DEBUG: 00:54:13.635: [upektc_img] CAPTURE_NUM_STATES entering state 1 404s (process:2076): libfprint-upektc_img-DEBUG: 00:54:13.635: request completed, len: 07c4 404s (process:2076): libfprint-SSM-DEBUG: 00:54:13.635: [upektc_img] CAPTURE_NUM_STATES entering state 5 404s (process:2076): libfprint-SSM-DEBUG: 00:54:13.636: [upektc_img] CAPTURE_NUM_STATES entering state 1 404s (process:2076): libfprint-upektc_img-DEBUG: 00:54:13.636: request completed, len: 0040 404s (process:2076): libfprint-upektc_img-DEBUG: 00:54:13.636: response_size is 2052, actual_length is 64 404s (process:2076): libfprint-upektc_img-DEBUG: 00:54:13.636: Waiting for rest of transfer 404s (process:2076): libfprint-SSM-DEBUG: 00:54:13.636: [upektc_img] CAPTURE_NUM_STATES entering state 1 404s (process:2076): libfprint-upektc_img-DEBUG: 00:54:13.637: request completed, len: 07c4 404s (process:2076): libfprint-SSM-DEBUG: 00:54:13.637: [upektc_img] CAPTURE_NUM_STATES entering state 5 404s (process:2076): libfprint-SSM-DEBUG: 00:54:13.637: [upektc_img] CAPTURE_NUM_STATES entering state 1 404s (process:2076): libfprint-upektc_img-DEBUG: 00:54:13.638: request completed, len: 0040 404s (process:2076): libfprint-upektc_img-DEBUG: 00:54:13.638: response_size is 2052, actual_length is 64 404s (process:2076): libfprint-upektc_img-DEBUG: 00:54:13.638: Waiting for rest of transfer 404s (process:2076): libfprint-SSM-DEBUG: 00:54:13.638: [upektc_img] CAPTURE_NUM_STATES entering state 1 404s (process:2076): libfprint-upektc_img-DEBUG: 00:54:13.638: request completed, len: 07c4 404s (process:2076): libfprint-SSM-DEBUG: 00:54:13.638: [upektc_img] CAPTURE_NUM_STATES entering state 5 404s (process:2076): libfprint-SSM-DEBUG: 00:54:13.639: [upektc_img] CAPTURE_NUM_STATES entering state 1 404s (process:2076): libfprint-upektc_img-DEBUG: 00:54:13.639: request completed, len: 0040 404s (process:2076): libfprint-upektc_img-DEBUG: 00:54:13.639: response_size is 2052, actual_length is 64 404s (process:2076): libfprint-upektc_img-DEBUG: 00:54:13.639: Waiting for rest of transfer 404s (process:2076): libfprint-SSM-DEBUG: 00:54:13.639: [upektc_img] CAPTURE_NUM_STATES entering state 1 404s (process:2076): libfprint-upektc_img-DEBUG: 00:54:13.640: request completed, len: 07c4 404s (process:2076): libfprint-SSM-DEBUG: 00:54:13.640: [upektc_img] CAPTURE_NUM_STATES entering state 5 404s (process:2076): libfprint-SSM-DEBUG: 00:54:13.640: [upektc_img] CAPTURE_NUM_STATES entering state 1 404s (process:2076): libfprint-upektc_img-DEBUG: 00:54:13.641: request completed, len: 0040 404s (process:2076): libfprint-upektc_img-DEBUG: 00:54:13.641: response_size is 2052, actual_length is 64 404s (process:2076): libfprint-upektc_img-DEBUG: 00:54:13.641: Waiting for rest of transfer 404s (process:2076): libfprint-SSM-DEBUG: 00:54:13.641: [upektc_img] CAPTURE_NUM_STATES entering state 1 404s (process:2076): libfprint-upektc_img-DEBUG: 00:54:13.641: request completed, len: 07c4 404s (process:2076): libfprint-SSM-DEBUG: 00:54:13.641: [upektc_img] CAPTURE_NUM_STATES entering state 5 404s (process:2076): libfprint-SSM-DEBUG: 00:54:13.642: [upektc_img] CAPTURE_NUM_STATES entering state 1 404s (process:2076): libfprint-upektc_img-DEBUG: 00:54:13.642: request completed, len: 0040 404s (process:2076): libfprint-upektc_img-DEBUG: 00:54:13.642: response_size is 2052, actual_length is 64 404s (process:2076): libfprint-upektc_img-DEBUG: 00:54:13.642: Waiting for rest of transfer 404s (process:2076): libfprint-SSM-DEBUG: 00:54:13.642: [upektc_img] CAPTURE_NUM_STATES entering state 1 404s (process:2076): libfprint-upektc_img-DEBUG: 00:54:13.643: request completed, len: 07c4 404s (process:2076): libfprint-SSM-DEBUG: 00:54:13.643: [upektc_img] CAPTURE_NUM_STATES entering state 5 404s (process:2076): libfprint-SSM-DEBUG: 00:54:13.643: [upektc_img] CAPTURE_NUM_STATES entering state 1 404s (process:2076): libfprint-upektc_img-DEBUG: 00:54:13.644: request completed, len: 0040 404s (process:2076): libfprint-upektc_img-DEBUG: 00:54:13.644: response_size is 2052, actual_length is 64 404s (process:2076): libfprint-upektc_img-DEBUG: 00:54:13.644: Waiting for rest of transfer 404s (process:2076): libfprint-SSM-DEBUG: 00:54:13.644: [upektc_img] CAPTURE_NUM_STATES entering state 1 404s (process:2076): libfprint-upektc_img-DEBUG: 00:54:13.645: request completed, len: 07c4 404s (process:2076): libfprint-SSM-DEBUG: 00:54:13.645: [upektc_img] CAPTURE_NUM_STATES entering state 5 404s (process:2076): libfprint-SSM-DEBUG: 00:54:13.645: [upektc_img] CAPTURE_NUM_STATES entering state 1 404s (process:2076): libfprint-upektc_img-DEBUG: 00:54:13.645: request completed, len: 0040 404s (process:2076): libfprint-upektc_img-DEBUG: 00:54:13.646: response_size is 2052, actual_length is 64 404s (process:2076): libfprint-upektc_img-DEBUG: 00:54:13.646: Waiting for rest of transfer 404s (process:2076): libfprint-SSM-DEBUG: 00:54:13.646: [upektc_img] CAPTURE_NUM_STATES entering state 1 404s (process:2076): libfprint-upektc_img-DEBUG: 00:54:13.646: request completed, len: 07c4 404s (process:2076): libfprint-SSM-DEBUG: 00:54:13.646: [upektc_img] CAPTURE_NUM_STATES entering state 5 404s (process:2076): libfprint-SSM-DEBUG: 00:54:13.647: [upektc_img] CAPTURE_NUM_STATES entering state 1 404s (process:2076): libfprint-upektc_img-DEBUG: 00:54:13.647: request completed, len: 0040 404s (process:2076): libfprint-upektc_img-DEBUG: 00:54:13.647: response_size is 2052, actual_length is 64 404s (process:2076): libfprint-upektc_img-DEBUG: 00:54:13.647: Waiting for rest of transfer 404s (process:2076): libfprint-SSM-DEBUG: 00:54:13.647: [upektc_img] CAPTURE_NUM_STATES entering state 1 404s (process:2076): libfprint-upektc_img-DEBUG: 00:54:13.648: request completed, len: 07c4 404s (process:2076): libfprint-SSM-DEBUG: 00:54:13.648: [upektc_img] CAPTURE_NUM_STATES entering state 5 404s (process:2076): libfprint-SSM-DEBUG: 00:54:13.648: [upektc_img] CAPTURE_NUM_STATES entering state 1 404s (process:2076): libfprint-upektc_img-DEBUG: 00:54:13.649: request completed, len: 0040 404s (process:2076): libfprint-upektc_img-DEBUG: 00:54:13.649: response_size is 2052, actual_length is 64 404s (process:2076): libfprint-upektc_img-DEBUG: 00:54:13.649: Waiting for rest of transfer 404s (process:2076): libfprint-SSM-DEBUG: 00:54:13.649: [upektc_img] CAPTURE_NUM_STATES entering state 1 404s (process:2076): libfprint-upektc_img-DEBUG: 00:54:13.649: request completed, len: 07c4 404s (process:2076): libfprint-SSM-DEBUG: 00:54:13.649: [upektc_img] CAPTURE_NUM_STATES entering state 5 404s (process:2076): libfprint-SSM-DEBUG: 00:54:13.650: [upektc_img] CAPTURE_NUM_STATES entering state 1 404s (process:2076): libfprint-upektc_img-DEBUG: 00:54:13.650: request completed, len: 0040 404s (process:2076): libfprint-upektc_img-DEBUG: 00:54:13.650: response_size is 2052, actual_length is 64 404s (process:2076): libfprint-upektc_img-DEBUG: 00:54:13.650: Waiting for rest of transfer 404s (process:2076): libfprint-SSM-DEBUG: 00:54:13.650: [upektc_img] CAPTURE_NUM_STATES entering state 1 404s (process:2076): libfprint-upektc_img-DEBUG: 00:54:13.651: request completed, len: 07c4 404s (process:2076): libfprint-SSM-DEBUG: 00:54:13.651: [upektc_img] CAPTURE_NUM_STATES entering state 5 404s (process:2076): libfprint-SSM-DEBUG: 00:54:13.651: [upektc_img] CAPTURE_NUM_STATES entering state 1 404s (process:2076): libfprint-upektc_img-DEBUG: 00:54:13.652: request completed, len: 0040 404s (process:2076): libfprint-upektc_img-DEBUG: 00:54:13.652: response_size is 186, actual_length is 64 404s (process:2076): libfprint-upektc_img-DEBUG: 00:54:13.652: Waiting for rest of transfer 404s (process:2076): libfprint-SSM-DEBUG: 00:54:13.652: [upektc_img] CAPTURE_NUM_STATES entering state 1 404s (process:2076): libfprint-upektc_img-DEBUG: 00:54:13.652: request completed, len: 007a 404s (process:2076): libfprint-upektc_img-DEBUG: 00:54:13.652: Image size is 55296 404s (process:2076): libfprint-image_device-DEBUG: 00:54:13.652: Image device captured an image 404s (process:2076): libfprint-image_device-DEBUG: 00:54:13.653: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 404s (process:2076): libfprint-device-DEBUG: 00:54:13.653: Device reported finger status change: FP_FINGER_STATUS_PRESENT 404s (process:2076): libfprint-device-DEBUG: 00:54:13.653: Device reported finger status change: FP_FINGER_STATUS_NONE 404s (process:2076): libfprint-image_device-DEBUG: 00:54:13.653: Image device reported finger status: off 404s (process:2076): libfprint-image_device-DEBUG: 00:54:13.653: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 404s (process:2076): libfprint-image_device-DEBUG: 00:54:13.653: Deactivating image device 404s (process:2076): libfprint-image_device-DEBUG: 00:54:13.653: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_DEACTIVATING 404s (process:2076): libfprint-SSM-DEBUG: 00:54:13.653: [upektc_img] CAPTURE_NUM_STATES completed successfully 404s (process:2076): libfprint-SSM-DEBUG: 00:54:13.653: [upektc_img] DEACTIVATE_NUM_STATES entering state 0 404s (process:2076): libfprint-SSM-DEBUG: 00:54:13.654: [upektc_img] DEACTIVATE_NUM_STATES entering state 1 404s (process:2076): libfprint-SSM-DEBUG: 00:54:13.654: [upektc_img] DEACTIVATE_NUM_STATES completed successfully 404s (process:2076): libfprint-upektc_img-DEBUG: 00:54:13.654: Deactivate completed 404s (process:2076): libfprint-image_device-DEBUG: 00:54:13.654: Image device deactivation completed 404s (process:2076): libfprint-image_device-DEBUG: 00:54:13.654: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE 404s (process:2076): libfprint-image-DEBUG: 00:54:13.664: Minutiae scan completed in 0.011414 secs 404s (process:2076): libfprint-device-DEBUG: 00:54:13.665: Device reported capture completion 404s (process:2076): libfprint-device-DEBUG: 00:54:13.665: Completing action FPI_DEVICE_ACTION_CAPTURE in idle! 404s (process:2076): libfprint-device-DEBUG: 00:54:13.665: Updated temperature model after 0.06 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 404s (process:2076): libfprint-image_device-DEBUG: 00:54:13.665: Image device close completed 404s (process:2076): libfprint-device-DEBUG: 00:54:13.665: Device reported close completion 404s (process:2076): libfprint-device-DEBUG: 00:54:13.666: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 404s (process:2076): libfprint-device-DEBUG: 00:54:13.666: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 404s ** (umockdev-run:2072): DEBUG: 00:54:13.774: umockdev.vala:154: Removing test bed /tmp/umockdev.3CNA22 404s (umockdev-run:2072): GLib-DEBUG: 00:54:13.788: unsetenv() is not thread-safe and should not be used after threads are created 404s Comparing PNGs /tmp/libfprint-umockdev-test-bf4zk2z_/capture.png and /usr/share/installed-tests/libfprint-2/upektc_img/capture.png 404s PASS: libfprint-2/driver-upektc_img.test 404s Running test: libfprint-2/driver-elan-cobo.test 404s ** (umockdev-run:2085): DEBUG: 00:54:13.905: umockdev.vala:127: Created udev test bed /tmp/umockdev.NJXH22 404s ** (umockdev-run:2085): DEBUG: 00:54:13.905: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0/usb1/1-10 404s ** (umockdev-run:2085): DEBUG: 00:54:13.907: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0/usb1/1-10 (subsystem usb) 404s ** (umockdev-run:2085): DEBUG: 00:54:13.912: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.NJXH22/dev/bus/usb/001/045 404s ** (umockdev-run:2085): DEBUG: 00:54:13.912: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0/usb1 404s ** (umockdev-run:2085): DEBUG: 00:54:13.914: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0/usb1 (subsystem usb) 404s ** (umockdev-run:2085): DEBUG: 00:54:13.920: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.NJXH22/dev/bus/usb/001/001 404s ** (umockdev-run:2085): DEBUG: 00:54:13.920: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0 404s ** (umockdev-run:2085): DEBUG: 00:54:13.921: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0 (subsystem pci) 405s (process:2089): libfprint-context-DEBUG: 00:54:14.040: Initializing FpContext (libfprint version 1.94.8+tod1) 405s (process:2089): libfprint-tod-DEBUG: 00:54:14.040: Impossible to load the shared drivers dir Error opening directory “/usr/lib/arm-linux-gnueabihf/libfprint-2/tod-1”: No such file or directory 405s (process:2089): libfprint-context-DEBUG: 00:54:14.043: No driver found for USB device 1D6B:0002 405s (process:2089): libfprint-device-DEBUG: 00:54:14.044: Device reported probe completion 405s (process:2089): libfprint-device-DEBUG: 00:54:14.044: Completing action FPI_DEVICE_ACTION_PROBE in idle! 405s (process:2089): libfprint-device-DEBUG: 00:54:14.044: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 405s (process:2089): libfprint-elan-DEBUG: 00:54:14.045: 7399822106704: ../libfprint/drivers/elan.c:908 405s (process:2089): libfprint-image_device-DEBUG: 00:54:14.046: Image device open completed 405s (process:2089): libfprint-device-DEBUG: 00:54:14.046: Device reported open completion 405s (process:2089): libfprint-device-DEBUG: 00:54:14.046: Completing action FPI_DEVICE_ACTION_OPEN in idle! 405s (process:2089): libfprint-device-DEBUG: 00:54:14.046: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 405s (process:2089): libfprint-device-DEBUG: 00:54:14.046: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 405s (process:2089): libfprint-image_device-DEBUG: 00:54:14.046: Activating image device 405s (process:2089): libfprint-image_device-DEBUG: 00:54:14.046: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING 405s (process:2089): libfprint-elan-DEBUG: 00:54:14.046: 7399822107768: ../libfprint/drivers/elan.c:960 405s (process:2089): libfprint-elan-DEBUG: 00:54:14.046: 7399822107773: ../libfprint/drivers/elan.c:951 405s (process:2089): libfprint-elan-DEBUG: 00:54:14.046: 7399822107777: ../libfprint/drivers/elan.c:892 405s (process:2089): libfprint-elan-DEBUG: 00:54:14.046: 7399822107780: ../libfprint/drivers/elan.c:100 405s (process:2089): libfprint-SSM-DEBUG: 00:54:14.046: [elan] ACTIVATE_NUM_STATES entering state 0 405s (process:2089): libfprint-elan-DEBUG: 00:54:14.046: 7399822107799: ../libfprint/drivers/elan.c:820 405s (process:2089): libfprint-elan-DEBUG: 00:54:14.047: 7399822108730: ../libfprint/drivers/elan.c:346 405s (process:2089): libfprint-elan-DEBUG: 00:54:14.047: 7399822108759: ../libfprint/drivers/elan.c:366 405s (process:2089): libfprint-elan-DEBUG: 00:54:14.047: 7399822108763: ../libfprint/drivers/elan.c:379 405s (process:2089): libfprint-elan-DEBUG: 00:54:14.048: 7399822109469: ../libfprint/drivers/elan.c:346 405s (process:2089): libfprint-elan-DEBUG: 00:54:14.048: 7399822109500: ../libfprint/drivers/elan.c:335 405s (process:2089): libfprint-SSM-DEBUG: 00:54:14.048: [elan] ACTIVATE_NUM_STATES entering state 1 405s (process:2089): libfprint-elan-DEBUG: 00:54:14.048: 7399822109517: ../libfprint/drivers/elan.c:820 405s (process:2089): libfprint-elan-DEBUG: 00:54:14.048: FW ver 0x0140 405s (process:2089): libfprint-SSM-DEBUG: 00:54:14.048: [elan] ACTIVATE_NUM_STATES entering state 2 405s (process:2089): libfprint-elan-DEBUG: 00:54:14.048: 7399822109527: ../libfprint/drivers/elan.c:820 405s (process:2089): libfprint-elan-DEBUG: 00:54:14.049: 7399822110399: ../libfprint/drivers/elan.c:346 405s (process:2089): libfprint-elan-DEBUG: 00:54:14.049: 7399822110431: ../libfprint/drivers/elan.c:366 405s (process:2089): libfprint-elan-DEBUG: 00:54:14.049: 7399822110435: ../libfprint/drivers/elan.c:379 405s (process:2089): libfprint-elan-DEBUG: 00:54:14.050: 7399822111191: ../libfprint/drivers/elan.c:346 405s (process:2089): libfprint-elan-DEBUG: 00:54:14.050: 7399822111213: ../libfprint/drivers/elan.c:335 405s (process:2089): libfprint-SSM-DEBUG: 00:54:14.050: [elan] ACTIVATE_NUM_STATES entering state 3 405s (process:2089): libfprint-elan-DEBUG: 00:54:14.050: 7399822111222: ../libfprint/drivers/elan.c:820 405s (process:2089): libfprint-elan-DEBUG: 00:54:14.050: sensor dimensions, WxH: 144x64 405s (process:2089): libfprint-SSM-DEBUG: 00:54:14.050: [elan] ACTIVATE_NUM_STATES entering state 4 405s (process:2089): libfprint-elan-DEBUG: 00:54:14.050: 7399822111232: ../libfprint/drivers/elan.c:820 405s (process:2089): libfprint-elan-DEBUG: 00:54:14.050: skipping command 0x40 0x2a for this device (for devices 0x1 but device is 0x0) 405s (process:2089): libfprint-elan-DEBUG: 00:54:14.050: 7399822111240: ../libfprint/drivers/elan.c:335 405s (process:2089): libfprint-SSM-DEBUG: 00:54:14.050: [elan] ACTIVATE_NUM_STATES completed successfully 405s (process:2089): libfprint-elan-DEBUG: 00:54:14.050: 7399822111247: ../libfprint/drivers/elan.c:881 405s (process:2089): libfprint-image_device-DEBUG: 00:54:14.050: Image device activation completed 405s (process:2089): libfprint-image_device-DEBUG: 00:54:14.050: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE 405s (process:2089): libfprint-elan-DEBUG: 00:54:14.050: 7399822111272: ../libfprint/drivers/elan.c:960 405s (process:2089): libfprint-image_device-DEBUG: 00:54:14.050: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 405s (process:2089): libfprint-elan-DEBUG: 00:54:14.050: 7399822111281: ../libfprint/drivers/elan.c:960 405s (process:2089): libfprint-elan-DEBUG: 00:54:14.050: 7399822111284: ../libfprint/drivers/elan.c:792 405s (process:2089): libfprint-elan-DEBUG: 00:54:14.050: 7399822111287: ../libfprint/drivers/elan.c:100 405s (process:2089): libfprint-SSM-DEBUG: 00:54:14.050: [elan] CALIBRATE_NUM_STATES entering state 0 405s (process:2089): libfprint-elan-DEBUG: 00:54:14.050: 7399822111294: ../libfprint/drivers/elan.c:691 405s (process:2089): libfprint-device-DEBUG: 00:54:14.050: Device reported finger status change: FP_FINGER_STATUS_NEEDED 405s (process:2089): libfprint-elan-DEBUG: 00:54:14.050: 7399822111791: ../libfprint/drivers/elan.c:346 405s (process:2089): libfprint-elan-DEBUG: 00:54:14.050: 7399822111802: ../libfprint/drivers/elan.c:366 405s (process:2089): libfprint-elan-DEBUG: 00:54:14.050: 7399822111807: ../libfprint/drivers/elan.c:379 405s (process:2089): libfprint-elan-DEBUG: 00:54:14.051: 7399822112527: ../libfprint/drivers/elan.c:346 405s (process:2089): libfprint-elan-DEBUG: 00:54:14.051: 7399822112571: ../libfprint/drivers/elan.c:335 405s (process:2089): libfprint-SSM-DEBUG: 00:54:14.051: [elan] CALIBRATE_NUM_STATES entering state 1 405s (process:2089): libfprint-elan-DEBUG: 00:54:14.051: 7399822112583: ../libfprint/drivers/elan.c:691 405s (process:2089): libfprint-elan-DEBUG: 00:54:14.051: 7399822112587: ../libfprint/drivers/elan.c:156 405s (process:2089): libfprint-elan-DEBUG: 00:54:14.051: 7399822112593: ../libfprint/drivers/elan.c:118 405s (process:2089): libfprint-SSM-DEBUG: 00:54:14.051: [elan] CALIBRATE_NUM_STATES entering state 2 405s (process:2089): libfprint-elan-DEBUG: 00:54:14.051: 7399822112618: ../libfprint/drivers/elan.c:691 405s (process:2089): libfprint-elan-DEBUG: 00:54:14.052: 7399822113142: ../libfprint/drivers/elan.c:346 405s (process:2089): libfprint-elan-DEBUG: 00:54:14.052: 7399822113166: ../libfprint/drivers/elan.c:366 405s (process:2089): libfprint-elan-DEBUG: 00:54:14.052: 7399822113174: ../libfprint/drivers/elan.c:379 405s (process:2089): libfprint-elan-DEBUG: 00:54:14.052: 7399822113651: ../libfprint/drivers/elan.c:346 405s (process:2089): libfprint-elan-DEBUG: 00:54:14.052: 7399822113667: ../libfprint/drivers/elan.c:335 405s (process:2089): libfprint-SSM-DEBUG: 00:54:14.052: [elan] CALIBRATE_NUM_STATES entering state 3 405s (process:2089): libfprint-elan-DEBUG: 00:54:14.052: 7399822113678: ../libfprint/drivers/elan.c:691 405s (process:2089): libfprint-elan-DEBUG: 00:54:14.052: 7399822113682: ../libfprint/drivers/elan.c:634 405s (process:2089): libfprint-elan-DEBUG: 00:54:14.052: calibration mean: 8248, bg mean: 7978, delta: 270 405s (process:2089): libfprint-SSM-DEBUG: 00:54:14.052: [elan] CALIBRATE_NUM_STATES completed successfully 405s (process:2089): libfprint-elan-DEBUG: 00:54:14.052: 7399822113704: ../libfprint/drivers/elan.c:776 405s (process:2089): libfprint-elan-DEBUG: 00:54:14.052: 7399822113707: ../libfprint/drivers/elan.c:620 405s (process:2089): libfprint-elan-DEBUG: 00:54:14.052: 7399822113711: ../libfprint/drivers/elan.c:100 405s (process:2089): libfprint-SSM-DEBUG: 00:54:14.052: [elan] CAPTURE_NUM_STATES entering state 0 405s (process:2089): libfprint-elan-DEBUG: 00:54:14.053: 7399822114191: ../libfprint/drivers/elan.c:346 405s (process:2089): libfprint-elan-DEBUG: 00:54:14.053: 7399822114212: ../libfprint/drivers/elan.c:366 405s (process:2089): libfprint-elan-DEBUG: 00:54:14.053: 7399822114219: ../libfprint/drivers/elan.c:379 405s (process:2089): libfprint-elan-DEBUG: 00:54:14.053: skipping read, not expecting anything 405s (process:2089): libfprint-elan-DEBUG: 00:54:14.053: 7399822114227: ../libfprint/drivers/elan.c:335 405s (process:2089): libfprint-SSM-DEBUG: 00:54:14.053: [elan] CAPTURE_NUM_STATES entering state 1 405s (process:2089): libfprint-elan-DEBUG: 00:54:14.053: 7399822114683: ../libfprint/drivers/elan.c:346 405s (process:2089): libfprint-elan-DEBUG: 00:54:14.053: 7399822114698: ../libfprint/drivers/elan.c:366 405s (process:2089): libfprint-elan-DEBUG: 00:54:14.053: 7399822114702: ../libfprint/drivers/elan.c:379 405s (process:2089): libfprint-elan-DEBUG: 00:54:14.054: 7399822115234: ../libfprint/drivers/elan.c:346 405s (process:2089): libfprint-elan-DEBUG: 00:54:14.054: 7399822115256: ../libfprint/drivers/elan.c:335 405s (process:2089): libfprint-SSM-DEBUG: 00:54:14.054: [elan] CAPTURE_NUM_STATES entering state 2 405s (process:2089): libfprint-device-DEBUG: 00:54:14.054: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 405s (process:2089): libfprint-image_device-DEBUG: 00:54:14.054: Image device reported finger status: on 405s (process:2089): libfprint-image_device-DEBUG: 00:54:14.054: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 405s (process:2089): libfprint-elan-DEBUG: 00:54:14.054: 7399822115295: ../libfprint/drivers/elan.c:960 405s (process:2089): libfprint-elan-DEBUG: 00:54:14.054: 7399822115782: ../libfprint/drivers/elan.c:346 405s (process:2089): libfprint-elan-DEBUG: 00:54:14.054: 7399822115797: ../libfprint/drivers/elan.c:366 405s (process:2089): libfprint-elan-DEBUG: 00:54:14.054: 7399822115802: ../libfprint/drivers/elan.c:379 405s (process:2089): libfprint-elan-DEBUG: 00:54:14.055: 7399822116386: ../libfprint/drivers/elan.c:346 405s (process:2089): libfprint-elan-DEBUG: 00:54:14.055: 7399822116411: ../libfprint/drivers/elan.c:335 405s (process:2089): libfprint-SSM-DEBUG: 00:54:14.055: [elan] CAPTURE_NUM_STATES entering state 3 405s (process:2089): libfprint-elan-DEBUG: 00:54:14.055: 7399822116423: ../libfprint/drivers/elan.c:203 405s (process:2089): libfprint-elan-DEBUG: 00:54:14.055: 7399822116444: ../libfprint/drivers/elan.c:118 405s (process:2089): libfprint-SSM-DEBUG: 00:54:14.055: [elan] CAPTURE_NUM_STATES entering state 1 405s (process:2089): libfprint-elan-DEBUG: 00:54:14.056: 7399822116962: ../libfprint/drivers/elan.c:346 405s (process:2089): libfprint-elan-DEBUG: 00:54:14.056: 7399822116977: ../libfprint/drivers/elan.c:366 405s (process:2089): libfprint-elan-DEBUG: 00:54:14.056: 7399822116981: ../libfprint/drivers/elan.c:379 405s (process:2089): libfprint-elan-DEBUG: 00:54:14.056: 7399822117543: ../libfprint/drivers/elan.c:346 405s (process:2089): libfprint-elan-DEBUG: 00:54:14.056: 7399822117566: ../libfprint/drivers/elan.c:335 405s (process:2089): libfprint-SSM-DEBUG: 00:54:14.056: [elan] CAPTURE_NUM_STATES entering state 2 405s (process:2089): libfprint-image_device-DEBUG: 00:54:14.056: Image device reported finger status: on 405s (process:2089): libfprint-elan-DEBUG: 00:54:14.057: 7399822118200: ../libfprint/drivers/elan.c:346 405s (process:2089): libfprint-elan-DEBUG: 00:54:14.057: 7399822118223: ../libfprint/drivers/elan.c:366 405s (process:2089): libfprint-elan-DEBUG: 00:54:14.057: 7399822118228: ../libfprint/drivers/elan.c:379 405s (process:2089): libfprint-elan-DEBUG: 00:54:14.057: 7399822118797: ../libfprint/drivers/elan.c:346 405s (process:2089): libfprint-elan-DEBUG: 00:54:14.057: 7399822118816: ../libfprint/drivers/elan.c:335 405s (process:2089): libfprint-SSM-DEBUG: 00:54:14.057: [elan] CAPTURE_NUM_STATES entering state 3 405s (process:2089): libfprint-elan-DEBUG: 00:54:14.057: 7399822118826: ../libfprint/drivers/elan.c:203 405s (process:2089): libfprint-elan-DEBUG: 00:54:14.057: 7399822118845: ../libfprint/drivers/elan.c:118 405s (process:2089): libfprint-SSM-DEBUG: 00:54:14.057: [elan] CAPTURE_NUM_STATES entering state 1 405s (process:2089): libfprint-elan-DEBUG: 00:54:14.058: 7399822119688: ../libfprint/drivers/elan.c:346 405s (process:2089): libfprint-elan-DEBUG: 00:54:14.058: 7399822119718: ../libfprint/drivers/elan.c:366 405s (process:2089): libfprint-elan-DEBUG: 00:54:14.058: 7399822119724: ../libfprint/drivers/elan.c:379 405s (process:2089): libfprint-elan-DEBUG: 00:54:14.059: 7399822120319: ../libfprint/drivers/elan.c:346 405s (process:2089): libfprint-elan-DEBUG: 00:54:14.059: 7399822120340: ../libfprint/drivers/elan.c:335 405s (process:2089): libfprint-SSM-DEBUG: 00:54:14.059: [elan] CAPTURE_NUM_STATES entering state 2 405s (process:2089): libfprint-image_device-DEBUG: 00:54:14.059: Image device reported finger status: on 405s (process:2089): libfprint-elan-DEBUG: 00:54:14.059: 7399822120912: ../libfprint/drivers/elan.c:346 405s (process:2089): libfprint-elan-DEBUG: 00:54:14.060: 7399822120928: ../libfprint/drivers/elan.c:366 405s (process:2089): libfprint-elan-DEBUG: 00:54:14.060: 7399822120934: ../libfprint/drivers/elan.c:379 405s (process:2089): libfprint-elan-DEBUG: 00:54:14.060: 7399822121514: ../libfprint/drivers/elan.c:346 405s (process:2089): libfprint-elan-DEBUG: 00:54:14.060: 7399822121542: ../libfprint/drivers/elan.c:335 405s (process:2089): libfprint-SSM-DEBUG: 00:54:14.060: [elan] CAPTURE_NUM_STATES entering state 3 405s (process:2089): libfprint-elan-DEBUG: 00:54:14.060: 7399822121555: ../libfprint/drivers/elan.c:203 405s (process:2089): libfprint-elan-DEBUG: 00:54:14.060: 7399822121596: ../libfprint/drivers/elan.c:118 405s (process:2089): libfprint-SSM-DEBUG: 00:54:14.060: [elan] CAPTURE_NUM_STATES entering state 1 405s (process:2089): libfprint-elan-DEBUG: 00:54:14.061: 7399822122170: ../libfprint/drivers/elan.c:346 405s (process:2089): libfprint-elan-DEBUG: 00:54:14.061: 7399822122192: ../libfprint/drivers/elan.c:366 405s (process:2089): libfprint-elan-DEBUG: 00:54:14.061: 7399822122200: ../libfprint/drivers/elan.c:379 405s (process:2089): libfprint-elan-DEBUG: 00:54:14.061: 7399822122682: ../libfprint/drivers/elan.c:346 405s (process:2089): libfprint-elan-DEBUG: 00:54:14.061: 7399822122697: ../libfprint/drivers/elan.c:335 405s (process:2089): libfprint-SSM-DEBUG: 00:54:14.061: [elan] CAPTURE_NUM_STATES entering state 2 405s (process:2089): libfprint-image_device-DEBUG: 00:54:14.061: Image device reported finger status: on 405s (process:2089): libfprint-elan-DEBUG: 00:54:14.062: 7399822123345: ../libfprint/drivers/elan.c:346 405s (process:2089): libfprint-elan-DEBUG: 00:54:14.062: 7399822123366: ../libfprint/drivers/elan.c:366 405s (process:2089): libfprint-elan-DEBUG: 00:54:14.062: 7399822123372: ../libfprint/drivers/elan.c:379 405s (process:2089): libfprint-elan-DEBUG: 00:54:14.062: 7399822123915: ../libfprint/drivers/elan.c:346 405s (process:2089): libfprint-elan-DEBUG: 00:54:14.063: 7399822123933: ../libfprint/drivers/elan.c:335 405s (process:2089): libfprint-SSM-DEBUG: 00:54:14.063: [elan] CAPTURE_NUM_STATES entering state 3 405s (process:2089): libfprint-elan-DEBUG: 00:54:14.063: 7399822123944: ../libfprint/drivers/elan.c:203 405s (process:2089): libfprint-elan-DEBUG: 00:54:14.063: 7399822123964: ../libfprint/drivers/elan.c:118 405s (process:2089): libfprint-SSM-DEBUG: 00:54:14.063: [elan] CAPTURE_NUM_STATES entering state 1 405s (process:2089): libfprint-elan-DEBUG: 00:54:14.063: 7399822124501: ../libfprint/drivers/elan.c:346 405s (process:2089): libfprint-elan-DEBUG: 00:54:14.063: 7399822124523: ../libfprint/drivers/elan.c:366 405s (process:2089): libfprint-elan-DEBUG: 00:54:14.063: 7399822124529: ../libfprint/drivers/elan.c:379 405s (process:2089): libfprint-elan-DEBUG: 00:54:14.064: 7399822125033: ../libfprint/drivers/elan.c:346 405s (process:2089): libfprint-elan-DEBUG: 00:54:14.064: 7399822125066: ../libfprint/drivers/elan.c:335 405s (process:2089): libfprint-SSM-DEBUG: 00:54:14.064: [elan] CAPTURE_NUM_STATES entering state 2 405s (process:2089): libfprint-image_device-DEBUG: 00:54:14.064: Image device reported finger status: on 405s (process:2089): libfprint-elan-DEBUG: 00:54:14.064: 7399822125558: ../libfprint/drivers/elan.c:346 405s (process:2089): libfprint-elan-DEBUG: 00:54:14.064: 7399822125574: ../libfprint/drivers/elan.c:366 405s (process:2089): libfprint-elan-DEBUG: 00:54:14.064: 7399822125580: ../libfprint/drivers/elan.c:379 405s (process:2089): libfprint-elan-DEBUG: 00:54:14.065: 7399822126151: ../libfprint/drivers/elan.c:346 405s (process:2089): libfprint-elan-DEBUG: 00:54:14.065: 7399822126174: ../libfprint/drivers/elan.c:335 405s (process:2089): libfprint-SSM-DEBUG: 00:54:14.065: [elan] CAPTURE_NUM_STATES entering state 3 405s (process:2089): libfprint-elan-DEBUG: 00:54:14.065: 7399822126186: ../libfprint/drivers/elan.c:203 405s (process:2089): libfprint-elan-DEBUG: 00:54:14.065: 7399822126205: ../libfprint/drivers/elan.c:118 405s (process:2089): libfprint-SSM-DEBUG: 00:54:14.065: [elan] CAPTURE_NUM_STATES entering state 1 405s (process:2089): libfprint-elan-DEBUG: 00:54:14.065: 7399822126723: ../libfprint/drivers/elan.c:346 405s (process:2089): libfprint-elan-DEBUG: 00:54:14.065: 7399822126738: ../libfprint/drivers/elan.c:366 405s (process:2089): libfprint-elan-DEBUG: 00:54:14.065: 7399822126743: ../libfprint/drivers/elan.c:379 405s (process:2089): libfprint-elan-DEBUG: 00:54:14.066: 7399822127540: ../libfprint/drivers/elan.c:346 405s (process:2089): libfprint-elan-DEBUG: 00:54:14.066: 7399822127574: ../libfprint/drivers/elan.c:335 405s (process:2089): libfprint-SSM-DEBUG: 00:54:14.066: [elan] CAPTURE_NUM_STATES entering state 2 405s (process:2089): libfprint-image_device-DEBUG: 00:54:14.066: Image device reported finger status: on 405s (process:2089): libfprint-elan-DEBUG: 00:54:14.067: 7399822128157: ../libfprint/drivers/elan.c:346 405s (process:2089): libfprint-elan-DEBUG: 00:54:14.067: 7399822128180: ../libfprint/drivers/elan.c:366 405s (process:2089): libfprint-elan-DEBUG: 00:54:14.067: 7399822128187: ../libfprint/drivers/elan.c:379 405s (process:2089): libfprint-elan-DEBUG: 00:54:14.067: 7399822128736: ../libfprint/drivers/elan.c:346 405s (process:2089): libfprint-elan-DEBUG: 00:54:14.067: 7399822128755: ../libfprint/drivers/elan.c:335 405s (process:2089): libfprint-SSM-DEBUG: 00:54:14.067: [elan] CAPTURE_NUM_STATES entering state 3 405s (process:2089): libfprint-elan-DEBUG: 00:54:14.067: 7399822128765: ../libfprint/drivers/elan.c:203 405s (process:2089): libfprint-elan-DEBUG: 00:54:14.067: 7399822128785: ../libfprint/drivers/elan.c:118 405s (process:2089): libfprint-SSM-DEBUG: 00:54:14.067: [elan] CAPTURE_NUM_STATES entering state 1 405s (process:2089): libfprint-elan-DEBUG: 00:54:14.068: 7399822129330: ../libfprint/drivers/elan.c:346 405s (process:2089): libfprint-elan-DEBUG: 00:54:14.068: 7399822129354: ../libfprint/drivers/elan.c:366 405s (process:2089): libfprint-elan-DEBUG: 00:54:14.068: 7399822129360: ../libfprint/drivers/elan.c:379 405s (process:2089): libfprint-elan-DEBUG: 00:54:14.068: 7399822129846: ../libfprint/drivers/elan.c:346 405s (process:2089): libfprint-elan-DEBUG: 00:54:14.068: 7399822129862: ../libfprint/drivers/elan.c:335 405s (process:2089): libfprint-SSM-DEBUG: 00:54:14.068: [elan] CAPTURE_NUM_STATES entering state 2 405s (process:2089): libfprint-image_device-DEBUG: 00:54:14.068: Image device reported finger status: on 405s (process:2089): libfprint-elan-DEBUG: 00:54:14.069: 7399822130377: ../libfprint/drivers/elan.c:346 405s (process:2089): libfprint-elan-DEBUG: 00:54:14.069: 7399822130398: ../libfprint/drivers/elan.c:366 405s (process:2089): libfprint-elan-DEBUG: 00:54:14.069: 7399822130404: ../libfprint/drivers/elan.c:379 405s (process:2089): libfprint-elan-DEBUG: 00:54:14.070: 7399822130969: ../libfprint/drivers/elan.c:346 405s (process:2089): libfprint-elan-DEBUG: 00:54:14.070: 7399822130988: ../libfprint/drivers/elan.c:335 405s (process:2089): libfprint-SSM-DEBUG: 00:54:14.070: [elan] CAPTURE_NUM_STATES entering state 3 405s (process:2089): libfprint-elan-DEBUG: 00:54:14.070: 7399822131012: ../libfprint/drivers/elan.c:203 405s (process:2089): libfprint-elan-DEBUG: 00:54:14.070: 7399822131041: ../libfprint/drivers/elan.c:118 405s (process:2089): libfprint-SSM-DEBUG: 00:54:14.070: [elan] CAPTURE_NUM_STATES entering state 1 405s (process:2089): libfprint-elan-DEBUG: 00:54:14.070: 7399822131890: ../libfprint/drivers/elan.c:346 405s (process:2089): libfprint-elan-DEBUG: 00:54:14.070: 7399822131907: ../libfprint/drivers/elan.c:366 405s (process:2089): libfprint-elan-DEBUG: 00:54:14.070: 7399822131914: ../libfprint/drivers/elan.c:379 405s (process:2089): libfprint-elan-DEBUG: 00:54:14.071: 7399822132479: ../libfprint/drivers/elan.c:346 405s (process:2089): libfprint-elan-DEBUG: 00:54:14.071: 7399822132498: ../libfprint/drivers/elan.c:335 405s (process:2089): libfprint-SSM-DEBUG: 00:54:14.071: [elan] CAPTURE_NUM_STATES entering state 2 405s (process:2089): libfprint-image_device-DEBUG: 00:54:14.071: Image device reported finger status: on 405s (process:2089): libfprint-elan-DEBUG: 00:54:14.072: 7399822132994: ../libfprint/drivers/elan.c:346 405s (process:2089): libfprint-elan-DEBUG: 00:54:14.072: 7399822133017: ../libfprint/drivers/elan.c:366 405s (process:2089): libfprint-elan-DEBUG: 00:54:14.072: 7399822133023: ../libfprint/drivers/elan.c:379 405s (process:2089): libfprint-elan-DEBUG: 00:54:14.072: 7399822133612: ../libfprint/drivers/elan.c:346 405s (process:2089): libfprint-elan-DEBUG: 00:54:14.072: 7399822133626: ../libfprint/drivers/elan.c:335 405s (process:2089): libfprint-SSM-DEBUG: 00:54:14.072: [elan] CAPTURE_NUM_STATES entering state 3 405s (process:2089): libfprint-elan-DEBUG: 00:54:14.072: 7399822133635: ../libfprint/drivers/elan.c:203 405s (process:2089): libfprint-elan-DEBUG: 00:54:14.072: 7399822133649: ../libfprint/drivers/elan.c:118 405s (process:2089): libfprint-SSM-DEBUG: 00:54:14.072: [elan] CAPTURE_NUM_STATES entering state 1 405s (process:2089): libfprint-elan-DEBUG: 00:54:14.073: 7399822134156: ../libfprint/drivers/elan.c:346 405s (process:2089): libfprint-elan-DEBUG: 00:54:14.073: 7399822134173: ../libfprint/drivers/elan.c:366 405s (process:2089): libfprint-elan-DEBUG: 00:54:14.073: 7399822134178: ../libfprint/drivers/elan.c:379 405s (process:2089): libfprint-elan-DEBUG: 00:54:14.073: 7399822134624: ../libfprint/drivers/elan.c:346 405s (process:2089): libfprint-elan-DEBUG: 00:54:14.073: 7399822134635: ../libfprint/drivers/elan.c:335 405s (process:2089): libfprint-SSM-DEBUG: 00:54:14.073: [elan] CAPTURE_NUM_STATES entering state 2 405s (process:2089): libfprint-image_device-DEBUG: 00:54:14.073: Image device reported finger status: on 405s (process:2089): libfprint-elan-DEBUG: 00:54:14.074: 7399822135074: ../libfprint/drivers/elan.c:346 405s (process:2089): libfprint-elan-DEBUG: 00:54:14.074: 7399822135087: ../libfprint/drivers/elan.c:366 405s (process:2089): libfprint-elan-DEBUG: 00:54:14.074: 7399822135092: ../libfprint/drivers/elan.c:379 405s (process:2089): libfprint-elan-DEBUG: 00:54:14.074: 7399822135763: ../libfprint/drivers/elan.c:346 405s (process:2089): libfprint-elan-DEBUG: 00:54:14.074: 7399822135795: ../libfprint/drivers/elan.c:335 405s (process:2089): libfprint-SSM-DEBUG: 00:54:14.074: [elan] CAPTURE_NUM_STATES entering state 3 405s (process:2089): libfprint-elan-DEBUG: 00:54:14.074: 7399822135808: ../libfprint/drivers/elan.c:203 405s (process:2089): libfprint-elan-DEBUG: 00:54:14.074: 7399822135832: ../libfprint/drivers/elan.c:118 405s (process:2089): libfprint-SSM-DEBUG: 00:54:14.074: [elan] CAPTURE_NUM_STATES entering state 1 405s (process:2089): libfprint-elan-DEBUG: 00:54:14.075: 7399822136496: ../libfprint/drivers/elan.c:346 405s (process:2089): libfprint-elan-DEBUG: 00:54:14.075: 7399822136520: ../libfprint/drivers/elan.c:366 405s (process:2089): libfprint-elan-DEBUG: 00:54:14.075: 7399822136528: ../libfprint/drivers/elan.c:379 405s (process:2089): libfprint-elan-DEBUG: 00:54:14.076: 7399822137045: ../libfprint/drivers/elan.c:346 405s (process:2089): libfprint-elan-DEBUG: 00:54:14.076: 7399822137096: ../libfprint/drivers/elan.c:335 405s (process:2089): libfprint-SSM-DEBUG: 00:54:14.076: [elan] CAPTURE_NUM_STATES entering state 2 405s (process:2089): libfprint-image_device-DEBUG: 00:54:14.076: Image device reported finger status: on 405s (process:2089): libfprint-elan-DEBUG: 00:54:14.076: 7399822137526: ../libfprint/drivers/elan.c:346 405s (process:2089): libfprint-elan-DEBUG: 00:54:14.076: 7399822137538: ../libfprint/drivers/elan.c:366 405s (process:2089): libfprint-elan-DEBUG: 00:54:14.076: 7399822137543: ../libfprint/drivers/elan.c:379 405s (process:2089): libfprint-elan-DEBUG: 00:54:14.077: 7399822138093: ../libfprint/drivers/elan.c:346 405s (process:2089): libfprint-elan-DEBUG: 00:54:14.077: 7399822138111: ../libfprint/drivers/elan.c:335 405s (process:2089): libfprint-SSM-DEBUG: 00:54:14.077: [elan] CAPTURE_NUM_STATES entering state 3 405s (process:2089): libfprint-elan-DEBUG: 00:54:14.077: 7399822138122: ../libfprint/drivers/elan.c:203 405s (process:2089): libfprint-elan-DEBUG: 00:54:14.077: 7399822138139: ../libfprint/drivers/elan.c:118 405s (process:2089): libfprint-SSM-DEBUG: 00:54:14.077: [elan] CAPTURE_NUM_STATES entering state 1 405s (process:2089): libfprint-elan-DEBUG: 00:54:14.077: 7399822138631: ../libfprint/drivers/elan.c:346 405s (process:2089): libfprint-elan-DEBUG: 00:54:14.077: 7399822138642: ../libfprint/drivers/elan.c:366 405s (process:2089): libfprint-elan-DEBUG: 00:54:14.077: 7399822138648: ../libfprint/drivers/elan.c:379 405s (process:2089): libfprint-elan-DEBUG: 00:54:14.078: 7399822139124: ../libfprint/drivers/elan.c:346 405s (process:2089): libfprint-elan-DEBUG: 00:54:14.078: 7399822139139: ../libfprint/drivers/elan.c:335 405s (process:2089): libfprint-SSM-DEBUG: 00:54:14.078: [elan] CAPTURE_NUM_STATES entering state 2 405s (process:2089): libfprint-image_device-DEBUG: 00:54:14.078: Image device reported finger status: on 405s (process:2089): libfprint-elan-DEBUG: 00:54:14.078: 7399822139591: ../libfprint/drivers/elan.c:346 405s (process:2089): libfprint-elan-DEBUG: 00:54:14.078: 7399822139603: ../libfprint/drivers/elan.c:366 405s (process:2089): libfprint-elan-DEBUG: 00:54:14.078: 7399822139609: ../libfprint/drivers/elan.c:379 405s (process:2089): libfprint-elan-DEBUG: 00:54:14.079: 7399822140197: ../libfprint/drivers/elan.c:346 405s (process:2089): libfprint-elan-DEBUG: 00:54:14.079: 7399822140217: ../libfprint/drivers/elan.c:335 405s (process:2089): libfprint-SSM-DEBUG: 00:54:14.079: [elan] CAPTURE_NUM_STATES entering state 3 405s (process:2089): libfprint-elan-DEBUG: 00:54:14.079: 7399822140232: ../libfprint/drivers/elan.c:203 405s (process:2089): libfprint-elan-DEBUG: 00:54:14.079: 7399822140246: ../libfprint/drivers/elan.c:118 405s (process:2089): libfprint-SSM-DEBUG: 00:54:14.079: [elan] CAPTURE_NUM_STATES entering state 1 405s (process:2089): libfprint-elan-DEBUG: 00:54:14.079: 7399822140706: ../libfprint/drivers/elan.c:346 405s (process:2089): libfprint-elan-DEBUG: 00:54:14.079: 7399822140719: ../libfprint/drivers/elan.c:366 405s (process:2089): libfprint-elan-DEBUG: 00:54:14.079: 7399822140723: ../libfprint/drivers/elan.c:379 405s (process:2089): libfprint-elan-DEBUG: 00:54:14.080: 7399822141234: ../libfprint/drivers/elan.c:346 405s (process:2089): libfprint-elan-DEBUG: 00:54:14.080: 7399822141249: ../libfprint/drivers/elan.c:335 405s (process:2089): libfprint-SSM-DEBUG: 00:54:14.080: [elan] CAPTURE_NUM_STATES entering state 2 405s (process:2089): libfprint-image_device-DEBUG: 00:54:14.080: Image device reported finger status: on 405s (process:2089): libfprint-elan-DEBUG: 00:54:14.080: 7399822141667: ../libfprint/drivers/elan.c:346 405s (process:2089): libfprint-elan-DEBUG: 00:54:14.080: 7399822141678: ../libfprint/drivers/elan.c:366 405s (process:2089): libfprint-elan-DEBUG: 00:54:14.080: 7399822141684: ../libfprint/drivers/elan.c:379 405s (process:2089): libfprint-elan-DEBUG: 00:54:14.081: 7399822142252: ../libfprint/drivers/elan.c:346 405s (process:2089): libfprint-elan-DEBUG: 00:54:14.081: 7399822142270: ../libfprint/drivers/elan.c:335 405s (process:2089): libfprint-SSM-DEBUG: 00:54:14.081: [elan] CAPTURE_NUM_STATES entering state 3 405s (process:2089): libfprint-elan-DEBUG: 00:54:14.081: 7399822142280: ../libfprint/drivers/elan.c:203 405s (process:2089): libfprint-elan-DEBUG: 00:54:14.081: 7399822142292: ../libfprint/drivers/elan.c:118 405s (process:2089): libfprint-SSM-DEBUG: 00:54:14.081: [elan] CAPTURE_NUM_STATES entering state 1 405s (process:2089): libfprint-elan-DEBUG: 00:54:14.081: 7399822142794: ../libfprint/drivers/elan.c:346 405s (process:2089): libfprint-elan-DEBUG: 00:54:14.081: 7399822142806: ../libfprint/drivers/elan.c:366 405s (process:2089): libfprint-elan-DEBUG: 00:54:14.081: 7399822142812: ../libfprint/drivers/elan.c:379 405s (process:2089): libfprint-elan-DEBUG: 00:54:14.082: 7399822143307: ../libfprint/drivers/elan.c:346 405s (process:2089): libfprint-elan-DEBUG: 00:54:14.082: 7399822143323: ../libfprint/drivers/elan.c:335 405s (process:2089): libfprint-SSM-DEBUG: 00:54:14.082: [elan] CAPTURE_NUM_STATES entering state 2 405s (process:2089): libfprint-image_device-DEBUG: 00:54:14.082: Image device reported finger status: on 405s (process:2089): libfprint-elan-DEBUG: 00:54:14.082: 7399822143746: ../libfprint/drivers/elan.c:346 405s (process:2089): libfprint-elan-DEBUG: 00:54:14.082: 7399822143757: ../libfprint/drivers/elan.c:366 405s (process:2089): libfprint-elan-DEBUG: 00:54:14.082: 7399822143762: ../libfprint/drivers/elan.c:379 405s (process:2089): libfprint-elan-DEBUG: 00:54:14.083: 7399822144325: ../libfprint/drivers/elan.c:346 405s (process:2089): libfprint-elan-DEBUG: 00:54:14.083: 7399822144343: ../libfprint/drivers/elan.c:335 405s (process:2089): libfprint-SSM-DEBUG: 00:54:14.083: [elan] CAPTURE_NUM_STATES entering state 3 405s (process:2089): libfprint-elan-DEBUG: 00:54:14.083: 7399822144354: ../libfprint/drivers/elan.c:203 405s (process:2089): libfprint-elan-DEBUG: 00:54:14.083: 7399822144387: ../libfprint/drivers/elan.c:118 405s (process:2089): libfprint-SSM-DEBUG: 00:54:14.083: [elan] CAPTURE_NUM_STATES entering state 1 405s (process:2089): libfprint-elan-DEBUG: 00:54:14.083: 7399822144865: ../libfprint/drivers/elan.c:346 405s (process:2089): libfprint-elan-DEBUG: 00:54:14.083: 7399822144877: ../libfprint/drivers/elan.c:366 405s (process:2089): libfprint-elan-DEBUG: 00:54:14.083: 7399822144883: ../libfprint/drivers/elan.c:379 405s (process:2089): libfprint-elan-DEBUG: 00:54:14.084: 7399822145374: ../libfprint/drivers/elan.c:346 405s (process:2089): libfprint-elan-DEBUG: 00:54:14.084: 7399822145390: ../libfprint/drivers/elan.c:335 405s (process:2089): libfprint-SSM-DEBUG: 00:54:14.084: [elan] CAPTURE_NUM_STATES entering state 2 405s (process:2089): libfprint-image_device-DEBUG: 00:54:14.084: Image device reported finger status: on 405s (process:2089): libfprint-elan-DEBUG: 00:54:14.084: 7399822145837: ../libfprint/drivers/elan.c:346 405s (process:2089): libfprint-elan-DEBUG: 00:54:14.084: 7399822145847: ../libfprint/drivers/elan.c:366 405s (process:2089): libfprint-elan-DEBUG: 00:54:14.084: 7399822145853: ../libfprint/drivers/elan.c:379 405s (process:2089): libfprint-elan-DEBUG: 00:54:14.085: 7399822146646: ../libfprint/drivers/elan.c:346 405s (process:2089): libfprint-elan-DEBUG: 00:54:14.085: 7399822146675: ../libfprint/drivers/elan.c:335 405s (process:2089): libfprint-SSM-DEBUG: 00:54:14.085: [elan] CAPTURE_NUM_STATES entering state 3 405s (process:2089): libfprint-elan-DEBUG: 00:54:14.085: 7399822146687: ../libfprint/drivers/elan.c:203 405s (process:2089): libfprint-elan-DEBUG: 00:54:14.085: 7399822146705: ../libfprint/drivers/elan.c:118 405s (process:2089): libfprint-SSM-DEBUG: 00:54:14.085: [elan] CAPTURE_NUM_STATES entering state 1 405s (process:2089): libfprint-elan-DEBUG: 00:54:14.086: 7399822147240: ../libfprint/drivers/elan.c:346 405s (process:2089): libfprint-elan-DEBUG: 00:54:14.086: 7399822147260: ../libfprint/drivers/elan.c:366 405s (process:2089): libfprint-elan-DEBUG: 00:54:14.086: 7399822147266: ../libfprint/drivers/elan.c:379 405s (process:2089): libfprint-elan-DEBUG: 00:54:14.086: 7399822147735: ../libfprint/drivers/elan.c:346 405s (process:2089): libfprint-elan-DEBUG: 00:54:14.086: 7399822147748: ../libfprint/drivers/elan.c:335 405s (process:2089): libfprint-SSM-DEBUG: 00:54:14.086: [elan] CAPTURE_NUM_STATES entering state 2 405s (process:2089): libfprint-image_device-DEBUG: 00:54:14.086: Image device reported finger status: on 405s (process:2089): libfprint-elan-DEBUG: 00:54:14.087: 7399822148230: ../libfprint/drivers/elan.c:346 405s (process:2089): libfprint-elan-DEBUG: 00:54:14.087: 7399822148244: ../libfprint/drivers/elan.c:366 405s (process:2089): libfprint-elan-DEBUG: 00:54:14.087: 7399822148250: ../libfprint/drivers/elan.c:379 405s (process:2089): libfprint-elan-DEBUG: 00:54:14.087: 7399822148757: ../libfprint/drivers/elan.c:346 405s (process:2089): libfprint-elan-DEBUG: 00:54:14.087: 7399822148771: ../libfprint/drivers/elan.c:335 405s (process:2089): libfprint-SSM-DEBUG: 00:54:14.087: [elan] CAPTURE_NUM_STATES entering state 3 405s (process:2089): libfprint-elan-DEBUG: 00:54:14.087: 7399822148781: ../libfprint/drivers/elan.c:203 405s (process:2089): libfprint-elan-DEBUG: 00:54:14.087: 7399822148796: ../libfprint/drivers/elan.c:118 405s (process:2089): libfprint-SSM-DEBUG: 00:54:14.087: [elan] CAPTURE_NUM_STATES entering state 1 405s (process:2089): libfprint-elan-DEBUG: 00:54:14.088: 7399822149274: ../libfprint/drivers/elan.c:346 405s (process:2089): libfprint-elan-DEBUG: 00:54:14.088: 7399822149292: ../libfprint/drivers/elan.c:366 405s (process:2089): libfprint-elan-DEBUG: 00:54:14.088: 7399822149298: ../libfprint/drivers/elan.c:379 405s (process:2089): libfprint-elan-DEBUG: 00:54:14.088: 7399822149790: ../libfprint/drivers/elan.c:346 405s (process:2089): libfprint-elan-DEBUG: 00:54:14.088: 7399822149801: ../libfprint/drivers/elan.c:335 405s (process:2089): libfprint-SSM-DEBUG: 00:54:14.088: [elan] CAPTURE_NUM_STATES entering state 2 405s (process:2089): libfprint-image_device-DEBUG: 00:54:14.088: Image device reported finger status: on 405s (process:2089): libfprint-elan-DEBUG: 00:54:14.089: 7399822150295: ../libfprint/drivers/elan.c:346 405s (process:2089): libfprint-elan-DEBUG: 00:54:14.089: 7399822150308: ../libfprint/drivers/elan.c:366 405s (process:2089): libfprint-elan-DEBUG: 00:54:14.089: 7399822150315: ../libfprint/drivers/elan.c:379 405s (process:2089): libfprint-elan-DEBUG: 00:54:14.089: 7399822150848: ../libfprint/drivers/elan.c:346 405s (process:2089): libfprint-elan-DEBUG: 00:54:14.089: 7399822150862: ../libfprint/drivers/elan.c:335 405s (process:2089): libfprint-SSM-DEBUG: 00:54:14.089: [elan] CAPTURE_NUM_STATES entering state 3 405s (process:2089): libfprint-elan-DEBUG: 00:54:14.089: 7399822150871: ../libfprint/drivers/elan.c:203 405s (process:2089): libfprint-elan-DEBUG: 00:54:14.089: 7399822150885: ../libfprint/drivers/elan.c:118 405s (process:2089): libfprint-SSM-DEBUG: 00:54:14.089: [elan] CAPTURE_NUM_STATES entering state 1 405s (process:2089): libfprint-elan-DEBUG: 00:54:14.090: 7399822151426: ../libfprint/drivers/elan.c:346 405s (process:2089): libfprint-elan-DEBUG: 00:54:14.090: 7399822151442: ../libfprint/drivers/elan.c:366 405s (process:2089): libfprint-elan-DEBUG: 00:54:14.090: 7399822151448: ../libfprint/drivers/elan.c:379 405s (process:2089): libfprint-elan-DEBUG: 00:54:14.090: 7399822151884: ../libfprint/drivers/elan.c:346 405s (process:2089): libfprint-elan-DEBUG: 00:54:14.090: 7399822151896: ../libfprint/drivers/elan.c:335 405s (process:2089): libfprint-SSM-DEBUG: 00:54:14.090: [elan] CAPTURE_NUM_STATES entering state 2 405s (process:2089): libfprint-SSM-DEBUG: 00:54:14.090: [elan] CAPTURE_NUM_STATES completed successfully 405s (process:2089): libfprint-elan-DEBUG: 00:54:14.090: 7399822151916: ../libfprint/drivers/elan.c:586 405s (process:2089): libfprint-elan-DEBUG: 00:54:14.090: 7399822151919: ../libfprint/drivers/elan.c:315 405s (process:2089): libfprint-elan-DEBUG: 00:54:14.091: 7399822151926: ../libfprint/drivers/elan.c:272 405s (process:2089): libfprint-elan-DEBUG: 00:54:14.091: 7399822152727: ../libfprint/drivers/elan.c:272 405s (process:2089): libfprint-elan-DEBUG: 00:54:14.092: 7399822153545: ../libfprint/drivers/elan.c:272 405s (process:2089): libfprint-elan-DEBUG: 00:54:14.093: 7399822154342: ../libfprint/drivers/elan.c:272 405s (process:2089): libfprint-elan-DEBUG: 00:54:14.094: 7399822155182: ../libfprint/drivers/elan.c:272 405s (process:2089): libfprint-elan-DEBUG: 00:54:14.095: 7399822155962: ../libfprint/drivers/elan.c:272 405s (process:2089): libfprint-elan-DEBUG: 00:54:14.095: 7399822156756: ../libfprint/drivers/elan.c:272 405s (process:2089): libfprint-elan-DEBUG: 00:54:14.096: 7399822157551: ../libfprint/drivers/elan.c:272 405s (process:2089): libfprint-elan-DEBUG: 00:54:14.097: 7399822158354: ../libfprint/drivers/elan.c:272 405s (process:2089): libfprint-elan-DEBUG: 00:54:14.098: 7399822159145: ../libfprint/drivers/elan.c:272 405s (process:2089): libfprint-elan-DEBUG: 00:54:14.098: 7399822159914: ../libfprint/drivers/elan.c:272 405s (process:2089): libfprint-elan-DEBUG: 00:54:14.099: 7399822160695: ../libfprint/drivers/elan.c:272 405s (process:2089): libfprint-elan-DEBUG: 00:54:14.100: 7399822161488: ../libfprint/drivers/elan.c:272 405s (process:2089): libfprint-elan-DEBUG: 00:54:14.101: 7399822162281: ../libfprint/drivers/elan.c:272 405s (process:2089): libfprint-assembling-DEBUG: 00:54:14.310: calc delta completed in 0.208644 secs 405s (process:2089): libfprint-assembling-DEBUG: 00:54:14.517: calc delta completed in 0.206657 secs 405s (process:2089): libfprint-assembling-DEBUG: 00:54:14.517: errors: 133465 rev: 143589 405s (process:2089): libfprint-assembling-DEBUG: 00:54:14.724: calc delta completed in 0.206752 secs 405s (process:2089): libfprint-assembling-DEBUG: 00:54:14.724: height is 225 405s (process:2089): libfprint-image_device-DEBUG: 00:54:14.724: Image device captured an image 405s (process:2089): libfprint-image_device-DEBUG: 00:54:14.726: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 405s (process:2089): libfprint-elan-DEBUG: 00:54:14.726: 7399822787574: ../libfprint/drivers/elan.c:960 405s (process:2089): libfprint-device-DEBUG: 00:54:14.726: Device reported finger status change: FP_FINGER_STATUS_PRESENT 405s (process:2089): libfprint-elan-DEBUG: 00:54:14.726: 7399822787596: ../libfprint/drivers/elan.c:507 405s (process:2089): libfprint-elan-DEBUG: 00:54:14.726: 7399822787601: ../libfprint/drivers/elan.c:100 405s (process:2089): libfprint-SSM-DEBUG: 00:54:14.726: [elan] STOP_CAPTURE_NUM_STATES entering state 0 405s (process:2089): libfprint-elan-DEBUG: 00:54:14.726: 7399822787616: ../libfprint/drivers/elan.c:466 405s (process:2089): libfprint-device-DEBUG: 00:54:14.727: Updated temperature model after 0.68 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 405s (process:2089): libfprint-elan-DEBUG: 00:54:14.727: 7399822788447: ../libfprint/drivers/elan.c:346 405s (process:2089): libfprint-elan-DEBUG: 00:54:14.727: 7399822788464: ../libfprint/drivers/elan.c:366 405s (process:2089): libfprint-elan-DEBUG: 00:54:14.727: 7399822788468: ../libfprint/drivers/elan.c:379 405s (process:2089): libfprint-elan-DEBUG: 00:54:14.727: skipping read, not expecting anything 405s (process:2089): libfprint-elan-DEBUG: 00:54:14.727: 7399822788477: ../libfprint/drivers/elan.c:335 405s (process:2089): libfprint-SSM-DEBUG: 00:54:14.727: [elan] STOP_CAPTURE_NUM_STATES completed successfully 405s (process:2089): libfprint-elan-DEBUG: 00:54:14.727: 7399822788487: ../libfprint/drivers/elan.c:483 405s (process:2089): libfprint-device-DEBUG: 00:54:14.727: Device reported finger status change: FP_FINGER_STATUS_NONE 405s (process:2089): libfprint-image_device-DEBUG: 00:54:14.727: Image device reported finger status: off 405s (process:2089): libfprint-image_device-DEBUG: 00:54:14.727: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 405s (process:2089): libfprint-elan-DEBUG: 00:54:14.727: 7399822788513: ../libfprint/drivers/elan.c:960 405s (process:2089): libfprint-image_device-DEBUG: 00:54:14.727: Deactivating image device 405s (process:2089): libfprint-image_device-DEBUG: 00:54:14.727: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_DEACTIVATING 405s (process:2089): libfprint-elan-DEBUG: 00:54:14.727: 7399822788527: ../libfprint/drivers/elan.c:960 405s (process:2089): libfprint-elan-DEBUG: 00:54:14.727: 7399822788531: ../libfprint/drivers/elan.c:975 405s (process:2089): libfprint-image_device-DEBUG: 00:54:14.727: Image device deactivation completed 405s (process:2089): libfprint-image_device-DEBUG: 00:54:14.727: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE 405s (process:2089): libfprint-elan-DEBUG: 00:54:14.727: 7399822788548: ../libfprint/drivers/elan.c:960 405s (process:2089): libfprint-image-DEBUG: 00:54:14.745: Minutiae scan completed in 0.018650 secs 405s (process:2089): libfprint-device-DEBUG: 00:54:14.745: Device reported capture completion 405s (process:2089): libfprint-device-DEBUG: 00:54:14.745: Completing action FPI_DEVICE_ACTION_CAPTURE in idle! 405s (process:2089): libfprint-device-DEBUG: 00:54:14.745: Updated temperature model after 0.02 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 405s (process:2089): libfprint-elan-DEBUG: 00:54:14.745: 7399822806762: ../libfprint/drivers/elan.c:939 405s (process:2089): libfprint-elan-DEBUG: 00:54:14.745: 7399822806772: ../libfprint/drivers/elan.c:100 405s (process:2089): libfprint-image_device-DEBUG: 00:54:14.746: Image device close completed 405s (process:2089): libfprint-device-DEBUG: 00:54:14.746: Device reported close completion 405s (process:2089): libfprint-device-DEBUG: 00:54:14.747: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 405s (process:2089): libfprint-device-DEBUG: 00:54:14.747: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 405s ** (umockdev-run:2085): DEBUG: 00:54:14.863: umockdev.vala:154: Removing test bed /tmp/umockdev.NJXH22 405s (umockdev-run:2085): GLib-DEBUG: 00:54:14.869: unsetenv() is not thread-safe and should not be used after threads are created 405s Comparing PNGs /tmp/libfprint-umockdev-test-7r1q9d89/capture.png and /usr/share/installed-tests/libfprint-2/elan-cobo/capture.png 405s PASS: libfprint-2/driver-elan-cobo.test 405s Running test: libfprint-2/driver-vfs0050.test 405s ** (umockdev-run:2098): DEBUG: 00:54:14.950: umockdev.vala:127: Created udev test bed /tmp/umockdev.4N5K22 405s ** (umockdev-run:2098): DEBUG: 00:54:14.950: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0/usb1/1-9 405s ** (umockdev-run:2098): DEBUG: 00:54:14.952: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0/usb1/1-9 (subsystem usb) 405s ** (umockdev-run:2098): DEBUG: 00:54:14.956: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.4N5K22/dev/bus/usb/001/004 405s ** (umockdev-run:2098): DEBUG: 00:54:14.956: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0/usb1 405s ** (umockdev-run:2098): DEBUG: 00:54:14.958: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0/usb1 (subsystem usb) 406s ** (umockdev-run:2098): DEBUG: 00:54:14.962: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.4N5K22/dev/bus/usb/001/001 406s ** (umockdev-run:2098): DEBUG: 00:54:14.962: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0 406s ** (umockdev-run:2098): DEBUG: 00:54:14.963: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0 (subsystem pci) 406s (umockdev-run:2098): GLib-GIO-DEBUG: 00:54:14.968: _g_io_module_get_default: Found default implementation local (GLocalVfs) for ?gio-vfs? 406s (process:2102): libfprint-context-DEBUG: 00:54:15.144: Initializing FpContext (libfprint version 1.94.8+tod1) 406s (process:2102): libfprint-tod-DEBUG: 00:54:15.144: Impossible to load the shared drivers dir Error opening directory “/usr/lib/arm-linux-gnueabihf/libfprint-2/tod-1”: No such file or directory 406s (process:2102): libfprint-context-DEBUG: 00:54:15.147: No driver found for USB device 1D6B:0002 406s (process:2102): libfprint-device-DEBUG: 00:54:15.147: Device reported probe completion 406s (process:2102): libfprint-device-DEBUG: 00:54:15.148: Completing action FPI_DEVICE_ACTION_PROBE in idle! 406s (process:2102): libfprint-device-DEBUG: 00:54:15.148: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 406s (process:2102): libfprint-SSM-DEBUG: 00:54:15.149: [vfs0050] SSM_STATES entering state 0 406s (process:2102): libfprint-SSM-DEBUG: 00:54:15.150: [vfs0050] SSM_STATES entering state 1 406s (process:2102): libfprint-SSM-DEBUG: 00:54:15.151: [vfs0050] SSM_STATES entering state 2 406s (process:2102): libfprint-SSM-DEBUG: 00:54:15.151: [vfs0050] SSM_STATES entering state 3 406s (process:2102): libfprint-SSM-DEBUG: 00:54:15.151: [vfs0050] SUBSM1_STATES entering state 0 406s (process:2102): libfprint-SSM-DEBUG: 00:54:15.152: [vfs0050] SUBSM1_STATES entering state 1 406s (process:2102): libfprint-SSM-DEBUG: 00:54:15.152: [vfs0050] SUBSM1_STATES entering state 2 406s (process:2102): libfprint-SSM-DEBUG: 00:54:15.153: [vfs0050] SUBSM1_STATES completed successfully 406s (process:2102): libfprint-SSM-DEBUG: 00:54:15.153: [vfs0050] SSM_STATES entering state 4 406s (process:2102): libfprint-SSM-DEBUG: 00:54:15.153: [vfs0050] SUBSM2_STATES entering state 0 406s (process:2102): libfprint-SSM-DEBUG: 00:54:15.153: [vfs0050] SUBSM2_STATES entering state 1 406s (process:2102): libfprint-SSM-DEBUG: 00:54:15.154: [vfs0050] SUBSM2_STATES entering state 2 406s (process:2102): libfprint-SSM-DEBUG: 00:54:15.154: [vfs0050] SUBSM2_STATES entering state 3 406s (process:2102): libfprint-SSM-DEBUG: 00:54:15.155: [vfs0050] SUBSM2_STATES entering state 4 406s (process:2102): libfprint-SSM-DEBUG: 00:54:15.155: [vfs0050] SUBSM2_STATES entering state 5 406s (process:2102): libfprint-SSM-DEBUG: 00:54:15.156: [vfs0050] SUBSM2_STATES entering state 6 406s (process:2102): libfprint-SSM-DEBUG: 00:54:15.156: [vfs0050] SUBSM1_STATES entering state 0 406s (process:2102): libfprint-SSM-DEBUG: 00:54:15.156: [vfs0050] SUBSM1_STATES entering state 1 406s (process:2102): libfprint-SSM-DEBUG: 00:54:15.157: [vfs0050] SUBSM1_STATES entering state 2 406s (process:2102): libfprint-SSM-DEBUG: 00:54:15.157: [vfs0050] SUBSM1_STATES completed successfully 406s (process:2102): libfprint-SSM-DEBUG: 00:54:15.157: [vfs0050] SUBSM2_STATES completed successfully 406s (process:2102): libfprint-SSM-DEBUG: 00:54:15.157: [vfs0050] SSM_STATES entering state 5 406s (process:2102): libfprint-SSM-DEBUG: 00:54:15.157: [vfs0050] SSM_STATES completed successfully 406s (process:2102): libfprint-image_device-DEBUG: 00:54:15.157: Image device open completed 406s (process:2102): libfprint-device-DEBUG: 00:54:15.157: Device reported open completion 406s (process:2102): libfprint-device-DEBUG: 00:54:15.157: Completing action FPI_DEVICE_ACTION_OPEN in idle! 406s (process:2102): libfprint-device-DEBUG: 00:54:15.157: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 406s (process:2102): libfprint-device-DEBUG: 00:54:15.158: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 406s (process:2102): libfprint-image_device-DEBUG: 00:54:15.158: Activating image device 406s (process:2102): libfprint-image_device-DEBUG: 00:54:15.158: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING 406s (process:2102): libfprint-SSM-DEBUG: 00:54:15.158: [vfs0050] SSM_STATES entering state 0 406s (process:2102): libfprint-SSM-DEBUG: 00:54:15.158: [vfs0050] SSM_STATES entering state 1 406s (process:2102): libfprint-SSM-DEBUG: 00:54:15.159: [vfs0050] SSM_STATES entering state 2 406s (process:2102): libfprint-SSM-DEBUG: 00:54:15.160: [vfs0050] SSM_STATES entering state 3 406s (process:2102): libfprint-SSM-DEBUG: 00:54:15.160: [vfs0050] SUBSM1_STATES entering state 0 406s (process:2102): libfprint-SSM-DEBUG: 00:54:15.161: [vfs0050] SUBSM1_STATES entering state 1 406s (process:2102): libfprint-SSM-DEBUG: 00:54:15.161: [vfs0050] SUBSM1_STATES entering state 2 406s (process:2102): libfprint-SSM-DEBUG: 00:54:15.162: [vfs0050] SUBSM1_STATES completed successfully 406s (process:2102): libfprint-SSM-DEBUG: 00:54:15.162: [vfs0050] SSM_STATES entering state 4 406s (process:2102): libfprint-SSM-DEBUG: 00:54:15.162: [vfs0050] SUBSM2_STATES entering state 0 406s (process:2102): libfprint-SSM-DEBUG: 00:54:15.162: [vfs0050] SUBSM2_STATES entering state 1 406s (process:2102): libfprint-SSM-DEBUG: 00:54:15.163: [vfs0050] SUBSM2_STATES entering state 2 406s (process:2102): libfprint-SSM-DEBUG: 00:54:15.163: [vfs0050] SUBSM2_STATES entering state 3 406s (process:2102): libfprint-SSM-DEBUG: 00:54:15.164: [vfs0050] SUBSM2_STATES entering state 4 406s (process:2102): libfprint-SSM-DEBUG: 00:54:15.164: [vfs0050] SUBSM2_STATES entering state 5 406s (process:2102): libfprint-SSM-DEBUG: 00:54:15.164: [vfs0050] SUBSM2_STATES entering state 6 406s (process:2102): libfprint-SSM-DEBUG: 00:54:15.164: [vfs0050] SUBSM1_STATES entering state 0 406s (process:2102): libfprint-SSM-DEBUG: 00:54:15.165: [vfs0050] SUBSM1_STATES entering state 1 406s (process:2102): libfprint-SSM-DEBUG: 00:54:15.165: [vfs0050] SUBSM1_STATES entering state 2 406s (process:2102): libfprint-SSM-DEBUG: 00:54:15.166: [vfs0050] SUBSM1_STATES completed successfully 406s (process:2102): libfprint-SSM-DEBUG: 00:54:15.166: [vfs0050] SUBSM2_STATES completed successfully 406s (process:2102): libfprint-SSM-DEBUG: 00:54:15.166: [vfs0050] SSM_STATES entering state 5 406s (process:2102): libfprint-SSM-DEBUG: 00:54:15.166: [vfs0050] SUBSM2_STATES entering state 0 406s (process:2102): libfprint-SSM-DEBUG: 00:54:15.166: [vfs0050] SUBSM2_STATES entering state 1 406s (process:2102): libfprint-SSM-DEBUG: 00:54:15.167: [vfs0050] SUBSM2_STATES entering state 2 406s (process:2102): libfprint-SSM-DEBUG: 00:54:15.167: [vfs0050] SUBSM2_STATES entering state 3 406s (process:2102): libfprint-SSM-DEBUG: 00:54:15.168: [vfs0050] SUBSM2_STATES entering state 4 406s (process:2102): libfprint-SSM-DEBUG: 00:54:15.168: [vfs0050] SUBSM2_STATES entering state 5 406s (process:2102): libfprint-SSM-DEBUG: 00:54:15.169: [vfs0050] SUBSM2_STATES entering state 6 406s (process:2102): libfprint-SSM-DEBUG: 00:54:15.169: [vfs0050] SUBSM2_STATES completed successfully 406s (process:2102): libfprint-SSM-DEBUG: 00:54:15.169: [vfs0050] SSM_STATES entering state 6 406s (process:2102): libfprint-image_device-DEBUG: 00:54:15.169: Image device activation completed 406s (process:2102): libfprint-image_device-DEBUG: 00:54:15.169: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE 406s (process:2102): libfprint-image_device-DEBUG: 00:54:15.169: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 406s (process:2102): libfprint-device-DEBUG: 00:54:15.169: Device reported finger status change: FP_FINGER_STATUS_NEEDED 406s (process:2102): libfprint-SSM-DEBUG: 00:54:15.169: [vfs0050] SSM_STATES entering state 7 406s (process:2102): libfprint-SSM-DEBUG: 00:54:15.169: [vfs0050] SSM_STATES entering state 8 406s (process:2102): libfprint-device-DEBUG: 00:54:15.169: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 406s (process:2102): libfprint-image_device-DEBUG: 00:54:15.169: Image device reported finger status: on 406s (process:2102): libfprint-image_device-DEBUG: 00:54:15.169: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 406s (process:2102): libfprint-SSM-DEBUG: 00:54:15.170: [vfs0050] SSM_STATES entering state 8 406s (process:2102): libfprint-SSM-DEBUG: 00:54:15.171: [vfs0050] SSM_STATES entering state 8 406s (process:2102): libfprint-SSM-DEBUG: 00:54:15.172: [vfs0050] SSM_STATES entering state 8 406s (process:2102): libfprint-SSM-DEBUG: 00:54:15.172: [vfs0050] SSM_STATES entering state 8 406s (process:2102): libfprint-SSM-DEBUG: 00:54:15.173: [vfs0050] SSM_STATES entering state 8 406s (process:2102): libfprint-SSM-DEBUG: 00:54:15.174: [vfs0050] SSM_STATES entering state 8 406s (process:2102): libfprint-SSM-DEBUG: 00:54:15.174: [vfs0050] SSM_STATES entering state 8 406s (process:2102): libfprint-SSM-DEBUG: 00:54:15.175: [vfs0050] SSM_STATES entering state 8 406s (process:2102): libfprint-SSM-DEBUG: 00:54:15.175: [vfs0050] SSM_STATES entering state 8 406s (process:2102): libfprint-SSM-DEBUG: 00:54:15.176: [vfs0050] SSM_STATES entering state 8 406s (process:2102): libfprint-SSM-DEBUG: 00:54:15.177: [vfs0050] SSM_STATES entering state 8 406s (process:2102): libfprint-SSM-DEBUG: 00:54:15.177: [vfs0050] SSM_STATES entering state 8 406s (process:2102): libfprint-SSM-DEBUG: 00:54:15.178: [vfs0050] SSM_STATES entering state 8 406s (process:2102): libfprint-SSM-DEBUG: 00:54:15.179: [vfs0050] SSM_STATES entering state 8 406s (process:2102): libfprint-SSM-DEBUG: 00:54:15.179: [vfs0050] SSM_STATES entering state 8 406s (process:2102): libfprint-SSM-DEBUG: 00:54:15.180: [vfs0050] SSM_STATES entering state 8 406s (process:2102): libfprint-SSM-DEBUG: 00:54:15.181: [vfs0050] SSM_STATES entering state 8 406s (process:2102): libfprint-SSM-DEBUG: 00:54:15.181: [vfs0050] SSM_STATES entering state 8 406s (process:2102): libfprint-SSM-DEBUG: 00:54:15.182: [vfs0050] SSM_STATES entering state 8 406s (process:2102): libfprint-SSM-DEBUG: 00:54:15.183: [vfs0050] SSM_STATES entering state 8 406s (process:2102): libfprint-SSM-DEBUG: 00:54:15.183: [vfs0050] SSM_STATES entering state 8 406s (process:2102): libfprint-SSM-DEBUG: 00:54:15.184: [vfs0050] SSM_STATES entering state 8 406s (process:2102): libfprint-SSM-DEBUG: 00:54:15.184: [vfs0050] SSM_STATES entering state 8 406s (process:2102): libfprint-SSM-DEBUG: 00:54:15.185: [vfs0050] SSM_STATES entering state 8 406s (process:2102): libfprint-SSM-DEBUG: 00:54:15.185: [vfs0050] SSM_STATES entering state 9 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.186: 1739667255186097 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.186: 1 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.186: 1 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.186: 2 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.186: 1 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.186: 13 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.186: 51 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.186: 9 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.186: 7 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.186: 5 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.186: 3 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.186: 1 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.186: 8 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.186: 6 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.186: 35 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.186: 2 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.186: 31 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.186: 29 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.186: 27 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.186: 25 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.186: 23 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.186: 21 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.186: 19 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.186: 17 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.186: 15 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.186: 13 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.186: 11 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.186: 9 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.186: 7 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.186: 5 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.186: 3 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.186: 1 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.186: 26 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.186: 24 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.186: 22 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.186: 20 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.186: 18 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.186: 16 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.186: 14 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.186: 12 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.186: 10 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.186: 8 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.186: 6 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.186: 4 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.186: 2 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.186: 38 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.186: 36 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.186: 34 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.186: 32 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.186: 30 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.186: 28 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.186: 26 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.186: 24 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.186: 22 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.186: 20 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.186: 18 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.186: 16 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.186: 14 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.186: 12 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.186: 10 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.186: 8 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.186: 6 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.186: 4 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.186: 100 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.186: 98 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.186: 96 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.186: 94 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.186: 92 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.186: 90 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.186: 100 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.186: 98 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.186: 96 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.186: 100 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.186: 99 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.186: 100 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.186: 98 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.186: 96 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.186: 99 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.186: 97 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.186: 95 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.186: 93 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.186: 100 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.186: 98 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.186: 96 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.186: 94 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.186: 92 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.186: 90 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.186: 88 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.186: 86 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.186: 84 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.186: 100 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.186: 98 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.186: 96 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.186: 100 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.186: 99 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.186: 97 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.186: 70 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.186: 68 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.186: 66 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.186: 64 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.186: 97 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.186: 8 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.186: 6 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.186: 4 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.186: 2 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.186: 10 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.186: 8 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.186: 6 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.186: 4 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.186: 2 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.186: 3 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.186: 100 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.186: 99 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.187: 100 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.187: 100 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.187: 99 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.187: 99 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.187: 99 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.187: 99 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.187: 99 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.187: 99 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.187: 100 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.187: 100 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.187: 100 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.187: 99 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.187: 100 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.187: 99 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.187: 99 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.187: 100 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.187: 100 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.187: 100 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.187: 98 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.187: 100 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.187: 100 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.187: 98 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.187: 96 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.187: 94 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.187: 100 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.187: 98 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.187: 96 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.187: 94 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.187: 92 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.187: 90 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.187: 88 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.187: 86 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.187: 84 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.187: 97 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.187: 95 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.187: 93 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.187: 97 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.187: 95 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.187: 93 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.187: 91 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.187: 89 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.187: 87 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.187: 85 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.187: 83 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.187: 87 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.187: 85 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.187: 83 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.187: 81 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.187: 79 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.187: 81 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.187: 79 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.187: 77 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.187: 79 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.187: 77 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.187: 75 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.187: 79 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.187: 75 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.187: 79 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.187: 77 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.187: 75 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.187: 73 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.187: 71 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.187: 71 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.187: 69 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.187: 70 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.187: 68 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.187: 66 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.187: 64 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.187: 66 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.187: 64 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.187: 62 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.187: 60 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.187: 58 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.187: 59 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.187: 60 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.187: 59 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.187: 62 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.187: 61 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.187: 59 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.187: 57 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.187: 58 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.187: 56 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.187: 54 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.187: 52 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.187: 50 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.187: 57 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.187: 54 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.187: 55 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.187: 57 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.187: 54 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.187: 55 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.187: 54 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.187: 56 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.187: 58 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.187: 56 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.187: 54 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.187: 55 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.187: 54 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.187: 52 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.187: 53 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.187: 52 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.187: 50 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.187: 48 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.187: 54 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.187: 54 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.187: 53 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.187: 54 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.187: 53 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.187: 52 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.187: 52 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.187: 50 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.187: 50 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.187: 50 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.187: 49 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.187: 49 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.187: 48 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.187: 49 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.187: 47 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.187: 46 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.187: 45 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.187: 44 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.187: 44 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.187: 44 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.187: 44 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.187: 44 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.187: 44 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.187: 46 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.187: 47 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.188: 47 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.188: 46 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.188: 46 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.188: 44 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.188: 44 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.188: 42 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.188: 43 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.188: 41 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.188: 42 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.188: 40 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.188: 42 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.188: 43 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.188: 43 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.188: 41 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.188: 42 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.188: 40 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.188: 42 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.188: 43 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.188: 42 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.188: 43 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.188: 41 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.188: 42 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.188: 42 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.188: 40 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.188: 42 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.188: 40 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.188: 42 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.188: 43 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.188: 41 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.188: 41 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.188: 40 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.188: 42 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.188: 40 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.188: 42 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.188: 42 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.188: 41 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.188: 41 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.188: 43 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.188: 41 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.188: 41 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.188: 41 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.188: 41 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.188: 41 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.188: 40 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.188: 39 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.188: 38 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.188: 39 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.188: 38 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.188: 38 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.188: 38 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.188: 36 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.188: 34 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.188: 36 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.188: 37 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.188: 38 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.188: 36 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.188: 36 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.188: 35 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.188: 35 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.188: 35 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.188: 36 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.188: 35 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.188: 35 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.188: 33 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.188: 33 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.188: 32 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.188: 32 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.188: 34 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.188: 35 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.188: 35 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.188: 34 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.188: 35 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.188: 33 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.188: 32 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.188: 33 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.188: 34 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.188: 33 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.188: 33 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.188: 33 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.188: 33 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.188: 33 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.188: 34 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.188: 35 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.188: 35 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.188: 34 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.188: 34 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.188: 33 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.188: 33 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.188: 33 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.188: 32 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.188: 32 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.188: 32 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.188: 32 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.188: 31 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.188: 33 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.188: 34 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.188: 32 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.188: 33 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.188: 33 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.188: 32 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.188: 30 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.188: 31 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.188: 31 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.188: 34 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.188: 32 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.188: 33 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.188: 33 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.188: 33 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.188: 31 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.188: 31 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.188: 31 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.188: 29 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.188: 28 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.188: 33 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.188: 32 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.188: 31 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.188: 31 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.188: 29 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.188: 31 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.188: 32 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.188: 31 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.188: 32 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.188: 30 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.188: 33 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.188: 31 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.188: 29 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.189: 29 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.189: 29 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.189: 29 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.189: 30 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.189: 30 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.189: 29 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.189: 29 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.189: 27 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.189: 26 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.189: 24 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.189: 27 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.189: 25 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.189: 27 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.189: 28 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.189: 28 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.189: 61 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.189: 30 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.189: 29 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.189: 29 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.189: 27 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.189: 27 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.189: 26 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.189: 25 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.189: 28 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.189: 27 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.189: 27 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.189: 27 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.189: 27 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.189: 28 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.189: 27 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.189: 27 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.189: 27 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.189: 28 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.189: 28 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.189: 27 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.189: 28 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.189: 26 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.189: 25 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.189: 23 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.189: 24 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.189: 27 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.189: 27 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.189: 28 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.189: 28 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.189: 26 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.189: 27 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.189: 28 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.189: 28 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.189: 28 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.189: 29 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.189: 28 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.189: 28 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.189: 29 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.189: 28 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.189: 27 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.189: 26 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.189: 28 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.189: 28 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.189: 28 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.189: 28 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.189: 28 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.189: 27 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.189: 27 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.189: 28 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.189: 28 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.189: 27 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.189: 26 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.189: 27 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.189: 27 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.189: 26 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.189: 26 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.189: 28 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.189: 27 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.189: 28 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.189: 29 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.189: 29 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.189: 29 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.189: 29 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.189: 28 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.189: 28 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.189: 28 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.189: 27 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.189: 27 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.189: 27 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.189: 28 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.189: 28 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.189: 27 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.189: 27 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.189: 28 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.189: 28 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.189: 28 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.189: 28 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.189: 28 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.189: 28 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.189: 28 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.189: 29 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.189: 28 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.189: 29 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.189: 29 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.189: 27 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.189: 28 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.189: 29 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.189: 29 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.189: 29 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.189: 31 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.189: 29 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.189: 29 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.189: 29 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.189: 29 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.189: 28 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.189: 29 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.189: 28 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.189: 29 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.189: 28 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.189: 28 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.189: 28 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.189: 28 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.189: 29 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.189: 29 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.189: 30 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.189: 30 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.190: 30 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.190: 30 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.190: 29 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.190: 29 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.190: 29 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.190: 29 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.190: 29 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.190: 29 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.190: 31 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.190: 30 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.190: 30 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.190: 30 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.190: 31 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.190: 31 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.190: 30 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.190: 30 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.190: 30 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.190: 29 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.190: 29 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.190: 30 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.190: 30 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.190: 30 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.190: 29 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.190: 30 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.190: 31 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.190: 31 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.190: 31 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.190: 30 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.190: 30 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.190: 31 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.190: 31 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.190: 31 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.190: 30 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.190: 1 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.190: 29 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.190: 30 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.190: 30 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.190: 30 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.190: 29 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.190: 31 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.190: 31 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.190: 31 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.190: 31 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.190: 31 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.190: 32 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.190: 91 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.190: 89 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.190: 86 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.190: 30 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.190: 30 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.190: 30 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.190: 30 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.190: 31 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.190: 30 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.190: 60 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.190: 60 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.190: 31 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.190: 30 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.190: 31 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.190: 30 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.190: 30 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.190: 29 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.190: 28 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.190: 30 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.190: 30 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.190: 30 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.190: 30 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.190: 30 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.190: 62 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.190: 61 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.190: 59 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.190: 57 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.190: 30 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.190: 29 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.190: 29 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.190: 57 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.190: 56 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.190: 53 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.190: 51 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.190: 46 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.190: 31 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.190: 31 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.190: 32 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.190: 32 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.190: 31 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.190: 30 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.190: 30 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.190: 30 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.190: 30 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.190: 30 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.190: 30 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.190: 30 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.190: 30 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.190: 30 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.190: 29 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.190: 30 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.190: 31 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.190: 30 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.190: 29 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.190: 29 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.190: 31 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.190: 31 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.190: 32 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.190: 31 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.190: 31 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.190: 31 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.190: 30 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.190: 30 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.190: 29 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.190: 29 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.190: 29 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.190: 29 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.190: 28 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.190: 27 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.190: 31 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.190: 31 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.190: 30 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.190: 31 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.190: 31 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.190: 31 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.190: 31 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.190: 30 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.190: 29 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.191: 30 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.191: 30 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.191: 29 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.191: 29 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.191: 28 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.191: 27 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.191: 29 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.191: 29 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.191: 30 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.191: 30 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.191: 30 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.191: 30 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.191: 30 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.191: 30 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.191: 31 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.191: 30 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.191: 30 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.191: 30 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.191: 30 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.191: 31 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.191: 30 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.191: 30 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.191: 29 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.191: 29 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.191: 31 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.191: 29 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.191: 30 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.191: 30 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.191: 29 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.191: 29 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.191: 30 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.191: 30 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.191: 30 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.191: 29 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.191: 29 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.191: 29 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.191: 30 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.191: 29 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.191: 29 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.191: 28 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.191: 28 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.191: 28 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.191: 28 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.191: 29 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.191: 28 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.191: 29 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.191: 29 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.191: 29 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.191: 29 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.191: 28 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.191: 28 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.191: 27 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.191: 27 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.191: 27 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.191: 29 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.191: 30 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.191: 29 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.191: 29 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.191: 29 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.191: 29 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.191: 30 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.191: 29 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.191: 30 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.191: 29 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.191: 31 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.191: 30 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.191: 29 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.191: 29 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.191: 29 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.191: 29 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.191: 27 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.191: 28 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.191: 29 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.191: 29 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.191: 28 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.191: 27 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.191: 27 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.191: 29 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.191: 29 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.191: 29 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.191: 28 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.191: 28 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.191: 28 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.191: 28 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.191: 28 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.191: 27 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.191: 28 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.191: 26 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.191: 26 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.191: 26 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.191: 25 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.191: 26 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.191: 26 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.191: 27 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.191: 27 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.191: 28 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.191: 53 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.191: 27 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.191: 28 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.191: 28 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.191: 26 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.191: 25 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.191: 24 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.191: 25 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.191: 24 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.191: 25 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.191: 26 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.191: 26 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.191: 25 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.191: 26 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.191: 27 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.191: 27 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.191: 26 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.191: 25 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.191: 25 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.191: 24 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.191: 24 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.191: 24 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.191: 24 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.191: 25 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.191: 25 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.191: 24 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.191: 26 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.191: 25 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.191: 25 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.191: 25 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.192: 25 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.192: 24 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.192: 24 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.192: 24 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.192: 24 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.192: 24 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.192: 23 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.192: 23 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.192: 26 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.192: 25 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.192: 25 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.192: 24 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.192: 26 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.192: 25 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.192: 24 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.192: 24 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.192: 24 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.192: 23 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.192: 23 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.192: 22 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.192: 22 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.192: 24 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.192: 23 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.192: 24 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.192: 23 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.192: 22 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.192: 22 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.192: 24 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.192: 23 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.192: 22 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.192: 22 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.192: 22 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.192: 23 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.192: 23 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.192: 24 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.192: 23 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.192: 23 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.192: 24 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.192: 23 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.192: 22 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.192: 24 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.192: 22 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.192: 93 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.192: 24 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.192: 22 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.192: 22 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.192: 22 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.192: 22 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.192: 22 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.192: 21 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.192: 21 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.192: 23 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.192: 21 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.192: 22 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.192: 22 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.192: 22 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.192: 21 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.192: 22 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.192: 21 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.192: 24 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.192: 23 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.192: 23 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.192: 22 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.192: 22 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.192: 22 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.192: 22 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.192: 22 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.192: 22 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.192: 21 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.192: 22 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.192: 22 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.192: 21 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.192: 21 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.192: 22 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.192: 21 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.192: 21 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.192: 21 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.192: 21 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.192: 20 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.192: 20 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.192: 20 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.192: 21 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.192: 21 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.192: 20 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.192: 21 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.192: 20 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.192: 21 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.192: 21 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.192: 21 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.192: 92 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.192: 20 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.192: 22 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.192: 22 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.192: 21 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.192: 22 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.192: 21 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.192: 21 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.192: 20 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.192: 21 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.192: 20 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.192: 20 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.192: 20 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.192: 20 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.192: 20 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.192: 19 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.192: 20 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.192: 20 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.192: 20 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.192: 19 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.192: 20 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.192: 19 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.192: 19 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.192: 19 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.193: 19 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.193: 19 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.193: 19 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.193: 19 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.193: 19 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.193: 19 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.193: 18 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.193: 18 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.193: 19 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.193: 18 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.193: 17 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.193: 19 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.193: 18 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.193: 19 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.193: 18 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.193: 18 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.193: 18 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.193: 18 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.193: 18 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.193: 18 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.193: 18 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.193: 19 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.193: 19 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.193: 19 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.193: 18 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.193: 17 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.193: 18 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.193: 92 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.193: 18 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.193: 18 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.193: 19 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.193: 18 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.193: 18 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.193: 18 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.193: 18 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.193: 59 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.193: 75 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.193: 74 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.193: 18 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.193: 18 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.193: 17 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.193: 17 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.193: 17 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.193: 18 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.193: 17 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.193: 17 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.193: 37 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.193: 36 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.193: 54 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.193: 17 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.193: 17 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.193: 16 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.193: 17 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.193: 17 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.193: 73 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.193: 71 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.193: 17 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.193: 16 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.193: 16 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.193: 15 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.193: 16 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.193: 17 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.193: 16 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.193: 17 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.193: 17 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.193: 16 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.193: 16 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.193: 16 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.193: 15 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.193: 16 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.193: 16 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.193: 16 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.193: 15 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.193: 15 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.193: 15 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.193: 15 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.193: 16 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.193: 16 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.193: 15 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.193: 15 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.193: 15 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.193: 14 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.193: 16 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.193: 16 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.193: 15 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.193: 14 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.193: 14 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.193: 14 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.193: 15 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.193: 14 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.193: 15 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.193: 15 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.193: 15 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.193: 15 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.193: 15 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.193: 15 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.193: 14 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.193: 14 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.193: 13 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.193: 13 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.193: 14 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.193: 15 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.193: 14 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.193: 14 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.193: 14 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.193: 14 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.193: 13 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.193: 14 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.193: 13 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.193: 52 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.193: 51 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.193: 15 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.193: 34 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.193: 32 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.193: 13 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.193: 13 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.193: 13 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.193: 13 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.193: 13 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.193: 13 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.193: 12 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.193: 13 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.193: 13 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.193: 12 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.193: 12 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.194: 12 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.194: 12 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.194: 13 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.194: 13 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.194: 12 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.194: 27 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.194: 13 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.194: 14 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.194: 12 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.194: 12 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.194: 13 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.194: 12 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.194: 12 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.194: 12 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.194: 11 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.194: 84 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.194: 45 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.194: 14 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.194: 13 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.194: 12 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.194: 11 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.194: 11 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.194: 11 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.194: 68 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.194: 100 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.194: 12 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.194: 13 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.194: 13 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.194: 14 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.194: 12 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.194: 11 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.194: 12 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.194: 12 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.194: 12 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.194: 12 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.194: 12 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.194: 11 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.194: 10 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.194: 38 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.194: 12 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.194: 79 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.194: 12 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.194: 11 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.194: 10 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.194: 9 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.194: 68 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.194: 67 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.194: 66 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.194: 66 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.194: 11 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.194: 10 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.194: 11 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.194: 27 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.194: 11 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.194: 23 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.194: 21 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.194: 11 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.194: 36 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.194: 23 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.194: 98 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.194: 11 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.194: 25 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.194: 23 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.194: 34 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.194: 33 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.194: 29 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.194: 9 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.194: 11 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.194: 11 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.194: 10 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.194: 10 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.194: 9 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.194: 9 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.194: 12 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.194: 10 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.194: 10 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.194: 10 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.194: 9 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.194: 7 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.194: 12 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.194: 10 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.194: 9 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.194: 9 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.194: 50 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.194: 61 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.194: 83 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.194: 26 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.194: 24 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.194: 38 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.194: 9 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.194: 92 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.194: 69 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.194: 67 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.194: 66 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.194: 92 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.194: 90 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.194: 79 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.194: 73 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.194: 71 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.194: 70 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.194: 68 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.194: 67 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.194: 89 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.194: 87 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.194: 90 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.194: 88 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.194: 86 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.194: 37 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.194: 53 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.194: 75 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.194: 73 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.194: 76 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.194: 74 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.194: 42 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.194: 41 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.194: 39 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.194: 48 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.194: 64 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.194: 62 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.194: 83 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.194: 29 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.194: 27 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.194: 86 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.194: 52 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.195: 50 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.195: 71 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.195: 20 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.195: 76 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.195: 42 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.195: 40 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.195: 70 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.195: 7 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.195: 34 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.195: 32 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.195: 30 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.195: 7 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.195: 8 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.195: 6 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.195: 4 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.195: 51 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.195: 41 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.195: 11 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.195: 9 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.195: 7 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.195: 100 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.195: 100 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.195: 100 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.195: 98 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.195: 100 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.195: 92 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.195: 90 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.195: 95 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.195: 94 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.195: 92 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.195: 83 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.195: 81 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.195: 97 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.195: 100 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.195: 98 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.195: 96 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.195: 89 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.195: 87 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.195: 70 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.195: 97 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.195: 81 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.195: 98 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.195: 77 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.195: 55 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.195: 53 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.195: 51 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.195: 49 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.195: 47 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.195: 45 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.195: 43 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.195: 41 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.195: 38 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.195: 37 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.195: 35 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.195: 33 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.195: 31 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.195: 29 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.195: 26 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.195: 25 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.195: 23 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.195: 21 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.195: 19 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.195: 16 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.195: 15 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.195: 12 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.195: 11 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.195: 9 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.195: 7 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.195: 44 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.195: 12 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.195: 52 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.195: 19 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.195: 6 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.195: 98 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.195: 26 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.195: 24 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.195: 34 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.195: 26 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.195: 99 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.195: 41 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.195: 26 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.195: 13 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.195: 22 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.195: 20 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.195: 12 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.195: 71 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.195: 3 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.195: 70 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.195: 10 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.195: 77 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.195: 6 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.195: 85 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.195: 60 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.195: 58 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.195: 4 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.195: 51 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.195: 63 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.195: 69 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.196: 74 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.196: 51 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.196: 99 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.196: 61 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.196: 59 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.196: 93 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.196: 41 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.196: 34 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.196: 59 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.196: 55 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.196: 83 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.196: 81 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.196: 48 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.196: 77 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.196: 39 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.196: 93 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.196: 35 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.196: 17 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.196: 36 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.196: 85 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.196: 83 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.196: 86 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.196: 4 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.196: 77 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.196: 80 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.196: 17 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.196: 51 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.196: 74 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.196: 72 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.196: 45 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.196: 43 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.196: 66 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.196: 3 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.196: 37 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.196: 60 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.196: 53 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.196: 56 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.196: 54 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.196: 47 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.196: 50 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.196: 44 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.196: 41 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.196: 40 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.196: 42 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.196: 56 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.196: 33 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.196: 36 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.196: 58 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.196: 62 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.196: 30 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.196: 28 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.196: 26 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.196: 16 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.196: 17 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.196: 36 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.196: 18 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.196: 68 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.196: 14 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.196: 40 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.196: 10 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.196: 8 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.196: 6 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.196: 4 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.196: 93 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.196: 53 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.196: 51 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.196: 52 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.196: 47 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.196: 93 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.196: 46 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.196: 89 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.196: 52 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.196: 91 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.196: 73 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.196: 46 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.196: 69 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.196: 32 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.196: 40 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.196: 32 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.196: 26 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.196: 24 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.196: 32 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.196: 65 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.196: 69 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.196: 26 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.196: 11 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.196: 22 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.196: 55 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.196: 59 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.196: 16 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.196: 4 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.196: 2 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.196: 10 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.196: 18 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.196: 31 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.196: 86 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.196: 27 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.196: 25 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.196: 23 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.196: 31 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.196: 19 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.196: 87 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.196: 31 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.196: 23 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.196: 27 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.196: 9 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.196: 96 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.196: 15 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.196: 92 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.196: 1 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.196: 39 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.196: 7 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.196: 17 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.196: 50 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.196: 89 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.196: 99 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.196: 12 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.196: 92 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.196: 3 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.196: 39 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.196: 89 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.196: 75 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.196: 73 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.196: 30 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.196: 81 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.196: 27 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.196: 24 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.197: 75 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.197: 70 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.197: 59 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.197: 57 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.197: 55 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.197: 44 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.197: 68 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.197: 40 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.197: 100 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.197: 62 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.197: 96 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.197: 94 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.197: 56 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.197: 28 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.197: 91 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.197: 33 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.197: 22 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.197: 93 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.197: 44 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.197: 89 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.197: 76 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.197: 38 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.197: 19 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.197: 72 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.197: 6 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.197: 25 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.197: 66 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.197: 21 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.197: 19 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.197: 59 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.197: 3 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.197: 13 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.197: 55 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.197: 83 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.197: 49 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.197: 5 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.197: 3 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.197: 6 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.197: 4 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.197: 41 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.197: 38 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.197: 37 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.197: 98 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.197: 33 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.197: 81 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.197: 29 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.197: 88 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.197: 88 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.197: 22 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.197: 21 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.197: 89 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.197: 17 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.197: 13 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.197: 12 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.197: 11 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.197: 9 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.197: 41 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.197: 75 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.197: 3 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.197: 71 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.197: 80 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.197: 67 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.197: 76 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.197: 74 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.197: 52 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.197: 59 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.197: 79 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.197: 77 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.197: 23 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.197: 97 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.197: 40 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.197: 1 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.197: 45 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.197: 84 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.197: 5 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.197: 68 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.197: 83 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.197: 81 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.197: 74 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.197: 1 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.197: 75 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.197: 73 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.197: 66 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.197: 69 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.197: 67 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.197: 65 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.197: 17 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.197: 61 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.197: 59 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.197: 57 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.197: 9 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.197: 53 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.197: 51 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.197: 100 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.197: 1 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.197: 96 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.197: 95 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.197: 6 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.197: 34 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.197: 88 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.197: 86 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.197: 33 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.197: 31 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.197: 5 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.197: 27 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.197: 93 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.197: 23 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.197: 21 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.197: 14 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.197: 17 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.197: 15 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.197: 75 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.197: 81 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.197: 9 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.197: 77 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.197: 67 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.197: 73 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.197: 69 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.197: 50 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.197: 67 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.197: 65 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.197: 63 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.197: 84 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.197: 40 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.197: 95 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.197: 55 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.197: 53 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.197: 65 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.197: 84 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.197: 65 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.198: 45 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.198: 24 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.198: 41 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.198: 39 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.198: 58 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.198: 35 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.198: 31 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.198: 29 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.198: 11 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.198: 27 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.198: 63 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.198: 15 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.198: 21 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.198: 54 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.198: 17 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.198: 49 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.198: 13 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.198: 9 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.198: 9 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.198: 7 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.198: 5 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.198: 1 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.198: 36 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.198: 37 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.198: 5 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.198: 30 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.198: 28 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.198: 29 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.198: 3 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.198: 22 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.198: 8 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.198: 1 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.198: 4 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.198: 14 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.198: 7 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.198: 10 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.198: 7 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.198: 6 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.198: 4 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.198: 2 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.198: 6 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.198: 1 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.198: 2 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.198: 6 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.198: 4 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.198: 2 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.198: 1 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.199: offsets_filtered: 1739667255199583 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.199: 5 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.199: 6 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.199: 5 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.199: 6 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.199: 6 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.199: 7 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.199: 7 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.199: 8 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.199: 8 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.199: 9 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.199: 9 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.199: 13 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.199: 13 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.199: 13 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.199: 13 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.199: 13 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.199: 13 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.199: 11 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.199: 9 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.199: 11 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.199: 13 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.199: 15 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.199: 17 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.199: 18 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.199: 18 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.199: 18 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.199: 17 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.199: 17 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.199: 16 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.199: 15 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.199: 14 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.199: 13 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.199: 13 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.199: 13 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.199: 13 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.199: 13 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.199: 13 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.199: 14 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.199: 16 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.199: 18 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.199: 20 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.199: 20 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.199: 20 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.199: 20 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.199: 20 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.199: 18 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.199: 18 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.199: 16 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.199: 16 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.199: 14 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.199: 16 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.199: 18 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.199: 20 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.199: 22 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.199: 24 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.199: 26 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.199: 28 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.199: 28 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.199: 28 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.199: 28 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.199: 28 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.199: 28 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.199: 90 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.199: 92 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.199: 94 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.199: 96 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.199: 96 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.199: 96 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.199: 96 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.199: 96 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.199: 96 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.199: 96 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.199: 96 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.199: 96 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.199: 96 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.199: 96 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.199: 96 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.199: 96 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.199: 96 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.199: 96 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.199: 97 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.199: 97 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.199: 97 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.199: 97 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.199: 96 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.199: 96 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.199: 96 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.199: 96 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.199: 95 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.199: 94 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.199: 93 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.199: 92 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.199: 90 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.199: 88 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.199: 86 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.199: 84 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.199: 70 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.199: 68 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.199: 68 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.199: 68 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.199: 68 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.199: 68 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.199: 68 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.199: 68 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.199: 68 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.199: 68 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.199: 68 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.199: 68 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.199: 68 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.199: 97 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.199: 99 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.199: 99 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.199: 99 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.199: 99 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.199: 99 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.199: 99 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.199: 99 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.199: 99 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.199: 99 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.199: 99 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.199: 99 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.199: 99 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.199: 99 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.199: 99 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.199: 99 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.199: 99 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.199: 99 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.199: 99 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.199: 99 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.199: 99 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.199: 99 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.199: 99 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.199: 99 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.199: 98 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.199: 98 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.199: 98 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.199: 97 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.199: 97 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.199: 96 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.199: 96 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.199: 95 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.199: 95 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.199: 94 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.199: 94 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.199: 93 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.199: 93 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.199: 92 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.199: 91 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.199: 90 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.199: 89 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.199: 88 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.199: 87 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.199: 87 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 86 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 85 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 85 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 84 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 83 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 83 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 81 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 81 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 79 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 79 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 79 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 79 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 79 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 77 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 77 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 77 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 75 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 75 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 75 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 73 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 71 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 71 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 70 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 69 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 68 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 66 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 66 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 64 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 64 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 62 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 62 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 61 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 60 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 60 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 59 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 59 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 59 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 58 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 58 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 57 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 57 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 57 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 57 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 56 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 56 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 56 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 55 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 55 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 55 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 54 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 54 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 54 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 54 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 54 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 54 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 54 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 54 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 54 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 54 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 54 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 53 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 53 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 53 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 52 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 52 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 52 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 52 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 50 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 50 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 50 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 50 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 49 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 49 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 49 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 49 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 48 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 47 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 47 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 47 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 46 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 46 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 46 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 46 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 45 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 44 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 44 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 44 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 44 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 44 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 44 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 44 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 44 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 43 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 43 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 43 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 43 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 43 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 42 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 42 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 42 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 42 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 42 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 42 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 42 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 42 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 42 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 42 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 42 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 42 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 42 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 42 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 42 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 42 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 42 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 42 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 42 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 41 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 41 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 41 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 41 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 41 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 41 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 41 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 41 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 41 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 41 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 41 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 41 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 40 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 40 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 40 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 39 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 39 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 38 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 38 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 38 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 38 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 38 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 37 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 36 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 36 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 36 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 36 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 36 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 35 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 35 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 35 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 35 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 35 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 35 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 35 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 35 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 35 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 34 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 34 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 34 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 34 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 34 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 34 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 34 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 34 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 33 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 33 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 33 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 33 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 33 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 33 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 33 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 33 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 33 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 33 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 33 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 33 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 33 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 33 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 33 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 33 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 33 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 33 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 33 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 33 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 33 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 33 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 33 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 32 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 32 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 32 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 32 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 32 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 32 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 32 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 32 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 32 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 32 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 32 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 31 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 31 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 31 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 31 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 31 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 31 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 31 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 31 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 31 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 31 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 31 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 31 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 31 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 30 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 30 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 30 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 30 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 30 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 29 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 29 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 29 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 29 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 29 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 29 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 29 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 29 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 29 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 29 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 29 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 28 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 28 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 28 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 27 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 27 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 27 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 27 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 27 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 27 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 27 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 27 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 27 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 27 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 27 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 27 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 27 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 27 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 27 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 27 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 27 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 27 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 27 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 27 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 27 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 27 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 27 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 27 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 27 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 27 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 28 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 28 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 28 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 28 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 28 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 28 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 28 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 28 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 28 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 28 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 28 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 28 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 28 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 28 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 28 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 28 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 28 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 28 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 28 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 28 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 28 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 28 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 28 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 28 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 28 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 28 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 28 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 28 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 28 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 28 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 28 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 28 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 28 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 28 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 28 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 28 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 28 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 28 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 28 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 28 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 28 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 28 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 28 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 28 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 28 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 28 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 28 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 28 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 28 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 28 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 28 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 28 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 28 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 28 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 28 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 28 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 28 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 28 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 28 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 28 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 29 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 29 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 29 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 29 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 29 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 29 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 29 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 29 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 29 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 29 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 29 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 29 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 29 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 29 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 29 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 29 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 29 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 29 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 29 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 29 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 29 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 29 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 29 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 29 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 29 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 30 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 30 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 30 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 30 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 30 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 30 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 30 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 30 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 30 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 30 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 30 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 30 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 30 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 30 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 30 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 30 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 30 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.200: 30 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 30 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 30 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 30 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 30 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 30 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 30 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 30 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 30 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 30 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 30 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 30 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 31 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 31 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 31 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 31 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 31 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 31 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 30 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 31 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 31 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 31 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 31 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 31 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 31 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 31 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 31 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 31 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 31 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 31 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 31 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 31 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 30 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 30 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 30 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 30 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 30 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 30 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 30 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 30 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 30 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 30 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 30 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 30 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 30 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 30 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 30 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 30 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 30 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 31 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 31 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 31 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 31 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 31 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 31 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 31 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 31 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 31 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 31 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 31 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 31 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 30 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 30 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 30 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 30 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 30 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 30 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 30 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 30 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 30 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 30 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 30 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 30 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 30 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 30 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 30 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 30 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 30 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 30 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 30 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 30 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 30 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 30 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 30 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 30 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 30 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 30 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 31 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 30 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 30 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 30 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 30 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 30 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 30 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 30 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 30 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 30 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 29 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 29 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 29 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 30 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 30 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 30 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 30 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 30 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 30 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 30 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 30 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 30 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 30 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 30 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 30 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 30 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 30 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 30 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 30 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 30 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 30 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 30 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 30 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 30 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 30 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 30 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 30 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 30 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 30 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 30 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 30 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 30 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 30 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 30 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 29 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 29 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 29 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 29 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 29 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 29 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 29 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 29 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 29 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 29 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 29 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 29 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 29 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 29 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 29 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 29 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 29 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 29 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 29 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 29 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 29 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 29 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 29 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 29 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 29 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 29 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 29 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 29 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 29 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 29 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 29 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 29 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 29 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 29 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 29 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 29 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 29 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 29 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 29 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 29 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 29 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 29 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 29 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 29 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 29 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 29 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 28 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 28 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 28 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 28 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 28 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 28 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 28 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 28 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 28 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 28 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 28 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 28 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 28 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 28 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 28 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 27 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 27 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 27 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 27 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 26 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 26 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 26 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 26 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 26 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 26 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 26 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 26 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 26 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 26 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 26 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 26 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 26 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 25 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 25 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 25 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 25 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 25 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 25 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 25 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 25 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 25 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 25 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 25 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 25 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 25 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 25 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 25 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 25 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 25 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 25 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 24 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 24 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 24 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 24 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 24 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 24 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 24 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 24 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 24 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 24 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 24 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 24 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 24 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 24 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 24 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 24 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 24 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 24 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 24 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 23 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 23 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 23 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 23 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 23 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 23 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 23 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 23 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 23 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 23 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 23 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 23 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 23 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 23 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 23 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 23 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 23 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 23 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 23 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 22 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 22 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 23 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 22 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 22 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 22 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 22 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 22 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 22 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 22 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 22 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 22 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 22 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 22 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 22 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 22 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 22 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 22 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 22 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 22 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 22 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 22 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 22 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 22 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 22 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 22 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 22 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 22 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 22 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 22 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 22 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 22 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 22 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 21 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 21 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 21 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 21 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 21 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 21 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 21 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 21 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 21 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 21 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 21 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 21 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 21 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 21 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 21 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 21 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 21 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 21 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 21 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 21 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 21 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 21 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 21 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 21 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 21 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 20 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 20 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 20 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 20 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 20 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 20 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 20 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 20 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 20 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 20 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 20 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 20 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 20 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 19 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 19 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 19 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 19 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 19 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 19 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 19 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 19 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 19 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 19 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 19 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 19 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 19 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 19 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 19 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 19 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 19 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 18 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 18 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 18 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 18 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 18 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 18 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 18 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.201: 18 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 18 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 18 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 18 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 18 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 18 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 18 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 18 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 18 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 18 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 18 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 18 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 18 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 18 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 18 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 18 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 18 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 18 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 18 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 18 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 18 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 18 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 18 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 18 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 18 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 18 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 18 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 17 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 17 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 17 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 17 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 17 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 17 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 17 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 17 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 17 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 17 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 17 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 17 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 17 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 16 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 16 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 16 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 16 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 16 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 16 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 16 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 16 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 16 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 16 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 16 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 16 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 16 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 16 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 16 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 16 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 15 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 15 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 15 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 15 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 15 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 15 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 15 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 15 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 15 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 15 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 15 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 15 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 15 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 15 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 15 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 15 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 15 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 14 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 14 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 14 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 14 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 14 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 14 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 14 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 14 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 14 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 14 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 14 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 14 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 14 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 14 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 14 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 14 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 14 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 14 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 13 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 13 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 13 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 13 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 13 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 13 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 13 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 13 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 13 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 13 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 13 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 13 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 13 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 13 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 13 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 13 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 13 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 13 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 13 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 13 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 13 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 13 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 12 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 12 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 12 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 12 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 12 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 12 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 12 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 13 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 13 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 13 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 13 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 12 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 12 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 12 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 12 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 12 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 12 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 12 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 12 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 12 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 12 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 12 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 12 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 12 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 12 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 12 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 12 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 12 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 12 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 12 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 12 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 12 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 12 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 12 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 12 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 12 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 12 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 12 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 12 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 12 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 12 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 12 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 21 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 23 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 23 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 23 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 23 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 23 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 23 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 23 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 23 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 23 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 21 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 11 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 11 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 11 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 11 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 11 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 11 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 11 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 11 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 11 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 11 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 10 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 10 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 10 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 10 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 10 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 10 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 10 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 10 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 10 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 10 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 10 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 10 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 12 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 12 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 24 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 26 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 38 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 50 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 61 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 66 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 67 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 67 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 68 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 69 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 70 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 70 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 70 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 71 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 71 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 73 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 73 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 73 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 73 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 73 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 73 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 73 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 73 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 73 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 71 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 70 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 70 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 68 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 67 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 67 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 64 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 64 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 62 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 53 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 53 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 52 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 52 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 50 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 48 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 42 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 42 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 41 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 40 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 40 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 41 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 40 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 34 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 32 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 32 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 34 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 40 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 40 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 40 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 40 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 40 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 41 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 41 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 41 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 51 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 51 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 81 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 83 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 90 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 92 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 92 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 92 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 92 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 92 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 92 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 94 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 94 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 94 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 94 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 92 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 92 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 90 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 89 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 87 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 83 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 81 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 81 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 77 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 70 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 55 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 53 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 51 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 49 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 47 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 45 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 43 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 41 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 38 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 37 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 35 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 33 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 31 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 31 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 29 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 29 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 26 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 25 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 25 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 25 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 24 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 24 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 24 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 24 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 24 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 24 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 23 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 22 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 21 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 20 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 20 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 20 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 22 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 22 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 24 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 24 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 26 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 26 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 26 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 26 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 26 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 26 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 34 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 34 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 41 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 51 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 51 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 58 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 58 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 58 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 58 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 59 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 59 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 59 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 60 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 59 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 60 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 59 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 60 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 59 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 59 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 59 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 59 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 59 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 61 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 61 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 61 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 61 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 59 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 59 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 59 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 59 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 59 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 55 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 59 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 59 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 55 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 60 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 53 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 53 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 54 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 53 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 53 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 51 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.202: 51 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.203: 51 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.203: 51 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.203: 51 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.203: 50 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.203: 47 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.203: 50 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.203: 50 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.203: 47 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.203: 47 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.203: 45 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.203: 44 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.203: 43 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.203: 42 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.203: 41 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.203: 41 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.203: 41 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.203: 41 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.203: 40 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.203: 40 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.203: 36 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.203: 36 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.203: 36 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.203: 36 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.203: 36 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.203: 36 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.203: 36 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.203: 36 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.203: 36 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.203: 36 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.203: 40 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.203: 40 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.203: 40 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.203: 46 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.203: 46 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.203: 46 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.203: 46 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.203: 46 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.203: 46 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.203: 46 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.203: 46 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.203: 46 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.203: 47 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.203: 47 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.203: 47 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.203: 47 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.203: 51 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.203: 51 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.203: 47 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.203: 46 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.203: 46 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.203: 40 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.203: 32 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.203: 32 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.203: 32 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.203: 32 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.203: 31 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.203: 27 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.203: 27 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.203: 26 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.203: 26 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.203: 26 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.203: 26 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.203: 26 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.203: 26 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.203: 26 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.203: 25 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.203: 25 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.203: 23 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.203: 25 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.203: 25 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.203: 23 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.203: 23 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.203: 25 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.203: 27 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.203: 27 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.203: 27 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.203: 27 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.203: 27 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.203: 27 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.203: 31 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.203: 31 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.203: 31 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.203: 39 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.203: 39 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.203: 31 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.203: 39 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.203: 39 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.203: 50 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.203: 57 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.203: 55 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.203: 55 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.203: 55 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.203: 55 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.203: 57 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.203: 59 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.203: 62 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.203: 68 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.203: 62 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.203: 59 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.203: 62 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.203: 59 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.203: 59 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.203: 62 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.203: 59 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.203: 59 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.203: 59 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.203: 59 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.203: 57 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.203: 59 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.203: 59 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.203: 57 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.203: 57 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.203: 56 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.203: 55 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.203: 56 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.203: 56 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.203: 44 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.203: 55 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.203: 55 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.203: 49 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.203: 44 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.203: 38 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.203: 33 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.203: 33 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.203: 33 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.203: 38 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.203: 38 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.203: 38 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.203: 37 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.203: 37 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.203: 33 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.203: 33 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.203: 37 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.203: 33 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.203: 33 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.203: 37 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.203: 33 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.203: 33 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.203: 33 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.203: 29 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.203: 29 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.203: 33 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.203: 33 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.203: 29 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.203: 29 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.203: 33 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.203: 37 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.203: 38 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.203: 41 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.203: 41 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.203: 52 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.203: 59 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.203: 59 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.203: 59 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.203: 59 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.203: 59 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.203: 52 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.203: 45 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.203: 52 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.203: 52 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.203: 52 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.203: 59 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.203: 67 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.203: 68 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.203: 68 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.203: 71 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.203: 73 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.203: 71 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.203: 71 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.203: 69 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.203: 68 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.203: 68 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.203: 67 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.203: 66 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.203: 66 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.203: 66 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.203: 65 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.203: 61 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.203: 65 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.203: 61 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.203: 65 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.203: 66 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.203: 66 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.203: 65 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.203: 66 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.203: 66 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.203: 65 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.203: 61 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.203: 59 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.203: 59 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.203: 59 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.203: 57 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.203: 53 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.203: 51 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.203: 34 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.203: 33 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.203: 34 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.203: 34 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.203: 33 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.203: 33 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.203: 34 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.203: 34 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.203: 34 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.203: 34 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.203: 50 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.203: 50 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.203: 50 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.203: 63 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.203: 63 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.203: 63 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.203: 55 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.203: 55 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.203: 63 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.203: 65 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.203: 65 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.203: 65 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.203: 65 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.203: 65 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.203: 65 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.203: 65 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.203: 65 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.203: 63 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.203: 58 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.203: 58 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.203: 55 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.203: 55 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.203: 53 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.203: 50 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.203: 53 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.203: 45 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.203: 45 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.203: 41 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.203: 40 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.203: 39 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.203: 35 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.203: 31 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.203: 29 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.203: 29 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.203: 29 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.203: 27 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.203: 27 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.203: 28 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.204: 28 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.204: 27 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.204: 22 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.204: 21 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.204: 17 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.204: 15 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.204: 15 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.204: 14 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.204: 13 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.204: 10 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.204: 9 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.204: 9 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.204: 8 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.204: 7 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.204: 7 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.204: 7 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.204: 6 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.204: 6 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.204: 6 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.204: 6 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.204: 6 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.204: 6 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.204: 6 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.204: 6 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.204: 6 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.204: 6 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.204: 6 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.204: 6 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.204: 4 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.204: 6 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.204: 6 406s (process:2102): libfprint-assembling-DEBUG: 00:54:15.204: 1 406s (process:2102): libfprint-image_device-DEBUG: 00:54:15.206: Image device captured an image 406s (process:2102): libfprint-image_device-DEBUG: 00:54:15.207: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 406s (process:2102): libfprint-device-DEBUG: 00:54:15.207: Device reported finger status change: FP_FINGER_STATUS_PRESENT 406s (process:2102): libfprint-device-DEBUG: 00:54:15.207: Device reported finger status change: FP_FINGER_STATUS_NONE 406s (process:2102): libfprint-image_device-DEBUG: 00:54:15.207: Image device reported finger status: off 406s (process:2102): libfprint-image_device-DEBUG: 00:54:15.207: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 406s (process:2102): libfprint-image_device-DEBUG: 00:54:15.207: Deactivating image device 406s (process:2102): libfprint-image_device-DEBUG: 00:54:15.207: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_DEACTIVATING 406s (process:2102): libfprint-image-DEBUG: 00:54:15.246: Minutiae scan completed in 0.038972 secs 406s (process:2102): libfprint-device-DEBUG: 00:54:15.258: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 406s (process:2102): libfprint-SSM-DEBUG: 00:54:15.286: [vfs0050] SSM_STATES entering state 10 406s (process:2102): libfprint-SSM-DEBUG: 00:54:15.286: [vfs0050] SSM_STATES entering state 3 406s (process:2102): libfprint-SSM-DEBUG: 00:54:15.286: [vfs0050] SUBSM1_STATES entering state 0 406s (process:2102): libfprint-SSM-DEBUG: 00:54:15.286: [vfs0050] SUBSM1_STATES entering state 1 406s (process:2102): libfprint-SSM-DEBUG: 00:54:15.287: [vfs0050] SUBSM1_STATES entering state 2 406s (process:2102): libfprint-SSM-DEBUG: 00:54:15.287: [vfs0050] SUBSM1_STATES completed successfully 406s (process:2102): libfprint-SSM-DEBUG: 00:54:15.287: [vfs0050] SSM_STATES entering state 4 406s (process:2102): libfprint-SSM-DEBUG: 00:54:15.287: [vfs0050] SUBSM2_STATES entering state 0 406s (process:2102): libfprint-SSM-DEBUG: 00:54:15.288: [vfs0050] SUBSM2_STATES entering state 1 406s (process:2102): libfprint-SSM-DEBUG: 00:54:15.288: [vfs0050] SUBSM2_STATES entering state 2 406s (process:2102): libfprint-SSM-DEBUG: 00:54:15.289: [vfs0050] SUBSM2_STATES entering state 3 406s (process:2102): libfprint-SSM-DEBUG: 00:54:15.290: [vfs0050] SUBSM2_STATES entering state 4 406s (process:2102): libfprint-SSM-DEBUG: 00:54:15.290: [vfs0050] SUBSM2_STATES entering state 5 406s (process:2102): libfprint-SSM-DEBUG: 00:54:15.291: [vfs0050] SUBSM2_STATES entering state 6 406s (process:2102): libfprint-SSM-DEBUG: 00:54:15.291: [vfs0050] SUBSM1_STATES entering state 0 406s (process:2102): libfprint-SSM-DEBUG: 00:54:15.291: [vfs0050] SUBSM1_STATES entering state 1 406s (process:2102): libfprint-SSM-DEBUG: 00:54:15.292: [vfs0050] SUBSM1_STATES entering state 2 406s (process:2102): libfprint-SSM-DEBUG: 00:54:15.292: [vfs0050] SUBSM1_STATES completed successfully 406s (process:2102): libfprint-SSM-DEBUG: 00:54:15.292: [vfs0050] SUBSM2_STATES completed successfully 406s (process:2102): libfprint-SSM-DEBUG: 00:54:15.292: [vfs0050] SSM_STATES entering state 5 406s (process:2102): libfprint-SSM-DEBUG: 00:54:15.292: [vfs0050] SSM_STATES completed successfully 406s (process:2102): libfprint-image_device-DEBUG: 00:54:15.292: Image device deactivation completed 406s (process:2102): libfprint-image_device-DEBUG: 00:54:15.292: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE 406s (process:2102): libfprint-device-DEBUG: 00:54:15.292: Device reported capture completion 406s (process:2102): libfprint-device-DEBUG: 00:54:15.292: Completing action FPI_DEVICE_ACTION_CAPTURE in idle! 406s (process:2102): libfprint-device-DEBUG: 00:54:15.292: Updated temperature model after 0.03 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 406s (process:2102): libfprint-image_device-DEBUG: 00:54:15.293: Image device close completed 406s (process:2102): libfprint-device-DEBUG: 00:54:15.293: Device reported close completion 406s (process:2102): libfprint-device-DEBUG: 00:54:15.293: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 406s (process:2102): libfprint-device-DEBUG: 00:54:15.293: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 406s ** (umockdev-run:2098): DEBUG: 00:54:15.501: umockdev.vala:154: Removing test bed /tmp/umockdev.4N5K22 406s (umockdev-run:2098): GLib-DEBUG: 00:54:15.511: unsetenv() is not thread-safe and should not be used after threads are created 406s Comparing PNGs /tmp/libfprint-umockdev-test-rddztdtz/capture.png and /usr/share/installed-tests/libfprint-2/vfs0050/capture.png 406s PASS: libfprint-2/driver-vfs0050.test 406s Running test: libfprint-2/driver-egismoc-0587.test 406s ** (umockdev-run:2111): DEBUG: 00:54:15.623: umockdev.vala:127: Created udev test bed /tmp/umockdev.3IBB22 406s ** (umockdev-run:2111): DEBUG: 00:54:15.623: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0/usb3/3-5 406s ** (umockdev-run:2111): DEBUG: 00:54:15.627: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0/usb3/3-5 (subsystem usb) 406s ** (umockdev-run:2111): DEBUG: 00:54:15.633: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.3IBB22/dev/bus/usb/003/009 406s ** (umockdev-run:2111): DEBUG: 00:54:15.633: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0/usb3 406s ** (umockdev-run:2111): DEBUG: 00:54:15.635: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0/usb3 (subsystem usb) 406s ** (umockdev-run:2111): DEBUG: 00:54:15.640: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.3IBB22/dev/bus/usb/003/001 406s ** (umockdev-run:2111): DEBUG: 00:54:15.640: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0 406s ** (umockdev-run:2111): DEBUG: 00:54:15.640: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0 (subsystem pci) 406s (process:2115): libfprint-context-DEBUG: 00:54:15.750: Initializing FpContext (libfprint version 1.94.8+tod1) 406s (process:2115): libfprint-tod-DEBUG: 00:54:15.750: Impossible to load the shared drivers dir Error opening directory “/usr/lib/arm-linux-gnueabihf/libfprint-2/tod-1”: No such file or directory 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.753: 7399823813980: ../libfprint/drivers/egismoc/egismoc.c:1597 406s (process:2115): libfprint-context-DEBUG: 00:54:15.753: No driver found for USB device 1D6B:0002 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.753: egismoc_probe enter --> 406s (process:2115): libfprint-device-DEBUG: 00:54:15.755: Device reported probe completion 406s (process:2115): libfprint-device-DEBUG: 00:54:15.755: Completing action FPI_DEVICE_ACTION_PROBE in idle! 406s (process:2115): libfprint-device-DEBUG: 00:54:15.755: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.756: Opening device 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.757: [egismoc] DEV_INIT_STATES entering state 0 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.757: [egismoc] DEV_INIT_STATES entering state 1 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.758: [egismoc] DEV_INIT_STATES entering state 2 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.759: [egismoc] DEV_INIT_STATES entering state 3 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.759: [egismoc] DEV_INIT_STATES entering state 4 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.760: [egismoc] DEV_INIT_STATES entering state 5 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.760: Execute command and get response 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.760: Get check bytes 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.760: [egismoc] CMD_STATES entering state 0 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.760: [egismoc] CMD_STATES entering state 1 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.761: Command receive callback 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.761: [egismoc] CMD_STATES completed successfully 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.761: Firmware version callback 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.761: Response suffix valid: yes 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.761: Device firmware version is 9050.6.4.67 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.761: [egismoc] DEV_INIT_STATES completed successfully 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.761: Task SSM done 406s (process:2115): libfprint-device-DEBUG: 00:54:15.761: Device reported open completion 406s (process:2115): libfprint-device-DEBUG: 00:54:15.761: Completing action FPI_DEVICE_ACTION_OPEN in idle! 406s (process:2115): libfprint-device-DEBUG: 00:54:15.761: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.761: List 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.761: [egismoc] LIST_STATES entering state 0 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.761: Execute command and get response 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.761: Get check bytes 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.762: [egismoc] CMD_STATES entering state 0 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.762: [egismoc] CMD_STATES entering state 1 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.762: Command receive callback 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.762: [egismoc] CMD_STATES completed successfully 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.763: List callback 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.763: Device fingerprint 1: FP1-00000000-2-00000000-nobody 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.763: Number of currently enrolled fingerprints on the device is 1 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.763: [egismoc] LIST_STATES entering state 1 406s (process:2115): libfprint-device-DEBUG: 00:54:15.763: Device reported listing completion 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.763: [egismoc] LIST_STATES completed successfully 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.763: Task SSM done 406s (process:2115): libfprint-device-DEBUG: 00:54:15.763: Completing action FPI_DEVICE_ACTION_LIST in idle! 406s (process:2115): libfprint-device-DEBUG: 00:54:15.763: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.763: Clear storage 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.763: [egismoc] DELETE_STATES entering state 0 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.763: Execute command and get response 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.763: Get check bytes 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.763: [egismoc] CMD_STATES entering state 0 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.764: [egismoc] CMD_STATES entering state 1 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.764: Command receive callback 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.764: [egismoc] CMD_STATES completed successfully 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.764: List callback 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.764: Device fingerprint 1: FP1-00000000-2-00000000-nobody 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.764: Number of currently enrolled fingerprints on the device is 1 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.764: [egismoc] DELETE_STATES entering state 1 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.764: Get delete command 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.764: Execute command and get response 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.764: Get check bytes 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.764: [egismoc] CMD_STATES entering state 0 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.765: [egismoc] CMD_STATES entering state 1 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.765: Command receive callback 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.765: [egismoc] CMD_STATES completed successfully 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.765: Delete callback 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.765: Response prefix valid: yes 406s (process:2115): libfprint-device-DEBUG: 00:54:15.765: Device reported deletion completion 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.765: [egismoc] DELETE_STATES completed successfully 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.766: Task SSM done 406s (process:2115): libfprint-device-DEBUG: 00:54:15.766: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 406s (process:2115): libfprint-device-DEBUG: 00:54:15.766: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.766: List 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.766: [egismoc] LIST_STATES entering state 0 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.766: Execute command and get response 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.766: Get check bytes 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.766: [egismoc] CMD_STATES entering state 0 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.766: [egismoc] CMD_STATES entering state 1 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.767: Command receive callback 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.767: [egismoc] CMD_STATES completed successfully 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.767: List callback 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.767: Number of currently enrolled fingerprints on the device is 0 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.767: [egismoc] LIST_STATES entering state 1 406s (process:2115): libfprint-device-DEBUG: 00:54:15.767: Device reported listing completion 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.767: [egismoc] LIST_STATES completed successfully 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.767: Task SSM done 406s (process:2115): libfprint-device-DEBUG: 00:54:15.767: Completing action FPI_DEVICE_ACTION_LIST in idle! 406s (process:2115): libfprint-device-DEBUG: 00:54:15.767: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 406s (process:2115): libfprint-device-DEBUG: 00:54:15.768: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.768: Enroll 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.768: [egismoc] ENROLL_STATES entering state 0 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.768: Execute command and get response 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.768: Get check bytes 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.768: [egismoc] CMD_STATES entering state 0 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.769: [egismoc] CMD_STATES entering state 1 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.769: Command receive callback 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.769: [egismoc] CMD_STATES completed successfully 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.769: List callback 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.769: Number of currently enrolled fingerprints on the device is 0 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.769: [egismoc] ENROLL_STATES entering state 1 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.769: [egismoc] ENROLL_STATES entering state 2 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.769: Execute command and get response 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.769: Get check bytes 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.769: [egismoc] CMD_STATES entering state 0 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.770: [egismoc] CMD_STATES entering state 1 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.770: Command receive callback 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.770: [egismoc] CMD_STATES completed successfully 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.770: Task SSM next state callback 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.770: [egismoc] ENROLL_STATES entering state 3 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.770: Execute command and get response 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.770: Get check bytes 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.770: [egismoc] CMD_STATES entering state 0 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.771: [egismoc] CMD_STATES entering state 1 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.772: Command receive callback 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.772: [egismoc] CMD_STATES completed successfully 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.772: Task SSM next state callback 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.772: [egismoc] ENROLL_STATES entering state 4 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.772: Wait for finger on sensor 406s (process:2115): libfprint-device-DEBUG: 00:54:15.772: Device reported finger status change: FP_FINGER_STATUS_NEEDED 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.772: Finger on sensor callback 406s (process:2115): libfprint-device-DEBUG: 00:54:15.772: Device reported finger status change: FP_FINGER_STATUS_PRESENT 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.772: [egismoc] ENROLL_STATES entering state 5 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.772: Execute command and get response 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.772: Get check bytes 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.772: [egismoc] CMD_STATES entering state 0 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.773: [egismoc] CMD_STATES entering state 1 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.773: Command receive callback 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.773: [egismoc] CMD_STATES completed successfully 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.773: Task SSM next state callback 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.773: [egismoc] ENROLL_STATES entering state 6 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.773: Get check command 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.773: Execute command and get response 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.773: Get check bytes 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.773: [egismoc] CMD_STATES entering state 0 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.774: [egismoc] CMD_STATES entering state 1 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.774: Command receive callback 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.774: [egismoc] CMD_STATES completed successfully 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.774: Enroll check callback 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.774: Response suffix valid: yes 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.774: [egismoc] ENROLL_STATES entering state 7 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.774: Execute command and get response 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.774: Get check bytes 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.774: [egismoc] CMD_STATES entering state 0 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.775: [egismoc] CMD_STATES entering state 1 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.775: Command receive callback 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.775: [egismoc] CMD_STATES completed successfully 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.775: Task SSM next state callback 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.775: [egismoc] ENROLL_STATES entering state 8 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.775: Execute command and get response 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.775: Get check bytes 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.775: [egismoc] CMD_STATES entering state 0 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.776: [egismoc] CMD_STATES entering state 1 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.776: Command receive callback 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.776: [egismoc] CMD_STATES completed successfully 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.776: Task SSM next state callback 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.776: [egismoc] ENROLL_STATES entering state 9 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.776: Execute command and get response 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.776: Get check bytes 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.776: [egismoc] CMD_STATES entering state 0 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.777: [egismoc] CMD_STATES entering state 1 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.777: Command receive callback 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.777: [egismoc] CMD_STATES completed successfully 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.777: Task SSM next state callback 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.777: [egismoc] ENROLL_STATES entering state 10 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.777: Wait for finger on sensor 406s (process:2115): libfprint-device-DEBUG: 00:54:15.777: Device reported finger status change: FP_FINGER_STATUS_NEEDED 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.777: Finger on sensor callback 406s (process:2115): libfprint-device-DEBUG: 00:54:15.777: Device reported finger status change: FP_FINGER_STATUS_PRESENT 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.777: [egismoc] ENROLL_STATES entering state 11 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.777: Execute command and get response 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.777: Get check bytes 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.777: [egismoc] CMD_STATES entering state 0 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.778: [egismoc] CMD_STATES entering state 1 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.778: Command receive callback 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.778: [egismoc] CMD_STATES completed successfully 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.778: Read capture callback 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.778: Response prefix valid: yes 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.778: Response suffix valid: yes 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.778: Partial capture successful. Please touch the sensor again (1/20) 406s (process:2115): libfprint-device-DEBUG: 00:54:15.778: Device reported enroll progress, reported 1 of 20 have been completed 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.778: [egismoc] ENROLL_STATES entering state 8 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.778: Execute command and get response 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.778: Get check bytes 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.778: [egismoc] CMD_STATES entering state 0 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.779: [egismoc] CMD_STATES entering state 1 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.779: Command receive callback 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.779: [egismoc] CMD_STATES completed successfully 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.779: Task SSM next state callback 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.779: [egismoc] ENROLL_STATES entering state 9 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.779: Execute command and get response 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.779: Get check bytes 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.779: [egismoc] CMD_STATES entering state 0 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.780: [egismoc] CMD_STATES entering state 1 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.780: Command receive callback 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.780: [egismoc] CMD_STATES completed successfully 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.780: Task SSM next state callback 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.780: [egismoc] ENROLL_STATES entering state 10 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.780: Wait for finger on sensor 406s (process:2115): libfprint-device-DEBUG: 00:54:15.780: Device reported finger status change: FP_FINGER_STATUS_NEEDED 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.781: Finger on sensor callback 406s (process:2115): libfprint-device-DEBUG: 00:54:15.781: Device reported finger status change: FP_FINGER_STATUS_PRESENT 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.781: [egismoc] ENROLL_STATES entering state 11 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.781: Execute command and get response 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.781: Get check bytes 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.781: [egismoc] CMD_STATES entering state 0 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.781: [egismoc] CMD_STATES entering state 1 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.782: Command receive callback 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.782: [egismoc] CMD_STATES completed successfully 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.782: Read capture callback 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.782: Response prefix valid: yes 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.782: Response suffix valid: yes 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.782: Partial capture successful. Please touch the sensor again (2/20) 406s (process:2115): libfprint-device-DEBUG: 00:54:15.782: Device reported enroll progress, reported 2 of 20 have been completed 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.782: [egismoc] ENROLL_STATES entering state 8 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.782: Execute command and get response 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.782: Get check bytes 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.782: [egismoc] CMD_STATES entering state 0 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.782: [egismoc] CMD_STATES entering state 1 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.783: Command receive callback 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.783: [egismoc] CMD_STATES completed successfully 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.783: Task SSM next state callback 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.783: [egismoc] ENROLL_STATES entering state 9 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.783: Execute command and get response 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.783: Get check bytes 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.783: [egismoc] CMD_STATES entering state 0 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.783: [egismoc] CMD_STATES entering state 1 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.784: Command receive callback 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.784: [egismoc] CMD_STATES completed successfully 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.784: Task SSM next state callback 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.784: [egismoc] ENROLL_STATES entering state 10 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.784: Wait for finger on sensor 406s (process:2115): libfprint-device-DEBUG: 00:54:15.784: Device reported finger status change: FP_FINGER_STATUS_NEEDED 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.784: Finger on sensor callback 406s (process:2115): libfprint-device-DEBUG: 00:54:15.784: Device reported finger status change: FP_FINGER_STATUS_PRESENT 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.784: [egismoc] ENROLL_STATES entering state 11 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.784: Execute command and get response 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.784: Get check bytes 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.784: [egismoc] CMD_STATES entering state 0 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.785: [egismoc] CMD_STATES entering state 1 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.785: Command receive callback 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.785: [egismoc] CMD_STATES completed successfully 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.785: Read capture callback 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.785: Response prefix valid: yes 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.785: Response suffix valid: yes 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.785: Partial capture successful. Please touch the sensor again (3/20) 406s (process:2115): libfprint-device-DEBUG: 00:54:15.785: Device reported enroll progress, reported 3 of 20 have been completed 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.785: [egismoc] ENROLL_STATES entering state 8 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.785: Execute command and get response 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.785: Get check bytes 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.785: [egismoc] CMD_STATES entering state 0 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.786: [egismoc] CMD_STATES entering state 1 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.786: Command receive callback 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.786: [egismoc] CMD_STATES completed successfully 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.786: Task SSM next state callback 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.786: [egismoc] ENROLL_STATES entering state 9 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.786: Execute command and get response 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.786: Get check bytes 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.786: [egismoc] CMD_STATES entering state 0 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.787: [egismoc] CMD_STATES entering state 1 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.787: Command receive callback 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.787: [egismoc] CMD_STATES completed successfully 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.787: Task SSM next state callback 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.787: [egismoc] ENROLL_STATES entering state 10 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.787: Wait for finger on sensor 406s (process:2115): libfprint-device-DEBUG: 00:54:15.787: Device reported finger status change: FP_FINGER_STATUS_NEEDED 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.787: Finger on sensor callback 406s (process:2115): libfprint-device-DEBUG: 00:54:15.787: Device reported finger status change: FP_FINGER_STATUS_PRESENT 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.787: [egismoc] ENROLL_STATES entering state 11 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.787: Execute command and get response 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.787: Get check bytes 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.787: [egismoc] CMD_STATES entering state 0 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.788: [egismoc] CMD_STATES entering state 1 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.788: Command receive callback 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.788: [egismoc] CMD_STATES completed successfully 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.788: Read capture callback 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.788: Response prefix valid: yes 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.788: Response suffix valid: yes 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.788: Partial capture successful. Please touch the sensor again (4/20) 406s (process:2115): libfprint-device-DEBUG: 00:54:15.788: Device reported enroll progress, reported 4 of 20 have been completed 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.788: [egismoc] ENROLL_STATES entering state 8 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.788: Execute command and get response 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.788: Get check bytes 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.788: [egismoc] CMD_STATES entering state 0 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.789: [egismoc] CMD_STATES entering state 1 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.789: Command receive callback 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.789: [egismoc] CMD_STATES completed successfully 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.789: Task SSM next state callback 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.789: [egismoc] ENROLL_STATES entering state 9 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.789: Execute command and get response 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.789: Get check bytes 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.789: [egismoc] CMD_STATES entering state 0 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.790: [egismoc] CMD_STATES entering state 1 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.790: Command receive callback 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.790: [egismoc] CMD_STATES completed successfully 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.790: Task SSM next state callback 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.790: [egismoc] ENROLL_STATES entering state 10 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.790: Wait for finger on sensor 406s (process:2115): libfprint-device-DEBUG: 00:54:15.790: Device reported finger status change: FP_FINGER_STATUS_NEEDED 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.791: Finger on sensor callback 406s (process:2115): libfprint-device-DEBUG: 00:54:15.791: Device reported finger status change: FP_FINGER_STATUS_PRESENT 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.791: [egismoc] ENROLL_STATES entering state 11 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.791: Execute command and get response 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.791: Get check bytes 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.791: [egismoc] CMD_STATES entering state 0 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.791: [egismoc] CMD_STATES entering state 1 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.792: Command receive callback 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.792: [egismoc] CMD_STATES completed successfully 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.792: Read capture callback 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.792: Response prefix valid: yes 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.792: Response suffix valid: yes 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.792: Partial capture successful. Please touch the sensor again (5/20) 406s (process:2115): libfprint-device-DEBUG: 00:54:15.792: Device reported enroll progress, reported 5 of 20 have been completed 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.792: [egismoc] ENROLL_STATES entering state 8 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.792: Execute command and get response 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.792: Get check bytes 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.792: [egismoc] CMD_STATES entering state 0 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.792: [egismoc] CMD_STATES entering state 1 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.792: Command receive callback 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.792: [egismoc] CMD_STATES completed successfully 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.792: Task SSM next state callback 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.792: [egismoc] ENROLL_STATES entering state 9 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.792: Execute command and get response 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.792: Get check bytes 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.792: [egismoc] CMD_STATES entering state 0 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.793: [egismoc] CMD_STATES entering state 1 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.793: Command receive callback 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.793: [egismoc] CMD_STATES completed successfully 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.793: Task SSM next state callback 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.793: [egismoc] ENROLL_STATES entering state 10 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.793: Wait for finger on sensor 406s (process:2115): libfprint-device-DEBUG: 00:54:15.793: Device reported finger status change: FP_FINGER_STATUS_NEEDED 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.794: Finger on sensor callback 406s (process:2115): libfprint-device-DEBUG: 00:54:15.794: Device reported finger status change: FP_FINGER_STATUS_PRESENT 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.794: [egismoc] ENROLL_STATES entering state 11 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.794: Execute command and get response 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.794: Get check bytes 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.794: [egismoc] CMD_STATES entering state 0 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.794: [egismoc] CMD_STATES entering state 1 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.795: Command receive callback 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.795: [egismoc] CMD_STATES completed successfully 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.795: Read capture callback 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.795: Response prefix valid: yes 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.795: Response suffix valid: yes 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.795: Partial capture successful. Please touch the sensor again (6/20) 406s (process:2115): libfprint-device-DEBUG: 00:54:15.795: Device reported enroll progress, reported 6 of 20 have been completed 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.795: [egismoc] ENROLL_STATES entering state 8 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.795: Execute command and get response 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.795: Get check bytes 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.795: [egismoc] CMD_STATES entering state 0 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.795: [egismoc] CMD_STATES entering state 1 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.796: Command receive callback 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.796: [egismoc] CMD_STATES completed successfully 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.796: Task SSM next state callback 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.796: [egismoc] ENROLL_STATES entering state 9 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.796: Execute command and get response 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.796: Get check bytes 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.796: [egismoc] CMD_STATES entering state 0 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.796: [egismoc] CMD_STATES entering state 1 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.797: Command receive callback 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.797: [egismoc] CMD_STATES completed successfully 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.797: Task SSM next state callback 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.797: [egismoc] ENROLL_STATES entering state 10 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.797: Wait for finger on sensor 406s (process:2115): libfprint-device-DEBUG: 00:54:15.797: Device reported finger status change: FP_FINGER_STATUS_NEEDED 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.797: Finger on sensor callback 406s (process:2115): libfprint-device-DEBUG: 00:54:15.797: Device reported finger status change: FP_FINGER_STATUS_PRESENT 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.797: [egismoc] ENROLL_STATES entering state 11 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.797: Execute command and get response 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.797: Get check bytes 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.797: [egismoc] CMD_STATES entering state 0 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.797: [egismoc] CMD_STATES entering state 1 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.798: Command receive callback 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.798: [egismoc] CMD_STATES completed successfully 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.798: Read capture callback 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.798: Response prefix valid: yes 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.798: Response suffix valid: yes 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.798: Partial capture successful. Please touch the sensor again (7/20) 406s (process:2115): libfprint-device-DEBUG: 00:54:15.798: Device reported enroll progress, reported 7 of 20 have been completed 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.798: [egismoc] ENROLL_STATES entering state 8 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.798: Execute command and get response 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.798: Get check bytes 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.798: [egismoc] CMD_STATES entering state 0 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.798: [egismoc] CMD_STATES entering state 1 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.799: Command receive callback 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.799: [egismoc] CMD_STATES completed successfully 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.799: Task SSM next state callback 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.799: [egismoc] ENROLL_STATES entering state 9 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.799: Execute command and get response 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.799: Get check bytes 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.799: [egismoc] CMD_STATES entering state 0 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.799: [egismoc] CMD_STATES entering state 1 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.800: Command receive callback 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.800: [egismoc] CMD_STATES completed successfully 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.800: Task SSM next state callback 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.800: [egismoc] ENROLL_STATES entering state 10 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.800: Wait for finger on sensor 406s (process:2115): libfprint-device-DEBUG: 00:54:15.800: Device reported finger status change: FP_FINGER_STATUS_NEEDED 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.800: Finger on sensor callback 406s (process:2115): libfprint-device-DEBUG: 00:54:15.800: Device reported finger status change: FP_FINGER_STATUS_PRESENT 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.800: [egismoc] ENROLL_STATES entering state 11 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.800: Execute command and get response 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.800: Get check bytes 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.800: [egismoc] CMD_STATES entering state 0 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.801: [egismoc] CMD_STATES entering state 1 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.801: Command receive callback 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.801: [egismoc] CMD_STATES completed successfully 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.801: Read capture callback 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.801: Response prefix valid: yes 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.801: Response suffix valid: yes 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.801: Partial capture successful. Please touch the sensor again (8/20) 406s (process:2115): libfprint-device-DEBUG: 00:54:15.801: Device reported enroll progress, reported 8 of 20 have been completed 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.801: [egismoc] ENROLL_STATES entering state 8 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.801: Execute command and get response 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.801: Get check bytes 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.801: [egismoc] CMD_STATES entering state 0 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.802: [egismoc] CMD_STATES entering state 1 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.802: Command receive callback 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.802: [egismoc] CMD_STATES completed successfully 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.802: Task SSM next state callback 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.802: [egismoc] ENROLL_STATES entering state 9 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.802: Execute command and get response 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.802: Get check bytes 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.802: [egismoc] CMD_STATES entering state 0 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.803: [egismoc] CMD_STATES entering state 1 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.803: Command receive callback 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.803: [egismoc] CMD_STATES completed successfully 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.803: Task SSM next state callback 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.803: [egismoc] ENROLL_STATES entering state 10 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.803: Wait for finger on sensor 406s (process:2115): libfprint-device-DEBUG: 00:54:15.803: Device reported finger status change: FP_FINGER_STATUS_NEEDED 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.804: Finger on sensor callback 406s (process:2115): libfprint-device-DEBUG: 00:54:15.804: Device reported finger status change: FP_FINGER_STATUS_PRESENT 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.804: [egismoc] ENROLL_STATES entering state 11 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.804: Execute command and get response 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.804: Get check bytes 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.804: [egismoc] CMD_STATES entering state 0 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.804: [egismoc] CMD_STATES entering state 1 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.805: Command receive callback 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.805: [egismoc] CMD_STATES completed successfully 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.805: Read capture callback 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.805: Response prefix valid: yes 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.805: Response suffix valid: yes 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.805: Partial capture successful. Please touch the sensor again (9/20) 406s (process:2115): libfprint-device-DEBUG: 00:54:15.805: Device reported enroll progress, reported 9 of 20 have been completed 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.805: [egismoc] ENROLL_STATES entering state 8 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.805: Execute command and get response 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.805: Get check bytes 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.805: [egismoc] CMD_STATES entering state 0 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.805: [egismoc] CMD_STATES entering state 1 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.806: Command receive callback 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.806: [egismoc] CMD_STATES completed successfully 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.806: Task SSM next state callback 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.806: [egismoc] ENROLL_STATES entering state 9 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.806: Execute command and get response 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.806: Get check bytes 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.806: [egismoc] CMD_STATES entering state 0 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.806: [egismoc] CMD_STATES entering state 1 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.806: Command receive callback 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.806: [egismoc] CMD_STATES completed successfully 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.806: Task SSM next state callback 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.806: [egismoc] ENROLL_STATES entering state 10 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.806: Wait for finger on sensor 406s (process:2115): libfprint-device-DEBUG: 00:54:15.806: Device reported finger status change: FP_FINGER_STATUS_NEEDED 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.807: Finger on sensor callback 406s (process:2115): libfprint-device-DEBUG: 00:54:15.807: Device reported finger status change: FP_FINGER_STATUS_PRESENT 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.807: [egismoc] ENROLL_STATES entering state 11 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.807: Execute command and get response 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.807: Get check bytes 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.807: [egismoc] CMD_STATES entering state 0 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.807: [egismoc] CMD_STATES entering state 1 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.808: Command receive callback 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.808: [egismoc] CMD_STATES completed successfully 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.808: Read capture callback 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.808: Response prefix valid: yes 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.808: Response suffix valid: NO 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.808: Response prefix valid: yes 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.808: Response suffix valid: yes 406s (process:2115): libfprint-device-DEBUG: 00:54:15.808: Device reported enroll progress, reported 9 of 20 have been completed 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.808: [egismoc] ENROLL_STATES entering state 8 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.808: Execute command and get response 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.808: Get check bytes 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.808: [egismoc] CMD_STATES entering state 0 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.808: [egismoc] CMD_STATES entering state 1 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.809: Command receive callback 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.809: [egismoc] CMD_STATES completed successfully 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.809: Task SSM next state callback 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.809: [egismoc] ENROLL_STATES entering state 9 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.809: Execute command and get response 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.809: Get check bytes 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.809: [egismoc] CMD_STATES entering state 0 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.809: [egismoc] CMD_STATES entering state 1 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.810: Command receive callback 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.810: [egismoc] CMD_STATES completed successfully 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.810: Task SSM next state callback 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.810: [egismoc] ENROLL_STATES entering state 10 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.810: Wait for finger on sensor 406s (process:2115): libfprint-device-DEBUG: 00:54:15.810: Device reported finger status change: FP_FINGER_STATUS_NEEDED 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.810: Finger on sensor callback 406s (process:2115): libfprint-device-DEBUG: 00:54:15.810: Device reported finger status change: FP_FINGER_STATUS_PRESENT 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.810: [egismoc] ENROLL_STATES entering state 11 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.810: Execute command and get response 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.810: Get check bytes 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.810: [egismoc] CMD_STATES entering state 0 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.811: [egismoc] CMD_STATES entering state 1 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.811: Command receive callback 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.811: [egismoc] CMD_STATES completed successfully 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.811: Read capture callback 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.811: Response prefix valid: yes 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.811: Response suffix valid: yes 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.811: Partial capture successful. Please touch the sensor again (10/20) 406s (process:2115): libfprint-device-DEBUG: 00:54:15.811: Device reported enroll progress, reported 10 of 20 have been completed 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.811: [egismoc] ENROLL_STATES entering state 8 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.811: Execute command and get response 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.811: Get check bytes 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.811: [egismoc] CMD_STATES entering state 0 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.812: [egismoc] CMD_STATES entering state 1 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.812: Command receive callback 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.812: [egismoc] CMD_STATES completed successfully 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.812: Task SSM next state callback 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.812: [egismoc] ENROLL_STATES entering state 9 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.812: Execute command and get response 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.812: Get check bytes 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.812: [egismoc] CMD_STATES entering state 0 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.812: [egismoc] CMD_STATES entering state 1 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.813: Command receive callback 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.813: [egismoc] CMD_STATES completed successfully 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.813: Task SSM next state callback 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.813: [egismoc] ENROLL_STATES entering state 10 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.813: Wait for finger on sensor 406s (process:2115): libfprint-device-DEBUG: 00:54:15.813: Device reported finger status change: FP_FINGER_STATUS_NEEDED 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.813: Finger on sensor callback 406s (process:2115): libfprint-device-DEBUG: 00:54:15.813: Device reported finger status change: FP_FINGER_STATUS_PRESENT 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.813: [egismoc] ENROLL_STATES entering state 11 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.813: Execute command and get response 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.813: Get check bytes 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.814: [egismoc] CMD_STATES entering state 0 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.814: [egismoc] CMD_STATES entering state 1 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.814: Command receive callback 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.814: [egismoc] CMD_STATES completed successfully 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.814: Read capture callback 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.814: Response prefix valid: yes 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.814: Response suffix valid: NO 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.814: Response prefix valid: yes 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.814: Response suffix valid: yes 406s (process:2115): libfprint-device-DEBUG: 00:54:15.814: Device reported enroll progress, reported 10 of 20 have been completed 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.814: [egismoc] ENROLL_STATES entering state 8 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.815: Execute command and get response 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.815: Get check bytes 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.815: [egismoc] CMD_STATES entering state 0 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.815: [egismoc] CMD_STATES entering state 1 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.815: Command receive callback 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.815: [egismoc] CMD_STATES completed successfully 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.815: Task SSM next state callback 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.815: [egismoc] ENROLL_STATES entering state 9 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.815: Execute command and get response 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.815: Get check bytes 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.815: [egismoc] CMD_STATES entering state 0 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.816: [egismoc] CMD_STATES entering state 1 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.816: Command receive callback 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.816: [egismoc] CMD_STATES completed successfully 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.816: Task SSM next state callback 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.816: [egismoc] ENROLL_STATES entering state 10 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.816: Wait for finger on sensor 406s (process:2115): libfprint-device-DEBUG: 00:54:15.816: Device reported finger status change: FP_FINGER_STATUS_NEEDED 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.817: Finger on sensor callback 406s (process:2115): libfprint-device-DEBUG: 00:54:15.817: Device reported finger status change: FP_FINGER_STATUS_PRESENT 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.817: [egismoc] ENROLL_STATES entering state 11 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.817: Execute command and get response 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.817: Get check bytes 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.817: [egismoc] CMD_STATES entering state 0 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.817: [egismoc] CMD_STATES entering state 1 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.818: Command receive callback 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.818: [egismoc] CMD_STATES completed successfully 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.818: Read capture callback 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.818: Response prefix valid: yes 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.818: Response suffix valid: yes 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.818: Partial capture successful. Please touch the sensor again (11/20) 406s (process:2115): libfprint-device-DEBUG: 00:54:15.818: Device reported enroll progress, reported 11 of 20 have been completed 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.818: [egismoc] ENROLL_STATES entering state 8 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.818: Execute command and get response 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.818: Get check bytes 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.818: [egismoc] CMD_STATES entering state 0 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.818: [egismoc] CMD_STATES entering state 1 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.819: Command receive callback 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.819: [egismoc] CMD_STATES completed successfully 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.819: Task SSM next state callback 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.819: [egismoc] ENROLL_STATES entering state 9 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.819: Execute command and get response 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.819: Get check bytes 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.819: [egismoc] CMD_STATES entering state 0 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.819: [egismoc] CMD_STATES entering state 1 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.820: Command receive callback 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.820: [egismoc] CMD_STATES completed successfully 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.820: Task SSM next state callback 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.820: [egismoc] ENROLL_STATES entering state 10 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.820: Wait for finger on sensor 406s (process:2115): libfprint-device-DEBUG: 00:54:15.820: Device reported finger status change: FP_FINGER_STATUS_NEEDED 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.820: Finger on sensor callback 406s (process:2115): libfprint-device-DEBUG: 00:54:15.820: Device reported finger status change: FP_FINGER_STATUS_PRESENT 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.820: [egismoc] ENROLL_STATES entering state 11 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.820: Execute command and get response 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.820: Get check bytes 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.820: [egismoc] CMD_STATES entering state 0 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.820: [egismoc] CMD_STATES entering state 1 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.821: Command receive callback 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.821: [egismoc] CMD_STATES completed successfully 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.821: Read capture callback 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.821: Response prefix valid: yes 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.821: Response suffix valid: yes 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.821: Partial capture successful. Please touch the sensor again (12/20) 406s (process:2115): libfprint-device-DEBUG: 00:54:15.821: Device reported enroll progress, reported 12 of 20 have been completed 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.821: [egismoc] ENROLL_STATES entering state 8 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.821: Execute command and get response 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.821: Get check bytes 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.821: [egismoc] CMD_STATES entering state 0 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.821: [egismoc] CMD_STATES entering state 1 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.822: Command receive callback 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.822: [egismoc] CMD_STATES completed successfully 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.822: Task SSM next state callback 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.822: [egismoc] ENROLL_STATES entering state 9 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.822: Execute command and get response 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.822: Get check bytes 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.822: [egismoc] CMD_STATES entering state 0 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.822: [egismoc] CMD_STATES entering state 1 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.823: Command receive callback 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.823: [egismoc] CMD_STATES completed successfully 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.823: Task SSM next state callback 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.823: [egismoc] ENROLL_STATES entering state 10 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.823: Wait for finger on sensor 406s (process:2115): libfprint-device-DEBUG: 00:54:15.823: Device reported finger status change: FP_FINGER_STATUS_NEEDED 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.823: Finger on sensor callback 406s (process:2115): libfprint-device-DEBUG: 00:54:15.823: Device reported finger status change: FP_FINGER_STATUS_PRESENT 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.823: [egismoc] ENROLL_STATES entering state 11 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.823: Execute command and get response 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.823: Get check bytes 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.823: [egismoc] CMD_STATES entering state 0 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.823: [egismoc] CMD_STATES entering state 1 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.824: Command receive callback 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.824: [egismoc] CMD_STATES completed successfully 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.824: Read capture callback 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.824: Response prefix valid: yes 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.824: Response suffix valid: yes 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.824: Partial capture successful. Please touch the sensor again (13/20) 406s (process:2115): libfprint-device-DEBUG: 00:54:15.824: Device reported enroll progress, reported 13 of 20 have been completed 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.824: [egismoc] ENROLL_STATES entering state 8 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.824: Execute command and get response 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.824: Get check bytes 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.824: [egismoc] CMD_STATES entering state 0 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.824: [egismoc] CMD_STATES entering state 1 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.825: Command receive callback 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.825: [egismoc] CMD_STATES completed successfully 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.825: Task SSM next state callback 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.825: [egismoc] ENROLL_STATES entering state 9 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.825: Execute command and get response 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.825: Get check bytes 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.825: [egismoc] CMD_STATES entering state 0 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.825: [egismoc] CMD_STATES entering state 1 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.826: Command receive callback 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.826: [egismoc] CMD_STATES completed successfully 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.826: Task SSM next state callback 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.826: [egismoc] ENROLL_STATES entering state 10 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.826: Wait for finger on sensor 406s (process:2115): libfprint-device-DEBUG: 00:54:15.826: Device reported finger status change: FP_FINGER_STATUS_NEEDED 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.826: Finger on sensor callback 406s (process:2115): libfprint-device-DEBUG: 00:54:15.826: Device reported finger status change: FP_FINGER_STATUS_PRESENT 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.826: [egismoc] ENROLL_STATES entering state 11 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.826: Execute command and get response 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.826: Get check bytes 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.826: [egismoc] CMD_STATES entering state 0 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.827: [egismoc] CMD_STATES entering state 1 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.827: Command receive callback 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.827: [egismoc] CMD_STATES completed successfully 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.827: Read capture callback 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.827: Response prefix valid: yes 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.827: Response suffix valid: yes 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.827: Partial capture successful. Please touch the sensor again (14/20) 406s (process:2115): libfprint-device-DEBUG: 00:54:15.827: Device reported enroll progress, reported 14 of 20 have been completed 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.827: [egismoc] ENROLL_STATES entering state 8 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.827: Execute command and get response 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.827: Get check bytes 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.827: [egismoc] CMD_STATES entering state 0 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.828: [egismoc] CMD_STATES entering state 1 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.828: Command receive callback 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.828: [egismoc] CMD_STATES completed successfully 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.828: Task SSM next state callback 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.828: [egismoc] ENROLL_STATES entering state 9 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.828: Execute command and get response 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.828: Get check bytes 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.828: [egismoc] CMD_STATES entering state 0 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.829: [egismoc] CMD_STATES entering state 1 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.829: Command receive callback 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.829: [egismoc] CMD_STATES completed successfully 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.829: Task SSM next state callback 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.829: [egismoc] ENROLL_STATES entering state 10 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.829: Wait for finger on sensor 406s (process:2115): libfprint-device-DEBUG: 00:54:15.829: Device reported finger status change: FP_FINGER_STATUS_NEEDED 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.830: Finger on sensor callback 406s (process:2115): libfprint-device-DEBUG: 00:54:15.830: Device reported finger status change: FP_FINGER_STATUS_PRESENT 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.830: [egismoc] ENROLL_STATES entering state 11 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.830: Execute command and get response 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.830: Get check bytes 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.830: [egismoc] CMD_STATES entering state 0 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.830: [egismoc] CMD_STATES entering state 1 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.831: Command receive callback 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.831: [egismoc] CMD_STATES completed successfully 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.831: Read capture callback 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.831: Response prefix valid: yes 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.831: Response suffix valid: yes 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.831: Partial capture successful. Please touch the sensor again (15/20) 406s (process:2115): libfprint-device-DEBUG: 00:54:15.831: Device reported enroll progress, reported 15 of 20 have been completed 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.831: [egismoc] ENROLL_STATES entering state 8 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.831: Execute command and get response 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.831: Get check bytes 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.831: [egismoc] CMD_STATES entering state 0 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.831: [egismoc] CMD_STATES entering state 1 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.832: Command receive callback 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.832: [egismoc] CMD_STATES completed successfully 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.832: Task SSM next state callback 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.832: [egismoc] ENROLL_STATES entering state 9 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.832: Execute command and get response 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.832: Get check bytes 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.832: [egismoc] CMD_STATES entering state 0 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.832: [egismoc] CMD_STATES entering state 1 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.832: Command receive callback 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.832: [egismoc] CMD_STATES completed successfully 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.833: Task SSM next state callback 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.833: [egismoc] ENROLL_STATES entering state 10 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.833: Wait for finger on sensor 406s (process:2115): libfprint-device-DEBUG: 00:54:15.833: Device reported finger status change: FP_FINGER_STATUS_NEEDED 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.833: Finger on sensor callback 406s (process:2115): libfprint-device-DEBUG: 00:54:15.833: Device reported finger status change: FP_FINGER_STATUS_PRESENT 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.833: [egismoc] ENROLL_STATES entering state 11 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.833: Execute command and get response 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.833: Get check bytes 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.833: [egismoc] CMD_STATES entering state 0 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.833: [egismoc] CMD_STATES entering state 1 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.834: Command receive callback 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.834: [egismoc] CMD_STATES completed successfully 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.834: Read capture callback 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.834: Response prefix valid: yes 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.834: Response suffix valid: yes 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.834: Partial capture successful. Please touch the sensor again (16/20) 406s (process:2115): libfprint-device-DEBUG: 00:54:15.834: Device reported enroll progress, reported 16 of 20 have been completed 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.834: [egismoc] ENROLL_STATES entering state 8 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.834: Execute command and get response 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.834: Get check bytes 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.834: [egismoc] CMD_STATES entering state 0 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.834: [egismoc] CMD_STATES entering state 1 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.835: Command receive callback 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.835: [egismoc] CMD_STATES completed successfully 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.835: Task SSM next state callback 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.835: [egismoc] ENROLL_STATES entering state 9 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.835: Execute command and get response 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.835: Get check bytes 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.835: [egismoc] CMD_STATES entering state 0 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.835: [egismoc] CMD_STATES entering state 1 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.836: Command receive callback 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.836: [egismoc] CMD_STATES completed successfully 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.836: Task SSM next state callback 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.836: [egismoc] ENROLL_STATES entering state 10 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.836: Wait for finger on sensor 406s (process:2115): libfprint-device-DEBUG: 00:54:15.836: Device reported finger status change: FP_FINGER_STATUS_NEEDED 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.836: Finger on sensor callback 406s (process:2115): libfprint-device-DEBUG: 00:54:15.836: Device reported finger status change: FP_FINGER_STATUS_PRESENT 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.836: [egismoc] ENROLL_STATES entering state 11 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.836: Execute command and get response 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.836: Get check bytes 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.836: [egismoc] CMD_STATES entering state 0 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.837: [egismoc] CMD_STATES entering state 1 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.838: Command receive callback 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.838: [egismoc] CMD_STATES completed successfully 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.838: Read capture callback 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.838: Response prefix valid: yes 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.838: Response suffix valid: yes 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.838: Partial capture successful. Please touch the sensor again (17/20) 406s (process:2115): libfprint-device-DEBUG: 00:54:15.838: Device reported enroll progress, reported 17 of 20 have been completed 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.838: [egismoc] ENROLL_STATES entering state 8 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.838: Execute command and get response 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.838: Get check bytes 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.838: [egismoc] CMD_STATES entering state 0 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.838: [egismoc] CMD_STATES entering state 1 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.839: Command receive callback 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.839: [egismoc] CMD_STATES completed successfully 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.839: Task SSM next state callback 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.839: [egismoc] ENROLL_STATES entering state 9 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.839: Execute command and get response 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.839: Get check bytes 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.839: [egismoc] CMD_STATES entering state 0 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.840: [egismoc] CMD_STATES entering state 1 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.840: Command receive callback 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.840: [egismoc] CMD_STATES completed successfully 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.840: Task SSM next state callback 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.840: [egismoc] ENROLL_STATES entering state 10 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.840: Wait for finger on sensor 406s (process:2115): libfprint-device-DEBUG: 00:54:15.840: Device reported finger status change: FP_FINGER_STATUS_NEEDED 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.840: Finger on sensor callback 406s (process:2115): libfprint-device-DEBUG: 00:54:15.841: Device reported finger status change: FP_FINGER_STATUS_PRESENT 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.841: [egismoc] ENROLL_STATES entering state 11 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.841: Execute command and get response 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.841: Get check bytes 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.841: [egismoc] CMD_STATES entering state 0 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.841: [egismoc] CMD_STATES entering state 1 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.842: Command receive callback 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.842: [egismoc] CMD_STATES completed successfully 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.842: Read capture callback 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.842: Response prefix valid: yes 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.842: Response suffix valid: yes 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.842: Partial capture successful. Please touch the sensor again (18/20) 406s (process:2115): libfprint-device-DEBUG: 00:54:15.842: Device reported enroll progress, reported 18 of 20 have been completed 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.842: [egismoc] ENROLL_STATES entering state 8 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.842: Execute command and get response 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.842: Get check bytes 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.842: [egismoc] CMD_STATES entering state 0 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.842: [egismoc] CMD_STATES entering state 1 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.843: Command receive callback 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.843: [egismoc] CMD_STATES completed successfully 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.843: Task SSM next state callback 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.843: [egismoc] ENROLL_STATES entering state 9 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.843: Execute command and get response 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.843: Get check bytes 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.843: [egismoc] CMD_STATES entering state 0 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.843: [egismoc] CMD_STATES entering state 1 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.844: Command receive callback 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.844: [egismoc] CMD_STATES completed successfully 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.844: Task SSM next state callback 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.844: [egismoc] ENROLL_STATES entering state 10 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.844: Wait for finger on sensor 406s (process:2115): libfprint-device-DEBUG: 00:54:15.844: Device reported finger status change: FP_FINGER_STATUS_NEEDED 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.844: Finger on sensor callback 406s (process:2115): libfprint-device-DEBUG: 00:54:15.844: Device reported finger status change: FP_FINGER_STATUS_PRESENT 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.844: [egismoc] ENROLL_STATES entering state 11 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.844: Execute command and get response 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.844: Get check bytes 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.844: [egismoc] CMD_STATES entering state 0 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.844: [egismoc] CMD_STATES entering state 1 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.845: Command receive callback 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.845: [egismoc] CMD_STATES completed successfully 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.845: Read capture callback 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.845: Response prefix valid: yes 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.845: Response suffix valid: yes 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.845: Partial capture successful. Please touch the sensor again (19/20) 406s (process:2115): libfprint-device-DEBUG: 00:54:15.845: Device reported enroll progress, reported 19 of 20 have been completed 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.845: [egismoc] ENROLL_STATES entering state 8 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.845: Execute command and get response 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.845: Get check bytes 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.845: [egismoc] CMD_STATES entering state 0 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.845: [egismoc] CMD_STATES entering state 1 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.846: Command receive callback 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.846: [egismoc] CMD_STATES completed successfully 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.846: Task SSM next state callback 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.846: [egismoc] ENROLL_STATES entering state 9 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.846: Execute command and get response 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.846: Get check bytes 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.846: [egismoc] CMD_STATES entering state 0 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.846: [egismoc] CMD_STATES entering state 1 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.847: Command receive callback 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.847: [egismoc] CMD_STATES completed successfully 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.847: Task SSM next state callback 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.847: [egismoc] ENROLL_STATES entering state 10 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.847: Wait for finger on sensor 406s (process:2115): libfprint-device-DEBUG: 00:54:15.847: Device reported finger status change: FP_FINGER_STATUS_NEEDED 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.847: Finger on sensor callback 406s (process:2115): libfprint-device-DEBUG: 00:54:15.847: Device reported finger status change: FP_FINGER_STATUS_PRESENT 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.847: [egismoc] ENROLL_STATES entering state 11 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.847: Execute command and get response 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.847: Get check bytes 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.847: [egismoc] CMD_STATES entering state 0 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.847: [egismoc] CMD_STATES entering state 1 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.848: Command receive callback 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.848: [egismoc] CMD_STATES completed successfully 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.848: Read capture callback 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.848: Response prefix valid: yes 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.848: Response suffix valid: yes 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.848: Partial capture successful. Please touch the sensor again (20/20) 406s (process:2115): libfprint-device-DEBUG: 00:54:15.848: Device reported enroll progress, reported 20 of 20 have been completed 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.848: [egismoc] ENROLL_STATES entering state 12 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.848: Execute command and get response 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.848: Get check bytes 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.848: [egismoc] CMD_STATES entering state 0 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.848: [egismoc] CMD_STATES entering state 1 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.849: Command receive callback 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.849: [egismoc] CMD_STATES completed successfully 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.849: Task SSM next state callback 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.849: [egismoc] ENROLL_STATES entering state 13 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.849: New fingerprint ID: FP1-00000000-2-00000000-nobody 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.849: Execute command and get response 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.849: Get check bytes 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.849: [egismoc] CMD_STATES entering state 0 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.850: [egismoc] CMD_STATES entering state 1 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.850: Command receive callback 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.850: [egismoc] CMD_STATES completed successfully 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.850: Task SSM next state callback 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.850: [egismoc] ENROLL_STATES entering state 14 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.850: Execute command and get response 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.850: Get check bytes 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.850: [egismoc] CMD_STATES entering state 0 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.850: [egismoc] CMD_STATES entering state 1 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.851: Command receive callback 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.851: [egismoc] CMD_STATES completed successfully 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.851: Task SSM next state callback 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.851: [egismoc] ENROLL_STATES entering state 15 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.851: Enrollment was successful! 406s (process:2115): libfprint-device-DEBUG: 00:54:15.851: Device reported enroll completion 406s (process:2115): libfprint-device-DEBUG: 00:54:15.851: Device reported finger status change: FP_FINGER_STATUS_NONE 406s (process:2115): libfprint-device-DEBUG: 00:54:15.851: Print for finger FP_FINGER_LEFT_INDEX enrolled 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.851: [egismoc] ENROLL_STATES completed successfully 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.851: Task SSM done 406s (process:2115): libfprint-device-DEBUG: 00:54:15.851: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 406s (process:2115): libfprint-device-DEBUG: 00:54:15.851: Updated temperature model after 0.08 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.851: List 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.851: [egismoc] LIST_STATES entering state 0 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.851: Execute command and get response 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.851: Get check bytes 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.851: [egismoc] CMD_STATES entering state 0 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.851: [egismoc] CMD_STATES entering state 1 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.852: Command receive callback 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.852: [egismoc] CMD_STATES completed successfully 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.852: List callback 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.852: Device fingerprint 1: FP1-00000000-2-00000000-nobody 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.852: Number of currently enrolled fingerprints on the device is 1 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.852: [egismoc] LIST_STATES entering state 1 406s (process:2115): libfprint-device-DEBUG: 00:54:15.852: Device reported listing completion 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.852: [egismoc] LIST_STATES completed successfully 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.852: Task SSM done 406s (process:2115): libfprint-device-DEBUG: 00:54:15.852: Completing action FPI_DEVICE_ACTION_LIST in idle! 406s (process:2115): libfprint-device-DEBUG: 00:54:15.852: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 406s (process:2115): libfprint-device-DEBUG: 00:54:15.852: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.852: Identify or Verify 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.852: [egismoc] IDENTIFY_STATES entering state 0 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.852: Execute command and get response 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.852: Get check bytes 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.852: [egismoc] CMD_STATES entering state 0 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.853: [egismoc] CMD_STATES entering state 1 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.853: Command receive callback 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.853: [egismoc] CMD_STATES completed successfully 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.853: List callback 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.853: Device fingerprint 1: FP1-00000000-2-00000000-nobody 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.853: Number of currently enrolled fingerprints on the device is 1 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.853: [egismoc] IDENTIFY_STATES entering state 1 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.853: [egismoc] IDENTIFY_STATES entering state 2 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.853: Execute command and get response 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.853: Get check bytes 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.853: [egismoc] CMD_STATES entering state 0 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.853: [egismoc] CMD_STATES entering state 1 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.854: Command receive callback 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.854: [egismoc] CMD_STATES completed successfully 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.854: Task SSM next state callback 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.854: [egismoc] IDENTIFY_STATES entering state 3 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.854: Execute command and get response 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.854: Get check bytes 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.854: [egismoc] CMD_STATES entering state 0 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.854: [egismoc] CMD_STATES entering state 1 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.855: Command receive callback 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.855: [egismoc] CMD_STATES completed successfully 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.855: Task SSM next state callback 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.855: [egismoc] IDENTIFY_STATES entering state 4 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.855: Wait for finger on sensor 406s (process:2115): libfprint-device-DEBUG: 00:54:15.855: Device reported finger status change: FP_FINGER_STATUS_NEEDED 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.855: Finger on sensor callback 406s (process:2115): libfprint-device-DEBUG: 00:54:15.855: Device reported finger status change: FP_FINGER_STATUS_PRESENT 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.855: [egismoc] IDENTIFY_STATES entering state 5 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.855: Execute command and get response 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.855: Get check bytes 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.855: [egismoc] CMD_STATES entering state 0 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.856: [egismoc] CMD_STATES entering state 1 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.856: Command receive callback 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.856: [egismoc] CMD_STATES completed successfully 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.856: Task SSM next state callback 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.856: [egismoc] IDENTIFY_STATES entering state 6 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.856: Get check command 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.856: Execute command and get response 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.856: Get check bytes 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.856: [egismoc] CMD_STATES entering state 0 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.856: [egismoc] CMD_STATES entering state 1 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.857: Command receive callback 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.857: [egismoc] CMD_STATES completed successfully 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.857: Identify check callback 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.857: Response suffix valid: yes 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.857: Identify successful for: FP1-00000000-2-00000000-nobody 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.857: Verifying against: FP1-00000000-2-00000000-nobody 406s (process:2115): libfprint-device-DEBUG: 00:54:15.857: Device reported verify result 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.857: [egismoc] IDENTIFY_STATES entering state 7 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.857: Execute command and get response 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.857: Get check bytes 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.857: [egismoc] CMD_STATES entering state 0 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.857: [egismoc] CMD_STATES entering state 1 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.858: Command receive callback 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.858: [egismoc] CMD_STATES completed successfully 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.858: Task SSM next state callback 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.858: [egismoc] IDENTIFY_STATES entering state 8 406s (process:2115): libfprint-device-DEBUG: 00:54:15.858: Device reported verify completion 406s (process:2115): libfprint-device-DEBUG: 00:54:15.858: Device reported finger status change: FP_FINGER_STATUS_NONE 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.858: [egismoc] IDENTIFY_STATES completed successfully 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.858: Task SSM done 406s (process:2115): libfprint-device-DEBUG: 00:54:15.858: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 406s (process:2115): libfprint-device-DEBUG: 00:54:15.858: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 406s (process:2115): libfprint-device-DEBUG: 00:54:15.858: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.858: Identify or Verify 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.858: [egismoc] IDENTIFY_STATES entering state 0 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.858: Execute command and get response 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.858: Get check bytes 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.858: [egismoc] CMD_STATES entering state 0 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.859: [egismoc] CMD_STATES entering state 1 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.859: Command receive callback 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.859: [egismoc] CMD_STATES completed successfully 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.859: List callback 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.859: Device fingerprint 1: FP1-00000000-2-00000000-nobody 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.859: Number of currently enrolled fingerprints on the device is 1 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.859: [egismoc] IDENTIFY_STATES entering state 1 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.859: [egismoc] IDENTIFY_STATES entering state 2 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.859: Execute command and get response 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.859: Get check bytes 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.859: [egismoc] CMD_STATES entering state 0 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.860: [egismoc] CMD_STATES entering state 1 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.860: Command receive callback 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.860: [egismoc] CMD_STATES completed successfully 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.860: Task SSM next state callback 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.860: [egismoc] IDENTIFY_STATES entering state 3 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.860: Execute command and get response 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.860: Get check bytes 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.860: [egismoc] CMD_STATES entering state 0 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.860: [egismoc] CMD_STATES entering state 1 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.861: Command receive callback 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.861: [egismoc] CMD_STATES completed successfully 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.861: Task SSM next state callback 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.861: [egismoc] IDENTIFY_STATES entering state 4 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.861: Wait for finger on sensor 406s (process:2115): libfprint-device-DEBUG: 00:54:15.861: Device reported finger status change: FP_FINGER_STATUS_NEEDED 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.861: Finger on sensor callback 406s (process:2115): libfprint-device-DEBUG: 00:54:15.861: Device reported finger status change: FP_FINGER_STATUS_PRESENT 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.861: [egismoc] IDENTIFY_STATES entering state 5 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.861: Execute command and get response 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.861: Get check bytes 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.861: [egismoc] CMD_STATES entering state 0 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.862: [egismoc] CMD_STATES entering state 1 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.862: Command receive callback 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.862: [egismoc] CMD_STATES completed successfully 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.862: Task SSM next state callback 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.862: [egismoc] IDENTIFY_STATES entering state 6 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.862: Get check command 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.862: Execute command and get response 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.862: Get check bytes 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.862: [egismoc] CMD_STATES entering state 0 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.863: [egismoc] CMD_STATES entering state 1 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.863: Command receive callback 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.863: [egismoc] CMD_STATES completed successfully 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.863: Identify check callback 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.863: Response suffix valid: yes 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.863: Identify successful for: FP1-00000000-2-00000000-nobody 406s (process:2115): libfprint-device-DEBUG: 00:54:15.863: Device reported identify result 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.863: [egismoc] IDENTIFY_STATES entering state 7 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.863: Execute command and get response 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.863: Get check bytes 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.863: [egismoc] CMD_STATES entering state 0 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.864: [egismoc] CMD_STATES entering state 1 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.864: Command receive callback 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.864: [egismoc] CMD_STATES completed successfully 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.864: Task SSM next state callback 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.864: [egismoc] IDENTIFY_STATES entering state 8 406s (process:2115): libfprint-device-DEBUG: 00:54:15.864: Device reported identify completion 406s (process:2115): libfprint-device-DEBUG: 00:54:15.864: Device reported finger status change: FP_FINGER_STATUS_NONE 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.864: [egismoc] IDENTIFY_STATES completed successfully 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.864: Task SSM done 406s (process:2115): libfprint-device-DEBUG: 00:54:15.864: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 406s (process:2115): libfprint-device-DEBUG: 00:54:15.864: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 406s (process:2115): libfprint-device-DEBUG: 00:54:15.865: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.865: Enroll 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.865: [egismoc] ENROLL_STATES entering state 0 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.865: Execute command and get response 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.865: Get check bytes 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.865: [egismoc] CMD_STATES entering state 0 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.865: [egismoc] CMD_STATES entering state 1 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.866: Command receive callback 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.866: [egismoc] CMD_STATES completed successfully 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.866: List callback 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.866: Device fingerprint 1: FP1-00000000-2-00000000-nobody 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.866: Number of currently enrolled fingerprints on the device is 1 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.866: [egismoc] ENROLL_STATES entering state 1 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.866: [egismoc] ENROLL_STATES entering state 2 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.866: Execute command and get response 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.866: Get check bytes 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.866: [egismoc] CMD_STATES entering state 0 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.866: [egismoc] CMD_STATES entering state 1 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.867: Command receive callback 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.867: [egismoc] CMD_STATES completed successfully 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.867: Task SSM next state callback 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.867: [egismoc] ENROLL_STATES entering state 3 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.867: Execute command and get response 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.867: Get check bytes 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.867: [egismoc] CMD_STATES entering state 0 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.867: [egismoc] CMD_STATES entering state 1 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.868: Command receive callback 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.868: [egismoc] CMD_STATES completed successfully 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.868: Task SSM next state callback 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.868: [egismoc] ENROLL_STATES entering state 4 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.868: Wait for finger on sensor 406s (process:2115): libfprint-device-DEBUG: 00:54:15.868: Device reported finger status change: FP_FINGER_STATUS_NEEDED 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.868: Finger on sensor callback 406s (process:2115): libfprint-device-DEBUG: 00:54:15.868: Device reported finger status change: FP_FINGER_STATUS_PRESENT 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.868: [egismoc] ENROLL_STATES entering state 5 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.868: Execute command and get response 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.868: Get check bytes 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.868: [egismoc] CMD_STATES entering state 0 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.869: [egismoc] CMD_STATES entering state 1 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.869: Command receive callback 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.869: [egismoc] CMD_STATES completed successfully 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.869: Task SSM next state callback 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.869: [egismoc] ENROLL_STATES entering state 6 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.869: Get check command 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.869: Execute command and get response 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.869: Get check bytes 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.869: [egismoc] CMD_STATES entering state 0 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.870: [egismoc] CMD_STATES entering state 1 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.870: Command receive callback 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.870: [egismoc] CMD_STATES completed successfully 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.870: Enroll check callback 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.870: Response suffix valid: NO 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.870: [egismoc] SSM ENROLL_STATES failed in state 6 with error: This finger has already enrolled, please try a different finger 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.870: [egismoc] ENROLL_STATES completed with error: This finger has already enrolled, please try a different finger 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.870: Task SSM done 406s (process:2115): libfprint-device-DEBUG: 00:54:15.870: Device reported generic error (This finger has already enrolled, please try a different finger) during action; action was: FPI_DEVICE_ACTION_ENROLL 406s (process:2115): libfprint-device-DEBUG: 00:54:15.870: Device reported enroll completion 406s (process:2115): libfprint-device-DEBUG: 00:54:15.870: Device reported finger status change: FP_FINGER_STATUS_NONE 406s (process:2115): libfprint-device-DEBUG: 00:54:15.870: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 406s (process:2115): libfprint-device-DEBUG: 00:54:15.870: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.870: List 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.870: [egismoc] LIST_STATES entering state 0 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.870: Execute command and get response 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.870: Get check bytes 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.871: [egismoc] CMD_STATES entering state 0 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.871: [egismoc] CMD_STATES entering state 1 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.871: Command receive callback 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.871: [egismoc] CMD_STATES completed successfully 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.871: List callback 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.871: Device fingerprint 1: FP1-00000000-2-00000000-nobody 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.871: Number of currently enrolled fingerprints on the device is 1 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.871: [egismoc] LIST_STATES entering state 1 406s (process:2115): libfprint-device-DEBUG: 00:54:15.871: Device reported listing completion 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.871: [egismoc] LIST_STATES completed successfully 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.871: Task SSM done 406s (process:2115): libfprint-device-DEBUG: 00:54:15.871: Completing action FPI_DEVICE_ACTION_LIST in idle! 406s (process:2115): libfprint-device-DEBUG: 00:54:15.871: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 406s (process:2115): libfprint-device-DEBUG: 00:54:15.872: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.872: Enroll 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.872: [egismoc] ENROLL_STATES entering state 0 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.872: Execute command and get response 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.872: Get check bytes 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.872: [egismoc] CMD_STATES entering state 0 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.872: [egismoc] CMD_STATES entering state 1 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.872: Command receive callback 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.872: [egismoc] CMD_STATES completed successfully 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.872: List callback 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.872: Device fingerprint 1: FP1-00000000-2-00000000-nobody 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.872: Number of currently enrolled fingerprints on the device is 1 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.872: [egismoc] ENROLL_STATES entering state 1 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.872: [egismoc] ENROLL_STATES entering state 2 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.872: Execute command and get response 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.872: Get check bytes 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.872: [egismoc] CMD_STATES entering state 0 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.873: [egismoc] CMD_STATES entering state 1 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.873: Command receive callback 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.873: [egismoc] CMD_STATES completed successfully 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.873: Task SSM next state callback 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.873: [egismoc] ENROLL_STATES entering state 3 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.873: Execute command and get response 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.873: Get check bytes 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.873: [egismoc] CMD_STATES entering state 0 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.874: [egismoc] CMD_STATES entering state 1 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.874: Command receive callback 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.874: [egismoc] CMD_STATES completed successfully 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.874: Task SSM next state callback 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.874: [egismoc] ENROLL_STATES entering state 4 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.874: Wait for finger on sensor 406s (process:2115): libfprint-device-DEBUG: 00:54:15.874: Device reported finger status change: FP_FINGER_STATUS_NEEDED 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.875: Finger on sensor callback 406s (process:2115): libfprint-device-DEBUG: 00:54:15.875: Device reported finger status change: FP_FINGER_STATUS_PRESENT 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.875: [egismoc] ENROLL_STATES entering state 5 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.875: Execute command and get response 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.875: Get check bytes 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.875: [egismoc] CMD_STATES entering state 0 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.875: [egismoc] CMD_STATES entering state 1 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.875: Command receive callback 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.875: [egismoc] CMD_STATES completed successfully 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.875: Task SSM next state callback 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.875: [egismoc] ENROLL_STATES entering state 6 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.875: Get check command 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.875: Execute command and get response 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.875: Get check bytes 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.875: [egismoc] CMD_STATES entering state 0 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.876: [egismoc] CMD_STATES entering state 1 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.876: Command receive callback 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.876: [egismoc] CMD_STATES completed successfully 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.876: Enroll check callback 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.876: Response suffix valid: yes 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.876: [egismoc] ENROLL_STATES entering state 7 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.876: Execute command and get response 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.876: Get check bytes 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.876: [egismoc] CMD_STATES entering state 0 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.877: [egismoc] CMD_STATES entering state 1 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.877: Command receive callback 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.877: [egismoc] CMD_STATES completed successfully 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.877: Task SSM next state callback 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.877: [egismoc] ENROLL_STATES entering state 8 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.877: Execute command and get response 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.877: Get check bytes 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.877: [egismoc] CMD_STATES entering state 0 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.878: [egismoc] CMD_STATES entering state 1 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.878: Command receive callback 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.878: [egismoc] CMD_STATES completed successfully 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.878: Task SSM next state callback 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.878: [egismoc] ENROLL_STATES entering state 9 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.878: Execute command and get response 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.878: Get check bytes 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.878: [egismoc] CMD_STATES entering state 0 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.878: [egismoc] CMD_STATES entering state 1 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.879: Command receive callback 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.879: [egismoc] CMD_STATES completed successfully 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.879: Task SSM next state callback 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.879: [egismoc] ENROLL_STATES entering state 10 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.879: Wait for finger on sensor 406s (process:2115): libfprint-device-DEBUG: 00:54:15.879: Device reported finger status change: FP_FINGER_STATUS_NEEDED 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.879: Finger on sensor callback 406s (process:2115): libfprint-device-DEBUG: 00:54:15.879: Device reported finger status change: FP_FINGER_STATUS_PRESENT 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.879: [egismoc] ENROLL_STATES entering state 11 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.879: Execute command and get response 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.879: Get check bytes 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.879: [egismoc] CMD_STATES entering state 0 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.880: [egismoc] CMD_STATES entering state 1 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.880: Command receive callback 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.880: [egismoc] CMD_STATES completed successfully 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.880: Read capture callback 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.880: Response prefix valid: yes 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.880: Response suffix valid: yes 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.880: Partial capture successful. Please touch the sensor again (1/20) 406s (process:2115): libfprint-device-DEBUG: 00:54:15.880: Device reported enroll progress, reported 1 of 20 have been completed 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.880: [egismoc] ENROLL_STATES entering state 8 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.880: Execute command and get response 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.880: Get check bytes 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.880: [egismoc] CMD_STATES entering state 0 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.881: [egismoc] CMD_STATES entering state 1 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.881: Command receive callback 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.881: [egismoc] CMD_STATES completed successfully 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.881: Task SSM next state callback 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.881: [egismoc] ENROLL_STATES entering state 9 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.881: Execute command and get response 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.881: Get check bytes 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.881: [egismoc] CMD_STATES entering state 0 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.882: [egismoc] CMD_STATES entering state 1 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.882: Command receive callback 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.882: [egismoc] CMD_STATES completed successfully 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.882: Task SSM next state callback 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.882: [egismoc] ENROLL_STATES entering state 10 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.882: Wait for finger on sensor 406s (process:2115): libfprint-device-DEBUG: 00:54:15.882: Device reported finger status change: FP_FINGER_STATUS_NEEDED 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.883: Finger on sensor callback 406s (process:2115): libfprint-device-DEBUG: 00:54:15.883: Device reported finger status change: FP_FINGER_STATUS_PRESENT 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.883: [egismoc] ENROLL_STATES entering state 11 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.883: Execute command and get response 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.883: Get check bytes 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.883: [egismoc] CMD_STATES entering state 0 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.883: [egismoc] CMD_STATES entering state 1 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.884: Command receive callback 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.884: [egismoc] CMD_STATES completed successfully 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.884: Read capture callback 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.884: Response prefix valid: yes 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.884: Response suffix valid: yes 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.884: Partial capture successful. Please touch the sensor again (2/20) 406s (process:2115): libfprint-device-DEBUG: 00:54:15.884: Device reported enroll progress, reported 2 of 20 have been completed 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.884: [egismoc] ENROLL_STATES entering state 8 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.884: Execute command and get response 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.884: Get check bytes 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.884: [egismoc] CMD_STATES entering state 0 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.884: [egismoc] CMD_STATES entering state 1 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.885: Command receive callback 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.885: [egismoc] CMD_STATES completed successfully 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.885: Task SSM next state callback 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.885: [egismoc] ENROLL_STATES entering state 9 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.885: Execute command and get response 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.885: Get check bytes 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.885: [egismoc] CMD_STATES entering state 0 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.885: [egismoc] CMD_STATES entering state 1 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.886: Command receive callback 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.886: [egismoc] CMD_STATES completed successfully 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.886: Task SSM next state callback 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.886: [egismoc] ENROLL_STATES entering state 10 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.886: Wait for finger on sensor 406s (process:2115): libfprint-device-DEBUG: 00:54:15.886: Device reported finger status change: FP_FINGER_STATUS_NEEDED 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.886: Finger on sensor callback 406s (process:2115): libfprint-device-DEBUG: 00:54:15.886: Device reported finger status change: FP_FINGER_STATUS_PRESENT 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.886: [egismoc] ENROLL_STATES entering state 11 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.886: Execute command and get response 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.886: Get check bytes 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.886: [egismoc] CMD_STATES entering state 0 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.886: [egismoc] CMD_STATES entering state 1 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.887: Command receive callback 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.887: [egismoc] CMD_STATES completed successfully 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.887: Read capture callback 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.887: Response prefix valid: yes 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.887: Response suffix valid: yes 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.887: Partial capture successful. Please touch the sensor again (3/20) 406s (process:2115): libfprint-device-DEBUG: 00:54:15.887: Device reported enroll progress, reported 3 of 20 have been completed 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.887: [egismoc] ENROLL_STATES entering state 8 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.887: Execute command and get response 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.887: Get check bytes 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.887: [egismoc] CMD_STATES entering state 0 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.887: [egismoc] CMD_STATES entering state 1 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.888: Command receive callback 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.888: [egismoc] CMD_STATES completed successfully 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.888: Task SSM next state callback 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.888: [egismoc] ENROLL_STATES entering state 9 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.888: Execute command and get response 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.888: Get check bytes 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.888: [egismoc] CMD_STATES entering state 0 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.888: [egismoc] CMD_STATES entering state 1 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.889: Command receive callback 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.889: [egismoc] CMD_STATES completed successfully 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.889: Task SSM next state callback 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.889: [egismoc] ENROLL_STATES entering state 10 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.889: Wait for finger on sensor 406s (process:2115): libfprint-device-DEBUG: 00:54:15.889: Device reported finger status change: FP_FINGER_STATUS_NEEDED 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.889: Finger on sensor callback 406s (process:2115): libfprint-device-DEBUG: 00:54:15.889: Device reported finger status change: FP_FINGER_STATUS_PRESENT 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.889: [egismoc] ENROLL_STATES entering state 11 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.889: Execute command and get response 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.889: Get check bytes 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.889: [egismoc] CMD_STATES entering state 0 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.890: [egismoc] CMD_STATES entering state 1 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.890: Command receive callback 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.890: [egismoc] CMD_STATES completed successfully 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.890: Read capture callback 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.890: Response prefix valid: yes 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.890: Response suffix valid: yes 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.890: Partial capture successful. Please touch the sensor again (4/20) 406s (process:2115): libfprint-device-DEBUG: 00:54:15.890: Device reported enroll progress, reported 4 of 20 have been completed 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.890: [egismoc] ENROLL_STATES entering state 8 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.890: Execute command and get response 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.890: Get check bytes 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.890: [egismoc] CMD_STATES entering state 0 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.891: [egismoc] CMD_STATES entering state 1 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.891: Command receive callback 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.891: [egismoc] CMD_STATES completed successfully 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.891: Task SSM next state callback 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.891: [egismoc] ENROLL_STATES entering state 9 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.891: Execute command and get response 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.891: Get check bytes 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.891: [egismoc] CMD_STATES entering state 0 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.892: [egismoc] CMD_STATES entering state 1 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.892: Command receive callback 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.892: [egismoc] CMD_STATES completed successfully 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.892: Task SSM next state callback 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.892: [egismoc] ENROLL_STATES entering state 10 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.892: Wait for finger on sensor 406s (process:2115): libfprint-device-DEBUG: 00:54:15.892: Device reported finger status change: FP_FINGER_STATUS_NEEDED 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.893: Finger on sensor callback 406s (process:2115): libfprint-device-DEBUG: 00:54:15.893: Device reported finger status change: FP_FINGER_STATUS_PRESENT 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.893: [egismoc] ENROLL_STATES entering state 11 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.893: Execute command and get response 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.893: Get check bytes 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.893: [egismoc] CMD_STATES entering state 0 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.893: [egismoc] CMD_STATES entering state 1 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.894: Command receive callback 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.894: [egismoc] CMD_STATES completed successfully 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.894: Read capture callback 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.894: Response prefix valid: yes 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.894: Response suffix valid: yes 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.894: Partial capture successful. Please touch the sensor again (5/20) 406s (process:2115): libfprint-device-DEBUG: 00:54:15.894: Device reported enroll progress, reported 5 of 20 have been completed 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.894: [egismoc] ENROLL_STATES entering state 8 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.894: Execute command and get response 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.894: Get check bytes 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.894: [egismoc] CMD_STATES entering state 0 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.894: [egismoc] CMD_STATES entering state 1 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.895: Command receive callback 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.895: [egismoc] CMD_STATES completed successfully 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.895: Task SSM next state callback 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.895: [egismoc] ENROLL_STATES entering state 9 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.895: Execute command and get response 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.895: Get check bytes 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.895: [egismoc] CMD_STATES entering state 0 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.895: [egismoc] CMD_STATES entering state 1 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.896: Command receive callback 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.896: [egismoc] CMD_STATES completed successfully 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.896: Task SSM next state callback 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.896: [egismoc] ENROLL_STATES entering state 10 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.896: Wait for finger on sensor 406s (process:2115): libfprint-device-DEBUG: 00:54:15.896: Device reported finger status change: FP_FINGER_STATUS_NEEDED 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.896: Finger on sensor callback 406s (process:2115): libfprint-device-DEBUG: 00:54:15.896: Device reported finger status change: FP_FINGER_STATUS_PRESENT 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.896: [egismoc] ENROLL_STATES entering state 11 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.896: Execute command and get response 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.896: Get check bytes 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.896: [egismoc] CMD_STATES entering state 0 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.897: [egismoc] CMD_STATES entering state 1 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.897: Command receive callback 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.897: [egismoc] CMD_STATES completed successfully 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.897: Read capture callback 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.897: Response prefix valid: yes 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.897: Response suffix valid: yes 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.897: Partial capture successful. Please touch the sensor again (6/20) 406s (process:2115): libfprint-device-DEBUG: 00:54:15.897: Device reported enroll progress, reported 6 of 20 have been completed 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.897: [egismoc] ENROLL_STATES entering state 8 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.897: Execute command and get response 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.897: Get check bytes 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.897: [egismoc] CMD_STATES entering state 0 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.898: [egismoc] CMD_STATES entering state 1 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.898: Command receive callback 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.898: [egismoc] CMD_STATES completed successfully 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.898: Task SSM next state callback 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.898: [egismoc] ENROLL_STATES entering state 9 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.898: Execute command and get response 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.898: Get check bytes 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.898: [egismoc] CMD_STATES entering state 0 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.899: [egismoc] CMD_STATES entering state 1 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.899: Command receive callback 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.899: [egismoc] CMD_STATES completed successfully 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.899: Task SSM next state callback 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.899: [egismoc] ENROLL_STATES entering state 10 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.899: Wait for finger on sensor 406s (process:2115): libfprint-device-DEBUG: 00:54:15.899: Device reported finger status change: FP_FINGER_STATUS_NEEDED 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.900: Finger on sensor callback 406s (process:2115): libfprint-device-DEBUG: 00:54:15.900: Device reported finger status change: FP_FINGER_STATUS_PRESENT 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.900: [egismoc] ENROLL_STATES entering state 11 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.900: Execute command and get response 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.900: Get check bytes 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.900: [egismoc] CMD_STATES entering state 0 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.900: [egismoc] CMD_STATES entering state 1 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.901: Command receive callback 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.901: [egismoc] CMD_STATES completed successfully 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.901: Read capture callback 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.901: Response prefix valid: yes 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.901: Response suffix valid: yes 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.901: Partial capture successful. Please touch the sensor again (7/20) 406s (process:2115): libfprint-device-DEBUG: 00:54:15.901: Device reported enroll progress, reported 7 of 20 have been completed 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.901: [egismoc] ENROLL_STATES entering state 8 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.901: Execute command and get response 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.901: Get check bytes 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.901: [egismoc] CMD_STATES entering state 0 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.901: [egismoc] CMD_STATES entering state 1 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.902: Command receive callback 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.902: [egismoc] CMD_STATES completed successfully 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.902: Task SSM next state callback 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.902: [egismoc] ENROLL_STATES entering state 9 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.902: Execute command and get response 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.902: Get check bytes 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.902: [egismoc] CMD_STATES entering state 0 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.902: [egismoc] CMD_STATES entering state 1 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.903: Command receive callback 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.903: [egismoc] CMD_STATES completed successfully 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.903: Task SSM next state callback 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.903: [egismoc] ENROLL_STATES entering state 10 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.903: Wait for finger on sensor 406s (process:2115): libfprint-device-DEBUG: 00:54:15.903: Device reported finger status change: FP_FINGER_STATUS_NEEDED 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.903: Finger on sensor callback 406s (process:2115): libfprint-device-DEBUG: 00:54:15.903: Device reported finger status change: FP_FINGER_STATUS_PRESENT 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.903: [egismoc] ENROLL_STATES entering state 11 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.903: Execute command and get response 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.903: Get check bytes 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.903: [egismoc] CMD_STATES entering state 0 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.904: [egismoc] CMD_STATES entering state 1 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.905: Command receive callback 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.905: [egismoc] CMD_STATES completed successfully 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.905: Read capture callback 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.905: Response prefix valid: yes 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.905: Response suffix valid: NO 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.905: Response prefix valid: yes 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.905: Response suffix valid: yes 406s (process:2115): libfprint-device-DEBUG: 00:54:15.905: Device reported enroll progress, reported 7 of 20 have been completed 406s listing - device should have prints 406s clear device storage 406s clear done 406s listing - device should be empty 406s enrolling 406s finger status: 406s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xf0cef628 (FpiDeviceEgisMoc at 0x72a810)>, 1, , None, None) 406s finger status: 406s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xf0cef628 (FpiDeviceEgisMoc at 0x72a810)>, 2, , None, None) 406s finger status: 406s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xf0cef628 (FpiDeviceEgisMoc at 0x72a810)>, 3, , None, None) 406s finger status: 406s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xf0cef628 (FpiDeviceEgisMoc at 0x72a810)>, 4, , None, None) 406s finger status: 406s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xf0cef628 (FpiDeviceEgisMoc at 0x72a810)>, 5, , None, None) 406s finger status: 406s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xf0cef628 (FpiDeviceEgisMoc at 0x72a810)>, 6, , None, None) 406s finger status: 406s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xf0cef628 (FpiDeviceEgisMoc at 0x72a810)>, 7, , None, None) 406s finger status: 406s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xf0cef628 (FpiDeviceEgisMoc at 0x72a810)>, 8, , None, None) 406s finger status: 406s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xf0cef628 (FpiDeviceEgisMoc at 0x72a810)>, 9, , None, None) 406s finger status: 406s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xf0cef628 (FpiDeviceEgisMoc at 0x72a810)>, 9, None, None, GLib.Error('The finger was not centered properly, please try again.', 'fp - device - retry - quark', 2)) 406s finger status: 406s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xf0cef628 (FpiDeviceEgisMoc at 0x72a810)>, 10, , None, None) 406s finger status: 406s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xf0cef628 (FpiDeviceEgisMoc at 0x72a810)>, 10, None, None, GLib.Error('The finger was not centered properly, please try again.', 'fp - device - retry - quark', 2)) 406s finger status: 406s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xf0cef628 (FpiDeviceEgisMoc at 0x72a810)>, 11, , None, None) 406s finger status: 406s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xf0cef628 (FpiDeviceEgisMoc at 0x72a810)>, 12, , None, None) 406s finger status: 406s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xf0cef628 (FpiDeviceEgisMoc at 0x72a810)>, 13, , None, None) 406s finger status: 406s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xf0cef628 (FpiDeviceEgisMoc at 0x72a810)>, 14, , None, None) 406s finger status: 406s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xf0cef628 (FpiDeviceEgisMoc at 0x72a810)>, 15, , None, None) 406s finger status: 406s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xf0cef628 (FpiDeviceEgisMoc at 0x72a810)>, 16, , None, None) 406s finger status: 406s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xf0cef628 (FpiDeviceEgisMoc at 0x72a810)>, 17, , None, None) 406s finger status: 406s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xf0cef628 (FpiDeviceEgisMoc at 0x72a810)>, 18, , None, None) 406s finger status: 406s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xf0cef628 (FpiDeviceEgisMoc at 0x72a810)>, 19, , None, None) 406s finger status: 406s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xf0cef628 (FpiDeviceEgisMoc at 0x72a810)>, 20, , None, None) 406s enroll done 406s listing - device should have 1 print 406s verifying 406s verify done 406s async identifying 406s indentification_done: 406s try to enroll duplicate 406s duplicate enroll attempt done 406s listing - device should still only have 1 print 406s enroll new finger 406s finger status: 406s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xf0cef628 (FpiDeviceEgisMoc at 0x72a810)>, 1, , None, None) 406s finger status: 406s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xf0cef628 (FpiDeviceEgisMoc at 0x72a810)>, 2, , None, None) 406s finger status: 406s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xf0cef628 (FpiDeviceEgisMoc at 0x72a810)>, 3, , None, None) 406s finger status: 406s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xf0cef628 (FpiDeviceEgisMoc at 0x72a810)>, 4, , None, None) 406s finger status: 406s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xf0cef628 (FpiDeviceEgisMoc at 0x72a810)>, 5, , None, None) 406s finger status: 406s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xf0cef628 (FpiDeviceEgisMoc at 0x72a810)>, 6, , None, None) 406s finger status: 406s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xf0cef628 (FpiDeviceEgisMoc at 0x72a810)>, 7, , None, None) 406s finger status: 406s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xf0cef628 (FpiDeviceEgisMoc at 0x72a810)>, 7, None, None, GLib.Error('The finger was not centered properly, please try again.', 'fp - device - retry - quark', 2))(process:2115): libfprint-SSM-DEBUG: 00:54:15.905: [egismoc] ENROLL_STATES entering state 8 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.905: Execute command and get response 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.905: Get check bytes 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.905: [egismoc] CMD_STATES entering state 0 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.905: [egismoc] CMD_STATES entering state 1 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.906: Command receive callback 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.906: [egismoc] CMD_STATES completed successfully 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.906: Task SSM next state callback 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.906: [egismoc] ENROLL_STATES entering state 9 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.906: Execute command and get response 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.906: Get check bytes 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.906: [egismoc] CMD_STATES entering state 0 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.906: [egismoc] CMD_STATES entering state 1 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.907: Command receive callback 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.907: [egismoc] CMD_STATES completed successfully 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.907: Task SSM next state callback 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.907: [egismoc] ENROLL_STATES entering state 10 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.907: Wait for finger on sensor 406s (process:2115): libfprint-device-DEBUG: 00:54:15.907: Device reported finger status change: FP_FINGER_STATUS_NEEDED 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.907: Finger on sensor callback 406s (process:2115): libfprint-device-DEBUG: 00:54:15.907: Device reported finger status change: FP_FINGER_STATUS_PRESENT 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.907: [egismoc] ENROLL_STATES entering state 11 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.907: Execute command and get response 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.907: Get check bytes 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.907: [egismoc] CMD_STATES entering state 0 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.907: [egismoc] CMD_STATES entering state 1 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.908: Command receive callback 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.908: [egismoc] CMD_STATES completed successfully 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.908: Read capture callback 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.908: Response prefix valid: yes 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.908: Response suffix valid: yes 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.908: Partial capture successful. Please touch the sensor again (8/20) 406s (process:2115): libfprint-device-DEBUG: 00:54:15.908: Device reported enroll progress, reported 8 of 20 have been completed 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.908: [egismoc] ENROLL_STATES entering state 8 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.908: Execute command and get response 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.908: Get check bytes 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.908: [egismoc] CMD_STATES entering state 0 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.908: [egismoc] CMD_STATES entering state 1 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.909: Command receive callback 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.909: [egismoc] CMD_STATES completed successfully 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.909: Task SSM next state callback 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.909: [egismoc] ENROLL_STATES entering state 9 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.909: Execute command and get response 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.909: Get check bytes 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.909: [egismoc] CMD_STATES entering state 0 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.909: [egismoc] CMD_STATES entering state 1 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.910: Command receive callback 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.910: [egismoc] CMD_STATES completed successfully 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.910: Task SSM next state callback 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.910: [egismoc] ENROLL_STATES entering state 10 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.910: Wait for finger on sensor 406s (process:2115): libfprint-device-DEBUG: 00:54:15.910: Device reported finger status change: FP_FINGER_STATUS_NEEDED 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.910: Finger on sensor callback 406s (process:2115): libfprint-device-DEBUG: 00:54:15.910: Device reported finger status change: FP_FINGER_STATUS_PRESENT 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.910: [egismoc] ENROLL_STATES entering state 11 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.910: Execute command and get response 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.910: Get check bytes 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.910: [egismoc] CMD_STATES entering state 0 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.911: [egismoc] CMD_STATES entering state 1 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.911: Command receive callback 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.911: [egismoc] CMD_STATES completed successfully 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.911: Read capture callback 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.911: Response prefix valid: yes 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.911: Response suffix valid: NO 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.911: Response prefix valid: yes 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.911: Response suffix valid: yes 406s (process:2115): libfprint-device-DEBUG: 00:54:15.911: Device reported enroll progress, reported 8 of 20 have been completed 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.911: [egismoc] ENROLL_STATES entering state 8 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.911: Execute command and get response 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.911: Get check bytes 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.911: [egismoc] CMD_STATES entering state 0 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.912: [egismoc] CMD_STATES entering state 1 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.912: Command receive callback 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.912: [egismoc] CMD_STATES completed successfully 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.912: Task SSM next state callback 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.912: [egismoc] ENROLL_STATES entering state 9 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.912: Execute command and get response 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.912: Get check bytes 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.912: [egismoc] CMD_STATES entering state 0 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.913: [egismoc] CMD_STATES entering state 1 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.913: Command receive callback 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.913: [egismoc] CMD_STATES completed successfully 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.913: Task SSM next state callback 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.913: [egismoc] ENROLL_STATES entering state 10 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.913: Wait for finger on sensor 406s (process:2115): libfprint-device-DEBUG: 00:54:15.913: Device reported finger status change: FP_FINGER_STATUS_NEEDED 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.914: Finger on sensor callback 406s (process:2115): libfprint-device-DEBUG: 00:54:15.914: Device reported finger status change: FP_FINGER_STATUS_PRESENT 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.914: [egismoc] ENROLL_STATES entering state 11 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.914: Execute command and get response 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.914: Get check bytes 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.914: [egismoc] CMD_STATES entering state 0 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.914: [egismoc] CMD_STATES entering state 1 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.915: Command receive callback 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.915: [egismoc] CMD_STATES completed successfully 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.915: Read capture callback 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.915: Response prefix valid: yes 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.915: Response suffix valid: yes 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.915: Partial capture successful. Please touch the sensor again (9/20) 406s (process:2115): libfprint-device-DEBUG: 00:54:15.915: Device reported enroll progress, reported 9 of 20 have been completed 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.915: [egismoc] ENROLL_STATES entering state 8 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.915: Execute command and get response 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.915: Get check bytes 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.915: [egismoc] CMD_STATES entering state 0 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.916: [egismoc] CMD_STATES entering state 1 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.916: Command receive callback 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.916: [egismoc] CMD_STATES completed successfully 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.916: Task SSM next state callback 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.916: [egismoc] ENROLL_STATES entering state 9 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.916: Execute command and get response 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.916: Get check bytes 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.916: [egismoc] CMD_STATES entering state 0 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.917: [egismoc] CMD_STATES entering state 1 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.917: Command receive callback 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.917: [egismoc] CMD_STATES completed successfully 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.917: Task SSM next state callback 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.917: [egismoc] ENROLL_STATES entering state 10 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.917: Wait for finger on sensor 406s (process:2115): libfprint-device-DEBUG: 00:54:15.917: Device reported finger status change: FP_FINGER_STATUS_NEEDED 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.918: Finger on sensor callback 406s (process:2115): libfprint-device-DEBUG: 00:54:15.918: Device reported finger status change: FP_FINGER_STATUS_PRESENT 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.918: [egismoc] ENROLL_STATES entering state 11 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.918: Execute command and get response 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.918: Get check bytes 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.918: [egismoc] CMD_STATES entering state 0 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.918: [egismoc] CMD_STATES entering state 1 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.918: Command receive callback 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.918: [egismoc] CMD_STATES completed successfully 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.918: Read capture callback 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.918: Response prefix valid: yes 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.918: Response suffix valid: yes 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.918: Partial capture successful. Please touch the sensor again (10/20) 406s (process:2115): libfprint-device-DEBUG: 00:54:15.918: Device reported enroll progress, reported 10 of 20 have been completed 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.918: [egismoc] ENROLL_STATES entering state 8 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.918: Execute command and get response 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.918: Get check bytes 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.918: [egismoc] CMD_STATES entering state 0 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.919: [egismoc] CMD_STATES entering state 1 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.920: Command receive callback 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.920: [egismoc] CMD_STATES completed successfully 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.920: Task SSM next state callback 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.920: [egismoc] ENROLL_STATES entering state 9 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.920: Execute command and get response 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.920: Get check bytes 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.920: [egismoc] CMD_STATES entering state 0 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.920: [egismoc] CMD_STATES entering state 1 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.920: Command receive callback 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.920: [egismoc] CMD_STATES completed successfully 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.920: Task SSM next state callback 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.920: [egismoc] ENROLL_STATES entering state 10 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.920: Wait for finger on sensor 406s (process:2115): libfprint-device-DEBUG: 00:54:15.920: Device reported finger status change: FP_FINGER_STATUS_NEEDED 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.921: Finger on sensor callback 406s (process:2115): libfprint-device-DEBUG: 00:54:15.921: Device reported finger status change: FP_FINGER_STATUS_PRESENT 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.921: [egismoc] ENROLL_STATES entering state 11 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.921: Execute command and get response 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.921: Get check bytes 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.921: [egismoc] CMD_STATES entering state 0 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.921: [egismoc] CMD_STATES entering state 1 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.922: Command receive callback 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.922: [egismoc] CMD_STATES completed successfully 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.922: Read capture callback 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.922: Response prefix valid: yes 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.922: Response suffix valid: yes 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.922: Partial capture successful. Please touch the sensor again (11/20) 406s (process:2115): libfprint-device-DEBUG: 00:54:15.922: Device reported enroll progress, reported 11 of 20 have been completed 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.922: [egismoc] ENROLL_STATES entering state 8 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.922: Execute command and get response 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.922: Get check bytes 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.922: [egismoc] CMD_STATES entering state 0 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.922: [egismoc] CMD_STATES entering state 1 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.923: Command receive callback 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.923: [egismoc] CMD_STATES completed successfully 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.923: Task SSM next state callback 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.923: [egismoc] ENROLL_STATES entering state 9 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.923: Execute command and get response 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.923: Get check bytes 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.923: [egismoc] CMD_STATES entering state 0 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.923: [egismoc] CMD_STATES entering state 1 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.924: Command receive callback 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.924: [egismoc] CMD_STATES completed successfully 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.924: Task SSM next state callback 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.924: [egismoc] ENROLL_STATES entering state 10 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.924: Wait for finger on sensor 406s (process:2115): libfprint-device-DEBUG: 00:54:15.924: Device reported finger status change: FP_FINGER_STATUS_NEEDED 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.925: Finger on sensor callback 406s (process:2115): libfprint-device-DEBUG: 00:54:15.925: Device reported finger status change: FP_FINGER_STATUS_PRESENT 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.925: [egismoc] ENROLL_STATES entering state 11 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.925: Execute command and get response 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.925: Get check bytes 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.925: [egismoc] CMD_STATES entering state 0 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.926: [egismoc] CMD_STATES entering state 1 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.926: Command receive callback 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.926: [egismoc] CMD_STATES completed successfully 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.926: Read capture callback 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.926: Response prefix valid: yes 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.926: Response suffix valid: yes 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.926: Partial capture successful. Please touch the sensor again (12/20) 406s (process:2115): libfprint-device-DEBUG: 00:54:15.926: Device reported enroll progress, reported 12 of 20 have been completed 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.926: [egismoc] ENROLL_STATES entering state 8 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.926: Execute command and get response 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.926: Get check bytes 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.926: [egismoc] CMD_STATES entering state 0 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.927: [egismoc] CMD_STATES entering state 1 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.927: Command receive callback 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.927: [egismoc] CMD_STATES completed successfully 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.928: Task SSM next state callback 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.928: [egismoc] ENROLL_STATES entering state 9 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.928: Execute command and get response 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.928: Get check bytes 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.928: [egismoc] CMD_STATES entering state 0 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.928: [egismoc] CMD_STATES entering state 1 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.929: Command receive callback 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.929: [egismoc] CMD_STATES completed successfully 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.929: Task SSM next state callback 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.929: [egismoc] ENROLL_STATES entering state 10 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.929: Wait for finger on sensor 406s (process:2115): libfprint-device-DEBUG: 00:54:15.929: Device reported finger status change: FP_FINGER_STATUS_NEEDED 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.929: Finger on sensor callback 406s (process:2115): libfprint-device-DEBUG: 00:54:15.929: Device reported finger status change: FP_FINGER_STATUS_PRESENT 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.929: [egismoc] ENROLL_STATES entering state 11 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.929: Execute command and get response 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.929: Get check bytes 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.929: [egismoc] CMD_STATES entering state 0 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.930: [egismoc] CMD_STATES entering state 1 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.930: Command receive callback 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.930: [egismoc] CMD_STATES completed successfully 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.930: Read capture callback 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.930: Response prefix valid: yes 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.930: Response suffix valid: yes 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.930: Partial capture successful. Please touch the sensor again (13/20) 406s (process:2115): libfprint-device-DEBUG: 00:54:15.930: Device reported enroll progress, reported 13 of 20 have been completed 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.930: [egismoc] ENROLL_STATES entering state 8 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.930: Execute command and get response 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.930: Get check bytes 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.930: [egismoc] CMD_STATES entering state 0 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.931: [egismoc] CMD_STATES entering state 1 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.931: Command receive callback 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.931: [egismoc] CMD_STATES completed successfully 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.931: Task SSM next state callback 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.931: [egismoc] ENROLL_STATES entering state 9 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.931: Execute command and get response 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.931: Get check bytes 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.931: [egismoc] CMD_STATES entering state 0 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.932: [egismoc] CMD_STATES entering state 1 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.932: Command receive callback 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.932: [egismoc] CMD_STATES completed successfully 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.932: Task SSM next state callback 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.932: [egismoc] ENROLL_STATES entering state 10 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.932: Wait for finger on sensor 406s (process:2115): libfprint-device-DEBUG: 00:54:15.932: Device reported finger status change: FP_FINGER_STATUS_NEEDED 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.933: Finger on sensor callback 406s (process:2115): libfprint-device-DEBUG: 00:54:15.933: Device reported finger status change: FP_FINGER_STATUS_PRESENT 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.933: [egismoc] ENROLL_STATES entering state 11 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.933: Execute command and get response 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.933: Get check bytes 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.933: [egismoc] CMD_STATES entering state 0 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.933: [egismoc] CMD_STATES entering state 1 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.934: Command receive callback 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.934: [egismoc] CMD_STATES completed successfully 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.934: Read capture callback 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.934: Response prefix valid: yes 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.934: Response suffix valid: yes 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.934: Partial capture successful. Please touch the sensor again (14/20) 406s (process:2115): libfprint-device-DEBUG: 00:54:15.934: Device reported enroll progress, reported 14 of 20 have been completed 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.934: [egismoc] ENROLL_STATES entering state 8 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.934: Execute command and get response 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.934: Get check bytes 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.934: [egismoc] CMD_STATES entering state 0 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.934: [egismoc] CMD_STATES entering state 1 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.935: Command receive callback 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.935: [egismoc] CMD_STATES completed successfully 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.935: Task SSM next state callback 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.935: [egismoc] ENROLL_STATES entering state 9 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.935: Execute command and get response 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.935: Get check bytes 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.935: [egismoc] CMD_STATES entering state 0 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.935: [egismoc] CMD_STATES entering state 1 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.936: Command receive callback 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.936: [egismoc] CMD_STATES completed successfully 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.936: Task SSM next state callback 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.936: [egismoc] ENROLL_STATES entering state 10 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.936: Wait for finger on sensor 406s (process:2115): libfprint-device-DEBUG: 00:54:15.936: Device reported finger status change: FP_FINGER_STATUS_NEEDED 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.937: Finger on sensor callback 406s (process:2115): libfprint-device-DEBUG: 00:54:15.937: Device reported finger status change: FP_FINGER_STATUS_PRESENT 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.937: [egismoc] ENROLL_STATES entering state 11 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.937: Execute command and get response 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.937: Get check bytes 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.937: [egismoc] CMD_STATES entering state 0 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.938: [egismoc] CMD_STATES entering state 1 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.938: Command receive callback 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.938: [egismoc] CMD_STATES completed successfully 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.938: Read capture callback 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.938: Response prefix valid: yes 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.938: Response suffix valid: yes 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.938: Partial capture successful. Please touch the sensor again (15/20) 406s (process:2115): libfprint-device-DEBUG: 00:54:15.938: Device reported enroll progress, reported 15 of 20 have been completed 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.938: [egismoc] ENROLL_STATES entering state 8 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.938: Execute command and get response 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.938: Get check bytes 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.938: [egismoc] CMD_STATES entering state 0 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.939: [egismoc] CMD_STATES entering state 1 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.940: Command receive callback 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.940: [egismoc] CMD_STATES completed successfully 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.940: Task SSM next state callback 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.940: [egismoc] ENROLL_STATES entering state 9 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.940: Execute command and get response 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.940: Get check bytes 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.940: [egismoc] CMD_STATES entering state 0 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.940: [egismoc] CMD_STATES entering state 1 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.941: Command receive callback 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.941: [egismoc] CMD_STATES completed successfully 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.941: Task SSM next state callback 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.941: [egismoc] ENROLL_STATES entering state 10 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.941: Wait for finger on sensor 406s (process:2115): libfprint-device-DEBUG: 00:54:15.941: Device reported finger status change: FP_FINGER_STATUS_NEEDED 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.942: Finger on sensor callback 406s (process:2115): libfprint-device-DEBUG: 00:54:15.942: Device reported finger status change: FP_FINGER_STATUS_PRESENT 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.942: [egismoc] ENROLL_STATES entering state 11 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.942: Execute command and get response 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.942: Get check bytes 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.942: [egismoc] CMD_STATES entering state 0 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.942: [egismoc] CMD_STATES entering state 1 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.943: Command receive callback 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.943: [egismoc] CMD_STATES completed successfully 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.943: Read capture callback 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.943: Response prefix valid: yes 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.943: Response suffix valid: yes 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.943: Partial capture successful. Please touch the sensor again (16/20) 406s (process:2115): libfprint-device-DEBUG: 00:54:15.943: Device reported enroll progress, reported 16 of 20 have been completed 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.943: [egismoc] ENROLL_STATES entering state 8 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.943: Execute command and get response 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.943: Get check bytes 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.943: [egismoc] CMD_STATES entering state 0 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.943: [egismoc] CMD_STATES entering state 1 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.944: Command receive callback 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.944: [egismoc] CMD_STATES completed successfully 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.944: Task SSM next state callback 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.944: [egismoc] ENROLL_STATES entering state 9 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.944: Execute command and get response 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.944: Get check bytes 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.944: [egismoc] CMD_STATES entering state 0 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.945: [egismoc] CMD_STATES entering state 1 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.945: Command receive callback 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.945: [egismoc] CMD_STATES completed successfully 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.945: Task SSM next state callback 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.945: [egismoc] ENROLL_STATES entering state 10 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.945: Wait for finger on sensor 406s (process:2115): libfprint-device-DEBUG: 00:54:15.945: Device reported finger status change: FP_FINGER_STATUS_NEEDED 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.946: Finger on sensor callback 406s (process:2115): libfprint-device-DEBUG: 00:54:15.946: Device reported finger status change: FP_FINGER_STATUS_PRESENT 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.946: [egismoc] ENROLL_STATES entering state 11 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.946: Execute command and get response 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.946: Get check bytes 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.946: [egismoc] CMD_STATES entering state 0 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.946: [egismoc] CMD_STATES entering state 1 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.947: Command receive callback 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.947: [egismoc] CMD_STATES completed successfully 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.947: Read capture callback 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.947: Response prefix valid: yes 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.947: Response suffix valid: yes 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.947: Partial capture successful. Please touch the sensor again (17/20) 406s (process:2115): libfprint-device-DEBUG: 00:54:15.947: Device reported enroll progress, reported 17 of 20 have been completed 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.947: [egismoc] ENROLL_STATES entering state 8 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.947: Execute command and get response 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.947: Get check bytes 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.947: [egismoc] CMD_STATES entering state 0 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.947: [egismoc] CMD_STATES entering state 1 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.948: Command receive callback 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.948: [egismoc] CMD_STATES completed successfully 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.948: Task SSM next state callback 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.948: [egismoc] ENROLL_STATES entering state 9 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.948: Execute command and get response 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.948: Get check bytes 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.948: [egismoc] CMD_STATES entering state 0 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.949: [egismoc] CMD_STATES entering state 1 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.949: Command receive callback 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.949: [egismoc] CMD_STATES completed successfully 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.949: Task SSM next state callback 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.949: [egismoc] ENROLL_STATES entering state 10 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.949: Wait for finger on sensor 406s (process:2115): libfprint-device-DEBUG: 00:54:15.949: Device reported finger status change: FP_FINGER_STATUS_NEEDED 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.950: Finger on sensor callback 406s (process:2115): libfprint-device-DEBUG: 00:54:15.950: Device reported finger status change: FP_FINGER_STATUS_PRESENT 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.950: [egismoc] ENROLL_STATES entering state 11 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.950: Execute command and get response 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.950: Get check bytes 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.950: [egismoc] CMD_STATES entering state 0 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.951: [egismoc] CMD_STATES entering state 1 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.951: Command receive callback 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.951: [egismoc] CMD_STATES completed successfully 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.951: Read capture callback 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.951: Response prefix valid: yes 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.951: Response suffix valid: yes 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.951: Partial capture successful. Please touch the sensor again (18/20) 406s (process:2115): libfprint-device-DEBUG: 00:54:15.951: Device reported enroll progress, reported 18 of 20 have been completed 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.951: [egismoc] ENROLL_STATES entering state 8 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.951: Execute command and get response 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.951: Get check bytes 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.951: [egismoc] CMD_STATES entering state 0 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.952: [egismoc] CMD_STATES entering state 1 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.953: Command receive callback 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.953: [egismoc] CMD_STATES completed successfully 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.953: Task SSM next state callback 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.953: [egismoc] ENROLL_STATES entering state 9 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.953: Execute command and get response 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.953: Get check bytes 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.953: [egismoc] CMD_STATES entering state 0 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.953: [egismoc] CMD_STATES entering state 1 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.954: Command receive callback 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.954: [egismoc] CMD_STATES completed successfully 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.954: Task SSM next state callback 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.954: [egismoc] ENROLL_STATES entering state 10 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.954: Wait for finger on sensor 406s (process:2115): libfprint-device-DEBUG: 00:54:15.954: Device reported finger status change: FP_FINGER_STATUS_NEEDED 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.955: Finger on sensor callback 406s (process:2115): libfprint-device-DEBUG: 00:54:15.955: Device reported finger status change: FP_FINGER_STATUS_PRESENT 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.955: [egismoc] ENROLL_STATES entering state 11 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.955: Execute command and get response 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.955: Get check bytes 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.955: [egismoc] CMD_STATES entering state 0 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.955: [egismoc] CMD_STATES entering state 1 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.956: Command receive callback 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.956: [egismoc] CMD_STATES completed successfully 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.956: Read capture callback 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.956: Response prefix valid: yes 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.956: Response suffix valid: yes 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.956: Partial capture successful. Please touch the sensor again (19/20) 406s (process:2115): libfprint-device-DEBUG: 00:54:15.956: Device reported enroll progress, reported 19 of 20 have been completed 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.956: [egismoc] ENROLL_STATES entering state 8 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.956: Execute command and get response 406s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.956: Get check bytes 406s (process:2115): libfprint-SSM-DEBUG: 00:54:15.956: [egismoc] CMD_STATES entering state 0 407s (process:2115): libfprint-SSM-DEBUG: 00:54:15.956: [egismoc] CMD_STATES entering state 1 407s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.957: Command receive callback 407s (process:2115): libfprint-SSM-DEBUG: 00:54:15.957: [egismoc] CMD_STATES completed successfully 407s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.957: Task SSM next state callback 407s (process:2115): libfprint-SSM-DEBUG: 00:54:15.957: [egismoc] ENROLL_STATES entering state 9 407s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.957: Execute command and get response 407s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.957: Get check bytes 407s (process:2115): libfprint-SSM-DEBUG: 00:54:15.957: [egismoc] CMD_STATES entering state 0 407s (process:2115): libfprint-SSM-DEBUG: 00:54:15.957: [egismoc] CMD_STATES entering state 1 407s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.958: Command receive callback 407s (process:2115): libfprint-SSM-DEBUG: 00:54:15.958: [egismoc] CMD_STATES completed successfully 407s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.958: Task SSM next state callback 407s (process:2115): libfprint-SSM-DEBUG: 00:54:15.958: [egismoc] ENROLL_STATES entering state 10 407s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.958: Wait for finger on sensor 407s (process:2115): libfprint-device-DEBUG: 00:54:15.958: Device reported finger status change: FP_FINGER_STATUS_NEEDED 407s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.960: Finger on sensor callback 407s (process:2115): libfprint-device-DEBUG: 00:54:15.960: Device reported finger status change: FP_FINGER_STATUS_PRESENT 407s (process:2115): libfprint-SSM-DEBUG: 00:54:15.960: [egismoc] ENROLL_STATES entering state 11 407s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.960: Execute command and get response 407s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.960: Get check bytes 407s (process:2115): libfprint-SSM-DEBUG: 00:54:15.960: [egismoc] CMD_STATES entering state 0 407s (process:2115): libfprint-SSM-DEBUG: 00:54:15.961: [egismoc] CMD_STATES entering state 1 407s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.961: Command receive callback 407s (process:2115): libfprint-SSM-DEBUG: 00:54:15.961: [egismoc] CMD_STATES completed successfully 407s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.961: Read capture callback 407s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.961: Response prefix valid: yes 407s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.961: Response suffix valid: yes 407s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.961: Partial capture successful. Please touch the sensor again (20/20) 407s (process:2115): libfprint-device-DEBUG: 00:54:15.961: Device reported enroll progress, reported 20 of 20 have been completed 407s (process:2115): libfprint-SSM-DEBUG: 00:54:15.961: [egismoc] ENROLL_STATES entering state 12 407s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.961: Execute command and get response 407s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.961: Get check bytes 407s (process:2115): libfprint-SSM-DEBUG: 00:54:15.961: [egismoc] CMD_STATES entering state 0 407s (process:2115): libfprint-SSM-DEBUG: 00:54:15.962: [egismoc] CMD_STATES entering state 1 407s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.962: Command receive callback 407s (process:2115): libfprint-SSM-DEBUG: 00:54:15.962: [egismoc] CMD_STATES completed successfully 407s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.962: Task SSM next state callback 407s (process:2115): libfprint-SSM-DEBUG: 00:54:15.962: [egismoc] ENROLL_STATES entering state 13 407s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.962: New fingerprint ID: FP1-00000000-7-00000000-nobody 407s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.962: Execute command and get response 407s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.962: Get check bytes 407s (process:2115): libfprint-SSM-DEBUG: 00:54:15.962: [egismoc] CMD_STATES entering state 0 407s (process:2115): libfprint-SSM-DEBUG: 00:54:15.963: [egismoc] CMD_STATES entering state 1 407s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.963: Command receive callback 407s (process:2115): libfprint-SSM-DEBUG: 00:54:15.963: [egismoc] CMD_STATES completed successfully 407s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.963: Task SSM next state callback 407s (process:2115): libfprint-SSM-DEBUG: 00:54:15.963: [egismoc] ENROLL_STATES entering state 14 407s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.963: Execute command and get response 407s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.963: Get check bytes 407s (process:2115): libfprint-SSM-DEBUG: 00:54:15.963: [egismoc] CMD_STATES entering state 0 407s (process:2115): libfprint-SSM-DEBUG: 00:54:15.964: [egismoc] CMD_STATES entering state 1 407s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.964: Command receive callback 407s (process:2115): libfprint-SSM-DEBUG: 00:54:15.964: [egismoc] CMD_STATES completed successfully 407s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.964: Task SSM next state callback 407s (process:2115): libfprint-SSM-DEBUG: 00:54:15.964: [egismoc] ENROLL_STATES entering state 15 407s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.964: Enrollment was successful! 407s (process:2115): libfprint-device-DEBUG: 00:54:15.964: Device reported enroll completion 407s (process:2115): libfprint-device-DEBUG: 00:54:15.964: Device reported finger status change: FP_FINGER_STATUS_NONE 407s (process:2115): libfprint-device-DEBUG: 00:54:15.964: Print for finger FP_FINGER_RIGHT_INDEX enrolled 407s (process:2115): libfprint-SSM-DEBUG: 00:54:15.964: [egismoc] ENROLL_STATES completed successfully 407s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.964: Task SSM done 407s (process:2115): libfprint-device-DEBUG: 00:54:15.964: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 407s (process:2115): libfprint-device-DEBUG: 00:54:15.964: Updated temperature model after 0.09 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 407s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.965: List 407s (process:2115): libfprint-SSM-DEBUG: 00:54:15.965: [egismoc] LIST_STATES entering state 0 407s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.965: Execute command and get response 407s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.965: Get check bytes 407s (process:2115): libfprint-SSM-DEBUG: 00:54:15.965: [egismoc] CMD_STATES entering state 0 407s (process:2115): libfprint-SSM-DEBUG: 00:54:15.965: [egismoc] CMD_STATES entering state 1 407s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.966: Command receive callback 407s (process:2115): libfprint-SSM-DEBUG: 00:54:15.966: [egismoc] CMD_STATES completed successfully 407s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.966: List callback 407s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.966: Device fingerprint 1: FP1-00000000-2-00000000-nobody 407s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.966: Device fingerprint 2: FP1-00000000-7-00000000-nobody 407s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.966: Number of currently enrolled fingerprints on the device is 2 407s (process:2115): libfprint-SSM-DEBUG: 00:54:15.966: [egismoc] LIST_STATES entering state 1 407s (process:2115): libfprint-device-DEBUG: 00:54:15.966: Device reported listing completion 407s (process:2115): libfprint-SSM-DEBUG: 00:54:15.966: [egismoc] LIST_STATES completed successfully 407s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.966: Task SSM done 407s (process:2115): libfprint-device-DEBUG: 00:54:15.966: Completing action FPI_DEVICE_ACTION_LIST in idle! 407s (process:2115): libfprint-device-DEBUG: 00:54:15.966: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 407s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.966: Delete 407s (process:2115): libfprint-SSM-DEBUG: 00:54:15.966: [egismoc] DELETE_STATES entering state 0 407s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.966: Execute command and get response 407s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.966: Get check bytes 407s (process:2115): libfprint-SSM-DEBUG: 00:54:15.966: [egismoc] CMD_STATES entering state 0 407s (process:2115): libfprint-SSM-DEBUG: 00:54:15.966: [egismoc] CMD_STATES entering state 1 407s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.967: Command receive callback 407s (process:2115): libfprint-SSM-DEBUG: 00:54:15.967: [egismoc] CMD_STATES completed successfully 407s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.967: List callback 407s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.967: Device fingerprint 1: FP1-00000000-2-00000000-nobody 407s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.967: Device fingerprint 2: FP1-00000000-7-00000000-nobody 407s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.967: Number of currently enrolled fingerprints on the device is 2 407s (process:2115): libfprint-SSM-DEBUG: 00:54:15.967: [egismoc] DELETE_STATES entering state 1 407s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.967: Get delete command 407s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.967: Delete fingerprint FP1-00000000-2-00000000-nobody (FP1-00000000-2-00000000-nobody) 407s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.967: Execute command and get response 407s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.967: Get check bytes 407s (process:2115): libfprint-SSM-DEBUG: 00:54:15.967: [egismoc] CMD_STATES entering state 0 407s (process:2115): libfprint-SSM-DEBUG: 00:54:15.968: [egismoc] CMD_STATES entering state 1 407s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.968: Command receive callback 407s (process:2115): libfprint-SSM-DEBUG: 00:54:15.968: [egismoc] CMD_STATES completed successfully 407s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.968: Delete callback 407s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.968: Response prefix valid: yes 407s (process:2115): libfprint-device-DEBUG: 00:54:15.968: Device reported deletion completion 407s (process:2115): libfprint-SSM-DEBUG: 00:54:15.968: [egismoc] DELETE_STATES completed successfully 407s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.968: Task SSM done 407s (process:2115): libfprint-device-DEBUG: 00:54:15.968: Completing action FPI_DEVICE_ACTION_DELETE in idle! 407s (process:2115): libfprint-device-DEBUG: 00:54:15.968: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 407s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.968: List 407s (process:2115): libfprint-SSM-DEBUG: 00:54:15.968: [egismoc] LIST_STATES entering state 0 407s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.968: Execute command and get response 407s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.968: Get check bytes 407s (process:2115): libfprint-SSM-DEBUG: 00:54:15.968: [egismoc] CMD_STATES entering state 0 407s (process:2115): libfprint-SSM-DEBUG: 00:54:15.969: [egismoc] CMD_STATES entering state 1 407s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.970: Command receive callback 407s (process:2115): libfprint-SSM-DEBUG: 00:54:15.970: [egismoc] CMD_STATES completed successfully 407s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.970: List callback 407s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.970: Device fingerprint 1: FP1-00000000-7-00000000-nobody 407s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.970: Number of currently enrolled fingerprints on the device is 1 407s (process:2115): libfprint-SSM-DEBUG: 00:54:15.970: [egismoc] LIST_STATES entering state 1 407s (process:2115): libfprint-device-DEBUG: 00:54:15.970: Device reported listing completion 407s (process:2115): libfprint-SSM-DEBUG: 00:54:15.970: [egismoc] LIST_STATES completed successfully 407s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.970: Task SSM done 407s (process:2115): libfprint-device-DEBUG: 00:54:15.970: Completing action FPI_DEVICE_ACTION_LIST in idle! 407s (process:2115): libfprint-device-DEBUG: 00:54:15.970: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 407s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.970: Clear storage 407s (process:2115): libfprint-SSM-DEBUG: 00:54:15.970: [egismoc] DELETE_STATES entering state 0 407s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.970: Execute command and get response 407s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.970: Get check bytes 407s (process:2115): libfprint-SSM-DEBUG: 00:54:15.970: [egismoc] CMD_STATES entering state 0 407s (process:2115): libfprint-SSM-DEBUG: 00:54:15.971: [egismoc] CMD_STATES entering state 1 407s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.971: Command receive callback 407s (process:2115): libfprint-SSM-DEBUG: 00:54:15.971: [egismoc] CMD_STATES completed successfully 407s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.971: List callback 407s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.971: Device fingerprint 1: FP1-00000000-7-00000000-nobody 407s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.971: Number of currently enrolled fingerprints on the device is 1 407s (process:2115): libfprint-SSM-DEBUG: 00:54:15.971: [egismoc] DELETE_STATES entering state 1 407s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.971: Get delete command 407s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.971: Execute command and get response 407s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.971: Get check bytes 407s (process:2115): libfprint-SSM-DEBUG: 00:54:15.971: [egismoc] CMD_STATES entering state 0 407s (process:2115): libfprint-SSM-DEBUG: 00:54:15.972: [egismoc] CMD_STATES entering state 1 407s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.972: Command receive callback 407s (process:2115): libfprint-SSM-DEBUG: 00:54:15.972: [egismoc] CMD_STATES completed successfully 407s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.972: Delete callback 407s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.972: Response prefix valid: yes 407s (process:2115): libfprint-device-DEBUG: 00:54:15.972: Device reported deletion completion 407s (process:2115): libfprint-SSM-DEBUG: 00:54:15.972: [egismoc] DELETE_STATES completed successfully 407s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.972: Task SSM done 407s (process:2115): libfprint-device-DEBUG: 00:54:15.972: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 407s (process:2115): libfprint-device-DEBUG: 00:54:15.972: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 407s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.972: List 407s (process:2115): libfprint-SSM-DEBUG: 00:54:15.972: [egismoc] LIST_STATES entering state 0 407s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.973: Execute command and get response 407s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.973: Get check bytes 407s (process:2115): libfprint-SSM-DEBUG: 00:54:15.973: [egismoc] CMD_STATES entering state 0 407s (process:2115): libfprint-SSM-DEBUG: 00:54:15.973: [egismoc] CMD_STATES entering state 1 407s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.974: Command receive callback 407s (process:2115): libfprint-SSM-DEBUG: 00:54:15.974: [egismoc] CMD_STATES completed successfully 407s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.974: List callback 407s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.974: Number of currently enrolled fingerprints on the device is 0 407s (process:2115): libfprint-SSM-DEBUG: 00:54:15.974: [egismoc] LIST_STATES entering state 1 407s (process:2115): libfprint-device-DEBUG: 00:54:15.974: Device reported listing completion 407s (process:2115): libfprint-SSM-DEBUG: 00:54:15.974: [egismoc] LIST_STATES completed successfully 407s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.974: Task SSM done 407s (process:2115): libfprint-device-DEBUG: 00:54:15.974: Completing action FPI_DEVICE_ACTION_LIST in idle! 407s (process:2115): libfprint-device-DEBUG: 00:54:15.974: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 407s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.974: Closing device 407s (process:2115): libfprint-egismoc-DEBUG: 00:54:15.974: Cancel 407s (process:2115): libfprint-device-DEBUG: 00:54:15.975: Device reported close completion 407s (process:2115): libfprint-device-DEBUG: 00:54:15.975: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 407s (process:2115): libfprint-device-DEBUG: 00:54:15.975: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 407s 407s finger status: 407s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xf0cef628 (FpiDeviceEgisMoc at 0x72a810)>, 8, , None, None) 407s finger status: 407s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xf0cef628 (FpiDeviceEgisMoc at 0x72a810)>, 8, None, None, GLib.Error('The finger was not centered properly, please try again.', 'fp - device - retry - quark', 2)) 407s finger status: 407s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xf0cef628 (FpiDeviceEgisMoc at 0x72a810)>, 9, , None, None) 407s finger status: 407s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xf0cef628 (FpiDeviceEgisMoc at 0x72a810)>, 10, , None, None) 407s finger status: 407s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xf0cef628 (FpiDeviceEgisMoc at 0x72a810)>, 11, , None, None) 407s finger status: 407s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xf0cef628 (FpiDeviceEgisMoc at 0x72a810)>, 12, , None, None) 407s finger status: 407s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xf0cef628 (FpiDeviceEgisMoc at 0x72a810)>, 13, , None, None) 407s finger status: 407s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xf0cef628 (FpiDeviceEgisMoc at 0x72a810)>, 14, , None, None) 407s finger status: 407s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xf0cef628 (FpiDeviceEgisMoc at 0x72a810)>, 15, , None, None) 407s finger status: 407s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xf0cef628 (FpiDeviceEgisMoc at 0x72a810)>, 16, , None, None) 407s finger status: 407s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xf0cef628 (FpiDeviceEgisMoc at 0x72a810)>, 17, , None, None) 407s finger status: 407s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xf0cef628 (FpiDeviceEgisMoc at 0x72a810)>, 18, , None, None) 407s finger status: 407s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xf0cef628 (FpiDeviceEgisMoc at 0x72a810)>, 19, , None, None) 407s finger status: 407s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xf0cef628 (FpiDeviceEgisMoc at 0x72a810)>, 20, , None, None) 407s enroll new finger done 407s listing - device should have 2 prints 407s deleting first print 407s delete done 407s listing - device should only have second print 407s clear device storage 407s clear done 407s listing - device should be empty 407s ** (umockdev-run:2111): DEBUG: 00:54:16.004: umockdev.vala:154: Removing test bed /tmp/umockdev.3IBB22 407s (umockdev-run:2111): GLib-DEBUG: 00:54:16.012: unsetenv() is not thread-safe and should not be used after threads are created 407s PASS: libfprint-2/driver-egismoc-0587.test 407s Running test: libfprint-2/driver-focaltech_moc.test 407s ** (umockdev-run:2123): DEBUG: 00:54:16.080: umockdev.vala:127: Created udev test bed /tmp/umockdev.HAPZ12 407s ** (umockdev-run:2123): DEBUG: 00:54:16.080: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:1c.4/0000:0b:00.0/usb3/3-1/3-1.4 407s ** (umockdev-run:2123): DEBUG: 00:54:16.087: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:1c.4/0000:0b:00.0/usb3/3-1/3-1.4 (subsystem usb) 407s ** (umockdev-run:2123): DEBUG: 00:54:16.094: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.HAPZ12/dev/bus/usb/003/006 407s ** (umockdev-run:2123): DEBUG: 00:54:16.095: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:1c.4/0000:0b:00.0/usb3/3-1 407s ** (umockdev-run:2123): DEBUG: 00:54:16.101: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:1c.4/0000:0b:00.0/usb3/3-1 (subsystem usb) 407s ** (umockdev-run:2123): DEBUG: 00:54:16.107: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.HAPZ12/dev/bus/usb/003/002 407s ** (umockdev-run:2123): DEBUG: 00:54:16.108: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:1c.4/0000:0b:00.0/usb3 407s ** (umockdev-run:2123): DEBUG: 00:54:16.113: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:1c.4/0000:0b:00.0/usb3 (subsystem usb) 407s ** (umockdev-run:2123): DEBUG: 00:54:16.120: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.HAPZ12/dev/bus/usb/003/001 407s ** (umockdev-run:2123): DEBUG: 00:54:16.120: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:1c.4/0000:0b:00.0 407s ** (umockdev-run:2123): DEBUG: 00:54:16.123: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:1c.4/0000:0b:00.0 (subsystem pci) 407s ** (umockdev-run:2123): DEBUG: 00:54:16.130: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:1c.4 407s ** (umockdev-run:2123): DEBUG: 00:54:16.131: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:1c.4 (subsystem pci) 407s (process:2127): libfprint-context-DEBUG: 00:54:16.250: Initializing FpContext (libfprint version 1.94.8+tod1) 407s (process:2127): libfprint-tod-DEBUG: 00:54:16.251: Impossible to load the shared drivers dir Error opening directory “/usr/lib/arm-linux-gnueabihf/libfprint-2/tod-1”: No such file or directory 407s libusb: warning [read_sysfs_attr] attribute bConfigurationValue doesn't end with newline? 407s libusb: warning [read_sysfs_attr] attribute bConfigurationValue doesn't end with newline? 407s (process:2127): libfprint-focaltech_moc-DEBUG: 00:54:16.254: 7399824315482: ../libfprint/drivers/focaltech_moc/focaltech_moc.c:1849 407s (process:2127): libfprint-context-DEBUG: 00:54:16.254: No driver found for USB device 05E3:0608 407s (process:2127): libfprint-context-DEBUG: 00:54:16.254: No driver found for USB device 1D6B:0002 407s (process:2127): libfprint-device-DEBUG: 00:54:16.255: Device reported probe completion 407s (process:2127): libfprint-device-DEBUG: 00:54:16.255: Completing action FPI_DEVICE_ACTION_PROBE in idle! 407s (process:2127): libfprint-device-DEBUG: 00:54:16.255: Not updating temperature model, device can run continuously! 407s (process:2127): libfprint-focaltech_moc-DEBUG: 00:54:16.257: class:dc, subclass:a0, protocol:b0 407s (process:2127): libfprint-focaltech_moc-DEBUG: 00:54:16.257: bytes size:0 407s (process:2127): libfprint-focaltech_moc-DEBUG: 00:54:16.257: 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 407s (process:2127): libfprint-focaltech_moc-DEBUG: 00:54:16.257: bytes size:0 407s (process:2127): libfprint-focaltech_moc-DEBUG: 00:54:16.257: 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 407s (process:2127): libfprint-SSM-DEBUG: 00:54:16.257: [focaltech_moc] DEV_INIT_STATES entering state 0 407s (process:2127): libfprint-SSM-DEBUG: 00:54:16.257: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 407s (process:2127): libfprint-SSM-DEBUG: 00:54:16.258: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 407s (process:2127): libfprint-focaltech_moc-DEBUG: 00:54:16.258: focaltechmoc enroll_times: 10 407s (process:2127): libfprint-SSM-DEBUG: 00:54:16.258: [focaltech_moc] DEV_INIT_STATES entering state 1 407s (process:2127): libfprint-SSM-DEBUG: 00:54:16.258: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 407s (process:2127): libfprint-SSM-DEBUG: 00:54:16.258: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 407s (process:2127): libfprint-SSM-DEBUG: 00:54:16.259: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 407s (process:2127): libfprint-SSM-DEBUG: 00:54:16.260: [focaltech_moc] DEV_INIT_STATES completed successfully 407s (process:2127): libfprint-device-DEBUG: 00:54:16.260: Device reported open completion 407s (process:2127): libfprint-SSM-DEBUG: 00:54:16.260: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 407s (process:2127): libfprint-device-DEBUG: 00:54:16.260: Completing action FPI_DEVICE_ACTION_OPEN in idle! 407s (process:2127): libfprint-device-DEBUG: 00:54:16.260: Not updating temperature model, device can run continuously! 407s (process:2127): libfprint-device-DEBUG: 00:54:16.261: Not updating temperature model, device can run continuously! 407s (process:2127): libfprint-SSM-DEBUG: 00:54:16.261: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 0 407s (process:2127): libfprint-SSM-DEBUG: 00:54:16.261: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 407s (process:2127): libfprint-SSM-DEBUG: 00:54:16.262: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 407s (process:2127): libfprint-SSM-DEBUG: 00:54:16.263: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 1 407s (process:2127): libfprint-SSM-DEBUG: 00:54:16.263: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 407s (process:2127): libfprint-SSM-DEBUG: 00:54:16.264: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 407s (process:2127): libfprint-SSM-DEBUG: 00:54:16.264: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 407s (process:2127): libfprint-SSM-DEBUG: 00:54:16.265: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 2 407s (process:2127): libfprint-SSM-DEBUG: 00:54:16.265: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 407s (process:2127): libfprint-SSM-DEBUG: 00:54:16.265: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 407s (process:2127): libfprint-SSM-DEBUG: 00:54:16.266: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 407s (process:2127): libfprint-SSM-DEBUG: 00:54:16.266: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 3 407s (process:2127): libfprint-SSM-DEBUG: 00:54:16.266: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 407s (process:2127): libfprint-SSM-DEBUG: 00:54:16.267: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 407s (process:2127): libfprint-SSM-DEBUG: 00:54:16.267: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 407s (process:2127): libfprint-focaltech_moc-DEBUG: 00:54:16.267: focaltechmoc user id: FP1-00000000-0-00000000-nobody 407s (process:2127): libfprint-SSM-DEBUG: 00:54:16.267: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 407s (process:2127): libfprint-SSM-DEBUG: 00:54:16.267: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 407s (process:2127): libfprint-SSM-DEBUG: 00:54:16.268: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 407s (process:2127): libfprint-SSM-DEBUG: 00:54:16.268: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 407s (process:2127): libfprint-SSM-DEBUG: 00:54:16.269: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5 407s (process:2127): libfprint-SSM-DEBUG: 00:54:16.269: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 407s (process:2127): libfprint-SSM-DEBUG: 00:54:16.320: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 407s (process:2127): libfprint-SSM-DEBUG: 00:54:16.320: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 407s (process:2127): libfprint-SSM-DEBUG: 00:54:16.320: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 407s (process:2127): libfprint-SSM-DEBUG: 00:54:16.322: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5 407s (process:2127): libfprint-SSM-DEBUG: 00:54:16.322: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 407s (process:2127): libfprint-SSM-DEBUG: 00:54:16.372: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 407s (process:2127): libfprint-SSM-DEBUG: 00:54:16.372: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 407s (process:2127): libfprint-SSM-DEBUG: 00:54:16.373: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 407s (process:2127): libfprint-SSM-DEBUG: 00:54:16.373: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5 407s (process:2127): libfprint-SSM-DEBUG: 00:54:16.373: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 407s (process:2127): libfprint-SSM-DEBUG: 00:54:16.423: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 407s (process:2127): libfprint-SSM-DEBUG: 00:54:16.423: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 407s (process:2127): libfprint-SSM-DEBUG: 00:54:16.424: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 407s (process:2127): libfprint-SSM-DEBUG: 00:54:16.424: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5 407s (process:2127): libfprint-SSM-DEBUG: 00:54:16.425: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 407s (process:2127): libfprint-SSM-DEBUG: 00:54:16.475: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 407s (process:2127): libfprint-SSM-DEBUG: 00:54:16.475: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 407s (process:2127): libfprint-SSM-DEBUG: 00:54:16.475: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 407s (process:2127): libfprint-SSM-DEBUG: 00:54:16.476: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5 407s (process:2127): libfprint-SSM-DEBUG: 00:54:16.476: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 407s (process:2127): libfprint-SSM-DEBUG: 00:54:16.526: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 407s (process:2127): libfprint-SSM-DEBUG: 00:54:16.526: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 407s (process:2127): libfprint-SSM-DEBUG: 00:54:16.527: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 407s (process:2127): libfprint-SSM-DEBUG: 00:54:16.528: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5 407s (process:2127): libfprint-SSM-DEBUG: 00:54:16.528: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 407s (process:2127): libfprint-SSM-DEBUG: 00:54:16.578: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 407s (process:2127): libfprint-SSM-DEBUG: 00:54:16.578: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 407s (process:2127): libfprint-SSM-DEBUG: 00:54:16.581: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 407s (process:2127): libfprint-SSM-DEBUG: 00:54:16.582: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 6 407s (process:2127): libfprint-SSM-DEBUG: 00:54:16.582: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 407s (process:2127): libfprint-SSM-DEBUG: 00:54:16.582: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 407s (process:2127): libfprint-SSM-DEBUG: 00:54:16.582: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 407s (process:2127): libfprint-device-DEBUG: 00:54:16.583: Device reported enroll progress, reported 1 of 10 have been completed 407s (process:2127): libfprint-focaltech_moc-DEBUG: 00:54:16.583: focaltechmoc remain: 9 407s (process:2127): libfprint-SSM-DEBUG: 00:54:16.583: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 407s (process:2127): libfprint-SSM-DEBUG: 00:54:16.583: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 407s (process:2127): libfprint-SSM-DEBUG: 00:54:16.583: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 407s (process:2127): libfprint-SSM-DEBUG: 00:54:16.584: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 407s (process:2127): libfprint-SSM-DEBUG: 00:54:16.585: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5 407s (process:2127): libfprint-SSM-DEBUG: 00:54:16.585: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 407s (process:2127): libfprint-SSM-DEBUG: 00:54:16.636: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 407s (process:2127): libfprint-SSM-DEBUG: 00:54:16.636: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 407s (process:2127): libfprint-SSM-DEBUG: 00:54:16.637: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 407s (process:2127): libfprint-SSM-DEBUG: 00:54:16.637: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5 407s (process:2127): libfprint-SSM-DEBUG: 00:54:16.637: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 407s (process:2127): libfprint-SSM-DEBUG: 00:54:16.687: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 407s (process:2127): libfprint-SSM-DEBUG: 00:54:16.688: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 407s (process:2127): libfprint-SSM-DEBUG: 00:54:16.688: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 407s (process:2127): libfprint-SSM-DEBUG: 00:54:16.689: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5 407s (process:2127): libfprint-SSM-DEBUG: 00:54:16.689: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 407s (process:2127): libfprint-SSM-DEBUG: 00:54:16.740: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 407s (process:2127): libfprint-SSM-DEBUG: 00:54:16.740: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 407s (process:2127): libfprint-SSM-DEBUG: 00:54:16.741: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 407s (process:2127): libfprint-SSM-DEBUG: 00:54:16.741: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5 407s (process:2127): libfprint-SSM-DEBUG: 00:54:16.741: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 407s (process:2127): libfprint-SSM-DEBUG: 00:54:16.792: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 407s (process:2127): libfprint-SSM-DEBUG: 00:54:16.792: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 407s (process:2127): libfprint-SSM-DEBUG: 00:54:16.793: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 407s (process:2127): libfprint-SSM-DEBUG: 00:54:16.794: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5 407s (process:2127): libfprint-SSM-DEBUG: 00:54:16.794: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 407s (process:2127): libfprint-SSM-DEBUG: 00:54:16.844: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 407s (process:2127): libfprint-SSM-DEBUG: 00:54:16.844: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 407s (process:2127): libfprint-SSM-DEBUG: 00:54:16.845: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 407s (process:2127): libfprint-SSM-DEBUG: 00:54:16.845: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 6 407s (process:2127): libfprint-SSM-DEBUG: 00:54:16.846: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 407s (process:2127): libfprint-SSM-DEBUG: 00:54:16.846: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 407s (process:2127): libfprint-SSM-DEBUG: 00:54:16.847: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 407s (process:2127): libfprint-device-DEBUG: 00:54:16.847: Device reported enroll progress, reported 2 of 10 have been completed 407s (process:2127): libfprint-focaltech_moc-DEBUG: 00:54:16.848: focaltechmoc remain: 8 407s (process:2127): libfprint-SSM-DEBUG: 00:54:16.848: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 407s (process:2127): libfprint-SSM-DEBUG: 00:54:16.848: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 407s (process:2127): libfprint-SSM-DEBUG: 00:54:16.848: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 407s (process:2127): libfprint-SSM-DEBUG: 00:54:16.848: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 407s (process:2127): libfprint-SSM-DEBUG: 00:54:16.849: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5 407s (process:2127): libfprint-SSM-DEBUG: 00:54:16.849: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 407s Executing: libfprint-2/driver-focaltech_moc.test 407s (process:2127): libfprint-SSM-DEBUG: 00:54:16.900: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 407s (process:2127): libfprint-SSM-DEBUG: 00:54:16.900: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 407s (process:2127): libfprint-SSM-DEBUG: 00:54:16.901: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 407s (process:2127): libfprint-SSM-DEBUG: 00:54:16.902: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 6 407s (process:2127): libfprint-SSM-DEBUG: 00:54:16.902: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 407s (process:2127): libfprint-SSM-DEBUG: 00:54:16.902: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 407s (process:2127): libfprint-SSM-DEBUG: 00:54:16.902: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 407s (process:2127): libfprint-device-DEBUG: 00:54:16.903: Device reported enroll progress, reported 3 of 10 have been completed 407s (process:2127): libfprint-focaltech_moc-DEBUG: 00:54:16.903: focaltechmoc remain: 7 407s (process:2127): libfprint-SSM-DEBUG: 00:54:16.903: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 407s (process:2127): libfprint-SSM-DEBUG: 00:54:16.903: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 407s (process:2127): libfprint-SSM-DEBUG: 00:54:16.904: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 407s (process:2127): libfprint-SSM-DEBUG: 00:54:16.904: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 407s (process:2127): libfprint-SSM-DEBUG: 00:54:16.905: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5 407s (process:2127): libfprint-SSM-DEBUG: 00:54:16.905: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 408s (process:2127): libfprint-SSM-DEBUG: 00:54:16.955: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 408s (process:2127): libfprint-SSM-DEBUG: 00:54:16.956: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 408s (process:2127): libfprint-SSM-DEBUG: 00:54:16.957: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 408s (process:2127): libfprint-SSM-DEBUG: 00:54:16.957: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5 408s (process:2127): libfprint-SSM-DEBUG: 00:54:16.957: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 408s (process:2127): libfprint-SSM-DEBUG: 00:54:17.008: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 408s (process:2127): libfprint-SSM-DEBUG: 00:54:17.008: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 408s (process:2127): libfprint-SSM-DEBUG: 00:54:17.010: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 408s (process:2127): libfprint-SSM-DEBUG: 00:54:17.011: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5 408s (process:2127): libfprint-SSM-DEBUG: 00:54:17.011: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 408s (process:2127): libfprint-SSM-DEBUG: 00:54:17.061: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 408s (process:2127): libfprint-SSM-DEBUG: 00:54:17.061: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 408s (process:2127): libfprint-SSM-DEBUG: 00:54:17.062: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 408s (process:2127): libfprint-SSM-DEBUG: 00:54:17.063: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5 408s (process:2127): libfprint-SSM-DEBUG: 00:54:17.063: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 408s (process:2127): libfprint-SSM-DEBUG: 00:54:17.113: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 408s (process:2127): libfprint-SSM-DEBUG: 00:54:17.113: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 408s (process:2127): libfprint-SSM-DEBUG: 00:54:17.114: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 408s (process:2127): libfprint-SSM-DEBUG: 00:54:17.114: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5 408s (process:2127): libfprint-SSM-DEBUG: 00:54:17.114: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 408s (process:2127): libfprint-SSM-DEBUG: 00:54:17.164: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 408s (process:2127): libfprint-SSM-DEBUG: 00:54:17.164: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 408s (process:2127): libfprint-SSM-DEBUG: 00:54:17.165: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 408s (process:2127): libfprint-SSM-DEBUG: 00:54:17.165: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 6 408s (process:2127): libfprint-SSM-DEBUG: 00:54:17.165: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 408s (process:2127): libfprint-SSM-DEBUG: 00:54:17.166: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 408s (process:2127): libfprint-SSM-DEBUG: 00:54:17.166: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 408s (process:2127): libfprint-device-DEBUG: 00:54:17.166: Device reported enroll progress, reported 4 of 10 have been completed 408s (process:2127): libfprint-focaltech_moc-DEBUG: 00:54:17.167: focaltechmoc remain: 6 408s (process:2127): libfprint-SSM-DEBUG: 00:54:17.167: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 408s (process:2127): libfprint-SSM-DEBUG: 00:54:17.167: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 408s (process:2127): libfprint-SSM-DEBUG: 00:54:17.167: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 408s (process:2127): libfprint-SSM-DEBUG: 00:54:17.167: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 408s (process:2127): libfprint-SSM-DEBUG: 00:54:17.168: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5 408s (process:2127): libfprint-SSM-DEBUG: 00:54:17.168: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 408s (process:2127): libfprint-SSM-DEBUG: 00:54:17.218: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 408s (process:2127): libfprint-SSM-DEBUG: 00:54:17.218: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 408s (process:2127): libfprint-SSM-DEBUG: 00:54:17.218: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 408s (process:2127): libfprint-SSM-DEBUG: 00:54:17.219: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5 408s (process:2127): libfprint-SSM-DEBUG: 00:54:17.219: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 408s (process:2127): libfprint-SSM-DEBUG: 00:54:17.269: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 408s (process:2127): libfprint-SSM-DEBUG: 00:54:17.269: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 408s (process:2127): libfprint-SSM-DEBUG: 00:54:17.270: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 408s (process:2127): libfprint-SSM-DEBUG: 00:54:17.270: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5 408s (process:2127): libfprint-SSM-DEBUG: 00:54:17.270: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 408s (process:2127): libfprint-SSM-DEBUG: 00:54:17.320: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 408s (process:2127): libfprint-SSM-DEBUG: 00:54:17.321: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 408s (process:2127): libfprint-SSM-DEBUG: 00:54:17.321: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 408s (process:2127): libfprint-SSM-DEBUG: 00:54:17.322: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 6 408s (process:2127): libfprint-SSM-DEBUG: 00:54:17.322: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 408s (process:2127): libfprint-SSM-DEBUG: 00:54:17.322: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 408s (process:2127): libfprint-SSM-DEBUG: 00:54:17.322: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 408s (process:2127): libfprint-device-DEBUG: 00:54:17.323: Device reported enroll progress, reported 5 of 10 have been completed 408s (process:2127): libfprint-focaltech_moc-DEBUG: 00:54:17.323: focaltechmoc remain: 5 408s (process:2127): libfprint-SSM-DEBUG: 00:54:17.323: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 408s (process:2127): libfprint-SSM-DEBUG: 00:54:17.323: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 408s (process:2127): libfprint-SSM-DEBUG: 00:54:17.323: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 408s (process:2127): libfprint-SSM-DEBUG: 00:54:17.323: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 408s (process:2127): libfprint-SSM-DEBUG: 00:54:17.324: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5 408s (process:2127): libfprint-SSM-DEBUG: 00:54:17.324: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 408s (process:2127): libfprint-SSM-DEBUG: 00:54:17.374: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 408s (process:2127): libfprint-SSM-DEBUG: 00:54:17.374: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 408s (process:2127): libfprint-SSM-DEBUG: 00:54:17.374: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 408s (process:2127): libfprint-SSM-DEBUG: 00:54:17.375: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5 408s (process:2127): libfprint-SSM-DEBUG: 00:54:17.375: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 408s (process:2127): libfprint-SSM-DEBUG: 00:54:17.425: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 408s (process:2127): libfprint-SSM-DEBUG: 00:54:17.425: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 408s (process:2127): libfprint-SSM-DEBUG: 00:54:17.426: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 408s (process:2127): libfprint-SSM-DEBUG: 00:54:17.427: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5 408s (process:2127): libfprint-SSM-DEBUG: 00:54:17.427: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 408s (process:2127): libfprint-SSM-DEBUG: 00:54:17.477: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 408s (process:2127): libfprint-SSM-DEBUG: 00:54:17.477: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 408s (process:2127): libfprint-SSM-DEBUG: 00:54:17.478: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 408s (process:2127): libfprint-SSM-DEBUG: 00:54:17.478: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5 408s (process:2127): libfprint-SSM-DEBUG: 00:54:17.479: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 408s (process:2127): libfprint-SSM-DEBUG: 00:54:17.529: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 408s (process:2127): libfprint-SSM-DEBUG: 00:54:17.529: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 408s (process:2127): libfprint-SSM-DEBUG: 00:54:17.529: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 408s (process:2127): libfprint-SSM-DEBUG: 00:54:17.530: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 6 408s (process:2127): libfprint-SSM-DEBUG: 00:54:17.530: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 408s (process:2127): libfprint-SSM-DEBUG: 00:54:17.531: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 408s (process:2127): libfprint-SSM-DEBUG: 00:54:17.531: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 408s (process:2127): libfprint-device-DEBUG: 00:54:17.531: Device reported enroll progress, reported 6 of 10 have been completed 408s (process:2127): libfprint-focaltech_moc-DEBUG: 00:54:17.532: focaltechmoc remain: 4 408s (process:2127): libfprint-SSM-DEBUG: 00:54:17.532: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 408s (process:2127): libfprint-SSM-DEBUG: 00:54:17.532: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 408s (process:2127): libfprint-SSM-DEBUG: 00:54:17.532: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 408s (process:2127): libfprint-SSM-DEBUG: 00:54:17.532: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 408s (process:2127): libfprint-SSM-DEBUG: 00:54:17.533: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 6 408s (process:2127): libfprint-SSM-DEBUG: 00:54:17.533: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 408s (process:2127): libfprint-SSM-DEBUG: 00:54:17.533: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 408s (process:2127): libfprint-SSM-DEBUG: 00:54:17.533: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 408s (process:2127): libfprint-device-DEBUG: 00:54:17.534: Device reported enroll progress, reported 6 of 10 have been completed 408s (process:2127): libfprint-SSM-DEBUG: 00:54:17.534: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 408s (process:2127): libfprint-SSM-DEBUG: 00:54:17.534: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 408s (process:2127): libfprint-SSM-DEBUG: 00:54:17.535: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 408s (process:2127): libfprint-SSM-DEBUG: 00:54:17.535: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 408s (process:2127): libfprint-SSM-DEBUG: 00:54:17.536: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5 408s (process:2127): libfprint-SSM-DEBUG: 00:54:17.536: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 408s (process:2127): libfprint-SSM-DEBUG: 00:54:17.586: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 408s (process:2127): libfprint-SSM-DEBUG: 00:54:17.586: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 408s (process:2127): libfprint-SSM-DEBUG: 00:54:17.587: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 408s (process:2127): libfprint-SSM-DEBUG: 00:54:17.588: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5 408s (process:2127): libfprint-SSM-DEBUG: 00:54:17.588: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 408s (process:2127): libfprint-SSM-DEBUG: 00:54:17.638: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 408s (process:2127): libfprint-SSM-DEBUG: 00:54:17.638: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 408s (process:2127): libfprint-SSM-DEBUG: 00:54:17.639: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 408s (process:2127): libfprint-SSM-DEBUG: 00:54:17.639: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5 408s (process:2127): libfprint-SSM-DEBUG: 00:54:17.639: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 408s (process:2127): libfprint-SSM-DEBUG: 00:54:17.690: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 408s (process:2127): libfprint-SSM-DEBUG: 00:54:17.690: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 408s (process:2127): libfprint-SSM-DEBUG: 00:54:17.690: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 408s (process:2127): libfprint-SSM-DEBUG: 00:54:17.691: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5 408s (process:2127): libfprint-SSM-DEBUG: 00:54:17.691: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 408s (process:2127): libfprint-SSM-DEBUG: 00:54:17.741: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 408s (process:2127): libfprint-SSM-DEBUG: 00:54:17.741: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 408s (process:2127): libfprint-SSM-DEBUG: 00:54:17.742: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 408s (process:2127): libfprint-SSM-DEBUG: 00:54:17.742: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 6 408s (process:2127): libfprint-SSM-DEBUG: 00:54:17.743: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 408s (process:2127): libfprint-SSM-DEBUG: 00:54:17.743: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 408s (process:2127): libfprint-SSM-DEBUG: 00:54:17.743: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 408s (process:2127): libfprint-device-DEBUG: 00:54:17.744: Device reported enroll progress, reported 7 of 10 have been completed 408s (process:2127): libfprint-focaltech_moc-DEBUG: 00:54:17.744: focaltechmoc remain: 3 408s (process:2127): libfprint-SSM-DEBUG: 00:54:17.744: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 408s (process:2127): libfprint-SSM-DEBUG: 00:54:17.744: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 408s (process:2127): libfprint-SSM-DEBUG: 00:54:17.744: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 408s (process:2127): libfprint-SSM-DEBUG: 00:54:17.744: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 408s (process:2127): libfprint-SSM-DEBUG: 00:54:17.745: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5 408s (process:2127): libfprint-SSM-DEBUG: 00:54:17.745: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 408s (process:2127): libfprint-SSM-DEBUG: 00:54:17.795: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 408s (process:2127): libfprint-SSM-DEBUG: 00:54:17.795: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 408s (process:2127): libfprint-SSM-DEBUG: 00:54:17.796: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 408s (process:2127): libfprint-SSM-DEBUG: 00:54:17.797: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5 408s (process:2127): libfprint-SSM-DEBUG: 00:54:17.797: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 408s (process:2127): libfprint-SSM-DEBUG: 00:54:17.847: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 408s (process:2127): libfprint-SSM-DEBUG: 00:54:17.847: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 408s (process:2127): libfprint-SSM-DEBUG: 00:54:17.848: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 408s (process:2127): libfprint-SSM-DEBUG: 00:54:17.848: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 6 408s (process:2127): libfprint-SSM-DEBUG: 00:54:17.848: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 408s (process:2127): libfprint-SSM-DEBUG: 00:54:17.849: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 408s (process:2127): libfprint-SSM-DEBUG: 00:54:17.849: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 408s (process:2127): libfprint-device-DEBUG: 00:54:17.850: Device reported enroll progress, reported 8 of 10 have been completed 408s (process:2127): libfprint-focaltech_moc-DEBUG: 00:54:17.850: focaltechmoc remain: 2 408s (process:2127): libfprint-SSM-DEBUG: 00:54:17.850: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 408s (process:2127): libfprint-SSM-DEBUG: 00:54:17.850: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 408s (process:2127): libfprint-SSM-DEBUG: 00:54:17.850: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 408s (process:2127): libfprint-SSM-DEBUG: 00:54:17.850: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 408s (process:2127): libfprint-SSM-DEBUG: 00:54:17.851: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5 408s (process:2127): libfprint-SSM-DEBUG: 00:54:17.851: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 408s (process:2127): libfprint-SSM-DEBUG: 00:54:17.901: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 408s (process:2127): libfprint-SSM-DEBUG: 00:54:17.901: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 408s (process:2127): libfprint-SSM-DEBUG: 00:54:17.902: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 408s (process:2127): libfprint-SSM-DEBUG: 00:54:17.902: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 6 408s (process:2127): libfprint-SSM-DEBUG: 00:54:17.902: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 408s (process:2127): libfprint-SSM-DEBUG: 00:54:17.903: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 408s (process:2127): libfprint-SSM-DEBUG: 00:54:17.903: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 408s (process:2127): libfprint-device-DEBUG: 00:54:17.903: Device reported enroll progress, reported 9 of 10 have been completed 408s (process:2127): libfprint-focaltech_moc-DEBUG: 00:54:17.903: focaltechmoc remain: 1 408s (process:2127): libfprint-SSM-DEBUG: 00:54:17.903: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 408s (process:2127): libfprint-SSM-DEBUG: 00:54:17.903: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 408s (process:2127): libfprint-SSM-DEBUG: 00:54:17.904: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 408s (process:2127): libfprint-SSM-DEBUG: 00:54:17.904: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 408s (process:2127): libfprint-SSM-DEBUG: 00:54:17.904: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5 408s (process:2127): libfprint-SSM-DEBUG: 00:54:17.904: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 408s (process:2127): libfprint-SSM-DEBUG: 00:54:17.954: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 408s (process:2127): libfprint-SSM-DEBUG: 00:54:17.954: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 408s (process:2127): libfprint-SSM-DEBUG: 00:54:17.955: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 408s (process:2127): libfprint-SSM-DEBUG: 00:54:17.956: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 6 408s (process:2127): libfprint-SSM-DEBUG: 00:54:17.956: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 408s (process:2127): libfprint-SSM-DEBUG: 00:54:17.956: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 408s (process:2127): libfprint-SSM-DEBUG: 00:54:17.956: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 408s (process:2127): libfprint-device-DEBUG: 00:54:17.957: Device reported enroll progress, reported 10 of 10 have been completed 408s (process:2127): libfprint-focaltech_moc-DEBUG: 00:54:17.957: focaltechmoc remain: 0 408s (process:2127): libfprint-SSM-DEBUG: 00:54:17.957: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 7 408s (process:2127): libfprint-SSM-DEBUG: 00:54:17.957: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 408s (process:2127): libfprint-SSM-DEBUG: 00:54:17.957: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 408s (process:2127): libfprint-SSM-DEBUG: 00:54:17.957: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 409s (process:2127): libfprint-SSM-DEBUG: 00:54:17.958: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 8 409s (process:2127): libfprint-SSM-DEBUG: 00:54:17.958: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 409s (process:2127): libfprint-SSM-DEBUG: 00:54:17.958: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 409s (process:2127): libfprint-SSM-DEBUG: 00:54:17.958: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 409s (process:2127): libfprint-focaltech_moc-DEBUG: 00:54:17.959: focaltech_moc_commit_cb success 409s (process:2127): libfprint-focaltech_moc-DEBUG: 00:54:17.959: Enrollment was successful! 409s (process:2127): libfprint-device-DEBUG: 00:54:17.959: Device reported enroll completion 409s (process:2127): libfprint-device-DEBUG: 00:54:17.959: Print for finger FP_FINGER_UNKNOWN enrolled 409s (process:2127): libfprint-SSM-DEBUG: 00:54:17.959: [focaltech_moc] MOC_ENROLL_NUM_STATES completed successfully 409s (process:2127): libfprint-SSM-DEBUG: 00:54:17.959: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 409s (process:2127): libfprint-device-DEBUG: 00:54:17.959: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 409s (process:2127): libfprint-device-DEBUG: 00:54:17.959: Not updating temperature model, device can run continuously! 409s (process:2127): libfprint-SSM-DEBUG: 00:54:17.959: [focaltech_moc] MOC_LIST_NUM_STATES entering state 0 409s (process:2127): libfprint-SSM-DEBUG: 00:54:17.959: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 409s (process:2127): libfprint-SSM-DEBUG: 00:54:17.960: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 409s (process:2127): libfprint-SSM-DEBUG: 00:54:17.960: [focaltech_moc] MOC_LIST_NUM_STATES entering state 1 409s (process:2127): libfprint-SSM-DEBUG: 00:54:17.960: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 409s (process:2127): libfprint-SSM-DEBUG: 00:54:17.961: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 409s (process:2127): libfprint-SSM-DEBUG: 00:54:17.961: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 409s (process:2127): libfprint-focaltech_moc-DEBUG: 00:54:17.962: focaltechmoc add slot: 0 409s (process:2127): libfprint-focaltech_moc-DEBUG: 00:54:17.962: FP1-00000000-0-00000000-nobody 409s (process:2127): libfprint-SSM-DEBUG: 00:54:17.962: [focaltech_moc] MOC_LIST_NUM_STATES entering state 2 409s (process:2127): libfprint-device-DEBUG: 00:54:17.962: Device reported listing completion 409s (process:2127): libfprint-SSM-DEBUG: 00:54:17.962: [focaltech_moc] MOC_LIST_NUM_STATES completed successfully 409s (process:2127): libfprint-SSM-DEBUG: 00:54:17.962: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 409s (process:2127): libfprint-device-DEBUG: 00:54:17.962: Completing action FPI_DEVICE_ACTION_LIST in idle! 409s (process:2127): libfprint-device-DEBUG: 00:54:17.962: Not updating temperature model, device can run continuously! 409s (process:2127): libfprint-device-DEBUG: 00:54:17.962: Not updating temperature model, device can run continuously! 409s (process:2127): libfprint-SSM-DEBUG: 00:54:17.962: [focaltech_moc] MOC_IDENTIFY_NUM_STATES entering state 0 409s (process:2127): libfprint-SSM-DEBUG: 00:54:17.962: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 409s (process:2127): libfprint-SSM-DEBUG: 00:54:17.963: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 409s (process:2127): libfprint-SSM-DEBUG: 00:54:17.963: [focaltech_moc] MOC_IDENTIFY_NUM_STATES entering state 1 409s (process:2127): libfprint-SSM-DEBUG: 00:54:17.963: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 409s (process:2127): libfprint-SSM-DEBUG: 00:54:17.963: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 409s (process:2127): libfprint-SSM-DEBUG: 00:54:17.964: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 409s (process:2127): libfprint-SSM-DEBUG: 00:54:17.964: [focaltech_moc] MOC_IDENTIFY_NUM_STATES entering state 2 409s (process:2127): libfprint-SSM-DEBUG: 00:54:17.964: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 409s (process:2127): libfprint-SSM-DEBUG: 00:54:18.014: [focaltech_moc] MOC_IDENTIFY_NUM_STATES entering state 1 409s (process:2127): libfprint-SSM-DEBUG: 00:54:18.014: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 409s (process:2127): libfprint-SSM-DEBUG: 00:54:18.015: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 409s (process:2127): libfprint-SSM-DEBUG: 00:54:18.015: [focaltech_moc] MOC_IDENTIFY_NUM_STATES entering state 2 409s (process:2127): libfprint-SSM-DEBUG: 00:54:18.015: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 409s (process:2127): libfprint-SSM-DEBUG: 00:54:18.066: [focaltech_moc] MOC_IDENTIFY_NUM_STATES entering state 1 409s (process:2127): libfprint-SSM-DEBUG: 00:54:18.066: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 409s (process:2127): libfprint-SSM-DEBUG: 00:54:18.066: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 409s (process:2127): libfprint-SSM-DEBUG: 00:54:18.067: [focaltech_moc] MOC_IDENTIFY_NUM_STATES entering state 2 409s (process:2127): libfprint-SSM-DEBUG: 00:54:18.067: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 409s (process:2127): libfprint-SSM-DEBUG: 00:54:18.117: [focaltech_moc] MOC_IDENTIFY_NUM_STATES entering state 1 409s (process:2127): libfprint-SSM-DEBUG: 00:54:18.117: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 409s (process:2127): libfprint-SSM-DEBUG: 00:54:18.117: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 409s (process:2127): libfprint-SSM-DEBUG: 00:54:18.118: [focaltech_moc] MOC_IDENTIFY_NUM_STATES entering state 2 409s (process:2127): libfprint-SSM-DEBUG: 00:54:18.118: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 409s (process:2127): libfprint-SSM-DEBUG: 00:54:18.168: [focaltech_moc] MOC_IDENTIFY_NUM_STATES entering state 1 409s (process:2127): libfprint-SSM-DEBUG: 00:54:18.168: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 409s (process:2127): libfprint-SSM-DEBUG: 00:54:18.169: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 409s (process:2127): libfprint-SSM-DEBUG: 00:54:18.169: [focaltech_moc] MOC_IDENTIFY_NUM_STATES entering state 3 409s (process:2127): libfprint-SSM-DEBUG: 00:54:18.169: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 409s (process:2127): libfprint-SSM-DEBUG: 00:54:18.170: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 409s (process:2127): libfprint-SSM-DEBUG: 00:54:18.170: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 409s (process:2127): libfprint-SSM-DEBUG: 00:54:18.170: [focaltech_moc] MOC_IDENTIFY_NUM_STATES entering state 4 409s (process:2127): libfprint-SSM-DEBUG: 00:54:18.170: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 409s (process:2127): libfprint-SSM-DEBUG: 00:54:18.171: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 409s (process:2127): libfprint-SSM-DEBUG: 00:54:18.171: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 409s (process:2127): libfprint-device-DEBUG: 00:54:18.172: Device reported verify result 409s (process:2127): libfprint-device-DEBUG: 00:54:18.172: Device reported verify completion 409s (process:2127): libfprint-SSM-DEBUG: 00:54:18.172: [focaltech_moc] MOC_IDENTIFY_NUM_STATES completed successfully 409s (process:2127): libfprint-SSM-DEBUG: 00:54:18.172: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 409s (process:2127): libfprint-device-DEBUG: 00:54:18.172: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 409s (process:2127): libfprint-device-DEBUG: 00:54:18.172: Not updating temperature model, device can run continuously! 409s (process:2127): libfprint-device-DEBUG: 00:54:18.172: Not updating temperature model, device can run continuously! 409s (process:2127): libfprint-SSM-DEBUG: 00:54:18.172: [focaltech_moc] MOC_IDENTIFY_NUM_STATES entering state 0 409s (process:2127): libfprint-SSM-DEBUG: 00:54:18.172: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 409s (process:2127): libfprint-SSM-DEBUG: 00:54:18.173: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 409s (process:2127): libfprint-SSM-DEBUG: 00:54:18.173: [focaltech_moc] MOC_IDENTIFY_NUM_STATES entering state 1 409s (process:2127): libfprint-SSM-DEBUG: 00:54:18.173: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 409s (process:2127): libfprint-SSM-DEBUG: 00:54:18.174: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 409s (process:2127): libfprint-SSM-DEBUG: 00:54:18.174: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 409s (process:2127): libfprint-SSM-DEBUG: 00:54:18.174: [focaltech_moc] MOC_IDENTIFY_NUM_STATES entering state 2 409s (process:2127): libfprint-SSM-DEBUG: 00:54:18.174: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 409s (process:2127): libfprint-SSM-DEBUG: 00:54:18.224: [focaltech_moc] MOC_IDENTIFY_NUM_STATES entering state 1 409s (process:2127): libfprint-SSM-DEBUG: 00:54:18.225: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 409s (process:2127): libfprint-SSM-DEBUG: 00:54:18.225: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 409s (process:2127): libfprint-SSM-DEBUG: 00:54:18.226: [focaltech_moc] MOC_IDENTIFY_NUM_STATES entering state 2 409s (process:2127): libfprint-SSM-DEBUG: 00:54:18.226: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 409s (process:2127): libfprint-SSM-DEBUG: 00:54:18.276: [focaltech_moc] MOC_IDENTIFY_NUM_STATES entering state 1 409s (process:2127): libfprint-SSM-DEBUG: 00:54:18.276: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 409s (process:2127): libfprint-SSM-DEBUG: 00:54:18.276: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 409s (process:2127): libfprint-SSM-DEBUG: 00:54:18.277: [focaltech_moc] MOC_IDENTIFY_NUM_STATES entering state 3 409s (process:2127): libfprint-SSM-DEBUG: 00:54:18.277: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 409s (process:2127): libfprint-SSM-DEBUG: 00:54:18.277: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 409s (process:2127): libfprint-SSM-DEBUG: 00:54:18.278: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 409s (process:2127): libfprint-SSM-DEBUG: 00:54:18.278: [focaltech_moc] MOC_IDENTIFY_NUM_STATES entering state 4 409s (process:2127): libfprint-SSM-DEBUG: 00:54:18.278: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 409s (process:2127): libfprint-SSM-DEBUG: 00:54:18.279: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 409s (process:2127): libfprint-SSM-DEBUG: 00:54:18.279: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 409s (process:2127): libfprint-device-DEBUG: 00:54:18.279: Device reported identify result 409s (process:2127): libfprint-device-DEBUG: 00:54:18.279: Device reported identify completion 409s (process:2127): libfprint-SSM-DEBUG: 00:54:18.279: [focaltech_moc] MOC_IDENTIFY_NUM_STATES completed successfully 409s (process:2127): libfprint-SSM-DEBUG: 00:54:18.279: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 409s (process:2127): libfprint-device-DEBUG: 00:54:18.280: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 409s (process:2127): libfprint-device-DEBUG: 00:54:18.280: Not updating temperature model, device can run continuously! 409s (process:2127): libfprint-SSM-DEBUG: 00:54:18.280: [focaltech_moc] MOC_DELETE_NUM_STATES entering state 0 409s (process:2127): libfprint-SSM-DEBUG: 00:54:18.280: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 409s (process:2127): libfprint-SSM-DEBUG: 00:54:18.281: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 409s (process:2127): libfprint-SSM-DEBUG: 00:54:18.281: [focaltech_moc] MOC_DELETE_NUM_STATES entering state 1 409s (process:2127): libfprint-SSM-DEBUG: 00:54:18.281: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 409s (process:2127): libfprint-SSM-DEBUG: 00:54:18.282: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 409s (process:2127): libfprint-SSM-DEBUG: 00:54:18.282: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 409s (process:2127): libfprint-focaltech_moc-DEBUG: 00:54:18.282: focaltechmoc add slot: 0 409s (process:2127): libfprint-focaltech_moc-DEBUG: 00:54:18.282: FP1-00000000-0-00000000-nobody 409s (process:2127): libfprint-SSM-DEBUG: 00:54:18.282: [focaltech_moc] MOC_DELETE_NUM_STATES entering state 2 409s (process:2127): libfprint-SSM-DEBUG: 00:54:18.282: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 409s (process:2127): libfprint-SSM-DEBUG: 00:54:18.283: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 409s (process:2127): libfprint-SSM-DEBUG: 00:54:18.283: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 409s (process:2127): libfprint-SSM-DEBUG: 00:54:18.283: [focaltech_moc] MOC_DELETE_NUM_STATES entering state 3 409s (process:2127): libfprint-SSM-DEBUG: 00:54:18.283: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 409s (process:2127): libfprint-SSM-DEBUG: 00:54:18.284: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 409s (process:2127): libfprint-SSM-DEBUG: 00:54:18.284: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 409s (process:2127): libfprint-focaltech_moc-DEBUG: 00:54:18.284: delete slot 0 409s (process:2127): libfprint-SSM-DEBUG: 00:54:18.284: [focaltech_moc] MOC_DELETE_NUM_STATES entering state 3 409s (process:2127): libfprint-SSM-DEBUG: 00:54:18.284: [focaltech_moc] MOC_DELETE_NUM_STATES entering state 4 409s (process:2127): libfprint-device-DEBUG: 00:54:18.284: Device reported deletion completion 409s (process:2127): libfprint-SSM-DEBUG: 00:54:18.284: [focaltech_moc] MOC_DELETE_NUM_STATES completed successfully 409s (process:2127): libfprint-SSM-DEBUG: 00:54:18.284: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 409s (process:2127): libfprint-device-DEBUG: 00:54:18.284: Completing action FPI_DEVICE_ACTION_DELETE in idle! 409s (process:2127): libfprint-device-DEBUG: 00:54:18.284: Not updating temperature model, device can run continuously! 409s (process:2127): libfprint-focaltech_moc-DEBUG: 00:54:18.285: Focaltechmoc dev_exit 409s (process:2127): libfprint-SSM-DEBUG: 00:54:18.285: [focaltech_moc] DEV_EXIT_STATES entering state 0 409s (process:2127): libfprint-SSM-DEBUG: 00:54:18.285: [focaltech_moc] DEV_EXIT_STATES completed successfully 409s (process:2127): libfprint-focaltech_moc-DEBUG: 00:54:18.285: class:dc, subclass:a0, protocol:b0 409s (process:2127): libfprint-device-DEBUG: 00:54:18.285: Device reported close completion 409s (process:2127): libfprint-device-DEBUG: 00:54:18.285: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 409s (process:2127): libfprint-device-DEBUG: 00:54:18.285: Not updating temperature model, device can run continuously! 409s enrolling 409s finger status: 409s enroll progress: (<__gi__.FpiDeviceFocaltechMoc object at 0xf1e36dc8 (FpiDeviceFocaltechMoc at 0x8e8868)>, 1, None, None, None) 409s finger status: 409s enroll progress: (<__gi__.FpiDeviceFocaltechMoc object at 0xf1e36dc8 (FpiDeviceFocaltechMoc at 0x8e8868)>, 2, None, None, None) 409s finger status: 409s enroll progress: (<__gi__.FpiDeviceFocaltechMoc object at 0xf1e36dc8 (FpiDeviceFocaltechMoc at 0x8e8868)>, 3, None, None, None) 409s finger status: 409s enroll progress: (<__gi__.FpiDeviceFocaltechMoc object at 0xf1e36dc8 (FpiDeviceFocaltechMoc at 0x8e8868)>, 4, None, None, None) 409s finger status: 409s enroll progress: (<__gi__.FpiDeviceFocaltechMoc object at 0xf1e36dc8 (FpiDeviceFocaltechMoc at 0x8e8868)>, 5, None, None, None) 409s finger status: 409s enroll progress: (<__gi__.FpiDeviceFocaltechMoc object at 0xf1e36dc8 (FpiDeviceFocaltechMoc at 0x8e8868)>, 6, None, None, None) 409s finger status: 409s enroll progress: (<__gi__.FpiDeviceFocaltechMoc object at 0xf1e36dc8 (FpiDeviceFocaltechMoc at 0x8e8868)>, 6, None, None, GLib.Error('The finger was not centered properly, please try again.', 'fp - device - retry - quark', 2)) 409s finger status: 409s enroll progress: (<__gi__.FpiDeviceFocaltechMoc object at 0xf1e36dc8 (FpiDeviceFocaltechMoc at 0x8e8868)>, 7, None, None, None) 409s finger status: 409s enroll progress: (<__gi__.FpiDeviceFocaltechMoc object at 0xf1e36dc8 (FpiDeviceFocaltechMoc at 0x8e8868)>, 8, None, None, None) 409s finger status: 409s enroll progress: (<__gi__.FpiDeviceFocaltechMoc object at 0xf1e36dc8 (FpiDeviceFocaltechMoc at 0x8e8868)>, 9, None, None, None) 409s finger status: 409s enroll progress: (<__gi__.FpiDeviceFocaltechMoc object at 0xf1e36dc8 (FpiDeviceFocaltechMoc at 0x8e8868)>, 10, None, None, None) 409s enroll done 409s listing 409s listing done 409s verifying 409s verify done 409s async identifying 409s indentification_done: 409s deleting 409s delete done 409s ** (umockdev-run:2123): DEBUG: 00:54:18.312: umockdev.vala:154: Removing test bed /tmp/umockdev.HAPZ12 409s (umockdev-run:2123): GLib-DEBUG: 00:54:18.324: unsetenv() is not thread-safe and should not be used after threads are created 409s PASS: libfprint-2/driver-focaltech_moc.test 409s Running test: libfprint-2/driver-uru4000-4500.test 409s ** (umockdev-run:2135): DEBUG: 00:54:18.384: umockdev.vala:127: Created udev test bed /tmp/umockdev.X1L612 409s ** (umockdev-run:2135): DEBUG: 00:54:18.384: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0/usb1/1-10 409s ** (umockdev-run:2135): DEBUG: 00:54:18.385: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0/usb1/1-10 (subsystem usb) 409s ** (umockdev-run:2135): DEBUG: 00:54:18.389: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.X1L612/dev/bus/usb/001/050 409s ** (umockdev-run:2135): DEBUG: 00:54:18.389: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0/usb1 409s ** (umockdev-run:2135): DEBUG: 00:54:18.390: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0/usb1 (subsystem usb) 409s ** (umockdev-run:2135): DEBUG: 00:54:18.394: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.X1L612/dev/bus/usb/001/001 409s ** (umockdev-run:2135): DEBUG: 00:54:18.395: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0 409s ** (umockdev-run:2135): DEBUG: 00:54:18.395: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0 (subsystem pci) 409s (process:2139): libfprint-context-DEBUG: 00:54:18.523: Initializing FpContext (libfprint version 1.94.8+tod1) 409s (process:2139): libfprint-tod-DEBUG: 00:54:18.524: Impossible to load the shared drivers dir Error opening directory “/usr/lib/arm-linux-gnueabihf/libfprint-2/tod-1”: No such file or directory 409s (process:2139): libfprint-context-DEBUG: 00:54:18.527: No driver found for USB device 1D6B:0002 409s (process:2139): libfprint-device-DEBUG: 00:54:18.527: Device reported probe completion 409s (process:2139): libfprint-device-DEBUG: 00:54:18.527: Completing action FPI_DEVICE_ACTION_PROBE in idle! 409s (process:2139): libfprint-device-DEBUG: 00:54:18.527: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 409s (process:2139): GLib-DEBUG: 00:54:18.529: setenv()/putenv() are not thread-safe and should not be used after threads are created 409s (process:2139): libfprint-image_device-DEBUG: 00:54:18.531: Image device open completed 409s (process:2139): libfprint-device-DEBUG: 00:54:18.531: Device reported open completion 409s (process:2139): libfprint-device-DEBUG: 00:54:18.531: Completing action FPI_DEVICE_ACTION_OPEN in idle! 409s (process:2139): libfprint-device-DEBUG: 00:54:18.531: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 409s (process:2139): libfprint-device-DEBUG: 00:54:18.531: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 409s (process:2139): libfprint-image_device-DEBUG: 00:54:18.531: Activating image device 409s (process:2139): libfprint-image_device-DEBUG: 00:54:18.531: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING 409s (process:2139): libfprint-SSM-DEBUG: 00:54:18.531: [uru4000] INIT_NUM_STATES entering state 0 409s (process:2139): libfprint-uru4000-DEBUG: 00:54:18.531: read 1 regs at 7 409s (process:2139): libfprint-uru4000-DEBUG: 00:54:18.532: reg value 1 409s (process:2139): libfprint-SSM-DEBUG: 00:54:18.532: [uru4000] INIT_NUM_STATES entering state 1 409s (process:2139): libfprint-SSM-DEBUG: 00:54:18.532: [uru4000] INIT_NUM_STATES entering state 3 409s (process:2139): libfprint-uru4000-DEBUG: 00:54:18.532: set 81 409s (process:2139): libfprint-SSM-DEBUG: 00:54:18.532: [uru4000] INIT_NUM_STATES entering state 4 409s (process:2139): libfprint-SSM-DEBUG: 00:54:18.532: [uru4000] POWERUP_NUM_STATES entering state 0 409s (process:2139): libfprint-SSM-DEBUG: 00:54:18.532: [uru4000] POWERUP_NUM_STATES entering state 1 409s (process:2139): libfprint-uru4000-DEBUG: 00:54:18.532: set 01 409s (process:2139): libfprint-uru4000-DEBUG: 00:54:18.533: recv irq type 56aa 409s (process:2139): libfprint-uru4000-DEBUG: 00:54:18.533: early scanpwr interrupt 409s (process:2139): libfprint-SSM-DEBUG: 00:54:18.533: [uru4000] POWERUP_NUM_STATES entering state 2 409s (process:2139): libfprint-uru4000-DEBUG: 00:54:18.533: read 1 regs at 7 409s (process:2139): libfprint-uru4000-DEBUG: 00:54:18.534: reg value 1 409s (process:2139): libfprint-SSM-DEBUG: 00:54:18.534: [uru4000] POWERUP_NUM_STATES entering state 3 409s (process:2139): libfprint-SSM-DEBUG: 00:54:18.534: [uru4000] POWERUP_NUM_STATES completed successfully 409s (process:2139): libfprint-SSM-DEBUG: 00:54:18.534: [uru4000] INIT_NUM_STATES entering state 5 409s (process:2139): libfprint-SSM-DEBUG: 00:54:18.534: [uru4000] INIT_NUM_STATES entering state 6 409s (process:2139): libfprint-SSM-DEBUG: 00:54:18.534: [uru4000] INIT_NUM_STATES entering state 7 409s (process:2139): libfprint-uru4000-DEBUG: 00:54:18.534: read 16 regs at f0 409s (process:2139): libfprint-uru4000-DEBUG: 00:54:18.534: reg value 1a 409s (process:2139): libfprint-SSM-DEBUG: 00:54:18.534: [uru4000] INIT_NUM_STATES entering state 8 409s (process:2139): libfprint-uru4000-DEBUG: 00:54:18.534: Versions 0010 and 0115 409s (process:2139): libfprint-SSM-DEBUG: 00:54:18.534: [uru4000] INIT_NUM_STATES completed successfully 409s (process:2139): libfprint-image_device-DEBUG: 00:54:18.534: Image device activation completed 409s (process:2139): libfprint-image_device-DEBUG: 00:54:18.534: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE 409s (process:2139): libfprint-image_device-DEBUG: 00:54:18.534: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 409s (process:2139): libfprint-uru4000-DEBUG: 00:54:18.534: wait finger on 409s (process:2139): libfprint-device-DEBUG: 00:54:18.534: Device reported finger status change: FP_FINGER_STATUS_NEEDED 409s (process:2139): libfprint-uru4000-DEBUG: 00:54:18.535: recv irq type 56aa 409s (process:2139): libfprint-uru4000-DEBUG: 00:54:18.535: recv irq type 56aa 409s (process:2139): libfprint-uru4000-DEBUG: 00:54:18.536: recv irq type 0101 409s (process:2139): libfprint-device-DEBUG: 00:54:18.536: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 409s (process:2139): libfprint-image_device-DEBUG: 00:54:18.536: Image device reported finger status: on 409s (process:2139): libfprint-image_device-DEBUG: 00:54:18.536: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 409s (process:2139): libfprint-uru4000-DEBUG: 00:54:18.536: starting capture 409s (process:2139): libfprint-uru4000-DEBUG: 00:54:18.536: Image encryption seed: 1374298404 409s (process:2139): libfprint-SSM-DEBUG: 00:54:18.536: [uru4000] IMAGING_NUM_STATES entering state 0 409s (process:2139): libfprint-SSM-DEBUG: 00:54:18.538: [uru4000] IMAGING_NUM_STATES entering state 1 409s (process:2139): libfprint-uru4000-DEBUG: 00:54:18.538: hw header lines 289 409s (process:2139): libfprint-uru4000-DEBUG: 00:54:18.538: dev2: 11240 409s (process:2139): libfprint-uru4000-DEBUG: 00:54:18.538: image seems to be encrypted 409s (process:2139): libfprint-SSM-DEBUG: 00:54:18.538: [uru4000] IMAGING_NUM_STATES entering state 2 409s (process:2139): libfprint-uru4000-DEBUG: 00:54:18.538: read 4 regs at 34 409s (process:2139): libfprint-uru4000-DEBUG: 00:54:18.539: reg value f2 409s (process:2139): libfprint-SSM-DEBUG: 00:54:18.539: [uru4000] IMAGING_NUM_STATES entering state 3 409s (process:2139): libfprint-uru4000-DEBUG: 00:54:18.539: encryption id 00 -> key 544409d6 409s (process:2139): libfprint-uru4000-DEBUG: 00:54:18.539: 0 02 72 409s (process:2139): libfprint-uru4000-DEBUG: 00:54:18.539: decoding 72 lines 409s (process:2139): libfprint-uru4000-DEBUG: 00:54:18.539: 1 00 1 409s (process:2139): libfprint-uru4000-DEBUG: 00:54:18.539: skipping 1 lines 409s (process:2139): libfprint-uru4000-DEBUG: 00:54:18.539: 2 02 49 409s (process:2139): libfprint-uru4000-DEBUG: 00:54:18.539: decoding 49 lines 409s (process:2139): libfprint-uru4000-DEBUG: 00:54:18.539: 3 01 1 409s (process:2139): libfprint-uru4000-DEBUG: 00:54:18.539: skipping 1 lines 409s (process:2139): libfprint-uru4000-DEBUG: 00:54:18.539: 4 00 1 409s (process:2139): libfprint-uru4000-DEBUG: 00:54:18.539: skipping 1 lines 409s (process:2139): libfprint-uru4000-DEBUG: 00:54:18.539: 5 02 49 409s (process:2139): libfprint-uru4000-DEBUG: 00:54:18.539: decoding 49 lines 409s (process:2139): libfprint-uru4000-DEBUG: 00:54:18.539: 6 00 1 409s (process:2139): libfprint-uru4000-DEBUG: 00:54:18.539: skipping 1 lines 409s (process:2139): libfprint-uru4000-DEBUG: 00:54:18.539: 7 02 116 409s (process:2139): libfprint-uru4000-DEBUG: 00:54:18.539: decoding 116 lines 409s (process:2139): libfprint-SSM-DEBUG: 00:54:18.540: [uru4000] IMAGING_NUM_STATES entering state 4 409s (process:2139): libfprint-image_device-DEBUG: 00:54:18.540: Image device captured an image 409s (process:2139): libfprint-image_device-DEBUG: 00:54:18.542: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 409s (process:2139): libfprint-device-DEBUG: 00:54:18.542: Device reported finger status change: FP_FINGER_STATUS_PRESENT 409s (process:2139): libfprint-SSM-DEBUG: 00:54:18.542: [uru4000] IMAGING_NUM_STATES completed successfully 409s (process:2139): libfprint-uru4000-DEBUG: 00:54:18.542: await finger off 409s (process:2139): libfprint-uru4000-DEBUG: 00:54:18.543: recv irq type 0200 409s (process:2139): libfprint-device-DEBUG: 00:54:18.543: Device reported finger status change: FP_FINGER_STATUS_NONE 409s (process:2139): libfprint-image_device-DEBUG: 00:54:18.543: Image device reported finger status: off 409s (process:2139): libfprint-image_device-DEBUG: 00:54:18.543: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 409s (process:2139): libfprint-image_device-DEBUG: 00:54:18.543: Deactivating image device 409s (process:2139): libfprint-image_device-DEBUG: 00:54:18.543: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_DEACTIVATING 409s (process:2139): libfprint-uru4000-DEBUG: 00:54:18.543: deactivating 409s (process:2139): libfprint-uru4000-DEBUG: 00:54:18.544: cancelled 409s (process:2139): libfprint-image_device-DEBUG: 00:54:18.544: Image device deactivation completed 409s (process:2139): libfprint-image_device-DEBUG: 00:54:18.544: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE 409s (process:2139): libfprint-image-DEBUG: 00:54:18.565: Minutiae scan completed in 0.023150 secs 409s (process:2139): libfprint-device-DEBUG: 00:54:18.565: Device reported capture completion 409s (process:2139): libfprint-device-DEBUG: 00:54:18.566: Completing action FPI_DEVICE_ACTION_CAPTURE in idle! 409s (process:2139): libfprint-device-DEBUG: 00:54:18.566: Updated temperature model after 0.03 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 409s (process:2139): libfprint-image_device-DEBUG: 00:54:18.567: Image device close completed 409s (process:2139): libfprint-device-DEBUG: 00:54:18.567: Device reported close completion 409s (process:2139): libfprint-device-DEBUG: 00:54:18.567: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 409s (process:2139): libfprint-device-DEBUG: 00:54:18.567: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 409s ** (umockdev-run:2135): DEBUG: 00:54:18.764: umockdev.vala:154: Removing test bed /tmp/umockdev.X1L612 409s (umockdev-run:2135): GLib-DEBUG: 00:54:18.771: unsetenv() is not thread-safe and should not be used after threads are created 409s Comparing PNGs /tmp/libfprint-umockdev-test-kbxzgs3w/capture.png and /usr/share/installed-tests/libfprint-2/uru4000-4500/capture.png 409s PASS: libfprint-2/driver-uru4000-4500.test 409s Running test: libfprint-2/driver-aes3500.test 409s ** (umockdev-run:2148): DEBUG: 00:54:18.872: umockdev.vala:127: Created udev test bed /tmp/umockdev.7L7G22 409s ** (umockdev-run:2148): DEBUG: 00:54:18.872: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:1c.0/0000:01:00.0/0000:02:02.0/0000:39:00.0/usb3/3-1/3-1.1/3-1.1.3 409s ** (umockdev-run:2148): DEBUG: 00:54:18.876: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:1c.0/0000:01:00.0/0000:02:02.0/0000:39:00.0/usb3/3-1/3-1.1/3-1.1.3 (subsystem usb) 409s ** (umockdev-run:2148): DEBUG: 00:54:18.880: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.7L7G22/dev/bus/usb/003/004 409s ** (umockdev-run:2148): DEBUG: 00:54:18.880: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:1c.0/0000:01:00.0/0000:02:02.0/0000:39:00.0/usb3/3-1/3-1.1 409s ** (umockdev-run:2148): DEBUG: 00:54:18.884: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:1c.0/0000:01:00.0/0000:02:02.0/0000:39:00.0/usb3/3-1/3-1.1 (subsystem usb) 409s ** (umockdev-run:2148): DEBUG: 00:54:18.889: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.7L7G22/dev/bus/usb/003/003 409s ** (umockdev-run:2148): DEBUG: 00:54:18.889: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:1c.0/0000:01:00.0/0000:02:02.0/0000:39:00.0/usb3/3-1 409s ** (umockdev-run:2148): DEBUG: 00:54:18.892: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:1c.0/0000:01:00.0/0000:02:02.0/0000:39:00.0/usb3/3-1 (subsystem usb) 409s ** (umockdev-run:2148): DEBUG: 00:54:18.897: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.7L7G22/dev/bus/usb/003/002 409s ** (umockdev-run:2148): DEBUG: 00:54:18.897: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:1c.0/0000:01:00.0/0000:02:02.0/0000:39:00.0/usb3 409s ** (umockdev-run:2148): DEBUG: 00:54:18.900: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:1c.0/0000:01:00.0/0000:02:02.0/0000:39:00.0/usb3 (subsystem usb) 409s ** (umockdev-run:2148): DEBUG: 00:54:18.904: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.7L7G22/dev/bus/usb/003/001 409s ** (umockdev-run:2148): DEBUG: 00:54:18.904: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:1c.0/0000:01:00.0/0000:02:02.0/0000:39:00.0 409s ** (umockdev-run:2148): DEBUG: 00:54:18.906: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:1c.0/0000:01:00.0/0000:02:02.0/0000:39:00.0 (subsystem pci) 409s ** (umockdev-run:2148): DEBUG: 00:54:18.910: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:1c.0/0000:01:00.0/0000:02:02.0 409s ** (umockdev-run:2148): DEBUG: 00:54:18.911: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:1c.0/0000:01:00.0/0000:02:02.0 (subsystem pci) 409s ** (umockdev-run:2148): DEBUG: 00:54:18.915: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:1c.0/0000:01:00.0 409s ** (umockdev-run:2148): DEBUG: 00:54:18.916: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:1c.0/0000:01:00.0 (subsystem pci) 409s ** (umockdev-run:2148): DEBUG: 00:54:18.919: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:1c.0 409s ** (umockdev-run:2148): DEBUG: 00:54:18.920: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:1c.0 (subsystem pci) 409s (umockdev-run:2148): GLib-GIO-DEBUG: 00:54:18.923: _g_io_module_get_default: Found default implementation local (GLocalVfs) for ?gio-vfs? 410s (process:2152): libfprint-context-DEBUG: 00:54:19.044: Initializing FpContext (libfprint version 1.94.8+tod1) 410s (process:2152): libfprint-tod-DEBUG: 00:54:19.044: Impossible to load the shared drivers dir Error opening directory “/usr/lib/arm-linux-gnueabihf/libfprint-2/tod-1”: No such file or directory 410s (process:2152): libfprint-context-DEBUG: 00:54:19.049: No driver found for USB device 2230:0006 410s (process:2152): libfprint-context-DEBUG: 00:54:19.049: No driver found for USB device 2230:0006 410s (process:2152): libfprint-context-DEBUG: 00:54:19.049: No driver found for USB device 1D6B:0002 410s (process:2152): libfprint-device-DEBUG: 00:54:19.050: Device reported probe completion 410s (process:2152): libfprint-device-DEBUG: 00:54:19.050: Completing action FPI_DEVICE_ACTION_PROBE in idle! 410s (process:2152): libfprint-device-DEBUG: 00:54:19.050: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 410s (process:2152): libfprint-image_device-DEBUG: 00:54:19.052: Image device open completed 410s (process:2152): libfprint-device-DEBUG: 00:54:19.052: Device reported open completion 410s (process:2152): libfprint-device-DEBUG: 00:54:19.052: Completing action FPI_DEVICE_ACTION_OPEN in idle! 410s (process:2152): libfprint-device-DEBUG: 00:54:19.052: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 410s (process:2152): libfprint-device-DEBUG: 00:54:19.052: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 410s (process:2152): libfprint-image_device-DEBUG: 00:54:19.052: Activating image device 410s (process:2152): libfprint-image_device-DEBUG: 00:54:19.052: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING 410s (process:2152): libfprint-aeslib-DEBUG: 00:54:19.052: write 50 regs 410s (process:2152): libfprint-aeslib-DEBUG: 00:54:19.057: all registers written 410s (process:2152): libfprint-image_device-DEBUG: 00:54:19.057: Image device activation completed 410s (process:2152): libfprint-image_device-DEBUG: 00:54:19.057: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE 410s (process:2152): libfprint-image_device-DEBUG: 00:54:19.057: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 410s (process:2152): libfprint-aeslib-DEBUG: 00:54:19.057: write 6 regs 410s (process:2152): libfprint-device-DEBUG: 00:54:19.057: Device reported finger status change: FP_FINGER_STATUS_NEEDED 410s (process:2152): libfprint-aeslib-DEBUG: 00:54:19.058: all registers written 410s (process:2152): libfprint-device-DEBUG: 00:54:19.059: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 410s (process:2152): libfprint-image_device-DEBUG: 00:54:19.059: Image device reported finger status: on 410s (process:2152): libfprint-image_device-DEBUG: 00:54:19.059: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 410s (process:2152): libfprint-aes3k-DEBUG: 00:54:19.059: frame header byte e0 410s (process:2152): libfprint-aes3k-DEBUG: 00:54:19.059: frame header byte e1 410s (process:2152): libfprint-aes3k-DEBUG: 00:54:19.059: frame header byte e2 410s (process:2152): libfprint-aes3k-DEBUG: 00:54:19.059: frame header byte e3 410s (process:2152): libfprint-aes3k-DEBUG: 00:54:19.059: frame header byte e4 410s (process:2152): libfprint-aes3k-DEBUG: 00:54:19.059: frame header byte e5 410s (process:2152): libfprint-aes3k-DEBUG: 00:54:19.059: frame header byte e6 410s (process:2152): libfprint-aes3k-DEBUG: 00:54:19.059: frame header byte e7 410s (process:2152): libfprint-image_device-DEBUG: 00:54:19.060: Image device captured an image 410s (process:2152): libfprint-image_device-DEBUG: 00:54:19.061: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 410s (process:2152): libfprint-device-DEBUG: 00:54:19.061: Device reported finger status change: FP_FINGER_STATUS_PRESENT 410s (process:2152): libfprint-device-DEBUG: 00:54:19.061: Device reported finger status change: FP_FINGER_STATUS_NONE 410s (process:2152): libfprint-image_device-DEBUG: 00:54:19.061: Image device reported finger status: off 410s (process:2152): libfprint-image_device-DEBUG: 00:54:19.061: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 410s (process:2152): libfprint-image_device-DEBUG: 00:54:19.061: Deactivating image device 410s (process:2152): libfprint-image_device-DEBUG: 00:54:19.061: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_DEACTIVATING 410s (process:2152): libfprint-image_device-DEBUG: 00:54:19.061: Image device deactivation completed 410s (process:2152): libfprint-image_device-DEBUG: 00:54:19.061: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE 410s (process:2152): libfprint-image-DEBUG: 00:54:19.082: Minutiae scan completed in 0.021419 secs 410s (process:2152): libfprint-device-DEBUG: 00:54:19.083: Device reported capture completion 410s (process:2152): libfprint-device-DEBUG: 00:54:19.083: Completing action FPI_DEVICE_ACTION_CAPTURE in idle! 410s (process:2152): libfprint-device-DEBUG: 00:54:19.083: Updated temperature model after 0.03 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 410s (process:2152): libfprint-image_device-DEBUG: 00:54:19.083: Image device close completed 410s (process:2152): libfprint-device-DEBUG: 00:54:19.083: Device reported close completion 410s (process:2152): libfprint-device-DEBUG: 00:54:19.084: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 410s (process:2152): libfprint-device-DEBUG: 00:54:19.084: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 410s ** (umockdev-run:2148): DEBUG: 00:54:19.210: umockdev.vala:154: Removing test bed /tmp/umockdev.7L7G22 410s (umockdev-run:2148): GLib-DEBUG: 00:54:19.226: unsetenv() is not thread-safe and should not be used after threads are created 410s Comparing PNGs /tmp/libfprint-umockdev-test-2uojx_sv/capture.png and /usr/share/installed-tests/libfprint-2/aes3500/capture.png 410s PASS: libfprint-2/driver-aes3500.test 410s Running test: libfprint-2/tod-fp-device-tod-fake_test_dev_tod_current.test 410s TAP version 14 410s # random seed: R02S07b5180b0f936c428ff51473cabde3f3 410s 1..14 410s # Start of device tests 410s # Start of async tests 410s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 410s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/current/libdevice-fake-tod-driver.so 410s # libfprint-tod-DEBUG: Found TOD entry point symbol 0xee1aaa9d, GType is 149614768 410s # libfprint-tod-DEBUG: Loading driver fake_test_dev_tod_current (Virtual device for debugging) 410s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0003 410s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 410s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0002 410s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_FAKE_DEVICE, yes 410s # libfprint-context-DEBUG: created 410s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_probe: Device Virtual device for debugging in action FPI_DEVICE_ACTION_PROBE 410s # 410s # libfprint-device-DEBUG: Device reported probe completion 410s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 410s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 410s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 410s # 410s # libfprint-device-DEBUG: Device reported open completion 410s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 410s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 410s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 410s # 410s # libfprint-device-DEBUG: Device reported close completion 410s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 410s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 410s ok 1 /device/async/open 410s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 410s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/current/libdevice-fake-tod-driver.so 410s # libfprint-tod-DEBUG: Found TOD entry point symbol 0xee1aaa9d, GType is 149614768 410s # libfprint-tod-DEBUG: Loading driver fake_test_dev_tod_current (Virtual device for debugging) 410s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0003 410s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 410s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0002 410s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_FAKE_DEVICE, yes 410s # libfprint-context-DEBUG: created 410s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_probe: Device Virtual device for debugging in action FPI_DEVICE_ACTION_PROBE 410s # 410s # libfprint-device-DEBUG: Device reported probe completion 410s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 410s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 410s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 410s # 410s # libfprint-device-DEBUG: Device reported open completion 410s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 410s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 410s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 410s # 410s # libfprint-device-DEBUG: Device reported close completion 410s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 410s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 410s ok 2 /device/async/close 410s # End of async tests 410s # Start of sync tests 410s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 410s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/current/libdevice-fake-tod-driver.so 410s # libfprint-tod-DEBUG: Found TOD entry point symbol 0xee1aaa9d, GType is 149614768 410s # libfprint-tod-DEBUG: Loading driver fake_test_dev_tod_current (Virtual device for debugging) 410s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0003 410s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 410s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0002 410s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_FAKE_DEVICE, yes 410s # libfprint-context-DEBUG: created 410s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_probe: Device Virtual device for debugging in action FPI_DEVICE_ACTION_PROBE 410s # 410s # libfprint-device-DEBUG: Device reported probe completion 410s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 410s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 410s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 410s # 410s # libfprint-device-DEBUG: Device reported open completion 410s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 410s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 410s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 410s # 410s # libfprint-device-DEBUG: Device reported close completion 410s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 410s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 410s ok 3 /device/sync/open 410s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 410s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/current/libdevice-fake-tod-driver.so 410s # libfprint-tod-DEBUG: Found TOD entry point symbol 0xee1aaa9d, GType is 149614768 410s # libfprint-tod-DEBUG: Loading driver fake_test_dev_tod_current (Virtual device for debugging) 410s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0003 410s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 410s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0002 410s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_FAKE_DEVICE, yes 410s # libfprint-context-DEBUG: created 410s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_probe: Device Virtual device for debugging in action FPI_DEVICE_ACTION_PROBE 410s # 410s # libfprint-device-DEBUG: Device reported probe completion 410s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 410s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 410s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 410s # 410s # libfprint-device-DEBUG: Device reported open completion 410s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 410s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 410s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 410s # 410s # libfprint-device-DEBUG: Device reported close completion 410s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 410s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 410s ok 4 /device/sync/close 410s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 410s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/current/libdevice-fake-tod-driver.so 410s # libfprint-tod-DEBUG: Found TOD entry point symbol 0xee1aaa9d, GType is 149614768 410s # libfprint-tod-DEBUG: Loading driver fake_test_dev_tod_current (Virtual device for debugging) 410s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0003 410s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 410s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0002 410s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_FAKE_DEVICE, yes 410s # libfprint-context-DEBUG: created 410s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_probe: Device Virtual device for debugging in action FPI_DEVICE_ACTION_PROBE 410s # 410s # libfprint-device-DEBUG: Device reported probe completion 410s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 410s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 410s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 410s # 410s # libfprint-device-DEBUG: Device reported open completion 410s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 410s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 410s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 410s # 410s # libfprint-device-DEBUG: Device reported close completion 410s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 410s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 410s ok 5 /device/sync/get_driver 410s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 410s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/current/libdevice-fake-tod-driver.so 410s # libfprint-tod-DEBUG: Found TOD entry point symbol 0xee1aaa9d, GType is 149614768 410s # libfprint-tod-DEBUG: Loading driver fake_test_dev_tod_current (Virtual device for debugging) 410s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0003 410s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 410s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0002 410s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_FAKE_DEVICE, yes 410s # libfprint-context-DEBUG: created 410s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_probe: Device Virtual device for debugging in action FPI_DEVICE_ACTION_PROBE 410s # 410s # libfprint-device-DEBUG: Device reported probe completion 410s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 410s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 410s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 410s # 410s # libfprint-device-DEBUG: Device reported open completion 410s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 410s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 410s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 410s # 410s # libfprint-device-DEBUG: Device reported close completion 410s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 410s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 410s ok 6 /device/sync/get_device_id 410s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 410s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/current/libdevice-fake-tod-driver.so 410s # libfprint-tod-DEBUG: Found TOD entry point symbol 0xee1aaa9d, GType is 149614768 410s # libfprint-tod-DEBUG: Loading driver fake_test_dev_tod_current (Virtual device for debugging) 410s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0003 410s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 410s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0002 410s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_FAKE_DEVICE, yes 410s # libfprint-context-DEBUG: created 410s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_probe: Device Virtual device for debugging in action FPI_DEVICE_ACTION_PROBE 410s # 410s # libfprint-device-DEBUG: Device reported probe completion 410s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 410s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 410s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 410s # 410s # libfprint-device-DEBUG: Device reported open completion 410s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 410s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 410s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 410s # 410s # libfprint-device-DEBUG: Device reported close completion 410s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 410s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 410s ok 7 /device/sync/get_name 410s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 410s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/current/libdevice-fake-tod-driver.so 410s # libfprint-tod-DEBUG: Found TOD entry point symbol 0xee1aaa9d, GType is 149614768 410s # libfprint-tod-DEBUG: Loading driver fake_test_dev_tod_current (Virtual device for debugging) 410s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0003 410s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 410s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0002 410s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_FAKE_DEVICE, yes 410s # libfprint-context-DEBUG: created 410s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_probe: Device Virtual device for debugging in action FPI_DEVICE_ACTION_PROBE 410s # 410s # libfprint-device-DEBUG: Device reported probe completion 410s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 410s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 410s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 410s # 410s # libfprint-device-DEBUG: Device reported open completion 410s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 410s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 410s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 410s # 410s # libfprint-device-DEBUG: Device reported close completion 410s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 410s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 410s ok 8 /device/sync/get_scan_type 410s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 410s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/current/libdevice-fake-tod-driver.so 410s # libfprint-tod-DEBUG: Found TOD entry point symbol 0xee1aaa9d, GType is 149614768 410s # libfprint-tod-DEBUG: Loading driver fake_test_dev_tod_current (Virtual device for debugging) 410s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0003 410s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 410s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0002 410s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_FAKE_DEVICE, yes 410s # libfprint-context-DEBUG: created 410s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_probe: Device Virtual device for debugging in action FPI_DEVICE_ACTION_PROBE 410s # 410s # libfprint-device-DEBUG: Device reported probe completion 410s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 410s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 410s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 410s # 410s # libfprint-device-DEBUG: Device reported open completion 410s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 410s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 410s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 410s # 410s # libfprint-device-DEBUG: Device reported close completion 410s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 410s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 410s ok 9 /device/sync/get_nr_enroll_stages 410s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 410s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/current/libdevice-fake-tod-driver.so 410s # libfprint-tod-DEBUG: Found TOD entry point symbol 0xee1aaa9d, GType is 149614768 410s # libfprint-tod-DEBUG: Loading driver fake_test_dev_tod_current (Virtual device for debugging) 410s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0003 410s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 410s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0002 410s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_FAKE_DEVICE, yes 410s # libfprint-context-DEBUG: created 410s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_probe: Device Virtual device for debugging in action FPI_DEVICE_ACTION_PROBE 410s # 410s # libfprint-device-DEBUG: Device reported probe completion 410s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 410s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 410s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 410s # 410s # libfprint-device-DEBUG: Device reported open completion 410s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 410s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 410s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 410s # 410s # libfprint-device-DEBUG: Device reported close completion 410s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 410s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 410s ok 10 /device/sync/supports_identify 410s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 410s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/current/libdevice-fake-tod-driver.so 410s # libfprint-tod-DEBUG: Found TOD entry point symbol 0xee1aaa9d, GType is 149614768 410s # libfprint-tod-DEBUG: Loading driver fake_test_dev_tod_current (Virtual device for debugging) 410s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0003 410s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 410s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0002 410s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_FAKE_DEVICE, yes 410s # libfprint-context-DEBUG: created 410s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_probe: Device Virtual device for debugging in action FPI_DEVICE_ACTION_PROBE 410s # 410s # libfprint-device-DEBUG: Device reported probe completion 410s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 410s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 410s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 410s # 410s # libfprint-device-DEBUG: Device reported open completion 410s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 410s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 410s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 410s # 410s # libfprint-device-DEBUG: Device reported close completion 410s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 410s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 410s ok 11 /device/sync/supports_capture 410s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 410s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/current/libdevice-fake-tod-driver.so 410s # libfprint-tod-DEBUG: Found TOD entry point symbol 0xee1aaa9d, GType is 149614768 410s # libfprint-tod-DEBUG: Loading driver fake_test_dev_tod_current (Virtual device for debugging) 410s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0003 410s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 410s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0002 410s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_FAKE_DEVICE, yes 410s # libfprint-context-DEBUG: created 410s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_probe: Device Virtual device for debugging in action FPI_DEVICE_ACTION_PROBE 410s # 410s # libfprint-device-DEBUG: Device reported probe completion 410s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 410s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 410s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 410s # 410s # libfprint-device-DEBUG: Device reported open completion 410s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 410s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 410s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 410s # 410s # libfprint-device-DEBUG: Device reported close completion 410s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 410s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 410s ok 12 /device/sync/has_storage 410s # Start of open tests 410s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 410s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/current/libdevice-fake-tod-driver.so 410s # libfprint-tod-DEBUG: Found TOD entry point symbol 0xee1aaa9d, GType is 149614768 410s # libfprint-tod-DEBUG: Loading driver fake_test_dev_tod_current (Virtual device for debugging) 410s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0003 410s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 410s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0002 410s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_FAKE_DEVICE, yes 410s # libfprint-context-DEBUG: created 410s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_probe: Device Virtual device for debugging in action FPI_DEVICE_ACTION_PROBE 410s # 410s # libfprint-device-DEBUG: Device reported probe completion 410s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 410s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 410s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 410s # 410s # libfprint-device-DEBUG: Device reported open completion 410s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 410s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 410s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 410s # 410s # libfprint-device-DEBUG: Device reported close completion 410s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 410s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 410s ok 13 /device/sync/open/notify 410s # End of open tests 410s # Start of close tests 410s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 410s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/current/libdevice-fake-tod-driver.so 410s # libfprint-tod-DEBUG: Found TOD entry point symbol 0xee1aaa9d, GType is 149614768 410s # libfprint-tod-DEBUG: Loading driver fake_test_dev_tod_current (Virtual device for debugging) 410s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0003 410s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 410s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0002 410s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_FAKE_DEVICE, yes 410s # libfprint-context-DEBUG: created 410s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_probe: Device Virtual device for debugging in action FPI_DEVICE_ACTION_PROBE 410s # 410s # libfprint-device-DEBUG: Device reported probe completion 410s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 410s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 410s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 410s # 410s # libfprint-device-DEBUG: Device reported open completion 410s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 410s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 410s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 410s # 410s # libfprint-device-DEBUG: Device reported close completion 410s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 410s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 410s ok 14 /device/sync/close/notify 410s # End of close tests 410s # End of sync tests 410s # End of device tests 410s PASS: libfprint-2/tod-fp-device-tod-fake_test_dev_tod_current.test 410s Running test: libfprint-2/tod-fp-context-tod-fake_test_dev_tod_current.test 410s TAP version 14 410s # random seed: R02S6d3a592b66006a69d554fcad3bb2644f 410s 1..4 410s # Start of context tests 410s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 410s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/current/libdevice-fake-tod-driver.so 410s # libfprint-tod-DEBUG: Found TOD entry point symbol 0xea623a9d, GType is 226204688 410s # libfprint-tod-DEBUG: Loading driver fake_test_dev_tod_current (Virtual device for debugging) 410s ok 1 /context/new 410s # GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used after threads are created 410s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 410s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0003 410s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 410s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0002 410s # GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used after threads are created 410s ok 2 /context/no-devices 410s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 410s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/current/libdevice-fake-tod-driver.so 410s # libfprint-tod-DEBUG: Found TOD entry point symbol 0xea623a9d, GType is 226204688 410s # libfprint-tod-DEBUG: Loading driver fake_test_dev_tod_current (Virtual device for debugging) 410s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0003 410s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 410s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0002 410s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_FAKE_DEVICE, yes 410s # libfprint-context-DEBUG: created 410s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_probe: Device Virtual device for debugging in action FPI_DEVICE_ACTION_PROBE 410s # 410s # libfprint-device-DEBUG: Device reported probe completion 410s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 410s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 410s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 410s # 410s # libfprint-device-DEBUG: Device reported open completion 410s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 410s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 410s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 410s # 410s # libfprint-device-DEBUG: Device reported close completion 410s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 410s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 410s ok 3 /context/has-virtual-device 410s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 410s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/current/libdevice-fake-tod-driver.so 410s # libfprint-tod-DEBUG: Found TOD entry point symbol 0xea623a9d, GType is 226204688 410s # libfprint-tod-DEBUG: Loading driver fake_test_dev_tod_current (Virtual device for debugging) 410s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0003 410s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 410s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0002 410s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_FAKE_DEVICE, yes 410s # libfprint-context-DEBUG: created 410s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_probe: Device Virtual device for debugging in action FPI_DEVICE_ACTION_PROBE 410s # 410s # libfprint-device-DEBUG: Device reported probe completion 410s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 410s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 410s ok 4 /context/enumerates-new-devices 410s # End of context tests 410s PASS: libfprint-2/tod-fp-context-tod-fake_test_dev_tod_current.test 410s Running test: libfprint-2/fpi-assembling.test 410s TAP version 14 410s # random seed: R02S584169865508a01df79e282d863722ce 410s 1..1 410s # Start of assembling tests 410s # libfprint-assembling-DEBUG: calc delta completed in 0.111300 secs 410s # libfprint-assembling-DEBUG: calc delta completed in 0.110968 secs 410s # libfprint-assembling-DEBUG: errors: 0 rev: 130848 410s # libfprint-assembling-DEBUG: calc delta completed in 0.111051 secs 410s # libfprint-assembling-DEBUG: height is 310 410s ok 1 /assembling/frames 410s # End of assembling tests 410s PASS: libfprint-2/fpi-assembling.test 410s Running test: libfprint-2/driver-goodixmoc.test 410s ** (umockdev-run:2207): DEBUG: 00:54:19.730: umockdev.vala:127: Created udev test bed /tmp/umockdev.UHUD22 410s ** (umockdev-run:2207): DEBUG: 00:54:19.730: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0/usb3/3-9 410s ** (umockdev-run:2207): DEBUG: 00:54:19.732: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0/usb3/3-9 (subsystem usb) 410s ** (umockdev-run:2207): DEBUG: 00:54:19.737: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.UHUD22/dev/bus/usb/003/004 410s ** (umockdev-run:2207): DEBUG: 00:54:19.737: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0/usb3 410s ** (umockdev-run:2207): DEBUG: 00:54:19.738: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0/usb3 (subsystem usb) 410s ** (umockdev-run:2207): DEBUG: 00:54:19.743: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.UHUD22/dev/bus/usb/003/001 410s ** (umockdev-run:2207): DEBUG: 00:54:19.743: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0 410s ** (umockdev-run:2207): DEBUG: 00:54:19.743: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0 (subsystem pci) 410s (process:2211): libfprint-context-DEBUG: 00:54:19.849: Initializing FpContext (libfprint version 1.94.8+tod1) 410s (process:2211): libfprint-tod-DEBUG: 00:54:19.849: Impossible to load the shared drivers dir Error opening directory “/usr/lib/arm-linux-gnueabihf/libfprint-2/tod-1”: No such file or directory 410s (process:2211): libfprint-context-DEBUG: 00:54:19.852: No driver found for USB device 1D6B:0002 410s (process:2211): libfprint-device-DEBUG: 00:54:19.854: Device reported probe completion 410s (process:2211): libfprint-device-DEBUG: 00:54:19.854: Completing action FPI_DEVICE_ACTION_PROBE in idle! 410s (process:2211): libfprint-device-DEBUG: 00:54:19.854: Not updating temperature model, device can run continuously! 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.855: [goodixmoc] FP_INIT_NUM_STATES entering state 0 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.855: [goodixmoc] FP_CMD_NUM_STATES entering state 0 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.856: [goodixmoc] FP_CMD_NUM_STATES entering state 1 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.856: [goodixmoc] FP_CMD_NUM_STATES entering state 1 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.857: [goodixmoc] FP_CMD_NUM_STATES entering state 2 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.857: [goodixmoc] FP_CMD_NUM_STATES entering state 2 410s (process:2211): libfprint-goodixmoc-DEBUG: 00:54:19.858: Firmware type: APP 410s (process:2211): libfprint-goodixmoc-DEBUG: 00:54:19.858: Firmware version: 01000274 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.858: [goodixmoc] FP_INIT_NUM_STATES entering state 1 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.858: [goodixmoc] FP_CMD_NUM_STATES entering state 0 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.858: [goodixmoc] FP_CMD_NUM_STATES completed successfully 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.858: [goodixmoc] FP_CMD_NUM_STATES entering state 1 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.858: [goodixmoc] FP_CMD_NUM_STATES entering state 1 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.859: [goodixmoc] FP_CMD_NUM_STATES entering state 2 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.859: [goodixmoc] FP_CMD_NUM_STATES entering state 2 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.860: [goodixmoc] FP_INIT_NUM_STATES entering state 2 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.860: [goodixmoc] FP_CMD_NUM_STATES entering state 0 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.860: [goodixmoc] FP_CMD_NUM_STATES completed successfully 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.860: [goodixmoc] FP_CMD_NUM_STATES entering state 1 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.861: [goodixmoc] FP_CMD_NUM_STATES entering state 1 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.861: [goodixmoc] FP_CMD_NUM_STATES entering state 2 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.861: [goodixmoc] FP_CMD_NUM_STATES entering state 2 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.862: [goodixmoc] FP_INIT_NUM_STATES completed successfully 410s (process:2211): libfprint-device-DEBUG: 00:54:19.862: Device reported open completion 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.862: [goodixmoc] FP_CMD_NUM_STATES completed successfully 410s (process:2211): libfprint-device-DEBUG: 00:54:19.862: Completing action FPI_DEVICE_ACTION_OPEN in idle! 410s (process:2211): libfprint-device-DEBUG: 00:54:19.862: Not updating temperature model, device can run continuously! 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.862: [goodixmoc] FP_CMD_NUM_STATES entering state 0 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.862: [goodixmoc] FP_CMD_NUM_STATES entering state 1 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.863: [goodixmoc] FP_CMD_NUM_STATES entering state 1 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.863: [goodixmoc] FP_CMD_NUM_STATES entering state 2 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.864: [goodixmoc] FP_CMD_NUM_STATES entering state 2 410s (process:2211): libfprint-goodixmoc-DEBUG: 00:54:19.864: Successfully cleared storage 410s (process:2211): libfprint-device-DEBUG: 00:54:19.864: Device reported deletion completion 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.864: [goodixmoc] FP_CMD_NUM_STATES completed successfully 410s (process:2211): libfprint-device-DEBUG: 00:54:19.864: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 410s (process:2211): libfprint-device-DEBUG: 00:54:19.864: Not updating temperature model, device can run continuously! 410s (process:2211): libfprint-device-DEBUG: 00:54:19.865: Not updating temperature model, device can run continuously! 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.865: [goodixmoc] enroll entering state 0 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.865: [goodixmoc] FP_CMD_NUM_STATES entering state 0 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.866: [goodixmoc] FP_CMD_NUM_STATES entering state 1 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.866: [goodixmoc] FP_CMD_NUM_STATES entering state 1 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.866: [goodixmoc] FP_CMD_NUM_STATES entering state 2 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.867: [goodixmoc] FP_CMD_NUM_STATES entering state 2 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.867: [goodixmoc] enroll entering state 1 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.867: [goodixmoc] FP_CMD_NUM_STATES entering state 0 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.868: [goodixmoc] FP_CMD_NUM_STATES completed successfully 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.868: [goodixmoc] FP_CMD_NUM_STATES entering state 1 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.868: [goodixmoc] FP_CMD_NUM_STATES entering state 1 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.869: [goodixmoc] FP_CMD_NUM_STATES entering state 2 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.869: [goodixmoc] FP_CMD_NUM_STATES entering state 2 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.869: [goodixmoc] enroll entering state 2 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.869: [goodixmoc] FP_CMD_NUM_STATES entering state 0 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.870: [goodixmoc] FP_CMD_NUM_STATES completed successfully 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.870: [goodixmoc] FP_CMD_NUM_STATES entering state 1 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.870: [goodixmoc] FP_CMD_NUM_STATES entering state 1 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.871: [goodixmoc] FP_CMD_NUM_STATES entering state 2 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.871: [goodixmoc] FP_CMD_NUM_STATES entering state 2 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.872: [goodixmoc] enroll entering state 3 410s (process:2211): libfprint-device-DEBUG: 00:54:19.872: Device reported finger status change: FP_FINGER_STATUS_NEEDED 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.872: [goodixmoc] FP_CMD_NUM_STATES entering state 0 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.872: [goodixmoc] FP_CMD_NUM_STATES completed successfully 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.872: [goodixmoc] FP_CMD_NUM_STATES entering state 1 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.872: [goodixmoc] FP_CMD_NUM_STATES entering state 1 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.873: [goodixmoc] FP_CMD_NUM_STATES entering state 2 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.873: [goodixmoc] FP_CMD_NUM_STATES entering state 2 410s (process:2211): libfprint-device-DEBUG: 00:54:19.874: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.874: [goodixmoc] enroll entering state 4 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.874: [goodixmoc] FP_CMD_NUM_STATES entering state 0 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.874: [goodixmoc] FP_CMD_NUM_STATES completed successfully 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.874: [goodixmoc] FP_CMD_NUM_STATES entering state 1 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.875: [goodixmoc] FP_CMD_NUM_STATES entering state 1 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.875: [goodixmoc] FP_CMD_NUM_STATES entering state 2 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.875: [goodixmoc] FP_CMD_NUM_STATES entering state 2 410s (process:2211): libfprint-device-DEBUG: 00:54:19.876: Device reported enroll progress, reported 1 of 12 have been completed 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.876: [goodixmoc] enroll entering state 5 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.876: [goodixmoc] FP_CMD_NUM_STATES entering state 0 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.876: [goodixmoc] FP_CMD_NUM_STATES completed successfully 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.876: [goodixmoc] FP_CMD_NUM_STATES entering state 1 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.877: [goodixmoc] FP_CMD_NUM_STATES entering state 1 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.877: [goodixmoc] FP_CMD_NUM_STATES entering state 2 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.878: [goodixmoc] FP_CMD_NUM_STATES entering state 2 410s (process:2211): libfprint-device-DEBUG: 00:54:19.878: Device reported finger status change: FP_FINGER_STATUS_NEEDED 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.878: [goodixmoc] enroll entering state 3 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.878: [goodixmoc] FP_CMD_NUM_STATES entering state 0 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.878: [goodixmoc] FP_CMD_NUM_STATES completed successfully 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.879: [goodixmoc] FP_CMD_NUM_STATES entering state 1 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.879: [goodixmoc] FP_CMD_NUM_STATES entering state 1 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.879: [goodixmoc] FP_CMD_NUM_STATES entering state 2 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.880: [goodixmoc] FP_CMD_NUM_STATES entering state 2 410s (process:2211): libfprint-device-DEBUG: 00:54:19.880: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.880: [goodixmoc] enroll entering state 4 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.880: [goodixmoc] FP_CMD_NUM_STATES entering state 0 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.881: [goodixmoc] FP_CMD_NUM_STATES completed successfully 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.881: [goodixmoc] FP_CMD_NUM_STATES entering state 1 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.881: [goodixmoc] FP_CMD_NUM_STATES entering state 1 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.882: [goodixmoc] FP_CMD_NUM_STATES entering state 2 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.882: [goodixmoc] FP_CMD_NUM_STATES entering state 2 410s (process:2211): libfprint-device-DEBUG: 00:54:19.882: Device reported enroll progress, reported 2 of 12 have been completed 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.882: [goodixmoc] enroll entering state 5 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.882: [goodixmoc] FP_CMD_NUM_STATES entering state 0 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.883: [goodixmoc] FP_CMD_NUM_STATES completed successfully 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.883: [goodixmoc] FP_CMD_NUM_STATES entering state 1 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.883: [goodixmoc] FP_CMD_NUM_STATES entering state 1 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.884: [goodixmoc] FP_CMD_NUM_STATES entering state 2 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.884: [goodixmoc] FP_CMD_NUM_STATES entering state 2 410s (process:2211): libfprint-device-DEBUG: 00:54:19.885: Device reported finger status change: FP_FINGER_STATUS_NEEDED 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.885: [goodixmoc] enroll entering state 3 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.885: [goodixmoc] FP_CMD_NUM_STATES entering state 0 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.885: [goodixmoc] FP_CMD_NUM_STATES completed successfully 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.885: [goodixmoc] FP_CMD_NUM_STATES entering state 1 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.885: [goodixmoc] FP_CMD_NUM_STATES entering state 1 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.886: [goodixmoc] FP_CMD_NUM_STATES entering state 2 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.886: [goodixmoc] FP_CMD_NUM_STATES entering state 2 410s (process:2211): libfprint-device-DEBUG: 00:54:19.887: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.887: [goodixmoc] enroll entering state 4 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.887: [goodixmoc] FP_CMD_NUM_STATES entering state 0 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.887: [goodixmoc] FP_CMD_NUM_STATES completed successfully 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.887: [goodixmoc] FP_CMD_NUM_STATES entering state 1 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.887: [goodixmoc] FP_CMD_NUM_STATES entering state 1 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.888: [goodixmoc] FP_CMD_NUM_STATES entering state 2 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.888: [goodixmoc] FP_CMD_NUM_STATES entering state 2 410s (process:2211): libfprint-device-DEBUG: 00:54:19.889: Device reported enroll progress, reported 3 of 12 have been completed 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.889: [goodixmoc] enroll entering state 5 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.889: [goodixmoc] FP_CMD_NUM_STATES entering state 0 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.889: [goodixmoc] FP_CMD_NUM_STATES completed successfully 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.889: [goodixmoc] FP_CMD_NUM_STATES entering state 1 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.890: [goodixmoc] FP_CMD_NUM_STATES entering state 1 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.890: [goodixmoc] FP_CMD_NUM_STATES entering state 2 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.891: [goodixmoc] FP_CMD_NUM_STATES entering state 2 410s (process:2211): libfprint-device-DEBUG: 00:54:19.891: Device reported finger status change: FP_FINGER_STATUS_NEEDED 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.891: [goodixmoc] enroll entering state 3 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.891: [goodixmoc] FP_CMD_NUM_STATES entering state 0 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.891: [goodixmoc] FP_CMD_NUM_STATES completed successfully 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.891: [goodixmoc] FP_CMD_NUM_STATES entering state 1 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.892: [goodixmoc] FP_CMD_NUM_STATES entering state 1 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.893: [goodixmoc] FP_CMD_NUM_STATES entering state 2 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.893: [goodixmoc] FP_CMD_NUM_STATES entering state 2 410s (process:2211): libfprint-device-DEBUG: 00:54:19.893: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.893: [goodixmoc] enroll entering state 4 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.893: [goodixmoc] FP_CMD_NUM_STATES entering state 0 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.894: [goodixmoc] FP_CMD_NUM_STATES completed successfully 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.894: [goodixmoc] FP_CMD_NUM_STATES entering state 1 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.894: [goodixmoc] FP_CMD_NUM_STATES entering state 1 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.895: [goodixmoc] FP_CMD_NUM_STATES entering state 2 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.895: [goodixmoc] FP_CMD_NUM_STATES entering state 2 410s (process:2211): libfprint-device-DEBUG: 00:54:19.896: Device reported enroll progress, reported 4 of 12 have been completed 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.896: [goodixmoc] enroll entering state 5 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.896: [goodixmoc] FP_CMD_NUM_STATES entering state 0 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.896: [goodixmoc] FP_CMD_NUM_STATES completed successfully 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.896: [goodixmoc] FP_CMD_NUM_STATES entering state 1 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.896: [goodixmoc] FP_CMD_NUM_STATES entering state 1 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.897: [goodixmoc] FP_CMD_NUM_STATES entering state 2 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.897: [goodixmoc] FP_CMD_NUM_STATES entering state 2 410s (process:2211): libfprint-device-DEBUG: 00:54:19.898: Device reported finger status change: FP_FINGER_STATUS_NEEDED 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.898: [goodixmoc] enroll entering state 3 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.898: [goodixmoc] FP_CMD_NUM_STATES entering state 0 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.898: [goodixmoc] FP_CMD_NUM_STATES completed successfully 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.898: [goodixmoc] FP_CMD_NUM_STATES entering state 1 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.899: [goodixmoc] FP_CMD_NUM_STATES entering state 1 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.899: [goodixmoc] FP_CMD_NUM_STATES entering state 2 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.900: [goodixmoc] FP_CMD_NUM_STATES entering state 2 410s (process:2211): libfprint-device-DEBUG: 00:54:19.900: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.900: [goodixmoc] enroll entering state 4 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.900: [goodixmoc] FP_CMD_NUM_STATES entering state 0 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.900: [goodixmoc] FP_CMD_NUM_STATES completed successfully 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.901: [goodixmoc] FP_CMD_NUM_STATES entering state 1 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.901: [goodixmoc] FP_CMD_NUM_STATES entering state 1 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.901: [goodixmoc] FP_CMD_NUM_STATES entering state 2 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.902: [goodixmoc] FP_CMD_NUM_STATES entering state 2 410s (process:2211): libfprint-device-DEBUG: 00:54:19.902: Device reported enroll progress, reported 5 of 12 have been completed 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.902: [goodixmoc] enroll entering state 5 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.902: [goodixmoc] FP_CMD_NUM_STATES entering state 0 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.903: [goodixmoc] FP_CMD_NUM_STATES completed successfully 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.903: [goodixmoc] FP_CMD_NUM_STATES entering state 1 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.903: [goodixmoc] FP_CMD_NUM_STATES entering state 1 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.904: [goodixmoc] FP_CMD_NUM_STATES entering state 2 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.904: [goodixmoc] FP_CMD_NUM_STATES entering state 2 410s (process:2211): libfprint-device-DEBUG: 00:54:19.905: Device reported finger status change: FP_FINGER_STATUS_NEEDED 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.905: [goodixmoc] enroll entering state 3 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.905: [goodixmoc] FP_CMD_NUM_STATES entering state 0 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.905: [goodixmoc] FP_CMD_NUM_STATES completed successfully 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.905: [goodixmoc] FP_CMD_NUM_STATES entering state 1 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.905: [goodixmoc] FP_CMD_NUM_STATES entering state 1 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.906: [goodixmoc] FP_CMD_NUM_STATES entering state 2 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.906: [goodixmoc] FP_CMD_NUM_STATES entering state 2 410s (process:2211): libfprint-device-DEBUG: 00:54:19.907: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.907: [goodixmoc] enroll entering state 4 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.907: [goodixmoc] FP_CMD_NUM_STATES entering state 0 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.907: [goodixmoc] FP_CMD_NUM_STATES completed successfully 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.907: [goodixmoc] FP_CMD_NUM_STATES entering state 1 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.908: [goodixmoc] FP_CMD_NUM_STATES entering state 1 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.908: [goodixmoc] FP_CMD_NUM_STATES entering state 2 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.909: [goodixmoc] FP_CMD_NUM_STATES entering state 2 410s (process:2211): libfprint-device-DEBUG: 00:54:19.909: Device reported enroll progress, reported 6 of 12 have been completed 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.909: [goodixmoc] enroll entering state 5 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.909: [goodixmoc] FP_CMD_NUM_STATES entering state 0 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.909: [goodixmoc] FP_CMD_NUM_STATES completed successfully 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.909: [goodixmoc] FP_CMD_NUM_STATES entering state 1 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.910: [goodixmoc] FP_CMD_NUM_STATES entering state 1 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.910: [goodixmoc] FP_CMD_NUM_STATES entering state 2 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.911: [goodixmoc] FP_CMD_NUM_STATES entering state 2 410s (process:2211): libfprint-device-DEBUG: 00:54:19.911: Device reported finger status change: FP_FINGER_STATUS_NEEDED 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.911: [goodixmoc] enroll entering state 3 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.911: [goodixmoc] FP_CMD_NUM_STATES entering state 0 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.912: [goodixmoc] FP_CMD_NUM_STATES completed successfully 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.912: [goodixmoc] FP_CMD_NUM_STATES entering state 1 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.912: [goodixmoc] FP_CMD_NUM_STATES entering state 1 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.913: [goodixmoc] FP_CMD_NUM_STATES entering state 2 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.913: [goodixmoc] FP_CMD_NUM_STATES entering state 2 410s (process:2211): libfprint-device-DEBUG: 00:54:19.914: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.914: [goodixmoc] enroll entering state 4 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.914: [goodixmoc] FP_CMD_NUM_STATES entering state 0 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.914: [goodixmoc] FP_CMD_NUM_STATES completed successfully 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.914: [goodixmoc] FP_CMD_NUM_STATES entering state 1 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.914: [goodixmoc] FP_CMD_NUM_STATES entering state 1 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.915: [goodixmoc] FP_CMD_NUM_STATES entering state 2 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.915: [goodixmoc] FP_CMD_NUM_STATES entering state 2 410s (process:2211): libfprint-device-DEBUG: 00:54:19.916: Device reported enroll progress, reported 7 of 12 have been completed 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.916: [goodixmoc] enroll entering state 5 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.916: [goodixmoc] FP_CMD_NUM_STATES entering state 0 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.916: [goodixmoc] FP_CMD_NUM_STATES completed successfully 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.916: [goodixmoc] FP_CMD_NUM_STATES entering state 1 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.917: [goodixmoc] FP_CMD_NUM_STATES entering state 1 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.917: [goodixmoc] FP_CMD_NUM_STATES entering state 2 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.917: [goodixmoc] FP_CMD_NUM_STATES entering state 2 410s (process:2211): libfprint-device-DEBUG: 00:54:19.918: Device reported finger status change: FP_FINGER_STATUS_NEEDED 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.918: [goodixmoc] enroll entering state 3 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.918: [goodixmoc] FP_CMD_NUM_STATES entering state 0 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.918: [goodixmoc] FP_CMD_NUM_STATES completed successfully 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.918: [goodixmoc] FP_CMD_NUM_STATES entering state 1 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.919: [goodixmoc] FP_CMD_NUM_STATES entering state 1 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.919: [goodixmoc] FP_CMD_NUM_STATES entering state 2 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.920: [goodixmoc] FP_CMD_NUM_STATES entering state 2 410s (process:2211): libfprint-device-DEBUG: 00:54:19.920: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.920: [goodixmoc] enroll entering state 4 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.920: [goodixmoc] FP_CMD_NUM_STATES entering state 0 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.920: [goodixmoc] FP_CMD_NUM_STATES completed successfully 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.921: [goodixmoc] FP_CMD_NUM_STATES entering state 1 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.921: [goodixmoc] FP_CMD_NUM_STATES entering state 1 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.921: [goodixmoc] FP_CMD_NUM_STATES entering state 2 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.922: [goodixmoc] FP_CMD_NUM_STATES entering state 2 410s (process:2211): libfprint-device-DEBUG: 00:54:19.922: Device reported enroll progress, reported 8 of 12 have been completed 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.922: [goodixmoc] enroll entering state 5 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.922: [goodixmoc] FP_CMD_NUM_STATES entering state 0 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.923: [goodixmoc] FP_CMD_NUM_STATES completed successfully 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.923: [goodixmoc] FP_CMD_NUM_STATES entering state 1 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.923: [goodixmoc] FP_CMD_NUM_STATES entering state 1 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.924: [goodixmoc] FP_CMD_NUM_STATES entering state 2 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.924: [goodixmoc] FP_CMD_NUM_STATES entering state 2 410s (process:2211): libfprint-device-DEBUG: 00:54:19.924: Device reported finger status change: FP_FINGER_STATUS_NEEDED 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.924: [goodixmoc] enroll entering state 3 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.925: [goodixmoc] FP_CMD_NUM_STATES entering state 0 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.925: [goodixmoc] FP_CMD_NUM_STATES completed successfully 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.925: [goodixmoc] FP_CMD_NUM_STATES entering state 1 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.925: [goodixmoc] FP_CMD_NUM_STATES entering state 1 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.926: [goodixmoc] FP_CMD_NUM_STATES entering state 2 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.926: [goodixmoc] FP_CMD_NUM_STATES entering state 2 410s (process:2211): libfprint-device-DEBUG: 00:54:19.927: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.927: [goodixmoc] enroll entering state 4 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.927: [goodixmoc] FP_CMD_NUM_STATES entering state 0 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.927: [goodixmoc] FP_CMD_NUM_STATES completed successfully 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.927: [goodixmoc] FP_CMD_NUM_STATES entering state 1 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.927: [goodixmoc] FP_CMD_NUM_STATES entering state 1 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.928: [goodixmoc] FP_CMD_NUM_STATES entering state 2 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.928: [goodixmoc] FP_CMD_NUM_STATES entering state 2 410s (process:2211): libfprint-device-DEBUG: 00:54:19.929: Device reported enroll progress, reported 9 of 12 have been completed 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.929: [goodixmoc] enroll entering state 5 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.929: [goodixmoc] FP_CMD_NUM_STATES entering state 0 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.929: [goodixmoc] FP_CMD_NUM_STATES completed successfully 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.929: [goodixmoc] FP_CMD_NUM_STATES entering state 1 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.930: [goodixmoc] FP_CMD_NUM_STATES entering state 1 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.930: [goodixmoc] FP_CMD_NUM_STATES entering state 2 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.931: [goodixmoc] FP_CMD_NUM_STATES entering state 2 410s (process:2211): libfprint-device-DEBUG: 00:54:19.931: Device reported finger status change: FP_FINGER_STATUS_NEEDED 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.931: [goodixmoc] enroll entering state 3 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.931: [goodixmoc] FP_CMD_NUM_STATES entering state 0 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.931: [goodixmoc] FP_CMD_NUM_STATES completed successfully 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.931: [goodixmoc] FP_CMD_NUM_STATES entering state 1 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.932: [goodixmoc] FP_CMD_NUM_STATES entering state 1 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.932: [goodixmoc] FP_CMD_NUM_STATES entering state 2 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.933: [goodixmoc] FP_CMD_NUM_STATES entering state 2 410s (process:2211): libfprint-device-DEBUG: 00:54:19.933: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.933: [goodixmoc] enroll entering state 4 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.933: [goodixmoc] FP_CMD_NUM_STATES entering state 0 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.933: [goodixmoc] FP_CMD_NUM_STATES completed successfully 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.934: [goodixmoc] FP_CMD_NUM_STATES entering state 1 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.934: [goodixmoc] FP_CMD_NUM_STATES entering state 1 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.934: [goodixmoc] FP_CMD_NUM_STATES entering state 2 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.935: [goodixmoc] FP_CMD_NUM_STATES entering state 2 410s (process:2211): libfprint-device-DEBUG: 00:54:19.935: Device reported enroll progress, reported 10 of 12 have been completed 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.935: [goodixmoc] enroll entering state 5 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.935: [goodixmoc] FP_CMD_NUM_STATES entering state 0 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.936: [goodixmoc] FP_CMD_NUM_STATES completed successfully 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.936: [goodixmoc] FP_CMD_NUM_STATES entering state 1 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.936: [goodixmoc] FP_CMD_NUM_STATES entering state 1 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.937: [goodixmoc] FP_CMD_NUM_STATES entering state 2 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.937: [goodixmoc] FP_CMD_NUM_STATES entering state 2 410s (process:2211): libfprint-device-DEBUG: 00:54:19.937: Device reported finger status change: FP_FINGER_STATUS_NEEDED 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.937: [goodixmoc] enroll entering state 3 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.937: [goodixmoc] FP_CMD_NUM_STATES entering state 0 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.938: [goodixmoc] FP_CMD_NUM_STATES completed successfully 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.938: [goodixmoc] FP_CMD_NUM_STATES entering state 1 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.938: [goodixmoc] FP_CMD_NUM_STATES entering state 1 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.939: [goodixmoc] FP_CMD_NUM_STATES entering state 2 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.939: [goodixmoc] FP_CMD_NUM_STATES entering state 2 410s (process:2211): libfprint-device-DEBUG: 00:54:19.940: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.940: [goodixmoc] enroll entering state 4 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.940: [goodixmoc] FP_CMD_NUM_STATES entering state 0 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.940: [goodixmoc] FP_CMD_NUM_STATES completed successfully 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.940: [goodixmoc] FP_CMD_NUM_STATES entering state 1 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.941: [goodixmoc] FP_CMD_NUM_STATES entering state 1 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.941: [goodixmoc] FP_CMD_NUM_STATES entering state 2 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.942: [goodixmoc] FP_CMD_NUM_STATES entering state 2 410s (process:2211): libfprint-device-DEBUG: 00:54:19.942: Device reported enroll progress, reported 11 of 12 have been completed 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.942: [goodixmoc] enroll entering state 5 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.942: [goodixmoc] FP_CMD_NUM_STATES entering state 0 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.942: [goodixmoc] FP_CMD_NUM_STATES completed successfully 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.943: [goodixmoc] FP_CMD_NUM_STATES entering state 1 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.943: [goodixmoc] FP_CMD_NUM_STATES entering state 1 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.944: [goodixmoc] FP_CMD_NUM_STATES entering state 2 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.944: [goodixmoc] FP_CMD_NUM_STATES entering state 2 410s (process:2211): libfprint-device-DEBUG: 00:54:19.945: Device reported finger status change: FP_FINGER_STATUS_NEEDED 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.945: [goodixmoc] enroll entering state 3 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.945: [goodixmoc] FP_CMD_NUM_STATES entering state 0 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.945: [goodixmoc] FP_CMD_NUM_STATES completed successfully 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.945: [goodixmoc] FP_CMD_NUM_STATES entering state 1 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.946: [goodixmoc] FP_CMD_NUM_STATES entering state 1 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.946: [goodixmoc] FP_CMD_NUM_STATES entering state 2 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.946: [goodixmoc] FP_CMD_NUM_STATES entering state 2 410s (process:2211): libfprint-device-DEBUG: 00:54:19.947: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.947: [goodixmoc] enroll entering state 4 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.947: [goodixmoc] FP_CMD_NUM_STATES entering state 0 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.947: [goodixmoc] FP_CMD_NUM_STATES completed successfully 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.947: [goodixmoc] FP_CMD_NUM_STATES entering state 1 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.948: [goodixmoc] FP_CMD_NUM_STATES entering state 1 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.948: [goodixmoc] FP_CMD_NUM_STATES entering state 2 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.949: [goodixmoc] FP_CMD_NUM_STATES entering state 2 410s (process:2211): libfprint-device-DEBUG: 00:54:19.949: Device reported enroll progress, reported 12 of 12 have been completed 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.949: [goodixmoc] enroll entering state 6 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.949: [goodixmoc] FP_CMD_NUM_STATES entering state 0 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.949: [goodixmoc] FP_CMD_NUM_STATES completed successfully 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.950: [goodixmoc] FP_CMD_NUM_STATES entering state 1 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.950: [goodixmoc] FP_CMD_NUM_STATES entering state 1 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.951: [goodixmoc] FP_CMD_NUM_STATES entering state 2 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.951: [goodixmoc] FP_CMD_NUM_STATES entering state 2 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.952: [goodixmoc] enroll entering state 7 410s (process:2211): libfprint-goodixmoc-DEBUG: 00:54:19.952: user_id: FP1-00000000-0-00000000-nobody, user_id_len: 30, finger: 1 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.952: [goodixmoc] FP_CMD_NUM_STATES entering state 0 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.952: [goodixmoc] FP_CMD_NUM_STATES completed successfully 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.952: [goodixmoc] FP_CMD_NUM_STATES entering state 1 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.952: [goodixmoc] FP_CMD_NUM_STATES entering state 1 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.953: [goodixmoc] FP_CMD_NUM_STATES entering state 2 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.953: [goodixmoc] FP_CMD_NUM_STATES entering state 2 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.954: [goodixmoc] enroll entering state 8 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.954: [goodixmoc] FP_CMD_NUM_STATES entering state 0 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.954: [goodixmoc] FP_CMD_NUM_STATES completed successfully 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.954: [goodixmoc] FP_CMD_NUM_STATES entering state 1 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.955: [goodixmoc] FP_CMD_NUM_STATES entering state 1 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.955: [goodixmoc] FP_CMD_NUM_STATES entering state 2 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.955: [goodixmoc] FP_CMD_NUM_STATES entering state 2 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.956: [goodixmoc] enroll completed successfully 410s (process:2211): libfprint-goodixmoc-DEBUG: 00:54:19.956: Enrollment complete! 410s (process:2211): libfprint-device-DEBUG: 00:54:19.956: Device reported enroll completion 410s (process:2211): libfprint-device-DEBUG: 00:54:19.956: Device reported finger status change: FP_FINGER_STATUS_NONE 410s (process:2211): libfprint-device-DEBUG: 00:54:19.956: Print for finger FP_FINGER_UNKNOWN enrolled 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.956: [goodixmoc] FP_CMD_NUM_STATES completed successfully 410s (process:2211): libfprint-device-DEBUG: 00:54:19.956: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 410s (process:2211): libfprint-device-DEBUG: 00:54:19.956: Not updating temperature model, device can run continuously! 410s (process:2211): libfprint-goodixmoc-DEBUG: 00:54:19.956: 7399828017541: ../libfprint/drivers/goodixmoc/goodix.c:1539 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.956: [goodixmoc] FP_CMD_NUM_STATES entering state 0 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.957: [goodixmoc] FP_CMD_NUM_STATES entering state 1 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.957: [goodixmoc] FP_CMD_NUM_STATES entering state 1 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.957: [goodixmoc] FP_CMD_NUM_STATES entering state 2 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.958: [goodixmoc] FP_CMD_NUM_STATES entering state 2 410s (process:2211): libfprint-goodixmoc-DEBUG: 00:54:19.958: Query complete! 410s (process:2211): libfprint-device-DEBUG: 00:54:19.958: Device reported listing completion 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.958: [goodixmoc] FP_CMD_NUM_STATES completed successfully 410s (process:2211): libfprint-device-DEBUG: 00:54:19.958: Completing action FPI_DEVICE_ACTION_LIST in idle! 410s (process:2211): libfprint-device-DEBUG: 00:54:19.958: Not updating temperature model, device can run continuously! 410s (process:2211): libfprint-device-DEBUG: 00:54:19.959: Not updating temperature model, device can run continuously! 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.959: [goodixmoc] verify entering state 0 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.959: [goodixmoc] FP_CMD_NUM_STATES entering state 0 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.959: [goodixmoc] FP_CMD_NUM_STATES entering state 1 410s (process:2211): libfprint-SSM-DEBUG: 00:54:19.959: [goodixmoc] FP_CMD_NUM_STATES entering state 1 411s (process:2211): libfprint-SSM-DEBUG: 00:54:19.960: [goodixmoc] FP_CMD_NUM_STATES entering state 2 411s (process:2211): libfprint-SSM-DEBUG: 00:54:19.960: [goodixmoc] FP_CMD_NUM_STATES entering state 2 411s (process:2211): libfprint-SSM-DEBUG: 00:54:19.961: [goodixmoc] verify entering state 1 411s (process:2211): libfprint-device-DEBUG: 00:54:19.961: Device reported finger status change: FP_FINGER_STATUS_NEEDED 411s (process:2211): libfprint-SSM-DEBUG: 00:54:19.961: [goodixmoc] FP_CMD_NUM_STATES entering state 0 411s (process:2211): libfprint-SSM-DEBUG: 00:54:19.961: [goodixmoc] FP_CMD_NUM_STATES completed successfully 411s (process:2211): libfprint-SSM-DEBUG: 00:54:19.961: [goodixmoc] FP_CMD_NUM_STATES entering state 1 411s (process:2211): libfprint-SSM-DEBUG: 00:54:19.961: [goodixmoc] FP_CMD_NUM_STATES entering state 1 411s (process:2211): libfprint-SSM-DEBUG: 00:54:19.962: [goodixmoc] FP_CMD_NUM_STATES entering state 2 411s (process:2211): libfprint-SSM-DEBUG: 00:54:19.962: [goodixmoc] FP_CMD_NUM_STATES entering state 2 411s (process:2211): libfprint-device-DEBUG: 00:54:19.963: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 411s (process:2211): libfprint-SSM-DEBUG: 00:54:19.963: [goodixmoc] verify entering state 2 411s (process:2211): libfprint-SSM-DEBUG: 00:54:19.963: [goodixmoc] FP_CMD_NUM_STATES entering state 0 411s (process:2211): libfprint-SSM-DEBUG: 00:54:19.963: [goodixmoc] FP_CMD_NUM_STATES completed successfully 411s (process:2211): libfprint-SSM-DEBUG: 00:54:19.963: [goodixmoc] FP_CMD_NUM_STATES entering state 1 411s (process:2211): libfprint-SSM-DEBUG: 00:54:19.964: [goodixmoc] FP_CMD_NUM_STATES entering state 1 411s (process:2211): libfprint-SSM-DEBUG: 00:54:19.964: [goodixmoc] FP_CMD_NUM_STATES entering state 2 411s (process:2211): libfprint-SSM-DEBUG: 00:54:19.964: [goodixmoc] FP_CMD_NUM_STATES entering state 2 411s (process:2211): libfprint-DEBUG: 00:54:19.965: match, score: 28, study: 0 411s (process:2211): libfprint-device-DEBUG: 00:54:19.965: Device reported verify result 411s (process:2211): libfprint-SSM-DEBUG: 00:54:19.965: [goodixmoc] verify entering state 3 411s (process:2211): libfprint-SSM-DEBUG: 00:54:19.965: [goodixmoc] FP_CMD_NUM_STATES entering state 0 411s (process:2211): libfprint-SSM-DEBUG: 00:54:19.965: [goodixmoc] FP_CMD_NUM_STATES completed successfully 411s (process:2211): libfprint-SSM-DEBUG: 00:54:19.965: [goodixmoc] FP_CMD_NUM_STATES entering state 1 411s (process:2211): libfprint-SSM-DEBUG: 00:54:19.966: [goodixmoc] FP_CMD_NUM_STATES entering state 1 411s (process:2211): libfprint-SSM-DEBUG: 00:54:19.966: [goodixmoc] FP_CMD_NUM_STATES entering state 2 411s (process:2211): libfprint-SSM-DEBUG: 00:54:19.967: [goodixmoc] FP_CMD_NUM_STATES entering state 2 411s (process:2211): libfprint-SSM-DEBUG: 00:54:19.967: [goodixmoc] verify completed successfully 411s (process:2211): libfprint-goodixmoc-DEBUG: 00:54:19.967: Verify complete! 411s (process:2211): libfprint-device-DEBUG: 00:54:19.967: Device reported verify completion 411s (process:2211): libfprint-device-DEBUG: 00:54:19.967: Device reported finger status change: FP_FINGER_STATUS_NONE 411s (process:2211): libfprint-SSM-DEBUG: 00:54:19.967: [goodixmoc] FP_CMD_NUM_STATES completed successfully 411s (process:2211): libfprint-device-DEBUG: 00:54:19.967: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 411s (process:2211): libfprint-device-DEBUG: 00:54:19.967: Not updating temperature model, device can run continuously! 411s (process:2211): libfprint-device-DEBUG: 00:54:19.968: Not updating temperature model, device can run continuously! 411s (process:2211): libfprint-SSM-DEBUG: 00:54:19.968: [goodixmoc] verify entering state 0 411s (process:2211): libfprint-SSM-DEBUG: 00:54:19.968: [goodixmoc] FP_CMD_NUM_STATES entering state 0 411s (process:2211): libfprint-SSM-DEBUG: 00:54:19.968: [goodixmoc] FP_CMD_NUM_STATES entering state 1 411s (process:2211): libfprint-SSM-DEBUG: 00:54:19.969: [goodixmoc] FP_CMD_NUM_STATES entering state 1 411s (process:2211): libfprint-SSM-DEBUG: 00:54:19.969: [goodixmoc] FP_CMD_NUM_STATES entering state 2 411s (process:2211): libfprint-SSM-DEBUG: 00:54:19.969: [goodixmoc] FP_CMD_NUM_STATES entering state 2 411s (process:2211): libfprint-SSM-DEBUG: 00:54:19.970: [goodixmoc] verify entering state 1 411s (process:2211): libfprint-device-DEBUG: 00:54:19.970: Device reported finger status change: FP_FINGER_STATUS_NEEDED 411s (process:2211): libfprint-SSM-DEBUG: 00:54:19.970: [goodixmoc] FP_CMD_NUM_STATES entering state 0 411s (process:2211): libfprint-SSM-DEBUG: 00:54:19.970: [goodixmoc] FP_CMD_NUM_STATES completed successfully 411s (process:2211): libfprint-SSM-DEBUG: 00:54:19.970: [goodixmoc] FP_CMD_NUM_STATES entering state 1 411s (process:2211): libfprint-SSM-DEBUG: 00:54:19.971: [goodixmoc] FP_CMD_NUM_STATES entering state 1 411s (process:2211): libfprint-SSM-DEBUG: 00:54:19.971: [goodixmoc] FP_CMD_NUM_STATES entering state 2 411s (process:2211): libfprint-SSM-DEBUG: 00:54:19.972: [goodixmoc] FP_CMD_NUM_STATES entering state 2 411s (process:2211): libfprint-device-DEBUG: 00:54:19.972: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 411s (process:2211): libfprint-SSM-DEBUG: 00:54:19.972: [goodixmoc] verify entering state 2 411s (process:2211): libfprint-SSM-DEBUG: 00:54:19.972: [goodixmoc] FP_CMD_NUM_STATES entering state 0 411s (process:2211): libfprint-SSM-DEBUG: 00:54:19.972: [goodixmoc] FP_CMD_NUM_STATES completed successfully 411s (process:2211): libfprint-SSM-DEBUG: 00:54:19.972: [goodixmoc] FP_CMD_NUM_STATES entering state 1 411s (process:2211): libfprint-SSM-DEBUG: 00:54:19.973: [goodixmoc] FP_CMD_NUM_STATES entering state 1 411s (process:2211): libfprint-SSM-DEBUG: 00:54:19.973: [goodixmoc] FP_CMD_NUM_STATES entering state 2 411s (process:2211): libfprint-SSM-DEBUG: 00:54:19.974: [goodixmoc] FP_CMD_NUM_STATES entering state 2 411s (process:2211): libfprint-DEBUG: 00:54:19.974: match, score: 35, study: 0 411s (process:2211): libfprint-device-DEBUG: 00:54:19.974: Device reported identify result 411s (process:2211): libfprint-SSM-DEBUG: 00:54:19.974: [goodixmoc] verify entering state 3 411s (process:2211): libfprint-SSM-DEBUG: 00:54:19.974: [goodixmoc] FP_CMD_NUM_STATES entering state 0 411s (process:2211): libfprint-SSM-DEBUG: 00:54:19.975: [goodixmoc] FP_CMD_NUM_STATES completed successfully 411s (process:2211): libfprint-SSM-DEBUG: 00:54:19.975: [goodixmoc] FP_CMD_NUM_STATES entering state 1 411s (process:2211): libfprint-SSM-DEBUG: 00:54:19.975: [goodixmoc] FP_CMD_NUM_STATES entering state 1 411s (process:2211): libfprint-SSM-DEBUG: 00:54:19.976: [goodixmoc] FP_CMD_NUM_STATES entering state 2 411s (process:2211): libfprint-SSM-DEBUG: 00:54:19.976: [goodixmoc] FP_CMD_NUM_STATES entering state 2 411s (process:2211): libfprint-SSM-DEBUG: 00:54:19.977: [goodixmoc] verify completed successfully 411s (process:2211): libfprint-goodixmoc-DEBUG: 00:54:19.977: Verify complete! 411s (process:2211): libfprint-device-DEBUG: 00:54:19.977: Device reported identify completion 411s (process:2211): libfprint-device-DEBUG: 00:54:19.977: Device reported finger status change: FP_FINGER_STATUS_NONE 411s (process:2211): libfprint-SSM-DEBUG: 00:54:19.977: [goodixmoc] FP_CMD_NUM_STATES completed successfully 411s (process:2211): libfprint-device-DEBUG: 00:54:19.977: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 411s (process:2211): libfprint-device-DEBUG: 00:54:19.977: Not updating temperature model, device can run continuously! 411s (process:2211): libfprint-SSM-DEBUG: 00:54:19.977: [goodixmoc] FP_CMD_NUM_STATES entering state 0 411s (process:2211): libfprint-SSM-DEBUG: 00:54:19.978: [goodixmoc] FP_CMD_NUM_STATES entering state 1 411s (process:2211): libfprint-SSM-DEBUG: 00:54:19.978: [goodixmoc] FP_CMD_NUM_STATES entering state 1 411s (process:2211): libfprint-SSM-DEBUG: 00:54:19.979: [goodixmoc] FP_CMD_NUM_STATES entering state 2 411s (process:2211): libfprint-SSM-DEBUG: 00:54:19.979: [goodixmoc] FP_CMD_NUM_STATES entering state 2 411s (process:2211): libfprint-goodixmoc-DEBUG: 00:54:19.979: Successfully deleted enrolled user 411s (process:2211): libfprint-device-DEBUG: 00:54:19.979: Device reported deletion completion 411s (process:2211): libfprint-SSM-DEBUG: 00:54:19.980: [goodixmoc] FP_CMD_NUM_STATES completed successfully 411s (process:2211): libfprint-device-DEBUG: 00:54:19.980: Completing action FPI_DEVICE_ACTION_DELETE in idle! 411s (process:2211): libfprint-device-DEBUG: 00:54:19.980: Not updating temperature model, device can run continuously! 411s (process:2211): libfprint-device-DEBUG: 00:54:19.980: Device reported close completion 411s (process:2211): libfprint-device-DEBUG: 00:54:19.980: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 411s (process:2211): libfprint-device-DEBUG: 00:54:19.980: Not updating temperature model, device can run continuously! 411s enrolling 411s enroll progress: (<__gi__.FpiDeviceGoodixMoc object at 0xeeaf59c8 (FpiDeviceGoodixMoc at 0x1d15a30)>, 1, None, None, None) 411s enroll progress: (<__gi__.FpiDeviceGoodixMoc object at 0xeeaf59c8 (FpiDeviceGoodixMoc at 0x1d15a30)>, 2, None, None, None) 411s enroll progress: (<__gi__.FpiDeviceGoodixMoc object at 0xeeaf59c8 (FpiDeviceGoodixMoc at 0x1d15a30)>, 3, None, None, None) 411s enroll progress: (<__gi__.FpiDeviceGoodixMoc object at 0xeeaf59c8 (FpiDeviceGoodixMoc at 0x1d15a30)>, 4, None, None, None) 411s enroll progress: (<__gi__.FpiDeviceGoodixMoc object at 0xeeaf59c8 (FpiDeviceGoodixMoc at 0x1d15a30)>, 5, None, None, None) 411s enroll progress: (<__gi__.FpiDeviceGoodixMoc object at 0xeeaf59c8 (FpiDeviceGoodixMoc at 0x1d15a30)>, 6, None, None, None) 411s enroll progress: (<__gi__.FpiDeviceGoodixMoc object at 0xeeaf59c8 (FpiDeviceGoodixMoc at 0x1d15a30)>, 7, None, None, None) 411s enroll progress: (<__gi__.FpiDeviceGoodixMoc object at 0xeeaf59c8 (FpiDeviceGoodixMoc at 0x1d15a30)>, 8, None, None, None) 411s enroll progress: (<__gi__.FpiDeviceGoodixMoc object at 0xeeaf59c8 (FpiDeviceGoodixMoc at 0x1d15a30)>, 9, None, None, None) 411s enroll progress: (<__gi__.FpiDeviceGoodixMoc object at 0xeeaf59c8 (FpiDeviceGoodixMoc at 0x1d15a30)>, 10, None, None, None) 411s enroll progress: (<__gi__.FpiDeviceGoodixMoc object at 0xeeaf59c8 (FpiDeviceGoodixMoc at 0x1d15a30)>, 11, None, None, None) 411s enroll progress: (<__gi__.FpiDeviceGoodixMoc object at 0xeeaf59c8 (FpiDeviceGoodixMoc at 0x1d15a30)>, 12, None, None, None) 411s enroll done 411s listing 411s listing done 411s verifying 411s verify done 411s async identifying 411s indentification_done: 411s deleting 411s delete done 411s ** (umockdev-run:2207): DEBUG: 00:54:20.002: umockdev.vala:154: Removing test bed /tmp/umockdev.UHUD22 411s (umockdev-run:2207): GLib-DEBUG: 00:54:20.010: unsetenv() is not thread-safe and should not be used after threads are created 411s PASS: libfprint-2/driver-goodixmoc.test 411s Running test: libfprint-2/fpi-device.test 411s TAP version 14 411s # random seed: R02Sf03296af2d23d7874e42552dd2ab9a32 411s 1..97 411s # Start of driver tests 411s ok 1 /driver/get_driver 411s ok 2 /driver/get_device_id 411s ok 3 /driver/get_name 411s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 411s # 411s # libfprint-device-DEBUG: Device reported open completion 411s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 411s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 411s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 411s # 411s # libfprint-device-DEBUG: Device reported close completion 411s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 411s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 411s ok 4 /driver/is_open 411s ok 5 /driver/get_nr_enroll_stages 411s ok 6 /driver/set_nr_enroll_stages 411s ok 7 /driver/supports_identify 411s ok 8 /driver/supports_capture 411s ok 9 /driver/has_storage 411s ok 10 /driver/do_not_support_identify 411s ok 11 /driver/do_not_support_capture 411s ok 12 /driver/has_not_storage 411s ok 13 /driver/get_usb_device 411s ok 14 /driver/get_virtual_env 411s ok 15 /driver/get_driver_data 411s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_probe: Device Virtual device for debugging in action FPI_DEVICE_ACTION_PROBE 411s # 411s # libfprint-device-DEBUG: Device reported probe completion 411s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 411s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 411s ok 16 /driver/initial_features 411s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_probe: Device Probed device name in action FPI_DEVICE_ACTION_PROBE 411s # 411s # libfprint-device-DEBUG: Device reported probe completion 411s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 411s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 411s ok 17 /driver/probe 411s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 411s # 411s # libfprint-device-DEBUG: Device reported open completion 411s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 411s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 411s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 411s # 411s # libfprint-device-DEBUG: Device reported close completion 411s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 411s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 411s ok 18 /driver/open 411s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 411s # 411s # libfprint-device-DEBUG: Device reported open completion 411s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 411s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 411s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 411s # 411s # libfprint-device-DEBUG: Device reported close completion 411s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 411s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 411s ok 19 /driver/close 411s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 411s # 411s # libfprint-device-DEBUG: Device reported open completion 411s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 411s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 411s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 411s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_enroll: Device Virtual device for debugging in action FPI_DEVICE_ACTION_ENROLL 411s # 411s # libfprint-device-DEBUG: Device reported enroll completion 411s # libfprint-device-DEBUG: Print for finger FP_FINGER_UNKNOWN enrolled 411s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 411s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 411s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 411s # 411s # libfprint-device-DEBUG: Device reported close completion 411s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 411s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 411s ok 20 /driver/enroll 411s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 411s # 411s # libfprint-device-DEBUG: Device reported open completion 411s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 411s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 411s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 411s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_verify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_VERIFY 411s # 411s # libfprint-device-DEBUG: Device reported verify result 411s # libfprint-device-DEBUG: Device reported verify completion 411s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 411s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 411s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 411s # 411s # libfprint-device-DEBUG: Device reported close completion 411s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 411s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 411s ok 21 /driver/verify 411s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 411s # 411s # libfprint-device-DEBUG: Device reported open completion 411s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 411s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 411s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 411s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_identify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY 411s # 411s # libfprint-device-DEBUG: Device reported identify result 411s # libfprint-device-DEBUG: Device reported identify completion 411s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 411s # libfprint-device-DEBUG: Updated temperature model after 0.02 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 411s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 411s # 411s # libfprint-device-DEBUG: Device reported close completion 411s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 411s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 411s ok 22 /driver/identify 411s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 411s # 411s # libfprint-device-DEBUG: Device reported open completion 411s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 411s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 411s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 411s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_capture: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CAPTURE 411s # 411s # libfprint-device-DEBUG: Device reported capture completion 411s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CAPTURE in idle! 411s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 411s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 411s # 411s # libfprint-device-DEBUG: Device reported close completion 411s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 411s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 411s ok 23 /driver/capture 411s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 411s # 411s # libfprint-device-DEBUG: Device reported open completion 411s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 411s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 411s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_list: Device Virtual device for debugging in action FPI_DEVICE_ACTION_LIST 411s # 411s # libfprint-device-DEBUG: Device reported listing completion 411s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_LIST in idle! 411s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 411s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 411s # 411s # libfprint-device-DEBUG: Device reported close completion 411s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 411s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 411s ok 24 /driver/list 411s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 411s # 411s # libfprint-device-DEBUG: Device reported open completion 411s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 411s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 411s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_delete: Device Virtual device for debugging in action FPI_DEVICE_ACTION_DELETE 411s # 411s # libfprint-device-DEBUG: Device reported deletion completion 411s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_DELETE in idle! 411s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 411s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 411s # 411s # libfprint-device-DEBUG: Device reported close completion 411s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 411s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 411s ok 25 /driver/delete 411s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 411s # 411s # libfprint-device-DEBUG: Device reported open completion 411s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 411s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 411s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_clear_storage: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLEAR_STORAGE 411s # 411s # libfprint-device-DEBUG: Device reported deletion completion 411s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 411s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 411s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 411s # 411s # libfprint-device-DEBUG: Device reported close completion 411s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 411s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 411s ok 26 /driver/clear_storage 411s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 411s # 411s # libfprint-device-DEBUG: Device reported open completion 411s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 411s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 411s # libfprint-device-DEBUG: Idle cancelling on ongoing operation! 411s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_cancel: Device Virtual device for debugging in action FPI_DEVICE_ACTION_DELETE 411s # 411s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_delete: Device Virtual device for debugging in action FPI_DEVICE_ACTION_DELETE 411s # 411s # libfprint-device-DEBUG: Device reported deletion completion 411s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_DELETE in idle! 411s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 411s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 411s # 411s # libfprint-device-DEBUG: Device reported close completion 411s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 411s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 411s ok 27 /driver/cancel 411s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 411s # 411s # libfprint-device-DEBUG: Device reported open completion 411s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 411s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 411s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 411s # libfprint-device-DEBUG: Idle cancelling on ongoing operation! 411s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_cancel: Device Virtual device for debugging in action FPI_DEVICE_ACTION_VERIFY 411s # 411s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_suspend: Device Virtual device for debugging in action FPI_DEVICE_ACTION_VERIFY 411s # 411s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_resume: Device Virtual device for debugging in action FPI_DEVICE_ACTION_VERIFY 411s # 411s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_verify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_VERIFY 411s # 411s # libfprint-device-DEBUG: Device reported verify result 411s # libfprint-device-DEBUG: Device reported verify completion 411s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 411s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 411s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 411s # 411s # libfprint-device-DEBUG: Device reported close completion 411s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 411s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 411s ok 28 /driver/critical 411s ok 29 /driver/get_current_action 411s ok 30 /driver/timeout 411s ok 31 /driver/error_types 411s ok 32 /driver/retry_error_types 411s # Start of get_scan_type tests 411s ok 33 /driver/get_scan_type/press 411s ok 34 /driver/get_scan_type/swipe 411s # End of get_scan_type tests 411s # Start of set_scan_type tests 411s ok 35 /driver/set_scan_type/press 411s ok 36 /driver/set_scan_type/swipe 411s # End of set_scan_type tests 411s # Start of finger_status tests 411s ok 37 /driver/finger_status/inactive 411s # libfprint-device-DEBUG: Device reported finger status change: FP_FINGER_STATUS_NEEDED 411s ok 38 /driver/finger_status/waiting 411s # libfprint-device-DEBUG: Device reported finger status change: FP_FINGER_STATUS_PRESENT 411s ok 39 /driver/finger_status/present 411s # libfprint-device-DEBUG: Device reported finger status change: FP_FINGER_STATUS_NEEDED 411s # libfprint-device-DEBUG: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 411s # libfprint-device-DEBUG: Device reported finger status change: FP_FINGER_STATUS_PRESENT 411s # libfprint-device-DEBUG: Device reported finger status change: FP_FINGER_STATUS_NONE 411s ok 40 /driver/finger_status/changes 411s # End of finger_status tests 411s # Start of features tests 411s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_probe: Device Virtual device for debugging in action FPI_DEVICE_ACTION_PROBE 411s # 411s # libfprint-device-DEBUG: Device reported probe completion 411s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 411s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 411s ok 41 /driver/features/probe_updates 411s # End of features tests 411s # Start of initial_features tests 411s ok 42 /driver/initial_features/none 411s ok 43 /driver/initial_features/no_capture 411s ok 44 /driver/initial_features/no_verify 411s ok 45 /driver/initial_features/no_identify 411s ok 46 /driver/initial_features/no_storage 411s ok 47 /driver/initial_features/no_list 411s ok 48 /driver/initial_features/no_delete 411s ok 49 /driver/initial_features/no_clear 411s # End of initial_features tests 411s # Start of probe tests 411s # libfprint-device-DEBUG: Device reported probe completion 411s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 411s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 411s ok 50 /driver/probe/error 411s # libfprint-device-DEBUG: Device reported generic error (The operation is not supported on this device!) during action; action was: FPI_DEVICE_ACTION_PROBE 411s # libfprint-device-DEBUG: Device reported probe completion 411s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 411s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 411s ok 51 /driver/probe/action_error 411s # End of probe tests 411s # Start of open tests 411s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 411s # 411s # libfprint-device-DEBUG: Device reported open completion 411s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 411s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 411s ok 52 /driver/open/error 411s # End of open tests 411s # Start of close tests 411s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 411s # 411s # libfprint-device-DEBUG: Device reported open completion 411s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 411s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 411s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 411s # 411s # libfprint-device-DEBUG: Device reported close completion 411s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 411s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 411s ok 53 /driver/close/error 411s # End of close tests 411s # Start of enroll tests 411s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 411s # 411s # libfprint-device-DEBUG: Device reported open completion 411s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 411s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 411s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 411s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_enroll: Device Virtual device for debugging in action FPI_DEVICE_ACTION_ENROLL 411s # 411s # libfprint-device-DEBUG: Device reported enroll completion 411s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 411s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 411s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 411s # 411s # libfprint-device-DEBUG: Device reported close completion 411s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 411s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 411s ok 54 /driver/enroll/error 411s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 411s # 411s # libfprint-device-DEBUG: Device reported open completion 411s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 411s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 411s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 411s # libfprint-device-DEBUG: Device reported enroll progress, reported 2064160774 of 1866937896 have been completed 411s # libfprint-device-DEBUG: Device reported enroll progress, reported 1971788273 of 1866937896 have been completed 411s # libfprint-device-DEBUG: Device reported enroll progress, reported 1950845126 of 1866937896 have been completed 411s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_enroll: Device Virtual device for debugging in action FPI_DEVICE_ACTION_ENROLL 411s # 411s # libfprint-device-DEBUG: Device reported enroll completion 411s # libfprint-device-DEBUG: Print for finger FP_FINGER_UNKNOWN enrolled 411s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 411s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 411s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 411s # 411s # libfprint-device-DEBUG: Device reported close completion 411s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 411s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 411s ok 55 /driver/enroll/progress 411s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 411s # 411s # libfprint-device-DEBUG: Device reported open completion 411s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 411s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 411s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 411s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_enroll: Device Virtual device for debugging in action FPI_DEVICE_ACTION_ENROLL 411s # 411s # libfprint-device-DEBUG: Device reported enroll completion 411s # libfprint-device-DEBUG: Print for finger FP_FINGER_UNKNOWN enrolled 411s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 411s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 411s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 411s # 411s # libfprint-device-DEBUG: Device reported close completion 411s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 411s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 411s ok 56 /driver/enroll/update_nbis 411s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 411s # 411s # libfprint-device-DEBUG: Device reported open completion 411s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 411s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 411s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 411s # 411s # libfprint-device-DEBUG: Device reported close completion 411s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 411s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 411s ok 57 /driver/enroll/update_nbis_wrong_device 411s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 411s # 411s # libfprint-device-DEBUG: Device reported open completion 411s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 411s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 411s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 411s # 411s # libfprint-device-DEBUG: Device reported close completion 411s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 411s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 411s ok 58 /driver/enroll/update_nbis_wrong_driver 411s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 411s # 411s # libfprint-device-DEBUG: Device reported open completion 411s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 411s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 411s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 411s # 411s # libfprint-device-DEBUG: Device reported close completion 411s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 411s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 411s ok 59 /driver/enroll/update_nbis_missing_feature 411s # Start of error tests 411s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 411s # 411s # libfprint-device-DEBUG: Device reported open completion 411s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 411s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 411s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 411s # libfprint-device-DEBUG: Device reported enroll completion 411s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 411s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 411s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 411s # libfprint-device-DEBUG: Device reported enroll completion 411s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 411s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 411s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 411s # libfprint-device-DEBUG: Device reported enroll completion 411s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 411s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 411s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 411s # 411s # libfprint-device-DEBUG: Device reported close completion 411s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 411s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 411s ok 60 /driver/enroll/error/no_print 411s # End of error tests 411s # End of enroll tests 411s # Start of verify tests 411s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 411s # 411s # libfprint-device-DEBUG: Device reported open completion 411s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 411s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 411s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 411s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_verify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_VERIFY 411s # 411s # libfprint-device-DEBUG: Device reported verify result 411s # libfprint-device-DEBUG: Device reported verify completion 411s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 411s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 411s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 411s # 411s # libfprint-device-DEBUG: Device reported close completion 411s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 411s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 411s ok 61 /driver/verify/fail 411s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 411s # 411s # libfprint-device-DEBUG: Device reported open completion 411s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 411s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 411s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 411s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_verify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_VERIFY 411s # 411s # libfprint-device-DEBUG: Device reported verify result 411s # libfprint-device-DEBUG: Device reported verify completion 411s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 411s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 411s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 411s # 411s # libfprint-device-DEBUG: Device reported close completion 411s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 411s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 411s ok 62 /driver/verify/retry 411s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 411s # 411s # libfprint-device-DEBUG: Device reported open completion 411s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 411s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 411s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 411s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_verify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_VERIFY 411s # 411s # libfprint-device-DEBUG: Device reported verify completion 411s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 411s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 411s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 411s # 411s # libfprint-device-DEBUG: Device reported close completion 411s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 411s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 411s ok 63 /driver/verify/error 411s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 411s # 411s # libfprint-device-DEBUG: Device reported open completion 411s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 411s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 411s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 411s # 411s # libfprint-device-DEBUG: Device reported close completion 411s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 411s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 411s ok 64 /driver/verify/not_supported 411s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 411s # 411s # libfprint-device-DEBUG: Device reported open completion 411s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 411s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 411s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 411s # libfprint-device-DEBUG: Device reported verify result 411s # libfprint-device-DEBUG: Device reported verify completion 411s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 411s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 411s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 411s # 411s # libfprint-device-DEBUG: Device reported close completion 411s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 411s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 411s ok 65 /driver/verify/report_no_cb 411s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 411s # 411s # libfprint-device-DEBUG: Device reported open completion 411s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 411s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 411s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 411s # libfprint-device-DEBUG: Device reported verify completion 411s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 411s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 411s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 411s # 411s # libfprint-device-DEBUG: Device reported close completion 411s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 411s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 411s ok 66 /driver/verify/not_reported 411s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 411s # 411s # libfprint-device-DEBUG: Device reported open completion 411s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 411s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 411s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 411s # libfprint-device-DEBUG: Device reported verify result 411s # libfprint-device-DEBUG: Device reported verify completion 411s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 411s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 411s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 411s # libfprint-device-DEBUG: Device reported verify result 411s # libfprint-device-DEBUG: Device reported verify completion 411s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 411s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 411s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 411s # libfprint-device-DEBUG: Device reported verify result 411s # libfprint-device-DEBUG: Device reported verify completion 411s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 411s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 411s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 411s # libfprint-device-DEBUG: Device reported verify result 411s # libfprint-device-DEBUG: Device reported verify completion 411s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 411s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 411s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 411s # libfprint-device-DEBUG: Device reported verify result 411s # libfprint-device-DEBUG: Device reported verify completion 411s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 411s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 411s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 411s # 411s # libfprint-device-DEBUG: Device reported close completion 411s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 411s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 411s ok 67 /driver/verify/complete_retry 411s # End of verify tests 411s # Start of identify tests 411s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 411s # 411s # libfprint-device-DEBUG: Device reported open completion 411s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 411s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 411s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 411s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_identify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY 411s # 411s # libfprint-device-DEBUG: Device reported identify result 411s # libfprint-device-DEBUG: Device reported identify completion 411s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 411s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 411s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 411s # 411s # libfprint-device-DEBUG: Device reported close completion 411s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 411s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_COLD 411s ok 68 /driver/identify/fail 411s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 411s # 411s # libfprint-device-DEBUG: Device reported open completion 411s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 411s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 411s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 411s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_identify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY 411s # 411s # libfprint-device-DEBUG: Device reported identify result 411s # libfprint-device-DEBUG: Device reported identify completion 411s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 411s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 411s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 411s # 411s # libfprint-device-DEBUG: Device reported close completion 411s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 411s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_COLD 411s ok 69 /driver/identify/retry 411s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 411s # 411s # libfprint-device-DEBUG: Device reported open completion 411s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 411s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 411s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 411s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_identify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY 411s # 411s # libfprint-device-DEBUG: Device reported identify completion 411s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 411s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 411s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 411s # 411s # libfprint-device-DEBUG: Device reported close completion 411s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 411s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 411s ok 70 /driver/identify/error 411s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 411s # 411s # libfprint-device-DEBUG: Device reported open completion 411s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 411s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 411s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 411s # libfprint-device-DEBUG: Device reported identify completion 411s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 411s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 411s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 411s # 411s # libfprint-device-DEBUG: Device reported close completion 411s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 411s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 411s ok 71 /driver/identify/not_reported 411s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 411s # 411s # libfprint-device-DEBUG: Device reported open completion 411s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 411s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 411s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 411s # libfprint-device-DEBUG: Device reported identify result 411s # libfprint-device-DEBUG: Device reported identify completion 411s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 411s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 411s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 411s # libfprint-device-DEBUG: Device reported identify result 411s # libfprint-device-DEBUG: Device reported identify completion 411s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 411s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 411s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 411s # libfprint-device-DEBUG: Device reported identify result 411s # libfprint-device-DEBUG: Device reported identify completion 411s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 411s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 411s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 411s # 411s # libfprint-device-DEBUG: Device reported close completion 411s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 411s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 411s ok 72 /driver/identify/complete_retry 411s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 411s # 411s # libfprint-device-DEBUG: Device reported open completion 411s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 411s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 411s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 411s # libfprint-device-DEBUG: Device reported identify result 411s # libfprint-device-DEBUG: Device reported identify completion 411s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 411s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 411s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 411s # 411s # libfprint-device-DEBUG: Device reported close completion 411s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 411s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 411s ok 73 /driver/identify/report_no_cb 411s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 411s # 411s # libfprint-device-DEBUG: Device reported open completion 411s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 411s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 411s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 411s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_suspend: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY 411s # 411s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_resume: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY 411s # 411s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_identify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY 411s # 411s # libfprint-device-DEBUG: Device reported identify result 411s # libfprint-device-DEBUG: Device reported identify completion 411s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 411s # libfprint-device-DEBUG: Updated temperature model after 0.02 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 411s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 411s # 411s # libfprint-device-DEBUG: Device reported close completion 411s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 411s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 411s ok 74 /driver/identify/suspend_continues 411s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 411s # 411s # libfprint-device-DEBUG: Device reported open completion 411s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 411s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 411s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 411s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_suspend: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY 411s # 411s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_identify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY 411s # 411s # libfprint-device-DEBUG: Device reported identify result 411s # libfprint-device-DEBUG: Device reported identify completion 411s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 411s # libfprint-device-DEBUG: Updated temperature model after 0.02 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 411s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 411s # 411s # libfprint-device-DEBUG: Device reported close completion 411s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 411s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 411s ok 75 /driver/identify/suspend_succeeds 411s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 411s # 411s # libfprint-device-DEBUG: Device reported open completion 411s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 411s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 411s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 411s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_suspend: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY 411s # 411s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_identify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY 411s # 411s # libfprint-device-DEBUG: Device reported identify completion 411s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 411s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 411s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 411s # 411s # libfprint-device-DEBUG: Device reported close completion 411s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 411s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_COLD 411s ok 76 /driver/identify/suspend_busy_error 411s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 411s # 411s # libfprint-device-DEBUG: Device reported open completion 411s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 411s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 411s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 411s # 411s # libfprint-device-DEBUG: Device reported close completion 411s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 411s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 411s ok 77 /driver/identify/suspend_while_idle 411s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 411s # 411s # libfprint-device-DEBUG: Device reported open completion 411s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 411s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 411s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 411s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.30, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 412s Executing: libfprint-2/fpi-device.test 413s # libfprint-device-DEBUG: Updated temperature model after 2.00 seconds, ratio 0.30 -> 0.74, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_HOT 413s # libfprint-device-DEBUG: Idle cancelling on ongoing operation! 413s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_cancel: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY 413s # 413s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_identify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY 413s # 413s # libfprint-device-DEBUG: Device reported identify completion 413s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 413s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.74 -> 0.74, active 0 -> 0, FP_TEMPERATURE_HOT -> FP_TEMPERATURE_HOT 413s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.74 -> 0.74, active 1 -> 1, FP_TEMPERATURE_HOT -> FP_TEMPERATURE_HOT 413s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.74 -> 0.74, active 0 -> 0, FP_TEMPERATURE_HOT -> FP_TEMPERATURE_HOT 415s # libfprint-device-DEBUG: Updated temperature model after 2.09 seconds, ratio 0.74 -> 0.49, active 0 -> 0, FP_TEMPERATURE_HOT -> FP_TEMPERATURE_WARM 417s Executing: libfprint-2/fpi-device.test 418s # libfprint-device-DEBUG: Updated temperature model after 3.10 seconds, ratio 0.49 -> 0.26, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_COLD 418s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 418s # 418s # libfprint-device-DEBUG: Device reported close completion 418s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 418s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.26 -> 0.26, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 418s ok 78 /driver/identify/warmup_cooldown 418s # slow test /driver/identify/warmup_cooldown executed in 7.29 secs 418s # End of identify tests 418s # Start of capture tests 418s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 418s # 418s # libfprint-device-DEBUG: Device reported open completion 418s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 418s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 418s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 418s # 418s # libfprint-device-DEBUG: Device reported close completion 418s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 418s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 418s ok 79 /driver/capture/not_supported 418s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 418s # 418s # libfprint-device-DEBUG: Device reported open completion 418s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 418s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 418s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 418s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_capture: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CAPTURE 418s # 418s # libfprint-device-DEBUG: Device reported capture completion 418s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CAPTURE in idle! 418s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 418s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 418s # 418s # libfprint-device-DEBUG: Device reported close completion 418s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 418s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 418s ok 80 /driver/capture/error 418s # End of capture tests 418s # Start of list tests 418s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 418s # 418s # libfprint-device-DEBUG: Device reported open completion 418s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 418s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 418s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_list: Device Virtual device for debugging in action FPI_DEVICE_ACTION_LIST 418s # 418s # libfprint-device-DEBUG: Device reported listing completion 418s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_LIST in idle! 418s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 418s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 418s # 418s # libfprint-device-DEBUG: Device reported close completion 418s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 418s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 418s ok 81 /driver/list/error 418s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 418s # 418s # libfprint-device-DEBUG: Device reported open completion 418s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 418s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 418s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 418s # 418s # libfprint-device-DEBUG: Device reported close completion 418s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 418s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 418s ok 82 /driver/list/no_storage 418s # End of list tests 418s # Start of delete tests 418s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 418s # 418s # libfprint-device-DEBUG: Device reported open completion 418s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 418s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 418s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_delete: Device Virtual device for debugging in action FPI_DEVICE_ACTION_DELETE 418s # 418s # libfprint-device-DEBUG: Device reported deletion completion 418s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_DELETE in idle! 418s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 418s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 418s # 418s # libfprint-device-DEBUG: Device reported close completion 418s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 418s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 418s ok 83 /driver/delete/error 418s # End of delete tests 418s # Start of clear_storage tests 418s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 418s # 418s # libfprint-device-DEBUG: Device reported open completion 418s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 418s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 418s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_clear_storage: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLEAR_STORAGE 418s # 418s # libfprint-device-DEBUG: Device reported deletion completion 418s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 418s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 418s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 418s # 418s # libfprint-device-DEBUG: Device reported close completion 418s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 418s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 418s ok 84 /driver/clear_storage/error 418s # End of clear_storage tests 418s # Start of cancel tests 418s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 418s # 418s # libfprint-device-DEBUG: Device reported open completion 418s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 418s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 418s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_delete: Device Virtual device for debugging in action FPI_DEVICE_ACTION_DELETE 418s # 418s # libfprint-device-DEBUG: Device reported deletion completion 418s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_DELETE in idle! 418s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 418s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 418s # 418s # libfprint-device-DEBUG: Device reported close completion 418s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 418s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 418s ok 85 /driver/cancel/fail 418s # End of cancel tests 418s # Start of get_current_action tests 418s # libfprint-device-DEBUG: Device reported open completion 418s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 418s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 418s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 418s # 418s # libfprint-device-DEBUG: Device reported close completion 418s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 418s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 418s ok 86 /driver/get_current_action/open 418s # End of get_current_action tests 418s # Start of get_cancellable tests 418s ok 87 /driver/get_cancellable/error 418s # libfprint-device-DEBUG: Device reported open completion 418s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 418s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 418s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 418s # 418s # libfprint-device-DEBUG: Device reported close completion 418s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 418s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 418s ok 88 /driver/get_cancellable/open 418s # Start of open tests 418s # libfprint-device-DEBUG: Device reported open completion 418s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 418s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 418s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 418s # 418s # libfprint-device-DEBUG: Device reported close completion 418s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 418s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 418s ok 89 /driver/get_cancellable/open/internal 418s # End of open tests 418s # End of get_cancellable tests 418s # Start of action_is_cancelled tests 418s # libfprint-device-DEBUG: Device reported open completion 418s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 418s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 418s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 418s # 418s # libfprint-device-DEBUG: Device reported close completion 418s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 418s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 418s ok 90 /driver/action_is_cancelled/open 418s ok 91 /driver/action_is_cancelled/error 418s # Start of open tests 418s # libfprint-device-DEBUG: Device reported open completion 418s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 418s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 418s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 418s # 418s # libfprint-device-DEBUG: Device reported close completion 418s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 418s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 418s ok 92 /driver/action_is_cancelled/open/internal 418s # End of open tests 418s # End of action_is_cancelled tests 418s # Start of complete_action tests 418s # Start of all tests 418s ok 93 /driver/complete_action/all/error 418s # End of all tests 418s # End of complete_action tests 418s # Start of action_error tests 418s ok 94 /driver/action_error/error 418s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 418s # 418s # libfprint-device-DEBUG: Device reported generic error (Passed (print) data is not valid.) during action; action was: FPI_DEVICE_ACTION_OPEN 418s # libfprint-device-DEBUG: Device reported open completion 418s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 418s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 418s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 418s # 418s # libfprint-device-DEBUG: Device reported open completion 418s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 418s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 418s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 418s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_enroll: Device Virtual device for debugging in action FPI_DEVICE_ACTION_ENROLL 418s # 418s # libfprint-device-DEBUG: Device reported generic error (Passed (print) data is not valid.) during action; action was: FPI_DEVICE_ACTION_ENROLL 418s # libfprint-device-DEBUG: Device reported enroll completion 418s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 418s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 418s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 418s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_verify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_VERIFY 418s # 418s # libfprint-device-DEBUG: Device reported generic error (Passed (print) data is not valid.) during action; action was: FPI_DEVICE_ACTION_VERIFY 418s # libfprint-device-DEBUG: Device reported verify completion 418s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 418s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 418s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 418s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_identify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY 418s # 418s # libfprint-device-DEBUG: Device reported generic error (Passed (print) data is not valid.) during action; action was: FPI_DEVICE_ACTION_IDENTIFY 418s # libfprint-device-DEBUG: Device reported identify completion 418s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 418s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 418s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 418s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_capture: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CAPTURE 418s # 418s # libfprint-device-DEBUG: Device reported generic error (Passed (print) data is not valid.) during action; action was: FPI_DEVICE_ACTION_CAPTURE 418s # libfprint-device-DEBUG: Device reported capture completion 418s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CAPTURE in idle! 418s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 418s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_list: Device Virtual device for debugging in action FPI_DEVICE_ACTION_LIST 418s # 418s # libfprint-device-DEBUG: Device reported generic error (Passed (print) data is not valid.) during action; action was: FPI_DEVICE_ACTION_LIST 418s # libfprint-device-DEBUG: Device reported listing completion 418s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_LIST in idle! 418s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 418s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_delete: Device Virtual device for debugging in action FPI_DEVICE_ACTION_DELETE 418s # 418s # libfprint-device-DEBUG: Device reported generic error (Passed (print) data is not valid.) during action; action was: FPI_DEVICE_ACTION_DELETE 418s # libfprint-device-DEBUG: Device reported deletion completion 418s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_DELETE in idle! 418s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 418s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_clear_storage: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLEAR_STORAGE 418s # 418s # libfprint-device-DEBUG: Device reported generic error (Passed (print) data is not valid.) during action; action was: FPI_DEVICE_ACTION_CLEAR_STORAGE 418s # libfprint-device-DEBUG: Device reported deletion completion 418s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 418s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 418s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 418s # 418s # libfprint-device-DEBUG: Device reported generic error (Passed (print) data is not valid.) during action; action was: FPI_DEVICE_ACTION_CLOSE 418s # libfprint-device-DEBUG: Device reported close completion 418s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 418s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 418s ok 95 /driver/action_error/all 418s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 418s # 418s # libfprint-device-DEBUG: Device reported open completion 418s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 418s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 418s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 418s # 418s # libfprint-device-DEBUG: Device reported open completion 418s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 418s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 418s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 418s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_enroll: Device Virtual device for debugging in action FPI_DEVICE_ACTION_ENROLL 418s # 418s # libfprint-device-DEBUG: Device reported enroll completion 418s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 418s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 418s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 418s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_verify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_VERIFY 418s # 418s # libfprint-device-DEBUG: Device reported verify completion 418s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 418s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 418s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 418s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_identify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY 418s # 418s # libfprint-device-DEBUG: Device reported identify completion 418s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 418s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 418s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 418s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_capture: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CAPTURE 418s # 418s # libfprint-device-DEBUG: Device reported capture completion 418s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CAPTURE in idle! 418s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 418s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_list: Device Virtual device for debugging in action FPI_DEVICE_ACTION_LIST 418s # 418s # libfprint-device-DEBUG: Device reported listing completion 418s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_LIST in idle! 418s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 418s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_delete: Device Virtual device for debugging in action FPI_DEVICE_ACTION_DELETE 418s # 418s # libfprint-device-DEBUG: Device reported deletion completion 418s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_DELETE in idle! 418s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 418s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_clear_storage: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLEAR_STORAGE 418s # 418s # libfprint-device-DEBUG: Device reported deletion completion 418s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 418s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 418s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 418s # 418s # libfprint-device-DEBUG: Device reported close completion 418s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 418s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 418s ok 96 /driver/action_error/fail 418s # End of action_error tests 418s # Start of timeout tests 418s ok 97 /driver/timeout/cancelled 418s # End of timeout tests 418s # End of driver tests 418s PASS: libfprint-2/fpi-device.test 418s Running test: libfprint-2/driver-elanmoc.test 418s ** (umockdev-run:2223): DEBUG: 00:54:27.625: umockdev.vala:127: Created udev test bed /tmp/umockdev.MSYB22 418s ** (umockdev-run:2223): DEBUG: 00:54:27.625: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0/usb1/1-9 418s ** (umockdev-run:2223): DEBUG: 00:54:27.627: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0/usb1/1-9 (subsystem usb) 418s ** (umockdev-run:2223): DEBUG: 00:54:27.632: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.MSYB22/dev/bus/usb/001/003 418s ** (umockdev-run:2223): DEBUG: 00:54:27.632: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0/usb1 418s ** (umockdev-run:2223): DEBUG: 00:54:27.633: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0/usb1 (subsystem usb) 418s ** (umockdev-run:2223): DEBUG: 00:54:27.637: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.MSYB22/dev/bus/usb/001/001 418s ** (umockdev-run:2223): DEBUG: 00:54:27.637: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0 418s ** (umockdev-run:2223): DEBUG: 00:54:27.638: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0 (subsystem pci) 418s (process:2227): libfprint-context-DEBUG: 00:54:27.756: Initializing FpContext (libfprint version 1.94.8+tod1) 418s (process:2227): libfprint-tod-DEBUG: 00:54:27.757: Impossible to load the shared drivers dir Error opening directory “/usr/lib/arm-linux-gnueabihf/libfprint-2/tod-1”: No such file or directory 418s (process:2227): libfprint-elanmoc-DEBUG: 00:54:27.759: 7399835820717: ../libfprint/drivers/elanmoc/elanmoc.c:1151 418s (process:2227): libfprint-context-DEBUG: 00:54:27.760: No driver found for USB device 1D6B:0002 418s (process:2227): libfprint-device-DEBUG: 00:54:27.760: Device reported probe completion 418s (process:2227): libfprint-device-DEBUG: 00:54:27.760: Completing action FPI_DEVICE_ACTION_PROBE in idle! 418s (process:2227): libfprint-device-DEBUG: 00:54:27.760: Not updating temperature model, device can run continuously! 418s (process:2227): libfprint-SSM-DEBUG: 00:54:27.762: [elanmoc] DEV_INIT_STATES entering state 0 418s (process:2227): libfprint-SSM-DEBUG: 00:54:27.762: [elanmoc] FP_CMD_NUM_STATES entering state 0 418s (process:2227): libfprint-SSM-DEBUG: 00:54:27.763: [elanmoc] FP_CMD_NUM_STATES entering state 1 418s (process:2227): libfprint-SSM-DEBUG: 00:54:27.763: [elanmoc] DEV_INIT_STATES entering state 1 418s (process:2227): libfprint-SSM-DEBUG: 00:54:27.763: [elanmoc] FP_CMD_NUM_STATES entering state 0 418s (process:2227): libfprint-SSM-DEBUG: 00:54:27.763: [elanmoc] FP_CMD_NUM_STATES completed successfully 418s (process:2227): libfprint-SSM-DEBUG: 00:54:27.764: [elanmoc] FP_CMD_NUM_STATES entering state 1 418s (process:2227): libfprint-SSM-DEBUG: 00:54:27.764: [elanmoc] DEV_INIT_STATES entering state 2 418s (process:2227): libfprint-SSM-DEBUG: 00:54:27.764: [elanmoc] FP_CMD_NUM_STATES entering state 0 418s (process:2227): libfprint-SSM-DEBUG: 00:54:27.764: [elanmoc] FP_CMD_NUM_STATES completed successfully 418s (process:2227): libfprint-SSM-DEBUG: 00:54:27.765: [elanmoc] FP_CMD_NUM_STATES entering state 1 418s (process:2227): libfprint-elanmoc-DEBUG: 00:54:27.765: elanmoc FW Version 8004 418s (process:2227): libfprint-SSM-DEBUG: 00:54:27.765: [elanmoc] DEV_INIT_STATES entering state 3 418s (process:2227): libfprint-SSM-DEBUG: 00:54:27.765: [elanmoc] FP_CMD_NUM_STATES entering state 0 418s (process:2227): libfprint-SSM-DEBUG: 00:54:27.765: [elanmoc] FP_CMD_NUM_STATES completed successfully 418s (process:2227): libfprint-SSM-DEBUG: 00:54:27.766: [elanmoc] FP_CMD_NUM_STATES entering state 1 418s (process:2227): libfprint-elanmoc-DEBUG: 00:54:27.766: elanmoc last_read DIM 0x57(87) 0x6B(107) 418s (process:2227): libfprint-SSM-DEBUG: 00:54:27.766: [elanmoc] DEV_INIT_STATES entering state 4 418s (process:2227): libfprint-SSM-DEBUG: 00:54:27.766: [elanmoc] FP_CMD_NUM_STATES entering state 0 418s (process:2227): libfprint-SSM-DEBUG: 00:54:27.766: [elanmoc] FP_CMD_NUM_STATES completed successfully 418s (process:2227): libfprint-SSM-DEBUG: 00:54:27.767: [elanmoc] FP_CMD_NUM_STATES entering state 1 418s (process:2227): libfprint-elanmoc-DEBUG: 00:54:27.767: elanmoc Current enrolled fingers in the Chipset: 1 (0x40 0x01) 418s (process:2227): libfprint-SSM-DEBUG: 00:54:27.767: [elanmoc] DEV_INIT_STATES completed successfully 418s (process:2227): libfprint-device-DEBUG: 00:54:27.767: Device reported open completion 418s (process:2227): libfprint-SSM-DEBUG: 00:54:27.767: [elanmoc] FP_CMD_NUM_STATES completed successfully 418s (process:2227): libfprint-device-DEBUG: 00:54:27.767: Completing action FPI_DEVICE_ACTION_OPEN in idle! 418s (process:2227): libfprint-device-DEBUG: 00:54:27.767: Not updating temperature model, device can run continuously! 418s (process:2227): libfprint-device-DEBUG: 00:54:27.768: Not updating temperature model, device can run continuously! 418s (process:2227): libfprint-SSM-DEBUG: 00:54:27.768: [elanmoc] MOC_ENROLL_NUM_STATES entering state 0 418s (process:2227): libfprint-SSM-DEBUG: 00:54:27.768: [elanmoc] FP_CMD_NUM_STATES entering state 0 418s (process:2227): libfprint-SSM-DEBUG: 00:54:27.769: [elanmoc] FP_CMD_NUM_STATES entering state 1 418s (process:2227): libfprint-elanmoc-DEBUG: 00:54:27.769: elanmoc Current enrolled fingers in the Chipset: 1 (0x40 0x01) 418s (process:2227): libfprint-SSM-DEBUG: 00:54:27.769: [elanmoc] MOC_ENROLL_NUM_STATES entering state 1 418s (process:2227): libfprint-SSM-DEBUG: 00:54:27.769: [elanmoc] FP_CMD_NUM_STATES entering state 0 418s (process:2227): libfprint-SSM-DEBUG: 00:54:27.770: [elanmoc] FP_CMD_NUM_STATES completed successfully 418s (process:2227): libfprint-SSM-DEBUG: 00:54:27.770: [elanmoc] FP_CMD_NUM_STATES entering state 1 418s (process:2227): libfprint-elanmoc-DEBUG: 00:54:27.770: ##### Re-Enrollment Case! ##### 418s (process:2227): libfprint-SSM-DEBUG: 00:54:27.770: [elanmoc] MOC_ENROLL_NUM_STATES entering state 2 418s (process:2227): libfprint-SSM-DEBUG: 00:54:27.770: [elanmoc] FP_CMD_NUM_STATES entering state 0 418s (process:2227): libfprint-SSM-DEBUG: 00:54:27.771: [elanmoc] FP_CMD_NUM_STATES completed successfully 418s (process:2227): libfprint-SSM-DEBUG: 00:54:27.771: [elanmoc] FP_CMD_NUM_STATES entering state 1 418s (process:2227): libfprint-device-DEBUG: 00:54:27.771: Device reported enroll progress, reported 1 of 9 have been completed 418s (process:2227): libfprint-SSM-DEBUG: 00:54:27.771: [elanmoc] MOC_ENROLL_NUM_STATES entering state 2 418s (process:2227): libfprint-SSM-DEBUG: 00:54:27.771: [elanmoc] FP_CMD_NUM_STATES entering state 0 418s (process:2227): libfprint-SSM-DEBUG: 00:54:27.772: [elanmoc] FP_CMD_NUM_STATES completed successfully 418s (process:2227): libfprint-SSM-DEBUG: 00:54:27.772: [elanmoc] FP_CMD_NUM_STATES entering state 1 418s (process:2227): libfprint-device-DEBUG: 00:54:27.772: Device reported enroll progress, reported 2 of 9 have been completed 418s (process:2227): libfprint-SSM-DEBUG: 00:54:27.773: [elanmoc] MOC_ENROLL_NUM_STATES entering state 2 418s (process:2227): libfprint-SSM-DEBUG: 00:54:27.773: [elanmoc] FP_CMD_NUM_STATES entering state 0 418s (process:2227): libfprint-SSM-DEBUG: 00:54:27.773: [elanmoc] FP_CMD_NUM_STATES completed successfully 418s (process:2227): libfprint-SSM-DEBUG: 00:54:27.773: [elanmoc] FP_CMD_NUM_STATES entering state 1 418s (process:2227): libfprint-device-DEBUG: 00:54:27.773: Device reported enroll progress, reported 3 of 9 have been completed 418s (process:2227): libfprint-SSM-DEBUG: 00:54:27.774: [elanmoc] MOC_ENROLL_NUM_STATES entering state 2 418s (process:2227): libfprint-SSM-DEBUG: 00:54:27.774: [elanmoc] FP_CMD_NUM_STATES entering state 0 418s (process:2227): libfprint-SSM-DEBUG: 00:54:27.774: [elanmoc] FP_CMD_NUM_STATES completed successfully 418s (process:2227): libfprint-SSM-DEBUG: 00:54:27.774: [elanmoc] FP_CMD_NUM_STATES entering state 1 418s (process:2227): libfprint-device-DEBUG: 00:54:27.775: Device reported enroll progress, reported 4 of 9 have been completed 418s (process:2227): libfprint-SSM-DEBUG: 00:54:27.775: [elanmoc] MOC_ENROLL_NUM_STATES entering state 2 418s (process:2227): libfprint-SSM-DEBUG: 00:54:27.775: [elanmoc] FP_CMD_NUM_STATES entering state 0 418s (process:2227): libfprint-SSM-DEBUG: 00:54:27.775: [elanmoc] FP_CMD_NUM_STATES completed successfully 418s (process:2227): libfprint-SSM-DEBUG: 00:54:27.775: [elanmoc] FP_CMD_NUM_STATES entering state 1 418s (process:2227): libfprint-device-DEBUG: 00:54:27.776: Device reported enroll progress, reported 5 of 9 have been completed 418s (process:2227): libfprint-SSM-DEBUG: 00:54:27.776: [elanmoc] MOC_ENROLL_NUM_STATES entering state 2 418s (process:2227): libfprint-SSM-DEBUG: 00:54:27.776: [elanmoc] FP_CMD_NUM_STATES entering state 0 418s (process:2227): libfprint-SSM-DEBUG: 00:54:27.776: [elanmoc] FP_CMD_NUM_STATES completed successfully 418s (process:2227): libfprint-SSM-DEBUG: 00:54:27.776: [elanmoc] FP_CMD_NUM_STATES entering state 1 418s (process:2227): libfprint-device-DEBUG: 00:54:27.777: Device reported enroll progress, reported 6 of 9 have been completed 418s (process:2227): libfprint-SSM-DEBUG: 00:54:27.777: [elanmoc] MOC_ENROLL_NUM_STATES entering state 2 418s (process:2227): libfprint-SSM-DEBUG: 00:54:27.777: [elanmoc] FP_CMD_NUM_STATES entering state 0 418s (process:2227): libfprint-SSM-DEBUG: 00:54:27.777: [elanmoc] FP_CMD_NUM_STATES completed successfully 418s (process:2227): libfprint-SSM-DEBUG: 00:54:27.777: [elanmoc] FP_CMD_NUM_STATES entering state 1 418s (process:2227): libfprint-device-DEBUG: 00:54:27.778: Device reported enroll progress, reported 7 of 9 have been completed 418s (process:2227): libfprint-SSM-DEBUG: 00:54:27.778: [elanmoc] MOC_ENROLL_NUM_STATES entering state 2 418s (process:2227): libfprint-SSM-DEBUG: 00:54:27.778: [elanmoc] FP_CMD_NUM_STATES entering state 0 418s (process:2227): libfprint-SSM-DEBUG: 00:54:27.778: [elanmoc] FP_CMD_NUM_STATES completed successfully 418s (process:2227): libfprint-SSM-DEBUG: 00:54:27.778: [elanmoc] FP_CMD_NUM_STATES entering state 1 418s (process:2227): libfprint-device-DEBUG: 00:54:27.779: Device reported enroll progress, reported 7 of 9 have been completed 418s (process:2227): libfprint-SSM-DEBUG: 00:54:27.779: [elanmoc] MOC_ENROLL_NUM_STATES entering state 2 418s (process:2227): libfprint-SSM-DEBUG: 00:54:27.779: [elanmoc] FP_CMD_NUM_STATES entering state 0 418s (process:2227): libfprint-SSM-DEBUG: 00:54:27.779: [elanmoc] FP_CMD_NUM_STATES completed successfully 418s (process:2227): libfprint-SSM-DEBUG: 00:54:27.779: [elanmoc] FP_CMD_NUM_STATES entering state 1 418s (process:2227): libfprint-device-DEBUG: 00:54:27.780: Device reported enroll progress, reported 8 of 9 have been completed 418s (process:2227): libfprint-SSM-DEBUG: 00:54:27.780: [elanmoc] MOC_ENROLL_NUM_STATES entering state 2 418s (process:2227): libfprint-SSM-DEBUG: 00:54:27.780: [elanmoc] FP_CMD_NUM_STATES entering state 0 418s (process:2227): libfprint-SSM-DEBUG: 00:54:27.780: [elanmoc] FP_CMD_NUM_STATES completed successfully 418s (process:2227): libfprint-SSM-DEBUG: 00:54:27.780: [elanmoc] FP_CMD_NUM_STATES entering state 1 418s (process:2227): libfprint-device-DEBUG: 00:54:27.781: Device reported enroll progress, reported 8 of 9 have been completed 418s (process:2227): libfprint-SSM-DEBUG: 00:54:27.781: [elanmoc] MOC_ENROLL_NUM_STATES entering state 2 418s (process:2227): libfprint-SSM-DEBUG: 00:54:27.781: [elanmoc] FP_CMD_NUM_STATES entering state 0 418s (process:2227): libfprint-SSM-DEBUG: 00:54:27.781: [elanmoc] FP_CMD_NUM_STATES completed successfully 418s (process:2227): libfprint-SSM-DEBUG: 00:54:27.781: [elanmoc] FP_CMD_NUM_STATES entering state 1 418s (process:2227): libfprint-device-DEBUG: 00:54:27.782: Device reported enroll progress, reported 9 of 9 have been completed 418s (process:2227): libfprint-SSM-DEBUG: 00:54:27.782: [elanmoc] MOC_ENROLL_NUM_STATES entering state 3 418s (process:2227): libfprint-SSM-DEBUG: 00:54:27.782: [elanmoc] FP_CMD_NUM_STATES entering state 0 418s (process:2227): libfprint-SSM-DEBUG: 00:54:27.782: [elanmoc] FP_CMD_NUM_STATES completed successfully 418s (process:2227): libfprint-SSM-DEBUG: 00:54:27.782: [elanmoc] FP_CMD_NUM_STATES entering state 1 418s (process:2227): libfprint-elanmoc-DEBUG: 00:54:27.783: elanmoc_commit_cb success 418s (process:2227): libfprint-elanmoc-DEBUG: 00:54:27.783: Enrollment was successful! 418s (process:2227): libfprint-device-DEBUG: 00:54:27.783: Device reported enroll completion 418s (process:2227): libfprint-device-DEBUG: 00:54:27.783: Print for finger FP_FINGER_UNKNOWN enrolled 418s (process:2227): libfprint-SSM-DEBUG: 00:54:27.783: [elanmoc] MOC_ENROLL_NUM_STATES completed successfully 418s (process:2227): libfprint-SSM-DEBUG: 00:54:27.783: [elanmoc] FP_CMD_NUM_STATES completed successfully 418s (process:2227): libfprint-device-DEBUG: 00:54:27.783: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 418s (process:2227): libfprint-device-DEBUG: 00:54:27.783: Not updating temperature model, device can run continuously! 418s (process:2227): libfprint-SSM-DEBUG: 00:54:27.783: [elanmoc] MOC_LIST_NUM_STATES entering state 0 418s (process:2227): libfprint-SSM-DEBUG: 00:54:27.783: [elanmoc] FP_CMD_NUM_STATES entering state 0 418s (process:2227): libfprint-SSM-DEBUG: 00:54:27.783: [elanmoc] FP_CMD_NUM_STATES entering state 1 418s (process:2227): libfprint-elanmoc-DEBUG: 00:54:27.784: elanmoc Current enrolled fingers in the Chipset: 1 (0x40 0x01) 418s (process:2227): libfprint-SSM-DEBUG: 00:54:27.784: [elanmoc] MOC_LIST_NUM_STATES entering state 1 418s (process:2227): libfprint-SSM-DEBUG: 00:54:27.784: [elanmoc] FP_CMD_NUM_STATES entering state 0 418s (process:2227): libfprint-SSM-DEBUG: 00:54:27.784: [elanmoc] FP_CMD_NUM_STATES completed successfully 418s (process:2227): libfprint-SSM-DEBUG: 00:54:27.785: [elanmoc] FP_CMD_NUM_STATES entering state 1 418s (process:2227): libfprint-SSM-DEBUG: 00:54:27.785: [elanmoc] MOC_LIST_NUM_STATES entering state 1 418s (process:2227): libfprint-SSM-DEBUG: 00:54:27.785: [elanmoc] FP_CMD_NUM_STATES entering state 0 418s (process:2227): libfprint-SSM-DEBUG: 00:54:27.785: [elanmoc] FP_CMD_NUM_STATES completed successfully 418s (process:2227): libfprint-SSM-DEBUG: 00:54:27.786: [elanmoc] FP_CMD_NUM_STATES entering state 1 418s (process:2227): libfprint-SSM-DEBUG: 00:54:27.786: [elanmoc] MOC_LIST_NUM_STATES entering state 1 418s (process:2227): libfprint-SSM-DEBUG: 00:54:27.786: [elanmoc] FP_CMD_NUM_STATES entering state 0 418s (process:2227): libfprint-SSM-DEBUG: 00:54:27.786: [elanmoc] FP_CMD_NUM_STATES completed successfully 418s (process:2227): libfprint-SSM-DEBUG: 00:54:27.787: [elanmoc] FP_CMD_NUM_STATES entering state 1 418s (process:2227): libfprint-SSM-DEBUG: 00:54:27.787: [elanmoc] MOC_LIST_NUM_STATES entering state 1 418s (process:2227): libfprint-SSM-DEBUG: 00:54:27.787: [elanmoc] FP_CMD_NUM_STATES entering state 0 418s (process:2227): libfprint-SSM-DEBUG: 00:54:27.787: [elanmoc] FP_CMD_NUM_STATES completed successfully 418s (process:2227): libfprint-SSM-DEBUG: 00:54:27.788: [elanmoc] FP_CMD_NUM_STATES entering state 1 418s (process:2227): libfprint-SSM-DEBUG: 00:54:27.788: [elanmoc] MOC_LIST_NUM_STATES entering state 1 418s (process:2227): libfprint-SSM-DEBUG: 00:54:27.788: [elanmoc] FP_CMD_NUM_STATES entering state 0 418s (process:2227): libfprint-SSM-DEBUG: 00:54:27.788: [elanmoc] FP_CMD_NUM_STATES completed successfully 418s (process:2227): libfprint-SSM-DEBUG: 00:54:27.789: [elanmoc] FP_CMD_NUM_STATES entering state 1 418s (process:2227): libfprint-SSM-DEBUG: 00:54:27.789: [elanmoc] MOC_LIST_NUM_STATES entering state 1 418s (process:2227): libfprint-SSM-DEBUG: 00:54:27.789: [elanmoc] FP_CMD_NUM_STATES entering state 0 418s (process:2227): libfprint-SSM-DEBUG: 00:54:27.790: [elanmoc] FP_CMD_NUM_STATES completed successfully 418s (process:2227): libfprint-SSM-DEBUG: 00:54:27.790: [elanmoc] FP_CMD_NUM_STATES entering state 1 418s (process:2227): libfprint-SSM-DEBUG: 00:54:27.790: [elanmoc] MOC_LIST_NUM_STATES entering state 1 418s (process:2227): libfprint-SSM-DEBUG: 00:54:27.790: [elanmoc] FP_CMD_NUM_STATES entering state 0 418s (process:2227): libfprint-SSM-DEBUG: 00:54:27.791: [elanmoc] FP_CMD_NUM_STATES completed successfully 418s (process:2227): libfprint-SSM-DEBUG: 00:54:27.791: [elanmoc] FP_CMD_NUM_STATES entering state 1 418s (process:2227): libfprint-SSM-DEBUG: 00:54:27.791: [elanmoc] MOC_LIST_NUM_STATES entering state 1 418s (process:2227): libfprint-SSM-DEBUG: 00:54:27.791: [elanmoc] FP_CMD_NUM_STATES entering state 0 418s (process:2227): libfprint-SSM-DEBUG: 00:54:27.792: [elanmoc] FP_CMD_NUM_STATES completed successfully 418s (process:2227): libfprint-SSM-DEBUG: 00:54:27.792: [elanmoc] FP_CMD_NUM_STATES entering state 1 418s (process:2227): libfprint-SSM-DEBUG: 00:54:27.792: [elanmoc] MOC_LIST_NUM_STATES entering state 1 418s (process:2227): libfprint-SSM-DEBUG: 00:54:27.792: [elanmoc] FP_CMD_NUM_STATES entering state 0 418s (process:2227): libfprint-SSM-DEBUG: 00:54:27.793: [elanmoc] FP_CMD_NUM_STATES completed successfully 418s (process:2227): libfprint-SSM-DEBUG: 00:54:27.793: [elanmoc] FP_CMD_NUM_STATES entering state 1 418s (process:2227): libfprint-SSM-DEBUG: 00:54:27.793: [elanmoc] MOC_LIST_NUM_STATES entering state 1 418s (process:2227): libfprint-SSM-DEBUG: 00:54:27.793: [elanmoc] FP_CMD_NUM_STATES entering state 0 418s (process:2227): libfprint-SSM-DEBUG: 00:54:27.794: [elanmoc] FP_CMD_NUM_STATES completed successfully 418s (process:2227): libfprint-SSM-DEBUG: 00:54:27.794: [elanmoc] FP_CMD_NUM_STATES entering state 1 418s (process:2227): libfprint-device-DEBUG: 00:54:27.794: Device reported listing completion 418s (process:2227): libfprint-SSM-DEBUG: 00:54:27.794: [elanmoc] MOC_LIST_NUM_STATES completed successfully 418s (process:2227): libfprint-SSM-DEBUG: 00:54:27.794: [elanmoc] FP_CMD_NUM_STATES completed successfully 418s (process:2227): libfprint-device-DEBUG: 00:54:27.794: Completing action FPI_DEVICE_ACTION_LIST in idle! 418s (process:2227): libfprint-device-DEBUG: 00:54:27.794: Not updating temperature model, device can run continuously! 418s (process:2227): libfprint-device-DEBUG: 00:54:27.795: Not updating temperature model, device can run continuously! 418s (process:2227): libfprint-SSM-DEBUG: 00:54:27.795: [elanmoc] IDENTIFY_NUM_STATES entering state 0 418s (process:2227): libfprint-elanmoc-DEBUG: 00:54:27.795: elanmoc elan_identify_run_state 418s (process:2227): libfprint-elanmoc-DEBUG: 00:54:27.795: elanmoc elan_identify_run_state IDENTIFY_SET_MODE 418s (process:2227): libfprint-SSM-DEBUG: 00:54:27.795: [elanmoc] FP_CMD_NUM_STATES entering state 0 418s (process:2227): libfprint-SSM-DEBUG: 00:54:27.795: [elanmoc] FP_CMD_NUM_STATES entering state 1 418s (process:2227): libfprint-SSM-DEBUG: 00:54:27.796: [elanmoc] IDENTIFY_NUM_STATES entering state 1 418s (process:2227): libfprint-elanmoc-DEBUG: 00:54:27.796: elanmoc elan_identify_run_state 418s (process:2227): libfprint-elanmoc-DEBUG: 00:54:27.796: elanmoc elan_identify_run_state VERIFY_WAIT_FINGER 418s (process:2227): libfprint-SSM-DEBUG: 00:54:27.796: [elanmoc] FP_CMD_NUM_STATES entering state 0 418s (process:2227): libfprint-SSM-DEBUG: 00:54:27.796: [elanmoc] FP_CMD_NUM_STATES completed successfully 418s (process:2227): libfprint-SSM-DEBUG: 00:54:27.796: [elanmoc] FP_CMD_NUM_STATES entering state 1 418s (process:2227): libfprint-elanmoc-DEBUG: 00:54:27.797: Verify was successful! for user: 0 mesg_code: 1 418s (process:2227): libfprint-SSM-DEBUG: 00:54:27.797: [elanmoc] FP_CMD_NUM_STATES entering state 0 418s (process:2227): libfprint-SSM-DEBUG: 00:54:27.797: [elanmoc] IDENTIFY_NUM_STATES completed successfully 418s (process:2227): libfprint-SSM-DEBUG: 00:54:27.797: [elanmoc] FP_CMD_NUM_STATES completed successfully 418s (process:2227): libfprint-SSM-DEBUG: 00:54:27.797: [elanmoc] FP_CMD_NUM_STATES entering state 1 418s (process:2227): libfprint-elanmoc-DEBUG: 00:54:27.798: Verify/Identify successful for: FP1-00000000-0-00000000-nobody 418s (process:2227): libfprint-device-DEBUG: 00:54:27.798: Device reported verify result 418s (process:2227): libfprint-device-DEBUG: 00:54:27.798: Device reported verify completion 418s (process:2227): libfprint-SSM-DEBUG: 00:54:27.798: [elanmoc] FP_CMD_NUM_STATES completed successfully 418s (process:2227): libfprint-device-DEBUG: 00:54:27.798: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 418s (process:2227): libfprint-device-DEBUG: 00:54:27.798: Not updating temperature model, device can run continuously! 418s (process:2227): libfprint-device-DEBUG: 00:54:27.798: Not updating temperature model, device can run continuously! 418s (process:2227): libfprint-SSM-DEBUG: 00:54:27.798: [elanmoc] IDENTIFY_NUM_STATES entering state 0 418s (process:2227): libfprint-elanmoc-DEBUG: 00:54:27.798: elanmoc elan_identify_run_state 418s (process:2227): libfprint-elanmoc-DEBUG: 00:54:27.798: elanmoc elan_identify_run_state IDENTIFY_SET_MODE 418s (process:2227): libfprint-SSM-DEBUG: 00:54:27.798: [elanmoc] FP_CMD_NUM_STATES entering state 0 418s (process:2227): libfprint-SSM-DEBUG: 00:54:27.799: [elanmoc] FP_CMD_NUM_STATES entering state 1 418s (process:2227): libfprint-SSM-DEBUG: 00:54:27.799: [elanmoc] IDENTIFY_NUM_STATES entering state 1 418s (process:2227): libfprint-elanmoc-DEBUG: 00:54:27.799: elanmoc elan_identify_run_state 418s (process:2227): libfprint-elanmoc-DEBUG: 00:54:27.799: elanmoc elan_identify_run_state VERIFY_WAIT_FINGER 418s (process:2227): libfprint-SSM-DEBUG: 00:54:27.799: [elanmoc] FP_CMD_NUM_STATES entering state 0 418s (process:2227): libfprint-SSM-DEBUG: 00:54:27.800: [elanmoc] FP_CMD_NUM_STATES completed successfully 418s (process:2227): libfprint-SSM-DEBUG: 00:54:27.800: [elanmoc] FP_CMD_NUM_STATES entering state 1 418s (process:2227): libfprint-elanmoc-DEBUG: 00:54:27.800: Verify was successful! for user: 0 mesg_code: 1 418s (process:2227): libfprint-SSM-DEBUG: 00:54:27.800: [elanmoc] FP_CMD_NUM_STATES entering state 0 418s (process:2227): libfprint-SSM-DEBUG: 00:54:27.801: [elanmoc] IDENTIFY_NUM_STATES completed successfully 418s (process:2227): libfprint-SSM-DEBUG: 00:54:27.801: [elanmoc] FP_CMD_NUM_STATES completed successfully 418s (process:2227): libfprint-SSM-DEBUG: 00:54:27.801: [elanmoc] FP_CMD_NUM_STATES entering state 1 418s (process:2227): libfprint-elanmoc-DEBUG: 00:54:27.801: Verify/Identify successful for: FP1-00000000-0-00000000-nobody 418s (process:2227): libfprint-device-DEBUG: 00:54:27.801: Device reported identify result 418s (process:2227): libfprint-device-DEBUG: 00:54:27.801: Device reported identify completion 418s (process:2227): libfprint-SSM-DEBUG: 00:54:27.801: [elanmoc] FP_CMD_NUM_STATES completed successfully 418s (process:2227): libfprint-device-DEBUG: 00:54:27.802: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 418s (process:2227): libfprint-device-DEBUG: 00:54:27.802: Not updating temperature model, device can run continuously! 418s (process:2227): libfprint-elanmoc-DEBUG: 00:54:27.802: Delete Finger, user_id = FP1-00000000-0-00000000-nobody! 418s (process:2227): libfprint-SSM-DEBUG: 00:54:27.802: [elanmoc] DELETE_NUM_STATES entering state 0 418s (process:2227): libfprint-SSM-DEBUG: 00:54:27.802: [elanmoc] FP_CMD_NUM_STATES entering state 0 418s (process:2227): libfprint-SSM-DEBUG: 00:54:27.803: [elanmoc] FP_CMD_NUM_STATES entering state 1 418s (process:2227): libfprint-device-DEBUG: 00:54:27.803: Device reported deletion completion 418s (process:2227): libfprint-SSM-DEBUG: 00:54:27.803: [elanmoc] DELETE_NUM_STATES completed successfully 418s (process:2227): libfprint-SSM-DEBUG: 00:54:27.803: [elanmoc] FP_CMD_NUM_STATES completed successfully 418s (process:2227): libfprint-device-DEBUG: 00:54:27.803: Completing action FPI_DEVICE_ACTION_DELETE in idle! 418s (process:2227): libfprint-device-DEBUG: 00:54:27.803: Not updating temperature model, device can run continuously! 418s (process:2227): libfprint-elanmoc-DEBUG: 00:54:27.803: Elanmoc dev_exit 418s (process:2227): libfprint-SSM-DEBUG: 00:54:27.803: [elanmoc] DEV_EXIT_STATES entering state 0 418s (process:2227): libfprint-SSM-DEBUG: 00:54:27.803: [elanmoc] FP_CMD_NUM_STATES entering state 0 418s (process:2227): libfprint-SSM-DEBUG: 00:54:27.804: [elanmoc] FP_CMD_NUM_STATES entering state 1 418s (process:2227): libfprint-SSM-DEBUG: 00:54:27.804: [elanmoc] DEV_EXIT_STATES completed successfully 418s (process:2227): libfprint-device-DEBUG: 00:54:27.804: Device reported close completion 418s (process:2227): libfprint-SSM-DEBUG: 00:54:27.804: [elanmoc] FP_CMD_NUM_STATES completed successfully 418s (process:2227): libfprint-device-DEBUG: 00:54:27.804: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 418s (process:2227): libfprint-device-DEBUG: 00:54:27.804: Not updating temperature model, device can run continuously! 418s enrolling 418s finger status: 418s enroll progress: (<__gi__.FpiDeviceElanmoc object at 0xef4bea88 (FpiDeviceElanmoc at 0x14cb288)>, 1, None, None, None) 418s finger status: 418s enroll progress: (<__gi__.FpiDeviceElanmoc object at 0xef4bea88 (FpiDeviceElanmoc at 0x14cb288)>, 2, None, None, None) 418s finger status: 418s enroll progress: (<__gi__.FpiDeviceElanmoc object at 0xef4bea88 (FpiDeviceElanmoc at 0x14cb288)>, 3, None, None, None) 418s finger status: 418s enroll progress: (<__gi__.FpiDeviceElanmoc object at 0xef4bea88 (FpiDeviceElanmoc at 0x14cb288)>, 4, None, None, None) 418s finger status: 418s enroll progress: (<__gi__.FpiDeviceElanmoc object at 0xef4bea88 (FpiDeviceElanmoc at 0x14cb288)>, 5, None, None, None) 418s finger status: 418s enroll progress: (<__gi__.FpiDeviceElanmoc object at 0xef4bea88 (FpiDeviceElanmoc at 0x14cb288)>, 6, None, None, None) 418s finger status: 418s enroll progress: (<__gi__.FpiDeviceElanmoc object at 0xef4bea88 (FpiDeviceElanmoc at 0x14cb288)>, 7, None, None, None) 418s finger status: 418s enroll progress: (<__gi__.FpiDeviceElanmoc object at 0xef4bea88 (FpiDeviceElanmoc at 0x14cb288)>, 7, None, None, GLib.Error('The finger was not centered properly, please try again.', 'fp - device - retry - quark', 2)) 418s finger status: 418s enroll progress: (<__gi__.FpiDeviceElanmoc object at 0xef4bea88 (FpiDeviceElanmoc at 0x14cb288)>, 8, None, None, None) 418s finger status: 418s enroll progress: (<__gi__.FpiDeviceElanmoc object at 0xef4bea88 (FpiDeviceElanmoc at 0x14cb288)>, 8, None, None, GLib.Error('The finger was not centered properly, please try again.', 'fp - device - retry - quark', 2)) 418s finger status: 418s enroll progress: (<__gi__.FpiDeviceElanmoc object at 0xef4bea88 (FpiDeviceElanmoc at 0x14cb288)>, 9, None, None, None) 418s enroll done 418s listing 418s listing done 418s verifying 418s verify done 418s async identifying 418s indentification_done: 418s deleting 418s delete done 418s ** (umockdev-run:2223): DEBUG: 00:54:27.833: umockdev.vala:154: Removing test bed /tmp/umockdev.MSYB22 418s (umockdev-run:2223): GLib-DEBUG: 00:54:27.840: unsetenv() is not thread-safe and should not be used after threads are created 418s PASS: libfprint-2/driver-elanmoc.test 418s Running test: libfprint-2/tod-fpi-device-tod-fake_test_dev_tod_current.test 418s (process:2233): libfprint-context-DEBUG: 00:54:27.858: Initializing FpContext (libfprint version 1.94.8+tod1) 418s (process:2233): libfprint-tod-DEBUG: 00:54:27.859: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/current/libdevice-fake-tod-driver.so 418s (process:2233): libfprint-tod-DEBUG: 00:54:27.859: Found TOD entry point symbol 0xea72da9d, GType is 43566440 418s (process:2233): libfprint-tod-DEBUG: 00:54:27.859: Loading driver fake_test_dev_tod_current (Virtual device for debugging) 418s (process:2233): libfprint-context-DEBUG: 00:54:27.861: No driver found for USB device 1D6B:0003 418s (process:2233): libfprint-context-DEBUG: 00:54:27.861: No driver found for USB device 0627:0001 418s (process:2233): libfprint-context-DEBUG: 00:54:27.861: No driver found for USB device 1D6B:0002 418s (process:2233): libfprint-context-DEBUG: 00:54:27.861: Found virtual environment device: FP_VIRTUAL_FAKE_DEVICE, yes 418s (process:2233): libfprint-context-DEBUG: 00:54:27.862: created 418s (process:2233): libfprint-fake_test_dev_tod_current-DEBUG: 00:54:27.863: fpi_device_fake_probe: Device Virtual device for debugging in action FPI_DEVICE_ACTION_PROBE 418s 418s (process:2233): libfprint-device-DEBUG: 00:54:27.863: Device reported probe completion 418s (process:2233): libfprint-device-DEBUG: 00:54:27.863: Completing action FPI_DEVICE_ACTION_PROBE in idle! 418s (process:2233): libfprint-device-DEBUG: 00:54:27.863: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 418s (/usr/libexec/installed-tests/libfprint-2/test-fpi-device-tod:2233): GLib-DEBUG: 00:54:27.863: setenv()/putenv() are not thread-safe and should not be used after threads are created 418s TAP version 14 418s # random seed: R02S7e469cbb0d41f435a4df6e342732a01a 418s 1..97 418s # Start of driver tests 418s ok 1 /driver/get_driver 418s ok 2 /driver/get_device_id 418s ok 3 /driver/get_name 418s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 418s # 418s # libfprint-device-DEBUG: Device reported open completion 418s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 418s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 418s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 418s # 418s # libfprint-device-DEBUG: Device reported close completion 418s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 418s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 418s ok 4 /driver/is_open 418s ok 5 /driver/get_nr_enroll_stages 418s ok 6 /driver/set_nr_enroll_stages 418s ok 7 /driver/supports_identify 418s ok 8 /driver/supports_capture 418s ok 9 /driver/has_storage 418s ok 10 /driver/do_not_support_identify 418s ok 11 /driver/do_not_support_capture 418s ok 12 /driver/has_not_storage 418s ok 13 /driver/get_usb_device 418s ok 14 /driver/get_virtual_env 418s ok 15 /driver/get_driver_data 418s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_current' 418s # libfprint-device-DEBUG: Tod version info is 'current' 418s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_probe: Device Virtual device for debugging in action FPI_DEVICE_ACTION_PROBE 418s # 418s # libfprint-device-DEBUG: Device reported probe completion 418s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 418s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 418s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_current' 418s # libfprint-device-DEBUG: Tod version info is 'current' 418s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_current' 418s # libfprint-device-DEBUG: Tod version info is 'current' 418s ok 16 /driver/initial_features 418s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_probe: Device Probed device name in action FPI_DEVICE_ACTION_PROBE 418s # 418s # libfprint-device-DEBUG: Device reported probe completion 418s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 418s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 418s ok 17 /driver/probe 418s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 418s # 418s # libfprint-device-DEBUG: Device reported open completion 418s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 418s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 418s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 418s # 418s # libfprint-device-DEBUG: Device reported close completion 418s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 418s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 418s ok 18 /driver/open 418s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 418s # 418s # libfprint-device-DEBUG: Device reported open completion 418s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 418s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 418s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 418s # 418s # libfprint-device-DEBUG: Device reported close completion 418s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 418s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 418s ok 19 /driver/close 418s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 418s # 418s # libfprint-device-DEBUG: Device reported open completion 418s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 418s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 418s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 418s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_enroll: Device Virtual device for debugging in action FPI_DEVICE_ACTION_ENROLL 418s # 418s # libfprint-device-DEBUG: Device reported enroll completion 418s # libfprint-device-DEBUG: Print for finger FP_FINGER_UNKNOWN enrolled 418s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 418s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 418s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 418s # 418s # libfprint-device-DEBUG: Device reported close completion 418s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 418s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 418s ok 20 /driver/enroll 418s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 418s # 418s # libfprint-device-DEBUG: Device reported open completion 418s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 418s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 418s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 418s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_verify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_VERIFY 418s # 418s # libfprint-device-DEBUG: Device reported verify result 418s # libfprint-device-DEBUG: Device reported verify completion 418s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 418s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 418s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 418s # 418s # libfprint-device-DEBUG: Device reported close completion 418s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 418s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_COLD 418s ok 21 /driver/verify 418s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 418s # 418s # libfprint-device-DEBUG: Device reported open completion 418s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 418s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 418s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 418s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_identify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY 418s # 418s # libfprint-device-DEBUG: Device reported identify result 418s # libfprint-device-DEBUG: Device reported identify completion 418s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 418s # libfprint-device-DEBUG: Updated temperature model after 0.02 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 418s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 418s # 418s # libfprint-device-DEBUG: Device reported close completion 418s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 418s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 418s ok 22 /driver/identify 418s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 418s # 418s # libfprint-device-DEBUG: Device reported open completion 418s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 418s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 418s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 418s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_capture: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CAPTURE 418s # 418s # libfprint-device-DEBUG: Device reported capture completion 418s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CAPTURE in idle! 418s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 418s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 418s # 418s # libfprint-device-DEBUG: Device reported close completion 418s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 418s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 418s ok 23 /driver/capture 418s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 418s # 418s # libfprint-device-DEBUG: Device reported open completion 418s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 418s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 418s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_list: Device Virtual device for debugging in action FPI_DEVICE_ACTION_LIST 418s # 418s # libfprint-device-DEBUG: Device reported listing completion 418s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_LIST in idle! 418s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 418s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 418s # 418s # libfprint-device-DEBUG: Device reported close completion 418s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 418s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 418s ok 24 /driver/list 418s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 418s # 418s # libfprint-device-DEBUG: Device reported open completion 418s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 418s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 418s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_delete: Device Virtual device for debugging in action FPI_DEVICE_ACTION_DELETE 418s # 418s # libfprint-device-DEBUG: Device reported deletion completion 418s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_DELETE in idle! 418s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 418s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 418s # 418s # libfprint-device-DEBUG: Device reported close completion 418s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 418s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 418s ok 25 /driver/delete 418s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 418s # 418s # libfprint-device-DEBUG: Device reported open completion 418s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 418s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 418s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_current' 418s # libfprint-device-DEBUG: Tod version info is 'current' 418s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_clear_storage: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLEAR_STORAGE 418s # 418s # libfprint-device-DEBUG: Device reported deletion completion 418s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 418s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 418s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 418s # 418s # libfprint-device-DEBUG: Device reported close completion 418s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 418s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 418s ok 26 /driver/clear_storage 418s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 418s # 418s # libfprint-device-DEBUG: Device reported open completion 418s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 418s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 418s # libfprint-device-DEBUG: Idle cancelling on ongoing operation! 418s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_cancel: Device Virtual device for debugging in action FPI_DEVICE_ACTION_DELETE 418s # 419s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_delete: Device Virtual device for debugging in action FPI_DEVICE_ACTION_DELETE 419s # 419s # libfprint-device-DEBUG: Device reported deletion completion 419s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_DELETE in idle! 419s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 419s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 419s # 419s # libfprint-device-DEBUG: Device reported close completion 419s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 419s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 419s ok 27 /driver/cancel 419s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 419s # 419s # libfprint-device-DEBUG: Device reported open completion 419s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 419s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 419s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_current' 419s # libfprint-device-DEBUG: Tod version info is 'current' 419s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 419s # libfprint-device-DEBUG: Idle cancelling on ongoing operation! 419s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_cancel: Device Virtual device for debugging in action FPI_DEVICE_ACTION_VERIFY 419s # 419s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_suspend: Device Virtual device for debugging in action FPI_DEVICE_ACTION_VERIFY 419s # 419s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_resume: Device Virtual device for debugging in action FPI_DEVICE_ACTION_VERIFY 419s # 419s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_verify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_VERIFY 419s # 419s # libfprint-device-DEBUG: Device reported verify result 419s # libfprint-device-DEBUG: Device reported verify completion 419s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 419s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 419s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 419s # 419s # libfprint-device-DEBUG: Device reported close completion 419s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 419s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 419s ok 28 /driver/critical 419s ok 29 /driver/get_current_action 419s ok 30 /driver/timeout 419s ok 31 /driver/error_types 419s ok 32 /driver/retry_error_types 419s # Start of get_scan_type tests 419s ok 33 /driver/get_scan_type/press 419s ok 34 /driver/get_scan_type/swipe 419s # End of get_scan_type tests 419s # Start of set_scan_type tests 419s ok 35 /driver/set_scan_type/press 419s ok 36 /driver/set_scan_type/swipe 419s # End of set_scan_type tests 419s # Start of finger_status tests 419s ok 37 /driver/finger_status/inactive 419s # libfprint-device-DEBUG: Device reported finger status change: FP_FINGER_STATUS_NEEDED 419s ok 38 /driver/finger_status/waiting 419s # libfprint-device-DEBUG: Device reported finger status change: FP_FINGER_STATUS_PRESENT 419s ok 39 /driver/finger_status/present 419s # libfprint-device-DEBUG: Device reported finger status change: FP_FINGER_STATUS_NEEDED 419s # libfprint-device-DEBUG: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 419s # libfprint-device-DEBUG: Device reported finger status change: FP_FINGER_STATUS_PRESENT 419s # libfprint-device-DEBUG: Device reported finger status change: FP_FINGER_STATUS_NONE 419s ok 40 /driver/finger_status/changes 419s # End of finger_status tests 419s # Start of features tests 419s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_current' 419s # libfprint-device-DEBUG: Tod version info is 'current' 419s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_probe: Device Virtual device for debugging in action FPI_DEVICE_ACTION_PROBE 419s # 419s # libfprint-device-DEBUG: Device reported probe completion 419s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 419s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 419s ok 41 /driver/features/probe_updates 419s # End of features tests 419s # Start of initial_features tests 419s ok 42 /driver/initial_features/none 419s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_current' 419s # libfprint-device-DEBUG: Tod version info is 'current' 419s ok 43 /driver/initial_features/no_capture 419s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_current' 419s # libfprint-device-DEBUG: Tod version info is 'current' 419s ok 44 /driver/initial_features/no_verify 419s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_current' 419s # libfprint-device-DEBUG: Tod version info is 'current' 419s ok 45 /driver/initial_features/no_identify 419s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_current' 419s # libfprint-device-DEBUG: Tod version info is 'current' 419s ok 46 /driver/initial_features/no_storage 419s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_current' 419s # libfprint-device-DEBUG: Tod version info is 'current' 419s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_current' 419s # libfprint-device-DEBUG: Tod version info is 'current' 419s ok 47 /driver/initial_features/no_list 419s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_current' 419s # libfprint-device-DEBUG: Tod version info is 'current' 419s ok 48 /driver/initial_features/no_delete 419s ok 49 /driver/initial_features/no_clear 419s # End of initial_features tests 419s # Start of probe tests 419s # libfprint-device-DEBUG: Device reported probe completion 419s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 419s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 419s ok 50 /driver/probe/error 419s # libfprint-device-DEBUG: Device reported generic error (The operation is not supported on this device!) during action; action was: FPI_DEVICE_ACTION_PROBE 419s # libfprint-device-DEBUG: Device reported probe completion 419s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 419s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 419s ok 51 /driver/probe/action_error 419s # End of probe tests 419s # Start of open tests 419s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 419s # 419s # libfprint-device-DEBUG: Device reported open completion 419s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 419s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 419s ok 52 /driver/open/error 419s # End of open tests 419s # Start of close tests 419s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 419s # 419s # libfprint-device-DEBUG: Device reported open completion 419s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 419s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 419s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 419s # 419s # libfprint-device-DEBUG: Device reported close completion 419s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 419s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 419s ok 53 /driver/close/error 419s # End of close tests 419s # Start of enroll tests 419s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 419s # 419s # libfprint-device-DEBUG: Device reported open completion 419s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 419s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 419s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 419s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_enroll: Device Virtual device for debugging in action FPI_DEVICE_ACTION_ENROLL 419s # 419s # libfprint-device-DEBUG: Device reported enroll completion 419s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 419s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 419s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 419s # 419s # libfprint-device-DEBUG: Device reported close completion 419s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 419s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 419s ok 54 /driver/enroll/error 419s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 419s # 419s # libfprint-device-DEBUG: Device reported open completion 419s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 419s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 419s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 419s # libfprint-device-DEBUG: Device reported enroll progress, reported 223622039 of 25777708 have been completed 419s # libfprint-device-DEBUG: Device reported enroll progress, reported 1460390113 of 25777708 have been completed 419s # libfprint-device-DEBUG: Device reported enroll progress, reported 1513716898 of 25777708 have been completed 419s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_enroll: Device Virtual device for debugging in action FPI_DEVICE_ACTION_ENROLL 419s # 419s # libfprint-device-DEBUG: Device reported enroll completion 419s # libfprint-device-DEBUG: Print for finger FP_FINGER_UNKNOWN enrolled 419s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 419s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 419s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 419s # 419s # libfprint-device-DEBUG: Device reported close completion 419s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 419s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 419s ok 55 /driver/enroll/progress 419s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 419s # 419s # libfprint-device-DEBUG: Device reported open completion 419s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 419s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 419s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 419s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_enroll: Device Virtual device for debugging in action FPI_DEVICE_ACTION_ENROLL 419s # 419s # libfprint-device-DEBUG: Device reported enroll completion 419s # libfprint-device-DEBUG: Print for finger FP_FINGER_UNKNOWN enrolled 419s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 419s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 419s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 419s # 419s # libfprint-device-DEBUG: Device reported close completion 419s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 419s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 419s ok 56 /driver/enroll/update_nbis 419s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 419s # 419s # libfprint-device-DEBUG: Device reported open completion 419s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 419s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 419s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 419s # 419s # libfprint-device-DEBUG: Device reported close completion 419s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 419s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 419s ok 57 /driver/enroll/update_nbis_wrong_device 419s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 419s # 419s # libfprint-device-DEBUG: Device reported open completion 419s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 419s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 419s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 419s # 419s # libfprint-device-DEBUG: Device reported close completion 419s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 419s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 419s ok 58 /driver/enroll/update_nbis_wrong_driver 419s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 419s # 419s # libfprint-device-DEBUG: Device reported open completion 419s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 419s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 419s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 419s # 419s # libfprint-device-DEBUG: Device reported close completion 419s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 419s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 419s ok 59 /driver/enroll/update_nbis_missing_feature 419s # Start of error tests 419s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 419s # 419s # libfprint-device-DEBUG: Device reported open completion 419s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 419s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 419s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 419s # libfprint-device-DEBUG: Device reported enroll completion 419s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 419s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 419s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 419s # libfprint-device-DEBUG: Device reported enroll completion 419s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 419s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 419s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 419s # libfprint-device-DEBUG: Device reported enroll completion 419s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 419s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 419s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 419s # 419s # libfprint-device-DEBUG: Device reported close completion 419s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 419s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 419s ok 60 /driver/enroll/error/no_print 419s # End of error tests 419s # End of enroll tests 419s # Start of verify tests 419s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 419s # 419s # libfprint-device-DEBUG: Device reported open completion 419s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 419s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 419s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 419s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_verify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_VERIFY 419s # 419s # libfprint-device-DEBUG: Device reported verify result 419s # libfprint-device-DEBUG: Device reported verify completion 419s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 419s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 419s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 419s # 419s # libfprint-device-DEBUG: Device reported close completion 419s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 419s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 419s ok 61 /driver/verify/fail 419s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 419s # 419s # libfprint-device-DEBUG: Device reported open completion 419s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 419s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 419s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 419s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_verify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_VERIFY 419s # 419s # libfprint-device-DEBUG: Device reported verify result 419s # libfprint-device-DEBUG: Device reported verify completion 419s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 419s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 419s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 419s # 419s # libfprint-device-DEBUG: Device reported close completion 419s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 419s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 419s ok 62 /driver/verify/retry 419s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 419s # 419s # libfprint-device-DEBUG: Device reported open completion 419s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 419s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 419s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 419s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_verify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_VERIFY 419s # 419s # libfprint-device-DEBUG: Device reported verify completion 419s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 419s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 419s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 419s # 419s # libfprint-device-DEBUG: Device reported close completion 419s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 419s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 419s ok 63 /driver/verify/error 419s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 419s # 419s # libfprint-device-DEBUG: Device reported open completion 419s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 419s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 419s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 419s # 419s # libfprint-device-DEBUG: Device reported close completion 419s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 419s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 419s ok 64 /driver/verify/not_supported 419s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 419s # 419s # libfprint-device-DEBUG: Device reported open completion 419s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 419s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 419s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 419s # libfprint-device-DEBUG: Device reported verify result 419s # libfprint-device-DEBUG: Device reported verify completion 419s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 419s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 419s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 419s # 419s # libfprint-device-DEBUG: Device reported close completion 419s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 419s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 419s ok 65 /driver/verify/report_no_cb 419s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 419s # 419s # libfprint-device-DEBUG: Device reported open completion 419s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 419s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 419s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 419s # libfprint-device-DEBUG: Device reported verify completion 419s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 419s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 419s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 419s # 419s # libfprint-device-DEBUG: Device reported close completion 419s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 419s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 419s ok 66 /driver/verify/not_reported 419s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 419s # 419s # libfprint-device-DEBUG: Device reported open completion 419s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 419s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 419s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 419s # libfprint-device-DEBUG: Device reported verify result 419s # libfprint-device-DEBUG: Device reported verify completion 419s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 419s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 419s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 419s # libfprint-device-DEBUG: Device reported verify result 419s # libfprint-device-DEBUG: Device reported verify completion 419s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 419s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 419s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 419s # libfprint-device-DEBUG: Device reported verify result 419s # libfprint-device-DEBUG: Device reported verify completion 419s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 419s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 419s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 419s # libfprint-device-DEBUG: Device reported verify result 419s # libfprint-device-DEBUG: Device reported verify completion 419s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 419s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 419s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 419s # libfprint-device-DEBUG: Device reported verify result 419s # libfprint-device-DEBUG: Device reported verify completion 419s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 419s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 419s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 419s # 419s # libfprint-device-DEBUG: Device reported close completion 419s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 419s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 419s ok 67 /driver/verify/complete_retry 419s # End of verify tests 419s # Start of identify tests 419s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 419s # 419s # libfprint-device-DEBUG: Device reported open completion 419s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 419s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 419s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 419s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_identify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY 419s # 419s # libfprint-device-DEBUG: Device reported identify result 419s # libfprint-device-DEBUG: Device reported identify completion 419s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 419s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 419s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 419s # 419s # libfprint-device-DEBUG: Device reported close completion 419s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 419s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_COLD 419s ok 68 /driver/identify/fail 419s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 419s # 419s # libfprint-device-DEBUG: Device reported open completion 419s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 419s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 419s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 419s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_identify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY 419s # 419s # libfprint-device-DEBUG: Device reported identify result 419s # libfprint-device-DEBUG: Device reported identify completion 419s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 419s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 419s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 419s # 419s # libfprint-device-DEBUG: Device reported close completion 419s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 419s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 419s ok 69 /driver/identify/retry 419s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 419s # 419s # libfprint-device-DEBUG: Device reported open completion 419s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 419s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 419s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 419s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_identify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY 419s # 419s # libfprint-device-DEBUG: Device reported identify completion 419s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 419s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 419s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 419s # 419s # libfprint-device-DEBUG: Device reported close completion 419s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 419s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 419s ok 70 /driver/identify/error 419s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 419s # 419s # libfprint-device-DEBUG: Device reported open completion 419s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 419s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 419s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 419s # libfprint-device-DEBUG: Device reported identify completion 419s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 419s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 419s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 419s # 419s # libfprint-device-DEBUG: Device reported close completion 419s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 419s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 419s ok 71 /driver/identify/not_reported 419s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 419s # 419s # libfprint-device-DEBUG: Device reported open completion 419s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 419s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 419s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 419s # libfprint-device-DEBUG: Device reported identify result 419s # libfprint-device-DEBUG: Device reported identify completion 419s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 419s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 419s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 419s # libfprint-device-DEBUG: Device reported identify result 419s # libfprint-device-DEBUG: Device reported identify completion 419s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 419s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 419s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 419s # libfprint-device-DEBUG: Device reported identify result 419s # libfprint-device-DEBUG: Device reported identify completion 419s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 419s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 419s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 419s # 419s # libfprint-device-DEBUG: Device reported close completion 419s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 419s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 419s ok 72 /driver/identify/complete_retry 419s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 419s # 419s # libfprint-device-DEBUG: Device reported open completion 419s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 419s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 419s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 419s # libfprint-device-DEBUG: Device reported identify result 419s # libfprint-device-DEBUG: Device reported identify completion 419s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 419s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 419s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 419s # 419s # libfprint-device-DEBUG: Device reported close completion 419s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 419s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 419s ok 73 /driver/identify/report_no_cb 419s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_current' 419s # libfprint-device-DEBUG: Tod version info is 'current' 419s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 419s # 419s # libfprint-device-DEBUG: Device reported open completion 419s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 419s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 419s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 419s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_suspend: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY 419s # 419s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_resume: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY 419s # 419s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_identify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY 419s # 419s # libfprint-device-DEBUG: Device reported identify result 419s # libfprint-device-DEBUG: Device reported identify completion 419s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 419s # libfprint-device-DEBUG: Updated temperature model after 0.02 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 419s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 419s # 419s # libfprint-device-DEBUG: Device reported close completion 419s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 419s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 419s ok 74 /driver/identify/suspend_continues 419s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_current' 419s # libfprint-device-DEBUG: Tod version info is 'current' 419s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 419s # 419s # libfprint-device-DEBUG: Device reported open completion 419s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 419s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 419s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 419s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_suspend: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY 419s # 419s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_identify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY 419s # 419s # libfprint-device-DEBUG: Device reported identify result 419s # libfprint-device-DEBUG: Device reported identify completion 419s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 419s # libfprint-device-DEBUG: Updated temperature model after 0.02 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 419s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 419s # 419s # libfprint-device-DEBUG: Device reported close completion 419s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 419s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 419s ok 75 /driver/identify/suspend_succeeds 419s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_current' 419s # libfprint-device-DEBUG: Tod version info is 'current' 419s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 419s # 419s # libfprint-device-DEBUG: Device reported open completion 419s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 419s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 419s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 419s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_suspend: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY 419s # 419s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_identify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY 419s # 419s # libfprint-device-DEBUG: Device reported identify completion 419s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 419s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 419s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 419s # 419s # libfprint-device-DEBUG: Device reported close completion 419s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 419s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 419s ok 76 /driver/identify/suspend_busy_error 419s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_current' 419s # libfprint-device-DEBUG: Tod version info is 'current' 419s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 419s # 419s # libfprint-device-DEBUG: Device reported open completion 419s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 419s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 419s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 419s # 419s # libfprint-device-DEBUG: Device reported close completion 419s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 419s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 419s ok 77 /driver/identify/suspend_while_idle 419s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_current' 419s # libfprint-device-DEBUG: Tod version info is 'current' 419s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 419s # 419s # libfprint-device-DEBUG: Device reported open completion 419s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 419s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 419s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 419s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.30, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 421s # libfprint-device-DEBUG: Updated temperature model after 2.00 seconds, ratio 0.30 -> 0.74, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_HOT 421s # libfprint-device-DEBUG: Idle cancelling on ongoing operation! 421s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_cancel: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY 421s # 421s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_identify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY 421s # 421s # libfprint-device-DEBUG: Device reported identify completion 421s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 421s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.74 -> 0.74, active 0 -> 0, FP_TEMPERATURE_HOT -> FP_TEMPERATURE_HOT 421s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.74 -> 0.74, active 1 -> 1, FP_TEMPERATURE_HOT -> FP_TEMPERATURE_HOT 421s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.74 -> 0.74, active 0 -> 0, FP_TEMPERATURE_HOT -> FP_TEMPERATURE_HOT 422s Executing: libfprint-2/tod-fpi-device-tod-fake_test_dev_tod_current.test 423s # libfprint-device-DEBUG: Updated temperature model after 2.09 seconds, ratio 0.74 -> 0.49, active 0 -> 0, FP_TEMPERATURE_HOT -> FP_TEMPERATURE_WARM 426s # libfprint-device-DEBUG: Updated temperature model after 3.10 seconds, ratio 0.49 -> 0.26, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_COLD 426s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 426s # 426s # libfprint-device-DEBUG: Device reported close completion 426s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 426s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.26 -> 0.26, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 426s ok 78 /driver/identify/warmup_cooldown 426s # slow test /driver/identify/warmup_cooldown executed in 7.30 secs 426s # End of identify tests 426s # Start of capture tests 426s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 426s # 426s # libfprint-device-DEBUG: Device reported open completion 426s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 426s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 426s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 426s # 426s # libfprint-device-DEBUG: Device reported close completion 426s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 426s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 426s ok 79 /driver/capture/not_supported 426s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 426s # 426s # libfprint-device-DEBUG: Device reported open completion 426s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 426s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 426s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 426s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_capture: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CAPTURE 426s # 426s # libfprint-device-DEBUG: Device reported capture completion 426s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CAPTURE in idle! 426s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 426s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 426s # 426s # libfprint-device-DEBUG: Device reported close completion 426s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 426s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 426s ok 80 /driver/capture/error 426s # End of capture tests 426s # Start of list tests 426s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 426s # 426s # libfprint-device-DEBUG: Device reported open completion 426s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 426s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 426s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_list: Device Virtual device for debugging in action FPI_DEVICE_ACTION_LIST 426s # 426s # libfprint-device-DEBUG: Device reported listing completion 426s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_LIST in idle! 426s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 426s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 426s # 426s # libfprint-device-DEBUG: Device reported close completion 426s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 426s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 426s ok 81 /driver/list/error 426s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 426s # 426s # libfprint-device-DEBUG: Device reported open completion 426s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 426s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 426s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 426s # 426s # libfprint-device-DEBUG: Device reported close completion 426s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 426s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 426s ok 82 /driver/list/no_storage 426s # End of list tests 426s # Start of delete tests 426s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 426s # 426s # libfprint-device-DEBUG: Device reported open completion 426s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 426s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 426s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_delete: Device Virtual device for debugging in action FPI_DEVICE_ACTION_DELETE 426s # 426s # libfprint-device-DEBUG: Device reported deletion completion 426s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_DELETE in idle! 426s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 426s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 426s # 426s # libfprint-device-DEBUG: Device reported close completion 426s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 426s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 426s ok 83 /driver/delete/error 426s # End of delete tests 426s # Start of clear_storage tests 426s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 426s # 426s # libfprint-device-DEBUG: Device reported open completion 426s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 426s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 426s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_current' 426s # libfprint-device-DEBUG: Tod version info is 'current' 426s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_clear_storage: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLEAR_STORAGE 426s # 426s # libfprint-device-DEBUG: Device reported deletion completion 426s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 426s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 426s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 426s # 426s # libfprint-device-DEBUG: Device reported close completion 426s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 426s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 426s ok 84 /driver/clear_storage/error 426s # End of clear_storage tests 426s # Start of cancel tests 426s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 426s # 426s # libfprint-device-DEBUG: Device reported open completion 426s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 426s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 426s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_delete: Device Virtual device for debugging in action FPI_DEVICE_ACTION_DELETE 426s # 426s # libfprint-device-DEBUG: Device reported deletion completion 426s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_DELETE in idle! 426s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 426s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 426s # 426s # libfprint-device-DEBUG: Device reported close completion 426s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 426s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 426s ok 85 /driver/cancel/fail 426s # End of cancel tests 426s # Start of get_current_action tests 426s # libfprint-device-DEBUG: Device reported open completion 426s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 426s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 426s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 426s # 426s # libfprint-device-DEBUG: Device reported close completion 426s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 426s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 426s ok 86 /driver/get_current_action/open 426s # End of get_current_action tests 426s # Start of get_cancellable tests 426s ok 87 /driver/get_cancellable/error 426s # libfprint-device-DEBUG: Device reported open completion 426s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 426s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 426s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 426s # 426s # libfprint-device-DEBUG: Device reported close completion 426s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 426s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 426s ok 88 /driver/get_cancellable/open 426s # Start of open tests 426s # libfprint-device-DEBUG: Device reported open completion 426s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 426s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 426s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 426s # 426s # libfprint-device-DEBUG: Device reported close completion 426s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 426s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 426s ok 89 /driver/get_cancellable/open/internal 426s # End of open tests 426s # End of get_cancellable tests 426s # Start of action_is_cancelled tests 426s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_current' 426s # libfprint-device-DEBUG: Tod version info is 'current' 426s # libfprint-device-DEBUG: Device reported open completion 426s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 426s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 426s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 426s # 426s # libfprint-device-DEBUG: Device reported close completion 426s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 426s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 426s ok 90 /driver/action_is_cancelled/open 426s ok 91 /driver/action_is_cancelled/error 426s # Start of open tests 426s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_current' 426s # libfprint-device-DEBUG: Tod version info is 'current' 426s # libfprint-device-DEBUG: Device reported open completion 426s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 426s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 426s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 426s # 426s # libfprint-device-DEBUG: Device reported close completion 426s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 426s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 426s ok 92 /driver/action_is_cancelled/open/internal 426s # End of open tests 426s # End of action_is_cancelled tests 426s # Start of complete_action tests 426s # Start of all tests 426s ok 93 /driver/complete_action/all/error 426s # End of all tests 426s # End of complete_action tests 426s # Start of action_error tests 426s ok 94 /driver/action_error/error 426s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 426s # 426s # libfprint-device-DEBUG: Device reported generic error (Passed (print) data is not valid.) during action; action was: FPI_DEVICE_ACTION_OPEN 426s # libfprint-device-DEBUG: Device reported open completion 426s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 426s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 426s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 426s # 426s # libfprint-device-DEBUG: Device reported open completion 426s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 426s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 426s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 426s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_enroll: Device Virtual device for debugging in action FPI_DEVICE_ACTION_ENROLL 426s # 426s # libfprint-device-DEBUG: Device reported generic error (Passed (print) data is not valid.) during action; action was: FPI_DEVICE_ACTION_ENROLL 426s # libfprint-device-DEBUG: Device reported enroll completion 426s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 426s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 426s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 426s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_verify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_VERIFY 426s # 426s # libfprint-device-DEBUG: Device reported generic error (Passed (print) data is not valid.) during action; action was: FPI_DEVICE_ACTION_VERIFY 426s # libfprint-device-DEBUG: Device reported verify completion 426s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 426s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 426s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 426s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_identify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY 426s # 426s # libfprint-device-DEBUG: Device reported generic error (Passed (print) data is not valid.) during action; action was: FPI_DEVICE_ACTION_IDENTIFY 426s # libfprint-device-DEBUG: Device reported identify completion 426s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 426s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 426s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 426s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_capture: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CAPTURE 426s # 426s # libfprint-device-DEBUG: Device reported generic error (Passed (print) data is not valid.) during action; action was: FPI_DEVICE_ACTION_CAPTURE 426s # libfprint-device-DEBUG: Device reported capture completion 426s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CAPTURE in idle! 426s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 426s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_list: Device Virtual device for debugging in action FPI_DEVICE_ACTION_LIST 426s # 426s # libfprint-device-DEBUG: Device reported generic error (Passed (print) data is not valid.) during action; action was: FPI_DEVICE_ACTION_LIST 426s # libfprint-device-DEBUG: Device reported listing completion 426s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_LIST in idle! 426s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 426s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_delete: Device Virtual device for debugging in action FPI_DEVICE_ACTION_DELETE 426s # 426s # libfprint-device-DEBUG: Device reported generic error (Passed (print) data is not valid.) during action; action was: FPI_DEVICE_ACTION_DELETE 426s # libfprint-device-DEBUG: Device reported deletion completion 426s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_DELETE in idle! 426s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 426s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_current' 426s # libfprint-device-DEBUG: Tod version info is 'current' 426s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_clear_storage: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLEAR_STORAGE 426s # 426s # libfprint-device-DEBUG: Device reported generic error (Passed (print) data is not valid.) during action; action was: FPI_DEVICE_ACTION_CLEAR_STORAGE 426s # libfprint-device-DEBUG: Device reported deletion completion 426s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 426s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 426s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 426s # 426s # libfprint-device-DEBUG: Device reported generic error (Passed (print) data is not valid.) during action; action was: FPI_DEVICE_ACTION_CLOSE 426s # libfprint-device-DEBUG: Device reported close completion 426s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 426s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 426s ok 95 /driver/action_error/all 426s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 426s # 426s # libfprint-device-DEBUG: Device reported open completion 426s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 426s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 426s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 426s # 426s # libfprint-device-DEBUG: Device reported open completion 426s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 426s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 426s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 426s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_enroll: Device Virtual device for debugging in action FPI_DEVICE_ACTION_ENROLL 426s # 426s # libfprint-device-DEBUG: Device reported enroll completion 426s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 426s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 426s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 426s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_verify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_VERIFY 426s # 426s # libfprint-device-DEBUG: Device reported verify completion 426s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 426s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 426s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 426s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_identify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY 426s # 426s # libfprint-device-DEBUG: Device reported identify completion 426s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 426s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 426s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 426s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_capture: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CAPTURE 426s # 426s # libfprint-device-DEBUG: Device reported capture completion 426s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CAPTURE in idle! 426s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 426s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_list: Device Virtual device for debugging in action FPI_DEVICE_ACTION_LIST 426s # 426s # libfprint-device-DEBUG: Device reported listing completion 426s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_LIST in idle! 426s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 426s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_delete: Device Virtual device for debugging in action FPI_DEVICE_ACTION_DELETE 426s # 426s # libfprint-device-DEBUG: Device reported deletion completion 426s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_DELETE in idle! 426s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 426s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_current' 426s # libfprint-device-DEBUG: Tod version info is 'current' 426s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_clear_storage: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLEAR_STORAGE 426s # 426s # libfprint-device-DEBUG: Device reported deletion completion 426s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 426s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 426s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 426s # 426s # libfprint-device-DEBUG: Device reported close completion 426s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 426s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 426s ok 96 /driver/action_error/fail 426s # End of action_error tests 426s # Start of timeout tests 426s ok 97 /driver/timeout/cancelled 426s # End of timeout tests 426s # End of driver tests 426s PASS: libfprint-2/tod-fpi-device-tod-fake_test_dev_tod_current.test 426s Running test: libfprint-2/driver-egismoc-05a1.test 426s ** (umockdev-run:2241): DEBUG: 00:54:35.468: umockdev.vala:127: Created udev test bed /tmp/umockdev.SD8712 426s ** (umockdev-run:2241): DEBUG: 00:54:35.468: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0/usb1/1-5 426s ** (umockdev-run:2241): DEBUG: 00:54:35.470: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0/usb1/1-5 (subsystem usb) 426s ** (umockdev-run:2241): DEBUG: 00:54:35.475: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.SD8712/dev/bus/usb/001/003 426s ** (umockdev-run:2241): DEBUG: 00:54:35.476: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0/usb1 426s ** (umockdev-run:2241): DEBUG: 00:54:35.477: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0/usb1 (subsystem usb) 426s ** (umockdev-run:2241): DEBUG: 00:54:35.481: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.SD8712/dev/bus/usb/001/001 426s ** (umockdev-run:2241): DEBUG: 00:54:35.482: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0 426s ** (umockdev-run:2241): DEBUG: 00:54:35.482: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0 (subsystem pci) 426s (process:2245): libfprint-context-DEBUG: 00:54:35.596: Initializing FpContext (libfprint version 1.94.8+tod1) 426s (process:2245): libfprint-tod-DEBUG: 00:54:35.596: Impossible to load the shared drivers dir Error opening directory “/usr/lib/arm-linux-gnueabihf/libfprint-2/tod-1”: No such file or directory 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.599: 7399843660431: ../libfprint/drivers/egismoc/egismoc.c:1597 426s (process:2245): libfprint-context-DEBUG: 00:54:35.599: No driver found for USB device 1D6B:0002 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.600: egismoc_probe enter --> 426s (process:2245): libfprint-device-DEBUG: 00:54:35.601: Device reported probe completion 426s (process:2245): libfprint-device-DEBUG: 00:54:35.601: Completing action FPI_DEVICE_ACTION_PROBE in idle! 426s (process:2245): libfprint-device-DEBUG: 00:54:35.601: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.602: Opening device 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.603: [egismoc] DEV_INIT_STATES entering state 0 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.603: [egismoc] DEV_INIT_STATES entering state 1 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.604: [egismoc] DEV_INIT_STATES entering state 2 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.604: [egismoc] DEV_INIT_STATES entering state 3 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.605: [egismoc] DEV_INIT_STATES entering state 4 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.605: [egismoc] DEV_INIT_STATES entering state 5 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.605: Execute command and get response 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.605: Get check bytes 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.605: [egismoc] CMD_STATES entering state 0 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.606: [egismoc] CMD_STATES entering state 1 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.606: Command receive callback 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.606: [egismoc] CMD_STATES completed successfully 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.606: Firmware version callback 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.606: Response suffix valid: yes 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.606: Device firmware version is 9050.1.2.13 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.606: [egismoc] DEV_INIT_STATES completed successfully 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.606: Task SSM done 426s (process:2245): libfprint-device-DEBUG: 00:54:35.606: Device reported open completion 426s (process:2245): libfprint-device-DEBUG: 00:54:35.606: Completing action FPI_DEVICE_ACTION_OPEN in idle! 426s (process:2245): libfprint-device-DEBUG: 00:54:35.606: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.607: List 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.607: [egismoc] LIST_STATES entering state 0 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.607: Execute command and get response 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.607: Get check bytes 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.607: [egismoc] CMD_STATES entering state 0 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.607: [egismoc] CMD_STATES entering state 1 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.608: Command receive callback 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.608: [egismoc] CMD_STATES completed successfully 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.608: List callback 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.608: Device fingerprint 1: FP1-20231209-3-A9E16FBD-root 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.608: Device fingerprint 2: FP1-20231209-1-85DC4FAC-root 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.608: Device fingerprint 3: FP1-20231209-2-04EFB67C-root 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.608: Number of currently enrolled fingerprints on the device is 3 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.608: [egismoc] LIST_STATES entering state 1 426s (process:2245): libfprint-device-DEBUG: 00:54:35.608: Device reported listing completion 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.608: [egismoc] LIST_STATES completed successfully 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.608: Task SSM done 426s (process:2245): libfprint-device-DEBUG: 00:54:35.608: Completing action FPI_DEVICE_ACTION_LIST in idle! 426s (process:2245): libfprint-device-DEBUG: 00:54:35.608: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.608: Clear storage 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.608: [egismoc] DELETE_STATES entering state 0 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.608: Execute command and get response 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.608: Get check bytes 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.608: [egismoc] CMD_STATES entering state 0 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.608: [egismoc] CMD_STATES entering state 1 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.609: Command receive callback 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.609: [egismoc] CMD_STATES completed successfully 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.609: List callback 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.609: Device fingerprint 1: FP1-20231209-3-A9E16FBD-root 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.609: Device fingerprint 2: FP1-20231209-1-85DC4FAC-root 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.609: Device fingerprint 3: FP1-20231209-2-04EFB67C-root 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.609: Number of currently enrolled fingerprints on the device is 3 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.609: [egismoc] DELETE_STATES entering state 1 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.609: Get delete command 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.609: Execute command and get response 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.609: Get check bytes 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.609: [egismoc] CMD_STATES entering state 0 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.609: [egismoc] CMD_STATES entering state 1 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.610: Command receive callback 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.610: [egismoc] CMD_STATES completed successfully 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.610: Delete callback 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.610: Response prefix valid: yes 426s (process:2245): libfprint-device-DEBUG: 00:54:35.610: Device reported deletion completion 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.610: [egismoc] DELETE_STATES completed successfully 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.610: Task SSM done 426s (process:2245): libfprint-device-DEBUG: 00:54:35.610: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 426s (process:2245): libfprint-device-DEBUG: 00:54:35.610: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.610: List 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.610: [egismoc] LIST_STATES entering state 0 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.610: Execute command and get response 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.610: Get check bytes 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.610: [egismoc] CMD_STATES entering state 0 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.610: [egismoc] CMD_STATES entering state 1 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.610: Command receive callback 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.611: [egismoc] CMD_STATES completed successfully 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.611: List callback 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.611: Number of currently enrolled fingerprints on the device is 0 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.611: [egismoc] LIST_STATES entering state 1 426s (process:2245): libfprint-device-DEBUG: 00:54:35.611: Device reported listing completion 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.611: [egismoc] LIST_STATES completed successfully 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.611: Task SSM done 426s (process:2245): libfprint-device-DEBUG: 00:54:35.611: Completing action FPI_DEVICE_ACTION_LIST in idle! 426s (process:2245): libfprint-device-DEBUG: 00:54:35.611: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 426s (process:2245): libfprint-device-DEBUG: 00:54:35.611: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.611: Enroll 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.611: [egismoc] ENROLL_STATES entering state 0 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.611: Execute command and get response 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.611: Get check bytes 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.611: [egismoc] CMD_STATES entering state 0 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.612: [egismoc] CMD_STATES entering state 1 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.612: Command receive callback 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.612: [egismoc] CMD_STATES completed successfully 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.612: List callback 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.612: Number of currently enrolled fingerprints on the device is 0 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.612: [egismoc] ENROLL_STATES entering state 1 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.612: [egismoc] ENROLL_STATES entering state 2 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.612: Execute command and get response 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.612: Get check bytes 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.612: [egismoc] CMD_STATES entering state 0 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.613: [egismoc] CMD_STATES entering state 1 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.613: Command receive callback 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.613: [egismoc] CMD_STATES completed successfully 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.613: Task SSM next state callback 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.613: [egismoc] ENROLL_STATES entering state 3 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.613: Execute command and get response 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.613: Get check bytes 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.613: [egismoc] CMD_STATES entering state 0 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.614: [egismoc] CMD_STATES entering state 1 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.614: Command receive callback 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.614: [egismoc] CMD_STATES completed successfully 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.614: Task SSM next state callback 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.614: [egismoc] ENROLL_STATES entering state 4 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.614: Wait for finger on sensor 426s (process:2245): libfprint-device-DEBUG: 00:54:35.614: Device reported finger status change: FP_FINGER_STATUS_NEEDED 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.615: Finger on sensor callback 426s (process:2245): libfprint-device-DEBUG: 00:54:35.615: Device reported finger status change: FP_FINGER_STATUS_PRESENT 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.615: [egismoc] ENROLL_STATES entering state 5 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.615: Execute command and get response 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.615: Get check bytes 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.615: [egismoc] CMD_STATES entering state 0 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.615: [egismoc] CMD_STATES entering state 1 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.615: Command receive callback 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.615: [egismoc] CMD_STATES completed successfully 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.615: Task SSM next state callback 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.615: [egismoc] ENROLL_STATES entering state 6 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.615: Get check command 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.615: Execute command and get response 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.615: Get check bytes 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.615: [egismoc] CMD_STATES entering state 0 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.616: [egismoc] CMD_STATES entering state 1 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.616: Command receive callback 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.616: [egismoc] CMD_STATES completed successfully 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.616: Enroll check callback 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.616: Response suffix valid: yes 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.616: [egismoc] ENROLL_STATES entering state 7 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.616: Execute command and get response 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.616: Get check bytes 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.616: [egismoc] CMD_STATES entering state 0 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.617: [egismoc] CMD_STATES entering state 1 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.617: Command receive callback 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.617: [egismoc] CMD_STATES completed successfully 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.617: Task SSM next state callback 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.617: [egismoc] ENROLL_STATES entering state 8 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.617: Execute command and get response 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.617: Get check bytes 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.617: [egismoc] CMD_STATES entering state 0 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.618: [egismoc] CMD_STATES entering state 1 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.618: Command receive callback 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.618: [egismoc] CMD_STATES completed successfully 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.618: Task SSM next state callback 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.618: [egismoc] ENROLL_STATES entering state 9 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.618: Execute command and get response 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.618: Get check bytes 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.618: [egismoc] CMD_STATES entering state 0 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.619: [egismoc] CMD_STATES entering state 1 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.619: Command receive callback 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.619: [egismoc] CMD_STATES completed successfully 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.619: Task SSM next state callback 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.619: [egismoc] ENROLL_STATES entering state 10 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.619: Wait for finger on sensor 426s (process:2245): libfprint-device-DEBUG: 00:54:35.619: Device reported finger status change: FP_FINGER_STATUS_NEEDED 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.619: Finger on sensor callback 426s (process:2245): libfprint-device-DEBUG: 00:54:35.619: Device reported finger status change: FP_FINGER_STATUS_PRESENT 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.619: [egismoc] ENROLL_STATES entering state 11 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.619: Execute command and get response 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.619: Get check bytes 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.619: [egismoc] CMD_STATES entering state 0 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.620: [egismoc] CMD_STATES entering state 1 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.620: Command receive callback 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.620: [egismoc] CMD_STATES completed successfully 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.620: Read capture callback 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.620: Response prefix valid: yes 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.620: Response suffix valid: yes 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.620: Partial capture successful. Please touch the sensor again (1/10) 426s (process:2245): libfprint-device-DEBUG: 00:54:35.620: Device reported enroll progress, reported 1 of 10 have been completed 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.620: [egismoc] ENROLL_STATES entering state 8 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.620: Execute command and get response 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.620: Get check bytes 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.620: [egismoc] CMD_STATES entering state 0 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.621: [egismoc] CMD_STATES entering state 1 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.621: Command receive callback 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.621: [egismoc] CMD_STATES completed successfully 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.621: Task SSM next state callback 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.621: [egismoc] ENROLL_STATES entering state 9 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.621: Execute command and get response 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.621: Get check bytes 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.621: [egismoc] CMD_STATES entering state 0 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.622: [egismoc] CMD_STATES entering state 1 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.622: Command receive callback 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.622: [egismoc] CMD_STATES completed successfully 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.622: Task SSM next state callback 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.622: [egismoc] ENROLL_STATES entering state 10 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.622: Wait for finger on sensor 426s (process:2245): libfprint-device-DEBUG: 00:54:35.622: Device reported finger status change: FP_FINGER_STATUS_NEEDED 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.623: Finger on sensor callback 426s (process:2245): libfprint-device-DEBUG: 00:54:35.623: Device reported finger status change: FP_FINGER_STATUS_PRESENT 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.623: [egismoc] ENROLL_STATES entering state 11 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.623: Execute command and get response 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.623: Get check bytes 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.623: [egismoc] CMD_STATES entering state 0 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.623: [egismoc] CMD_STATES entering state 1 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.624: Command receive callback 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.624: [egismoc] CMD_STATES completed successfully 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.624: Read capture callback 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.624: Response prefix valid: yes 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.624: Response suffix valid: yes 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.624: Partial capture successful. Please touch the sensor again (2/10) 426s (process:2245): libfprint-device-DEBUG: 00:54:35.624: Device reported enroll progress, reported 2 of 10 have been completed 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.624: [egismoc] ENROLL_STATES entering state 8 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.624: Execute command and get response 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.624: Get check bytes 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.624: [egismoc] CMD_STATES entering state 0 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.624: [egismoc] CMD_STATES entering state 1 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.624: Command receive callback 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.625: [egismoc] CMD_STATES completed successfully 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.625: Task SSM next state callback 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.625: [egismoc] ENROLL_STATES entering state 9 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.625: Execute command and get response 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.625: Get check bytes 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.625: [egismoc] CMD_STATES entering state 0 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.625: [egismoc] CMD_STATES entering state 1 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.625: Command receive callback 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.625: [egismoc] CMD_STATES completed successfully 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.625: Task SSM next state callback 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.625: [egismoc] ENROLL_STATES entering state 10 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.625: Wait for finger on sensor 426s (process:2245): libfprint-device-DEBUG: 00:54:35.625: Device reported finger status change: FP_FINGER_STATUS_NEEDED 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.626: Finger on sensor callback 426s (process:2245): libfprint-device-DEBUG: 00:54:35.626: Device reported finger status change: FP_FINGER_STATUS_PRESENT 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.626: [egismoc] ENROLL_STATES entering state 11 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.626: Execute command and get response 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.626: Get check bytes 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.626: [egismoc] CMD_STATES entering state 0 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.626: [egismoc] CMD_STATES entering state 1 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.627: Command receive callback 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.627: [egismoc] CMD_STATES completed successfully 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.627: Read capture callback 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.627: Response prefix valid: NO 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.627: Response prefix valid: NO 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.627: Response prefix valid: yes 426s (process:2245): libfprint-device-DEBUG: 00:54:35.627: Device reported enroll progress, reported 2 of 10 have been completed 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.627: [egismoc] ENROLL_STATES entering state 8 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.627: Execute command and get response 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.627: Get check bytes 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.627: [egismoc] CMD_STATES entering state 0 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.627: [egismoc] CMD_STATES entering state 1 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.628: Command receive callback 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.628: [egismoc] CMD_STATES completed successfully 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.628: Task SSM next state callback 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.628: [egismoc] ENROLL_STATES entering state 9 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.628: Execute command and get response 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.628: Get check bytes 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.628: [egismoc] CMD_STATES entering state 0 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.628: [egismoc] CMD_STATES entering state 1 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.629: Command receive callback 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.629: [egismoc] CMD_STATES completed successfully 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.629: Task SSM next state callback 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.629: [egismoc] ENROLL_STATES entering state 10 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.629: Wait for finger on sensor 426s (process:2245): libfprint-device-DEBUG: 00:54:35.629: Device reported finger status change: FP_FINGER_STATUS_NEEDED 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.629: Finger on sensor callback 426s (process:2245): libfprint-device-DEBUG: 00:54:35.629: Device reported finger status change: FP_FINGER_STATUS_PRESENT 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.629: [egismoc] ENROLL_STATES entering state 11 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.629: Execute command and get response 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.629: Get check bytes 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.629: [egismoc] CMD_STATES entering state 0 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.629: [egismoc] CMD_STATES entering state 1 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.630: Command receive callback 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.630: [egismoc] CMD_STATES completed successfully 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.630: Read capture callback 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.630: Response prefix valid: yes 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.630: Response suffix valid: yes 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.630: Partial capture successful. Please touch the sensor again (3/10) 426s (process:2245): libfprint-device-DEBUG: 00:54:35.630: Device reported enroll progress, reported 3 of 10 have been completed 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.630: [egismoc] ENROLL_STATES entering state 8 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.630: Execute command and get response 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.630: Get check bytes 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.630: [egismoc] CMD_STATES entering state 0 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.630: [egismoc] CMD_STATES entering state 1 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.631: Command receive callback 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.631: [egismoc] CMD_STATES completed successfully 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.631: Task SSM next state callback 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.631: [egismoc] ENROLL_STATES entering state 9 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.631: Execute command and get response 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.631: Get check bytes 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.631: [egismoc] CMD_STATES entering state 0 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.631: [egismoc] CMD_STATES entering state 1 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.632: Command receive callback 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.632: [egismoc] CMD_STATES completed successfully 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.632: Task SSM next state callback 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.632: [egismoc] ENROLL_STATES entering state 10 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.632: Wait for finger on sensor 426s (process:2245): libfprint-device-DEBUG: 00:54:35.632: Device reported finger status change: FP_FINGER_STATUS_NEEDED 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.632: Finger on sensor callback 426s (process:2245): libfprint-device-DEBUG: 00:54:35.632: Device reported finger status change: FP_FINGER_STATUS_PRESENT 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.632: [egismoc] ENROLL_STATES entering state 11 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.632: Execute command and get response 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.632: Get check bytes 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.632: [egismoc] CMD_STATES entering state 0 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.633: [egismoc] CMD_STATES entering state 1 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.633: Command receive callback 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.633: [egismoc] CMD_STATES completed successfully 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.633: Read capture callback 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.633: Response prefix valid: yes 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.633: Response suffix valid: yes 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.633: Partial capture successful. Please touch the sensor again (4/10) 426s (process:2245): libfprint-device-DEBUG: 00:54:35.633: Device reported enroll progress, reported 4 of 10 have been completed 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.633: [egismoc] ENROLL_STATES entering state 8 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.633: Execute command and get response 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.633: Get check bytes 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.633: [egismoc] CMD_STATES entering state 0 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.633: [egismoc] CMD_STATES entering state 1 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.634: Command receive callback 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.634: [egismoc] CMD_STATES completed successfully 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.634: Task SSM next state callback 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.634: [egismoc] ENROLL_STATES entering state 9 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.634: Execute command and get response 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.634: Get check bytes 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.634: [egismoc] CMD_STATES entering state 0 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.634: [egismoc] CMD_STATES entering state 1 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.635: Command receive callback 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.635: [egismoc] CMD_STATES completed successfully 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.635: Task SSM next state callback 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.635: [egismoc] ENROLL_STATES entering state 10 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.635: Wait for finger on sensor 426s (process:2245): libfprint-device-DEBUG: 00:54:35.635: Device reported finger status change: FP_FINGER_STATUS_NEEDED 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.635: Finger on sensor callback 426s (process:2245): libfprint-device-DEBUG: 00:54:35.635: Device reported finger status change: FP_FINGER_STATUS_PRESENT 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.635: [egismoc] ENROLL_STATES entering state 11 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.635: Execute command and get response 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.635: Get check bytes 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.635: [egismoc] CMD_STATES entering state 0 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.636: [egismoc] CMD_STATES entering state 1 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.636: Command receive callback 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.636: [egismoc] CMD_STATES completed successfully 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.636: Read capture callback 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.636: Response prefix valid: yes 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.636: Response suffix valid: yes 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.636: Partial capture successful. Please touch the sensor again (5/10) 426s (process:2245): libfprint-device-DEBUG: 00:54:35.636: Device reported enroll progress, reported 5 of 10 have been completed 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.636: [egismoc] ENROLL_STATES entering state 8 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.636: Execute command and get response 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.636: Get check bytes 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.636: [egismoc] CMD_STATES entering state 0 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.636: [egismoc] CMD_STATES entering state 1 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.637: Command receive callback 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.637: [egismoc] CMD_STATES completed successfully 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.637: Task SSM next state callback 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.637: [egismoc] ENROLL_STATES entering state 9 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.637: Execute command and get response 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.637: Get check bytes 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.637: [egismoc] CMD_STATES entering state 0 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.637: [egismoc] CMD_STATES entering state 1 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.638: Command receive callback 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.638: [egismoc] CMD_STATES completed successfully 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.638: Task SSM next state callback 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.638: [egismoc] ENROLL_STATES entering state 10 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.638: Wait for finger on sensor 426s (process:2245): libfprint-device-DEBUG: 00:54:35.638: Device reported finger status change: FP_FINGER_STATUS_NEEDED 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.638: Finger on sensor callback 426s (process:2245): libfprint-device-DEBUG: 00:54:35.638: Device reported finger status change: FP_FINGER_STATUS_PRESENT 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.638: [egismoc] ENROLL_STATES entering state 11 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.638: Execute command and get response 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.638: Get check bytes 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.638: [egismoc] CMD_STATES entering state 0 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.639: [egismoc] CMD_STATES entering state 1 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.639: Command receive callback 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.639: [egismoc] CMD_STATES completed successfully 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.639: Read capture callback 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.639: Response prefix valid: yes 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.639: Response suffix valid: yes 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.639: Partial capture successful. Please touch the sensor again (6/10) 426s (process:2245): libfprint-device-DEBUG: 00:54:35.639: Device reported enroll progress, reported 6 of 10 have been completed 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.639: [egismoc] ENROLL_STATES entering state 8 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.639: Execute command and get response 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.639: Get check bytes 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.639: [egismoc] CMD_STATES entering state 0 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.639: [egismoc] CMD_STATES entering state 1 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.640: Command receive callback 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.640: [egismoc] CMD_STATES completed successfully 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.640: Task SSM next state callback 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.640: [egismoc] ENROLL_STATES entering state 9 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.640: Execute command and get response 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.640: Get check bytes 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.640: [egismoc] CMD_STATES entering state 0 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.640: [egismoc] CMD_STATES entering state 1 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.641: Command receive callback 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.641: [egismoc] CMD_STATES completed successfully 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.641: Task SSM next state callback 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.641: [egismoc] ENROLL_STATES entering state 10 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.641: Wait for finger on sensor 426s (process:2245): libfprint-device-DEBUG: 00:54:35.641: Device reported finger status change: FP_FINGER_STATUS_NEEDED 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.641: Finger on sensor callback 426s (process:2245): libfprint-device-DEBUG: 00:54:35.641: Device reported finger status change: FP_FINGER_STATUS_PRESENT 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.641: [egismoc] ENROLL_STATES entering state 11 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.641: Execute command and get response 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.641: Get check bytes 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.641: [egismoc] CMD_STATES entering state 0 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.642: [egismoc] CMD_STATES entering state 1 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.642: Command receive callback 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.642: [egismoc] CMD_STATES completed successfully 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.642: Read capture callback 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.642: Response prefix valid: yes 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.642: Response suffix valid: yes 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.642: Partial capture successful. Please touch the sensor again (7/10) 426s (process:2245): libfprint-device-DEBUG: 00:54:35.642: Device reported enroll progress, reported 7 of 10 have been completed 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.642: [egismoc] ENROLL_STATES entering state 8 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.642: Execute command and get response 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.642: Get check bytes 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.642: [egismoc] CMD_STATES entering state 0 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.642: [egismoc] CMD_STATES entering state 1 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.643: Command receive callback 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.643: [egismoc] CMD_STATES completed successfully 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.643: Task SSM next state callback 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.643: [egismoc] ENROLL_STATES entering state 9 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.643: Execute command and get response 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.643: Get check bytes 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.643: [egismoc] CMD_STATES entering state 0 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.643: [egismoc] CMD_STATES entering state 1 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.644: Command receive callback 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.644: [egismoc] CMD_STATES completed successfully 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.644: Task SSM next state callback 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.644: [egismoc] ENROLL_STATES entering state 10 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.644: Wait for finger on sensor 426s (process:2245): libfprint-device-DEBUG: 00:54:35.644: Device reported finger status change: FP_FINGER_STATUS_NEEDED 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.644: Finger on sensor callback 426s (process:2245): libfprint-device-DEBUG: 00:54:35.644: Device reported finger status change: FP_FINGER_STATUS_PRESENT 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.644: [egismoc] ENROLL_STATES entering state 11 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.644: Execute command and get response 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.644: Get check bytes 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.644: [egismoc] CMD_STATES entering state 0 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.645: [egismoc] CMD_STATES entering state 1 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.645: Command receive callback 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.645: [egismoc] CMD_STATES completed successfully 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.645: Read capture callback 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.645: Response prefix valid: yes 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.645: Response suffix valid: yes 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.645: Partial capture successful. Please touch the sensor again (8/10) 426s (process:2245): libfprint-device-DEBUG: 00:54:35.645: Device reported enroll progress, reported 8 of 10 have been completed 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.645: [egismoc] ENROLL_STATES entering state 8 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.645: Execute command and get response 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.645: Get check bytes 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.645: [egismoc] CMD_STATES entering state 0 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.646: [egismoc] CMD_STATES entering state 1 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.646: Command receive callback 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.646: [egismoc] CMD_STATES completed successfully 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.646: Task SSM next state callback 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.646: [egismoc] ENROLL_STATES entering state 9 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.646: Execute command and get response 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.646: Get check bytes 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.646: [egismoc] CMD_STATES entering state 0 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.646: [egismoc] CMD_STATES entering state 1 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.647: Command receive callback 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.647: [egismoc] CMD_STATES completed successfully 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.647: Task SSM next state callback 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.647: [egismoc] ENROLL_STATES entering state 10 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.647: Wait for finger on sensor 426s (process:2245): libfprint-device-DEBUG: 00:54:35.647: Device reported finger status change: FP_FINGER_STATUS_NEEDED 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.647: Finger on sensor callback 426s (process:2245): libfprint-device-DEBUG: 00:54:35.647: Device reported finger status change: FP_FINGER_STATUS_PRESENT 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.647: [egismoc] ENROLL_STATES entering state 11 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.647: Execute command and get response 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.647: Get check bytes 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.647: [egismoc] CMD_STATES entering state 0 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.648: [egismoc] CMD_STATES entering state 1 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.648: Command receive callback 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.648: [egismoc] CMD_STATES completed successfully 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.648: Read capture callback 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.648: Response prefix valid: yes 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.648: Response suffix valid: yes 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.648: Partial capture successful. Please touch the sensor again (9/10) 426s (process:2245): libfprint-device-DEBUG: 00:54:35.648: Device reported enroll progress, reported 9 of 10 have been completed 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.648: [egismoc] ENROLL_STATES entering state 8 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.648: Execute command and get response 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.648: Get check bytes 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.648: [egismoc] CMD_STATES entering state 0 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.649: [egismoc] CMD_STATES entering state 1 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.649: Command receive callback 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.649: [egismoc] CMD_STATES completed successfully 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.649: Task SSM next state callback 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.649: [egismoc] ENROLL_STATES entering state 9 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.649: Execute command and get response 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.649: Get check bytes 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.649: [egismoc] CMD_STATES entering state 0 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.649: [egismoc] CMD_STATES entering state 1 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.650: Command receive callback 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.650: [egismoc] CMD_STATES completed successfully 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.650: Task SSM next state callback 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.650: [egismoc] ENROLL_STATES entering state 10 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.650: Wait for finger on sensor 426s (process:2245): libfprint-device-DEBUG: 00:54:35.650: Device reported finger status change: FP_FINGER_STATUS_NEEDED 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.650: Finger on sensor callback 426s (process:2245): libfprint-device-DEBUG: 00:54:35.650: Device reported finger status change: FP_FINGER_STATUS_PRESENT 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.650: [egismoc] ENROLL_STATES entering state 11 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.650: Execute command and get response 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.650: Get check bytes 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.650: [egismoc] CMD_STATES entering state 0 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.651: [egismoc] CMD_STATES entering state 1 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.651: Command receive callback 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.651: [egismoc] CMD_STATES completed successfully 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.651: Read capture callback 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.651: Response prefix valid: yes 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.651: Response suffix valid: yes 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.651: Partial capture successful. Please touch the sensor again (10/10) 426s (process:2245): libfprint-device-DEBUG: 00:54:35.651: Device reported enroll progress, reported 10 of 10 have been completed 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.651: [egismoc] ENROLL_STATES entering state 12 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.651: Execute command and get response 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.651: Get check bytes 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.651: [egismoc] CMD_STATES entering state 0 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.652: [egismoc] CMD_STATES entering state 1 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.652: Command receive callback 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.652: [egismoc] CMD_STATES completed successfully 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.652: Task SSM next state callback 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.652: [egismoc] ENROLL_STATES entering state 13 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.652: New fingerprint ID: FP1-00000000-2-00000000-nobody 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.652: Execute command and get response 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.652: Get check bytes 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.652: [egismoc] CMD_STATES entering state 0 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.653: [egismoc] CMD_STATES entering state 1 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.653: Command receive callback 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.653: [egismoc] CMD_STATES completed successfully 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.653: Task SSM next state callback 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.653: [egismoc] ENROLL_STATES entering state 14 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.653: Execute command and get response 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.653: Get check bytes 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.653: [egismoc] CMD_STATES entering state 0 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.653: [egismoc] CMD_STATES entering state 1 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.654: Command receive callback 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.654: [egismoc] CMD_STATES completed successfully 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.654: Task SSM next state callback 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.654: [egismoc] ENROLL_STATES entering state 15 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.654: Enrollment was successful! 426s (process:2245): libfprint-device-DEBUG: 00:54:35.654: Device reported enroll completion 426s (process:2245): libfprint-device-DEBUG: 00:54:35.654: Device reported finger status change: FP_FINGER_STATUS_NONE 426s (process:2245): libfprint-device-DEBUG: 00:54:35.654: Print for finger FP_FINGER_LEFT_INDEX enrolled 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.654: [egismoc] ENROLL_STATES completed successfully 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.654: Task SSM done 426s (process:2245): libfprint-device-DEBUG: 00:54:35.654: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 426s (process:2245): libfprint-device-DEBUG: 00:54:35.654: Updated temperature model after 0.04 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.654: List 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.654: [egismoc] LIST_STATES entering state 0 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.654: Execute command and get response 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.654: Get check bytes 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.654: [egismoc] CMD_STATES entering state 0 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.654: [egismoc] CMD_STATES entering state 1 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.655: Command receive callback 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.655: [egismoc] CMD_STATES completed successfully 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.655: List callback 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.655: Device fingerprint 1: FP1-00000000-2-00000000-nobody 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.655: Number of currently enrolled fingerprints on the device is 1 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.655: [egismoc] LIST_STATES entering state 1 426s (process:2245): libfprint-device-DEBUG: 00:54:35.655: Device reported listing completion 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.655: [egismoc] LIST_STATES completed successfully 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.655: Task SSM done 426s (process:2245): libfprint-device-DEBUG: 00:54:35.655: Completing action FPI_DEVICE_ACTION_LIST in idle! 426s (process:2245): libfprint-device-DEBUG: 00:54:35.655: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 426s (process:2245): libfprint-device-DEBUG: 00:54:35.655: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.655: Identify or Verify 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.655: [egismoc] IDENTIFY_STATES entering state 0 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.655: Execute command and get response 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.655: Get check bytes 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.655: [egismoc] CMD_STATES entering state 0 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.656: [egismoc] CMD_STATES entering state 1 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.656: Command receive callback 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.656: [egismoc] CMD_STATES completed successfully 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.656: List callback 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.656: Device fingerprint 1: FP1-00000000-2-00000000-nobody 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.656: Number of currently enrolled fingerprints on the device is 1 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.656: [egismoc] IDENTIFY_STATES entering state 1 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.656: [egismoc] IDENTIFY_STATES entering state 2 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.656: Execute command and get response 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.656: Get check bytes 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.656: [egismoc] CMD_STATES entering state 0 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.656: [egismoc] CMD_STATES entering state 1 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.657: Command receive callback 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.657: [egismoc] CMD_STATES completed successfully 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.657: Task SSM next state callback 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.657: [egismoc] IDENTIFY_STATES entering state 3 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.657: Execute command and get response 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.657: Get check bytes 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.657: [egismoc] CMD_STATES entering state 0 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.657: [egismoc] CMD_STATES entering state 1 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.658: Command receive callback 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.658: [egismoc] CMD_STATES completed successfully 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.658: Task SSM next state callback 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.658: [egismoc] IDENTIFY_STATES entering state 4 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.658: Wait for finger on sensor 426s (process:2245): libfprint-device-DEBUG: 00:54:35.658: Device reported finger status change: FP_FINGER_STATUS_NEEDED 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.658: Finger on sensor callback 426s (process:2245): libfprint-device-DEBUG: 00:54:35.658: Device reported finger status change: FP_FINGER_STATUS_PRESENT 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.658: [egismoc] IDENTIFY_STATES entering state 5 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.658: Execute command and get response 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.658: Get check bytes 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.658: [egismoc] CMD_STATES entering state 0 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.659: [egismoc] CMD_STATES entering state 1 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.659: Command receive callback 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.659: [egismoc] CMD_STATES completed successfully 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.659: Task SSM next state callback 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.659: [egismoc] IDENTIFY_STATES entering state 6 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.659: Get check command 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.659: Execute command and get response 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.659: Get check bytes 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.659: [egismoc] CMD_STATES entering state 0 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.659: [egismoc] CMD_STATES entering state 1 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.660: Command receive callback 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.660: [egismoc] CMD_STATES completed successfully 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.660: Identify check callback 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.660: Response suffix valid: yes 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.660: Identify successful for: FP1-00000000-2-00000000-nobody 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.660: Verifying against: FP1-00000000-2-00000000-nobody 426s (process:2245): libfprint-device-DEBUG: 00:54:35.660: Device reported verify result 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.660: [egismoc] IDENTIFY_STATES entering state 7 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.660: Execute command and get response 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.660: Get check bytes 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.660: [egismoc] CMD_STATES entering state 0 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.660: [egismoc] CMD_STATES entering state 1 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.661: Command receive callback 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.661: [egismoc] CMD_STATES completed successfully 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.661: Task SSM next state callback 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.661: [egismoc] IDENTIFY_STATES entering state 8 426s (process:2245): libfprint-device-DEBUG: 00:54:35.661: Device reported verify completion 426s (process:2245): libfprint-device-DEBUG: 00:54:35.661: Device reported finger status change: FP_FINGER_STATUS_NONE 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.661: [egismoc] IDENTIFY_STATES completed successfully 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.661: Task SSM done 426s (process:2245): libfprint-device-DEBUG: 00:54:35.661: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 426s (process:2245): libfprint-device-DEBUG: 00:54:35.661: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 426s (process:2245): libfprint-device-DEBUG: 00:54:35.661: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.661: Identify or Verify 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.661: [egismoc] IDENTIFY_STATES entering state 0 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.661: Execute command and get response 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.661: Get check bytes 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.661: [egismoc] CMD_STATES entering state 0 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.662: [egismoc] CMD_STATES entering state 1 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.662: Command receive callback 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.662: [egismoc] CMD_STATES completed successfully 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.662: List callback 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.662: Device fingerprint 1: FP1-00000000-2-00000000-nobody 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.662: Number of currently enrolled fingerprints on the device is 1 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.662: [egismoc] IDENTIFY_STATES entering state 1 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.662: [egismoc] IDENTIFY_STATES entering state 2 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.662: Execute command and get response 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.662: Get check bytes 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.662: [egismoc] CMD_STATES entering state 0 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.663: [egismoc] CMD_STATES entering state 1 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.663: Command receive callback 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.663: [egismoc] CMD_STATES completed successfully 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.663: Task SSM next state callback 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.663: [egismoc] IDENTIFY_STATES entering state 3 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.663: Execute command and get response 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.663: Get check bytes 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.663: [egismoc] CMD_STATES entering state 0 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.664: [egismoc] CMD_STATES entering state 1 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.664: Command receive callback 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.664: [egismoc] CMD_STATES completed successfully 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.664: Task SSM next state callback 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.664: [egismoc] IDENTIFY_STATES entering state 4 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.664: Wait for finger on sensor 426s (process:2245): libfprint-device-DEBUG: 00:54:35.664: Device reported finger status change: FP_FINGER_STATUS_NEEDED 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.664: Finger on sensor callback 426s (process:2245): libfprint-device-DEBUG: 00:54:35.664: Device reported finger status change: FP_FINGER_STATUS_PRESENT 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.664: [egismoc] IDENTIFY_STATES entering state 5 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.664: Execute command and get response 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.664: Get check bytes 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.665: [egismoc] CMD_STATES entering state 0 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.665: [egismoc] CMD_STATES entering state 1 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.665: Command receive callback 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.665: [egismoc] CMD_STATES completed successfully 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.665: Task SSM next state callback 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.665: [egismoc] IDENTIFY_STATES entering state 6 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.665: Get check command 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.665: Execute command and get response 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.665: Get check bytes 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.665: [egismoc] CMD_STATES entering state 0 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.666: [egismoc] CMD_STATES entering state 1 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.666: Command receive callback 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.666: [egismoc] CMD_STATES completed successfully 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.666: Identify check callback 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.666: Response suffix valid: yes 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.666: Identify successful for: FP1-00000000-2-00000000-nobody 426s (process:2245): libfprint-device-DEBUG: 00:54:35.666: Device reported identify result 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.666: [egismoc] IDENTIFY_STATES entering state 7 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.666: Execute command and get response 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.666: Get check bytes 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.666: [egismoc] CMD_STATES entering state 0 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.667: [egismoc] CMD_STATES entering state 1 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.667: Command receive callback 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.667: [egismoc] CMD_STATES completed successfully 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.667: Task SSM next state callback 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.667: [egismoc] IDENTIFY_STATES entering state 8 426s (process:2245): libfprint-device-DEBUG: 00:54:35.667: Device reported identify completion 426s (process:2245): libfprint-device-DEBUG: 00:54:35.667: Device reported finger status change: FP_FINGER_STATUS_NONE 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.667: [egismoc] IDENTIFY_STATES completed successfully 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.667: Task SSM done 426s (process:2245): libfprint-device-DEBUG: 00:54:35.667: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 426s (process:2245): libfprint-device-DEBUG: 00:54:35.667: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 426s (process:2245): libfprint-device-DEBUG: 00:54:35.668: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.668: Enroll 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.668: [egismoc] ENROLL_STATES entering state 0 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.668: Execute command and get response 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.668: Get check bytes 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.668: [egismoc] CMD_STATES entering state 0 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.668: [egismoc] CMD_STATES entering state 1 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.669: Command receive callback 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.669: [egismoc] CMD_STATES completed successfully 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.669: List callback 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.669: Device fingerprint 1: FP1-00000000-2-00000000-nobody 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.669: Number of currently enrolled fingerprints on the device is 1 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.669: [egismoc] ENROLL_STATES entering state 1 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.669: [egismoc] ENROLL_STATES entering state 2 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.669: Execute command and get response 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.669: Get check bytes 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.669: [egismoc] CMD_STATES entering state 0 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.669: [egismoc] CMD_STATES entering state 1 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.669: Command receive callback 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.669: [egismoc] CMD_STATES completed successfully 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.669: Task SSM next state callback 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.669: [egismoc] ENROLL_STATES entering state 3 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.669: Execute command and get response 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.669: Get check bytes 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.669: [egismoc] CMD_STATES entering state 0 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.670: [egismoc] CMD_STATES entering state 1 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.670: Command receive callback 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.670: [egismoc] CMD_STATES completed successfully 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.670: Task SSM next state callback 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.670: [egismoc] ENROLL_STATES entering state 4 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.670: Wait for finger on sensor 426s (process:2245): libfprint-device-DEBUG: 00:54:35.670: Device reported finger status change: FP_FINGER_STATUS_NEEDED 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.671: Finger on sensor callback 426s (process:2245): libfprint-device-DEBUG: 00:54:35.671: Device reported finger status change: FP_FINGER_STATUS_PRESENT 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.671: [egismoc] ENROLL_STATES entering state 5 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.671: Execute command and get response 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.671: Get check bytes 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.671: [egismoc] CMD_STATES entering state 0 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.671: [egismoc] CMD_STATES entering state 1 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.672: Command receive callback 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.672: [egismoc] CMD_STATES completed successfully 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.672: Task SSM next state callback 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.672: [egismoc] ENROLL_STATES entering state 6 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.672: Get check command 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.672: Execute command and get response 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.672: Get check bytes 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.672: [egismoc] CMD_STATES entering state 0 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.672: [egismoc] CMD_STATES entering state 1 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.672: Command receive callback 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.672: [egismoc] CMD_STATES completed successfully 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.672: Enroll check callback 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.672: Response suffix valid: NO 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.672: [egismoc] SSM ENROLL_STATES failed in state 6 with error: This finger has already enrolled, please try a different finger 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.672: [egismoc] ENROLL_STATES completed with error: This finger has already enrolled, please try a different finger 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.672: Task SSM done 426s (process:2245): libfprint-device-DEBUG: 00:54:35.672: Device reported generic error (This finger has already enrolled, please try a different finger) during action; action was: FPI_DEVICE_ACTION_ENROLL 426s (process:2245): libfprint-device-DEBUG: 00:54:35.672: Device reported enroll completion 426s (process:2245): libfprint-device-DEBUG: 00:54:35.672: Device reported finger status change: FP_FINGER_STATUS_NONE 426s (process:2245): libfprint-device-DEBUG: 00:54:35.672: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 426s (process:2245): libfprint-device-DEBUG: 00:54:35.672: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.673: List 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.673: [egismoc] LIST_STATES entering state 0 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.673: Execute command and get response 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.673: Get check bytes 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.673: [egismoc] CMD_STATES entering state 0 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.673: [egismoc] CMD_STATES entering state 1 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.674: Command receive callback 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.674: [egismoc] CMD_STATES completed successfully 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.674: List callback 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.674: Device fingerprint 1: FP1-00000000-2-00000000-nobody 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.674: Number of currently enrolled fingerprints on the device is 1 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.674: [egismoc] LIST_STATES entering state 1 426s (process:2245): libfprint-device-DEBUG: 00:54:35.674: Device reported listing completion 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.674: [egismoc] LIST_STATES completed successfully 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.674: Task SSM done 426s (process:2245): libfprint-device-DEBUG: 00:54:35.674: Completing action FPI_DEVICE_ACTION_LIST in idle! 426s (process:2245): libfprint-device-DEBUG: 00:54:35.674: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 426s (process:2245): libfprint-device-DEBUG: 00:54:35.674: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.674: Enroll 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.674: [egismoc] ENROLL_STATES entering state 0 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.674: Execute command and get response 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.674: Get check bytes 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.674: [egismoc] CMD_STATES entering state 0 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.674: [egismoc] CMD_STATES entering state 1 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.675: Command receive callback 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.675: [egismoc] CMD_STATES completed successfully 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.675: List callback 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.675: Device fingerprint 1: FP1-00000000-2-00000000-nobody 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.675: Number of currently enrolled fingerprints on the device is 1 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.675: [egismoc] ENROLL_STATES entering state 1 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.675: [egismoc] ENROLL_STATES entering state 2 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.675: Execute command and get response 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.675: Get check bytes 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.675: [egismoc] CMD_STATES entering state 0 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.675: [egismoc] CMD_STATES entering state 1 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.676: Command receive callback 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.676: [egismoc] CMD_STATES completed successfully 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.676: Task SSM next state callback 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.676: [egismoc] ENROLL_STATES entering state 3 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.676: Execute command and get response 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.676: Get check bytes 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.676: [egismoc] CMD_STATES entering state 0 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.676: [egismoc] CMD_STATES entering state 1 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.677: Command receive callback 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.677: [egismoc] CMD_STATES completed successfully 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.677: Task SSM next state callback 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.677: [egismoc] ENROLL_STATES entering state 4 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.677: Wait for finger on sensor 426s (process:2245): libfprint-device-DEBUG: 00:54:35.677: Device reported finger status change: FP_FINGER_STATUS_NEEDED 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.677: Finger on sensor callback 426s (process:2245): libfprint-device-DEBUG: 00:54:35.677: Device reported finger status change: FP_FINGER_STATUS_PRESENT 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.677: [egismoc] ENROLL_STATES entering state 5 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.677: Execute command and get response 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.677: Get check bytes 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.677: [egismoc] CMD_STATES entering state 0 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.678: [egismoc] CMD_STATES entering state 1 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.678: Command receive callback 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.678: [egismoc] CMD_STATES completed successfully 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.678: Task SSM next state callback 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.678: [egismoc] ENROLL_STATES entering state 6 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.678: Get check command 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.678: Execute command and get response 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.678: Get check bytes 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.678: [egismoc] CMD_STATES entering state 0 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.679: [egismoc] CMD_STATES entering state 1 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.679: Command receive callback 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.679: [egismoc] CMD_STATES completed successfully 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.679: Enroll check callback 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.679: Response suffix valid: yes 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.679: [egismoc] ENROLL_STATES entering state 7 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.679: Execute command and get response 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.679: Get check bytes 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.679: [egismoc] CMD_STATES entering state 0 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.679: [egismoc] CMD_STATES entering state 1 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.680: Command receive callback 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.680: [egismoc] CMD_STATES completed successfully 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.680: Task SSM next state callback 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.680: [egismoc] ENROLL_STATES entering state 8 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.680: Execute command and get response 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.680: Get check bytes 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.680: [egismoc] CMD_STATES entering state 0 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.680: [egismoc] CMD_STATES entering state 1 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.681: Command receive callback 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.681: [egismoc] CMD_STATES completed successfully 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.681: Task SSM next state callback 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.681: [egismoc] ENROLL_STATES entering state 9 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.681: Execute command and get response 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.681: Get check bytes 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.681: [egismoc] CMD_STATES entering state 0 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.681: [egismoc] CMD_STATES entering state 1 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.682: Command receive callback 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.682: [egismoc] CMD_STATES completed successfully 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.682: Task SSM next state callback 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.682: [egismoc] ENROLL_STATES entering state 10 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.682: Wait for finger on sensor 426s (process:2245): libfprint-device-DEBUG: 00:54:35.682: Device reported finger status change: FP_FINGER_STATUS_NEEDED 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.682: Finger on sensor callback 426s (process:2245): libfprint-device-DEBUG: 00:54:35.682: Device reported finger status change: FP_FINGER_STATUS_PRESENT 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.682: [egismoc] ENROLL_STATES entering state 11 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.682: Execute command and get response 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.682: Get check bytes 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.682: [egismoc] CMD_STATES entering state 0 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.683: [egismoc] CMD_STATES entering state 1 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.683: Command receive callback 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.683: [egismoc] CMD_STATES completed successfully 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.683: Read capture callback 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.683: Response prefix valid: yes 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.683: Response suffix valid: yes 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.683: Partial capture successful. Please touch the sensor again (1/10) 426s (process:2245): libfprint-device-DEBUG: 00:54:35.683: Device reported enroll progress, reported 1 of 10 have been completed 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.683: [egismoc] ENROLL_STATES entering state 8 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.683: Execute command and get response 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.683: Get check bytes 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.683: [egismoc] CMD_STATES entering state 0 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.684: [egismoc] CMD_STATES entering state 1 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.684: Command receive callback 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.684: [egismoc] CMD_STATES completed successfully 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.684: Task SSM next state callback 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.684: [egismoc] ENROLL_STATES entering state 9 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.684: Execute command and get response 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.684: Get check bytes 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.684: [egismoc] CMD_STATES entering state 0 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.684: [egismoc] CMD_STATES entering state 1 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.685: Command receive callback 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.685: [egismoc] CMD_STATES completed successfully 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.685: Task SSM next state callback 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.685: [egismoc] ENROLL_STATES entering state 10 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.685: Wait for finger on sensor 426s (process:2245): libfprint-device-DEBUG: 00:54:35.685: Device reported finger status change: FP_FINGER_STATUS_NEEDED 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.685: Finger on sensor callback 426s (process:2245): libfprint-device-DEBUG: 00:54:35.685: Device reported finger status change: FP_FINGER_STATUS_PRESENT 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.685: [egismoc] ENROLL_STATES entering state 11 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.685: Execute command and get response 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.685: Get check bytes 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.685: [egismoc] CMD_STATES entering state 0 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.686: [egismoc] CMD_STATES entering state 1 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.686: Command receive callback 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.686: [egismoc] CMD_STATES completed successfully 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.686: Read capture callback 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.686: Response prefix valid: yes 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.686: Response suffix valid: yes 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.686: Partial capture successful. Please touch the sensor again (2/10) 426s (process:2245): libfprint-device-DEBUG: 00:54:35.686: Device reported enroll progress, reported 2 of 10 have been completed 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.686: [egismoc] ENROLL_STATES entering state 8 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.686: Execute command and get response 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.686: Get check bytes 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.686: [egismoc] CMD_STATES entering state 0 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.687: [egismoc] CMD_STATES entering state 1 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.687: Command receive callback 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.687: [egismoc] CMD_STATES completed successfully 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.687: Task SSM next state callback 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.687: [egismoc] ENROLL_STATES entering state 9 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.687: Execute command and get response 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.687: Get check bytes 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.687: [egismoc] CMD_STATES entering state 0 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.688: [egismoc] CMD_STATES entering state 1 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.688: Command receive callback 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.688: [egismoc] CMD_STATES completed successfully 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.688: Task SSM next state callback 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.688: [egismoc] ENROLL_STATES entering state 10 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.688: Wait for finger on sensor 426s (process:2245): libfprint-device-DEBUG: 00:54:35.688: Device reported finger status change: FP_FINGER_STATUS_NEEDED 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.688: Finger on sensor callback 426s (process:2245): libfprint-device-DEBUG: 00:54:35.689: Device reported finger status change: FP_FINGER_STATUS_PRESENT 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.689: [egismoc] ENROLL_STATES entering state 11 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.689: Execute command and get response 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.689: Get check bytes 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.689: [egismoc] CMD_STATES entering state 0 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.689: [egismoc] CMD_STATES entering state 1 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.689: Command receive callback 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.689: [egismoc] CMD_STATES completed successfully 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.689: Read capture callback 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.689: Response prefix valid: yes 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.689: Response suffix valid: NO 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.689: Response prefix valid: yes 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.689: Response suffix valid: yes 426s (process:2245): libfprint-device-DEBUG: 00:54:35.689: Device reported enroll progress, reported 2 of 10 have been completed 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.689: [egismoc] ENROLL_STATES entering state 8 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.690: Execute command and get response 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.690: Get check bytes 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.690: [egismoc] CMD_STATES entering state 0 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.690: [egismoc] CMD_STATES entering state 1 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.690: Command receive callback 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.690: [egismoc] CMD_STATES completed successfully 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.690: Task SSM next state callback 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.690: [egismoc] ENROLL_STATES entering state 9 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.690: Execute command and get response 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.690: Get check bytes 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.690: [egismoc] CMD_STATES entering state 0 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.691: [egismoc] CMD_STATES entering state 1 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.691: Command receive callback 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.691: [egismoc] CMD_STATES completed successfully 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.691: Task SSM next state callback 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.691: [egismoc] ENROLL_STATES entering state 10 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.691: Wait for finger on sensor 426s (process:2245): libfprint-device-DEBUG: 00:54:35.691: Device reported finger status change: FP_FINGER_STATUS_NEEDED 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.692: Finger on sensor callback 426s (process:2245): libfprint-device-DEBUG: 00:54:35.692: Device reported finger status change: FP_FINGER_STATUS_PRESENT 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.692: [egismoc] ENROLL_STATES entering state 11 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.692: Execute command and get response 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.692: Get check bytes 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.692: [egismoc] CMD_STATES entering state 0 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.692: [egismoc] CMD_STATES entering state 1 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.693: Command receive callback 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.693: [egismoc] CMD_STATES completed successfully 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.693: Read capture callback 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.693: Response prefix valid: yes 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.693: Response suffix valid: NO 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.693: Response prefix valid: yes 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.693: Response suffix valid: yes 426s (process:2245): libfprint-device-DEBUG: 00:54:35.693: Device reported enroll progress, reported 2 of 10 have been completed 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.693: [egismoc] ENROLL_STATES entering state 8 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.693: Execute command and get response 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.693: Get check bytes 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.693: [egismoc] CMD_STATES entering state 0 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.693: [egismoc] CMD_STATES entering state 1 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.694: Command receive callback 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.694: [egismoc] CMD_STATES completed successfully 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.694: Task SSM next state callback 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.694: [egismoc] ENROLL_STATES entering state 9 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.694: Execute command and get response 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.694: Get check bytes 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.694: [egismoc] CMD_STATES entering state 0 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.694: [egismoc] CMD_STATES entering state 1 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.695: Command receive callback 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.695: [egismoc] CMD_STATES completed successfully 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.695: Task SSM next state callback 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.695: [egismoc] ENROLL_STATES entering state 10 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.695: Wait for finger on sensor 426s (process:2245): libfprint-device-DEBUG: 00:54:35.695: Device reported finger status change: FP_FINGER_STATUS_NEEDED 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.695: Finger on sensor callback 426s (process:2245): libfprint-device-DEBUG: 00:54:35.695: Device reported finger status change: FP_FINGER_STATUS_PRESENT 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.695: [egismoc] ENROLL_STATES entering state 11 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.695: Execute command and get response 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.695: Get check bytes 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.695: [egismoc] CMD_STATES entering state 0 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.696: [egismoc] CMD_STATES entering state 1 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.696: Command receive callback 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.696: [egismoc] CMD_STATES completed successfully 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.696: Read capture callback 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.696: Response prefix valid: yes 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.696: Response suffix valid: yes 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.696: Partial capture successful. Please touch the sensor again (3/10) 426s (process:2245): libfprint-device-DEBUG: 00:54:35.696: Device reported enroll progress, reported 3 of 10 have been completed 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.696: [egismoc] ENROLL_STATES entering state 8 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.696: Execute command and get response 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.696: Get check bytes 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.696: [egismoc] CMD_STATES entering state 0 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.696: [egismoc] CMD_STATES entering state 1 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.697: Command receive callback 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.697: [egismoc] CMD_STATES completed successfully 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.697: Task SSM next state callback 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.697: [egismoc] ENROLL_STATES entering state 9 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.697: Execute command and get response 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.697: Get check bytes 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.697: [egismoc] CMD_STATES entering state 0 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.697: [egismoc] CMD_STATES entering state 1 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.698: Command receive callback 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.698: [egismoc] CMD_STATES completed successfully 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.698: Task SSM next state callback 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.698: [egismoc] ENROLL_STATES entering state 10 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.698: Wait for finger on sensor 426s (process:2245): libfprint-device-DEBUG: 00:54:35.698: Device reported finger status change: FP_FINGER_STATUS_NEEDED 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.698: Finger on sensor callback 426s (process:2245): libfprint-device-DEBUG: 00:54:35.698: Device reported finger status change: FP_FINGER_STATUS_PRESENT 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.698: [egismoc] ENROLL_STATES entering state 11 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.698: Execute command and get response 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.698: Get check bytes 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.698: [egismoc] CMD_STATES entering state 0 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.699: [egismoc] CMD_STATES entering state 1 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.699: Command receive callback 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.699: [egismoc] CMD_STATES completed successfully 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.699: Read capture callback 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.699: Response prefix valid: yes 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.699: Response suffix valid: NO 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.699: Response prefix valid: yes 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.699: Response suffix valid: yes 426s (process:2245): libfprint-device-DEBUG: 00:54:35.699: Device reported enroll progress, reported 3 of 10 have been completed 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.699: [egismoc] ENROLL_STATES entering state 8 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.699: Execute command and get response 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.699: Get check bytes 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.699: [egismoc] CMD_STATES entering state 0 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.700: [egismoc] CMD_STATES entering state 1 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.700: Command receive callback 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.700: [egismoc] CMD_STATES completed successfully 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.700: Task SSM next state callback 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.700: [egismoc] ENROLL_STATES entering state 9 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.700: Execute command and get response 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.700: Get check bytes 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.700: [egismoc] CMD_STATES entering state 0 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.701: [egismoc] CMD_STATES entering state 1 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.701: Command receive callback 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.701: [egismoc] CMD_STATES completed successfully 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.701: Task SSM next state callback 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.701: [egismoc] ENROLL_STATES entering state 10 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.701: Wait for finger on sensor 426s (process:2245): libfprint-device-DEBUG: 00:54:35.701: Device reported finger status change: FP_FINGER_STATUS_NEEDED 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.702: Finger on sensor callback 426s (process:2245): libfprint-device-DEBUG: 00:54:35.702: Device reported finger status change: FP_FINGER_STATUS_PRESENT 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.702: [egismoc] ENROLL_STATES entering state 11 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.702: Execute command and get response 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.702: Get check bytes 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.702: [egismoc] CMD_STATES entering state 0 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.702: [egismoc] CMD_STATES entering state 1 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.702: Command receive callback 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.702: [egismoc] CMD_STATES completed successfully 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.703: Read capture callback 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.703: Response prefix valid: yes 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.703: Response suffix valid: yes 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.703: Partial capture successful. Please touch the sensor again (4/10) 426s (process:2245): libfprint-device-DEBUG: 00:54:35.703: Device reported enroll progress, reported 4 of 10 have been completed 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.703: [egismoc] ENROLL_STATES entering state 8 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.703: Execute command and get response 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.703: Get check bytes 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.703: [egismoc] CMD_STATES entering state 0 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.703: [egismoc] CMD_STATES entering state 1 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.703: Command receive callback 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.703: [egismoc] CMD_STATES completed successfully 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.703: Task SSM next state callback 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.703: [egismoc] ENROLL_STATES entering state 9 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.703: Execute command and get response 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.703: Get check bytes 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.703: [egismoc] CMD_STATES entering state 0 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.704: [egismoc] CMD_STATES entering state 1 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.704: Command receive callback 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.704: [egismoc] CMD_STATES completed successfully 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.704: Task SSM next state callback 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.704: [egismoc] ENROLL_STATES entering state 10 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.704: Wait for finger on sensor 426s (process:2245): libfprint-device-DEBUG: 00:54:35.704: Device reported finger status change: FP_FINGER_STATUS_NEEDED 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.705: Finger on sensor callback 426s (process:2245): libfprint-device-DEBUG: 00:54:35.705: Device reported finger status change: FP_FINGER_STATUS_PRESENT 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.705: [egismoc] ENROLL_STATES entering state 11 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.705: Execute command and get response 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.705: Get check bytes 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.705: [egismoc] CMD_STATES entering state 0 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.705: [egismoc] CMD_STATES entering state 1 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.706: Command receive callback 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.706: [egismoc] CMD_STATES completed successfully 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.706: Read capture callback 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.706: Response prefix valid: yes 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.706: Response suffix valid: yes 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.706: Partial capture successful. Please touch the sensor again (5/10) 426s (process:2245): libfprint-device-DEBUG: 00:54:35.706: Device reported enroll progress, reported 5 of 10 have been completed 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.706: [egismoc] ENROLL_STATES entering state 8 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.706: Execute command and get response 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.706: Get check bytes 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.706: [egismoc] CMD_STATES entering state 0 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.706: [egismoc] CMD_STATES entering state 1 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.707: Command receive callback 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.707: [egismoc] CMD_STATES completed successfully 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.707: Task SSM next state callback 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.707: [egismoc] ENROLL_STATES entering state 9 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.707: Execute command and get response 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.707: Get check bytes 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.707: [egismoc] CMD_STATES entering state 0 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.707: [egismoc] CMD_STATES entering state 1 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.707: Command receive callback 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.707: [egismoc] CMD_STATES completed successfully 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.707: Task SSM next state callback 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.707: [egismoc] ENROLL_STATES entering state 10 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.707: Wait for finger on sensor 426s (process:2245): libfprint-device-DEBUG: 00:54:35.707: Device reported finger status change: FP_FINGER_STATUS_NEEDED 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.708: Finger on sensor callback 426s (process:2245): libfprint-device-DEBUG: 00:54:35.708: Device reported finger status change: FP_FINGER_STATUS_PRESENT 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.708: [egismoc] ENROLL_STATES entering state 11 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.708: Execute command and get response 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.708: Get check bytes 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.708: [egismoc] CMD_STATES entering state 0 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.708: [egismoc] CMD_STATES entering state 1 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.709: Command receive callback 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.709: [egismoc] CMD_STATES completed successfully 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.709: Read capture callback 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.709: Response prefix valid: yes 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.709: Response suffix valid: yes 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.709: Partial capture successful. Please touch the sensor again (6/10) 426s (process:2245): libfprint-device-DEBUG: 00:54:35.709: Device reported enroll progress, reported 6 of 10 have been completed 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.709: [egismoc] ENROLL_STATES entering state 8 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.709: Execute command and get response 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.709: Get check bytes 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.709: [egismoc] CMD_STATES entering state 0 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.709: [egismoc] CMD_STATES entering state 1 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.710: Command receive callback 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.710: [egismoc] CMD_STATES completed successfully 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.710: Task SSM next state callback 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.710: [egismoc] ENROLL_STATES entering state 9 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.710: Execute command and get response 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.710: Get check bytes 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.710: [egismoc] CMD_STATES entering state 0 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.710: [egismoc] CMD_STATES entering state 1 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.711: Command receive callback 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.711: [egismoc] CMD_STATES completed successfully 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.711: Task SSM next state callback 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.711: [egismoc] ENROLL_STATES entering state 10 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.711: Wait for finger on sensor 426s (process:2245): libfprint-device-DEBUG: 00:54:35.711: Device reported finger status change: FP_FINGER_STATUS_NEEDED 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.711: Finger on sensor callback 426s (process:2245): libfprint-device-DEBUG: 00:54:35.711: Device reported finger status change: FP_FINGER_STATUS_PRESENT 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.711: [egismoc] ENROLL_STATES entering state 11 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.711: Execute command and get response 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.711: Get check bytes 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.711: [egismoc] CMD_STATES entering state 0 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.711: [egismoc] CMD_STATES entering state 1 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.712: Command receive callback 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.712: [egismoc] CMD_STATES completed successfully 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.712: Read capture callback 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.712: Response prefix valid: yes 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.712: Response suffix valid: yes 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.712: Partial capture successful. Please touch the sensor again (7/10) 426s (process:2245): libfprint-device-DEBUG: 00:54:35.712: Device reported enroll progress, reported 7 of 10 have been completed 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.712: [egismoc] ENROLL_STATES entering state 8 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.712: Execute command and get response 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.712: Get check bytes 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.712: [egismoc] CMD_STATES entering state 0 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.712: [egismoc] CMD_STATES entering state 1 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.713: Command receive callback 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.713: [egismoc] CMD_STATES completed successfully 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.713: Task SSM next state callback 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.713: [egismoc] ENROLL_STATES entering state 9 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.713: Execute command and get response 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.713: Get check bytes 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.713: [egismoc] CMD_STATES entering state 0 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.713: [egismoc] CMD_STATES entering state 1 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.714: Command receive callback 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.714: [egismoc] CMD_STATES completed successfully 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.714: Task SSM next state callback 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.714: [egismoc] ENROLL_STATES entering state 10 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.714: Wait for finger on sensor 426s (process:2245): libfprint-device-DEBUG: 00:54:35.714: Device reported finger status change: FP_FINGER_STATUS_NEEDED 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.714: Finger on sensor callback 426s (process:2245): libfprint-device-DEBUG: 00:54:35.714: Device reported finger status change: FP_FINGER_STATUS_PRESENT 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.714: [egismoc] ENROLL_STATES entering state 11 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.714: Execute command and get response 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.714: Get check bytes 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.714: [egismoc] CMD_STATES entering state 0 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.715: [egismoc] CMD_STATES entering state 1 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.715: Command receive callback 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.715: [egismoc] CMD_STATES completed successfully 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.715: Read capture callback 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.715: Response prefix valid: yes 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.715: Response suffix valid: yes 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.715: Partial capture successful. Please touch the sensor again (8/10) 426s (process:2245): libfprint-device-DEBUG: 00:54:35.715: Device reported enroll progress, reported 8 of 10 have been completed 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.715: [egismoc] ENROLL_STATES entering state 8 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.715: Execute command and get response 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.715: Get check bytes 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.715: [egismoc] CMD_STATES entering state 0 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.715: [egismoc] CMD_STATES entering state 1 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.716: Command receive callback 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.716: [egismoc] CMD_STATES completed successfully 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.716: Task SSM next state callback 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.716: [egismoc] ENROLL_STATES entering state 9 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.716: Execute command and get response 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.716: Get check bytes 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.716: [egismoc] CMD_STATES entering state 0 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.716: [egismoc] CMD_STATES entering state 1 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.717: Command receive callback 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.717: [egismoc] CMD_STATES completed successfully 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.717: Task SSM next state callback 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.717: [egismoc] ENROLL_STATES entering state 10 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.717: Wait for finger on sensor 426s (process:2245): libfprint-device-DEBUG: 00:54:35.717: Device reported finger status change: FP_FINGER_STATUS_NEEDED 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.717: Finger on sensor callback 426s (process:2245): libfprint-device-DEBUG: 00:54:35.717: Device reported finger status change: FP_FINGER_STATUS_PRESENT 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.717: [egismoc] ENROLL_STATES entering state 11 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.717: Execute command and get response 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.717: Get check bytes 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.717: [egismoc] CMD_STATES entering state 0 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.718: [egismoc] CMD_STATES entering state 1 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.718: Command receive callback 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.718: [egismoc] CMD_STATES completed successfully 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.718: Read capture callback 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.718: Response prefix valid: yes 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.718: Response suffix valid: yes 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.718: Partial capture successful. Please touch the sensor again (9/10) 426s (process:2245): libfprint-device-DEBUG: 00:54:35.718: Device reported enroll progress, reported 9 of 10 have been completed 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.718: [egismoc] ENROLL_STATES entering state 8 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.718: Execute command and get response 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.718: Get check bytes 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.718: [egismoc] CMD_STATES entering state 0 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.719: [egismoc] CMD_STATES entering state 1 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.719: Command receive callback 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.719: [egismoc] CMD_STATES completed successfully 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.719: Task SSM next state callback 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.719: [egismoc] ENROLL_STATES entering state 9 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.719: Execute command and get response 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.719: Get check bytes 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.719: [egismoc] CMD_STATES entering state 0 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.719: [egismoc] CMD_STATES entering state 1 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.720: Command receive callback 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.720: [egismoc] CMD_STATES completed successfully 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.720: Task SSM next state callback 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.720: [egismoc] ENROLL_STATES entering state 10 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.720: Wait for finger on sensor 426s (process:2245): libfprint-device-DEBUG: 00:54:35.720: Device reported finger status change: FP_FINGER_STATUS_NEEDED 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.720: Finger on sensor callback 426s (process:2245): libfprint-device-DEBUG: 00:54:35.720: Device reported finger status change: FP_FINGER_STATUS_PRESENT 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.720: [egismoc] ENROLL_STATES entering state 11 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.720: Execute command and get response 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.720: Get check bytes 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.720: [egismoc] CMD_STATES entering state 0 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.721: [egismoc] CMD_STATES entering state 1 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.722: Command receive callback 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.722: [egismoc] CMD_STATES completed successfully 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.722: Read capture callback 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.722: Response prefix valid: yes 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.722: Response suffix valid: yes 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.722: Partial capture successful. Please touch the sensor again (10/10) 426s (process:2245): libfprint-device-DEBUG: 00:54:35.722: Device reported enroll progress, reported 10 of 10 have been completed 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.722: [egismoc] ENROLL_STATES entering state 12 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.722: Execute command and get response 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.722: Get check bytes 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.722: [egismoc] CMD_STATES entering state 0 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.722: [egismoc] CMD_STATES entering state 1 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.722: Command receive callback 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.722: [egismoc] CMD_STATES completed successfully 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.722: Task SSM next state callback 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.722: [egismoc] ENROLL_STATES entering state 13 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.722: New fingerprint ID: FP1-00000000-7-00000000-nobody 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.722: Execute command and get response 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.722: Get check bytes 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.722: [egismoc] CMD_STATES entering state 0 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.723: [egismoc] CMD_STATES entering state 1 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.723: Command receive callback 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.723: [egismoc] CMD_STATES completed successfully 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.723: Task SSM next state callback 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.723: [egismoc] ENROLL_STATES entering state 14 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.723: Execute command and get response 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.723: Get check bytes 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.723: [egismoc] CMD_STATES entering state 0 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.724: [egismoc] CMD_STATES entering state 1 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.724: Command receive callback 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.724: [egismoc] CMD_STATES completed successfully 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.724: Task SSM next state callback 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.724: [egismoc] ENROLL_STATES entering state 15 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.724: Enrollment was successful! 426s (process:2245): libfprint-device-DEBUG: 00:54:35.724: Device reported enroll completion 426s (process:2245): libfprint-device-DEBUG: 00:54:35.724: Device reported finger status change: FP_FINGER_STATUS_NONE 426s (process:2245): libfprint-device-DEBUG: 00:54:35.724: Print for finger FP_FINGER_RIGHT_INDEX enrolled 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.724: [egismoc] ENROLL_STATES completed successfully 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.724: Task SSM done 426s (process:2245): libfprint-device-DEBUG: 00:54:35.724: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 426s (process:2245): libfprint-device-DEBUG: 00:54:35.724: Updated temperature model after 0.05 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.724: List 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.724: [egismoc] LIST_STATES entering state 0 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.724: Execute command and get response 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.724: Get check bytes 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.724: [egismoc] CMD_STATES entering state 0 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.725: [egismoc] CMD_STATES entering state 1 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.726: Command receive callback 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.726: [egismoc] CMD_STATES completed successfully 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.726: List callback 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.726: Device fingerprint 1: FP1-00000000-2-00000000-nobody 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.726: Device fingerprint 2: FP1-00000000-7-00000000-nobody 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.726: Number of currently enrolled fingerprints on the device is 2 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.726: [egismoc] LIST_STATES entering state 1 426s (process:2245): libfprint-device-DEBUG: 00:54:35.727: Device reported listing completion 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.727: [egismoc] LIST_STATES completed successfully 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.727: Task SSM done 426s (process:2245): libfprint-device-DEBUG: 00:54:35.727: Completing action FPI_DEVICE_ACTION_LIST in idle! 426s (process:2245): libfprint-device-DEBUG: 00:54:35.727: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.727: Delete 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.727: [egismoc] DELETE_STATES entering state 0 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.727: Execute command and get response 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.727: Get check bytes 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.727: [egismoc] CMD_STATES entering state 0 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.727: [egismoc] CMD_STATES entering state 1 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.728: Command receive callback 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.728: [egismoc] CMD_STATES completed successfully 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.728: List callback 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.728: Device fingerprint 1: FP1-00000000-2-00000000-nobody 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.728: Device fingerprint 2: FP1-00000000-7-00000000-nobody 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.728: Number of currently enrolled fingerprints on the device is 2 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.728: [egismoc] DELETE_STATES entering state 1 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.728: Get delete command 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.728: Delete fingerprint FP1-00000000-2-00000000-nobody (FP1-00000000-2-00000000-nobody) 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.728: Execute command and get response 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.728: Get check bytes 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.728: [egismoc] CMD_STATES entering state 0 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.729: [egismoc] CMD_STATES entering state 1 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.730: Command receive callback 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.730: [egismoc] CMD_STATES completed successfully 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.730: Delete callback 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.730: Response prefix valid: yes 426s (process:2245): libfprint-device-DEBUG: 00:54:35.730: Device reported deletion completion 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.730: [egismoc] DELETE_STATES completed successfully 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.730: Task SSM done 426s (process:2245): libfprint-device-DEBUG: 00:54:35.730: Completing action FPI_DEVICE_ACTION_DELETE in idle! 426s (process:2245): libfprint-device-DEBUG: 00:54:35.730: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.730: List 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.730: [egismoc] LIST_STATES entering state 0 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.730: Execute command and get response 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.730: Get check bytes 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.730: [egismoc] CMD_STATES entering state 0 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.730: [egismoc] CMD_STATES entering state 1 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.731: Command receive callback 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.731: [egismoc] CMD_STATES completed successfully 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.731: List callback 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.731: Device fingerprint 1: FP1-00000000-7-00000000-nobody 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.731: Number of currently enrolled fingerprints on the device is 1 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.731: [egismoc] LIST_STATES entering state 1 426s (process:2245): libfprint-device-DEBUG: 00:54:35.731: Device reported listing completion 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.731: [egismoc] LIST_STATES completed successfully 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.731: Task SSM done 426s (process:2245): libfprint-device-DEBUG: 00:54:35.731: Completing action FPI_DEVICE_ACTION_LIST in idle! 426s (process:2245): libfprint-device-DEBUG: 00:54:35.731: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.731: Clear storage 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.731: [egismoc] DELETE_STATES entering state 0 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.731: Execute command and get response 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.731: Get check bytes 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.731: [egismoc] CMD_STATES entering state 0 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.732: [egismoc] CMD_STATES entering state 1 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.732: Command receive callback 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.732: [egismoc] CMD_STATES completed successfully 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.732: List callback 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.732: Device fingerprint 1: FP1-00000000-7-00000000-nobody 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.732: Number of currently enrolled fingerprints on the device is 1 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.732: [egismoc] DELETE_STATES entering state 1 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.732: Get delete command 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.732: Execute command and get response 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.732: Get check bytes 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.732: [egismoc] CMD_STATES entering state 0 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.733: [egismoc] CMD_STATES entering state 1 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.733: Command receive callback 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.733: [egismoc] CMD_STATES completed successfully 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.733: Delete callback 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.733: Response prefix valid: yes 426s (process:2245): libfprint-device-DEBUG: 00:54:35.733: Device reported deletion completion 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.733: [egismoc] DELETE_STATES completed successfully 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.733: Task SSM done 426s (process:2245): libfprint-device-DEBUG: 00:54:35.733: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 426s (process:2245): libfprint-device-DEBUG: 00:54:35.733: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.734: List 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.734: [egismoc] LIST_STATES entering state 0 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.734: Execute command and get response 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.734: Get check bytes 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.734: [egismoc] CMD_STATES entering state 0 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.734: [egismoc] CMD_STATES entering state 1 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.735: Command receive callback 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.735: [egismoc] CMD_STATES completed successfully 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.735: List callback 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.735: Number of currently enrolled fingerprints on the device is 0 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.735: [egismoc] LIST_STATES entering state 1 426s (process:2245): libfprint-device-DEBUG: 00:54:35.735: Device reported listing completion 426s (process:2245): libfprint-SSM-DEBUG: 00:54:35.735: [egismoc] LIST_STATES completed successfully 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.735: Task SSM done 426s (process:2245): libfprint-device-DEBUG: 00:54:35.735: Completing action FPI_DEVICE_ACTION_LIST in idle! 426s (process:2245): libfprint-device-DEBUG: 00:54:35.735: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.735: Closing device 426s (process:2245): libfprint-egismoc-DEBUG: 00:54:35.735: Cancel 426s (process:2245): libfprint-device-DEBUG: 00:54:35.735: Device reported close completion 426s (process:2245): libfprint-device-DEBUG: 00:54:35.735: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 426s (process:2245): libfprint-device-DEBUG: 00:54:35.735: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 426s listing - device should have prints 426s clear device storage 426s clear done 426s listing - device should be empty 426s enrolling 426s finger status: 426s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xe9b6f628 (FpiDeviceEgisMoc at 0x1402810)>, 1, , None, None) 426s finger status: 426s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xe9b6f628 (FpiDeviceEgisMoc at 0x1402810)>, 2, , None, None) 426s finger status: 426s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xe9b6f628 (FpiDeviceEgisMoc at 0x1402810)>, 2, None, None, GLib.Error('Your device is having trouble recognizing you. Make sure your sensor is clean.', 'fp - device - retry - quark', 3)) 426s finger status: 426s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xe9b6f628 (FpiDeviceEgisMoc at 0x1402810)>, 3, , None, None) 426s finger status: 426s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xe9b6f628 (FpiDeviceEgisMoc at 0x1402810)>, 4, , None, None) 426s finger status: 426s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xe9b6f628 (FpiDeviceEgisMoc at 0x1402810)>, 5, , None, None) 426s finger status: 426s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xe9b6f628 (FpiDeviceEgisMoc at 0x1402810)>, 6, , None, None) 426s finger status: 426s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xe9b6f628 (FpiDeviceEgisMoc at 0x1402810)>, 7, , None, None) 426s finger status: 426s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xe9b6f628 (FpiDeviceEgisMoc at 0x1402810)>, 8, , None, None) 426s finger status: 426s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xe9b6f628 (FpiDeviceEgisMoc at 0x1402810)>, 9, , None, None) 426s finger status: 426s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xe9b6f628 (FpiDeviceEgisMoc at 0x1402810)>, 10, , None, None) 426s enroll done 426s listing - device should have 1 print 426s verifying 426s verify done 426s async identifying 426s indentification_done: 426s try to enroll duplicate 426s duplicate enroll attempt done 426s listing - device should still only have 1 print 426s enroll new finger 426s finger status: 426s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xe9b6f628 (FpiDeviceEgisMoc at 0x1402810)>, 1, , None, None) 426s finger status: 426s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xe9b6f628 (FpiDeviceEgisMoc at 0x1402810)>, 2, , None, None) 426s finger status: 426s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xe9b6f628 (FpiDeviceEgisMoc at 0x1402810)>, 2, None, None, GLib.Error('The finger was not centered properly, please try again.', 'fp - device - retry - quark', 2)) 426s finger status: 426s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xe9b6f628 (FpiDeviceEgisMoc at 0x1402810)>, 2, None, None, GLib.Error('The finger was not centered properly, please try again.', 'fp - device - retry - quark', 2)) 426s finger status: 426s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xe9b6f628 (FpiDeviceEgisMoc at 0x1402810)>, 3, , None, None) 426s finger status: 426s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xe9b6f628 (FpiDeviceEgisMoc at 0x1402810)>, 3, None, None, GLib.Error('The finger was not centered properly, please try again.', 'fp - device - retry - quark', 2)) 426s finger status: 426s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xe9b6f628 (FpiDeviceEgisMoc at 0x1402810)>, 4, , None, None) 426s finger status: 426s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xe9b6f628 (FpiDeviceEgisMoc at 0x1402810)>, 5, , None, None) 426s finger status: 426s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xe9b6f628 (FpiDeviceEgisMoc at 0x1402810)>, 6, , None, None) 426s finger status: 426s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xe9b6f628 (FpiDeviceEgisMoc at 0x1402810)>, 7, , None, None) 426s finger status: 426s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xe9b6f628 (FpiDeviceEgisMoc at 0x1402810)>, 8, , None, None) 426s finger status: 426s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xe9b6f628 (FpiDeviceEgisMoc at 0x1402810)>, 9, , None, None) 426s finger status: 426s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xe9b6f628 (FpiDeviceEgisMoc at 0x1402810)>, 10, , None, None) 426s enroll new finger done 426s listing - device should have 2 prints 426s deleting first print 426s delete done 426s listing - device should only have second print 426s clear device storage 426s clear done 426s listing - device should be empty 426s ** (umockdev-run:2241): DEBUG: 00:54:35.763: umockdev.vala:154: Removing test bed /tmp/umockdev.SD8712 426s (umockdev-run:2241): GLib-DEBUG: 00:54:35.772: unsetenv() is not thread-safe and should not be used after threads are created 426s PASS: libfprint-2/driver-egismoc-05a1.test 426s Running test: libfprint-2/driver-vfs301.test 426s ** (umockdev-run:2253): DEBUG: 00:54:35.837: umockdev.vala:127: Created udev test bed /tmp/umockdev.3EAJ22 426s ** (umockdev-run:2253): DEBUG: 00:54:35.837: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.3 426s ** (umockdev-run:2253): DEBUG: 00:54:35.839: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.3 (subsystem usb) 426s ** (umockdev-run:2253): DEBUG: 00:54:35.843: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.3EAJ22/dev/bus/usb/002/005 426s ** (umockdev-run:2253): DEBUG: 00:54:35.843: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:1d.0/usb2/2-1 426s ** (umockdev-run:2253): DEBUG: 00:54:35.845: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:1d.0/usb2/2-1 (subsystem usb) 426s ** (umockdev-run:2253): DEBUG: 00:54:35.849: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.3EAJ22/dev/bus/usb/002/002 426s ** (umockdev-run:2253): DEBUG: 00:54:35.849: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:1d.0/usb2 426s ** (umockdev-run:2253): DEBUG: 00:54:35.850: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:1d.0/usb2 (subsystem usb) 426s ** (umockdev-run:2253): DEBUG: 00:54:35.855: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.3EAJ22/dev/bus/usb/002/001 426s ** (umockdev-run:2253): DEBUG: 00:54:35.855: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:1d.0 426s ** (umockdev-run:2253): DEBUG: 00:54:35.855: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:1d.0 (subsystem pci) 426s (umockdev-run:2253): GLib-GIO-DEBUG: 00:54:35.859: _g_io_module_get_default: Found default implementation local (GLocalVfs) for ?gio-vfs? 427s (process:2257): libfprint-context-DEBUG: 00:54:35.997: Initializing FpContext (libfprint version 1.94.8+tod1) 427s (process:2257): libfprint-tod-DEBUG: 00:54:35.997: Impossible to load the shared drivers dir Error opening directory “/usr/lib/arm-linux-gnueabihf/libfprint-2/tod-1”: No such file or directory 427s (process:2257): libfprint-context-DEBUG: 00:54:36.000: No driver found for USB device 8087:0020 427s (process:2257): libfprint-context-DEBUG: 00:54:36.000: No driver found for USB device 1D6B:0002 427s (process:2257): libfprint-device-DEBUG: 00:54:36.001: Device reported probe completion 427s (process:2257): libfprint-device-DEBUG: 00:54:36.001: Completing action FPI_DEVICE_ACTION_PROBE in idle! 427s (process:2257): libfprint-device-DEBUG: 00:54:36.001: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 427s (process:2257): libfprint-image_device-DEBUG: 00:54:36.003: Image device open completed 427s (process:2257): libfprint-device-DEBUG: 00:54:36.003: Device reported open completion 427s (process:2257): libfprint-device-DEBUG: 00:54:36.003: Completing action FPI_DEVICE_ACTION_OPEN in idle! 427s (process:2257): libfprint-device-DEBUG: 00:54:36.003: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 427s (process:2257): libfprint-device-DEBUG: 00:54:36.004: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 427s (process:2257): libfprint-image_device-DEBUG: 00:54:36.004: Activating image device 427s (process:2257): libfprint-image_device-DEBUG: 00:54:36.004: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING 427s (process:2257): libfprint-SSM-DEBUG: 00:54:36.004: [vfs301] 1 entering state 0 427s (process:2257): libfprint-SSM-DEBUG: 00:54:36.042: [vfs301] 1 completed successfully 427s (process:2257): libfprint-image_device-DEBUG: 00:54:36.042: Image device activation completed 427s (process:2257): libfprint-image_device-DEBUG: 00:54:36.043: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE 427s (process:2257): libfprint-image_device-DEBUG: 00:54:36.043: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 427s (process:2257): libfprint-SSM-DEBUG: 00:54:36.043: [vfs301] M_LOOP_NUM_STATES entering state 0 427s (process:2257): libfprint-SSM-DEBUG: 00:54:36.044: [vfs301] M_LOOP_NUM_STATES entering state 1 427s (process:2257): libfprint-device-DEBUG: 00:54:36.044: Device reported finger status change: FP_FINGER_STATUS_NEEDED 427s (process:2257): libfprint-device-DEBUG: 00:54:36.106: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 427s (process:2257): libfprint-SSM-DEBUG: 00:54:36.244: [vfs301] M_LOOP_NUM_STATES entering state 2 427s (process:2257): libfprint-SSM-DEBUG: 00:54:36.245: [vfs301] M_LOOP_NUM_STATES entering state 1 427s (process:2257): libfprint-SSM-DEBUG: 00:54:36.445: [vfs301] M_LOOP_NUM_STATES entering state 2 427s (process:2257): libfprint-SSM-DEBUG: 00:54:36.446: [vfs301] M_LOOP_NUM_STATES entering state 3 427s (process:2257): libfprint-device-DEBUG: 00:54:36.446: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 427s (process:2257): libfprint-image_device-DEBUG: 00:54:36.446: Image device reported finger status: on 427s (process:2257): libfprint-image_device-DEBUG: 00:54:36.446: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 427s (process:2257): libfprint-SSM-DEBUG: 00:54:36.447: [vfs301] M_LOOP_NUM_STATES entering state 4 427s (process:2257): libfprint-SSM-DEBUG: 00:54:36.647: [vfs301] M_LOOP_NUM_STATES entering state 5 427s (process:2257): libfprint-SSM-DEBUG: 00:54:36.652: [vfs301] M_LOOP_NUM_STATES entering state 6 427s (process:2257): libfprint-image_device-DEBUG: 00:54:36.652: Image device captured an image 427s (process:2257): libfprint-image_device-DEBUG: 00:54:36.653: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 427s (process:2257): libfprint-device-DEBUG: 00:54:36.653: Device reported finger status change: FP_FINGER_STATUS_PRESENT 427s (process:2257): libfprint-SSM-DEBUG: 00:54:36.653: [vfs301] M_LOOP_NUM_STATES completed successfully 427s (process:2257): libfprint-device-DEBUG: 00:54:36.653: Device reported finger status change: FP_FINGER_STATUS_NONE 427s (process:2257): libfprint-image_device-DEBUG: 00:54:36.653: Image device reported finger status: off 427s (process:2257): libfprint-image_device-DEBUG: 00:54:36.653: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 427s (process:2257): libfprint-image_device-DEBUG: 00:54:36.653: Deactivating image device 427s (process:2257): libfprint-image_device-DEBUG: 00:54:36.653: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_DEACTIVATING 427s (process:2257): libfprint-image_device-DEBUG: 00:54:36.653: Image device deactivation completed 427s (process:2257): libfprint-image_device-DEBUG: 00:54:36.653: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE 427s (process:2257): libfprint-image-DEBUG: 00:54:36.671: Minutiae scan completed in 0.017927 secs 427s (process:2257): libfprint-device-DEBUG: 00:54:36.672: Device reported capture completion 427s (process:2257): libfprint-device-DEBUG: 00:54:36.672: Completing action FPI_DEVICE_ACTION_CAPTURE in idle! 427s (process:2257): libfprint-device-DEBUG: 00:54:36.672: Updated temperature model after 0.57 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 427s (process:2257): libfprint-image_device-DEBUG: 00:54:36.672: Image device close completed 427s (process:2257): libfprint-device-DEBUG: 00:54:36.672: Device reported close completion 427s (process:2257): libfprint-device-DEBUG: 00:54:36.672: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 427s (process:2257): libfprint-device-DEBUG: 00:54:36.672: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 427s ** (umockdev-run:2253): DEBUG: 00:54:36.764: umockdev.vala:154: Removing test bed /tmp/umockdev.3EAJ22 427s (umockdev-run:2253): GLib-DEBUG: 00:54:36.773: unsetenv() is not thread-safe and should not be used after threads are created 427s Comparing PNGs /tmp/libfprint-umockdev-test-tu5w1xrs/capture.png and /usr/share/installed-tests/libfprint-2/vfs301/capture.png 427s PASS: libfprint-2/driver-vfs301.test 427s Running test: libfprint-2/fp-context.test 427s TAP version 14 427s # random seed: R02S7b52f7cefb1ff2612dc0488ea0d0504f 427s 1..9 427s # Start of context tests 427s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 427s # libfprint-tod-DEBUG: Impossible to load the shared drivers dir Error opening directory ?/usr/lib/arm-linux-gnueabihf/libfprint-2/tod-1?: No such file or directory 427s ok 1 /context/new 427s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 427s # libfprint-tod-DEBUG: Impossible to load the shared drivers dir Error opening directory ?/usr/lib/arm-linux-gnueabihf/libfprint-2/tod-1?: No such file or directory 427s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0003 427s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 427s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0002 427s ok 2 /context/no-devices 427s # GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used after threads are created 427s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 427s # libfprint-tod-DEBUG: Impossible to load the shared drivers dir Error opening directory ?/usr/lib/arm-linux-gnueabihf/libfprint-2/tod-1?: No such file or directory 427s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0003 427s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 427s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0002 427s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_IMAGE, /tmp/libfprint-52FI22/virtual_image.socket 427s # libfprint-context-DEBUG: created 427s # libfprint-device-DEBUG: Device reported probe completion 427s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 427s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 427s # GLib-DEBUG: unsetenv() is not thread-safe and should not be used after threads are created 427s ok 3 /context/has-virtual-device 427s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 427s # libfprint-tod-DEBUG: Impossible to load the shared drivers dir Error opening directory ?/usr/lib/arm-linux-gnueabihf/libfprint-2/tod-1?: No such file or directory 427s # GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used after threads are created 427s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0003 427s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 427s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0002 427s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_IMAGE, /tmp/libfprint-QZXI22/virtual_image.socket 427s # libfprint-context-DEBUG: created 427s # libfprint-device-DEBUG: Device reported probe completion 427s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 427s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 427s # GLib-DEBUG: unsetenv() is not thread-safe and should not be used after threads are created 427s ok 4 /context/enumerates-new-devices 427s # GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used after threads are created 427s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 427s # libfprint-tod-DEBUG: Impossible to load the shared drivers dir Error opening directory ?/usr/lib/arm-linux-gnueabihf/libfprint-2/tod-1?: No such file or directory 427s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0003 427s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 427s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0002 427s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_IMAGE, /tmp/libfprint-92WI22/virtual_image.socket 427s # libfprint-context-DEBUG: created 427s # libfprint-device-DEBUG: Device reported probe completion 427s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 427s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 427s # GLib-DEBUG: unsetenv() is not thread-safe and should not be used after threads are created 427s ok 5 /context/remove-device-closed 427s # GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used after threads are created 427s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 427s # libfprint-tod-DEBUG: Impossible to load the shared drivers dir Error opening directory ?/usr/lib/arm-linux-gnueabihf/libfprint-2/tod-1?: No such file or directory 427s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0003 427s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 427s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0002 427s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_IMAGE, /tmp/libfprint-2XUI22/virtual_image.socket 427s # libfprint-context-DEBUG: created 427s # libfprint-device-DEBUG: Device reported probe completion 427s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 427s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 427s (/usr/libexec/installed-tests/libfprint-2/test-fp-context:2264): libfprint-virtual_image-DEBUG: 00:54:36.826: 7399844887403: ../libfprint/drivers/virtual-image.c:216 427s (/usr/libexec/installed-tests/libfprint-2/test-fp-context:2264): libfprint-virtual_device_connection-DEBUG: 00:54:36.826: 7399844887534: ../libfprint/drivers/virtual-device-listener.c:153 427s Executing: libfprint-2/fp-context.test 427s # libfprint-image_device-DEBUG: Image device open completed 427s # libfprint-device-DEBUG: Device reported open completion 427s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 427s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 427s (/usr/libexec/installed-tests/libfprint-2/test-fp-context:2264): libfprint-virtual_image-DEBUG: 00:54:36.927: 7399844988021: ../libfprint/drivers/virtual-image.c:244 428s # libfprint-image_device-DEBUG: Image device close completed 428s # libfprint-device-DEBUG: Device reported close completion 428s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 428s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 428s # GLib-DEBUG: unsetenv() is not thread-safe and should not be used after threads are created 428s ok 6 /context/remove-device-closing 428s # GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used after threads are created 428s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 428s # libfprint-tod-DEBUG: Impossible to load the shared drivers dir Error opening directory ?/usr/lib/arm-linux-gnueabihf/libfprint-2/tod-1?: No such file or directory 428s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0003 428s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 428s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0002 428s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_IMAGE, /tmp/libfprint-J3K112/virtual_image.socket 428s # libfprint-context-DEBUG: created 428s # libfprint-device-DEBUG: Device reported probe completion 428s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 428s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 428s (/usr/libexec/installed-tests/libfprint-2/test-fp-context:2264): libfprint-virtual_image-DEBUG: 00:54:37.030: 7399845091865: ../libfprint/drivers/virtual-image.c:216 428s (/usr/libexec/installed-tests/libfprint-2/test-fp-context:2264): libfprint-virtual_device_connection-DEBUG: 00:54:37.030: 7399845091891: ../libfprint/drivers/virtual-device-listener.c:153 428s # libfprint-image_device-DEBUG: Image device open completed 428s # libfprint-device-DEBUG: Device reported open completion 428s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 428s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 428s (/usr/libexec/installed-tests/libfprint-2/test-fp-context:2264): libfprint-virtual_image-DEBUG: 00:54:37.131: 7399845192340: ../libfprint/drivers/virtual-image.c:244 428s # libfprint-image_device-DEBUG: Image device close completed 428s # libfprint-device-DEBUG: Device reported close completion 428s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 428s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 428s # GLib-DEBUG: unsetenv() is not thread-safe and should not be used after threads are created 428s ok 7 /context/remove-device-open 428s # GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used after threads are created 428s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 428s # libfprint-tod-DEBUG: Impossible to load the shared drivers dir Error opening directory ?/usr/lib/arm-linux-gnueabihf/libfprint-2/tod-1?: No such file or directory 428s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0003 428s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 428s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0002 428s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_IMAGE, /tmp/libfprint-V0I312/virtual_image.socket 428s # libfprint-context-DEBUG: created 428s # libfprint-device-DEBUG: Device reported probe completion 428s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 428s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 428s (/usr/libexec/installed-tests/libfprint-2/test-fp-context:2264): libfprint-virtual_image-DEBUG: 00:54:37.235: 7399845296327: ../libfprint/drivers/virtual-image.c:216 428s (/usr/libexec/installed-tests/libfprint-2/test-fp-context:2264): libfprint-virtual_device_connection-DEBUG: 00:54:37.235: 7399845296356: ../libfprint/drivers/virtual-device-listener.c:153 428s # libfprint-image_device-DEBUG: Image device open completed 428s # libfprint-device-DEBUG: Device reported open completion 428s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 428s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 428s (/usr/libexec/installed-tests/libfprint-2/test-fp-context:2264): libfprint-virtual_image-DEBUG: 00:54:37.337: 7399845398223: ../libfprint/drivers/virtual-image.c:244 428s # libfprint-image_device-DEBUG: Image device close completed 428s # libfprint-device-DEBUG: Device reported close completion 428s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 428s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 428s # GLib-DEBUG: unsetenv() is not thread-safe and should not be used after threads are created 428s ok 8 /context/remove-device-opening 428s # GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used after threads are created 428s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 428s # libfprint-tod-DEBUG: Impossible to load the shared drivers dir Error opening directory ?/usr/lib/arm-linux-gnueabihf/libfprint-2/tod-1?: No such file or directory 428s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0003 428s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 428s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0002 428s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_IMAGE, /tmp/libfprint-KTCA22/virtual_image.socket 428s # libfprint-context-DEBUG: created 428s # libfprint-device-DEBUG: Device reported probe completion 428s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 428s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 428s (/usr/libexec/installed-tests/libfprint-2/test-fp-context:2264): libfprint-virtual_image-DEBUG: 00:54:37.441: 7399845501958: ../libfprint/drivers/virtual-image.c:216 428s (/usr/libexec/installed-tests/libfprint-2/test-fp-context:2264): libfprint-virtual_device_connection-DEBUG: 00:54:37.441: 7399845501983: ../libfprint/drivers/virtual-device-listener.c:153 428s # libfprint-image_device-DEBUG: Image device open completed 428s # libfprint-device-DEBUG: Device reported open completion 428s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 428s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 428s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 428s # libfprint-image_device-DEBUG: Activating image device 428s # libfprint-image_device-DEBUG: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING 428s # libfprint-image_device-DEBUG: Image device activation completed 428s # libfprint-image_device-DEBUG: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE 428s # libfprint-image_device-DEBUG: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 428s # libfprint-device-DEBUG: Device reported finger status change: FP_FINGER_STATUS_NEEDED 428s # libfprint-image_device-DEBUG: Deactivating image device 428s # libfprint-image_device-DEBUG: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_DEACTIVATING 428s # libfprint-image_device-DEBUG: Image device deactivation completed 428s # libfprint-image_device-DEBUG: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE 428s # libfprint-device-DEBUG: Device reported generic error (The driver encountered a protocol error with the device.) during action; action was: FPI_DEVICE_ACTION_ENROLL 428s # libfprint-device-DEBUG: Device reported enroll completion 428s # libfprint-device-DEBUG: Device reported finger status change: FP_FINGER_STATUS_NONE 428s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 428s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 428s (/usr/libexec/installed-tests/libfprint-2/test-fp-context:2264): libfprint-virtual_image-DEBUG: 00:54:37.541: 7399845602671: ../libfprint/drivers/virtual-image.c:244 428s # libfprint-image_device-DEBUG: Image device close completed 428s # libfprint-device-DEBUG: Device reported close completion 428s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 428s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 428s # GLib-DEBUG: unsetenv() is not thread-safe and should not be used after threads are created 428s ok 9 /context/remove-device-active 428s # End of context tests 428s PASS: libfprint-2/fp-context.test 428s Running test: libfprint-2/driver-vfs7552.test 428s ** (umockdev-run:2288): DEBUG: 00:54:37.692: umockdev.vala:127: Created udev test bed /tmp/umockdev.NJ5F22 428s ** (umockdev-run:2288): DEBUG: 00:54:37.692: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0/usb1/1-7 428s ** (umockdev-run:2288): DEBUG: 00:54:37.694: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0/usb1/1-7 (subsystem usb) 428s ** (umockdev-run:2288): DEBUG: 00:54:37.698: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.NJ5F22/dev/bus/usb/001/003 428s ** (umockdev-run:2288): DEBUG: 00:54:37.698: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0/usb1 428s ** (umockdev-run:2288): DEBUG: 00:54:37.699: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0/usb1 (subsystem usb) 428s ** (umockdev-run:2288): DEBUG: 00:54:37.703: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.NJ5F22/dev/bus/usb/001/001 428s ** (umockdev-run:2288): DEBUG: 00:54:37.703: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0 428s ** (umockdev-run:2288): DEBUG: 00:54:37.704: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0 (subsystem pci) 428s (umockdev-run:2288): GLib-GIO-DEBUG: 00:54:37.709: _g_io_module_get_default: Found default implementation local (GLocalVfs) for ?gio-vfs? 428s (process:2292): libfprint-context-DEBUG: 00:54:37.836: Initializing FpContext (libfprint version 1.94.8+tod1) 428s (process:2292): libfprint-tod-DEBUG: 00:54:37.836: Impossible to load the shared drivers dir Error opening directory “/usr/lib/arm-linux-gnueabihf/libfprint-2/tod-1”: No such file or directory 428s (process:2292): libfprint-context-DEBUG: 00:54:37.839: No driver found for USB device 1D6B:0002 428s (process:2292): libfprint-device-DEBUG: 00:54:37.840: Device reported probe completion 428s (process:2292): libfprint-device-DEBUG: 00:54:37.840: Completing action FPI_DEVICE_ACTION_PROBE in idle! 428s (process:2292): libfprint-device-DEBUG: 00:54:37.840: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.842: [vfs7552] DEV_OPEN_NUM_STATES entering state 0 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.842: [vfs7552] DEVICE OPEN entering state 0 428s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.842: Sending vfs7552_cmd_01 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.843: [vfs7552] DEVICE OPEN entering state 1 428s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.843: Receiving 64 bytes 428s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.843: Got 38 bytes out of 64 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.843: [vfs7552] DEVICE OPEN entering state 2 428s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.843: Sending vfs7552_cmd_19 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.844: [vfs7552] DEVICE OPEN entering state 3 428s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.844: Receiving 128 bytes 428s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.844: Got 68 bytes out of 128 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.844: [vfs7552] DEVICE OPEN entering state 4 428s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.844: Sending vfs7552_init_00 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.845: [vfs7552] DEVICE OPEN entering state 5 428s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.845: Receiving 64 bytes 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.845: [vfs7552] DEVICE OPEN entering state 6 428s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.845: Sending vfs7552_init_01 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.845: [vfs7552] DEVICE OPEN entering state 7 428s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.845: Receiving 64 bytes 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.846: [vfs7552] DEVICE OPEN entering state 8 428s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.846: Sending vfs7552_init_02 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.846: [vfs7552] DEVICE OPEN entering state 9 428s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.846: Receiving 64 bytes 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.847: [vfs7552] DEVICE OPEN entering state 10 428s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.847: Sending vfs7552_init_03 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.847: [vfs7552] DEVICE OPEN entering state 11 428s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.847: Receiving 64 bytes 428s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.848: Got 10 bytes out of 64 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.848: [vfs7552] DEVICE OPEN entering state 12 428s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.848: Sending vfs7552_init_04 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.848: [vfs7552] DEVICE OPEN entering state 13 428s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.848: Receiving 64 bytes 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.848: [vfs7552] DEVICE OPEN completed successfully 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.848: [vfs7552] DEV_OPEN_NUM_STATES completed successfully 428s (process:2292): libfprint-image_device-DEBUG: 00:54:37.849: Image device open completed 428s (process:2292): libfprint-device-DEBUG: 00:54:37.849: Device reported open completion 428s (process:2292): libfprint-device-DEBUG: 00:54:37.849: Completing action FPI_DEVICE_ACTION_OPEN in idle! 428s (process:2292): libfprint-device-DEBUG: 00:54:37.849: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 428s (process:2292): libfprint-device-DEBUG: 00:54:37.849: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 428s (process:2292): libfprint-image_device-DEBUG: 00:54:37.849: Activating image device 428s (process:2292): libfprint-image_device-DEBUG: 00:54:37.849: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING 428s (process:2292): libfprint-image_device-DEBUG: 00:54:37.849: Image device activation completed 428s (process:2292): libfprint-image_device-DEBUG: 00:54:37.849: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE 428s (process:2292): libfprint-image_device-DEBUG: 00:54:37.849: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 428s (process:2292): libfprint-device-DEBUG: 00:54:37.849: Device reported finger status change: FP_FINGER_STATUS_NEEDED 428s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.899: changing to 1 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.899: [vfs7552] ACTIVATE_NUM_STATES entering state 0 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.899: [vfs7552] ACTIVATE INIT entering state 0 428s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.899: Sending vfs7552_image_start 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.899: [vfs7552] ACTIVATE INIT entering state 1 428s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.899: Receiving 2048 bytes 428s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.900: Got 1962 bytes out of 2048 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.900: [vfs7552] ACTIVATE INIT completed successfully 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.900: [vfs7552] ACTIVATE_NUM_STATES entering state 1 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.900: [vfs7552] ACTIVATE INTERRUPT QUERY entering state 0 428s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.900: Receiving 8 bytes 428s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.900: Got 5 bytes out of 8 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.900: [vfs7552] ACTIVATE INTERRUPT QUERY completed successfully 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.900: [vfs7552] ACTIVATE_NUM_STATES entering state 2 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.900: [vfs7552] ACTIVATE_NUM_STATES entering state 1 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.900: [vfs7552] ACTIVATE INTERRUPT QUERY entering state 0 428s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.900: Receiving 8 bytes 428s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.901: Got 5 bytes out of 8 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.901: [vfs7552] ACTIVATE INTERRUPT QUERY completed successfully 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.901: [vfs7552] ACTIVATE_NUM_STATES entering state 2 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.901: [vfs7552] ACTIVATE_NUM_STATES entering state 3 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.901: [vfs7552] ACTIVATE_NUM_STATES completed successfully 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.901: [vfs7552] CAPTURE_NUM_STATES entering state 0 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.901: [vfs7552] QUERY DATA READY entering state 0 428s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.901: Sending vfs7552_is_image_ready 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.901: [vfs7552] QUERY DATA READY entering state 1 428s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.901: Receiving 64 bytes 428s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.901: Got 6 bytes out of 64 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.901: [vfs7552] QUERY DATA READY completed successfully 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.901: [vfs7552] CAPTURE_NUM_STATES entering state 1 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.901: [vfs7552] CAPTURE_NUM_STATES entering state 0 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.901: [vfs7552] QUERY DATA READY entering state 0 428s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.901: Sending vfs7552_is_image_ready 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.902: [vfs7552] QUERY DATA READY entering state 1 428s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.902: Receiving 64 bytes 428s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.902: Got 6 bytes out of 64 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.902: [vfs7552] QUERY DATA READY completed successfully 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.902: [vfs7552] CAPTURE_NUM_STATES entering state 1 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.902: [vfs7552] CAPTURE_NUM_STATES entering state 0 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.902: [vfs7552] QUERY DATA READY entering state 0 428s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.902: Sending vfs7552_is_image_ready 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.903: [vfs7552] QUERY DATA READY entering state 1 428s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.903: Receiving 64 bytes 428s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.903: Got 6 bytes out of 64 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.903: [vfs7552] QUERY DATA READY completed successfully 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.903: [vfs7552] CAPTURE_NUM_STATES entering state 1 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.903: [vfs7552] CAPTURE_NUM_STATES entering state 0 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.903: [vfs7552] QUERY DATA READY entering state 0 428s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.903: Sending vfs7552_is_image_ready 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.904: [vfs7552] QUERY DATA READY entering state 1 428s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.904: Receiving 64 bytes 428s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.904: Got 6 bytes out of 64 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.904: [vfs7552] QUERY DATA READY completed successfully 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.904: [vfs7552] CAPTURE_NUM_STATES entering state 1 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.904: [vfs7552] CAPTURE_NUM_STATES entering state 0 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.904: [vfs7552] QUERY DATA READY entering state 0 428s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.904: Sending vfs7552_is_image_ready 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.904: [vfs7552] QUERY DATA READY entering state 1 428s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.904: Receiving 64 bytes 428s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.905: Got 6 bytes out of 64 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.905: [vfs7552] QUERY DATA READY completed successfully 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.905: [vfs7552] CAPTURE_NUM_STATES entering state 1 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.905: [vfs7552] CAPTURE_NUM_STATES entering state 0 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.905: [vfs7552] QUERY DATA READY entering state 0 428s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.905: Sending vfs7552_is_image_ready 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.905: [vfs7552] QUERY DATA READY entering state 1 428s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.905: Receiving 64 bytes 428s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.906: Got 6 bytes out of 64 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.906: [vfs7552] QUERY DATA READY completed successfully 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.906: [vfs7552] CAPTURE_NUM_STATES entering state 1 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.906: [vfs7552] CAPTURE_NUM_STATES entering state 0 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.906: [vfs7552] QUERY DATA READY entering state 0 428s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.906: Sending vfs7552_is_image_ready 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.906: [vfs7552] QUERY DATA READY entering state 1 428s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.906: Receiving 64 bytes 428s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.907: Got 6 bytes out of 64 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.907: [vfs7552] QUERY DATA READY completed successfully 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.907: [vfs7552] CAPTURE_NUM_STATES entering state 1 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.907: [vfs7552] CAPTURE_NUM_STATES entering state 0 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.907: [vfs7552] QUERY DATA READY entering state 0 428s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.907: Sending vfs7552_is_image_ready 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.907: [vfs7552] QUERY DATA READY entering state 1 428s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.907: Receiving 64 bytes 428s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.907: Got 6 bytes out of 64 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.907: [vfs7552] QUERY DATA READY completed successfully 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.907: [vfs7552] CAPTURE_NUM_STATES entering state 1 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.907: [vfs7552] CAPTURE_NUM_STATES entering state 0 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.907: [vfs7552] QUERY DATA READY entering state 0 428s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.907: Sending vfs7552_is_image_ready 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.908: [vfs7552] QUERY DATA READY entering state 1 428s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.908: Receiving 64 bytes 428s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.908: Got 6 bytes out of 64 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.908: [vfs7552] QUERY DATA READY completed successfully 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.908: [vfs7552] CAPTURE_NUM_STATES entering state 1 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.908: [vfs7552] CAPTURE_NUM_STATES entering state 0 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.908: [vfs7552] QUERY DATA READY entering state 0 428s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.908: Sending vfs7552_is_image_ready 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.909: [vfs7552] QUERY DATA READY entering state 1 428s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.909: Receiving 64 bytes 428s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.909: Got 6 bytes out of 64 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.909: [vfs7552] QUERY DATA READY completed successfully 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.909: [vfs7552] CAPTURE_NUM_STATES entering state 1 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.909: [vfs7552] CAPTURE_NUM_STATES entering state 0 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.909: [vfs7552] QUERY DATA READY entering state 0 428s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.909: Sending vfs7552_is_image_ready 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.909: [vfs7552] QUERY DATA READY entering state 1 428s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.909: Receiving 64 bytes 428s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.910: Got 6 bytes out of 64 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.910: [vfs7552] QUERY DATA READY completed successfully 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.910: [vfs7552] CAPTURE_NUM_STATES entering state 1 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.910: [vfs7552] CAPTURE_NUM_STATES entering state 0 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.910: [vfs7552] QUERY DATA READY entering state 0 428s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.910: Sending vfs7552_is_image_ready 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.910: [vfs7552] QUERY DATA READY entering state 1 428s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.910: Receiving 64 bytes 428s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.911: Got 6 bytes out of 64 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.911: [vfs7552] QUERY DATA READY completed successfully 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.911: [vfs7552] CAPTURE_NUM_STATES entering state 1 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.911: [vfs7552] CAPTURE_NUM_STATES entering state 0 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.911: [vfs7552] QUERY DATA READY entering state 0 428s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.911: Sending vfs7552_is_image_ready 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.911: [vfs7552] QUERY DATA READY entering state 1 428s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.911: Receiving 64 bytes 428s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.912: Got 6 bytes out of 64 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.912: [vfs7552] QUERY DATA READY completed successfully 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.912: [vfs7552] CAPTURE_NUM_STATES entering state 1 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.912: [vfs7552] CAPTURE_NUM_STATES entering state 0 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.912: [vfs7552] QUERY DATA READY entering state 0 428s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.912: Sending vfs7552_is_image_ready 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.912: [vfs7552] QUERY DATA READY entering state 1 428s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.912: Receiving 64 bytes 428s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.912: Got 6 bytes out of 64 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.912: [vfs7552] QUERY DATA READY completed successfully 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.912: [vfs7552] CAPTURE_NUM_STATES entering state 1 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.912: [vfs7552] CAPTURE_NUM_STATES entering state 0 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.912: [vfs7552] QUERY DATA READY entering state 0 428s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.912: Sending vfs7552_is_image_ready 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.913: [vfs7552] QUERY DATA READY entering state 1 428s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.913: Receiving 64 bytes 428s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.913: Got 6 bytes out of 64 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.913: [vfs7552] QUERY DATA READY completed successfully 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.913: [vfs7552] CAPTURE_NUM_STATES entering state 1 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.913: [vfs7552] CAPTURE_NUM_STATES entering state 0 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.913: [vfs7552] QUERY DATA READY entering state 0 428s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.913: Sending vfs7552_is_image_ready 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.914: [vfs7552] QUERY DATA READY entering state 1 428s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.914: Receiving 64 bytes 428s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.914: Got 6 bytes out of 64 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.914: [vfs7552] QUERY DATA READY completed successfully 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.914: [vfs7552] CAPTURE_NUM_STATES entering state 1 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.914: [vfs7552] CAPTURE_NUM_STATES entering state 0 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.914: [vfs7552] QUERY DATA READY entering state 0 428s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.914: Sending vfs7552_is_image_ready 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.915: [vfs7552] QUERY DATA READY entering state 1 428s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.915: Receiving 64 bytes 428s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.915: Got 6 bytes out of 64 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.915: [vfs7552] QUERY DATA READY completed successfully 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.915: [vfs7552] CAPTURE_NUM_STATES entering state 1 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.915: [vfs7552] CAPTURE_NUM_STATES entering state 0 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.915: [vfs7552] QUERY DATA READY entering state 0 428s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.915: Sending vfs7552_is_image_ready 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.916: [vfs7552] QUERY DATA READY entering state 1 428s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.916: Receiving 64 bytes 428s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.916: Got 6 bytes out of 64 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.916: [vfs7552] QUERY DATA READY completed successfully 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.916: [vfs7552] CAPTURE_NUM_STATES entering state 1 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.916: [vfs7552] CAPTURE_NUM_STATES entering state 0 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.916: [vfs7552] QUERY DATA READY entering state 0 428s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.916: Sending vfs7552_is_image_ready 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.917: [vfs7552] QUERY DATA READY entering state 1 428s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.917: Receiving 64 bytes 428s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.917: Got 6 bytes out of 64 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.917: [vfs7552] QUERY DATA READY completed successfully 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.917: [vfs7552] CAPTURE_NUM_STATES entering state 1 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.917: [vfs7552] CAPTURE_NUM_STATES entering state 0 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.917: [vfs7552] QUERY DATA READY entering state 0 428s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.917: Sending vfs7552_is_image_ready 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.918: [vfs7552] QUERY DATA READY entering state 1 428s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.918: Receiving 64 bytes 428s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.918: Got 6 bytes out of 64 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.918: [vfs7552] QUERY DATA READY completed successfully 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.918: [vfs7552] CAPTURE_NUM_STATES entering state 1 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.918: [vfs7552] CAPTURE_NUM_STATES entering state 0 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.918: [vfs7552] QUERY DATA READY entering state 0 428s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.918: Sending vfs7552_is_image_ready 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.918: [vfs7552] QUERY DATA READY entering state 1 428s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.918: Receiving 64 bytes 428s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.919: Got 6 bytes out of 64 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.919: [vfs7552] QUERY DATA READY completed successfully 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.919: [vfs7552] CAPTURE_NUM_STATES entering state 1 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.919: [vfs7552] CAPTURE_NUM_STATES entering state 0 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.919: [vfs7552] QUERY DATA READY entering state 0 428s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.919: Sending vfs7552_is_image_ready 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.919: [vfs7552] QUERY DATA READY entering state 1 428s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.919: Receiving 64 bytes 428s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.920: Got 6 bytes out of 64 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.920: [vfs7552] QUERY DATA READY completed successfully 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.920: [vfs7552] CAPTURE_NUM_STATES entering state 1 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.920: [vfs7552] CAPTURE_NUM_STATES entering state 0 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.920: [vfs7552] QUERY DATA READY entering state 0 428s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.920: Sending vfs7552_is_image_ready 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.920: [vfs7552] QUERY DATA READY entering state 1 428s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.920: Receiving 64 bytes 428s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.921: Got 6 bytes out of 64 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.921: [vfs7552] QUERY DATA READY completed successfully 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.921: [vfs7552] CAPTURE_NUM_STATES entering state 1 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.921: [vfs7552] CAPTURE_NUM_STATES entering state 0 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.921: [vfs7552] QUERY DATA READY entering state 0 428s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.921: Sending vfs7552_is_image_ready 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.921: [vfs7552] QUERY DATA READY entering state 1 428s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.921: Receiving 64 bytes 428s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.921: Got 6 bytes out of 64 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.921: [vfs7552] QUERY DATA READY completed successfully 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.921: [vfs7552] CAPTURE_NUM_STATES entering state 1 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.921: [vfs7552] CAPTURE_NUM_STATES entering state 0 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.921: [vfs7552] QUERY DATA READY entering state 0 428s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.921: Sending vfs7552_is_image_ready 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.922: [vfs7552] QUERY DATA READY entering state 1 428s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.922: Receiving 64 bytes 428s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.922: Got 6 bytes out of 64 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.922: [vfs7552] QUERY DATA READY completed successfully 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.922: [vfs7552] CAPTURE_NUM_STATES entering state 1 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.922: [vfs7552] CAPTURE_NUM_STATES entering state 0 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.922: [vfs7552] QUERY DATA READY entering state 0 428s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.922: Sending vfs7552_is_image_ready 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.923: [vfs7552] QUERY DATA READY entering state 1 428s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.923: Receiving 64 bytes 428s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.923: Got 6 bytes out of 64 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.923: [vfs7552] QUERY DATA READY completed successfully 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.923: [vfs7552] CAPTURE_NUM_STATES entering state 1 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.923: [vfs7552] CAPTURE_NUM_STATES entering state 0 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.923: [vfs7552] QUERY DATA READY entering state 0 428s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.923: Sending vfs7552_is_image_ready 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.924: [vfs7552] QUERY DATA READY entering state 1 428s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.924: Receiving 64 bytes 428s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.924: Got 6 bytes out of 64 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.924: [vfs7552] QUERY DATA READY completed successfully 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.924: [vfs7552] CAPTURE_NUM_STATES entering state 1 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.924: [vfs7552] CAPTURE_NUM_STATES entering state 0 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.924: [vfs7552] QUERY DATA READY entering state 0 428s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.924: Sending vfs7552_is_image_ready 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.924: [vfs7552] QUERY DATA READY entering state 1 428s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.924: Receiving 64 bytes 428s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.925: Got 6 bytes out of 64 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.925: [vfs7552] QUERY DATA READY completed successfully 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.925: [vfs7552] CAPTURE_NUM_STATES entering state 1 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.925: [vfs7552] CAPTURE_NUM_STATES entering state 0 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.925: [vfs7552] QUERY DATA READY entering state 0 428s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.925: Sending vfs7552_is_image_ready 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.925: [vfs7552] QUERY DATA READY entering state 1 428s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.925: Receiving 64 bytes 428s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.926: Got 6 bytes out of 64 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.926: [vfs7552] QUERY DATA READY completed successfully 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.926: [vfs7552] CAPTURE_NUM_STATES entering state 1 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.926: [vfs7552] CAPTURE_NUM_STATES entering state 0 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.926: [vfs7552] QUERY DATA READY entering state 0 428s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.926: Sending vfs7552_is_image_ready 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.926: [vfs7552] QUERY DATA READY entering state 1 428s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.926: Receiving 64 bytes 428s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.927: Got 6 bytes out of 64 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.927: [vfs7552] QUERY DATA READY completed successfully 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.927: [vfs7552] CAPTURE_NUM_STATES entering state 1 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.927: [vfs7552] CAPTURE_NUM_STATES entering state 0 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.927: [vfs7552] QUERY DATA READY entering state 0 428s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.927: Sending vfs7552_is_image_ready 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.927: [vfs7552] QUERY DATA READY entering state 1 428s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.927: Receiving 64 bytes 428s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.927: Got 6 bytes out of 64 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.927: [vfs7552] QUERY DATA READY completed successfully 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.927: [vfs7552] CAPTURE_NUM_STATES entering state 1 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.927: [vfs7552] CAPTURE_NUM_STATES entering state 0 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.927: [vfs7552] QUERY DATA READY entering state 0 428s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.927: Sending vfs7552_is_image_ready 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.928: [vfs7552] QUERY DATA READY entering state 1 428s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.928: Receiving 64 bytes 428s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.928: Got 6 bytes out of 64 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.928: [vfs7552] QUERY DATA READY completed successfully 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.928: [vfs7552] CAPTURE_NUM_STATES entering state 1 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.928: [vfs7552] CAPTURE_NUM_STATES entering state 0 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.928: [vfs7552] QUERY DATA READY entering state 0 428s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.928: Sending vfs7552_is_image_ready 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.929: [vfs7552] QUERY DATA READY entering state 1 428s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.929: Receiving 64 bytes 428s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.929: Got 6 bytes out of 64 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.929: [vfs7552] QUERY DATA READY completed successfully 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.929: [vfs7552] CAPTURE_NUM_STATES entering state 1 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.929: [vfs7552] CAPTURE_NUM_STATES entering state 0 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.929: [vfs7552] QUERY DATA READY entering state 0 428s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.929: Sending vfs7552_is_image_ready 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.930: [vfs7552] QUERY DATA READY entering state 1 428s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.930: Receiving 64 bytes 428s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.930: Got 6 bytes out of 64 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.930: [vfs7552] QUERY DATA READY completed successfully 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.930: [vfs7552] CAPTURE_NUM_STATES entering state 1 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.930: [vfs7552] CAPTURE_NUM_STATES entering state 0 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.930: [vfs7552] QUERY DATA READY entering state 0 428s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.930: Sending vfs7552_is_image_ready 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.930: [vfs7552] QUERY DATA READY entering state 1 428s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.930: Receiving 64 bytes 428s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.931: Got 6 bytes out of 64 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.931: [vfs7552] QUERY DATA READY completed successfully 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.931: [vfs7552] CAPTURE_NUM_STATES entering state 1 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.931: [vfs7552] CAPTURE_NUM_STATES entering state 0 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.931: [vfs7552] QUERY DATA READY entering state 0 428s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.931: Sending vfs7552_is_image_ready 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.931: [vfs7552] QUERY DATA READY entering state 1 428s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.931: Receiving 64 bytes 428s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.932: Got 6 bytes out of 64 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.932: [vfs7552] QUERY DATA READY completed successfully 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.932: [vfs7552] CAPTURE_NUM_STATES entering state 1 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.932: [vfs7552] CAPTURE_NUM_STATES entering state 0 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.932: [vfs7552] QUERY DATA READY entering state 0 428s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.932: Sending vfs7552_is_image_ready 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.932: [vfs7552] QUERY DATA READY entering state 1 428s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.932: Receiving 64 bytes 428s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.932: Got 6 bytes out of 64 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.932: [vfs7552] QUERY DATA READY completed successfully 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.932: [vfs7552] CAPTURE_NUM_STATES entering state 1 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.933: [vfs7552] CAPTURE_NUM_STATES entering state 0 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.933: [vfs7552] QUERY DATA READY entering state 0 428s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.933: Sending vfs7552_is_image_ready 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.933: [vfs7552] QUERY DATA READY entering state 1 428s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.933: Receiving 64 bytes 428s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.933: Got 6 bytes out of 64 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.933: [vfs7552] QUERY DATA READY completed successfully 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.933: [vfs7552] CAPTURE_NUM_STATES entering state 1 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.933: [vfs7552] CAPTURE_NUM_STATES entering state 0 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.933: [vfs7552] QUERY DATA READY entering state 0 428s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.933: Sending vfs7552_is_image_ready 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.934: [vfs7552] QUERY DATA READY entering state 1 428s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.934: Receiving 64 bytes 428s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.934: Got 6 bytes out of 64 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.934: [vfs7552] QUERY DATA READY completed successfully 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.934: [vfs7552] CAPTURE_NUM_STATES entering state 1 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.934: [vfs7552] CAPTURE_NUM_STATES entering state 0 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.934: [vfs7552] QUERY DATA READY entering state 0 428s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.934: Sending vfs7552_is_image_ready 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.935: [vfs7552] QUERY DATA READY entering state 1 428s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.935: Receiving 64 bytes 428s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.935: Got 6 bytes out of 64 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.935: [vfs7552] QUERY DATA READY completed successfully 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.935: [vfs7552] CAPTURE_NUM_STATES entering state 1 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.935: [vfs7552] CAPTURE_NUM_STATES entering state 0 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.935: [vfs7552] QUERY DATA READY entering state 0 428s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.935: Sending vfs7552_is_image_ready 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.935: [vfs7552] QUERY DATA READY entering state 1 428s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.935: Receiving 64 bytes 428s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.936: Got 6 bytes out of 64 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.936: [vfs7552] QUERY DATA READY completed successfully 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.936: [vfs7552] CAPTURE_NUM_STATES entering state 1 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.936: [vfs7552] CAPTURE_NUM_STATES entering state 0 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.936: [vfs7552] QUERY DATA READY entering state 0 428s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.936: Sending vfs7552_is_image_ready 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.936: [vfs7552] QUERY DATA READY entering state 1 428s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.936: Receiving 64 bytes 428s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.937: Got 6 bytes out of 64 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.937: [vfs7552] QUERY DATA READY completed successfully 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.937: [vfs7552] CAPTURE_NUM_STATES entering state 1 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.937: [vfs7552] CAPTURE_NUM_STATES entering state 0 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.937: [vfs7552] QUERY DATA READY entering state 0 428s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.937: Sending vfs7552_is_image_ready 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.937: [vfs7552] QUERY DATA READY entering state 1 428s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.937: Receiving 64 bytes 428s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.937: Got 6 bytes out of 64 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.937: [vfs7552] QUERY DATA READY completed successfully 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.937: [vfs7552] CAPTURE_NUM_STATES entering state 1 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.937: [vfs7552] CAPTURE_NUM_STATES entering state 0 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.937: [vfs7552] QUERY DATA READY entering state 0 428s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.937: Sending vfs7552_is_image_ready 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.938: [vfs7552] QUERY DATA READY entering state 1 428s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.938: Receiving 64 bytes 428s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.938: Got 6 bytes out of 64 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.938: [vfs7552] QUERY DATA READY completed successfully 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.938: [vfs7552] CAPTURE_NUM_STATES entering state 1 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.938: [vfs7552] CAPTURE_NUM_STATES entering state 0 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.938: [vfs7552] QUERY DATA READY entering state 0 428s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.938: Sending vfs7552_is_image_ready 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.939: [vfs7552] QUERY DATA READY entering state 1 428s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.939: Receiving 64 bytes 428s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.939: Got 6 bytes out of 64 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.939: [vfs7552] QUERY DATA READY completed successfully 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.939: [vfs7552] CAPTURE_NUM_STATES entering state 1 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.939: [vfs7552] CAPTURE_NUM_STATES entering state 0 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.939: [vfs7552] QUERY DATA READY entering state 0 428s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.939: Sending vfs7552_is_image_ready 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.940: [vfs7552] QUERY DATA READY entering state 1 428s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.940: Receiving 64 bytes 428s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.940: Got 6 bytes out of 64 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.940: [vfs7552] QUERY DATA READY completed successfully 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.940: [vfs7552] CAPTURE_NUM_STATES entering state 1 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.940: [vfs7552] CAPTURE_NUM_STATES entering state 0 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.940: [vfs7552] QUERY DATA READY entering state 0 428s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.940: Sending vfs7552_is_image_ready 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.940: [vfs7552] QUERY DATA READY entering state 1 428s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.940: Receiving 64 bytes 428s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.941: Got 6 bytes out of 64 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.941: [vfs7552] QUERY DATA READY completed successfully 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.941: [vfs7552] CAPTURE_NUM_STATES entering state 1 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.941: [vfs7552] CAPTURE_NUM_STATES entering state 0 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.941: [vfs7552] QUERY DATA READY entering state 0 428s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.941: Sending vfs7552_is_image_ready 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.941: [vfs7552] QUERY DATA READY entering state 1 428s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.941: Receiving 64 bytes 428s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.942: Got 6 bytes out of 64 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.942: [vfs7552] QUERY DATA READY completed successfully 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.942: [vfs7552] CAPTURE_NUM_STATES entering state 1 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.942: [vfs7552] CAPTURE_NUM_STATES entering state 0 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.942: [vfs7552] QUERY DATA READY entering state 0 428s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.942: Sending vfs7552_is_image_ready 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.942: [vfs7552] QUERY DATA READY entering state 1 428s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.942: Receiving 64 bytes 428s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.943: Got 6 bytes out of 64 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.943: [vfs7552] QUERY DATA READY completed successfully 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.943: [vfs7552] CAPTURE_NUM_STATES entering state 1 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.943: [vfs7552] CAPTURE_NUM_STATES entering state 0 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.943: [vfs7552] QUERY DATA READY entering state 0 428s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.943: Sending vfs7552_is_image_ready 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.943: [vfs7552] QUERY DATA READY entering state 1 428s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.943: Receiving 64 bytes 428s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.943: Got 6 bytes out of 64 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.943: [vfs7552] QUERY DATA READY completed successfully 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.943: [vfs7552] CAPTURE_NUM_STATES entering state 1 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.943: [vfs7552] CAPTURE_NUM_STATES entering state 0 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.943: [vfs7552] QUERY DATA READY entering state 0 428s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.943: Sending vfs7552_is_image_ready 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.944: [vfs7552] QUERY DATA READY entering state 1 428s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.944: Receiving 64 bytes 428s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.944: Got 6 bytes out of 64 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.944: [vfs7552] QUERY DATA READY completed successfully 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.944: [vfs7552] CAPTURE_NUM_STATES entering state 1 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.944: [vfs7552] CAPTURE_NUM_STATES entering state 0 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.944: [vfs7552] QUERY DATA READY entering state 0 428s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.944: Sending vfs7552_is_image_ready 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.945: [vfs7552] QUERY DATA READY entering state 1 428s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.945: Receiving 64 bytes 428s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.945: Got 6 bytes out of 64 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.945: [vfs7552] QUERY DATA READY completed successfully 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.945: [vfs7552] CAPTURE_NUM_STATES entering state 1 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.945: [vfs7552] CAPTURE_NUM_STATES entering state 0 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.945: [vfs7552] QUERY DATA READY entering state 0 428s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.945: Sending vfs7552_is_image_ready 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.946: [vfs7552] QUERY DATA READY entering state 1 428s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.946: Receiving 64 bytes 428s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.946: Got 6 bytes out of 64 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.946: [vfs7552] QUERY DATA READY completed successfully 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.946: [vfs7552] CAPTURE_NUM_STATES entering state 1 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.946: [vfs7552] CAPTURE_NUM_STATES entering state 0 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.946: [vfs7552] QUERY DATA READY entering state 0 428s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.946: Sending vfs7552_is_image_ready 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.947: [vfs7552] QUERY DATA READY entering state 1 428s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.947: Receiving 64 bytes 428s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.947: Got 6 bytes out of 64 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.947: [vfs7552] QUERY DATA READY completed successfully 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.947: [vfs7552] CAPTURE_NUM_STATES entering state 1 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.947: [vfs7552] CAPTURE_NUM_STATES entering state 0 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.947: [vfs7552] QUERY DATA READY entering state 0 428s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.947: Sending vfs7552_is_image_ready 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.947: [vfs7552] QUERY DATA READY entering state 1 428s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.947: Receiving 64 bytes 428s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.948: Got 6 bytes out of 64 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.948: [vfs7552] QUERY DATA READY completed successfully 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.948: [vfs7552] CAPTURE_NUM_STATES entering state 1 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.948: [vfs7552] CAPTURE_NUM_STATES entering state 0 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.948: [vfs7552] QUERY DATA READY entering state 0 428s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.948: Sending vfs7552_is_image_ready 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.948: [vfs7552] QUERY DATA READY entering state 1 428s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.948: Receiving 64 bytes 428s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.949: Got 6 bytes out of 64 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.949: [vfs7552] QUERY DATA READY completed successfully 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.949: [vfs7552] CAPTURE_NUM_STATES entering state 1 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.949: [vfs7552] CAPTURE_NUM_STATES entering state 0 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.949: [vfs7552] QUERY DATA READY entering state 0 428s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.949: Sending vfs7552_is_image_ready 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.949: [vfs7552] QUERY DATA READY entering state 1 428s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.949: Receiving 64 bytes 428s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.949: Got 6 bytes out of 64 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.950: [vfs7552] QUERY DATA READY completed successfully 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.950: [vfs7552] CAPTURE_NUM_STATES entering state 1 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.950: [vfs7552] CAPTURE_NUM_STATES entering state 0 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.950: [vfs7552] QUERY DATA READY entering state 0 428s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.950: Sending vfs7552_is_image_ready 428s (process:2292): libfprint-device-DEBUG: 00:54:37.950: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.950: [vfs7552] QUERY DATA READY entering state 1 428s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.950: Receiving 64 bytes 428s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.950: Got 6 bytes out of 64 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.950: [vfs7552] QUERY DATA READY completed successfully 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.950: [vfs7552] CAPTURE_NUM_STATES entering state 1 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.950: [vfs7552] CAPTURE_NUM_STATES entering state 0 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.950: [vfs7552] QUERY DATA READY entering state 0 428s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.950: Sending vfs7552_is_image_ready 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.951: [vfs7552] QUERY DATA READY entering state 1 428s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.951: Receiving 64 bytes 428s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.951: Got 6 bytes out of 64 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.951: [vfs7552] QUERY DATA READY completed successfully 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.951: [vfs7552] CAPTURE_NUM_STATES entering state 1 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.951: [vfs7552] CAPTURE_NUM_STATES entering state 0 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.951: [vfs7552] QUERY DATA READY entering state 0 428s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.951: Sending vfs7552_is_image_ready 428s (process:2292): libfprint-SSM-DEBUG: 00:54:37.952: [vfs7552] QUERY DATA READY entering state 1 428s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.952: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.952: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:37.952: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:37.952: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:37.952: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:37.952: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.952: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:37.952: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.952: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.953: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:37.953: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:37.953: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:37.953: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:37.953: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.953: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:37.953: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.953: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.954: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:37.954: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:37.954: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:37.954: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:37.954: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.954: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:37.954: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.954: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.955: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:37.955: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:37.955: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:37.955: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:37.955: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.955: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:37.955: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.955: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.955: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:37.956: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:37.956: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:37.956: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:37.956: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.956: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:37.956: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.956: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.956: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:37.956: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:37.956: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:37.956: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:37.956: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.956: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:37.957: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.957: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.957: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:37.957: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:37.957: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:37.957: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:37.957: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.957: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:37.958: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.958: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.958: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:37.958: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:37.958: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:37.958: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:37.958: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.958: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:37.959: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.959: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.959: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:37.959: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:37.959: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:37.959: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:37.959: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.959: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:37.959: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.959: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.960: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:37.960: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:37.960: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:37.960: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:37.960: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.960: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:37.960: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.960: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.961: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:37.961: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:37.961: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:37.961: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:37.961: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.961: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:37.961: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.961: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.962: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:37.962: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:37.962: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:37.962: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:37.962: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.962: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:37.962: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.962: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.962: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:37.962: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:37.962: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:37.962: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:37.962: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.962: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:37.963: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.963: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.963: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:37.963: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:37.963: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:37.963: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:37.963: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.963: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:37.964: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.964: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.964: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:37.964: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:37.964: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:37.964: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:37.964: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.964: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:37.964: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.964: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.965: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:37.965: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:37.965: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:37.965: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:37.965: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.965: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:37.965: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.965: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.966: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:37.966: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:37.966: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:37.966: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:37.966: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.966: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:37.966: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.966: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.967: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:37.967: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:37.967: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:37.967: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:37.967: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.967: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:37.967: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.967: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.968: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:37.968: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:37.968: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:37.968: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:37.968: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.968: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:37.968: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.968: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.968: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:37.968: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:37.968: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:37.968: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:37.968: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.968: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:37.969: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.969: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.969: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:37.969: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:37.969: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:37.969: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:37.969: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.969: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:37.970: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.970: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.970: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:37.970: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:37.970: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:37.970: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:37.970: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.970: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:37.971: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.971: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.971: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:37.971: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:37.971: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:37.971: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:37.971: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.971: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:37.971: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.971: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.972: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:37.972: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:37.972: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:37.972: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:37.972: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.972: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:37.972: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.972: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.973: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:37.973: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:37.973: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:37.973: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:37.973: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.973: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:37.973: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.973: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.973: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:37.974: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:37.974: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:37.974: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:37.974: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.974: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:37.974: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.974: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.974: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:37.974: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:37.974: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:37.974: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:37.974: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.974: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:37.975: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.975: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.975: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:37.975: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:37.975: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:37.975: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:37.975: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.975: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:37.976: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.976: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.976: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:37.976: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:37.976: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:37.976: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:37.976: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.976: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:37.977: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.977: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.977: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:37.977: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:37.977: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:37.977: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:37.977: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.977: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:37.978: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.978: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.978: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:37.978: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:37.978: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:37.978: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:37.978: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.978: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:37.979: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.979: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.979: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:37.979: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:37.979: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:37.979: [vfs7552] CAPTURE_NUM_STATES entering state 2 429s (process:2292): libfprint-SSM-DEBUG: 00:54:37.979: [vfs7552] REQUEST CHUNK entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.979: Sending vfs7552_read_image_chunk 429s (process:2292): libfprint-SSM-DEBUG: 00:54:37.979: [vfs7552] REQUEST CHUNK completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:37.979: [vfs7552] CAPTURE_NUM_STATES entering state 3 429s (process:2292): libfprint-SSM-DEBUG: 00:54:37.980: [vfs7552] CAPTURE_NUM_STATES entering state 2 429s (process:2292): libfprint-SSM-DEBUG: 00:54:37.980: [vfs7552] REQUEST CHUNK entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.980: Sending vfs7552_read_image_chunk 429s (process:2292): libfprint-SSM-DEBUG: 00:54:37.980: [vfs7552] REQUEST CHUNK completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:37.980: [vfs7552] CAPTURE_NUM_STATES entering state 3 429s (process:2292): libfprint-SSM-DEBUG: 00:54:37.981: [vfs7552] CAPTURE_NUM_STATES entering state 2 429s (process:2292): libfprint-SSM-DEBUG: 00:54:37.981: [vfs7552] REQUEST CHUNK entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.981: Sending vfs7552_read_image_chunk 429s (process:2292): libfprint-SSM-DEBUG: 00:54:37.981: [vfs7552] REQUEST CHUNK completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:37.981: [vfs7552] CAPTURE_NUM_STATES entering state 3 429s (process:2292): libfprint-SSM-DEBUG: 00:54:37.982: [vfs7552] CAPTURE_NUM_STATES entering state 4 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.982: variance_before = 396 429s 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.982: background stored 429s (process:2292): libfprint-SSM-DEBUG: 00:54:37.982: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:37.982: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.982: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:37.982: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.982: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.983: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:37.983: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:37.983: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:37.983: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:37.983: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.983: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:37.983: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.983: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.984: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:37.984: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:37.984: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:37.984: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:37.984: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.984: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:37.984: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.984: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.985: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:37.985: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:37.985: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:37.985: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:37.985: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.985: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:37.985: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.985: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.985: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:37.985: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:37.985: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:37.985: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:37.985: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.985: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:37.986: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.986: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.986: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:37.986: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:37.986: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:37.986: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:37.986: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.986: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:37.987: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.987: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.987: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:37.987: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:37.987: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:37.987: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:37.987: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.987: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:37.987: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.987: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.988: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:37.988: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:37.988: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:37.988: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:37.988: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.988: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:37.988: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.988: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.989: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:37.989: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:37.989: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:37.989: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:37.989: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.989: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:37.989: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.989: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.990: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:37.990: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:37.990: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:37.990: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:37.990: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.990: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:37.990: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.990: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.991: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:37.991: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:37.991: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:37.991: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:37.991: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.991: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:37.991: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.991: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.991: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:37.991: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:37.991: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:37.991: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:37.991: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.991: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:37.992: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.992: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.992: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:37.992: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:37.992: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:37.992: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:37.992: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.992: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:37.993: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.993: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.993: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:37.993: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:37.993: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:37.993: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:37.993: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.993: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:37.993: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.993: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.994: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:37.994: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:37.994: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:37.994: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:37.994: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.994: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:37.994: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.994: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.995: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:37.995: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:37.995: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:37.995: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:37.995: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.995: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:37.995: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.995: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.996: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:37.996: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:37.996: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:37.996: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:37.996: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.996: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:37.996: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.996: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.996: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:37.996: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:37.996: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:37.996: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:37.996: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.996: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:37.997: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.997: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.997: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:37.997: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:37.997: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:37.997: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:37.997: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.997: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:37.998: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.998: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.998: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:37.998: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:37.998: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:37.998: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:37.998: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.998: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:37.999: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.999: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.999: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:37.999: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:37.999: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:37.999: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:37.999: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:37.999: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:37.999: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.000: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.000: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.000: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.000: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.000: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.000: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.000: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.000: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.000: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.001: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.001: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.001: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.001: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.001: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.001: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.001: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.001: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.002: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.002: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.002: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.002: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.002: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.002: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.002: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.002: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.002: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.002: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.002: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.002: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.002: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.002: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.003: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.003: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.003: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.003: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.003: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.003: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.003: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.003: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.004: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.004: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.004: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.004: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.004: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.004: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.004: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.004: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.005: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.005: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.005: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.005: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.005: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.005: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.005: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.005: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.005: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.005: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.006: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.006: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.006: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.006: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.006: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.006: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.006: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.006: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.007: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.007: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.007: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.007: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.007: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.007: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.007: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.007: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.007: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.007: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.007: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.007: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.007: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.007: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.008: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.008: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.008: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.008: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.008: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.008: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.008: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.008: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.009: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.009: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.009: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.009: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.009: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.009: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.009: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.009: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.009: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.009: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.010: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.010: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.010: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.010: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.010: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.010: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.010: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.010: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.011: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.011: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.011: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.011: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.011: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.011: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.011: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.011: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.012: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.012: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.012: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.012: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.012: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.012: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.012: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.012: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.012: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.012: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.012: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.012: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.012: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.012: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.013: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.013: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.013: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.013: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.013: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.013: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.013: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.013: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.014: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.014: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.014: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.014: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.014: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.014: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.014: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.014: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.014: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.015: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.015: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.015: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.015: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.015: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.015: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.015: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.015: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.015: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.016: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.016: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.016: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.016: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.016: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.016: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.016: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.016: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.017: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.017: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.017: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.017: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.017: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.017: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.017: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.017: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.017: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.017: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.017: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.017: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.018: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.018: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.018: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.018: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.018: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.018: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.018: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.018: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.018: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.018: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.019: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.019: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.019: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.019: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.019: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.019: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.019: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.019: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.020: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.020: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.020: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.020: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.020: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.020: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.020: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.020: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.020: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.020: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.021: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.021: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.021: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.021: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.021: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.021: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.021: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.021: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.022: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.022: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.022: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.022: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.022: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.022: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.022: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.022: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.022: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.022: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.022: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.023: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.023: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.023: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.023: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.023: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.023: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.023: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.023: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.023: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.023: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.023: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.024: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.024: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.025: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.025: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.025: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.025: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.025: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.025: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.025: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.025: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.026: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.026: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.026: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.026: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.026: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.026: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.026: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.026: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.027: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.027: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.027: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.027: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.027: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.027: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.027: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.027: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.028: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.028: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.028: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.028: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.028: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.028: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.028: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.028: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.028: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.028: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.028: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.028: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.028: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.028: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.029: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.029: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.029: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.029: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.029: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.029: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.029: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.029: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.030: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.030: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.030: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.030: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.030: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.030: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.030: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.030: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.031: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.031: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.031: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.031: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.031: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.031: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.031: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.031: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.031: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.031: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.032: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.032: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.032: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.032: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.032: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.032: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.032: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.032: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.033: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.033: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.033: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.033: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.033: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.033: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.033: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.033: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.034: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.034: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.034: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.034: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.034: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.034: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.034: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.034: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.035: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.035: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.035: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.035: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.035: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.035: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.035: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.035: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.035: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.035: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.035: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.035: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.035: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.035: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.036: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.036: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.036: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.036: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.036: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.036: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.036: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.036: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.037: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.037: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.037: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.037: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.037: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.037: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.037: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.037: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.037: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.037: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.038: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.038: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.038: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.038: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.038: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.038: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.038: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.038: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.039: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.039: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.039: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.039: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.039: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.039: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.039: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.039: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.040: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.040: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.040: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.040: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.040: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.040: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.040: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.040: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.040: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.040: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.040: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.040: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.041: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.041: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.041: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.041: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.041: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.041: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.041: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.041: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.041: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.041: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.042: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.042: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.042: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.042: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.042: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.042: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.042: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.042: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.043: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.043: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.043: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.043: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.043: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.043: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.043: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.043: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.043: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.043: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.044: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.044: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.044: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.044: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.044: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.044: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.044: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.044: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.045: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.045: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.045: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.045: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.045: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.045: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.045: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.045: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.046: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.046: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.046: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.046: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.046: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.046: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.046: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.046: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.046: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.046: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.046: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.046: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.046: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.046: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.047: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.047: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.047: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.047: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.047: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.047: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.047: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.047: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.048: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.048: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.048: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.048: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.048: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.048: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.048: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.048: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.048: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.048: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.049: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.049: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.049: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.049: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.049: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.049: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.049: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.049: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.050: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.050: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.050: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.050: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.050: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.050: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.050: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.050: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.050: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.051: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.051: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.051: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.051: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.051: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.051: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.051: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.051: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.051: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.051: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.051: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.051: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.051: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.052: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.052: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.052: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.052: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.052: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.052: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.052: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.052: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.053: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.053: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.053: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.053: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.053: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.053: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.053: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.053: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.053: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.053: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.054: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.054: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.054: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.054: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.054: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.054: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.054: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.054: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.055: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.055: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.055: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.055: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.055: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.055: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.055: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.055: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.056: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.056: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.056: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.056: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.056: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.056: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.056: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.056: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.057: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.057: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.057: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.057: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.057: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.057: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.057: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.057: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.057: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.057: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.057: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.057: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.057: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.057: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.058: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.058: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.058: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.058: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.058: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.058: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.058: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.058: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.059: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.059: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.059: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.059: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.059: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.059: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.059: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.059: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.059: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.059: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.060: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.060: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.060: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.060: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.060: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.060: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.060: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.060: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.061: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.061: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.061: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.061: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.061: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.061: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.061: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.061: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.061: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.061: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.062: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.062: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.062: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.062: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.062: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.062: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.062: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.062: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.062: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.062: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.062: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.062: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.063: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.063: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.063: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.063: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.063: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.063: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.063: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.063: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.064: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.064: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.064: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.064: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.064: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.064: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.064: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.064: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.064: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.064: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.065: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.065: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.065: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.065: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.065: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.065: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.065: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.065: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.066: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.066: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.066: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.066: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.066: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.066: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.066: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.066: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.066: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.066: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.066: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.066: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.066: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.066: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.067: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.067: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.067: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.067: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.067: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.067: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.067: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.067: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.068: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.068: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.068: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.068: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.068: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.068: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.068: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.068: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.069: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.069: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.069: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.069: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.069: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.069: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.069: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.069: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.070: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.070: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.070: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.070: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.070: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.070: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.070: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.070: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.070: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.070: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.071: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.071: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.071: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.071: [vfs7552] CAPTURE_NUM_STATES entering state 2 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.071: [vfs7552] REQUEST CHUNK entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.071: Sending vfs7552_read_image_chunk 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.072: [vfs7552] REQUEST CHUNK completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.073: [vfs7552] CAPTURE_NUM_STATES entering state 3 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.073: [vfs7552] CAPTURE_NUM_STATES entering state 2 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.073: [vfs7552] REQUEST CHUNK entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.073: Sending vfs7552_read_image_chunk 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.073: [vfs7552] REQUEST CHUNK completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.073: [vfs7552] CAPTURE_NUM_STATES entering state 3 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.074: [vfs7552] CAPTURE_NUM_STATES entering state 2 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.074: [vfs7552] REQUEST CHUNK entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.074: Sending vfs7552_read_image_chunk 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.074: [vfs7552] REQUEST CHUNK completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.074: [vfs7552] CAPTURE_NUM_STATES entering state 3 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.075: [vfs7552] CAPTURE_NUM_STATES entering state 4 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.075: Cleaning image 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.075: variance_after = 20 429s 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.075: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.075: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.075: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.075: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.075: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.076: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.076: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.076: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.076: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.076: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.076: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.076: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.076: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.077: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.077: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.077: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.077: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.077: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.077: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.077: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.077: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.078: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.078: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.078: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.078: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.078: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.078: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.078: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.078: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.079: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.079: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.079: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.079: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.079: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.079: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.079: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.079: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.080: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.080: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.080: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.080: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.080: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.080: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.080: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.080: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.080: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.080: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.080: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.080: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.080: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.080: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.081: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.081: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.081: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.081: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.081: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.081: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.081: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.081: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.082: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.082: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.082: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.082: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.082: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.082: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.082: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.082: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.082: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.082: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.083: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.083: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.083: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.083: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.083: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.083: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.083: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.083: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.084: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.084: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.084: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.084: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.084: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.084: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.084: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.084: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.084: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.084: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.084: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.084: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.084: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.084: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.085: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.085: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.085: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.085: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.085: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.085: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.085: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.085: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.086: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.086: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.086: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.086: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.086: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.086: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.086: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.086: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.086: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.086: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.087: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.087: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.087: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.087: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.087: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.087: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.087: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.087: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.088: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.088: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.088: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.088: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.088: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.088: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.088: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.088: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.089: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.089: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.089: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.089: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.089: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.089: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.089: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.089: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.089: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.089: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.089: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.089: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.089: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.089: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.090: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.090: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.090: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.090: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.090: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.090: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.090: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.090: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.091: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.091: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.091: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.091: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.091: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.091: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.091: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.091: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.091: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.091: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.092: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.092: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.092: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.092: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.092: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.092: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.092: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.092: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.093: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.093: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.093: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.093: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.093: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.093: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.093: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.093: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.094: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.094: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.094: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.094: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.094: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.094: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.094: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.094: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.094: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.094: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.094: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.094: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.094: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.094: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.095: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.095: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.095: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.095: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.095: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.095: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.095: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.095: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.096: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.096: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.096: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.096: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.096: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.096: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.096: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.096: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.097: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.097: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.097: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.097: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.097: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.097: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.097: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.097: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.097: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.097: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.098: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.098: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.098: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.098: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.098: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.098: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.098: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.098: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.099: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.099: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.099: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.099: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.099: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.099: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.099: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.099: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.099: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.099: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.099: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.099: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.099: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.099: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.100: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.100: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.100: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.100: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.100: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.100: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.100: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.100: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.101: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.101: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.101: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.101: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.101: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.101: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.101: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.101: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.102: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.102: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.102: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.102: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.102: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.102: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.102: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.102: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.102: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.102: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.103: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.103: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.103: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.103: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.103: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.103: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.103: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.103: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.104: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.104: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.104: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.104: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.104: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.104: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.104: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.104: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.105: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.105: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.105: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.105: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.105: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.105: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.105: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.105: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.105: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.105: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.105: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.105: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.105: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.105: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.106: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.106: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.106: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.106: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.106: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.106: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.106: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.106: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.107: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.107: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.107: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.107: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.107: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.107: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.107: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.107: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.108: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.108: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.108: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.108: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.108: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.108: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.108: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.108: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.108: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.108: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.109: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.109: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.109: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.109: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.109: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.109: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.109: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.109: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.110: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.110: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.110: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.110: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.110: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.110: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.110: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.110: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.111: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.111: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.111: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.111: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.111: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.111: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.111: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.111: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.112: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.112: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.112: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.112: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.112: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.112: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.112: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.112: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.113: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.113: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.113: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.113: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.113: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.113: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.113: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.113: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.113: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.113: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.113: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.113: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.113: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.113: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.114: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.114: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.114: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.114: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.114: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.114: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.114: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.114: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.115: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.115: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.115: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.115: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.115: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.115: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.115: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.115: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.116: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.116: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.116: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.116: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.116: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.116: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.116: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.116: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.116: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.116: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.117: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.117: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.117: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.117: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.117: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.117: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.117: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.117: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.118: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.118: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.118: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.118: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.118: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.118: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.118: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.118: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.119: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.119: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.119: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.119: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.119: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.119: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.119: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.119: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.119: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.119: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.119: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.119: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.119: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.119: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.120: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.120: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.120: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.120: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.120: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.120: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.120: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.120: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.121: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.121: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.121: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.121: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.121: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.121: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.121: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.121: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.121: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.121: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.122: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.122: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.122: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.122: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.122: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.122: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.122: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.122: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.123: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.123: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.123: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.123: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.123: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.123: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.123: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.123: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.123: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.123: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.123: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.123: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.123: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.123: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.124: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.124: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.124: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.124: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.124: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.124: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.124: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.124: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.125: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.125: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.125: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.125: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.125: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.125: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.125: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.125: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.125: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.125: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.126: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.126: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.126: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.126: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.126: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.126: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.126: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.126: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.127: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.127: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.127: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.127: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.127: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.127: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.127: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.127: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.128: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.128: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.128: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.128: [vfs7552] CAPTURE_NUM_STATES entering state 2 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.128: [vfs7552] REQUEST CHUNK entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.128: Sending vfs7552_read_image_chunk 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.128: [vfs7552] REQUEST CHUNK completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.128: [vfs7552] CAPTURE_NUM_STATES entering state 3 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.128: [vfs7552] CAPTURE_NUM_STATES entering state 2 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.128: [vfs7552] REQUEST CHUNK entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.128: Sending vfs7552_read_image_chunk 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.129: [vfs7552] REQUEST CHUNK completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.129: [vfs7552] CAPTURE_NUM_STATES entering state 3 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.129: [vfs7552] CAPTURE_NUM_STATES entering state 2 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.129: [vfs7552] REQUEST CHUNK entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.129: Sending vfs7552_read_image_chunk 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.130: [vfs7552] REQUEST CHUNK completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.130: [vfs7552] CAPTURE_NUM_STATES entering state 3 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.130: [vfs7552] CAPTURE_NUM_STATES entering state 4 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.130: Cleaning image 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.130: variance_after = 18 429s 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.130: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.130: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.130: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.131: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.131: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.131: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.131: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.131: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.131: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.131: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.131: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.131: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.131: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.132: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.132: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.132: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.132: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.132: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.132: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.132: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.132: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.133: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.133: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.133: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.133: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.133: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.133: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.133: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.133: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.134: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.134: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.134: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.134: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.134: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.134: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.134: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.134: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.134: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.134: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.134: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.134: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.134: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.134: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.135: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.135: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.135: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.135: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.135: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.135: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.135: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.135: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.136: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.136: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.136: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.136: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.136: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.136: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.136: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.136: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.136: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.137: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.137: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.137: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.137: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.137: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.137: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.137: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.137: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.137: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.138: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.138: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.138: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.138: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.138: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.138: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.138: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.138: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.139: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.139: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.139: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.139: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.139: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.139: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.139: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.139: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.139: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.139: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.139: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.139: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.139: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.139: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.140: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.140: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.140: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.140: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.140: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.140: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.140: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.140: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.141: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.141: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.141: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.141: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.141: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.141: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.141: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.141: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.142: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.142: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.142: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.142: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.142: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.142: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.142: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.142: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.143: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.143: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.143: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.143: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.143: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.143: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.143: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.143: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.143: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.143: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.144: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.144: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.144: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.144: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.144: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.144: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.144: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.144: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.145: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.145: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.145: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.145: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.145: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.145: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.145: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.145: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.145: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.145: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.145: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.145: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.145: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.145: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.146: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.146: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.146: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.146: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.146: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.146: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.146: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.146: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.147: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.147: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.147: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.147: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.147: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.147: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.147: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.147: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.148: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.148: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.148: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.148: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.148: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.148: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.148: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.148: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.148: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.148: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.149: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.149: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.149: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.149: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.149: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.149: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.149: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.149: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.150: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.150: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.150: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.150: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.150: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.150: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.150: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.150: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.151: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.151: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.151: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.151: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.151: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.151: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.151: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.151: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.151: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.151: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.151: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.151: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.151: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.151: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.152: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.152: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.152: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.152: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.152: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.152: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.152: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.152: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.153: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.153: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.153: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.153: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.153: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.153: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.153: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.153: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.153: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.153: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.154: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.154: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.154: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.154: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.154: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.154: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.155: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.155: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.155: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.155: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.155: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.155: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.155: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.155: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.156: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.156: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.156: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.156: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.156: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.156: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.156: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.156: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.156: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.156: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.157: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.157: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.157: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.157: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.157: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.157: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.157: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.157: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.158: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.158: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.158: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.158: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.158: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.158: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.158: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.158: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.159: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.159: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.159: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.159: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.159: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.159: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.159: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.159: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.159: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.159: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.159: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.159: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.159: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.159: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.160: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.160: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.160: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.160: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.160: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.160: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.160: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.160: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.161: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.161: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.161: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.161: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.161: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.161: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.161: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.161: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.161: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.161: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.162: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.162: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.162: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.162: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.162: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.162: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.162: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.162: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.163: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.163: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.163: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.163: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.163: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.163: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.163: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.163: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.164: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.164: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.164: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.164: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.164: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.164: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.164: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.164: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.165: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.165: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.165: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.165: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.165: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.165: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.165: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.165: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.165: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.165: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.165: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.165: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.165: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.165: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.166: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.166: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.166: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.166: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.166: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.166: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.166: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.166: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.167: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.167: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.167: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.167: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.167: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.167: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.167: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.167: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.167: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.167: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.168: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.168: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.168: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.168: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.168: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.168: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.168: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.168: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.169: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.169: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.169: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.169: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.169: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.169: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.169: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.169: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.170: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.170: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.170: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.170: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.170: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.170: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.170: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.170: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.170: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.170: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.170: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.170: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.170: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.170: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.171: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.171: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.171: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.171: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.171: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.171: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.171: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.171: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.172: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.172: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.172: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.172: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.172: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.172: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.172: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.172: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.172: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.172: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.173: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.173: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.173: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.173: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.173: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.173: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.173: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.173: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.174: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.174: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.174: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.174: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.174: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.174: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.174: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.174: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.175: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.175: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.175: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.175: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.175: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.175: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.175: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.175: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.175: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.175: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.175: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.175: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.175: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.175: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.176: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.176: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.176: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.176: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.176: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.176: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.176: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.176: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.177: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.177: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.177: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.177: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.177: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.177: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.177: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.177: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.177: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.177: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.178: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.178: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.178: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.178: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.178: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.178: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.178: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.178: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.179: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.179: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.179: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.179: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.179: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.179: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.179: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.179: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.180: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.180: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.180: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.180: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.180: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.180: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.180: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.180: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.180: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.180: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.180: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.180: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.180: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.180: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.181: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.181: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.181: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.181: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.181: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.181: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.181: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.181: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.182: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.182: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.182: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.182: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.182: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.182: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.182: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.182: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.182: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.182: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.183: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.183: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.183: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.183: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.183: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.183: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.183: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.183: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.184: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.184: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.184: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.184: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.184: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.184: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.184: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.184: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.185: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.185: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.185: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.185: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.185: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.185: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.185: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.185: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.186: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.186: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.186: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.186: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.186: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.186: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.186: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.186: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.187: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.187: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.187: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.187: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.187: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.187: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.187: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.187: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.187: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.187: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.187: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.187: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.187: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.187: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.188: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.188: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.188: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.188: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.188: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.188: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.188: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.188: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.189: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.189: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.189: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.189: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.189: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.189: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.189: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.189: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.189: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.189: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.190: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.190: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.190: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.190: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.190: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.190: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.190: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.190: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.191: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.191: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.191: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.191: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.191: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.191: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.191: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.191: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.192: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.192: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.192: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.192: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.192: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.192: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.192: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.192: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.193: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.193: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.193: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.193: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.193: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.193: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.193: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.193: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.193: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.193: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.193: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.193: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.193: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.193: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.194: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.194: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.194: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.194: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.194: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.194: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.194: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.194: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.195: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.195: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.195: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.195: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.195: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.195: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.195: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.195: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.195: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.195: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.196: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.196: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.196: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.196: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.196: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.196: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.196: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.196: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.197: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.197: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.197: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.197: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.197: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.197: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.197: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.197: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.197: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.197: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.197: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.197: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.197: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.197: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.198: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.198: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.198: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.198: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.198: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.198: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.198: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.198: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.199: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.199: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.199: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.199: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.199: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.199: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.199: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.199: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.199: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.199: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.200: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.200: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.200: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.200: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.200: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.200: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.200: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.200: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.201: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.201: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.201: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.201: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.201: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.201: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.201: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.201: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.201: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.202: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.202: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.202: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.202: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.202: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.202: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.202: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.202: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.202: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.202: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.202: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.202: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.202: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.203: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.203: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.203: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.203: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.203: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.203: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.203: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.203: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.204: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.204: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.204: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.204: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.204: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.204: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.204: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.204: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.204: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.204: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.205: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.205: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.205: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.205: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.205: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.205: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.205: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.205: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.206: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.206: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.206: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.206: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.206: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.206: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.206: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.206: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.206: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.206: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.206: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.206: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.206: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.206: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.207: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.207: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.207: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.207: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.207: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.207: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.207: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.207: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.208: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.208: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.208: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.208: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.208: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.208: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.208: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.208: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.209: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.209: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.209: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.209: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.209: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.209: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.209: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.209: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.209: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.209: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.210: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.210: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.210: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.210: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.210: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.210: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.210: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.210: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.211: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.211: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.211: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.211: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.211: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.211: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.211: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.211: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.212: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.212: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.212: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.212: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.212: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.212: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.212: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.212: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.212: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.212: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.212: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.212: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.212: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.212: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.213: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.213: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.213: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.213: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.213: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.213: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.213: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.213: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.214: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.214: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.214: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.214: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.214: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.214: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.214: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.214: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.215: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.215: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.215: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.215: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.215: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.215: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.215: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.215: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.215: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.215: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.216: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.216: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.216: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.216: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.216: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.216: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.216: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.216: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.217: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.217: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.217: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.217: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.217: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.217: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.217: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.217: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.218: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.218: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.218: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.218: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.218: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.218: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.218: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.218: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.219: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.219: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.219: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.219: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.219: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.219: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.219: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.219: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.219: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.219: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.219: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.219: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.219: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.219: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.220: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.220: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.220: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.220: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.220: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.220: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.220: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.220: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.221: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.221: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.221: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.221: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.221: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.221: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.221: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.221: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.221: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.221: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.222: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.222: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.222: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.222: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.222: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.222: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.222: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.222: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.223: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.223: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.223: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.223: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.223: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.223: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.223: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.223: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.224: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.224: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.224: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.224: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.224: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.224: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.224: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.224: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.225: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.225: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.225: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.225: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.225: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.225: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.225: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.225: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.225: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.225: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.225: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.225: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.225: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.225: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.226: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.226: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.226: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.226: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.226: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.226: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.226: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.226: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.227: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.227: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.227: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.227: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.227: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.227: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.227: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.227: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.227: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.227: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.228: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.228: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.228: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.228: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.228: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.228: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.228: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.228: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.229: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.229: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.229: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.229: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.229: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.229: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.229: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.229: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.229: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.229: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.229: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.229: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.229: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.229: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.230: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.230: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.230: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.230: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.230: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.230: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.230: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.230: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.231: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.231: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.231: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.231: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.231: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.231: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.231: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.231: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.232: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.232: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.232: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.232: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.232: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.232: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.232: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.232: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.233: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.233: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.233: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.233: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.233: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.233: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.233: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.233: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.234: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.234: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.234: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.234: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.234: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.234: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.234: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.234: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.235: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.235: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.235: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.235: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.235: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.235: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.235: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.235: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.236: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.236: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.236: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.236: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.236: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.236: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.236: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.236: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.237: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.237: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.237: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.237: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.237: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.237: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.237: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.237: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.238: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.238: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.238: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.238: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.238: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.238: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.238: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.238: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.239: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.239: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.239: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.239: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.239: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.239: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.239: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.239: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.240: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.240: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.240: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.240: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.240: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.240: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.240: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.240: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.241: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.241: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.241: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.241: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.241: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.241: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.241: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.241: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.241: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.242: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.242: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.242: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.242: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.242: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.242: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.242: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.243: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.243: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.243: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.243: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.243: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.243: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.243: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.243: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.244: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.244: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.244: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.244: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.244: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.244: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.244: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.244: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.245: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.245: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.245: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.245: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.245: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.245: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.245: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.245: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.245: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.245: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.246: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.246: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.246: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.246: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.246: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.246: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.246: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.246: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.247: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.247: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.247: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.247: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.247: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.247: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.247: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.247: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.248: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.248: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.248: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.248: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.248: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.248: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.248: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.248: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.248: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.248: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.248: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.248: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.248: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.248: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.249: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.249: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.249: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.249: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.249: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.249: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.249: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.249: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.250: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.250: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.250: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.250: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.250: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.250: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.250: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.250: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.251: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.251: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.251: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.251: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.251: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.251: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.251: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.251: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.252: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.252: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.252: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.252: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.252: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.252: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.252: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.252: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.253: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.253: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.253: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.253: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.253: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.253: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.253: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.253: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.254: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.254: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.254: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.254: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.254: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.254: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.254: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.254: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.255: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.255: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.255: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.255: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.255: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.255: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.255: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.255: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.256: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.256: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.256: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.256: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.256: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.256: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.256: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.256: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.257: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.257: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.257: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.257: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.257: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.257: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.257: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.257: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.258: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.258: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.258: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.258: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.258: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.258: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.258: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.258: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.258: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.258: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.259: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.259: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.259: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.259: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.259: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.259: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.259: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.259: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.260: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.260: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.260: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.260: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.260: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.260: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.260: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.260: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.261: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.261: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.261: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.261: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.261: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.261: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.261: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.261: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.262: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.262: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.262: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.262: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.262: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.262: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.262: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.262: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.263: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.263: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.263: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.263: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.263: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.263: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.263: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.263: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.263: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.264: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.264: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.264: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.264: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.264: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.264: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.264: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.264: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.264: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.264: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.264: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.264: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.264: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.265: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.265: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.265: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.265: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.265: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.265: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.265: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.265: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.266: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.266: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.266: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.266: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.266: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.266: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.266: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.266: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.267: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.267: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.267: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.267: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.267: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.267: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.267: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.267: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.268: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.268: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.268: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.268: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.268: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.268: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.268: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.268: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.269: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.269: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.269: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.269: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.269: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.269: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.269: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.269: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.270: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.270: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.270: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.270: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.270: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.270: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.270: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.270: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.271: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.271: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.271: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.271: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.271: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.271: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.271: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.271: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.271: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.271: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.272: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.272: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.272: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.272: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.272: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.272: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.272: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.272: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.273: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.273: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.273: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.273: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.273: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.273: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.273: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.273: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.274: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.274: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.274: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.274: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.274: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.274: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.274: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.274: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.275: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.275: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.275: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.275: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.275: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.275: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.275: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.275: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.276: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.276: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.276: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.276: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.276: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.276: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.276: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.276: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.277: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.277: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.277: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.277: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.277: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.277: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.277: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.277: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.277: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.277: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.277: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.277: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.277: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.277: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.278: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.278: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.279: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.279: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.279: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.279: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.279: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.279: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.280: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.280: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.280: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.280: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.280: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.280: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.280: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.280: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.281: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.281: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.281: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.281: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.281: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.281: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.281: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.281: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.281: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.281: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.282: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.282: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.282: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.282: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.282: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.282: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.282: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.282: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.283: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.283: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.283: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.283: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.283: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.283: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.283: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.283: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.284: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.284: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.284: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.284: [vfs7552] CAPTURE_NUM_STATES entering state 2 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.284: [vfs7552] REQUEST CHUNK entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.284: Sending vfs7552_read_image_chunk 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.284: [vfs7552] REQUEST CHUNK completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.284: [vfs7552] CAPTURE_NUM_STATES entering state 3 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.285: [vfs7552] CAPTURE_NUM_STATES entering state 2 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.285: [vfs7552] REQUEST CHUNK entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.285: Sending vfs7552_read_image_chunk 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.285: [vfs7552] REQUEST CHUNK completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.285: [vfs7552] CAPTURE_NUM_STATES entering state 3 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.286: [vfs7552] CAPTURE_NUM_STATES entering state 2 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.286: [vfs7552] REQUEST CHUNK entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.286: Sending vfs7552_read_image_chunk 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.286: [vfs7552] REQUEST CHUNK completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.286: [vfs7552] CAPTURE_NUM_STATES entering state 3 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.286: [vfs7552] CAPTURE_NUM_STATES entering state 4 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.286: Cleaning image 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.287: variance_after = 20 429s 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.287: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.287: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.287: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.287: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.287: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.287: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.287: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.287: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.288: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.288: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.288: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.288: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.288: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.289: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.289: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.289: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.289: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.289: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.289: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.289: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.289: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.290: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.290: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.290: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.290: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.290: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.290: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.290: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.290: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.291: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.291: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.291: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.291: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.291: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.291: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.291: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.291: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.292: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.292: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.292: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.292: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.292: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.292: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.292: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.292: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.293: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.293: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.293: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.293: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.293: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.293: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.293: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.293: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.293: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.293: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.293: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.293: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.293: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.293: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.294: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.294: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.294: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.294: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.294: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.294: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.294: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.294: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.295: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.295: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.295: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.295: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.295: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.295: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.295: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.295: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.296: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.296: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.296: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.296: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.296: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.296: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.296: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.296: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.297: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.297: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.297: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.297: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.297: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.297: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.297: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.297: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.298: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.298: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.298: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.298: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.298: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.298: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.298: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.298: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.298: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.298: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.299: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.299: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.299: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.299: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.299: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.299: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.299: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.299: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.300: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.300: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.300: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.300: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.300: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.300: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.300: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.300: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.301: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.301: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.301: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.301: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.301: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.301: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.301: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.301: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.302: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.302: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.302: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.302: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.302: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.302: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.302: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.302: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.303: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.303: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.303: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.303: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.303: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.303: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.303: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.303: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.304: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.304: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.304: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.304: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.304: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.304: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.304: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.304: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.305: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.305: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.305: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.305: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.305: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.305: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.305: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.305: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.306: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.306: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.306: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.306: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.306: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.306: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.306: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.306: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.307: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.307: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.307: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.307: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.307: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.307: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.307: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.307: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.308: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.308: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.308: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.308: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.308: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.308: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.308: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.308: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.309: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.309: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.309: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.309: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.309: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.309: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.309: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.309: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.310: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.310: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.310: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.310: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.310: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.310: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.310: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.310: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.310: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.310: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.310: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.310: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.311: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.311: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.311: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.311: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.311: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.311: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.312: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.312: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.312: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.312: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.312: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.312: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.313: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.313: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.313: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.313: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.313: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.313: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.313: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.313: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.313: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.313: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.313: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.313: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.313: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.313: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.314: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.314: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.314: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.314: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.314: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.314: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.314: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.314: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.315: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.315: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.315: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.315: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.315: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.315: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.315: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.315: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.316: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.316: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.316: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.316: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.316: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.316: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.316: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.316: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.317: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.317: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.317: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.317: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.317: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.317: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.317: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.317: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.317: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.317: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.318: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.318: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.318: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.318: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.318: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.318: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.318: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.318: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.319: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.319: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.319: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.319: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.319: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.319: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.319: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.319: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.320: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.320: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.320: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.320: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.320: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.320: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.320: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.320: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.321: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.321: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.321: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.321: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.321: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.321: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.321: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.321: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.321: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.321: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.321: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.321: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.321: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.321: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.323: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.323: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.324: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.324: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.324: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.324: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.324: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.324: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.324: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.324: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.325: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.325: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.325: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.325: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.325: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.325: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.325: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.325: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.326: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.326: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.326: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.326: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.326: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.326: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.326: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.326: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.326: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.326: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.326: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.327: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.327: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.327: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.327: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.327: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.327: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.327: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.327: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.327: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.327: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.327: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.328: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.328: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.328: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.328: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.328: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.328: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.328: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.328: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.329: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.329: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.329: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.329: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.329: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.329: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.329: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.329: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.330: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.330: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.330: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.330: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.330: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.330: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.330: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.330: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.331: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.331: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.331: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.331: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.331: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.331: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.331: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.331: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.332: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.332: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.332: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.332: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.332: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.332: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.332: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.332: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.333: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.333: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.333: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.333: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.333: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.333: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.333: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.333: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.333: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.333: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.334: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.334: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.334: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.334: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.334: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.334: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.334: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.334: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.335: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.335: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.335: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.335: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.335: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.335: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.335: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.335: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.336: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.336: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.336: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.336: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.336: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.336: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.336: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.336: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.337: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.337: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.337: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.337: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.337: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.337: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.337: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.337: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.337: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.337: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.337: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.337: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.337: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.337: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.338: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.338: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.338: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.338: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.338: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.338: [vfs7552] CAPTURE_NUM_STATES entering state 2 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.338: [vfs7552] REQUEST CHUNK entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.338: Sending vfs7552_read_image_chunk 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.339: [vfs7552] REQUEST CHUNK completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.339: [vfs7552] CAPTURE_NUM_STATES entering state 3 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.339: [vfs7552] CAPTURE_NUM_STATES entering state 2 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.339: [vfs7552] REQUEST CHUNK entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.339: Sending vfs7552_read_image_chunk 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.340: [vfs7552] REQUEST CHUNK completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.340: [vfs7552] CAPTURE_NUM_STATES entering state 3 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.340: [vfs7552] CAPTURE_NUM_STATES entering state 2 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.341: [vfs7552] REQUEST CHUNK entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.341: Sending vfs7552_read_image_chunk 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.341: [vfs7552] REQUEST CHUNK completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.341: [vfs7552] CAPTURE_NUM_STATES entering state 3 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.342: [vfs7552] CAPTURE_NUM_STATES entering state 4 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.342: Cleaning image 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.342: variance_after = 18 429s 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.342: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.342: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.342: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.342: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.342: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.342: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.342: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.342: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.342: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.342: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.342: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.343: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.343: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.343: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.343: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.343: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.343: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.343: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.343: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.344: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.344: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.344: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.344: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.344: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.344: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.344: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.344: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.345: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.345: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.345: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.345: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.345: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.345: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.345: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.345: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.346: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.346: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.346: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.346: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.346: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.346: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.346: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.346: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.347: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.347: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.347: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.347: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.347: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.347: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.347: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.347: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.348: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.348: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.348: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.348: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.348: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.348: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.348: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.348: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.348: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.348: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.349: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.349: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.349: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.349: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.349: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.349: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.349: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.349: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.350: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.350: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.350: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.350: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.350: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.350: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.350: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.350: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.351: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.351: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.351: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.351: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.351: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.351: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.351: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.351: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.351: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.351: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.351: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.351: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.351: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.351: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.352: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.352: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.352: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.352: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.352: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.352: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.352: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.352: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.353: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.353: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.353: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.353: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.353: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.353: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.353: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.353: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.354: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.354: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.354: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.354: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.354: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.354: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.354: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.354: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.355: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.355: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.355: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.355: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.355: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.355: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.355: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.355: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.355: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.355: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.356: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.356: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.356: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.356: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.356: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.356: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.356: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.356: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.357: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.357: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.357: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.357: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.357: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.357: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.357: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.357: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.357: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.357: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.357: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.357: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.357: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.357: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.358: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.358: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.358: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.358: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.358: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.358: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.358: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.358: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.359: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.359: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.359: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.359: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.359: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.359: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.359: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.359: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.359: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.359: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.360: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.360: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.360: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.360: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.360: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.360: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.360: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.360: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.361: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.361: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.361: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.361: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.361: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.361: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.361: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.361: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.362: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.362: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.362: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.362: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.362: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.362: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.362: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.362: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.362: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.362: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.362: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.362: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.362: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.362: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.363: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.363: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.363: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.363: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.363: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.363: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.363: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.363: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.364: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.364: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.364: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.364: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.364: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.364: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.364: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.364: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.365: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.365: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.365: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.365: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.365: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.365: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.365: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.365: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.365: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.365: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.366: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.366: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.366: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.366: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.366: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.366: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.366: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.366: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.367: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.367: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.367: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.367: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.367: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.367: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.367: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.367: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.368: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.368: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.368: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.368: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.368: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.368: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.368: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.368: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.368: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.368: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.368: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.368: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.368: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.368: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.369: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.369: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.369: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.369: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.369: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.369: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.369: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.369: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.370: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.370: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.370: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.370: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.370: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.370: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.370: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.370: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.370: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.370: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.371: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.371: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.371: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.371: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.371: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.371: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.371: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.371: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.372: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.372: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.372: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.372: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.372: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.372: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.372: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.372: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.373: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.373: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.373: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.373: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.373: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.373: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.373: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.373: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.373: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.373: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.373: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.373: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.373: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.373: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.374: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.374: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.374: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.374: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.374: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.374: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.374: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.374: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.375: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.375: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.375: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.375: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.375: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.375: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.375: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.375: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.376: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.376: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.376: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.376: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.376: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.376: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.376: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.376: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.376: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.376: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.377: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.377: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.377: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.377: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.377: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.377: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.377: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.377: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.378: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.378: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.378: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.378: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.378: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.378: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.378: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.378: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.378: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.378: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.378: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.378: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.378: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.378: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.379: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.379: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.379: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.379: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.379: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.379: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.379: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.379: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.380: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.380: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.380: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.380: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.380: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.380: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.380: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.380: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.380: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.380: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.381: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.381: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.381: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.381: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.381: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.381: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.381: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.381: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.382: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.382: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.382: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.382: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.382: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.382: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.382: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.382: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.383: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.383: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.383: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.383: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.383: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.383: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.383: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.383: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.383: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.383: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.383: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.383: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.383: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.383: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.384: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.384: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.384: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.384: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.384: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.384: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.384: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.384: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.385: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.385: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.385: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.385: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.385: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.385: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.385: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.385: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.385: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.385: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.386: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.386: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.386: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.386: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.386: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.386: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.386: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.386: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.387: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.387: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.387: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.387: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.387: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.387: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.387: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.387: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.387: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.387: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.387: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.387: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.387: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.387: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.388: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.388: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.388: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.388: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.388: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.388: [vfs7552] CAPTURE_NUM_STATES entering state 2 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.388: [vfs7552] REQUEST CHUNK entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.388: Sending vfs7552_read_image_chunk 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.389: [vfs7552] REQUEST CHUNK completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.389: [vfs7552] CAPTURE_NUM_STATES entering state 3 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.389: [vfs7552] CAPTURE_NUM_STATES entering state 2 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.389: [vfs7552] REQUEST CHUNK entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.389: Sending vfs7552_read_image_chunk 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.390: [vfs7552] REQUEST CHUNK completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.390: [vfs7552] CAPTURE_NUM_STATES entering state 3 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.390: [vfs7552] CAPTURE_NUM_STATES entering state 2 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.390: [vfs7552] REQUEST CHUNK entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.390: Sending vfs7552_read_image_chunk 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.390: [vfs7552] REQUEST CHUNK completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.390: [vfs7552] CAPTURE_NUM_STATES entering state 3 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.391: [vfs7552] CAPTURE_NUM_STATES entering state 4 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.391: Cleaning image 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.391: variance_after = 18 429s 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.391: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.391: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.391: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.391: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.391: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.392: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.392: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.392: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.392: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.392: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.392: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.392: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.392: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.393: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.393: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.393: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.393: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.393: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.393: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.393: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.393: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.393: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.393: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.393: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.393: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.393: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.393: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.394: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.394: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.394: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.394: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.394: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.394: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.394: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.394: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.395: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.395: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.395: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.395: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.395: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.395: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.395: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.395: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.395: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.396: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.396: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.396: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.396: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.396: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.396: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.396: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.396: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.396: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.397: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.397: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.397: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.397: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.397: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.397: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.397: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.397: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.398: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.398: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.398: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.398: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.398: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.398: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.398: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.398: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.398: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.398: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.398: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.398: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.398: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.398: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.399: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.399: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.399: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.399: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.399: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.399: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.399: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.399: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.400: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.400: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.400: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.400: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.400: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.400: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.400: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.400: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.400: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.400: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.401: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.401: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.401: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.401: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.401: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.401: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.401: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.401: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.402: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.402: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.402: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.402: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.402: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.402: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.402: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.402: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.403: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.403: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.403: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.403: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.403: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.403: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.403: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.403: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.403: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.403: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.403: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.403: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.403: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.403: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.404: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.404: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.404: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.404: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.404: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.404: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.404: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.404: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.405: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.405: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.405: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.405: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.405: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.405: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.405: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.405: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.405: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.405: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.406: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.406: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.406: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.406: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.406: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.406: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.406: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.406: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.407: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.407: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.407: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.407: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.407: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.407: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.407: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.407: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.408: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.408: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.408: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.408: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.408: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.408: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.408: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.408: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.408: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.408: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.408: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.408: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.408: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.408: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.409: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.409: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.409: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.409: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.409: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.409: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.409: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.409: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.410: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.410: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.410: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.410: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.410: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.410: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.410: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.410: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.410: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.410: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.411: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.411: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.411: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.411: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.411: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.411: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.411: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.411: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.412: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.412: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.412: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.412: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.412: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.412: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.412: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.412: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.413: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.413: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.413: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.413: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.413: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.413: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.413: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.413: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.413: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.413: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.413: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.413: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.413: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.413: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.414: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.414: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.414: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.414: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.414: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.414: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.414: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.414: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.415: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.415: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.415: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.415: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.415: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.415: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.415: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.415: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.416: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.416: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.416: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.416: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.416: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.416: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.416: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.416: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.416: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.416: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.417: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.417: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.417: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.417: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.417: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.417: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.417: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.417: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.418: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.418: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.418: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.418: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.418: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.418: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.418: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.418: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.418: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.418: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.418: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.418: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.418: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.418: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.419: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.419: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.419: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.419: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.419: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.419: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.419: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.419: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.420: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.420: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.420: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.420: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.420: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.420: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.420: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.420: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.421: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.421: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.421: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.421: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.421: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.421: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.421: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.421: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.421: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.421: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.422: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.422: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.422: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.422: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.422: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.422: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.422: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.422: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.423: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.423: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.423: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.423: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.423: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.423: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.423: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.423: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.424: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.424: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.424: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.424: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.424: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.424: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.424: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.424: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.424: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.424: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.424: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.424: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.424: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.424: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.425: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.425: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.425: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.425: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.425: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.425: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.425: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.425: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.426: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.426: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.426: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.426: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.426: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.426: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.426: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.426: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.427: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.427: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.427: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.427: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.427: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.427: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.427: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.427: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.428: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.428: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.428: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.428: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.428: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.428: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.428: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.428: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.428: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.428: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.429: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.429: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.429: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.429: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.429: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.429: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.429: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.429: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.430: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.430: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.430: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.430: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.430: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.430: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.430: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.430: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.431: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.431: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.431: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.431: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.431: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.431: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.431: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.431: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.431: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.431: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.431: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.431: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.431: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.431: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.432: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.432: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.432: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.432: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.432: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.432: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.432: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.432: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.433: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.433: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.433: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.433: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.433: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.433: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.433: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.433: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.434: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.434: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.434: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.434: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.434: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.434: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.434: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.434: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.435: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.435: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.435: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.435: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.435: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.435: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.435: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.435: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.436: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.436: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.436: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.436: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.436: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.436: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.436: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.436: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.437: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.437: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.437: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.437: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.437: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.437: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.437: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.437: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.437: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.437: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.438: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.438: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.438: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.438: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.438: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.438: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.438: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.438: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.439: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.439: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.439: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.439: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.439: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.439: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.439: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.439: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.439: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.439: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.439: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.439: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.439: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.439: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.440: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.440: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.440: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.440: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.440: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.440: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.440: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.440: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.441: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.441: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.441: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.441: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.441: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.441: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.441: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.441: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.441: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.442: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.442: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.442: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.442: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.442: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.442: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.442: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.442: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.442: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.443: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.443: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.443: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.443: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.443: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.443: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.443: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.443: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.444: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.444: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.444: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.444: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.444: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.444: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.444: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.444: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.444: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.444: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.444: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.444: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.444: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.444: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.445: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.445: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.445: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.445: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.445: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.445: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.445: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.445: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.446: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.446: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.446: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.446: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.446: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.446: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.446: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.446: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.447: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.447: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.447: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.447: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.447: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.447: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.447: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.447: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.447: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.447: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.448: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.448: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.448: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.448: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.448: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.448: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.448: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.448: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.449: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.449: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.449: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.449: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.449: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.449: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.449: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.449: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.449: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.449: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.449: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.449: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.449: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.449: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.450: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.450: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.450: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.450: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.450: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.450: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.450: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.450: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.451: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.451: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.451: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.451: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.451: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.451: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.451: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.451: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.452: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.452: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.452: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.452: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.452: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.452: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.452: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.452: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.452: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.452: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.453: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.453: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.453: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.453: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.453: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.453: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.453: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.453: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.454: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.454: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.454: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.454: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.454: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.454: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.454: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.454: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.454: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.454: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.454: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.454: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.454: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.454: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.455: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.455: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.455: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.455: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.455: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.455: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.455: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.455: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.456: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.456: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.456: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.456: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.456: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.456: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.456: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.456: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.457: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.457: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.457: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.457: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.457: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.457: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.457: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.457: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.457: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.457: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.458: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.458: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.458: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.458: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.458: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.458: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.458: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.458: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.459: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.459: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.459: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.459: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.459: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.459: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.459: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.459: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.459: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.459: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.459: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.459: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.459: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.459: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.460: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.460: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.460: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.460: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.460: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.460: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.460: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.460: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.461: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.461: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.461: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.461: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.461: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.461: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.461: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.461: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.461: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.462: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.462: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.462: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.462: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.462: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.462: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.462: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.462: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.462: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.463: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.463: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.463: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.463: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.463: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.463: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.463: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.463: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.464: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.464: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.464: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.464: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.464: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.464: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.464: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.464: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.465: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.465: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.465: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.465: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.465: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.465: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.465: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.465: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.465: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.465: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.465: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.465: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.465: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.465: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.466: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.466: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.466: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.466: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.466: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.466: [vfs7552] CAPTURE_NUM_STATES entering state 2 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.466: [vfs7552] REQUEST CHUNK entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.466: Sending vfs7552_read_image_chunk 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.467: [vfs7552] REQUEST CHUNK completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.467: [vfs7552] CAPTURE_NUM_STATES entering state 3 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.467: [vfs7552] CAPTURE_NUM_STATES entering state 2 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.467: [vfs7552] REQUEST CHUNK entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.467: Sending vfs7552_read_image_chunk 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.468: [vfs7552] REQUEST CHUNK completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.468: [vfs7552] CAPTURE_NUM_STATES entering state 3 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.468: [vfs7552] CAPTURE_NUM_STATES entering state 2 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.468: [vfs7552] REQUEST CHUNK entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.468: Sending vfs7552_read_image_chunk 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.468: [vfs7552] REQUEST CHUNK completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.468: [vfs7552] CAPTURE_NUM_STATES entering state 3 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.469: [vfs7552] CAPTURE_NUM_STATES entering state 4 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.469: Cleaning image 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.469: variance_after = 18 429s 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.469: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.469: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.469: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.469: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.470: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.470: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.470: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.470: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.470: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.470: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.470: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.470: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.470: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.471: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.471: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.471: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.471: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.471: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.471: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.471: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.471: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.472: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.472: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.472: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.472: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.472: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.472: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.472: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.472: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.472: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.472: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.472: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.472: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.472: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.472: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.473: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.473: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.473: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.473: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.473: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.473: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.473: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.473: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.474: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.474: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.474: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.474: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.474: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.474: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.474: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.474: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.474: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.475: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.475: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.475: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.475: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.475: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.475: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.475: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.475: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.475: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.476: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.476: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.476: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.476: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.476: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.476: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.476: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.476: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.477: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.477: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.477: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.477: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.477: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.477: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.477: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.477: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.477: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.477: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.477: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.477: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.477: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.477: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.478: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.478: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.479: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.479: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.479: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.479: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.479: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.479: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.479: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.479: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.479: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.479: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.479: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.479: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.479: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.479: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.480: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.480: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.480: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.480: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.480: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.480: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.480: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.480: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.481: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.481: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.481: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.481: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.481: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.481: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.481: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.481: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.482: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.482: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.482: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.482: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.482: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.482: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.482: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.482: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.482: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.482: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.483: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.483: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.483: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.483: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.483: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.483: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.483: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.483: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.484: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.484: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.484: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.484: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.484: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.484: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.484: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.484: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.485: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.485: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.485: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.485: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.485: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.485: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.485: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.485: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.485: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.485: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.485: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.485: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.485: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.485: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.486: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.486: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.486: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.486: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.486: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.486: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.486: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.486: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.487: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.487: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.487: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.487: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.487: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.487: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.487: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.487: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.488: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.488: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.488: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.488: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.488: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.488: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.488: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.488: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.488: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.488: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.489: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.489: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.489: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.489: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.489: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.489: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.489: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.489: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.490: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.490: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.490: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.490: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.490: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.490: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.490: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.490: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.491: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.491: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.491: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.491: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.491: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.491: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.491: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.491: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.491: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.491: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.491: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.491: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.491: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.491: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.492: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.492: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.492: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.492: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.492: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.492: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.492: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.492: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.493: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.493: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.493: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.493: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.493: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.493: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.493: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.493: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.494: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.494: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.494: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.494: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.494: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.494: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.494: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.494: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.494: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.494: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.495: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.495: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.495: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.495: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.495: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.495: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.495: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.495: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.496: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.496: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.496: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.496: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.496: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.496: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.496: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.496: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.497: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.497: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.497: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.497: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.497: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.497: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.497: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.497: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.497: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.497: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.497: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.498: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.498: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.498: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.498: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.498: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.498: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.498: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.498: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.498: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.498: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.498: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.499: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.499: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.499: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.499: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.499: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.499: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.499: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.499: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.500: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.500: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.500: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.500: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.500: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.500: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.500: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.500: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.501: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.501: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.501: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.501: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.501: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.501: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.501: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.501: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.501: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.501: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.502: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.502: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.502: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.502: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.502: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.502: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.502: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.502: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.503: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.503: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.503: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.503: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.503: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.503: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.503: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.503: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.504: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.504: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.504: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.504: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.504: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.504: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.504: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.504: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.504: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.504: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.504: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.505: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.505: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.505: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.505: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.505: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.505: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.505: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.505: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.505: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.505: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.505: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.506: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.506: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.506: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.506: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.506: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.506: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.506: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.506: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.507: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.507: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.507: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.507: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.507: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.507: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.507: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.507: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.507: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.508: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.508: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.508: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.508: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.508: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.508: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.508: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.508: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.508: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.509: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.509: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.509: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.509: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.509: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.509: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.509: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.509: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.510: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.510: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.510: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.510: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.510: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.510: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.510: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.510: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.510: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.510: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.510: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.511: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.511: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.511: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.511: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.511: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.511: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.511: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.511: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.511: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.511: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.511: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.512: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.512: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.512: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.512: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.512: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.512: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.512: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.512: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.513: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.513: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.513: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.513: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.513: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.513: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.513: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.513: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.513: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.513: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.514: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.514: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.514: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.514: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.514: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.514: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.514: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.514: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.515: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.515: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.515: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.515: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.515: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.515: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.515: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.515: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.516: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.516: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.516: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.516: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.516: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.516: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.516: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.516: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.517: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.517: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.517: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.517: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.517: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.517: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.517: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.517: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.517: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.517: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.517: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.517: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.517: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.517: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.518: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.518: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.518: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.518: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.518: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.518: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.518: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.518: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.519: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.519: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.519: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.519: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.519: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.519: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.519: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.519: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.519: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.519: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.520: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.520: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.520: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.520: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.520: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.520: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.520: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.520: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.521: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.521: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.521: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.521: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.521: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.521: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.521: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.521: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.522: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.522: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.522: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.522: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.522: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.522: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.522: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.522: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.522: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.522: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.522: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.522: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.522: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.522: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.523: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.523: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.523: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.523: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.523: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.523: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.523: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.523: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.524: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.524: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.524: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.524: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.524: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.524: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.524: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.524: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.524: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.524: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.525: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.525: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.525: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.525: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.525: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.525: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.525: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.525: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.526: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.526: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.526: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.526: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.526: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.526: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.526: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.526: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.526: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.527: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.527: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.527: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.527: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.527: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.527: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.527: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.527: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.527: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.527: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.527: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.527: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.527: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.528: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.528: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.528: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.528: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.528: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.528: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.528: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.528: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.529: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.529: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.529: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.529: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.529: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.529: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.529: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.529: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.529: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.529: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.530: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.530: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.530: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.530: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.530: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.530: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.530: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.530: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.531: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.531: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.531: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.531: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.531: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.531: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.531: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.531: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.531: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.531: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.531: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.531: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.531: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.531: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.532: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.532: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.532: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.532: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.532: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.532: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.532: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.532: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.533: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.533: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.533: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.533: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.533: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.533: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.533: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.533: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.534: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.534: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.534: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.534: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.534: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.534: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.534: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.534: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.535: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.535: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.535: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.535: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.535: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.535: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.535: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.535: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.535: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.535: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.536: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.536: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.536: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.536: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.536: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.536: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.536: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.536: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.537: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.537: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.537: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.537: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.537: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.537: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.537: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.537: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.538: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.538: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.538: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.538: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.538: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.538: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.538: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.538: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.538: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.538: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.539: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.539: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.539: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.539: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.539: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.539: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.539: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.539: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.539: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.539: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.539: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.539: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.540: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.540: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.540: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.540: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.540: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.540: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.540: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.540: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.541: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.541: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.541: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.541: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.541: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.541: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.541: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.541: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.541: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.541: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.542: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.542: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.542: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.542: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.542: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.542: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.542: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.542: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.543: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.543: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.543: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.543: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.543: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.543: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.543: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.543: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.543: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.544: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.544: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.544: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.544: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.544: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.544: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.544: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.544: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.544: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.544: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.544: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.544: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.544: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.545: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.545: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.545: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.545: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.545: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.545: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.545: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.545: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.546: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.546: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.546: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.546: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.546: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.546: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.546: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.546: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.546: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.546: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.547: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.547: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.547: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.547: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.547: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.547: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.547: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.547: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.548: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.548: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.548: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.548: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.548: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.548: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.548: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.548: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.549: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.549: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.549: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.549: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.549: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.549: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.549: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.549: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.549: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.549: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.549: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.549: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.549: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.549: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.550: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.550: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.550: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.550: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.550: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.550: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.550: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.550: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.551: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.551: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.551: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.551: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.551: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.551: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.551: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.551: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.551: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.551: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.552: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.552: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.552: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.552: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.552: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.552: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.552: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.552: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.553: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.553: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.553: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.553: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.553: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.553: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.553: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.553: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.554: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.554: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.554: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.554: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.554: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.554: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.554: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.554: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.555: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.555: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.555: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.555: [vfs7552] CAPTURE_NUM_STATES entering state 2 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.555: [vfs7552] REQUEST CHUNK entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.555: Sending vfs7552_read_image_chunk 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.555: [vfs7552] REQUEST CHUNK completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.555: [vfs7552] CAPTURE_NUM_STATES entering state 3 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.555: [vfs7552] CAPTURE_NUM_STATES entering state 2 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.555: [vfs7552] REQUEST CHUNK entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.556: Sending vfs7552_read_image_chunk 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.556: [vfs7552] REQUEST CHUNK completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.556: [vfs7552] CAPTURE_NUM_STATES entering state 3 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.556: [vfs7552] CAPTURE_NUM_STATES entering state 2 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.556: [vfs7552] REQUEST CHUNK entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.556: Sending vfs7552_read_image_chunk 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.557: [vfs7552] REQUEST CHUNK completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.557: [vfs7552] CAPTURE_NUM_STATES entering state 3 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.557: [vfs7552] CAPTURE_NUM_STATES entering state 4 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.557: Cleaning image 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.557: variance_after = 18 429s 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.557: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.557: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.557: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.558: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.558: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.558: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.558: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.558: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.558: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.558: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.558: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.559: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.559: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.559: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.559: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.559: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.559: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.559: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.559: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.559: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.559: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.560: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.560: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.560: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.560: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.560: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.560: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.560: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.560: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.561: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.561: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.561: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.561: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.561: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.561: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.561: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.561: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.561: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.561: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.561: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.561: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.561: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.561: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.562: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.562: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.562: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.562: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.562: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.562: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.562: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.562: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.563: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.563: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.563: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.563: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.563: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.563: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.563: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.563: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.564: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.564: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.564: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.564: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.564: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.564: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.564: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.564: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.564: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.564: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.565: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.565: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.565: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.565: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.565: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.565: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.565: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.565: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.566: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.566: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.566: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.566: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.566: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.566: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.566: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.566: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.567: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.567: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.567: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.567: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.567: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.567: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.567: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.567: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.567: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.567: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.567: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.567: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.567: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.567: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.568: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.568: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.568: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.568: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.568: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.568: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.568: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.568: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.569: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.569: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.569: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.569: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.569: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.569: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.569: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.569: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.570: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.570: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.570: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.570: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.570: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.570: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.570: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.570: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.570: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.570: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.571: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.571: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.571: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.571: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.571: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.571: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.571: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.571: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.572: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.572: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.572: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.572: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.572: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.572: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.572: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.572: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.573: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.573: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.573: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.573: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.573: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.573: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.573: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.573: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.573: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.573: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.573: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.573: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.574: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.574: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.574: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.574: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.574: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.574: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.574: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.574: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.574: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.574: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.575: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.575: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.575: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.575: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.575: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.575: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.575: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.575: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.576: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.576: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.576: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.576: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.576: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.576: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.576: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.576: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.577: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.577: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.577: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.577: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.577: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.577: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.577: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.577: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.578: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.578: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.578: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.578: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.578: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.578: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.578: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.578: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.578: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.578: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.579: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.579: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.579: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.579: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.579: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.579: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.579: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.579: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.580: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.580: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.580: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.580: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.580: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.580: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.580: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.580: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.581: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.581: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.581: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.581: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.581: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.581: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.581: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.581: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.582: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.582: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.582: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.582: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.582: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.582: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.582: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.582: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.582: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.583: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.583: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.583: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.583: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.583: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.583: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.583: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.583: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.583: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.583: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.583: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.583: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.583: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.584: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.584: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.584: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.584: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.584: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.584: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.584: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.584: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.585: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.585: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.585: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.585: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.585: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.585: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.585: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.585: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.585: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.585: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.586: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.586: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.586: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.586: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.586: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.586: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.586: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.586: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.587: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.587: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.587: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.587: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.587: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.587: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.587: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.587: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.588: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.588: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.588: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.588: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.588: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.588: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.588: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.588: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.588: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.588: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.588: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.588: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.588: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.588: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.589: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.589: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.589: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.589: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.589: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.589: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.589: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.589: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.590: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.590: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.590: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.590: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.590: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.590: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.590: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.590: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.590: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.590: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.591: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.591: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.591: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.591: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.591: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.591: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.591: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.591: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.592: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.592: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.592: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.592: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.592: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.592: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.592: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.592: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.593: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.593: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.593: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.593: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.593: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.593: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.593: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.593: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.593: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.593: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.593: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.593: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.593: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.593: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.594: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.594: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.594: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.594: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.594: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.594: [vfs7552] CAPTURE_NUM_STATES entering state 2 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.594: [vfs7552] REQUEST CHUNK entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.594: Sending vfs7552_read_image_chunk 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.595: [vfs7552] REQUEST CHUNK completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.595: [vfs7552] CAPTURE_NUM_STATES entering state 3 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.595: [vfs7552] CAPTURE_NUM_STATES entering state 2 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.595: [vfs7552] REQUEST CHUNK entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.595: Sending vfs7552_read_image_chunk 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.595: [vfs7552] REQUEST CHUNK completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.595: [vfs7552] CAPTURE_NUM_STATES entering state 3 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.596: [vfs7552] CAPTURE_NUM_STATES entering state 2 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.596: [vfs7552] REQUEST CHUNK entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.596: Sending vfs7552_read_image_chunk 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.596: [vfs7552] REQUEST CHUNK completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.596: [vfs7552] CAPTURE_NUM_STATES entering state 3 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.597: [vfs7552] CAPTURE_NUM_STATES entering state 4 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.597: Cleaning image 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.597: variance_after = 17 429s 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.597: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.597: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.597: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.597: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.597: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.598: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.598: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.598: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.598: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.598: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.598: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.598: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.598: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.599: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.599: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.599: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.599: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.599: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.599: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.599: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.599: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.599: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.599: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.599: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.599: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.599: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.599: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.600: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.600: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.600: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.600: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.600: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.600: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.600: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.600: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.601: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.601: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.601: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.601: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.601: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.601: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.601: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.601: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.602: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.602: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.602: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.602: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.602: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.602: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.602: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.602: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.602: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.602: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.603: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.603: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.603: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.603: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.603: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.603: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.603: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.603: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.604: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.604: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.604: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.604: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.604: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.604: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.604: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.604: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.604: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.604: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.604: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.604: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.604: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.604: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.605: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.605: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.605: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.605: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.605: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.605: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.605: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.605: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.606: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.606: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.606: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.606: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.606: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.606: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.606: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.606: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.606: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.606: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.607: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.607: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.607: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.607: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.607: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.607: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.607: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.607: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.608: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.608: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.608: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.608: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.608: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.608: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.608: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.608: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.609: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.609: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.609: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.609: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.609: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.609: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.609: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.609: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.609: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.609: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.609: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.609: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.609: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.609: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.610: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.610: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.610: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.610: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.610: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.610: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.610: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.610: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.611: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.611: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.611: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.611: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.611: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.611: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.611: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.611: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.611: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.611: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.612: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.612: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.612: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.612: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.612: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.612: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.612: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.612: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.613: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.613: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.613: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.613: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.613: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.613: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.613: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.613: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.614: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.614: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.614: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.614: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.614: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.614: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.614: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.614: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.615: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.615: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.615: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.615: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.615: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.615: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.615: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.615: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.615: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.615: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.615: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.615: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.615: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.615: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.616: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.616: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.616: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.616: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.616: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.616: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.616: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.616: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.617: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.617: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.617: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.617: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.617: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.617: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.617: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.617: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.617: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.617: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.618: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.618: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.618: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.618: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.618: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.618: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.618: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.618: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.619: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.619: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.619: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.619: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.619: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.619: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.619: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.619: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.620: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.620: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.620: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.620: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.620: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.620: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.620: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.620: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.620: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.620: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.620: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.620: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.620: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.620: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.621: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.621: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.621: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.621: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.621: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.621: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.621: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.621: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.622: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.622: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.622: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.622: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.622: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.622: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.622: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.622: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.622: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.623: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.623: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.623: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.623: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.623: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.623: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.623: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.623: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.623: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.624: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.624: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.624: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.624: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.624: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.624: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.624: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.624: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.625: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.625: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.625: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.625: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.625: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.625: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.625: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.625: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.625: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.625: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.625: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.625: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.625: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.625: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.626: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.626: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.626: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.626: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.626: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.626: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.626: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.626: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.627: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.627: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.627: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.627: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.627: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.627: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.627: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.627: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.628: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.628: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.628: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.628: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.628: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.628: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.628: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.628: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.628: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.628: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.629: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.629: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.629: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.629: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.629: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.629: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.629: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.629: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.630: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.630: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.630: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.630: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.630: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.630: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.630: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.630: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.630: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.630: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.630: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.630: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.630: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.630: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.631: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.631: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.631: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.631: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.631: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.631: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.631: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.631: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.632: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.632: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.632: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.632: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.632: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.632: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.632: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.632: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.632: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.632: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.633: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.633: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.633: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.633: [vfs7552] CAPTURE_NUM_STATES entering state 2 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.633: [vfs7552] REQUEST CHUNK entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.633: Sending vfs7552_read_image_chunk 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.633: [vfs7552] REQUEST CHUNK completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.633: [vfs7552] CAPTURE_NUM_STATES entering state 3 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.634: [vfs7552] CAPTURE_NUM_STATES entering state 2 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.634: [vfs7552] REQUEST CHUNK entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.634: Sending vfs7552_read_image_chunk 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.634: [vfs7552] REQUEST CHUNK completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.634: [vfs7552] CAPTURE_NUM_STATES entering state 3 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.635: [vfs7552] CAPTURE_NUM_STATES entering state 2 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.635: [vfs7552] REQUEST CHUNK entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.635: Sending vfs7552_read_image_chunk 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.635: [vfs7552] REQUEST CHUNK completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.635: [vfs7552] CAPTURE_NUM_STATES entering state 3 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.635: [vfs7552] CAPTURE_NUM_STATES entering state 4 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.635: Cleaning image 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.636: variance_after = 16 429s 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.636: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.636: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.636: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.636: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.636: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.636: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.636: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.636: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.636: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.636: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.636: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.637: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.637: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.637: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.637: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.637: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.637: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.637: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.637: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.638: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.638: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.638: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.638: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.638: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.638: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.638: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.638: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.639: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.639: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.639: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.639: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.639: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.639: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.639: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.639: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.639: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.639: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.640: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.640: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.640: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.640: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.640: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.640: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.640: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.640: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.641: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.641: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.641: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.641: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.641: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.641: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.641: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.641: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.641: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.641: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.641: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.641: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.641: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.641: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.642: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.642: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.642: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.642: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.642: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.642: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.642: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.642: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.643: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.643: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.643: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.643: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.643: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.643: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.643: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.643: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.643: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.643: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.644: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.644: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.644: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.644: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.644: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.644: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.644: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.644: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.645: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.645: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.645: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.645: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.645: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.645: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.645: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.645: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.646: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.646: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.646: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.646: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.646: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.646: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.646: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.646: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.647: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.647: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.647: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.647: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.647: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.647: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.647: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.647: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.647: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.647: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.647: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.647: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.647: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.647: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.648: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.648: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.648: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.648: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.648: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.648: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.648: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.648: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.649: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.649: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.649: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.649: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.649: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.649: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.649: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.649: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.649: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.649: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.650: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.650: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.650: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.650: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.650: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.650: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.650: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.650: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.651: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.651: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.651: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.651: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.651: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.651: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.651: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.651: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.652: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.652: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.652: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.652: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.652: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.652: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.652: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.652: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.652: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.652: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.652: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.652: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.652: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.652: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.653: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.653: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.653: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.653: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.653: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.653: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.653: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.653: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.654: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.654: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.654: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.654: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.654: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.654: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.654: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.654: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.654: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.654: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.655: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.655: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.655: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.655: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.655: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.655: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.655: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.655: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.656: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.656: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.656: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.656: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.656: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.656: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.656: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.656: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.657: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.657: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.657: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.657: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.657: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.657: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.657: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.657: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.658: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.658: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.658: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.658: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.658: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.658: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.658: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.658: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.658: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.658: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.658: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.658: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.658: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.658: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.659: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.659: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.659: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.659: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.659: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.659: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.659: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.659: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.660: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.660: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.660: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.660: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.660: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.660: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.660: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.660: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.661: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.661: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.661: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.661: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.661: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.661: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.661: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.661: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.661: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.661: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.662: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.662: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.662: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.662: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.662: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.662: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.662: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.662: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.663: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.663: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.663: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.663: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.663: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.663: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.663: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.663: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.664: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.664: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.664: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.664: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.664: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.664: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.664: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.664: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.664: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.664: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.664: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.664: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.664: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.664: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.665: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.665: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.665: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.665: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.665: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.665: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.665: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.665: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.666: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.666: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.666: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.666: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.666: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.666: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.666: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.666: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.667: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.667: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.667: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.667: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.667: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.667: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.667: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.667: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.667: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.667: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.668: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.668: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.668: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.668: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.668: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.668: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.668: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.668: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.669: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.669: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.669: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.669: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.669: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.669: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.669: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.669: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.669: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.669: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.669: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.669: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.669: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.669: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.670: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.670: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.670: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.670: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.670: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.670: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.670: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.670: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.671: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.671: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.671: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.671: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.671: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.671: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.671: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.671: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.671: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.671: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.672: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.672: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.672: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.672: [vfs7552] CAPTURE_NUM_STATES entering state 2 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.672: [vfs7552] REQUEST CHUNK entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.672: Sending vfs7552_read_image_chunk 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.672: [vfs7552] REQUEST CHUNK completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.672: [vfs7552] CAPTURE_NUM_STATES entering state 3 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.673: [vfs7552] CAPTURE_NUM_STATES entering state 2 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.673: [vfs7552] REQUEST CHUNK entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.673: Sending vfs7552_read_image_chunk 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.673: [vfs7552] REQUEST CHUNK completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.673: [vfs7552] CAPTURE_NUM_STATES entering state 3 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.674: [vfs7552] CAPTURE_NUM_STATES entering state 2 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.674: [vfs7552] REQUEST CHUNK entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.674: Sending vfs7552_read_image_chunk 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.674: [vfs7552] REQUEST CHUNK completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.674: [vfs7552] CAPTURE_NUM_STATES entering state 3 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.675: [vfs7552] CAPTURE_NUM_STATES entering state 4 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.675: Cleaning image 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.675: variance_after = 17 429s 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.675: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.675: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.675: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.675: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.675: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.676: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.676: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.676: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.676: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.676: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.676: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.676: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.676: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.676: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.677: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.677: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.677: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.677: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.677: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.677: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.677: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.677: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.677: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.677: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.677: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.677: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.677: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.678: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.678: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.678: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.678: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.678: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.678: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.678: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.678: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.679: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.679: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.679: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.679: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.679: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.679: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.679: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.679: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.679: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.679: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.680: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.680: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.680: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.680: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.680: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.680: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.680: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.680: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.681: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.681: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.681: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.681: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.681: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.681: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.681: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.681: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.682: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.682: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.682: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.682: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.682: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.682: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.682: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.682: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.683: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.683: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.683: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.683: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.683: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.683: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.683: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.683: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.684: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.684: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.684: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.684: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.684: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.684: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.684: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.684: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.684: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.684: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.684: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.684: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.684: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.684: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.685: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.685: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.685: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.685: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.685: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.685: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.685: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.685: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.686: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.686: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.687: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.687: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.687: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.687: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.687: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.687: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.688: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.688: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.688: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.688: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.688: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.688: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.688: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.688: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.688: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.688: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.689: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.689: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.689: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.689: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.689: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.689: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.689: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.689: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.690: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.690: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.690: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.690: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.690: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.690: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.690: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.690: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.691: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.691: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.691: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.691: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.691: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.691: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.691: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.691: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.691: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.691: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.691: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.691: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.691: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.691: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.692: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.692: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.692: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.692: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.692: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.692: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.692: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.692: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.693: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.693: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.693: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.693: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.693: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.693: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.693: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.693: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.694: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.694: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.694: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.694: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.694: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.694: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.694: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.694: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.695: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.695: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.695: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.695: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.695: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.695: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.695: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.695: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.695: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.695: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.696: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.696: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.696: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.696: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.696: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.696: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.696: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.696: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.697: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.697: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.697: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.697: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.697: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.697: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.697: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.697: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.698: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.698: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.698: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.698: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.698: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.698: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.698: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.698: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.698: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.698: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.698: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.698: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.698: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.698: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.699: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.699: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.699: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.699: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.699: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.699: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.699: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.699: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.700: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.700: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.700: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.700: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.700: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.700: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.700: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.700: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.700: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.700: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.701: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.701: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.701: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.701: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.701: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.701: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.701: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.701: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.702: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.702: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.702: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.702: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.702: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.702: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.702: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.702: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.703: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.703: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.703: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.703: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.703: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.703: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.703: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.703: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.703: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.703: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.703: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.703: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.703: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.703: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.704: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.704: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.704: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.704: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.704: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.704: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.704: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.704: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.705: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.705: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.705: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.705: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.705: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.705: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.705: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.705: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.705: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.705: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.706: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.706: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.706: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.706: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.706: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.706: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.706: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.706: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.707: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.707: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.707: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.707: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.707: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.707: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.707: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.707: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.707: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.707: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.707: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.707: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.707: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.707: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.708: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.708: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.708: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.708: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.708: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.708: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.708: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.708: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.709: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.709: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.709: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.709: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.709: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.709: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.709: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.709: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.710: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.710: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.710: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.710: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.710: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.710: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.710: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.710: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.710: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.710: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.711: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.711: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.711: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.711: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.711: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.711: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.711: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.711: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.712: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.712: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.712: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.712: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.712: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.712: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.712: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.712: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.712: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.712: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.712: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.712: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.713: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.713: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.713: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.713: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.713: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.713: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.713: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.713: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.713: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.713: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.714: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.714: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.714: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.714: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.714: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.714: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.714: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.714: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.715: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.715: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.715: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.715: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.715: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.715: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.715: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.715: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.715: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.715: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.716: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.716: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.716: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.716: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.716: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.716: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.716: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.716: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.717: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.717: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.717: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.717: [vfs7552] CAPTURE_NUM_STATES entering state 2 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.717: [vfs7552] REQUEST CHUNK entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.717: Sending vfs7552_read_image_chunk 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.717: [vfs7552] REQUEST CHUNK completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.717: [vfs7552] CAPTURE_NUM_STATES entering state 3 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.718: [vfs7552] CAPTURE_NUM_STATES entering state 2 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.718: [vfs7552] REQUEST CHUNK entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.718: Sending vfs7552_read_image_chunk 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.718: [vfs7552] REQUEST CHUNK completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.718: [vfs7552] CAPTURE_NUM_STATES entering state 3 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.718: [vfs7552] CAPTURE_NUM_STATES entering state 2 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.718: [vfs7552] REQUEST CHUNK entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.718: Sending vfs7552_read_image_chunk 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.719: [vfs7552] REQUEST CHUNK completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.719: [vfs7552] CAPTURE_NUM_STATES entering state 3 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.719: [vfs7552] CAPTURE_NUM_STATES entering state 4 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.719: Cleaning image 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.719: variance_after = 17 429s 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.719: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.719: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.719: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.720: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.720: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.720: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.720: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.720: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.720: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.720: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.720: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.721: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.721: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.721: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.721: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.721: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.721: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.721: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.721: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.721: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.721: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.722: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.722: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.722: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.722: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.722: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.722: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.722: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.722: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.723: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.723: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.723: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.723: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.723: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.723: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.723: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.723: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.723: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.724: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.724: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.724: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.724: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.724: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.724: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.724: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.724: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.724: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.724: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.724: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.724: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.724: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.725: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.725: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.725: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.725: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.725: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.725: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.725: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.725: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.726: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.726: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.726: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.726: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.726: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.726: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.726: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.726: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.726: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.726: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.727: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.727: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.727: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.727: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.727: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.727: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.727: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.727: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.728: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.728: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.728: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.728: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.728: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.728: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.728: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.728: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.729: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.729: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.729: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.729: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.729: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.729: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.729: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.729: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.729: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.729: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.729: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.729: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.729: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.729: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.730: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.730: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.730: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.730: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.730: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.730: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.730: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.730: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.731: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.731: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.731: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.731: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.731: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.731: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.731: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.731: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.731: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.731: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.732: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.732: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.732: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.732: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.732: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.732: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.732: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.732: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.733: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.733: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.733: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.733: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.733: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.733: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.733: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.733: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.734: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.734: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.734: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.734: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.734: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.734: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.734: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.734: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.734: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.734: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.734: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.734: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.734: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.734: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.735: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.735: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.735: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.735: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.735: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.735: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.735: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.735: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.736: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.736: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.736: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.736: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.736: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.736: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.736: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.736: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.737: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.737: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.737: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.737: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.737: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.737: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.737: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.737: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.737: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.737: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.738: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.738: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.738: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.738: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.738: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.738: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.738: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.738: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.739: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.739: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.739: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.739: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.739: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.739: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.739: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.739: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.740: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.740: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.740: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.740: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.740: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.740: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.740: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.740: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.740: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.740: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.740: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.740: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.740: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.740: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.741: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.741: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.741: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.741: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.741: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.741: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.741: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.741: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.742: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.742: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.742: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.742: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.742: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.742: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.742: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.742: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.742: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.743: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.743: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.743: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.743: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.743: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.743: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.743: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.743: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.743: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.744: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.744: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.744: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.744: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.744: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.744: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.744: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.744: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.745: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.745: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.745: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.745: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.745: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.745: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.745: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.745: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.745: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.745: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.745: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.745: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.745: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.745: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.746: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.746: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.746: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.746: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.746: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.746: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.746: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.746: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.747: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.747: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.747: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.747: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.747: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.747: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.747: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.747: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.748: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.748: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.748: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.748: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.748: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.748: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.748: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.748: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.748: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.748: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.749: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.749: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.749: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.749: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.749: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.749: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.749: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.749: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.750: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.750: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.750: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.750: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.750: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.750: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.750: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.750: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.750: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.750: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.750: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.750: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.750: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.750: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.751: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.751: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.751: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.751: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.751: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.751: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.751: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.751: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.752: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.752: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.752: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.752: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.752: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.752: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.752: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.752: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.752: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.752: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.753: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.753: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.753: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.753: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.753: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.753: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.753: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.753: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.754: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.754: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.754: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.754: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.754: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.754: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.754: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.754: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.755: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.755: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.755: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.755: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.755: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.755: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.755: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.755: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.755: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.755: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.755: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.755: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.755: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.755: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.756: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.756: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.756: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.756: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.756: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.756: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.756: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.756: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.757: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.757: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.757: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.757: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.757: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.757: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.757: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.757: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.757: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.758: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.758: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.758: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.758: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.758: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.758: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.758: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.758: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.758: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.759: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.759: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.759: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.759: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.759: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.759: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.759: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.759: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.760: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.760: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.760: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.760: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.760: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.760: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.760: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.760: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.760: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.760: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.760: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.760: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.760: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.760: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.761: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.761: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.761: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.761: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.761: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.761: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.761: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.761: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.762: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.762: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.762: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.762: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.762: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.762: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.762: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.762: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.762: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.762: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.763: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.763: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.763: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.763: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.763: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.763: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.763: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.763: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.764: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.764: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.764: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.764: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.764: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.764: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.764: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.764: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.765: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.765: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.765: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.765: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.765: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.765: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.765: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.765: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.765: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.765: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.765: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.765: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.765: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.765: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.766: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.766: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.766: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.766: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.766: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.766: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.766: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.766: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.767: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.767: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.767: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.767: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.767: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.767: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.767: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.767: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.767: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.767: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.768: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.768: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.768: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.768: [vfs7552] CAPTURE_NUM_STATES entering state 2 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.768: [vfs7552] REQUEST CHUNK entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.768: Sending vfs7552_read_image_chunk 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.768: [vfs7552] REQUEST CHUNK completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.768: [vfs7552] CAPTURE_NUM_STATES entering state 3 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.769: [vfs7552] CAPTURE_NUM_STATES entering state 2 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.769: [vfs7552] REQUEST CHUNK entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.769: Sending vfs7552_read_image_chunk 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.769: [vfs7552] REQUEST CHUNK completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.769: [vfs7552] CAPTURE_NUM_STATES entering state 3 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.769: [vfs7552] CAPTURE_NUM_STATES entering state 2 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.770: [vfs7552] REQUEST CHUNK entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.770: Sending vfs7552_read_image_chunk 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.770: [vfs7552] REQUEST CHUNK completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.770: [vfs7552] CAPTURE_NUM_STATES entering state 3 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.770: [vfs7552] CAPTURE_NUM_STATES entering state 4 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.770: Cleaning image 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.770: variance_after = 17 429s 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.770: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.770: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.770: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.771: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.771: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.771: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.771: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.771: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.771: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.771: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.771: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.772: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.772: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.772: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.772: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.772: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.772: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.772: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.772: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.773: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.773: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.773: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.773: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.773: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.773: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.773: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.773: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.773: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.773: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.774: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.774: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.774: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.774: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.774: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.774: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.774: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.774: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.775: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.775: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.775: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.775: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.775: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.775: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.775: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.775: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.776: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.776: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.776: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.776: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.776: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.776: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.776: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.776: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.776: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.776: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.776: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.776: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.776: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.776: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.777: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.777: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.777: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.777: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.777: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.777: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.777: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.777: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.778: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.778: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.778: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.778: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.778: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.778: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.778: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.778: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.779: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.779: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.779: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.779: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.779: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.779: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.779: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.779: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.779: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.779: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.780: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.780: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.780: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.780: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.780: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.780: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.780: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.780: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.781: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.781: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.781: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.781: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.781: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.781: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.781: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.781: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.781: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.781: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.781: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.781: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.781: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.781: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.782: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.782: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.782: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.782: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.782: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.782: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.782: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.782: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.783: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.783: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.783: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.783: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.783: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.783: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.783: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.783: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.784: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.784: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.784: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.784: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.784: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.784: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.784: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.784: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.784: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.784: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.785: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.785: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.785: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.785: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.785: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.785: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.785: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.785: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.786: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.786: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.786: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.786: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.786: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.786: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.786: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.786: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.786: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.786: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.786: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.786: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.786: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.786: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.787: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.787: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.787: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.787: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.787: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.787: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.787: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.787: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.788: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.788: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.788: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.788: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.788: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.788: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.788: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.788: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.789: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.789: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.789: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.789: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.789: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.789: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.789: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.789: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.789: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.789: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.790: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.790: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.790: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.790: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.790: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.790: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.790: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.790: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.791: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.791: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.791: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.791: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.791: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.791: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.791: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.791: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.792: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.792: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.792: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.792: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.792: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.792: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.792: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.792: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.792: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.792: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.792: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.792: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.792: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.792: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.793: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.793: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.793: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.793: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.793: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.793: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.793: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.793: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.794: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.794: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.794: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.794: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.794: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.794: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.794: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.794: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.794: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.794: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.795: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.795: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.795: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.795: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.795: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.795: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.795: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.795: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.796: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.796: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.796: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.796: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.796: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.796: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.796: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.796: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.797: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.797: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.797: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.797: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.797: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.797: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.797: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.797: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.797: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.797: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.797: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.797: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.797: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.797: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.798: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.798: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.798: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.798: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.798: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.798: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.798: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.798: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.799: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.799: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.799: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.799: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.799: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.799: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.799: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.799: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.800: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.800: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.800: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.800: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.800: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.800: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.800: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.800: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.800: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.800: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.801: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.801: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.801: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.801: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.801: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.801: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.801: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.801: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.802: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.802: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.802: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.802: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.802: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.802: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.802: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.802: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.803: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.803: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.803: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.803: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.803: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.803: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.803: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.803: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.803: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.803: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.803: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.803: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.803: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.803: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.804: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.804: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.804: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.804: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.804: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.804: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.804: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.804: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.805: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.805: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.805: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.805: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.805: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.805: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.805: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.805: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.806: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.806: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.806: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.806: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.806: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.806: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.806: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.806: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.806: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.806: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.807: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.807: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.807: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.807: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.807: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.807: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.807: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.807: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.808: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.808: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.808: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.808: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.808: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.808: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.808: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.808: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.808: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.808: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.808: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.808: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.808: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.808: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.809: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.809: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.809: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.809: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.809: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.809: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.809: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.809: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.810: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.810: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.810: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.810: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.810: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.810: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.810: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.810: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.811: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.811: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.811: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.811: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.811: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.811: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.811: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.811: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.812: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.812: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.812: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.812: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.812: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.812: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.812: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.812: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.813: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.813: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.813: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.813: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.813: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.813: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.813: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.813: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.813: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.813: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.814: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.814: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.814: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.814: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.814: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.814: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.814: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.814: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.815: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.815: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.815: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.815: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.815: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.815: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.815: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.815: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.816: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.816: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.816: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.816: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.816: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.816: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.816: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.816: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.817: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.817: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.817: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.817: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.817: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.817: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.817: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.817: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.817: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.817: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.817: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.817: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.817: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.817: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.818: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.818: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.818: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.818: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.818: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.818: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.818: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.818: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.819: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.819: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.819: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.819: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.819: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.819: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.819: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.819: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.820: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.820: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.820: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.820: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.820: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.820: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.820: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.820: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.820: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.820: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.821: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.821: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.821: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.821: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.821: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.821: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.821: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.821: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.822: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.822: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.822: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.822: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.822: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.822: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.822: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.822: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.822: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.822: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.822: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.822: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.822: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.822: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.823: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.823: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.823: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.823: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.823: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.823: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.823: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.823: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.824: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.824: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.824: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.824: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.824: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.824: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.824: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.824: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.825: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.825: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.825: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.825: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.825: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.825: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.825: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.825: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.825: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.825: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.826: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.826: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.826: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.826: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.826: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.826: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.826: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.826: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.827: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.827: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.827: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.827: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.827: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.827: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.827: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.827: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.828: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.828: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.828: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.828: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.828: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.828: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.828: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.828: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.828: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.828: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.828: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.828: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.828: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.828: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.829: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.829: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.829: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.829: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.829: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.829: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.829: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.829: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.830: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.830: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.830: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.830: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.830: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.830: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.830: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.830: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.830: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.830: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.831: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.831: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.831: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.831: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.831: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.831: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.831: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.831: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.832: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.832: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.832: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.832: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.832: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.832: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.832: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.832: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.832: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.832: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.832: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.832: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.832: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.832: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.833: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.833: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.833: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.833: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.833: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.833: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.833: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.833: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.834: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.834: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.834: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.834: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.834: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.834: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.834: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.834: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.835: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.835: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.835: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.835: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.835: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.835: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.835: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.835: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.835: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.835: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.836: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.836: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.836: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.836: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.836: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.836: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.836: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.836: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.837: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.837: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.837: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.837: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.837: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.837: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.837: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.837: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.837: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.838: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.838: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.838: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.838: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.838: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.838: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.838: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.838: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.838: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.838: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.838: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.838: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.838: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.839: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.839: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.839: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.839: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.839: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.839: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.839: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.839: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.840: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.840: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.840: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.840: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.840: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.840: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.840: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.840: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.840: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.840: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.841: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.841: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.841: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.841: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.841: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.841: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.841: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.841: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.842: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.842: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.842: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.842: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.842: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.842: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.842: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.842: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.843: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.843: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.843: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.843: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.843: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.843: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.843: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.843: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.843: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.843: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.843: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.843: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.843: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.843: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.844: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.844: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.844: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.844: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.844: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.844: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.844: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.844: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.845: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.845: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.845: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.845: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.845: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.845: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.845: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.845: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.845: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.845: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.846: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.846: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.846: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.846: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.846: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.846: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.846: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.846: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.847: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.847: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.847: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.847: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.847: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.847: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.847: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.847: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.847: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.847: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.847: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.847: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.847: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.847: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.848: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.848: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.848: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.848: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.848: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.848: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.848: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.848: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.849: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.849: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.849: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.849: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.849: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.849: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.849: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.849: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.850: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.850: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.850: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.850: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.850: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.850: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.850: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.850: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.850: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.850: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.851: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.851: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.851: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.851: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.851: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.851: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.851: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.851: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.852: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.852: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.852: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.852: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.852: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.852: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.852: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.852: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.853: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.853: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.853: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.853: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.853: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.853: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.853: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.853: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.853: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.853: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.853: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.853: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.853: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.853: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.854: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.854: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.854: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.854: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.854: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.854: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.854: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.854: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.855: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.855: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.855: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.855: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.855: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.855: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.855: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.855: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.855: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.855: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.856: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.856: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.856: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.856: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.856: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.856: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.856: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.856: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.857: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.857: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.857: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.857: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.857: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.857: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.857: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.857: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.858: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.858: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.858: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.858: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.858: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.858: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.858: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.858: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.858: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.858: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.858: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.858: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.858: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.858: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.859: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.859: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.859: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.859: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.859: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.859: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.859: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.859: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.860: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.860: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.860: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.860: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.860: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.860: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.860: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.860: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.860: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.860: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.861: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.861: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.861: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.861: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.861: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.861: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.861: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.861: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.862: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.862: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.862: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.862: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.862: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.862: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.862: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.862: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.863: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.863: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.863: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.863: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.863: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.863: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.863: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.863: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.863: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.863: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.863: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.863: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.863: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.863: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.864: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.864: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.864: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.864: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.864: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.864: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.864: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.864: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.865: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.865: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.865: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.865: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.865: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.865: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.865: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.865: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.866: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.866: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.866: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.866: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.866: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.866: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.866: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.866: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.866: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.866: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.867: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.867: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.867: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.867: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.867: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.867: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.867: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.867: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.868: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.868: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.868: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.868: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.868: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.868: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.868: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.868: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.869: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.869: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.869: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.869: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.869: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.869: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.869: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.869: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.869: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.869: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.869: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.869: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.869: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.869: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.870: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.870: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.870: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.870: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.870: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.870: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.870: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.870: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.871: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.871: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.871: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.871: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.871: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.871: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.871: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.871: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.871: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.871: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.872: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.872: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.872: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.872: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.872: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.872: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.872: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.872: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.873: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.873: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.873: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.873: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.873: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.873: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.873: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.873: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.874: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.874: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.874: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.874: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.874: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.874: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.874: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.874: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.875: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.875: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.875: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.875: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.875: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.875: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.875: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.875: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.875: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.875: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.875: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.875: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.875: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.875: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.876: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.876: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.876: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.876: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.876: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.876: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.876: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.876: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.877: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.877: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.877: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.877: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.877: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.877: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.877: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.877: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.878: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.878: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.878: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.878: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.878: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.878: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.878: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.878: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.878: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.878: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.879: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.879: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.879: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.879: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.879: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.879: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.879: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.879: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.880: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.880: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.880: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.880: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.880: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.880: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.880: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.880: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.881: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.881: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.881: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.881: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.881: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.881: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.881: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.881: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.881: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.881: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.881: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.881: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.881: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.881: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.882: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.882: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.882: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.882: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.882: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.882: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.882: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.882: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.883: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.883: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.883: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.883: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.883: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.883: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.883: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.883: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.884: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.884: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.884: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.884: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.884: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.884: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.884: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.884: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.884: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.884: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.885: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.885: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.885: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.885: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.885: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.885: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.885: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.885: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.886: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.886: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.886: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.886: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.886: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.886: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.886: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.886: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.886: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.887: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.887: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.887: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.887: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.887: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.887: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.887: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.888: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.888: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.888: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.888: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.888: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.888: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.888: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.888: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.889: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.889: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.889: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.889: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.889: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.889: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.889: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.889: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.890: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.890: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.890: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.890: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.890: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.890: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.890: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.890: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.890: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.890: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.890: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.890: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.890: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.890: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.891: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.891: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.891: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.891: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.891: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.891: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.891: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.891: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.892: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.892: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.892: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.892: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.892: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.892: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.892: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.892: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.892: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.892: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.893: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.893: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.893: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.893: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.893: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.893: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.893: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.894: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.894: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.894: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.894: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.894: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.894: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.894: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.894: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.894: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.895: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.895: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.895: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.895: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.895: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.895: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.895: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.895: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.896: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.896: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.896: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.896: [vfs7552] CAPTURE_NUM_STATES entering state 2 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.896: [vfs7552] REQUEST CHUNK entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.896: Sending vfs7552_read_image_chunk 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.896: [vfs7552] REQUEST CHUNK completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.896: [vfs7552] CAPTURE_NUM_STATES entering state 3 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.896: [vfs7552] CAPTURE_NUM_STATES entering state 2 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.896: [vfs7552] REQUEST CHUNK entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.896: Sending vfs7552_read_image_chunk 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.897: [vfs7552] REQUEST CHUNK completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.897: [vfs7552] CAPTURE_NUM_STATES entering state 3 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.897: [vfs7552] CAPTURE_NUM_STATES entering state 2 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.897: [vfs7552] REQUEST CHUNK entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.897: Sending vfs7552_read_image_chunk 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.898: [vfs7552] REQUEST CHUNK completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.898: [vfs7552] CAPTURE_NUM_STATES entering state 3 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.898: [vfs7552] CAPTURE_NUM_STATES entering state 4 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.898: Cleaning image 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.898: variance_after = 20 429s 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.898: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.898: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.898: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.899: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.899: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.899: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.899: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.899: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.899: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.899: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.899: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.899: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.899: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.900: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.900: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.900: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.900: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.900: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.900: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.900: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.900: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.901: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.901: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.901: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.901: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.901: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.901: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.901: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.901: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.902: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.902: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.902: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.902: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.902: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.902: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.902: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.902: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.902: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.902: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.902: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.902: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.902: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.902: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.903: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.903: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.903: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.903: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.903: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.903: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.903: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.903: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.904: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.904: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.904: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.904: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.904: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.904: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.904: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.904: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.904: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.904: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.905: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.905: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.905: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.905: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.905: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.905: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.906: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.906: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.906: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.906: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.906: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.906: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.906: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.906: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.906: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.906: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.907: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.907: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.907: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.907: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.907: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.907: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.907: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.907: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.908: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.908: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.908: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.908: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.908: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.908: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.908: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.908: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.909: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.909: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.909: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.909: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.909: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.909: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.909: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.909: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.909: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.909: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.909: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.909: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.909: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.909: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.910: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.910: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.910: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.910: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.910: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.910: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.910: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.910: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.911: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.911: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.911: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.911: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.911: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.911: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.911: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.911: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.911: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.911: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.912: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.912: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.912: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.912: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.912: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.912: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.912: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.912: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.913: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.913: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.913: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.913: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.913: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.913: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.913: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.913: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.914: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.914: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.914: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.914: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.914: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.914: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.914: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.914: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.914: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.914: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.914: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.914: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.914: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.914: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.915: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.915: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.915: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.915: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.915: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.915: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.915: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.915: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.916: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.916: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.916: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.916: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.916: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.916: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.916: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.916: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.917: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.917: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.917: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.917: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.917: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.917: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.917: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.917: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.917: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.917: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.918: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.918: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.918: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.918: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.918: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.918: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.918: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.918: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.919: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.919: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.919: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.919: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.919: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.919: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.919: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.919: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.920: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.920: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.920: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.920: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.920: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.920: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.920: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.920: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.920: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.920: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.920: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.920: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.920: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.920: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.921: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.921: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.921: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.921: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.921: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.921: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.921: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.921: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.922: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.922: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.922: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.922: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.922: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.922: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.922: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.922: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.922: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.922: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.923: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.923: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.923: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.923: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.923: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.923: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.923: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.923: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.924: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.924: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.924: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.924: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.924: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.924: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.924: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.924: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.924: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.925: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.925: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.925: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.925: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.925: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.925: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.925: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.925: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.925: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.925: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.925: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.925: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.925: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.926: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.926: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.926: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.926: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.926: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.926: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.926: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.926: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.927: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.927: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.927: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.927: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.927: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.927: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.927: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.927: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.927: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.927: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.928: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.928: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.928: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.928: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.928: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.928: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.928: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.928: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.929: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.929: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.929: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.929: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.929: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.929: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.929: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.929: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.930: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.930: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.930: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.930: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.930: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.930: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.930: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.930: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.930: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.930: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.930: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.930: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.930: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.930: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.931: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.931: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.931: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.931: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.931: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.931: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.931: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.931: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.932: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.932: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.932: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.932: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.932: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.932: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.932: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.932: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.932: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.932: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.933: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.933: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.933: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.933: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.933: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.933: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.933: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.933: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.934: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.934: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.934: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.934: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.934: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.934: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.934: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.934: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.935: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.935: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.935: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.935: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.935: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.935: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.935: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.935: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.935: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.935: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.935: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.935: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.935: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.935: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.936: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.936: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.936: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.936: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.936: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.936: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.936: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.936: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.937: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.937: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.937: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.937: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.937: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.937: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.937: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.937: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.938: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.938: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.938: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.938: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.938: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.938: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.938: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.938: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.939: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.939: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.939: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.939: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.939: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.939: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.939: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.939: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.939: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.939: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.940: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.940: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.940: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.940: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.940: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.940: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.940: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.940: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.941: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.941: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.941: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.941: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.941: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.941: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.941: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.941: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.942: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.942: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.942: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.942: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.942: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.942: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.942: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.942: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.942: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.942: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.942: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.942: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.942: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.942: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.943: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.943: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.943: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.943: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.943: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.943: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.943: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.943: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.944: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.944: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.944: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.944: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.944: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.944: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.944: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.944: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.945: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.945: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.945: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.945: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.945: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.945: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.945: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.945: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.945: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.945: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.946: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.946: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.946: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.946: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.946: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.946: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.946: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.946: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.947: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.947: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.947: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.947: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.947: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.947: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.947: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.947: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.948: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.948: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.948: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.948: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.948: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.948: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.948: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.948: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.949: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.949: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.949: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.949: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.949: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.949: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.949: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.949: Receiving 64 bytes 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.949: Got 6 bytes out of 64 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.949: [vfs7552] QUERY DATA READY completed successfully 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.949: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.949: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.949: [vfs7552] QUERY DATA READY entering state 0 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.949: Sending vfs7552_is_image_ready 429s (process:2292): libfprint-SSM-DEBUG: 00:54:38.950: [vfs7552] QUERY DATA READY entering state 1 429s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.950: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.950: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:38.950: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:38.950: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:38.950: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:38.950: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.950: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:38.951: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.951: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.951: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:38.951: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:38.951: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:38.951: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:38.951: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.951: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:38.951: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.951: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.952: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:38.952: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:38.952: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:38.952: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:38.952: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.952: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:38.952: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.952: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.953: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:38.953: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:38.953: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:38.953: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:38.953: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.953: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:38.953: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.953: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.954: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:38.954: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:38.954: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:38.954: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:38.954: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.954: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:38.954: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.954: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.954: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:38.954: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:38.954: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:38.954: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:38.954: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.954: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:38.955: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.955: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.955: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:38.955: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:38.955: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:38.955: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:38.955: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.955: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:38.956: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.956: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.956: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:38.956: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:38.956: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:38.956: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:38.956: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.956: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:38.956: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.956: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.957: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:38.957: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:38.957: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:38.957: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:38.957: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.957: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:38.957: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.957: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.958: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:38.958: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:38.958: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:38.958: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:38.958: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.958: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:38.958: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.958: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.959: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:38.959: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:38.959: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:38.959: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:38.959: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.959: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:38.959: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.959: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.959: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:38.959: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:38.959: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:38.959: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:38.959: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.959: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:38.960: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.960: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.960: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:38.960: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:38.960: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:38.960: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:38.960: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.960: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:38.961: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.961: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.961: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:38.961: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:38.961: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:38.961: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:38.961: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.961: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:38.962: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.962: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.962: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:38.962: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:38.962: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:38.962: [vfs7552] CAPTURE_NUM_STATES entering state 2 430s (process:2292): libfprint-SSM-DEBUG: 00:54:38.962: [vfs7552] REQUEST CHUNK entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.962: Sending vfs7552_read_image_chunk 430s (process:2292): libfprint-SSM-DEBUG: 00:54:38.962: [vfs7552] REQUEST CHUNK completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:38.962: [vfs7552] CAPTURE_NUM_STATES entering state 3 430s (process:2292): libfprint-SSM-DEBUG: 00:54:38.963: [vfs7552] CAPTURE_NUM_STATES entering state 2 430s (process:2292): libfprint-SSM-DEBUG: 00:54:38.963: [vfs7552] REQUEST CHUNK entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.963: Sending vfs7552_read_image_chunk 430s (process:2292): libfprint-SSM-DEBUG: 00:54:38.963: [vfs7552] REQUEST CHUNK completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:38.963: [vfs7552] CAPTURE_NUM_STATES entering state 3 430s (process:2292): libfprint-SSM-DEBUG: 00:54:38.964: [vfs7552] CAPTURE_NUM_STATES entering state 2 430s (process:2292): libfprint-SSM-DEBUG: 00:54:38.964: [vfs7552] REQUEST CHUNK entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.964: Sending vfs7552_read_image_chunk 430s (process:2292): libfprint-SSM-DEBUG: 00:54:38.964: [vfs7552] REQUEST CHUNK completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:38.964: [vfs7552] CAPTURE_NUM_STATES entering state 3 430s (process:2292): libfprint-SSM-DEBUG: 00:54:38.964: [vfs7552] CAPTURE_NUM_STATES entering state 4 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.964: Cleaning image 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.965: variance_after = 17 430s 430s (process:2292): libfprint-SSM-DEBUG: 00:54:38.965: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:38.965: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.965: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:38.965: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.965: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.965: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:38.965: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:38.965: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:38.965: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:38.965: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.965: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:38.966: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.966: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.966: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:38.966: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:38.966: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:38.966: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:38.966: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.966: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:38.967: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.967: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.967: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:38.967: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:38.967: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:38.967: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:38.967: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.967: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:38.967: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.967: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.968: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:38.968: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:38.968: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:38.968: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:38.968: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.968: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:38.968: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.968: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.969: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:38.969: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:38.969: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:38.969: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:38.969: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.969: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:38.969: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.969: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.970: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:38.970: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:38.970: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:38.970: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:38.970: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.970: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:38.970: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.970: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.970: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:38.970: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:38.970: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:38.970: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:38.970: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.970: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:38.971: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.971: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.971: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:38.971: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:38.971: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:38.972: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:38.972: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.972: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:38.972: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.972: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.973: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:38.973: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:38.973: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:38.973: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:38.973: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.973: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:38.973: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.973: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.973: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:38.973: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:38.973: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:38.973: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:38.974: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.974: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:38.974: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.974: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.974: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:38.974: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:38.974: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:38.974: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:38.974: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.974: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:38.975: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.975: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.975: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:38.975: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:38.975: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:38.975: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:38.975: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.975: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:38.976: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.976: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.976: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:38.976: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:38.976: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:38.976: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:38.976: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.976: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:38.976: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.976: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.977: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:38.977: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:38.977: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:38.977: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:38.977: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.977: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:38.977: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.977: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.978: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:38.978: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:38.978: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:38.978: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:38.978: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.978: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:38.979: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.979: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.979: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:38.979: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:38.979: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:38.979: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:38.979: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.979: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:38.980: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.980: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.980: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:38.980: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:38.980: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:38.980: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:38.980: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.980: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:38.981: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.981: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.981: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:38.981: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:38.981: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:38.981: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:38.981: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.981: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:38.982: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.982: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.982: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:38.982: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:38.982: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:38.982: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:38.982: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.982: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:38.982: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.983: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.983: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:38.983: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:38.983: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:38.983: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:38.983: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.983: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:38.983: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.983: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.984: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:38.984: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:38.984: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:38.984: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:38.984: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.984: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:38.984: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.984: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.985: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:38.985: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:38.985: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:38.985: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:38.985: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.985: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:38.985: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.985: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.986: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:38.986: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:38.986: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:38.986: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:38.986: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.986: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:38.986: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.986: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.987: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:38.987: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:38.987: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:38.987: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:38.987: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.987: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:38.987: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.987: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.988: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:38.988: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:38.988: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:38.988: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:38.988: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.988: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:38.988: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.988: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.989: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:38.989: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:38.989: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:38.989: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:38.989: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.989: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:38.989: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.989: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.989: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:38.990: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:38.990: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:38.990: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:38.990: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.990: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:38.990: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.990: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.990: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:38.990: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:38.990: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:38.990: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:38.990: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.990: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:38.991: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.991: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.991: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:38.991: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:38.991: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:38.991: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:38.991: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.991: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:38.992: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.992: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.992: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:38.992: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:38.992: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:38.992: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:38.992: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.992: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:38.993: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.993: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.993: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:38.993: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:38.993: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:38.993: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:38.993: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.993: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:38.994: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.994: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.994: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:38.994: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:38.994: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:38.994: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:38.994: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.994: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:38.995: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.995: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.995: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:38.995: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:38.995: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:38.995: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:38.995: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.995: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:38.996: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.996: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.996: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:38.996: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:38.996: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:38.996: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:38.996: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.996: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:38.997: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.997: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.997: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:38.997: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:38.997: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:38.997: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:38.997: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.997: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:38.997: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.997: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.998: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:38.998: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:38.998: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:38.998: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:38.998: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.998: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:38.998: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.998: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.999: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:38.999: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:38.999: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:38.999: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:38.999: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.999: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:38.999: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:38.999: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.000: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.000: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.000: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.000: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.000: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.000: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.000: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.000: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.001: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.001: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.001: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.001: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.001: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.001: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.001: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.001: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.002: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.002: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.002: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.002: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.002: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.002: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.002: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.002: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.003: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.003: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.003: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.003: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.003: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.003: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.003: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.003: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.004: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.004: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.004: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.004: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.004: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.004: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.004: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.004: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.005: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.005: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.005: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.005: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.005: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.005: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.005: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.005: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.006: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.006: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.006: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.006: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.006: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.006: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.006: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.006: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.007: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.007: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.007: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.007: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.007: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.007: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.007: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.007: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.008: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.008: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.008: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.008: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.008: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.008: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.008: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.008: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.009: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.009: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.009: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.009: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.009: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.009: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.009: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.009: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.010: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.010: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.010: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.010: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.010: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.010: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.010: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.010: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.011: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.011: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.011: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.011: [vfs7552] CAPTURE_NUM_STATES entering state 2 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.011: [vfs7552] REQUEST CHUNK entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.011: Sending vfs7552_read_image_chunk 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.011: [vfs7552] REQUEST CHUNK completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.011: [vfs7552] CAPTURE_NUM_STATES entering state 3 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.012: [vfs7552] CAPTURE_NUM_STATES entering state 2 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.012: [vfs7552] REQUEST CHUNK entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.012: Sending vfs7552_read_image_chunk 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.012: [vfs7552] REQUEST CHUNK completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.012: [vfs7552] CAPTURE_NUM_STATES entering state 3 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.013: [vfs7552] CAPTURE_NUM_STATES entering state 2 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.013: [vfs7552] REQUEST CHUNK entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.013: Sending vfs7552_read_image_chunk 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.013: [vfs7552] REQUEST CHUNK completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.013: [vfs7552] CAPTURE_NUM_STATES entering state 3 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.014: [vfs7552] CAPTURE_NUM_STATES entering state 4 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.014: Cleaning image 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.014: variance_after = 17 430s 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.014: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.014: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.014: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.014: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.014: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.015: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.015: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.015: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.015: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.015: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.015: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.015: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.015: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.016: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.016: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.016: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.016: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.016: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.016: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.016: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.016: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.017: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.017: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.017: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.017: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.017: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.017: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.017: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.017: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.017: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.017: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.017: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.017: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.017: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.018: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.018: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.018: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.018: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.018: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.018: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.018: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.018: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.018: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.019: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.019: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.019: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.019: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.019: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.019: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.019: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.019: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.020: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.020: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.020: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.020: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.020: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.020: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.020: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.020: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.021: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.021: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.021: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.021: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.021: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.021: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.021: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.021: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.022: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.022: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.022: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.022: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.022: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.022: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.022: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.022: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.023: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.023: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.023: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.023: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.023: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.023: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.023: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.023: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.024: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.024: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.024: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.024: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.024: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.024: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.024: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.024: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.025: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.025: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.025: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.025: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.025: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.025: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.025: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.025: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.026: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.026: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.026: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.026: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.026: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.026: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.026: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.026: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.027: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.027: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.027: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.027: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.027: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.027: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.027: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.027: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.028: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.028: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.028: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.028: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.028: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.028: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.028: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.028: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.029: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.029: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.029: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.029: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.029: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.029: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.029: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.029: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.030: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.030: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.030: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.030: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.030: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.030: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.030: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.030: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.031: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.031: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.031: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.031: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.031: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.031: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.031: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.031: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.032: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.032: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.032: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.032: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.032: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.032: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.032: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.032: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.033: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.033: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.033: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.033: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.033: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.033: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.033: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.033: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.034: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.034: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.034: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.034: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.034: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.034: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.034: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.034: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.035: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.035: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.035: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.035: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.035: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.035: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.035: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.035: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.036: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.036: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.036: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.036: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.036: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.036: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.036: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.036: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.037: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.037: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.037: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.037: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.037: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.037: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.037: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.037: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.038: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.038: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.038: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.038: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.038: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.038: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.038: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.038: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.039: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.039: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.039: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.039: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.039: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.039: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.039: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.039: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.040: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.040: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.040: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.040: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.040: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.040: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.040: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.040: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.041: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.041: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.041: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.041: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.041: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.041: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.041: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.041: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.042: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.042: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.042: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.042: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.042: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.042: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.042: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.042: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.042: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.042: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.043: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.043: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.043: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.043: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.043: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.043: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.043: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.043: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.044: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.044: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.044: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.044: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.044: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.044: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.044: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.044: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.045: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.045: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.045: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.045: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.045: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.045: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.045: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.045: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.046: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.046: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.046: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.046: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.046: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.046: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.046: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.046: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.047: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.047: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.047: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.047: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.047: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.047: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.047: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.047: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.048: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.048: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.048: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.048: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.048: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.048: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.048: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.048: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.049: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.049: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.049: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.049: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.049: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.049: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.049: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.049: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.049: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.050: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.050: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.050: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.050: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.050: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.050: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.050: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.051: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.051: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.051: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.051: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.051: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.051: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.051: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.051: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.052: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.052: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.052: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.052: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.052: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.052: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.052: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.052: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.052: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.052: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.052: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.052: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.052: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.052: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.053: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.053: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.053: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.053: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.053: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.053: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.053: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.053: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.054: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.054: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.054: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.054: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.054: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.054: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.054: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.054: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.055: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.055: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.055: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.055: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.055: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.055: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.055: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.055: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.056: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.056: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.056: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.056: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.056: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.056: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.056: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.056: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.057: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.057: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.057: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.057: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.057: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.057: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.057: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.057: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.058: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.058: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.058: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.058: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.058: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.058: [vfs7552] CAPTURE_NUM_STATES entering state 2 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.058: [vfs7552] REQUEST CHUNK entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.058: Sending vfs7552_read_image_chunk 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.059: [vfs7552] REQUEST CHUNK completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.059: [vfs7552] CAPTURE_NUM_STATES entering state 3 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.059: [vfs7552] CAPTURE_NUM_STATES entering state 2 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.059: [vfs7552] REQUEST CHUNK entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.059: Sending vfs7552_read_image_chunk 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.060: [vfs7552] REQUEST CHUNK completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.060: [vfs7552] CAPTURE_NUM_STATES entering state 3 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.060: [vfs7552] CAPTURE_NUM_STATES entering state 2 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.060: [vfs7552] REQUEST CHUNK entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.060: Sending vfs7552_read_image_chunk 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.061: [vfs7552] REQUEST CHUNK completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.061: [vfs7552] CAPTURE_NUM_STATES entering state 3 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.061: [vfs7552] CAPTURE_NUM_STATES entering state 4 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.061: Cleaning image 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.061: variance_after = 17 430s 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.061: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.061: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.061: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.062: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.062: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.062: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.062: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.062: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.062: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.062: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.062: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.063: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.063: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.063: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.063: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.063: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.063: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.063: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.063: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.064: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.064: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.064: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.064: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.064: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.064: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.064: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.064: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.065: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.065: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.065: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.065: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.065: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.065: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.065: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.065: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.066: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.066: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.066: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.066: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.066: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.066: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.066: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.066: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.067: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.067: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.067: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.067: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.067: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.067: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.067: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.067: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.068: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.068: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.068: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.068: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.068: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.068: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.068: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.068: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.069: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.069: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.069: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.069: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.069: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.069: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.069: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.069: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.070: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.070: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.070: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.070: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.070: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.070: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.070: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.070: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.071: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.071: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.071: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.071: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.071: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.071: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.071: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.071: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.072: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.072: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.072: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.072: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.072: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.072: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.072: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.072: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.073: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.073: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.073: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.073: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.073: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.073: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.073: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.073: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.073: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.073: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.074: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.074: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.074: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.074: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.074: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.074: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.074: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.074: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.075: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.075: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.075: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.075: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.075: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.075: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.075: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.075: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.076: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.076: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.076: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.076: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.076: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.076: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.076: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.076: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.077: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.077: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.077: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.077: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.077: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.077: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.077: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.077: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.078: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.078: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.078: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.078: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.078: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.078: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.078: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.078: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.079: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.079: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.079: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.079: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.079: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.079: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.079: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.079: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.080: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.080: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.080: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.080: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.080: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.080: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.080: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.080: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.081: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.081: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.081: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.081: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.081: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.081: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.081: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.081: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.081: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.081: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.081: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.081: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.082: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.082: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.082: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.082: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.082: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.082: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.082: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.082: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.082: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.082: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.083: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.083: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.083: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.083: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.083: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.083: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.083: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.083: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.084: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.084: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.084: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.084: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.084: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.084: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.084: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.084: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.085: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.085: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.085: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.085: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.085: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.085: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.085: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.085: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.086: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.086: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.086: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.086: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.086: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.086: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.086: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.086: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.087: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.087: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.087: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.087: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.087: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.087: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.087: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.087: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.088: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.088: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.088: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.088: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.088: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.088: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.088: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.088: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.089: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.089: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.089: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.089: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.089: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.089: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.089: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.089: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.089: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.089: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.090: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.090: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.090: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.090: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.090: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.090: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.090: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.090: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.091: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.091: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.091: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.091: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.091: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.091: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.091: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.091: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.092: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.092: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.092: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.092: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.092: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.092: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.092: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.092: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.093: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.093: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.093: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.093: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.093: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.093: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.093: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.093: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.094: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.094: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.094: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.094: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.094: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.094: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.094: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.094: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.095: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.095: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.095: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.095: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.095: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.095: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.095: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.095: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.096: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.096: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.096: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.096: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.096: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.096: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.096: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.096: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.097: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.097: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.097: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.097: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.097: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.097: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.097: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.097: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.098: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.098: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.098: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.098: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.098: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.098: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.099: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.099: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.099: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.099: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.099: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.099: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.099: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.099: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.100: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.100: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.100: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.100: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.100: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.100: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.100: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.100: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.101: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.101: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.101: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.101: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.101: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.101: [vfs7552] CAPTURE_NUM_STATES entering state 2 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.101: [vfs7552] REQUEST CHUNK entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.101: Sending vfs7552_read_image_chunk 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.102: [vfs7552] REQUEST CHUNK completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.102: [vfs7552] CAPTURE_NUM_STATES entering state 3 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.102: [vfs7552] CAPTURE_NUM_STATES entering state 2 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.102: [vfs7552] REQUEST CHUNK entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.102: Sending vfs7552_read_image_chunk 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.103: [vfs7552] REQUEST CHUNK completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.103: [vfs7552] CAPTURE_NUM_STATES entering state 3 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.103: [vfs7552] CAPTURE_NUM_STATES entering state 2 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.103: [vfs7552] REQUEST CHUNK entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.103: Sending vfs7552_read_image_chunk 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.104: [vfs7552] REQUEST CHUNK completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.104: [vfs7552] CAPTURE_NUM_STATES entering state 3 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.104: [vfs7552] CAPTURE_NUM_STATES entering state 4 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.104: Cleaning image 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.104: variance_after = 17 430s 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.104: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.104: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.104: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.105: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.105: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.105: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.105: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.105: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.105: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.105: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.105: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.106: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.106: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.106: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.106: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.106: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.106: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.106: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.106: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.107: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.107: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.107: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.107: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.107: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.107: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.107: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.107: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.108: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.108: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.108: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.108: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.108: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.108: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.108: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.108: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.109: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.109: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.110: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.110: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.110: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.110: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.110: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.110: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.110: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.110: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.111: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.111: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.111: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.111: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.111: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.111: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.111: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.111: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.112: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.112: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.112: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.112: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.112: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.112: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.112: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.112: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.113: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.113: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.113: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.113: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.113: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.113: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.113: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.113: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.113: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.113: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.113: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.113: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.113: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.113: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.114: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.114: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.115: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.115: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.115: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.115: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.115: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.115: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.115: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.115: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.115: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.115: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.115: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.116: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.116: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.116: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.116: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.116: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.117: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.117: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.117: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.117: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.117: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.117: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.117: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.117: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.117: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.118: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.118: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.118: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.118: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.118: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.118: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.118: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.118: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.118: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.118: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.118: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.118: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.118: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.119: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.119: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.119: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.119: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.119: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.119: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.119: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.119: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.120: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.120: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.120: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.120: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.120: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.120: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.120: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.120: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.121: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.121: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.121: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.121: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.121: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.121: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.121: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.121: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.122: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.122: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.123: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.123: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.123: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.123: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.123: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.123: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.123: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.123: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.123: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.124: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.124: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.124: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.124: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.124: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.124: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.124: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.124: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.124: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.124: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.124: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.124: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.124: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.125: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.125: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.125: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.125: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.125: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.125: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.125: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.125: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.126: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.126: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.126: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.126: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.126: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.126: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.126: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.126: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.127: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.127: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.127: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.127: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.127: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.127: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.127: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.127: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.128: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.128: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.128: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.128: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.128: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.128: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.128: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.128: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.129: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.129: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.129: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.129: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.129: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.129: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.129: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.129: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.130: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.130: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.131: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.131: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.131: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.131: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.131: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.131: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.131: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.131: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.132: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.132: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.132: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.132: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.132: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.132: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.132: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.132: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.133: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.133: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.133: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.133: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.133: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.133: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.133: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.133: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.134: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.134: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.134: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.134: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.134: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.134: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.134: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.134: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.135: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.135: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.135: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.135: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.135: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.135: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.135: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.135: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.136: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.136: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.136: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.136: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.136: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.136: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.136: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.136: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.137: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.137: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.137: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.137: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.137: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.137: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.137: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.137: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.138: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.138: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.138: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.138: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.138: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.138: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.138: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.138: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.139: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.139: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.139: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.139: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.139: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.139: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.139: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.139: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.139: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.139: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.139: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.139: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.140: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.140: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.140: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.140: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.140: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.140: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.140: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.140: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.140: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.140: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.141: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.141: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.141: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.141: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.141: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.141: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.141: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.141: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.142: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.142: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.142: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.142: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.142: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.142: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.142: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.142: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.143: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.143: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.143: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.143: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.143: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.143: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.143: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.143: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.144: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.144: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.144: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.144: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.144: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.144: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.144: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.144: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.145: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.145: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.145: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.145: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.145: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.145: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.145: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.145: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.146: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.146: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.146: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.146: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.146: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.146: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.146: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.146: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.147: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.147: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.147: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.147: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.147: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.147: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.147: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.147: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.148: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.148: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.148: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.148: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.148: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.148: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.148: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.148: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.149: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.149: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.149: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.149: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.149: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.149: [vfs7552] CAPTURE_NUM_STATES entering state 2 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.149: [vfs7552] REQUEST CHUNK entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.149: Sending vfs7552_read_image_chunk 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.150: [vfs7552] REQUEST CHUNK completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.150: [vfs7552] CAPTURE_NUM_STATES entering state 3 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.150: [vfs7552] CAPTURE_NUM_STATES entering state 2 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.150: [vfs7552] REQUEST CHUNK entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.150: Sending vfs7552_read_image_chunk 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.151: [vfs7552] REQUEST CHUNK completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.151: [vfs7552] CAPTURE_NUM_STATES entering state 3 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.151: [vfs7552] CAPTURE_NUM_STATES entering state 2 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.151: [vfs7552] REQUEST CHUNK entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.151: Sending vfs7552_read_image_chunk 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.152: [vfs7552] REQUEST CHUNK completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.152: [vfs7552] CAPTURE_NUM_STATES entering state 3 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.152: [vfs7552] CAPTURE_NUM_STATES entering state 4 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.152: Cleaning image 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.152: variance_after = 16 430s 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.152: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.152: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.152: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.153: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.153: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.153: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.153: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.153: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.153: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.153: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.153: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.154: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.154: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.154: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.154: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.154: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.154: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.154: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.154: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.155: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.155: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.155: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.155: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.155: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.155: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.155: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.155: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.156: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.156: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.156: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.156: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.156: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.156: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.156: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.156: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.157: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.157: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.157: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.157: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.157: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.157: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.157: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.157: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.158: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.158: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.158: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.158: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.158: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.158: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.158: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.158: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.159: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.159: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.159: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.159: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.159: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.159: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.159: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.159: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.160: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.160: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.160: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.160: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.160: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.160: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.160: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.160: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.161: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.161: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.161: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.161: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.161: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.161: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.161: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.161: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.162: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.162: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.162: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.162: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.162: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.162: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.162: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.162: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.163: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.163: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.163: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.163: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.163: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.163: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.163: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.163: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.164: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.164: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.164: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.164: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.164: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.164: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.164: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.164: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.165: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.165: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.165: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.165: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.165: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.165: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.165: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.165: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.166: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.166: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.166: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.166: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.166: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.166: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.166: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.166: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.167: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.167: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.167: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.167: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.167: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.167: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.167: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.167: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.168: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.168: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.168: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.168: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.168: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.168: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.168: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.168: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.169: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.169: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.169: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.169: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.169: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.169: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.169: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.169: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.170: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.170: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.170: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.170: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.170: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.170: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.170: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.170: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.170: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.170: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.171: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.171: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.171: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.171: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.171: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.171: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.171: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.171: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.172: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.172: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.172: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.172: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.172: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.172: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.172: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.172: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.173: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.173: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.173: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.173: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.173: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.173: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.173: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.173: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.174: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.174: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.174: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.174: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.174: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.174: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.174: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.174: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.175: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.175: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.175: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.175: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.175: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.175: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.175: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.175: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.176: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.176: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.176: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.176: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.176: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.176: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.176: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.176: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.177: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.177: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.177: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.177: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.177: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.177: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.177: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.177: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.178: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.178: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.178: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.178: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.178: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.178: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.178: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.178: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.179: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.179: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.179: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.179: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.179: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.179: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.179: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.179: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.179: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.179: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.179: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.179: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.179: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.180: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.180: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.180: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.181: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.181: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.181: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.181: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.181: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.181: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.181: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.181: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.181: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.181: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.181: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.181: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.181: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.181: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.182: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.182: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.182: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.182: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.182: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.182: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.182: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.182: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.183: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.183: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.183: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.183: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.183: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.183: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.183: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.183: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.184: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.184: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.184: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.184: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.184: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.184: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.184: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.184: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.185: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.185: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.185: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.185: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.185: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.185: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.185: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.185: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.186: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.186: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.186: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.186: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.186: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.186: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.186: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.186: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.187: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.187: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.187: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.187: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.187: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.187: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.187: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.187: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.188: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.188: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.188: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.188: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.188: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.188: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.188: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.188: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.189: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.189: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.189: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.189: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.189: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.189: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.189: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.189: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.189: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.189: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.190: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.190: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.190: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.190: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.190: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.190: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.190: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.190: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.191: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.191: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.191: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.191: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.191: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.191: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.191: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.191: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.192: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.192: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.192: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.192: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.192: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.192: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.192: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.192: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.193: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.193: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.193: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.193: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.193: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.193: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.194: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.194: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.194: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.194: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.194: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.194: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.194: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.194: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.195: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.195: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.195: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.195: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.195: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.195: [vfs7552] CAPTURE_NUM_STATES entering state 2 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.195: [vfs7552] REQUEST CHUNK entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.195: Sending vfs7552_read_image_chunk 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.195: [vfs7552] REQUEST CHUNK completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.195: [vfs7552] CAPTURE_NUM_STATES entering state 3 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.196: [vfs7552] CAPTURE_NUM_STATES entering state 2 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.196: [vfs7552] REQUEST CHUNK entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.196: Sending vfs7552_read_image_chunk 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.196: [vfs7552] REQUEST CHUNK completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.197: [vfs7552] CAPTURE_NUM_STATES entering state 3 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.197: [vfs7552] CAPTURE_NUM_STATES entering state 2 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.197: [vfs7552] REQUEST CHUNK entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.197: Sending vfs7552_read_image_chunk 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.198: [vfs7552] REQUEST CHUNK completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.198: [vfs7552] CAPTURE_NUM_STATES entering state 3 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.198: [vfs7552] CAPTURE_NUM_STATES entering state 4 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.198: Cleaning image 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.198: variance_after = 17 430s 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.198: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.198: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.198: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.199: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.199: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.199: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.199: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.199: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.199: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.199: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.199: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.200: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.200: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.200: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.200: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.200: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.200: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.200: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.200: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.201: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.201: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.201: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.201: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.201: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.201: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.201: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.201: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.202: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.202: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.202: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.202: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.202: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.202: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.202: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.202: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.203: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.203: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.203: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.203: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.203: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.203: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.203: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.203: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.204: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.204: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.204: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.204: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.204: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.204: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.204: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.204: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.205: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.205: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.205: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.205: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.205: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.205: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.205: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.205: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.206: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.206: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.206: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.206: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.206: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.206: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.206: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.206: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.206: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.207: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.207: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.207: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.207: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.207: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.207: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.207: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.207: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.207: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.208: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.208: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.208: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.208: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.208: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.208: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.208: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.208: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.209: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.209: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.209: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.209: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.209: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.209: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.209: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.209: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.210: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.210: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.210: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.210: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.210: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.210: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.210: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.210: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.211: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.211: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.211: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.211: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.211: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.211: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.211: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.211: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.212: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.212: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.212: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.212: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.212: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.212: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.212: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.212: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.213: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.213: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.213: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.213: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.213: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.213: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.213: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.213: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.214: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.214: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.214: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.214: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.214: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.214: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.215: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.215: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.215: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.215: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.215: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.215: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.215: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.215: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.216: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.216: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.216: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.216: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.216: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.216: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.216: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.216: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.217: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.217: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.217: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.217: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.217: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.217: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.217: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.217: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.218: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.218: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.218: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.218: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.218: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.218: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.218: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.218: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.219: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.219: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.219: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.219: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.219: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.219: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.219: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.219: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.220: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.220: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.220: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.220: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.220: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.220: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.220: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.220: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.220: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.220: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.221: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.221: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.221: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.221: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.221: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.221: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.221: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.221: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.222: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.222: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.222: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.222: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.222: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.222: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.222: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.222: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.223: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.223: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.223: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.223: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.223: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.223: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.223: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.223: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.224: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.224: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.224: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.224: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.224: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.224: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.224: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.224: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.225: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.225: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.225: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.225: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.225: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.225: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.225: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.225: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.226: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.226: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.226: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.226: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.226: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.226: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.226: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.226: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.227: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.227: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.227: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.227: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.227: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.227: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.227: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.227: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.228: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.228: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.228: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.228: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.228: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.228: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.228: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.228: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.229: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.229: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.229: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.229: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.229: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.229: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.229: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.229: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.230: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.230: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.230: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.230: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.230: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.230: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.230: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.230: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.231: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.231: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.231: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.231: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.231: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.231: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.231: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.231: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.232: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.232: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.232: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.232: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.232: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.232: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.232: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.232: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.233: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.233: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.233: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.233: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.233: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.233: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.234: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.234: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.235: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.235: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.235: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.235: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.235: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.235: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.235: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.235: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.236: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.236: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.236: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.236: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.236: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.236: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.236: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.236: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.237: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.237: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.237: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.237: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.237: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.237: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.237: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.237: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.237: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.238: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.238: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.238: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.238: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.238: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.238: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.238: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.238: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.238: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.238: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.238: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.238: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.238: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.239: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.239: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.239: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.239: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.239: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.239: [vfs7552] CAPTURE_NUM_STATES entering state 2 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.239: [vfs7552] REQUEST CHUNK entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.239: Sending vfs7552_read_image_chunk 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.240: [vfs7552] REQUEST CHUNK completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.240: [vfs7552] CAPTURE_NUM_STATES entering state 3 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.240: [vfs7552] CAPTURE_NUM_STATES entering state 2 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.240: [vfs7552] REQUEST CHUNK entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.240: Sending vfs7552_read_image_chunk 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.241: [vfs7552] REQUEST CHUNK completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.241: [vfs7552] CAPTURE_NUM_STATES entering state 3 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.241: [vfs7552] CAPTURE_NUM_STATES entering state 2 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.241: [vfs7552] REQUEST CHUNK entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.241: Sending vfs7552_read_image_chunk 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.242: [vfs7552] REQUEST CHUNK completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.242: [vfs7552] CAPTURE_NUM_STATES entering state 3 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.242: [vfs7552] CAPTURE_NUM_STATES entering state 4 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.242: Cleaning image 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.242: variance_after = 16 430s 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.242: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.242: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.242: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.243: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.243: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.243: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.243: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.243: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.243: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.243: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.243: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.244: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.244: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.244: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.244: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.244: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.244: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.244: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.244: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.245: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.245: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.245: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.245: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.245: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.245: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.245: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.245: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.246: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.246: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.246: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.246: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.246: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.246: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.246: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.246: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.247: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.247: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.247: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.247: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.247: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.247: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.247: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.247: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.248: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.248: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.248: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.248: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.248: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.248: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.248: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.248: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.249: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.249: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.249: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.249: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.249: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.249: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.250: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.250: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.250: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.250: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.250: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.250: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.250: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.250: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.250: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.250: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.251: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.251: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.251: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.251: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.251: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.251: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.251: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.251: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.252: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.252: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.252: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.252: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.252: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.252: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.252: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.252: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.253: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.253: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.253: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.253: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.253: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.253: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.253: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.253: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.254: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.254: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.254: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.254: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.254: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.254: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.254: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.254: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.255: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.255: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.255: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.255: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.255: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.255: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.255: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.255: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.256: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.256: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.256: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.256: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.256: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.256: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.256: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.256: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.257: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.257: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.257: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.257: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.257: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.257: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.257: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.257: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.258: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.258: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.258: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.258: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.258: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.258: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.258: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.258: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.259: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.259: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.259: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.259: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.259: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.259: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.259: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.259: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.260: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.260: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.260: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.260: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.260: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.260: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.260: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.260: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.261: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.261: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.261: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.261: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.261: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.261: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.261: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.261: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.262: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.262: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.262: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.262: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.262: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.262: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.262: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.262: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.263: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.263: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.263: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.263: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.263: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.263: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.263: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.263: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.264: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.264: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.264: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.264: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.264: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.264: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.264: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.264: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.265: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.265: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.265: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.265: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.265: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.265: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.265: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.265: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.266: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.266: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.266: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.266: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.266: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.266: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.266: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.266: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.267: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.267: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.268: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.268: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.268: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.268: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.268: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.268: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.268: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.268: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.269: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.269: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.269: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.269: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.269: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.269: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.269: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.269: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.269: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.269: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.269: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.269: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.269: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.269: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.270: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.270: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.270: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.270: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.270: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.270: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.270: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.270: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.271: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.271: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.271: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.271: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.271: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.271: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.271: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.271: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.272: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.272: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.272: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.272: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.272: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.272: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.272: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.272: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.273: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.273: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.273: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.273: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.273: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.273: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.273: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.273: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.274: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.274: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.275: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.275: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.275: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.275: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.275: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.275: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.275: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.275: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.276: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.276: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.276: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.276: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.276: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.276: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.276: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.276: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.277: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.277: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.277: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.277: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.277: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.277: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.277: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.277: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.278: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.278: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.278: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.278: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.278: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.278: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.278: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.278: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.279: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.279: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.279: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.279: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.279: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.279: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.279: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.279: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.280: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.280: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.280: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.280: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.280: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.280: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.280: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.280: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.281: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.281: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.281: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.281: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.281: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.281: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.281: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.281: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.281: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.281: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.281: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.281: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.281: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.281: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.282: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.282: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.282: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.282: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.282: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.282: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.282: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.282: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.283: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.283: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.283: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.283: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.283: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.283: [vfs7552] CAPTURE_NUM_STATES entering state 2 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.283: [vfs7552] REQUEST CHUNK entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.283: Sending vfs7552_read_image_chunk 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.284: [vfs7552] REQUEST CHUNK completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.284: [vfs7552] CAPTURE_NUM_STATES entering state 3 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.284: [vfs7552] CAPTURE_NUM_STATES entering state 2 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.284: [vfs7552] REQUEST CHUNK entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.284: Sending vfs7552_read_image_chunk 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.285: [vfs7552] REQUEST CHUNK completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.285: [vfs7552] CAPTURE_NUM_STATES entering state 3 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.285: [vfs7552] CAPTURE_NUM_STATES entering state 2 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.285: [vfs7552] REQUEST CHUNK entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.285: Sending vfs7552_read_image_chunk 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.286: [vfs7552] REQUEST CHUNK completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.286: [vfs7552] CAPTURE_NUM_STATES entering state 3 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.286: [vfs7552] CAPTURE_NUM_STATES entering state 4 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.286: Cleaning image 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.286: variance_after = 2168 430s 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.286: [vfs7552] CAPTURE_NUM_STATES completed successfully 430s (process:2292): libfprint-device-DEBUG: 00:54:39.286: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 430s (process:2292): libfprint-image_device-DEBUG: 00:54:39.286: Image device reported finger status: on 430s (process:2292): libfprint-image_device-DEBUG: 00:54:39.286: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.336: changing to 2 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.337: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.337: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.337: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.337: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.337: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.338: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.338: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.338: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.338: [vfs7552] CAPTURE_NUM_STATES entering state 2 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.338: [vfs7552] REQUEST CHUNK entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.338: Sending vfs7552_read_image_chunk 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.338: [vfs7552] REQUEST CHUNK completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.338: [vfs7552] CAPTURE_NUM_STATES entering state 3 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.339: [vfs7552] CAPTURE_NUM_STATES entering state 2 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.339: [vfs7552] REQUEST CHUNK entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.339: Sending vfs7552_read_image_chunk 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.339: [vfs7552] REQUEST CHUNK completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.339: [vfs7552] CAPTURE_NUM_STATES entering state 3 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.340: [vfs7552] CAPTURE_NUM_STATES entering state 2 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.340: [vfs7552] REQUEST CHUNK entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.340: Sending vfs7552_read_image_chunk 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.340: [vfs7552] REQUEST CHUNK completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.340: [vfs7552] CAPTURE_NUM_STATES entering state 3 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.341: [vfs7552] CAPTURE_NUM_STATES entering state 4 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.341: Cleaning image 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.341: variance_after = 2082 430s 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.341: [vfs7552] CAPTURE_NUM_STATES completed successfully 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.341: Image captured 430s (process:2292): libfprint-image_device-DEBUG: 00:54:39.341: Image device captured an image 430s (process:2292): libfprint-image_device-DEBUG: 00:54:39.342: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 430s (process:2292): libfprint-device-DEBUG: 00:54:39.342: Device reported finger status change: FP_FINGER_STATUS_PRESENT 430s (process:2292): libfprint-image-DEBUG: 00:54:39.360: Minutiae scan completed in 0.017778 secs 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.391: changing to 3 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.391: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.391: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.391: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.392: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.392: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.392: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.392: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.392: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.392: [vfs7552] CAPTURE_NUM_STATES entering state 2 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.392: [vfs7552] REQUEST CHUNK entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.392: Sending vfs7552_read_image_chunk 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.392: [vfs7552] REQUEST CHUNK completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.392: [vfs7552] CAPTURE_NUM_STATES entering state 3 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.393: [vfs7552] CAPTURE_NUM_STATES entering state 2 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.393: [vfs7552] REQUEST CHUNK entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.393: Sending vfs7552_read_image_chunk 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.393: [vfs7552] REQUEST CHUNK completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.393: [vfs7552] CAPTURE_NUM_STATES entering state 3 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.394: [vfs7552] CAPTURE_NUM_STATES entering state 2 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.394: [vfs7552] REQUEST CHUNK entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.394: Sending vfs7552_read_image_chunk 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.395: [vfs7552] REQUEST CHUNK completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.395: [vfs7552] CAPTURE_NUM_STATES entering state 3 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.395: [vfs7552] CAPTURE_NUM_STATES entering state 4 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.395: Cleaning image 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.395: variance_after = 2003 430s 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.395: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.395: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.395: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.396: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.396: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.396: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.396: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.396: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.396: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.396: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.396: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.397: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.397: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.397: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.397: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.397: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.397: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.397: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.397: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.397: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.397: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.398: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.398: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.398: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.398: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.398: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.398: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.399: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.399: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.399: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.399: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.399: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.399: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.399: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.399: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.399: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.399: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.400: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.400: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.400: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.400: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.400: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.400: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.400: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.400: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.401: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.401: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.401: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.401: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.401: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.401: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.401: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.401: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.402: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.402: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.402: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.402: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.402: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.402: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.402: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.402: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.403: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.403: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.403: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.403: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.403: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.403: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.403: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.403: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.404: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.404: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.404: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.404: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.404: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.404: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.404: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.404: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.405: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.405: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.405: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.405: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.405: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.405: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.405: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.405: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.406: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.406: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.406: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.406: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.406: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.406: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.406: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.406: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.406: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.406: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.406: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.406: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.407: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.407: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.407: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.407: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.407: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.407: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.407: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.407: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.407: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.407: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.408: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.408: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.408: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.408: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.408: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.408: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.408: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.408: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.409: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.409: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.409: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.409: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.409: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.409: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.409: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.409: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.410: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.410: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.410: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.410: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.410: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.410: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.410: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.410: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.411: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.411: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.411: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.411: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.411: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.411: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.411: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.411: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.412: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.412: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.412: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.412: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.412: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.412: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.412: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.412: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.413: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.413: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.413: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.413: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.413: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.413: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.413: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.413: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.414: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.414: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.414: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.414: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.414: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.414: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.414: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.414: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.414: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.414: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.415: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.415: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.415: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.415: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.415: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.415: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.415: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.415: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.416: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.416: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.416: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.416: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.416: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.416: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.416: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.416: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.417: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.417: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.417: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.417: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.417: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.417: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.417: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.417: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.418: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.418: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.418: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.418: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.418: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.418: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.418: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.418: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.419: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.419: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.419: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.419: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.419: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.419: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.419: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.419: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.420: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.420: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.420: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.420: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.420: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.420: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.420: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.420: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.421: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.421: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.421: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.421: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.421: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.421: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.421: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.421: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.421: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.421: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.421: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.421: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.421: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.421: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.422: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.422: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.422: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.422: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.422: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.422: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.422: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.422: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.423: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.423: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.423: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.423: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.423: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.423: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.423: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.423: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.424: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.424: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.424: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.424: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.424: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.424: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.424: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.424: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.425: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.425: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.425: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.425: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.425: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.425: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.425: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.425: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.426: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.426: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.426: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.426: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.426: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.426: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.426: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.426: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.427: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.427: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.427: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.427: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.427: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.427: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.427: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.427: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.428: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.428: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.428: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.428: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.428: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.428: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.428: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.428: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.428: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.429: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.429: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.429: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.429: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.429: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.429: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.429: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.429: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.429: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.430: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.430: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.430: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.430: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.430: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.430: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.430: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.430: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.431: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.431: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.431: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.431: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.431: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.431: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.431: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.431: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.432: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.432: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.432: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.432: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.432: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.432: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.432: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.432: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.433: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.433: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.433: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.433: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.433: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.433: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.433: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.433: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.434: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.434: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.434: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.434: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.434: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.434: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.434: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.434: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.435: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.435: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.435: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.435: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.435: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.435: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.435: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.435: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.435: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.436: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.436: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.436: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.436: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.436: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.436: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.436: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.436: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.436: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.436: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.436: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.436: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.436: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.437: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.437: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.437: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.437: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.437: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.437: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.437: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.437: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.438: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.438: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.438: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.438: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.438: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.438: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.438: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.438: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.439: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.439: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.439: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.439: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.439: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.439: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.439: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.439: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.440: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.440: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.440: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.440: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.440: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.440: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.440: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.440: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.441: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.441: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.441: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.441: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.441: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.441: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.441: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.441: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.442: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.442: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.442: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.442: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.442: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.442: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.442: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.442: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.443: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.443: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.443: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.443: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.443: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.443: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.443: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.443: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.444: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.444: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.444: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.444: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.444: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.444: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.444: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.444: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.444: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.444: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.445: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.445: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.445: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.445: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.445: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.445: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.445: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.445: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.446: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.446: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.446: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.446: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.446: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.446: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.446: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.446: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.447: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.447: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.447: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.447: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.447: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.447: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.447: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.447: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.448: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.448: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.448: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.448: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.448: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.448: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.448: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.448: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.449: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.449: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.449: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.449: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.449: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.449: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.449: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.449: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.450: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.450: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.450: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.450: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.450: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.450: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.450: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.450: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.451: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.451: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.451: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.451: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.451: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.451: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.451: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.451: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.452: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.452: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.452: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.452: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.452: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.452: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.452: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.452: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.453: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.453: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.453: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.453: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.453: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.453: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.453: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.453: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.454: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.454: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.454: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.454: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.454: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.454: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.454: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.454: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.454: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.455: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.455: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.455: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.455: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.455: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.455: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.455: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.455: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.455: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.455: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.455: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.455: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.455: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.456: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.456: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.457: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.457: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.457: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.457: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.457: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.457: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.458: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.458: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.458: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.458: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.458: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.458: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.458: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.458: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.459: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.459: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.460: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.460: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.460: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.460: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.460: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.460: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.460: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.460: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.460: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.461: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.461: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.461: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.461: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.461: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.461: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.461: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.461: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.461: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.461: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.461: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.461: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.461: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.462: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.462: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.462: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.462: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.462: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.462: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.462: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.462: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.463: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.463: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.463: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.463: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.463: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.463: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.463: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.463: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.464: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.464: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.464: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.464: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.464: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.464: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.464: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.464: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.465: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.465: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.465: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.465: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.465: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.465: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.465: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.465: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.466: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.466: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.466: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.466: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.466: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.466: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.466: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.466: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.467: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.467: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.467: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.467: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.467: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.467: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.467: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.467: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.468: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.468: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.468: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.468: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.468: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.468: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.468: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.468: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.469: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.469: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.469: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.469: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.469: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.469: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.469: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.469: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.470: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.470: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.470: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.470: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.470: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.470: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.470: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.470: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.471: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.471: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.472: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.472: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.472: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.472: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.472: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.472: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.472: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.472: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.473: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.473: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.473: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.473: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.473: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.473: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.473: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.473: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.474: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.474: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.474: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.474: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.474: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.474: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.474: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.474: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.475: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.475: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.475: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.475: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.475: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.475: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.475: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.475: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.476: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.476: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.476: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.476: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.476: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.476: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.476: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.476: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.477: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.477: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.477: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.477: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.477: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.477: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.477: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.477: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.478: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.478: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.478: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.478: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.478: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.478: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.478: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.478: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.479: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.479: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.479: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.479: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.479: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.479: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.479: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.479: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.480: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.480: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.480: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.480: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.480: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.480: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.480: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.480: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.481: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.481: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.481: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.481: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.481: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.481: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.481: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.481: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.482: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.482: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.482: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.482: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.482: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.482: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.482: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.482: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.483: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.483: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.483: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.483: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.483: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.483: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.483: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.483: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.484: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.484: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.484: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.484: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.484: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.484: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.484: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.484: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.485: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.485: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.485: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.485: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.485: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.485: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.485: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.485: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.486: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.486: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.486: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.486: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.486: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.486: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.486: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.486: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.487: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.487: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.487: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.487: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.487: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.487: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.487: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.487: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.488: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.488: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.488: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.488: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.488: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.488: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.488: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.488: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.489: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.489: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.489: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.489: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.489: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.489: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.489: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.489: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.490: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.490: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.490: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.490: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.490: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.490: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.490: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.490: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.491: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.491: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.491: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.491: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.491: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.491: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.491: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.491: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.492: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.492: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.492: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.492: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.492: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.492: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.492: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.492: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.493: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.493: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.493: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.493: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.493: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.493: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.493: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.493: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.494: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.494: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.494: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.494: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.494: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.494: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.494: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.494: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.495: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.495: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.495: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.495: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.495: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.495: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.495: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.495: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.496: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.496: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.496: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.496: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.496: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.496: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.496: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.496: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.497: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.497: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.497: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.497: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.497: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.497: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.497: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.497: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.498: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.498: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.498: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.498: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.498: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.498: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.498: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.498: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.499: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.499: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.499: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.499: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.499: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.499: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.499: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.499: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.500: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.500: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.500: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.500: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.500: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.500: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.500: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.500: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.501: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.501: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.501: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.501: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.501: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.501: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.501: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.501: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.502: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.502: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.502: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.502: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.502: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.502: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.502: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.502: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.503: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.503: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.503: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.503: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.503: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.503: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.503: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.503: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.504: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.504: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.504: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.504: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.504: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.504: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.504: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.504: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.504: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.504: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.505: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.505: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.505: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.505: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.505: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.505: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.505: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.505: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.505: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.505: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.505: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.505: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.506: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.506: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.507: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.507: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.507: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.507: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.507: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.507: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.507: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.508: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.508: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.508: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.508: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.508: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.508: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.508: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.509: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.509: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.509: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.509: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.509: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.509: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.509: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.509: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.510: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.510: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.510: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.510: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.510: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.510: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.510: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.510: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.511: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.511: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.511: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.511: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.511: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.511: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.511: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.511: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.512: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.512: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.512: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.512: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.512: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.512: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.512: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.512: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.512: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.512: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.513: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.513: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.513: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.513: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.513: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.513: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.513: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.513: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.514: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.514: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.514: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.514: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.514: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.514: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.514: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.514: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.515: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.515: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.515: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.515: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.515: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.515: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.515: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.515: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.516: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.516: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.516: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.516: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.516: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.516: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.516: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.516: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.517: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.517: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.517: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.517: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.517: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.517: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.517: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.517: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.518: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.518: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.518: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.518: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.518: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.518: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.519: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.519: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.519: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.519: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.519: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.519: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.519: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.519: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.520: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.520: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.520: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.520: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.520: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.520: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.520: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.520: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.520: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.520: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.521: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.521: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.521: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.521: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.521: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.521: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.521: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.521: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.522: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.522: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.522: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.522: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.522: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.522: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.522: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.522: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.523: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.523: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.523: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.523: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.523: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.523: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.523: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.523: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.524: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.524: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.524: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.524: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.524: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.524: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.524: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.524: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.528: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.528: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.528: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.528: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.528: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.528: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.529: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.529: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.530: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.530: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.530: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.530: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.530: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.530: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.530: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.530: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.531: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.531: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.531: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.531: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.531: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.531: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.532: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.532: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.532: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.532: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.532: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.532: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.532: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.532: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.533: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.533: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.535: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.535: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.535: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.535: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.535: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.535: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.536: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.536: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.536: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.536: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.536: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.536: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.536: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.536: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.537: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.537: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.537: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.537: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.537: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.537: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.537: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.537: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.538: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.538: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.538: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.538: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.538: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.538: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.538: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.538: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.539: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.539: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.539: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.539: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.539: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.539: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.539: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.539: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.541: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.541: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.542: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.542: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.542: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.542: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.542: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.542: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.543: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.543: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.544: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.544: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.544: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.544: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.544: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.544: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.544: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.544: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.545: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.545: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.545: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.545: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.545: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.545: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.545: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.545: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.546: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.546: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.546: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.546: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.546: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.546: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.546: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.546: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.547: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.547: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.547: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.547: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.547: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.547: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.547: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.547: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.548: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.548: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.548: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.548: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.548: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.548: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.548: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.548: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.549: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.549: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.549: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.549: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.549: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.549: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.549: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.549: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.550: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.550: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.550: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.550: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.550: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.550: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.550: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.550: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.551: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.551: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.551: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.551: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.551: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.551: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.551: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.551: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.552: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.552: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.552: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.552: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.552: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.552: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.552: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.552: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.553: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.553: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.553: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.553: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.553: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.553: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.553: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.553: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.554: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.554: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.554: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.554: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.554: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.554: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.554: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.554: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.555: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.555: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.555: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.555: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.555: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.555: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.555: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.555: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.556: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.556: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.556: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.556: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.556: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.556: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.556: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.556: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.557: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.557: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.557: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.557: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.557: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.557: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.557: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.557: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.558: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.558: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.558: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.558: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.558: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.558: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.558: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.558: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.559: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.559: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.559: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.559: [vfs7552] CAPTURE_NUM_STATES entering state 2 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.559: [vfs7552] REQUEST CHUNK entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.559: Sending vfs7552_read_image_chunk 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.559: [vfs7552] REQUEST CHUNK completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.559: [vfs7552] CAPTURE_NUM_STATES entering state 3 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.560: [vfs7552] CAPTURE_NUM_STATES entering state 2 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.560: [vfs7552] REQUEST CHUNK entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.560: Sending vfs7552_read_image_chunk 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.560: [vfs7552] REQUEST CHUNK completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.560: [vfs7552] CAPTURE_NUM_STATES entering state 3 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.561: [vfs7552] CAPTURE_NUM_STATES entering state 2 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.561: [vfs7552] REQUEST CHUNK entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.561: Sending vfs7552_read_image_chunk 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.561: [vfs7552] REQUEST CHUNK completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.561: [vfs7552] CAPTURE_NUM_STATES entering state 3 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.562: [vfs7552] CAPTURE_NUM_STATES entering state 4 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.562: Cleaning image 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.562: variance_after = 1737 430s 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.562: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.562: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.562: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.562: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.562: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.563: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.563: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.563: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.563: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.563: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.563: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.563: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.563: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.564: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.564: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.564: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.564: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.564: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.564: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.564: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.564: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.565: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.565: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.565: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.565: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.565: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.565: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.565: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.565: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.566: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.566: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.566: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.566: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.566: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.566: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.566: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.566: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.567: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.567: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.567: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.567: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.567: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.567: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.567: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.567: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.568: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.568: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.568: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.568: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.568: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.568: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.569: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.569: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.569: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.569: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.569: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.569: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.569: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.569: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.569: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.569: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.570: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.570: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.570: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.570: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.570: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.570: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.571: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.571: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.571: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.571: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.571: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.571: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.571: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.571: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.572: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.572: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.572: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.572: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.572: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.572: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.572: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.572: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.572: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.573: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.573: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.573: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.573: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.573: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.573: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.573: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.573: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.573: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.574: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.574: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.574: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.574: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.574: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.574: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.574: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.574: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.575: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.575: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.575: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.575: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.575: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.575: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.575: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.575: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.576: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.576: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.576: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.576: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.576: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.576: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.576: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.576: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.577: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.577: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.577: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.577: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.577: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.577: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.577: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.577: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.578: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.578: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.578: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.578: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.578: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.578: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.579: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.579: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.579: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.579: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.579: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.579: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.579: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.579: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.580: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.580: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.580: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.580: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.580: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.580: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.580: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.580: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.581: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.581: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.581: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.581: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.581: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.581: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.581: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.581: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.582: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.582: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.582: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.582: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.582: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.582: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.582: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.582: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.583: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.583: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.583: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.583: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.583: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.583: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.583: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.583: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.584: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.584: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.584: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.584: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.584: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.584: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.584: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.584: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.585: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.585: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.585: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.585: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.585: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.585: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.585: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.585: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.586: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.586: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.586: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.586: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.586: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.586: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.586: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.586: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.587: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.587: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.587: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.587: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.587: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.587: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.587: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.587: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.588: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.588: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.588: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.588: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.588: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.588: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.588: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.588: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.589: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.589: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.589: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.589: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.589: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.589: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.589: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.589: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.590: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.590: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.590: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.590: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.590: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.590: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.590: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.590: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.591: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.591: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.591: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.591: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.591: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.591: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.591: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.591: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.592: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.592: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.592: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.592: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.592: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.592: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.592: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.592: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.593: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.593: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.593: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.593: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.593: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.593: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.593: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.593: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.594: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.594: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.594: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.594: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.594: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.594: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.594: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.594: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.595: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.595: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.595: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.595: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.595: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.595: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.595: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.595: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.596: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.596: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.596: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.596: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.596: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.596: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.596: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.596: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.596: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.596: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.597: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.597: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.597: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.597: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.597: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.597: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.597: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.597: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.598: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.598: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.598: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.598: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.598: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.598: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.598: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.598: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.599: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.599: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.599: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.599: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.599: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.599: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.599: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.599: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.600: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.600: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.600: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.600: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.600: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.600: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.600: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.600: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.601: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.601: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.601: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.601: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.601: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.601: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.601: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.601: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.602: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.602: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.602: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.602: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.602: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.602: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.602: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.602: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.603: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.603: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.603: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.603: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.603: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.603: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.604: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.604: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.604: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.604: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.604: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.604: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.604: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.604: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.604: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.604: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.605: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.605: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.605: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.605: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.605: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.605: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.605: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.605: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.606: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.606: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.606: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.606: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.606: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.606: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.606: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.606: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.607: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.607: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.607: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.607: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.607: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.607: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.607: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.607: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.608: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.608: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.608: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.608: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.608: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.608: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.608: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.608: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.609: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.609: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.609: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.609: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.609: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.609: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.609: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.609: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.610: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.610: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.610: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.610: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.610: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.610: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.610: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.611: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.611: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.611: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.611: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.611: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.611: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.611: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.611: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.612: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.612: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.612: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.612: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.612: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.612: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.612: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.613: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.613: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.613: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.613: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.613: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.613: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.613: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.613: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.614: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.614: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.614: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.614: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.614: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.614: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.614: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.614: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.614: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.615: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.615: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.615: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.615: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.615: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.615: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.615: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.615: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.615: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.616: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.616: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.616: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.616: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.616: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.616: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.616: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.616: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.617: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.617: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.617: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.617: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.617: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.617: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.617: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.617: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.618: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.618: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.618: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.618: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.618: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.618: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.618: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.618: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.619: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.619: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.619: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.619: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.619: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.619: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.619: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.619: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.620: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.620: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.620: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.620: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.620: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.620: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.620: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.620: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.621: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.621: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.621: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.621: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.621: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.621: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.621: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.621: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.622: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.622: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.622: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.622: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.622: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.622: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.622: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.622: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.623: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.623: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.623: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.623: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.623: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.623: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.623: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.623: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.624: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.624: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.624: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.624: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.624: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.624: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.624: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.624: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.625: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.625: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.625: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.625: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.625: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.625: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.625: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.625: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.626: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.626: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.626: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.626: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.626: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.626: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.626: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.626: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.627: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.627: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.627: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.627: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.627: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.627: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.627: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.627: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.628: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.628: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.628: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.628: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.628: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.628: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.628: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.628: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.629: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.629: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.629: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.629: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.629: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.629: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.629: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.629: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.630: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.630: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.630: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.630: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.630: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.630: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.630: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.630: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.630: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.631: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.631: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.631: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.631: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.631: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.631: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.631: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.631: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.631: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.631: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.631: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.631: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.631: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.632: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.632: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.632: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.632: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.632: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.632: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.632: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.632: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.633: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.633: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.633: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.633: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.633: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.633: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.633: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.633: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.634: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.634: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.634: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.634: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.634: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.634: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.634: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.634: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.635: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.635: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.635: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.635: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.635: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.635: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.635: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.635: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.636: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.636: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.636: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.636: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.636: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.636: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.636: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.636: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.637: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.637: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.637: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.637: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.637: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.637: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.637: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.637: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.638: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.638: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.638: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.638: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.638: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.638: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.638: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.638: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.639: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.639: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.639: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.639: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.639: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.639: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.639: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.639: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.640: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.640: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.640: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.640: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.640: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.640: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.640: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.640: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.641: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.641: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.641: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.641: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.641: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.641: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.641: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.641: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.642: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.642: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.642: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.642: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.642: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.642: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.642: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.642: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.643: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.643: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.643: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.643: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.643: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.643: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.643: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.643: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.644: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.644: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.644: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.644: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.644: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.644: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.644: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.644: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.645: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.645: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.645: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.645: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.645: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.645: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.645: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.645: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.646: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.646: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.646: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.646: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.646: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.646: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.646: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.646: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.647: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.647: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.647: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.647: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.647: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.647: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.647: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.647: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.648: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.648: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.648: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.648: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.648: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.648: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.648: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.648: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.649: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.649: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.649: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.649: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.649: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.649: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.649: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.649: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.650: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.650: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.650: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.650: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.650: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.650: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.650: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.650: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.651: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.651: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.651: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.651: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.651: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.651: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.651: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.651: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.652: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.652: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.652: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.652: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.652: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.652: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.652: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.652: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.653: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.653: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.653: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.653: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.653: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.653: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.653: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.653: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.654: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.654: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.654: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.654: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.654: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.654: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.654: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.654: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.655: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.655: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.655: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.655: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.655: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.655: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.655: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.655: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.656: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.656: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.656: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.656: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.656: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.656: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.656: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.656: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.657: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.657: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.657: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.657: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.657: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.657: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.657: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.657: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.658: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.658: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.658: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.658: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.658: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.658: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.658: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.658: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.659: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.659: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.659: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.659: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.659: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.659: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.659: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.659: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.660: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.660: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.660: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.660: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.660: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.660: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.660: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.660: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.660: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.660: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.661: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.661: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.661: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.661: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.661: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.661: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.661: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.661: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.662: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.662: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.662: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.662: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.662: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.662: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.662: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.662: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.663: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.663: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.663: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.663: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.663: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.663: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.663: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.663: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.664: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.664: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.664: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.664: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.664: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.664: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.664: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.664: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.665: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.665: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.665: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.665: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.665: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.665: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.665: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.665: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.666: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.666: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.666: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.666: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.666: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.666: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.666: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.666: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.667: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.667: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.667: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.667: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.667: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.667: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.667: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.667: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.668: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.668: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.668: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.668: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.668: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.668: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.668: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.668: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.669: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.669: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.669: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.669: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.669: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.669: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.669: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.669: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.670: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.670: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.670: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.670: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.670: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.670: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.670: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.670: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.671: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.671: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.671: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.671: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.671: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.671: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.671: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.671: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.672: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.672: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.672: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.672: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.672: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.672: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.672: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.672: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.673: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.673: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.673: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.673: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.673: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.673: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.673: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.673: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.674: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.674: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.674: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.674: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.674: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.674: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.674: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.674: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.674: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.675: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.675: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.675: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.675: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.675: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.675: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.675: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.675: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.675: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.675: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.675: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.675: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.675: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.676: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.676: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.676: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.676: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.676: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.676: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.676: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.676: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.677: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.677: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.677: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.677: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.677: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.677: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.677: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.677: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.678: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.678: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.678: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.678: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.678: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.678: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.678: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.678: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.679: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.679: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.679: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.679: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.679: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.679: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.679: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.679: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.680: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.680: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.680: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.680: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.680: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.680: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.680: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.680: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.681: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.681: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.681: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.681: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.681: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.681: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.681: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.681: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.682: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.682: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.682: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.682: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.682: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.682: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.682: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.682: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.683: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.683: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.683: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.683: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.683: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.683: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.683: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.683: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.684: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.684: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.684: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.684: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.684: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.684: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.684: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.684: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.684: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.684: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.685: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.685: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.685: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.685: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.685: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.685: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.685: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.685: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.686: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.686: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.686: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.686: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.686: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.686: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.686: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.686: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.687: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.687: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.687: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.687: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.687: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.687: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.687: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.687: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.688: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.688: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.688: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.688: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.688: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.688: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.688: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.689: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.689: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.689: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.689: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.689: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.689: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.689: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.689: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.689: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.690: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.690: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.690: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.690: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.690: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.690: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.690: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.690: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.691: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.691: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.691: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.691: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.691: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.691: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.691: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.691: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.692: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.692: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.692: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.692: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.692: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.692: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.692: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.692: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.693: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.693: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.693: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.693: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.693: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.693: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.693: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.693: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.694: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.694: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.694: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.694: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.694: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.694: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.694: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.694: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.695: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.695: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.695: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.695: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.695: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.695: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.695: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.695: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.696: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.696: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.696: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.696: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.696: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.696: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.696: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.696: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.697: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.697: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.697: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.697: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.697: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.697: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.697: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.697: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.698: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.698: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.698: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.698: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.698: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.698: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.698: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.698: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.699: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.699: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.699: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.699: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.699: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.699: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.699: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.699: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.700: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.700: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.700: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.700: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.700: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.700: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.700: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.700: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.701: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.701: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.701: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.701: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.701: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.701: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.701: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.701: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.701: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.702: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.702: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.702: [vfs7552] CAPTURE_NUM_STATES entering state 2 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.702: [vfs7552] REQUEST CHUNK entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.702: Sending vfs7552_read_image_chunk 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.702: [vfs7552] REQUEST CHUNK completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.702: [vfs7552] CAPTURE_NUM_STATES entering state 3 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.703: [vfs7552] CAPTURE_NUM_STATES entering state 2 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.703: [vfs7552] REQUEST CHUNK entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.703: Sending vfs7552_read_image_chunk 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.703: [vfs7552] REQUEST CHUNK completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.703: [vfs7552] CAPTURE_NUM_STATES entering state 3 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.704: [vfs7552] CAPTURE_NUM_STATES entering state 2 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.704: [vfs7552] REQUEST CHUNK entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.704: Sending vfs7552_read_image_chunk 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.704: [vfs7552] REQUEST CHUNK completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.704: [vfs7552] CAPTURE_NUM_STATES entering state 3 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.705: [vfs7552] CAPTURE_NUM_STATES entering state 4 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.705: Cleaning image 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.705: variance_after = 1526 430s 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.705: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.705: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.705: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.705: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.705: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.706: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.706: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.706: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.706: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.706: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.706: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.706: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.706: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.707: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.707: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.707: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.707: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.707: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.707: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.707: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.707: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.708: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.708: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.708: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.708: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.708: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.708: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.708: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.708: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.709: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.709: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.709: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.709: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.709: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.709: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.709: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.709: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.709: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.709: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.709: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.709: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.709: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.709: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.710: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.710: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.710: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.710: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.710: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.710: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.710: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.710: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.711: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.711: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.711: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.711: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.711: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.711: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.711: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.711: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.712: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.712: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.712: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.712: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.712: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.712: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.712: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.712: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.713: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.713: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.713: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.713: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.713: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.713: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.713: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.713: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.714: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.714: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.714: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.714: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.714: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.714: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.714: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.714: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.715: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.715: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.715: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.715: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.715: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.715: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.715: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.715: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.716: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.716: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.716: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.716: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.716: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.716: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.716: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.716: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.717: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.717: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.717: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.717: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.717: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.717: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.717: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.717: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.718: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.718: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.718: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.718: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.718: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.718: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.718: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.718: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.718: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.718: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.719: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.719: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.719: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.719: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.719: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.719: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.719: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.719: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.720: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.720: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.720: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.720: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.720: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.720: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.720: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.720: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.721: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.721: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.721: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.721: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.721: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.721: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.721: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.721: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.722: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.722: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.722: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.722: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.722: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.722: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.722: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.722: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.723: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.723: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.723: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.723: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.723: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.723: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.723: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.723: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.724: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.724: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.724: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.724: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.724: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.724: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.725: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.725: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.725: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.725: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.725: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.725: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.725: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.725: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.725: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.726: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.726: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.726: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.726: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.726: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.726: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.726: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.726: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.726: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.727: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.727: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.727: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.727: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.727: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.727: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.727: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.727: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.728: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.728: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.728: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.728: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.728: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.728: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.728: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.728: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.729: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.729: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.729: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.729: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.729: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.729: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.729: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.729: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.730: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.730: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.730: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.730: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.730: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.730: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.730: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.730: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.731: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.731: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.731: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.731: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.731: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.731: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.731: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.731: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.732: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.732: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.732: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.732: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.732: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.732: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.732: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.732: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.733: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.733: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.733: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.733: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.733: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.733: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.733: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.733: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.734: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.734: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.734: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.734: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.734: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.734: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.734: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.734: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.735: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.735: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.735: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.735: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.735: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.735: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.735: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.735: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.735: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.735: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.735: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.735: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.735: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.735: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.736: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.736: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.736: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.736: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.736: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.736: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.736: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.736: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.737: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.737: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.737: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.737: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.737: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.737: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.737: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.737: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.738: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.738: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.738: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.738: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.738: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.738: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.738: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.738: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.739: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.739: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.739: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.739: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.739: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.739: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.739: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.739: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.740: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.740: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.740: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.740: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.740: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.740: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.740: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.740: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.741: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.741: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.741: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.741: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.741: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.741: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.741: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.741: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.742: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.742: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.742: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.742: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.742: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.742: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.742: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.742: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.743: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.743: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.743: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.743: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.743: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.743: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.743: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.743: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.744: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.744: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.744: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.744: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.744: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.744: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.744: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.744: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.745: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.745: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.745: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.745: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.745: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.745: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.745: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.745: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.746: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.746: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.746: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.746: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.746: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.746: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.746: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.746: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.747: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.747: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.747: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.747: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.747: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.747: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.747: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.747: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.748: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.748: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.748: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.748: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.748: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.748: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.748: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.748: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.748: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.748: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.749: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.749: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.749: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.749: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.749: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.749: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.749: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.749: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.750: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.750: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.750: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.750: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.750: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.750: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.750: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.750: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.751: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.751: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.751: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.751: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.751: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.751: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.751: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.751: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.752: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.752: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.752: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.752: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.752: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.752: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.752: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.752: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.753: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.753: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.753: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.753: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.753: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.753: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.753: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.753: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.754: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.754: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.754: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.754: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.754: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.754: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.754: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.754: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.755: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.755: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.755: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.755: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.755: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.755: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.755: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.755: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.756: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.756: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.756: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.756: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.756: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.756: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.756: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.756: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.757: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.757: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.757: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.757: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.757: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.757: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.757: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.757: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.757: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.757: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.757: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.757: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.757: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.757: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.758: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.758: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.758: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.758: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.758: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.758: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.758: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.758: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.759: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.759: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.759: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.759: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.759: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.759: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.759: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.759: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.760: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.760: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.760: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.760: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.760: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.760: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.760: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.760: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.761: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.761: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.761: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.761: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.761: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.761: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.761: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.761: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.762: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.762: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.762: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.762: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.762: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.762: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.762: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.762: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.763: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.763: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.763: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.763: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.763: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.763: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.763: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.763: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.764: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.764: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.764: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.764: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.764: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.764: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.764: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.764: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.764: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.764: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.765: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.765: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.765: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.765: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.765: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.765: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.765: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.765: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.766: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.766: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.766: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.766: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.766: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.766: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.766: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.766: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.767: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.767: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.767: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.767: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.767: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.767: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.767: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.767: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.768: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.768: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.768: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.768: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.768: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.768: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.768: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.768: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.769: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.769: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.769: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.769: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.769: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.769: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.769: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.769: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.770: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.770: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.770: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.770: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.770: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.770: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.770: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.770: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.771: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.771: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.771: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.771: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.771: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.771: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.771: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.771: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.772: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.772: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.772: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.772: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.772: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.772: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.772: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.772: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.773: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.773: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.773: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.773: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.773: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.773: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.773: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.773: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.774: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.774: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.774: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.774: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.774: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.774: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.775: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.775: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.775: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.775: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.775: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.775: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.775: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.775: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.776: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.776: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.776: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.776: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.776: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.776: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.776: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.776: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.777: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.777: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.777: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.777: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.777: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.777: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.777: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.777: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.778: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.778: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.779: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.779: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.779: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.779: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.779: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.779: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.779: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.779: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.780: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.780: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.780: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.780: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.780: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.780: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.780: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.780: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.781: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.781: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.781: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.781: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.781: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.781: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.781: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.781: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.782: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.782: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.782: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.782: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.782: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.782: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.783: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.783: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.783: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.783: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.783: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.783: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.783: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.783: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.784: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.784: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.784: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.784: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.784: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.784: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.784: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.784: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.784: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.784: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.785: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.785: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.785: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.785: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.785: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.785: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.785: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.785: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.786: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.786: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.786: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.786: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.786: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.786: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.786: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.786: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.787: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.787: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.787: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.787: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.787: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.787: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.787: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.787: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.788: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.788: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.788: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.788: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.788: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.788: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.788: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.788: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.789: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.789: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.789: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.789: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.789: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.789: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.789: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.789: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.790: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.790: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.790: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.790: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.790: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.790: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.790: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.790: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.791: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.791: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.791: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.791: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.791: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.791: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.791: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.791: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.792: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.792: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.792: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.792: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.792: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.792: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.792: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.792: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.793: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.793: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.793: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.793: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.793: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.793: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.793: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.793: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.794: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.794: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.794: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.794: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.794: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.794: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.794: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.794: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.794: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.794: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.794: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.794: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.794: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.794: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.795: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.795: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.795: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.795: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.795: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.795: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.795: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.795: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.796: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.796: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.796: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.796: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.796: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.796: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.796: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.796: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.797: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.797: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.797: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.797: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.797: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.797: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.797: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.797: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.798: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.798: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.798: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.798: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.798: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.798: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.798: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.798: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.799: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.799: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.799: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.799: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.799: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.799: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.799: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.799: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.800: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.800: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.800: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.800: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.800: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.800: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.800: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.800: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.801: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.801: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.801: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.801: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.801: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.801: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.801: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.801: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.802: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.802: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.802: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.802: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.802: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.802: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.802: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.802: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.803: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.803: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.803: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.803: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.803: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.803: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.803: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.803: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.804: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.804: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.804: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.804: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.804: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.804: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.804: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.804: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.805: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.805: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.805: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.805: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.805: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.805: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.805: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.805: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.806: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.806: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.807: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.807: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.807: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.807: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.807: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.807: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.807: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.807: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.808: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.808: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.808: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.808: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.808: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.808: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.808: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.808: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.809: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.809: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.809: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.809: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.809: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.809: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.810: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.810: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.810: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.810: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.810: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.810: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.810: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.810: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.811: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.811: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.811: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.811: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.811: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.811: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.811: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.811: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.812: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.812: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.812: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.812: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.812: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.812: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.812: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.812: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.813: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.813: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.813: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.813: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.813: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.813: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.813: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.813: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.814: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.814: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.814: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.814: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.814: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.814: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.814: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.814: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.815: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.815: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.815: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.815: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.815: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.815: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.815: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.815: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.816: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.816: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.816: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.816: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.816: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.816: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.816: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.816: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.817: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.817: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.817: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.817: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.817: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.817: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.817: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.817: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.818: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.818: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.818: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.818: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.818: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.818: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.818: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.818: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.819: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.819: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.819: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.819: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.819: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.819: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.819: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.819: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.820: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.820: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.820: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.820: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.820: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.820: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.820: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.820: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.821: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.821: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.821: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.821: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.821: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.821: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.821: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.821: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.822: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.822: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.822: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.822: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.822: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.822: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.822: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.822: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.823: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.823: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.823: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.823: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.823: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.823: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.823: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.823: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.824: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.824: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.824: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.824: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.824: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.824: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.824: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.824: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.825: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.825: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.825: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.825: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.825: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.825: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.825: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.825: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.826: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.826: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.826: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.826: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.826: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.826: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.826: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.826: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.826: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.826: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.827: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.827: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.827: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.827: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.827: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.827: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.827: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.827: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.828: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.828: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.828: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.828: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.828: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.828: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.828: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.828: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.829: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.829: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.829: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.829: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.829: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.829: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.829: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.829: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.830: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.830: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.830: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.830: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.830: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.830: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.830: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.830: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.831: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.831: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.831: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.831: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.831: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.831: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.831: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.831: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.832: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.832: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.832: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.832: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.832: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.832: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.832: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.832: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.833: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.833: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.833: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.833: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.833: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.833: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.833: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.833: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.834: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.834: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.834: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.834: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.834: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.834: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.834: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.834: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.835: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.835: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.835: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.835: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.835: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.835: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.835: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.835: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.836: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.836: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.836: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.836: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.836: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.836: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.836: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.836: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.837: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.837: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.837: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.837: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.837: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.837: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.837: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.837: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.838: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.838: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.838: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.838: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.838: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.838: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.838: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.838: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.838: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.838: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.839: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.839: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.839: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.839: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.839: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.839: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.839: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.839: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.839: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.839: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.839: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.839: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.840: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.840: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.840: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.840: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.840: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.840: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.840: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.840: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.841: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.841: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.841: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.841: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.841: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.841: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.841: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.841: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.842: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.842: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.842: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.842: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.842: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.842: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.842: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.842: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.843: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.843: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.843: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.843: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.843: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.843: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.843: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.843: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.844: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.844: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.844: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.844: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.844: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.844: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.844: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.844: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.845: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.845: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.845: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.845: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.845: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.845: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.845: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.845: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.846: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.846: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.846: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.846: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.846: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.846: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.846: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.846: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.847: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.847: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.847: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.848: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.848: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.848: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.848: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.848: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.848: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.848: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.848: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.848: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.848: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.848: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.848: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.848: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.849: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.849: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.849: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.849: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.849: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.849: [vfs7552] CAPTURE_NUM_STATES entering state 2 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.849: [vfs7552] REQUEST CHUNK entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.849: Sending vfs7552_read_image_chunk 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.850: [vfs7552] REQUEST CHUNK completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.850: [vfs7552] CAPTURE_NUM_STATES entering state 3 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.850: [vfs7552] CAPTURE_NUM_STATES entering state 2 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.850: [vfs7552] REQUEST CHUNK entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.850: Sending vfs7552_read_image_chunk 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.851: [vfs7552] REQUEST CHUNK completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.851: [vfs7552] CAPTURE_NUM_STATES entering state 3 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.851: [vfs7552] CAPTURE_NUM_STATES entering state 2 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.851: [vfs7552] REQUEST CHUNK entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.851: Sending vfs7552_read_image_chunk 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.852: [vfs7552] REQUEST CHUNK completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.852: [vfs7552] CAPTURE_NUM_STATES entering state 3 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.852: [vfs7552] CAPTURE_NUM_STATES entering state 4 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.852: Cleaning image 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.852: variance_after = 1435 430s 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.852: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.852: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.852: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.853: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.853: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.853: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.853: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.853: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.853: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.853: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.853: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.854: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.854: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.854: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.854: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.854: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.854: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.854: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.854: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.855: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.855: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.855: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.855: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.855: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.855: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.855: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.855: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.856: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.856: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.856: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.856: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.856: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.856: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.856: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.856: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.857: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.857: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.857: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.857: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.857: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.857: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.857: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.857: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.857: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.858: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.858: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.858: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.858: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.858: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.858: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.858: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.858: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.858: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.859: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.859: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.859: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.859: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.859: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.859: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.859: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.859: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.860: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.860: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.860: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.860: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.860: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.860: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.860: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.860: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.861: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.861: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.861: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.861: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.861: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.861: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.861: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.861: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.862: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.862: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.862: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.862: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.862: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.862: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.862: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.862: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.863: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.863: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.863: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.863: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.863: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.863: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.863: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.863: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.864: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.864: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.864: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.864: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.864: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.864: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.864: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.864: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.865: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.865: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.865: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.865: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.865: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.865: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.865: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.865: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.866: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.866: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.866: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.866: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.866: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.866: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.866: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.866: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.867: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.867: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.867: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.867: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.867: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.867: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.867: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.867: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.867: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.867: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.867: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.867: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.867: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.867: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.868: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.868: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.868: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.868: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.868: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.868: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.868: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.868: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.869: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.869: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.869: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.869: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.869: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.869: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.869: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.869: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.870: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.870: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.870: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.870: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.870: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.870: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.870: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.870: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.871: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.871: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.871: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.871: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.871: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.871: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.871: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.871: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.872: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.872: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.872: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.872: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.872: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.872: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.872: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.872: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.873: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.873: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.873: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.873: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.873: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.873: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.873: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.873: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.874: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.874: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.874: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.874: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.874: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.874: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.874: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.874: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.875: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.875: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.875: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.875: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.875: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.875: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.875: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.875: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.876: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.876: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.876: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.876: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.876: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.876: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.876: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.876: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.876: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.876: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.877: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.877: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.877: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.877: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.877: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.877: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.878: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.878: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.878: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.878: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.878: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.878: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.878: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.878: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.879: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.879: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.879: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.879: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.879: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.879: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.879: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.879: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.879: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.879: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.880: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.880: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.880: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.880: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.880: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.880: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.880: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.880: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.881: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.881: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.881: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.881: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.881: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.881: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.881: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.881: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.882: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.882: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.882: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.882: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.882: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.882: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.882: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.882: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.883: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.883: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.883: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.883: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.883: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.883: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.883: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.883: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.884: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.884: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.884: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.884: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.884: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.884: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.884: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.884: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.885: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.885: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.885: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.885: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.885: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.885: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.885: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.885: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.886: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.886: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.886: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.886: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.886: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.886: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.887: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.887: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.887: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.887: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.887: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.887: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.887: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.887: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.888: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.888: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.888: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.888: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.888: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.888: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.888: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.888: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.889: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.889: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.890: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.890: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.890: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.890: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.890: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.890: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.890: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.890: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.891: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.891: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.891: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.891: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.891: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.891: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.892: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.892: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.892: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.892: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.892: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.892: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.892: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.892: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.893: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.893: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.893: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.893: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.893: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.893: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.893: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.893: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.894: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.894: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.894: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.895: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.895: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.895: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.895: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.895: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.895: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.895: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.896: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.896: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.896: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.896: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.896: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.896: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.896: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.896: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.897: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.897: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.897: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.897: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.897: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.897: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.897: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.898: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.898: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.898: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.898: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.898: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.898: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.898: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.899: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.899: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.899: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.899: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.899: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.899: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.899: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.899: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.900: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.900: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.900: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.900: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.900: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.900: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.900: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.900: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.901: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.901: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.901: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.901: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.901: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.901: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.901: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.901: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.902: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.902: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.902: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.902: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.902: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.902: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.902: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.902: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.903: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.903: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.903: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.903: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.903: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.903: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.903: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.903: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.903: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.903: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.904: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.904: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.904: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.904: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.904: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.904: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.904: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.904: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.905: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.905: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.905: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.905: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.905: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.905: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.905: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.905: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.906: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.906: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.906: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.906: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.906: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.906: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.906: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.906: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.907: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.907: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.907: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.907: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.907: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.907: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.907: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.907: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.908: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.908: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.908: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.908: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.908: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.908: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.908: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.908: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.909: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.909: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.909: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.909: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.909: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.909: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.909: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.909: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.909: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.910: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.910: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.910: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.910: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.910: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.910: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.910: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.910: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.910: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.910: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.910: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.910: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.911: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.911: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.911: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.911: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.911: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.911: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.911: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.911: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.911: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.912: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.912: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.912: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.912: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.912: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.912: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.912: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.912: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.913: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.913: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.913: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.913: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.913: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.913: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.913: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.913: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.914: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.914: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.914: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.914: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.914: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.914: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.914: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.914: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.915: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.915: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.915: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.915: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.915: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.915: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.915: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.915: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.916: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.916: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.916: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.916: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.916: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.916: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.916: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.916: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.917: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.917: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.917: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.917: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.917: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.917: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.917: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.917: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.918: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.918: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.918: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.918: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.918: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.918: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.918: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.918: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.919: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.919: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.919: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.919: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.919: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.919: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.919: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.919: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.920: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.920: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.920: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.920: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.920: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.920: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.920: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.920: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.921: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.921: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.922: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.922: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.922: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.922: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.922: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.922: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.922: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.922: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.922: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.923: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.923: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.923: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.923: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.923: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.923: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.923: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.924: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.924: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.924: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.924: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.924: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.924: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.924: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.924: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.925: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.925: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.925: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.925: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.925: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.925: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.926: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.926: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.926: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.926: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.926: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.926: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.926: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.926: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.927: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.927: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.927: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.927: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.927: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.927: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.927: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.927: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.928: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.928: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.928: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.928: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.928: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.928: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.928: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.928: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.929: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.929: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.929: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.929: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.929: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.929: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.929: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.929: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.930: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.930: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.930: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.930: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.930: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.930: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.930: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.930: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.931: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.931: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.931: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.931: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.931: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.931: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.931: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.931: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.932: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.932: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.933: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.933: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.933: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.933: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.933: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.933: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.933: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.933: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.934: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.934: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.934: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.934: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.934: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.934: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.934: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.934: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.934: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.934: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.934: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.934: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.934: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.935: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.935: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.935: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.935: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.935: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.935: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.935: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.935: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.935: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.936: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.936: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.936: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.936: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.936: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.936: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.936: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.936: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.937: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.937: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.937: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.937: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.937: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.937: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.937: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.937: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.938: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.938: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.938: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.938: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.938: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.938: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.938: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.938: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.939: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.939: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.939: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.939: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.939: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.939: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.939: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.939: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.940: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.940: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.940: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.940: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.940: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.940: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.940: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.940: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.941: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.941: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.941: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.941: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.941: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.941: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.941: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.941: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.942: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.942: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.942: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.942: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.942: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.942: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.942: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.942: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.943: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.943: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.943: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.943: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.943: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.943: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.943: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.943: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.944: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.944: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.944: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.944: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.944: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.944: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.944: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.944: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.945: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.945: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.945: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.945: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.945: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.945: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.945: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.945: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.945: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.945: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.946: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.946: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.946: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.946: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.946: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.946: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.946: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.946: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.947: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.947: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.947: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.947: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.947: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.947: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.947: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.947: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.948: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.948: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.948: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.948: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.948: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.948: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.948: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.948: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.949: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.949: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.949: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.949: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.949: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.949: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.949: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.949: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.950: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.950: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.950: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.950: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.950: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.950: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.950: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.950: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.951: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.951: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.951: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.951: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.951: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.951: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.951: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.951: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.952: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.952: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.952: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.952: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.952: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.952: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.952: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.952: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.952: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.953: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.953: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.953: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.953: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.953: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.953: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.953: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.953: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.953: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.953: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.953: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.953: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.953: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.954: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.954: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.954: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.954: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.954: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.954: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.954: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.954: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.955: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.955: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.955: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.955: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.955: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.955: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.955: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.955: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.956: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.956: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.956: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.956: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.956: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.956: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.956: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.956: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.957: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.957: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.957: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.957: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.957: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.957: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.957: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.957: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.958: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.958: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.958: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.958: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.958: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.958: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.958: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.958: Sending vfs7552_is_image_ready 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.959: [vfs7552] QUERY DATA READY entering state 1 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.959: Receiving 64 bytes 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.959: Got 6 bytes out of 64 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.959: [vfs7552] QUERY DATA READY completed successfully 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.959: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.959: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2292): libfprint-SSM-DEBUG: 00:54:39.959: [vfs7552] QUERY DATA READY entering state 0 430s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.959: Sending vfs7552_is_image_ready 431s (process:2292): libfprint-SSM-DEBUG: 00:54:39.960: [vfs7552] QUERY DATA READY entering state 1 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.960: Receiving 64 bytes 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.960: Got 6 bytes out of 64 431s (process:2292): libfprint-SSM-DEBUG: 00:54:39.960: [vfs7552] QUERY DATA READY completed successfully 431s (process:2292): libfprint-SSM-DEBUG: 00:54:39.960: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2292): libfprint-SSM-DEBUG: 00:54:39.960: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2292): libfprint-SSM-DEBUG: 00:54:39.960: [vfs7552] QUERY DATA READY entering state 0 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.960: Sending vfs7552_is_image_ready 431s (process:2292): libfprint-SSM-DEBUG: 00:54:39.961: [vfs7552] QUERY DATA READY entering state 1 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.961: Receiving 64 bytes 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.961: Got 6 bytes out of 64 431s (process:2292): libfprint-SSM-DEBUG: 00:54:39.961: [vfs7552] QUERY DATA READY completed successfully 431s (process:2292): libfprint-SSM-DEBUG: 00:54:39.961: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2292): libfprint-SSM-DEBUG: 00:54:39.961: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2292): libfprint-SSM-DEBUG: 00:54:39.961: [vfs7552] QUERY DATA READY entering state 0 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.961: Sending vfs7552_is_image_ready 431s (process:2292): libfprint-SSM-DEBUG: 00:54:39.962: [vfs7552] QUERY DATA READY entering state 1 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.962: Receiving 64 bytes 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.963: Got 6 bytes out of 64 431s (process:2292): libfprint-SSM-DEBUG: 00:54:39.963: [vfs7552] QUERY DATA READY completed successfully 431s (process:2292): libfprint-SSM-DEBUG: 00:54:39.963: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2292): libfprint-SSM-DEBUG: 00:54:39.963: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2292): libfprint-SSM-DEBUG: 00:54:39.963: [vfs7552] QUERY DATA READY entering state 0 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.963: Sending vfs7552_is_image_ready 431s (process:2292): libfprint-SSM-DEBUG: 00:54:39.964: [vfs7552] QUERY DATA READY entering state 1 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.964: Receiving 64 bytes 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.964: Got 6 bytes out of 64 431s (process:2292): libfprint-SSM-DEBUG: 00:54:39.964: [vfs7552] QUERY DATA READY completed successfully 431s (process:2292): libfprint-SSM-DEBUG: 00:54:39.964: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2292): libfprint-SSM-DEBUG: 00:54:39.964: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2292): libfprint-SSM-DEBUG: 00:54:39.964: [vfs7552] QUERY DATA READY entering state 0 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.964: Sending vfs7552_is_image_ready 431s (process:2292): libfprint-SSM-DEBUG: 00:54:39.965: [vfs7552] QUERY DATA READY entering state 1 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.965: Receiving 64 bytes 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.965: Got 6 bytes out of 64 431s (process:2292): libfprint-SSM-DEBUG: 00:54:39.965: [vfs7552] QUERY DATA READY completed successfully 431s (process:2292): libfprint-SSM-DEBUG: 00:54:39.965: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2292): libfprint-SSM-DEBUG: 00:54:39.965: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2292): libfprint-SSM-DEBUG: 00:54:39.965: [vfs7552] QUERY DATA READY entering state 0 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.965: Sending vfs7552_is_image_ready 431s (process:2292): libfprint-SSM-DEBUG: 00:54:39.965: [vfs7552] QUERY DATA READY entering state 1 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.965: Receiving 64 bytes 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.966: Got 6 bytes out of 64 431s (process:2292): libfprint-SSM-DEBUG: 00:54:39.966: [vfs7552] QUERY DATA READY completed successfully 431s (process:2292): libfprint-SSM-DEBUG: 00:54:39.966: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2292): libfprint-SSM-DEBUG: 00:54:39.966: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2292): libfprint-SSM-DEBUG: 00:54:39.966: [vfs7552] QUERY DATA READY entering state 0 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.966: Sending vfs7552_is_image_ready 431s (process:2292): libfprint-SSM-DEBUG: 00:54:39.966: [vfs7552] QUERY DATA READY entering state 1 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.966: Receiving 64 bytes 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.967: Got 6 bytes out of 64 431s (process:2292): libfprint-SSM-DEBUG: 00:54:39.967: [vfs7552] QUERY DATA READY completed successfully 431s (process:2292): libfprint-SSM-DEBUG: 00:54:39.967: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2292): libfprint-SSM-DEBUG: 00:54:39.967: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2292): libfprint-SSM-DEBUG: 00:54:39.967: [vfs7552] QUERY DATA READY entering state 0 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.967: Sending vfs7552_is_image_ready 431s (process:2292): libfprint-SSM-DEBUG: 00:54:39.967: [vfs7552] QUERY DATA READY entering state 1 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.967: Receiving 64 bytes 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.968: Got 6 bytes out of 64 431s (process:2292): libfprint-SSM-DEBUG: 00:54:39.968: [vfs7552] QUERY DATA READY completed successfully 431s (process:2292): libfprint-SSM-DEBUG: 00:54:39.968: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2292): libfprint-SSM-DEBUG: 00:54:39.968: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2292): libfprint-SSM-DEBUG: 00:54:39.968: [vfs7552] QUERY DATA READY entering state 0 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.968: Sending vfs7552_is_image_ready 431s (process:2292): libfprint-SSM-DEBUG: 00:54:39.968: [vfs7552] QUERY DATA READY entering state 1 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.968: Receiving 64 bytes 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.969: Got 6 bytes out of 64 431s (process:2292): libfprint-SSM-DEBUG: 00:54:39.969: [vfs7552] QUERY DATA READY completed successfully 431s (process:2292): libfprint-SSM-DEBUG: 00:54:39.969: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2292): libfprint-SSM-DEBUG: 00:54:39.969: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2292): libfprint-SSM-DEBUG: 00:54:39.969: [vfs7552] QUERY DATA READY entering state 0 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.969: Sending vfs7552_is_image_ready 431s (process:2292): libfprint-SSM-DEBUG: 00:54:39.970: [vfs7552] QUERY DATA READY entering state 1 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.970: Receiving 64 bytes 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.970: Got 6 bytes out of 64 431s (process:2292): libfprint-SSM-DEBUG: 00:54:39.970: [vfs7552] QUERY DATA READY completed successfully 431s (process:2292): libfprint-SSM-DEBUG: 00:54:39.970: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2292): libfprint-SSM-DEBUG: 00:54:39.970: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2292): libfprint-SSM-DEBUG: 00:54:39.970: [vfs7552] QUERY DATA READY entering state 0 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.970: Sending vfs7552_is_image_ready 431s (process:2292): libfprint-SSM-DEBUG: 00:54:39.971: [vfs7552] QUERY DATA READY entering state 1 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.971: Receiving 64 bytes 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.972: Got 6 bytes out of 64 431s (process:2292): libfprint-SSM-DEBUG: 00:54:39.972: [vfs7552] QUERY DATA READY completed successfully 431s (process:2292): libfprint-SSM-DEBUG: 00:54:39.972: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2292): libfprint-SSM-DEBUG: 00:54:39.972: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2292): libfprint-SSM-DEBUG: 00:54:39.972: [vfs7552] QUERY DATA READY entering state 0 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.972: Sending vfs7552_is_image_ready 431s (process:2292): libfprint-SSM-DEBUG: 00:54:39.972: [vfs7552] QUERY DATA READY entering state 1 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.972: Receiving 64 bytes 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.973: Got 6 bytes out of 64 431s (process:2292): libfprint-SSM-DEBUG: 00:54:39.973: [vfs7552] QUERY DATA READY completed successfully 431s (process:2292): libfprint-SSM-DEBUG: 00:54:39.973: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2292): libfprint-SSM-DEBUG: 00:54:39.973: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2292): libfprint-SSM-DEBUG: 00:54:39.973: [vfs7552] QUERY DATA READY entering state 0 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.973: Sending vfs7552_is_image_ready 431s (process:2292): libfprint-SSM-DEBUG: 00:54:39.973: [vfs7552] QUERY DATA READY entering state 1 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.973: Receiving 64 bytes 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.974: Got 6 bytes out of 64 431s (process:2292): libfprint-SSM-DEBUG: 00:54:39.974: [vfs7552] QUERY DATA READY completed successfully 431s (process:2292): libfprint-SSM-DEBUG: 00:54:39.974: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2292): libfprint-SSM-DEBUG: 00:54:39.974: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2292): libfprint-SSM-DEBUG: 00:54:39.974: [vfs7552] QUERY DATA READY entering state 0 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.974: Sending vfs7552_is_image_ready 431s (process:2292): libfprint-SSM-DEBUG: 00:54:39.974: [vfs7552] QUERY DATA READY entering state 1 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.974: Receiving 64 bytes 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.975: Got 6 bytes out of 64 431s (process:2292): libfprint-SSM-DEBUG: 00:54:39.975: [vfs7552] QUERY DATA READY completed successfully 431s (process:2292): libfprint-SSM-DEBUG: 00:54:39.975: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2292): libfprint-SSM-DEBUG: 00:54:39.975: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2292): libfprint-SSM-DEBUG: 00:54:39.975: [vfs7552] QUERY DATA READY entering state 0 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.975: Sending vfs7552_is_image_ready 431s (process:2292): libfprint-SSM-DEBUG: 00:54:39.975: [vfs7552] QUERY DATA READY entering state 1 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.975: Receiving 64 bytes 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.976: Got 6 bytes out of 64 431s (process:2292): libfprint-SSM-DEBUG: 00:54:39.976: [vfs7552] QUERY DATA READY completed successfully 431s (process:2292): libfprint-SSM-DEBUG: 00:54:39.976: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2292): libfprint-SSM-DEBUG: 00:54:39.976: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2292): libfprint-SSM-DEBUG: 00:54:39.976: [vfs7552] QUERY DATA READY entering state 0 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.976: Sending vfs7552_is_image_ready 431s (process:2292): libfprint-SSM-DEBUG: 00:54:39.976: [vfs7552] QUERY DATA READY entering state 1 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.976: Receiving 64 bytes 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.977: Got 6 bytes out of 64 431s (process:2292): libfprint-SSM-DEBUG: 00:54:39.977: [vfs7552] QUERY DATA READY completed successfully 431s (process:2292): libfprint-SSM-DEBUG: 00:54:39.977: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2292): libfprint-SSM-DEBUG: 00:54:39.977: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2292): libfprint-SSM-DEBUG: 00:54:39.977: [vfs7552] QUERY DATA READY entering state 0 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.977: Sending vfs7552_is_image_ready 431s (process:2292): libfprint-SSM-DEBUG: 00:54:39.977: [vfs7552] QUERY DATA READY entering state 1 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.977: Receiving 64 bytes 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.978: Got 6 bytes out of 64 431s (process:2292): libfprint-SSM-DEBUG: 00:54:39.978: [vfs7552] QUERY DATA READY completed successfully 431s (process:2292): libfprint-SSM-DEBUG: 00:54:39.978: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2292): libfprint-SSM-DEBUG: 00:54:39.978: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2292): libfprint-SSM-DEBUG: 00:54:39.978: [vfs7552] QUERY DATA READY entering state 0 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.978: Sending vfs7552_is_image_ready 431s (process:2292): libfprint-SSM-DEBUG: 00:54:39.978: [vfs7552] QUERY DATA READY entering state 1 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.978: Receiving 64 bytes 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.979: Got 6 bytes out of 64 431s (process:2292): libfprint-SSM-DEBUG: 00:54:39.979: [vfs7552] QUERY DATA READY completed successfully 431s (process:2292): libfprint-SSM-DEBUG: 00:54:39.979: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2292): libfprint-SSM-DEBUG: 00:54:39.979: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2292): libfprint-SSM-DEBUG: 00:54:39.979: [vfs7552] QUERY DATA READY entering state 0 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.979: Sending vfs7552_is_image_ready 431s (process:2292): libfprint-SSM-DEBUG: 00:54:39.979: [vfs7552] QUERY DATA READY entering state 1 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.979: Receiving 64 bytes 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.980: Got 6 bytes out of 64 431s (process:2292): libfprint-SSM-DEBUG: 00:54:39.980: [vfs7552] QUERY DATA READY completed successfully 431s (process:2292): libfprint-SSM-DEBUG: 00:54:39.980: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2292): libfprint-SSM-DEBUG: 00:54:39.980: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2292): libfprint-SSM-DEBUG: 00:54:39.980: [vfs7552] QUERY DATA READY entering state 0 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.980: Sending vfs7552_is_image_ready 431s (process:2292): libfprint-SSM-DEBUG: 00:54:39.981: [vfs7552] QUERY DATA READY entering state 1 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.981: Receiving 64 bytes 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.982: Got 6 bytes out of 64 431s (process:2292): libfprint-SSM-DEBUG: 00:54:39.982: [vfs7552] QUERY DATA READY completed successfully 431s (process:2292): libfprint-SSM-DEBUG: 00:54:39.982: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2292): libfprint-SSM-DEBUG: 00:54:39.982: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2292): libfprint-SSM-DEBUG: 00:54:39.982: [vfs7552] QUERY DATA READY entering state 0 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.982: Sending vfs7552_is_image_ready 431s (process:2292): libfprint-SSM-DEBUG: 00:54:39.982: [vfs7552] QUERY DATA READY entering state 1 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.982: Receiving 64 bytes 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.983: Got 6 bytes out of 64 431s (process:2292): libfprint-SSM-DEBUG: 00:54:39.983: [vfs7552] QUERY DATA READY completed successfully 431s (process:2292): libfprint-SSM-DEBUG: 00:54:39.983: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2292): libfprint-SSM-DEBUG: 00:54:39.983: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2292): libfprint-SSM-DEBUG: 00:54:39.983: [vfs7552] QUERY DATA READY entering state 0 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.983: Sending vfs7552_is_image_ready 431s (process:2292): libfprint-SSM-DEBUG: 00:54:39.983: [vfs7552] QUERY DATA READY entering state 1 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.983: Receiving 64 bytes 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.984: Got 6 bytes out of 64 431s (process:2292): libfprint-SSM-DEBUG: 00:54:39.984: [vfs7552] QUERY DATA READY completed successfully 431s (process:2292): libfprint-SSM-DEBUG: 00:54:39.984: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2292): libfprint-SSM-DEBUG: 00:54:39.984: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2292): libfprint-SSM-DEBUG: 00:54:39.984: [vfs7552] QUERY DATA READY entering state 0 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.984: Sending vfs7552_is_image_ready 431s (process:2292): libfprint-SSM-DEBUG: 00:54:39.984: [vfs7552] QUERY DATA READY entering state 1 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.984: Receiving 64 bytes 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.985: Got 6 bytes out of 64 431s (process:2292): libfprint-SSM-DEBUG: 00:54:39.985: [vfs7552] QUERY DATA READY completed successfully 431s (process:2292): libfprint-SSM-DEBUG: 00:54:39.985: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2292): libfprint-SSM-DEBUG: 00:54:39.985: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2292): libfprint-SSM-DEBUG: 00:54:39.985: [vfs7552] QUERY DATA READY entering state 0 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.985: Sending vfs7552_is_image_ready 431s (process:2292): libfprint-SSM-DEBUG: 00:54:39.986: [vfs7552] QUERY DATA READY entering state 1 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.986: Receiving 64 bytes 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.987: Got 6 bytes out of 64 431s (process:2292): libfprint-SSM-DEBUG: 00:54:39.987: [vfs7552] QUERY DATA READY completed successfully 431s (process:2292): libfprint-SSM-DEBUG: 00:54:39.987: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2292): libfprint-SSM-DEBUG: 00:54:39.987: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2292): libfprint-SSM-DEBUG: 00:54:39.987: [vfs7552] QUERY DATA READY entering state 0 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.987: Sending vfs7552_is_image_ready 431s (process:2292): libfprint-SSM-DEBUG: 00:54:39.987: [vfs7552] QUERY DATA READY entering state 1 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.987: Receiving 64 bytes 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.988: Got 6 bytes out of 64 431s (process:2292): libfprint-SSM-DEBUG: 00:54:39.988: [vfs7552] QUERY DATA READY completed successfully 431s (process:2292): libfprint-SSM-DEBUG: 00:54:39.988: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2292): libfprint-SSM-DEBUG: 00:54:39.988: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2292): libfprint-SSM-DEBUG: 00:54:39.988: [vfs7552] QUERY DATA READY entering state 0 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.988: Sending vfs7552_is_image_ready 431s (process:2292): libfprint-SSM-DEBUG: 00:54:39.988: [vfs7552] QUERY DATA READY entering state 1 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.988: Receiving 64 bytes 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.989: Got 6 bytes out of 64 431s (process:2292): libfprint-SSM-DEBUG: 00:54:39.989: [vfs7552] QUERY DATA READY completed successfully 431s (process:2292): libfprint-SSM-DEBUG: 00:54:39.989: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2292): libfprint-SSM-DEBUG: 00:54:39.989: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2292): libfprint-SSM-DEBUG: 00:54:39.989: [vfs7552] QUERY DATA READY entering state 0 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.989: Sending vfs7552_is_image_ready 431s (process:2292): libfprint-SSM-DEBUG: 00:54:39.989: [vfs7552] QUERY DATA READY entering state 1 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.989: Receiving 64 bytes 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.990: Got 6 bytes out of 64 431s (process:2292): libfprint-SSM-DEBUG: 00:54:39.990: [vfs7552] QUERY DATA READY completed successfully 431s (process:2292): libfprint-SSM-DEBUG: 00:54:39.990: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2292): libfprint-SSM-DEBUG: 00:54:39.990: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2292): libfprint-SSM-DEBUG: 00:54:39.990: [vfs7552] QUERY DATA READY entering state 0 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.990: Sending vfs7552_is_image_ready 431s (process:2292): libfprint-SSM-DEBUG: 00:54:39.991: [vfs7552] QUERY DATA READY entering state 1 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.991: Receiving 64 bytes 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.991: Got 6 bytes out of 64 431s (process:2292): libfprint-SSM-DEBUG: 00:54:39.991: [vfs7552] QUERY DATA READY completed successfully 431s (process:2292): libfprint-SSM-DEBUG: 00:54:39.991: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2292): libfprint-SSM-DEBUG: 00:54:39.991: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2292): libfprint-SSM-DEBUG: 00:54:39.991: [vfs7552] QUERY DATA READY entering state 0 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.991: Sending vfs7552_is_image_ready 431s (process:2292): libfprint-SSM-DEBUG: 00:54:39.992: [vfs7552] QUERY DATA READY entering state 1 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.992: Receiving 64 bytes 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.993: Got 6 bytes out of 64 431s (process:2292): libfprint-SSM-DEBUG: 00:54:39.993: [vfs7552] QUERY DATA READY completed successfully 431s (process:2292): libfprint-SSM-DEBUG: 00:54:39.993: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2292): libfprint-SSM-DEBUG: 00:54:39.993: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2292): libfprint-SSM-DEBUG: 00:54:39.993: [vfs7552] QUERY DATA READY entering state 0 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.993: Sending vfs7552_is_image_ready 431s (process:2292): libfprint-SSM-DEBUG: 00:54:39.994: [vfs7552] QUERY DATA READY entering state 1 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.994: Receiving 64 bytes 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.994: Got 6 bytes out of 64 431s (process:2292): libfprint-SSM-DEBUG: 00:54:39.994: [vfs7552] QUERY DATA READY completed successfully 431s (process:2292): libfprint-SSM-DEBUG: 00:54:39.994: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2292): libfprint-SSM-DEBUG: 00:54:39.994: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2292): libfprint-SSM-DEBUG: 00:54:39.994: [vfs7552] QUERY DATA READY entering state 0 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.994: Sending vfs7552_is_image_ready 431s (process:2292): libfprint-SSM-DEBUG: 00:54:39.995: [vfs7552] QUERY DATA READY entering state 1 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.995: Receiving 64 bytes 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.996: Got 6 bytes out of 64 431s (process:2292): libfprint-SSM-DEBUG: 00:54:39.996: [vfs7552] QUERY DATA READY completed successfully 431s (process:2292): libfprint-SSM-DEBUG: 00:54:39.996: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2292): libfprint-SSM-DEBUG: 00:54:39.996: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2292): libfprint-SSM-DEBUG: 00:54:39.996: [vfs7552] QUERY DATA READY entering state 0 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.996: Sending vfs7552_is_image_ready 431s (process:2292): libfprint-SSM-DEBUG: 00:54:39.997: [vfs7552] QUERY DATA READY entering state 1 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.997: Receiving 64 bytes 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.998: Got 6 bytes out of 64 431s (process:2292): libfprint-SSM-DEBUG: 00:54:39.998: [vfs7552] QUERY DATA READY completed successfully 431s (process:2292): libfprint-SSM-DEBUG: 00:54:39.998: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2292): libfprint-SSM-DEBUG: 00:54:39.998: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2292): libfprint-SSM-DEBUG: 00:54:39.998: [vfs7552] QUERY DATA READY entering state 0 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.998: Sending vfs7552_is_image_ready 431s (process:2292): libfprint-SSM-DEBUG: 00:54:39.998: [vfs7552] QUERY DATA READY entering state 1 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.998: Receiving 64 bytes 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.999: Got 6 bytes out of 64 431s (process:2292): libfprint-SSM-DEBUG: 00:54:39.999: [vfs7552] QUERY DATA READY completed successfully 431s (process:2292): libfprint-SSM-DEBUG: 00:54:39.999: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2292): libfprint-SSM-DEBUG: 00:54:39.999: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2292): libfprint-SSM-DEBUG: 00:54:39.999: [vfs7552] QUERY DATA READY entering state 0 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:39.999: Sending vfs7552_is_image_ready 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.000: [vfs7552] QUERY DATA READY entering state 1 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.000: Receiving 64 bytes 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.001: Got 6 bytes out of 64 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.001: [vfs7552] QUERY DATA READY completed successfully 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.001: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.001: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.001: [vfs7552] QUERY DATA READY entering state 0 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.001: Sending vfs7552_is_image_ready 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.002: [vfs7552] QUERY DATA READY entering state 1 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.002: Receiving 64 bytes 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.002: Got 6 bytes out of 64 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.002: [vfs7552] QUERY DATA READY completed successfully 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.002: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.002: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.002: [vfs7552] QUERY DATA READY entering state 0 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.002: Sending vfs7552_is_image_ready 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.003: [vfs7552] QUERY DATA READY entering state 1 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.003: Receiving 64 bytes 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.004: Got 6 bytes out of 64 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.004: [vfs7552] QUERY DATA READY completed successfully 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.004: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.004: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.004: [vfs7552] QUERY DATA READY entering state 0 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.004: Sending vfs7552_is_image_ready 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.004: [vfs7552] QUERY DATA READY entering state 1 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.004: Receiving 64 bytes 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.005: Got 6 bytes out of 64 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.005: [vfs7552] QUERY DATA READY completed successfully 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.005: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.005: [vfs7552] CAPTURE_NUM_STATES entering state 2 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.005: [vfs7552] REQUEST CHUNK entering state 0 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.005: Sending vfs7552_read_image_chunk 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.005: [vfs7552] REQUEST CHUNK completed successfully 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.005: [vfs7552] CAPTURE_NUM_STATES entering state 3 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.006: [vfs7552] CAPTURE_NUM_STATES entering state 2 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.006: [vfs7552] REQUEST CHUNK entering state 0 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.006: Sending vfs7552_read_image_chunk 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.006: [vfs7552] REQUEST CHUNK completed successfully 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.006: [vfs7552] CAPTURE_NUM_STATES entering state 3 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.007: [vfs7552] CAPTURE_NUM_STATES entering state 2 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.007: [vfs7552] REQUEST CHUNK entering state 0 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.007: Sending vfs7552_read_image_chunk 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.007: [vfs7552] REQUEST CHUNK completed successfully 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.007: [vfs7552] CAPTURE_NUM_STATES entering state 3 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.008: [vfs7552] CAPTURE_NUM_STATES entering state 4 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.008: Cleaning image 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.008: variance_after = 1425 431s 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.008: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.008: [vfs7552] QUERY DATA READY entering state 0 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.008: Sending vfs7552_is_image_ready 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.008: [vfs7552] QUERY DATA READY entering state 1 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.008: Receiving 64 bytes 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.009: Got 6 bytes out of 64 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.009: [vfs7552] QUERY DATA READY completed successfully 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.009: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.009: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.009: [vfs7552] QUERY DATA READY entering state 0 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.009: Sending vfs7552_is_image_ready 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.009: [vfs7552] QUERY DATA READY entering state 1 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.009: Receiving 64 bytes 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.010: Got 6 bytes out of 64 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.010: [vfs7552] QUERY DATA READY completed successfully 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.010: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.010: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.010: [vfs7552] QUERY DATA READY entering state 0 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.010: Sending vfs7552_is_image_ready 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.010: [vfs7552] QUERY DATA READY entering state 1 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.010: Receiving 64 bytes 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.011: Got 6 bytes out of 64 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.011: [vfs7552] QUERY DATA READY completed successfully 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.011: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.011: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.011: [vfs7552] QUERY DATA READY entering state 0 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.011: Sending vfs7552_is_image_ready 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.012: [vfs7552] QUERY DATA READY entering state 1 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.012: Receiving 64 bytes 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.012: Got 6 bytes out of 64 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.012: [vfs7552] QUERY DATA READY completed successfully 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.012: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.012: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.012: [vfs7552] QUERY DATA READY entering state 0 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.012: Sending vfs7552_is_image_ready 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.013: [vfs7552] QUERY DATA READY entering state 1 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.013: Receiving 64 bytes 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.013: Got 6 bytes out of 64 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.013: [vfs7552] QUERY DATA READY completed successfully 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.013: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.013: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.013: [vfs7552] QUERY DATA READY entering state 0 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.013: Sending vfs7552_is_image_ready 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.014: [vfs7552] QUERY DATA READY entering state 1 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.014: Receiving 64 bytes 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.014: Got 6 bytes out of 64 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.014: [vfs7552] QUERY DATA READY completed successfully 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.014: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.014: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.014: [vfs7552] QUERY DATA READY entering state 0 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.014: Sending vfs7552_is_image_ready 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.015: [vfs7552] QUERY DATA READY entering state 1 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.015: Receiving 64 bytes 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.015: Got 6 bytes out of 64 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.015: [vfs7552] QUERY DATA READY completed successfully 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.015: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.015: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.015: [vfs7552] QUERY DATA READY entering state 0 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.015: Sending vfs7552_is_image_ready 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.016: [vfs7552] QUERY DATA READY entering state 1 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.016: Receiving 64 bytes 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.016: Got 6 bytes out of 64 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.016: [vfs7552] QUERY DATA READY completed successfully 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.016: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.016: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.016: [vfs7552] QUERY DATA READY entering state 0 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.016: Sending vfs7552_is_image_ready 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.017: [vfs7552] QUERY DATA READY entering state 1 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.017: Receiving 64 bytes 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.017: Got 6 bytes out of 64 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.017: [vfs7552] QUERY DATA READY completed successfully 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.017: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.017: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.017: [vfs7552] QUERY DATA READY entering state 0 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.017: Sending vfs7552_is_image_ready 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.018: [vfs7552] QUERY DATA READY entering state 1 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.018: Receiving 64 bytes 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.018: Got 6 bytes out of 64 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.018: [vfs7552] QUERY DATA READY completed successfully 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.018: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.018: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.018: [vfs7552] QUERY DATA READY entering state 0 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.018: Sending vfs7552_is_image_ready 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.019: [vfs7552] QUERY DATA READY entering state 1 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.019: Receiving 64 bytes 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.019: Got 6 bytes out of 64 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.019: [vfs7552] QUERY DATA READY completed successfully 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.019: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.019: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.019: [vfs7552] QUERY DATA READY entering state 0 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.019: Sending vfs7552_is_image_ready 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.020: [vfs7552] QUERY DATA READY entering state 1 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.020: Receiving 64 bytes 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.020: Got 6 bytes out of 64 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.020: [vfs7552] QUERY DATA READY completed successfully 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.020: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.020: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.020: [vfs7552] QUERY DATA READY entering state 0 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.020: Sending vfs7552_is_image_ready 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.021: [vfs7552] QUERY DATA READY entering state 1 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.021: Receiving 64 bytes 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.021: Got 6 bytes out of 64 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.021: [vfs7552] QUERY DATA READY completed successfully 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.021: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.021: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.021: [vfs7552] QUERY DATA READY entering state 0 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.021: Sending vfs7552_is_image_ready 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.022: [vfs7552] QUERY DATA READY entering state 1 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.022: Receiving 64 bytes 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.022: Got 6 bytes out of 64 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.022: [vfs7552] QUERY DATA READY completed successfully 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.022: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.022: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.022: [vfs7552] QUERY DATA READY entering state 0 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.022: Sending vfs7552_is_image_ready 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.023: [vfs7552] QUERY DATA READY entering state 1 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.023: Receiving 64 bytes 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.023: Got 6 bytes out of 64 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.023: [vfs7552] QUERY DATA READY completed successfully 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.023: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.023: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.023: [vfs7552] QUERY DATA READY entering state 0 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.023: Sending vfs7552_is_image_ready 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.024: [vfs7552] QUERY DATA READY entering state 1 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.024: Receiving 64 bytes 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.024: Got 6 bytes out of 64 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.024: [vfs7552] QUERY DATA READY completed successfully 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.024: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.024: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.024: [vfs7552] QUERY DATA READY entering state 0 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.024: Sending vfs7552_is_image_ready 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.025: [vfs7552] QUERY DATA READY entering state 1 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.025: Receiving 64 bytes 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.025: Got 6 bytes out of 64 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.025: [vfs7552] QUERY DATA READY completed successfully 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.025: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.025: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.025: [vfs7552] QUERY DATA READY entering state 0 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.025: Sending vfs7552_is_image_ready 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.026: [vfs7552] QUERY DATA READY entering state 1 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.026: Receiving 64 bytes 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.027: Got 6 bytes out of 64 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.027: [vfs7552] QUERY DATA READY completed successfully 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.027: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.027: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.027: [vfs7552] QUERY DATA READY entering state 0 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.027: Sending vfs7552_is_image_ready 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.027: [vfs7552] QUERY DATA READY entering state 1 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.027: Receiving 64 bytes 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.028: Got 6 bytes out of 64 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.028: [vfs7552] QUERY DATA READY completed successfully 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.028: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.028: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.028: [vfs7552] QUERY DATA READY entering state 0 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.028: Sending vfs7552_is_image_ready 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.028: [vfs7552] QUERY DATA READY entering state 1 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.028: Receiving 64 bytes 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.029: Got 6 bytes out of 64 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.029: [vfs7552] QUERY DATA READY completed successfully 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.029: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.029: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.029: [vfs7552] QUERY DATA READY entering state 0 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.029: Sending vfs7552_is_image_ready 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.029: [vfs7552] QUERY DATA READY entering state 1 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.029: Receiving 64 bytes 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.030: Got 6 bytes out of 64 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.030: [vfs7552] QUERY DATA READY completed successfully 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.030: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.030: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.030: [vfs7552] QUERY DATA READY entering state 0 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.030: Sending vfs7552_is_image_ready 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.030: [vfs7552] QUERY DATA READY entering state 1 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.030: Receiving 64 bytes 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.031: Got 6 bytes out of 64 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.031: [vfs7552] QUERY DATA READY completed successfully 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.031: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.031: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.031: [vfs7552] QUERY DATA READY entering state 0 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.031: Sending vfs7552_is_image_ready 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.031: [vfs7552] QUERY DATA READY entering state 1 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.031: Receiving 64 bytes 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.032: Got 6 bytes out of 64 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.032: [vfs7552] QUERY DATA READY completed successfully 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.032: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.032: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.032: [vfs7552] QUERY DATA READY entering state 0 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.032: Sending vfs7552_is_image_ready 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.032: [vfs7552] QUERY DATA READY entering state 1 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.032: Receiving 64 bytes 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.033: Got 6 bytes out of 64 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.033: [vfs7552] QUERY DATA READY completed successfully 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.033: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.033: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.033: [vfs7552] QUERY DATA READY entering state 0 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.033: Sending vfs7552_is_image_ready 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.033: [vfs7552] QUERY DATA READY entering state 1 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.033: Receiving 64 bytes 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.034: Got 6 bytes out of 64 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.034: [vfs7552] QUERY DATA READY completed successfully 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.034: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.034: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.034: [vfs7552] QUERY DATA READY entering state 0 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.034: Sending vfs7552_is_image_ready 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.034: [vfs7552] QUERY DATA READY entering state 1 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.034: Receiving 64 bytes 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.035: Got 6 bytes out of 64 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.035: [vfs7552] QUERY DATA READY completed successfully 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.035: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.035: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.035: [vfs7552] QUERY DATA READY entering state 0 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.035: Sending vfs7552_is_image_ready 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.035: [vfs7552] QUERY DATA READY entering state 1 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.035: Receiving 64 bytes 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.036: Got 6 bytes out of 64 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.036: [vfs7552] QUERY DATA READY completed successfully 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.036: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.036: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.036: [vfs7552] QUERY DATA READY entering state 0 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.036: Sending vfs7552_is_image_ready 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.036: [vfs7552] QUERY DATA READY entering state 1 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.036: Receiving 64 bytes 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.037: Got 6 bytes out of 64 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.037: [vfs7552] QUERY DATA READY completed successfully 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.037: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.037: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.037: [vfs7552] QUERY DATA READY entering state 0 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.037: Sending vfs7552_is_image_ready 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.037: [vfs7552] QUERY DATA READY entering state 1 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.037: Receiving 64 bytes 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.038: Got 6 bytes out of 64 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.038: [vfs7552] QUERY DATA READY completed successfully 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.038: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.038: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.038: [vfs7552] QUERY DATA READY entering state 0 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.038: Sending vfs7552_is_image_ready 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.038: [vfs7552] QUERY DATA READY entering state 1 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.038: Receiving 64 bytes 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.039: Got 6 bytes out of 64 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.039: [vfs7552] QUERY DATA READY completed successfully 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.039: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.039: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.039: [vfs7552] QUERY DATA READY entering state 0 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.039: Sending vfs7552_is_image_ready 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.039: [vfs7552] QUERY DATA READY entering state 1 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.039: Receiving 64 bytes 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.040: Got 6 bytes out of 64 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.040: [vfs7552] QUERY DATA READY completed successfully 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.040: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.040: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.040: [vfs7552] QUERY DATA READY entering state 0 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.040: Sending vfs7552_is_image_ready 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.040: [vfs7552] QUERY DATA READY entering state 1 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.040: Receiving 64 bytes 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.041: Got 6 bytes out of 64 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.041: [vfs7552] QUERY DATA READY completed successfully 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.041: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.041: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.041: [vfs7552] QUERY DATA READY entering state 0 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.041: Sending vfs7552_is_image_ready 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.041: [vfs7552] QUERY DATA READY entering state 1 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.041: Receiving 64 bytes 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.042: Got 6 bytes out of 64 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.042: [vfs7552] QUERY DATA READY completed successfully 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.042: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.042: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.042: [vfs7552] QUERY DATA READY entering state 0 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.042: Sending vfs7552_is_image_ready 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.042: [vfs7552] QUERY DATA READY entering state 1 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.042: Receiving 64 bytes 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.043: Got 6 bytes out of 64 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.043: [vfs7552] QUERY DATA READY completed successfully 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.043: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.043: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.043: [vfs7552] QUERY DATA READY entering state 0 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.043: Sending vfs7552_is_image_ready 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.043: [vfs7552] QUERY DATA READY entering state 1 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.043: Receiving 64 bytes 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.044: Got 6 bytes out of 64 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.044: [vfs7552] QUERY DATA READY completed successfully 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.044: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.044: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.044: [vfs7552] QUERY DATA READY entering state 0 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.044: Sending vfs7552_is_image_ready 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.044: [vfs7552] QUERY DATA READY entering state 1 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.044: Receiving 64 bytes 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.045: Got 6 bytes out of 64 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.045: [vfs7552] QUERY DATA READY completed successfully 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.045: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.045: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.045: [vfs7552] QUERY DATA READY entering state 0 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.045: Sending vfs7552_is_image_ready 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.045: [vfs7552] QUERY DATA READY entering state 1 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.045: Receiving 64 bytes 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.046: Got 6 bytes out of 64 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.046: [vfs7552] QUERY DATA READY completed successfully 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.046: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.046: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.046: [vfs7552] QUERY DATA READY entering state 0 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.046: Sending vfs7552_is_image_ready 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.046: [vfs7552] QUERY DATA READY entering state 1 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.046: Receiving 64 bytes 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.047: Got 6 bytes out of 64 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.047: [vfs7552] QUERY DATA READY completed successfully 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.047: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.047: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.047: [vfs7552] QUERY DATA READY entering state 0 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.047: Sending vfs7552_is_image_ready 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.047: [vfs7552] QUERY DATA READY entering state 1 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.047: Receiving 64 bytes 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.048: Got 6 bytes out of 64 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.048: [vfs7552] QUERY DATA READY completed successfully 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.048: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.048: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.048: [vfs7552] QUERY DATA READY entering state 0 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.048: Sending vfs7552_is_image_ready 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.048: [vfs7552] QUERY DATA READY entering state 1 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.048: Receiving 64 bytes 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.049: Got 6 bytes out of 64 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.049: [vfs7552] QUERY DATA READY completed successfully 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.049: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.049: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.049: [vfs7552] QUERY DATA READY entering state 0 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.049: Sending vfs7552_is_image_ready 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.049: [vfs7552] QUERY DATA READY entering state 1 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.049: Receiving 64 bytes 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.050: Got 6 bytes out of 64 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.050: [vfs7552] QUERY DATA READY completed successfully 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.050: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.050: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.050: [vfs7552] QUERY DATA READY entering state 0 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.050: Sending vfs7552_is_image_ready 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.050: [vfs7552] QUERY DATA READY entering state 1 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.050: Receiving 64 bytes 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.051: Got 6 bytes out of 64 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.051: [vfs7552] QUERY DATA READY completed successfully 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.051: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.051: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.051: [vfs7552] QUERY DATA READY entering state 0 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.051: Sending vfs7552_is_image_ready 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.051: [vfs7552] QUERY DATA READY entering state 1 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.051: Receiving 64 bytes 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.052: Got 6 bytes out of 64 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.052: [vfs7552] QUERY DATA READY completed successfully 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.052: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.052: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.052: [vfs7552] QUERY DATA READY entering state 0 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.052: Sending vfs7552_is_image_ready 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.052: [vfs7552] QUERY DATA READY entering state 1 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.052: Receiving 64 bytes 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.053: Got 6 bytes out of 64 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.053: [vfs7552] QUERY DATA READY completed successfully 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.053: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.053: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.053: [vfs7552] QUERY DATA READY entering state 0 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.053: Sending vfs7552_is_image_ready 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.053: [vfs7552] QUERY DATA READY entering state 1 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.053: Receiving 64 bytes 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.054: Got 6 bytes out of 64 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.054: [vfs7552] QUERY DATA READY completed successfully 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.054: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.054: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.054: [vfs7552] QUERY DATA READY entering state 0 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.054: Sending vfs7552_is_image_ready 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.054: [vfs7552] QUERY DATA READY entering state 1 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.054: Receiving 64 bytes 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.055: Got 6 bytes out of 64 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.055: [vfs7552] QUERY DATA READY completed successfully 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.055: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.055: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.055: [vfs7552] QUERY DATA READY entering state 0 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.055: Sending vfs7552_is_image_ready 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.055: [vfs7552] QUERY DATA READY entering state 1 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.055: Receiving 64 bytes 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.056: Got 6 bytes out of 64 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.056: [vfs7552] QUERY DATA READY completed successfully 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.056: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.056: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.056: [vfs7552] QUERY DATA READY entering state 0 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.056: Sending vfs7552_is_image_ready 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.056: [vfs7552] QUERY DATA READY entering state 1 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.056: Receiving 64 bytes 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.057: Got 6 bytes out of 64 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.057: [vfs7552] QUERY DATA READY completed successfully 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.057: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.057: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.057: [vfs7552] QUERY DATA READY entering state 0 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.057: Sending vfs7552_is_image_ready 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.057: [vfs7552] QUERY DATA READY entering state 1 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.057: Receiving 64 bytes 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.058: Got 6 bytes out of 64 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.058: [vfs7552] QUERY DATA READY completed successfully 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.058: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.058: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.058: [vfs7552] QUERY DATA READY entering state 0 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.058: Sending vfs7552_is_image_ready 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.058: [vfs7552] QUERY DATA READY entering state 1 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.058: Receiving 64 bytes 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.059: Got 6 bytes out of 64 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.059: [vfs7552] QUERY DATA READY completed successfully 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.059: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.059: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.059: [vfs7552] QUERY DATA READY entering state 0 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.059: Sending vfs7552_is_image_ready 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.059: [vfs7552] QUERY DATA READY entering state 1 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.059: Receiving 64 bytes 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.060: Got 6 bytes out of 64 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.060: [vfs7552] QUERY DATA READY completed successfully 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.060: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.060: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.060: [vfs7552] QUERY DATA READY entering state 0 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.060: Sending vfs7552_is_image_ready 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.060: [vfs7552] QUERY DATA READY entering state 1 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.060: Receiving 64 bytes 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.061: Got 6 bytes out of 64 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.061: [vfs7552] QUERY DATA READY completed successfully 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.061: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.061: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.061: [vfs7552] QUERY DATA READY entering state 0 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.061: Sending vfs7552_is_image_ready 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.061: [vfs7552] QUERY DATA READY entering state 1 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.061: Receiving 64 bytes 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.062: Got 6 bytes out of 64 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.062: [vfs7552] QUERY DATA READY completed successfully 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.062: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.062: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.062: [vfs7552] QUERY DATA READY entering state 0 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.062: Sending vfs7552_is_image_ready 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.062: [vfs7552] QUERY DATA READY entering state 1 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.062: Receiving 64 bytes 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.063: Got 6 bytes out of 64 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.063: [vfs7552] QUERY DATA READY completed successfully 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.063: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.063: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.063: [vfs7552] QUERY DATA READY entering state 0 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.063: Sending vfs7552_is_image_ready 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.063: [vfs7552] QUERY DATA READY entering state 1 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.063: Receiving 64 bytes 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.064: Got 6 bytes out of 64 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.064: [vfs7552] QUERY DATA READY completed successfully 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.064: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.064: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.064: [vfs7552] QUERY DATA READY entering state 0 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.064: Sending vfs7552_is_image_ready 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.064: [vfs7552] QUERY DATA READY entering state 1 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.064: Receiving 64 bytes 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.065: Got 6 bytes out of 64 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.065: [vfs7552] QUERY DATA READY completed successfully 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.065: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.065: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.065: [vfs7552] QUERY DATA READY entering state 0 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.065: Sending vfs7552_is_image_ready 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.065: [vfs7552] QUERY DATA READY entering state 1 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.065: Receiving 64 bytes 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.066: Got 6 bytes out of 64 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.066: [vfs7552] QUERY DATA READY completed successfully 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.066: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.066: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.066: [vfs7552] QUERY DATA READY entering state 0 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.066: Sending vfs7552_is_image_ready 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.066: [vfs7552] QUERY DATA READY entering state 1 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.066: Receiving 64 bytes 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.067: Got 6 bytes out of 64 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.067: [vfs7552] QUERY DATA READY completed successfully 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.067: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.067: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.067: [vfs7552] QUERY DATA READY entering state 0 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.067: Sending vfs7552_is_image_ready 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.067: [vfs7552] QUERY DATA READY entering state 1 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.067: Receiving 64 bytes 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.068: Got 6 bytes out of 64 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.068: [vfs7552] QUERY DATA READY completed successfully 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.068: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.068: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.068: [vfs7552] QUERY DATA READY entering state 0 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.068: Sending vfs7552_is_image_ready 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.068: [vfs7552] QUERY DATA READY entering state 1 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.068: Receiving 64 bytes 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.069: Got 6 bytes out of 64 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.069: [vfs7552] QUERY DATA READY completed successfully 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.069: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.069: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.069: [vfs7552] QUERY DATA READY entering state 0 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.069: Sending vfs7552_is_image_ready 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.069: [vfs7552] QUERY DATA READY entering state 1 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.069: Receiving 64 bytes 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.070: Got 6 bytes out of 64 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.070: [vfs7552] QUERY DATA READY completed successfully 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.070: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.070: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.070: [vfs7552] QUERY DATA READY entering state 0 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.070: Sending vfs7552_is_image_ready 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.070: [vfs7552] QUERY DATA READY entering state 1 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.070: Receiving 64 bytes 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.071: Got 6 bytes out of 64 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.071: [vfs7552] QUERY DATA READY completed successfully 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.071: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.071: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.071: [vfs7552] QUERY DATA READY entering state 0 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.071: Sending vfs7552_is_image_ready 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.071: [vfs7552] QUERY DATA READY entering state 1 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.071: Receiving 64 bytes 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.072: Got 6 bytes out of 64 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.072: [vfs7552] QUERY DATA READY completed successfully 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.072: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.072: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.072: [vfs7552] QUERY DATA READY entering state 0 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.072: Sending vfs7552_is_image_ready 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.072: [vfs7552] QUERY DATA READY entering state 1 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.072: Receiving 64 bytes 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.073: Got 6 bytes out of 64 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.073: [vfs7552] QUERY DATA READY completed successfully 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.073: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.073: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.073: [vfs7552] QUERY DATA READY entering state 0 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.073: Sending vfs7552_is_image_ready 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.073: [vfs7552] QUERY DATA READY entering state 1 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.073: Receiving 64 bytes 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.074: Got 6 bytes out of 64 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.074: [vfs7552] QUERY DATA READY completed successfully 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.074: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.074: [vfs7552] CAPTURE_NUM_STATES entering state 2 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.074: [vfs7552] REQUEST CHUNK entering state 0 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.074: Sending vfs7552_read_image_chunk 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.074: [vfs7552] REQUEST CHUNK completed successfully 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.074: [vfs7552] CAPTURE_NUM_STATES entering state 3 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.075: [vfs7552] CAPTURE_NUM_STATES entering state 2 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.075: [vfs7552] REQUEST CHUNK entering state 0 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.075: Sending vfs7552_read_image_chunk 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.075: [vfs7552] REQUEST CHUNK completed successfully 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.075: [vfs7552] CAPTURE_NUM_STATES entering state 3 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.076: [vfs7552] CAPTURE_NUM_STATES entering state 2 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.076: [vfs7552] REQUEST CHUNK entering state 0 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.076: Sending vfs7552_read_image_chunk 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.077: [vfs7552] REQUEST CHUNK completed successfully 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.077: [vfs7552] CAPTURE_NUM_STATES entering state 3 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.077: [vfs7552] CAPTURE_NUM_STATES entering state 4 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.077: Cleaning image 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.077: variance_after = 1532 431s 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.077: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.077: [vfs7552] QUERY DATA READY entering state 0 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.077: Sending vfs7552_is_image_ready 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.078: [vfs7552] QUERY DATA READY entering state 1 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.078: Receiving 64 bytes 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.078: Got 6 bytes out of 64 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.078: [vfs7552] QUERY DATA READY completed successfully 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.078: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.078: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.078: [vfs7552] QUERY DATA READY entering state 0 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.078: Sending vfs7552_is_image_ready 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.079: [vfs7552] QUERY DATA READY entering state 1 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.079: Receiving 64 bytes 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.079: Got 6 bytes out of 64 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.079: [vfs7552] QUERY DATA READY completed successfully 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.079: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.079: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.079: [vfs7552] QUERY DATA READY entering state 0 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.079: Sending vfs7552_is_image_ready 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.080: [vfs7552] QUERY DATA READY entering state 1 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.080: Receiving 64 bytes 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.080: Got 6 bytes out of 64 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.080: [vfs7552] QUERY DATA READY completed successfully 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.080: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.080: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.080: [vfs7552] QUERY DATA READY entering state 0 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.080: Sending vfs7552_is_image_ready 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.081: [vfs7552] QUERY DATA READY entering state 1 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.081: Receiving 64 bytes 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.081: Got 6 bytes out of 64 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.081: [vfs7552] QUERY DATA READY completed successfully 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.081: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.081: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.081: [vfs7552] QUERY DATA READY entering state 0 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.081: Sending vfs7552_is_image_ready 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.082: [vfs7552] QUERY DATA READY entering state 1 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.082: Receiving 64 bytes 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.082: Got 6 bytes out of 64 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.082: [vfs7552] QUERY DATA READY completed successfully 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.082: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.082: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.082: [vfs7552] QUERY DATA READY entering state 0 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.082: Sending vfs7552_is_image_ready 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.083: [vfs7552] QUERY DATA READY entering state 1 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.083: Receiving 64 bytes 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.083: Got 6 bytes out of 64 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.083: [vfs7552] QUERY DATA READY completed successfully 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.083: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.083: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.083: [vfs7552] QUERY DATA READY entering state 0 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.083: Sending vfs7552_is_image_ready 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.084: [vfs7552] QUERY DATA READY entering state 1 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.084: Receiving 64 bytes 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.084: Got 6 bytes out of 64 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.084: [vfs7552] QUERY DATA READY completed successfully 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.084: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.084: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.084: [vfs7552] QUERY DATA READY entering state 0 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.084: Sending vfs7552_is_image_ready 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.085: [vfs7552] QUERY DATA READY entering state 1 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.085: Receiving 64 bytes 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.085: Got 6 bytes out of 64 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.085: [vfs7552] QUERY DATA READY completed successfully 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.085: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.085: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.085: [vfs7552] QUERY DATA READY entering state 0 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.085: Sending vfs7552_is_image_ready 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.086: [vfs7552] QUERY DATA READY entering state 1 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.086: Receiving 64 bytes 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.086: Got 6 bytes out of 64 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.086: [vfs7552] QUERY DATA READY completed successfully 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.086: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.086: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.086: [vfs7552] QUERY DATA READY entering state 0 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.086: Sending vfs7552_is_image_ready 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.087: [vfs7552] QUERY DATA READY entering state 1 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.087: Receiving 64 bytes 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.087: Got 6 bytes out of 64 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.087: [vfs7552] QUERY DATA READY completed successfully 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.087: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.087: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.087: [vfs7552] QUERY DATA READY entering state 0 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.087: Sending vfs7552_is_image_ready 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.088: [vfs7552] QUERY DATA READY entering state 1 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.088: Receiving 64 bytes 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.088: Got 6 bytes out of 64 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.088: [vfs7552] QUERY DATA READY completed successfully 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.088: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.088: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.088: [vfs7552] QUERY DATA READY entering state 0 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.088: Sending vfs7552_is_image_ready 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.089: [vfs7552] QUERY DATA READY entering state 1 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.089: Receiving 64 bytes 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.089: Got 6 bytes out of 64 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.089: [vfs7552] QUERY DATA READY completed successfully 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.089: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.089: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.089: [vfs7552] QUERY DATA READY entering state 0 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.089: Sending vfs7552_is_image_ready 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.090: [vfs7552] QUERY DATA READY entering state 1 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.090: Receiving 64 bytes 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.090: Got 6 bytes out of 64 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.090: [vfs7552] QUERY DATA READY completed successfully 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.090: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.090: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.090: [vfs7552] QUERY DATA READY entering state 0 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.090: Sending vfs7552_is_image_ready 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.091: [vfs7552] QUERY DATA READY entering state 1 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.091: Receiving 64 bytes 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.091: Got 6 bytes out of 64 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.091: [vfs7552] QUERY DATA READY completed successfully 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.091: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.091: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.091: [vfs7552] QUERY DATA READY entering state 0 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.091: Sending vfs7552_is_image_ready 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.092: [vfs7552] QUERY DATA READY entering state 1 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.092: Receiving 64 bytes 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.092: Got 6 bytes out of 64 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.092: [vfs7552] QUERY DATA READY completed successfully 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.092: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.092: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.092: [vfs7552] QUERY DATA READY entering state 0 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.092: Sending vfs7552_is_image_ready 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.093: [vfs7552] QUERY DATA READY entering state 1 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.093: Receiving 64 bytes 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.093: Got 6 bytes out of 64 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.093: [vfs7552] QUERY DATA READY completed successfully 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.093: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.093: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.093: [vfs7552] QUERY DATA READY entering state 0 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.093: Sending vfs7552_is_image_ready 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.094: [vfs7552] QUERY DATA READY entering state 1 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.094: Receiving 64 bytes 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.094: Got 6 bytes out of 64 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.094: [vfs7552] QUERY DATA READY completed successfully 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.094: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.094: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.094: [vfs7552] QUERY DATA READY entering state 0 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.094: Sending vfs7552_is_image_ready 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.095: [vfs7552] QUERY DATA READY entering state 1 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.095: Receiving 64 bytes 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.095: Got 6 bytes out of 64 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.095: [vfs7552] QUERY DATA READY completed successfully 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.095: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.095: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.095: [vfs7552] QUERY DATA READY entering state 0 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.095: Sending vfs7552_is_image_ready 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.096: [vfs7552] QUERY DATA READY entering state 1 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.096: Receiving 64 bytes 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.096: Got 6 bytes out of 64 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.096: [vfs7552] QUERY DATA READY completed successfully 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.096: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.096: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.096: [vfs7552] QUERY DATA READY entering state 0 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.096: Sending vfs7552_is_image_ready 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.097: [vfs7552] QUERY DATA READY entering state 1 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.097: Receiving 64 bytes 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.097: Got 6 bytes out of 64 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.097: [vfs7552] QUERY DATA READY completed successfully 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.097: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.097: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.097: [vfs7552] QUERY DATA READY entering state 0 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.097: Sending vfs7552_is_image_ready 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.098: [vfs7552] QUERY DATA READY entering state 1 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.098: Receiving 64 bytes 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.098: Got 6 bytes out of 64 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.098: [vfs7552] QUERY DATA READY completed successfully 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.098: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.098: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.098: [vfs7552] QUERY DATA READY entering state 0 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.098: Sending vfs7552_is_image_ready 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.099: [vfs7552] QUERY DATA READY entering state 1 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.099: Receiving 64 bytes 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.099: Got 6 bytes out of 64 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.099: [vfs7552] QUERY DATA READY completed successfully 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.099: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.099: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.099: [vfs7552] QUERY DATA READY entering state 0 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.099: Sending vfs7552_is_image_ready 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.100: [vfs7552] QUERY DATA READY entering state 1 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.100: Receiving 64 bytes 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.100: Got 6 bytes out of 64 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.100: [vfs7552] QUERY DATA READY completed successfully 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.100: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.100: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.100: [vfs7552] QUERY DATA READY entering state 0 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.100: Sending vfs7552_is_image_ready 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.101: [vfs7552] QUERY DATA READY entering state 1 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.101: Receiving 64 bytes 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.101: Got 6 bytes out of 64 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.101: [vfs7552] QUERY DATA READY completed successfully 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.101: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.101: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.101: [vfs7552] QUERY DATA READY entering state 0 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.101: Sending vfs7552_is_image_ready 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.102: [vfs7552] QUERY DATA READY entering state 1 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.102: Receiving 64 bytes 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.102: Got 6 bytes out of 64 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.102: [vfs7552] QUERY DATA READY completed successfully 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.102: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.102: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.102: [vfs7552] QUERY DATA READY entering state 0 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.102: Sending vfs7552_is_image_ready 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.103: [vfs7552] QUERY DATA READY entering state 1 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.103: Receiving 64 bytes 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.103: Got 6 bytes out of 64 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.103: [vfs7552] QUERY DATA READY completed successfully 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.103: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.103: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.103: [vfs7552] QUERY DATA READY entering state 0 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.103: Sending vfs7552_is_image_ready 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.104: [vfs7552] QUERY DATA READY entering state 1 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.104: Receiving 64 bytes 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.104: Got 6 bytes out of 64 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.104: [vfs7552] QUERY DATA READY completed successfully 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.104: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.104: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.104: [vfs7552] QUERY DATA READY entering state 0 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.104: Sending vfs7552_is_image_ready 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.105: [vfs7552] QUERY DATA READY entering state 1 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.105: Receiving 64 bytes 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.105: Got 6 bytes out of 64 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.105: [vfs7552] QUERY DATA READY completed successfully 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.105: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.105: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.105: [vfs7552] QUERY DATA READY entering state 0 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.105: Sending vfs7552_is_image_ready 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.106: [vfs7552] QUERY DATA READY entering state 1 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.106: Receiving 64 bytes 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.106: Got 6 bytes out of 64 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.106: [vfs7552] QUERY DATA READY completed successfully 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.106: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.106: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.106: [vfs7552] QUERY DATA READY entering state 0 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.106: Sending vfs7552_is_image_ready 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.107: [vfs7552] QUERY DATA READY entering state 1 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.107: Receiving 64 bytes 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.107: Got 6 bytes out of 64 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.107: [vfs7552] QUERY DATA READY completed successfully 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.107: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.107: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.107: [vfs7552] QUERY DATA READY entering state 0 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.107: Sending vfs7552_is_image_ready 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.108: [vfs7552] QUERY DATA READY entering state 1 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.108: Receiving 64 bytes 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.108: Got 6 bytes out of 64 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.108: [vfs7552] QUERY DATA READY completed successfully 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.108: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.108: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.108: [vfs7552] QUERY DATA READY entering state 0 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.108: Sending vfs7552_is_image_ready 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.109: [vfs7552] QUERY DATA READY entering state 1 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.109: Receiving 64 bytes 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.109: Got 6 bytes out of 64 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.109: [vfs7552] QUERY DATA READY completed successfully 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.109: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.109: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.109: [vfs7552] QUERY DATA READY entering state 0 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.109: Sending vfs7552_is_image_ready 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.110: [vfs7552] QUERY DATA READY entering state 1 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.110: Receiving 64 bytes 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.110: Got 6 bytes out of 64 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.110: [vfs7552] QUERY DATA READY completed successfully 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.110: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.110: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.110: [vfs7552] QUERY DATA READY entering state 0 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.110: Sending vfs7552_is_image_ready 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.111: [vfs7552] QUERY DATA READY entering state 1 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.111: Receiving 64 bytes 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.111: Got 6 bytes out of 64 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.111: [vfs7552] QUERY DATA READY completed successfully 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.111: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.111: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.111: [vfs7552] QUERY DATA READY entering state 0 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.111: Sending vfs7552_is_image_ready 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.112: [vfs7552] QUERY DATA READY entering state 1 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.112: Receiving 64 bytes 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.112: Got 6 bytes out of 64 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.112: [vfs7552] QUERY DATA READY completed successfully 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.112: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.112: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.112: [vfs7552] QUERY DATA READY entering state 0 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.112: Sending vfs7552_is_image_ready 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.113: [vfs7552] QUERY DATA READY entering state 1 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.113: Receiving 64 bytes 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.113: Got 6 bytes out of 64 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.113: [vfs7552] QUERY DATA READY completed successfully 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.113: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.113: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.113: [vfs7552] QUERY DATA READY entering state 0 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.113: Sending vfs7552_is_image_ready 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.114: [vfs7552] QUERY DATA READY entering state 1 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.114: Receiving 64 bytes 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.114: Got 6 bytes out of 64 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.114: [vfs7552] QUERY DATA READY completed successfully 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.114: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.114: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.114: [vfs7552] QUERY DATA READY entering state 0 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.114: Sending vfs7552_is_image_ready 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.115: [vfs7552] QUERY DATA READY entering state 1 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.115: Receiving 64 bytes 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.115: Got 6 bytes out of 64 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.115: [vfs7552] QUERY DATA READY completed successfully 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.115: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.115: [vfs7552] CAPTURE_NUM_STATES entering state 2 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.115: [vfs7552] REQUEST CHUNK entering state 0 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.115: Sending vfs7552_read_image_chunk 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.116: [vfs7552] REQUEST CHUNK completed successfully 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.116: [vfs7552] CAPTURE_NUM_STATES entering state 3 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.116: [vfs7552] CAPTURE_NUM_STATES entering state 2 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.116: [vfs7552] REQUEST CHUNK entering state 0 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.116: Sending vfs7552_read_image_chunk 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.117: [vfs7552] REQUEST CHUNK completed successfully 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.117: [vfs7552] CAPTURE_NUM_STATES entering state 3 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.117: [vfs7552] CAPTURE_NUM_STATES entering state 2 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.117: [vfs7552] REQUEST CHUNK entering state 0 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.117: Sending vfs7552_read_image_chunk 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.118: [vfs7552] REQUEST CHUNK completed successfully 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.118: [vfs7552] CAPTURE_NUM_STATES entering state 3 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.118: [vfs7552] CAPTURE_NUM_STATES entering state 4 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.118: Cleaning image 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.118: variance_after = 1691 431s 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.118: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.118: [vfs7552] QUERY DATA READY entering state 0 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.118: Sending vfs7552_is_image_ready 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.119: [vfs7552] QUERY DATA READY entering state 1 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.119: Receiving 64 bytes 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.119: Got 6 bytes out of 64 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.119: [vfs7552] QUERY DATA READY completed successfully 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.119: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.119: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.119: [vfs7552] QUERY DATA READY entering state 0 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.119: Sending vfs7552_is_image_ready 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.120: [vfs7552] QUERY DATA READY entering state 1 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.120: Receiving 64 bytes 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.120: Got 6 bytes out of 64 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.120: [vfs7552] QUERY DATA READY completed successfully 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.120: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.120: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.120: [vfs7552] QUERY DATA READY entering state 0 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.120: Sending vfs7552_is_image_ready 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.121: [vfs7552] QUERY DATA READY entering state 1 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.121: Receiving 64 bytes 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.121: Got 6 bytes out of 64 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.121: [vfs7552] QUERY DATA READY completed successfully 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.121: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.121: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.121: [vfs7552] QUERY DATA READY entering state 0 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.121: Sending vfs7552_is_image_ready 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.122: [vfs7552] QUERY DATA READY entering state 1 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.122: Receiving 64 bytes 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.122: Got 6 bytes out of 64 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.122: [vfs7552] QUERY DATA READY completed successfully 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.122: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.122: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.122: [vfs7552] QUERY DATA READY entering state 0 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.122: Sending vfs7552_is_image_ready 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.123: [vfs7552] QUERY DATA READY entering state 1 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.123: Receiving 64 bytes 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.123: Got 6 bytes out of 64 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.123: [vfs7552] QUERY DATA READY completed successfully 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.123: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.123: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.123: [vfs7552] QUERY DATA READY entering state 0 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.123: Sending vfs7552_is_image_ready 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.124: [vfs7552] QUERY DATA READY entering state 1 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.124: Receiving 64 bytes 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.124: Got 6 bytes out of 64 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.124: [vfs7552] QUERY DATA READY completed successfully 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.124: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.124: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.124: [vfs7552] QUERY DATA READY entering state 0 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.124: Sending vfs7552_is_image_ready 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.125: [vfs7552] QUERY DATA READY entering state 1 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.125: Receiving 64 bytes 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.125: Got 6 bytes out of 64 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.125: [vfs7552] QUERY DATA READY completed successfully 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.125: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.125: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.125: [vfs7552] QUERY DATA READY entering state 0 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.125: Sending vfs7552_is_image_ready 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.126: [vfs7552] QUERY DATA READY entering state 1 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.126: Receiving 64 bytes 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.126: Got 6 bytes out of 64 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.126: [vfs7552] QUERY DATA READY completed successfully 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.126: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.126: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.126: [vfs7552] QUERY DATA READY entering state 0 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.126: Sending vfs7552_is_image_ready 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.127: [vfs7552] QUERY DATA READY entering state 1 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.127: Receiving 64 bytes 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.127: Got 6 bytes out of 64 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.127: [vfs7552] QUERY DATA READY completed successfully 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.127: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.127: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.127: [vfs7552] QUERY DATA READY entering state 0 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.127: Sending vfs7552_is_image_ready 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.128: [vfs7552] QUERY DATA READY entering state 1 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.128: Receiving 64 bytes 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.128: Got 6 bytes out of 64 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.128: [vfs7552] QUERY DATA READY completed successfully 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.128: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.128: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.128: [vfs7552] QUERY DATA READY entering state 0 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.128: Sending vfs7552_is_image_ready 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.129: [vfs7552] QUERY DATA READY entering state 1 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.129: Receiving 64 bytes 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.129: Got 6 bytes out of 64 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.129: [vfs7552] QUERY DATA READY completed successfully 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.129: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.129: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.129: [vfs7552] QUERY DATA READY entering state 0 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.129: Sending vfs7552_is_image_ready 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.130: [vfs7552] QUERY DATA READY entering state 1 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.130: Receiving 64 bytes 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.130: Got 6 bytes out of 64 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.130: [vfs7552] QUERY DATA READY completed successfully 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.130: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.130: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.130: [vfs7552] QUERY DATA READY entering state 0 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.130: Sending vfs7552_is_image_ready 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.131: [vfs7552] QUERY DATA READY entering state 1 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.131: Receiving 64 bytes 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.131: Got 6 bytes out of 64 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.131: [vfs7552] QUERY DATA READY completed successfully 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.131: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.131: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.131: [vfs7552] QUERY DATA READY entering state 0 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.131: Sending vfs7552_is_image_ready 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.132: [vfs7552] QUERY DATA READY entering state 1 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.132: Receiving 64 bytes 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.132: Got 6 bytes out of 64 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.132: [vfs7552] QUERY DATA READY completed successfully 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.132: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.132: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.132: [vfs7552] QUERY DATA READY entering state 0 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.132: Sending vfs7552_is_image_ready 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.133: [vfs7552] QUERY DATA READY entering state 1 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.133: Receiving 64 bytes 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.133: Got 6 bytes out of 64 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.133: [vfs7552] QUERY DATA READY completed successfully 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.133: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.133: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.133: [vfs7552] QUERY DATA READY entering state 0 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.133: Sending vfs7552_is_image_ready 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.134: [vfs7552] QUERY DATA READY entering state 1 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.134: Receiving 64 bytes 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.134: Got 6 bytes out of 64 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.134: [vfs7552] QUERY DATA READY completed successfully 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.134: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.134: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.134: [vfs7552] QUERY DATA READY entering state 0 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.134: Sending vfs7552_is_image_ready 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.135: [vfs7552] QUERY DATA READY entering state 1 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.135: Receiving 64 bytes 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.135: Got 6 bytes out of 64 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.135: [vfs7552] QUERY DATA READY completed successfully 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.135: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.135: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.135: [vfs7552] QUERY DATA READY entering state 0 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.135: Sending vfs7552_is_image_ready 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.136: [vfs7552] QUERY DATA READY entering state 1 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.136: Receiving 64 bytes 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.136: Got 6 bytes out of 64 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.136: [vfs7552] QUERY DATA READY completed successfully 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.136: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.136: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.136: [vfs7552] QUERY DATA READY entering state 0 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.136: Sending vfs7552_is_image_ready 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.137: [vfs7552] QUERY DATA READY entering state 1 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.137: Receiving 64 bytes 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.137: Got 6 bytes out of 64 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.137: [vfs7552] QUERY DATA READY completed successfully 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.137: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.137: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.137: [vfs7552] QUERY DATA READY entering state 0 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.137: Sending vfs7552_is_image_ready 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.138: [vfs7552] QUERY DATA READY entering state 1 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.138: Receiving 64 bytes 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.138: Got 6 bytes out of 64 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.138: [vfs7552] QUERY DATA READY completed successfully 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.138: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.138: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.138: [vfs7552] QUERY DATA READY entering state 0 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.138: Sending vfs7552_is_image_ready 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.139: [vfs7552] QUERY DATA READY entering state 1 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.139: Receiving 64 bytes 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.139: Got 6 bytes out of 64 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.139: [vfs7552] QUERY DATA READY completed successfully 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.139: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.139: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.139: [vfs7552] QUERY DATA READY entering state 0 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.139: Sending vfs7552_is_image_ready 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.140: [vfs7552] QUERY DATA READY entering state 1 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.140: Receiving 64 bytes 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.140: Got 6 bytes out of 64 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.140: [vfs7552] QUERY DATA READY completed successfully 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.140: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.140: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.140: [vfs7552] QUERY DATA READY entering state 0 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.140: Sending vfs7552_is_image_ready 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.141: [vfs7552] QUERY DATA READY entering state 1 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.141: Receiving 64 bytes 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.141: Got 6 bytes out of 64 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.141: [vfs7552] QUERY DATA READY completed successfully 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.141: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.141: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.141: [vfs7552] QUERY DATA READY entering state 0 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.141: Sending vfs7552_is_image_ready 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.142: [vfs7552] QUERY DATA READY entering state 1 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.142: Receiving 64 bytes 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.142: Got 6 bytes out of 64 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.142: [vfs7552] QUERY DATA READY completed successfully 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.142: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.142: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.142: [vfs7552] QUERY DATA READY entering state 0 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.142: Sending vfs7552_is_image_ready 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.143: [vfs7552] QUERY DATA READY entering state 1 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.143: Receiving 64 bytes 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.143: Got 6 bytes out of 64 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.143: [vfs7552] QUERY DATA READY completed successfully 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.143: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.143: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.143: [vfs7552] QUERY DATA READY entering state 0 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.143: Sending vfs7552_is_image_ready 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.144: [vfs7552] QUERY DATA READY entering state 1 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.144: Receiving 64 bytes 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.144: Got 6 bytes out of 64 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.144: [vfs7552] QUERY DATA READY completed successfully 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.144: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.144: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.144: [vfs7552] QUERY DATA READY entering state 0 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.144: Sending vfs7552_is_image_ready 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.145: [vfs7552] QUERY DATA READY entering state 1 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.145: Receiving 64 bytes 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.145: Got 6 bytes out of 64 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.145: [vfs7552] QUERY DATA READY completed successfully 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.145: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.145: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.145: [vfs7552] QUERY DATA READY entering state 0 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.145: Sending vfs7552_is_image_ready 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.146: [vfs7552] QUERY DATA READY entering state 1 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.146: Receiving 64 bytes 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.146: Got 6 bytes out of 64 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.146: [vfs7552] QUERY DATA READY completed successfully 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.146: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.146: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.146: [vfs7552] QUERY DATA READY entering state 0 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.146: Sending vfs7552_is_image_ready 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.147: [vfs7552] QUERY DATA READY entering state 1 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.147: Receiving 64 bytes 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.147: Got 6 bytes out of 64 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.147: [vfs7552] QUERY DATA READY completed successfully 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.147: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.147: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.147: [vfs7552] QUERY DATA READY entering state 0 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.147: Sending vfs7552_is_image_ready 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.148: [vfs7552] QUERY DATA READY entering state 1 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.148: Receiving 64 bytes 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.148: Got 6 bytes out of 64 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.148: [vfs7552] QUERY DATA READY completed successfully 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.148: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.148: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.148: [vfs7552] QUERY DATA READY entering state 0 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.148: Sending vfs7552_is_image_ready 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.148: [vfs7552] QUERY DATA READY entering state 1 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.149: Receiving 64 bytes 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.149: Got 6 bytes out of 64 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.149: [vfs7552] QUERY DATA READY completed successfully 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.149: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.149: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.149: [vfs7552] QUERY DATA READY entering state 0 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.149: Sending vfs7552_is_image_ready 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.149: [vfs7552] QUERY DATA READY entering state 1 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.149: Receiving 64 bytes 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.150: Got 6 bytes out of 64 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.150: [vfs7552] QUERY DATA READY completed successfully 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.150: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.150: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.150: [vfs7552] QUERY DATA READY entering state 0 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.150: Sending vfs7552_is_image_ready 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.150: [vfs7552] QUERY DATA READY entering state 1 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.150: Receiving 64 bytes 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.151: Got 6 bytes out of 64 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.151: [vfs7552] QUERY DATA READY completed successfully 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.151: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.151: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.151: [vfs7552] QUERY DATA READY entering state 0 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.151: Sending vfs7552_is_image_ready 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.151: [vfs7552] QUERY DATA READY entering state 1 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.151: Receiving 64 bytes 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.152: Got 6 bytes out of 64 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.152: [vfs7552] QUERY DATA READY completed successfully 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.152: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.152: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.152: [vfs7552] QUERY DATA READY entering state 0 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.152: Sending vfs7552_is_image_ready 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.152: [vfs7552] QUERY DATA READY entering state 1 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.152: Receiving 64 bytes 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.153: Got 6 bytes out of 64 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.153: [vfs7552] QUERY DATA READY completed successfully 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.153: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.153: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.153: [vfs7552] QUERY DATA READY entering state 0 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.153: Sending vfs7552_is_image_ready 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.153: [vfs7552] QUERY DATA READY entering state 1 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.153: Receiving 64 bytes 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.154: Got 6 bytes out of 64 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.154: [vfs7552] QUERY DATA READY completed successfully 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.154: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.154: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.154: [vfs7552] QUERY DATA READY entering state 0 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.154: Sending vfs7552_is_image_ready 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.154: [vfs7552] QUERY DATA READY entering state 1 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.154: Receiving 64 bytes 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.155: Got 6 bytes out of 64 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.155: [vfs7552] QUERY DATA READY completed successfully 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.155: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.155: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.155: [vfs7552] QUERY DATA READY entering state 0 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.155: Sending vfs7552_is_image_ready 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.155: [vfs7552] QUERY DATA READY entering state 1 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.155: Receiving 64 bytes 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.156: Got 6 bytes out of 64 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.156: [vfs7552] QUERY DATA READY completed successfully 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.156: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.156: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.156: [vfs7552] QUERY DATA READY entering state 0 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.156: Sending vfs7552_is_image_ready 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.156: [vfs7552] QUERY DATA READY entering state 1 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.156: Receiving 64 bytes 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.157: Got 6 bytes out of 64 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.157: [vfs7552] QUERY DATA READY completed successfully 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.157: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.157: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.157: [vfs7552] QUERY DATA READY entering state 0 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.157: Sending vfs7552_is_image_ready 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.157: [vfs7552] QUERY DATA READY entering state 1 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.157: Receiving 64 bytes 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.158: Got 6 bytes out of 64 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.158: [vfs7552] QUERY DATA READY completed successfully 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.158: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.158: [vfs7552] CAPTURE_NUM_STATES entering state 2 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.158: [vfs7552] REQUEST CHUNK entering state 0 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.158: Sending vfs7552_read_image_chunk 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.158: [vfs7552] REQUEST CHUNK completed successfully 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.158: [vfs7552] CAPTURE_NUM_STATES entering state 3 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.159: [vfs7552] CAPTURE_NUM_STATES entering state 2 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.159: [vfs7552] REQUEST CHUNK entering state 0 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.159: Sending vfs7552_read_image_chunk 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.159: [vfs7552] REQUEST CHUNK completed successfully 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.159: [vfs7552] CAPTURE_NUM_STATES entering state 3 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.160: [vfs7552] CAPTURE_NUM_STATES entering state 2 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.160: [vfs7552] REQUEST CHUNK entering state 0 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.160: Sending vfs7552_read_image_chunk 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.160: [vfs7552] REQUEST CHUNK completed successfully 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.160: [vfs7552] CAPTURE_NUM_STATES entering state 3 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.161: [vfs7552] CAPTURE_NUM_STATES entering state 4 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.161: Cleaning image 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.161: variance_after = 1845 431s 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.161: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.161: [vfs7552] QUERY DATA READY entering state 0 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.161: Sending vfs7552_is_image_ready 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.161: [vfs7552] QUERY DATA READY entering state 1 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.161: Receiving 64 bytes 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.162: Got 6 bytes out of 64 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.162: [vfs7552] QUERY DATA READY completed successfully 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.162: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.162: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.162: [vfs7552] QUERY DATA READY entering state 0 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.162: Sending vfs7552_is_image_ready 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.162: [vfs7552] QUERY DATA READY entering state 1 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.163: Receiving 64 bytes 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.163: Got 6 bytes out of 64 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.163: [vfs7552] QUERY DATA READY completed successfully 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.163: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.163: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.163: [vfs7552] QUERY DATA READY entering state 0 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.163: Sending vfs7552_is_image_ready 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.164: [vfs7552] QUERY DATA READY entering state 1 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.164: Receiving 64 bytes 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.164: Got 6 bytes out of 64 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.164: [vfs7552] QUERY DATA READY completed successfully 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.164: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.164: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.164: [vfs7552] QUERY DATA READY entering state 0 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.164: Sending vfs7552_is_image_ready 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.164: [vfs7552] QUERY DATA READY entering state 1 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.164: Receiving 64 bytes 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.165: Got 6 bytes out of 64 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.165: [vfs7552] QUERY DATA READY completed successfully 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.165: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.165: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.165: [vfs7552] QUERY DATA READY entering state 0 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.165: Sending vfs7552_is_image_ready 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.165: [vfs7552] QUERY DATA READY entering state 1 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.165: Receiving 64 bytes 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.166: Got 6 bytes out of 64 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.166: [vfs7552] QUERY DATA READY completed successfully 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.166: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.166: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.166: [vfs7552] QUERY DATA READY entering state 0 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.166: Sending vfs7552_is_image_ready 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.166: [vfs7552] QUERY DATA READY entering state 1 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.166: Receiving 64 bytes 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.167: Got 6 bytes out of 64 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.167: [vfs7552] QUERY DATA READY completed successfully 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.167: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.167: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.167: [vfs7552] QUERY DATA READY entering state 0 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.167: Sending vfs7552_is_image_ready 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.167: [vfs7552] QUERY DATA READY entering state 1 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.167: Receiving 64 bytes 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.168: Got 6 bytes out of 64 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.168: [vfs7552] QUERY DATA READY completed successfully 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.168: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.168: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.168: [vfs7552] QUERY DATA READY entering state 0 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.168: Sending vfs7552_is_image_ready 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.168: [vfs7552] QUERY DATA READY entering state 1 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.168: Receiving 64 bytes 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.169: Got 6 bytes out of 64 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.169: [vfs7552] QUERY DATA READY completed successfully 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.169: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.169: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.169: [vfs7552] QUERY DATA READY entering state 0 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.169: Sending vfs7552_is_image_ready 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.169: [vfs7552] QUERY DATA READY entering state 1 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.169: Receiving 64 bytes 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.170: Got 6 bytes out of 64 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.170: [vfs7552] QUERY DATA READY completed successfully 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.170: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.170: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.170: [vfs7552] QUERY DATA READY entering state 0 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.170: Sending vfs7552_is_image_ready 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.170: [vfs7552] QUERY DATA READY entering state 1 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.170: Receiving 64 bytes 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.171: Got 6 bytes out of 64 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.171: [vfs7552] QUERY DATA READY completed successfully 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.171: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.171: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.171: [vfs7552] QUERY DATA READY entering state 0 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.171: Sending vfs7552_is_image_ready 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.171: [vfs7552] QUERY DATA READY entering state 1 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.171: Receiving 64 bytes 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.172: Got 6 bytes out of 64 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.172: [vfs7552] QUERY DATA READY completed successfully 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.172: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.172: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.172: [vfs7552] QUERY DATA READY entering state 0 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.172: Sending vfs7552_is_image_ready 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.172: [vfs7552] QUERY DATA READY entering state 1 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.172: Receiving 64 bytes 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.173: Got 6 bytes out of 64 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.173: [vfs7552] QUERY DATA READY completed successfully 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.173: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.173: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.173: [vfs7552] QUERY DATA READY entering state 0 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.173: Sending vfs7552_is_image_ready 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.173: [vfs7552] QUERY DATA READY entering state 1 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.173: Receiving 64 bytes 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.174: Got 6 bytes out of 64 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.174: [vfs7552] QUERY DATA READY completed successfully 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.174: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.174: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.174: [vfs7552] QUERY DATA READY entering state 0 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.174: Sending vfs7552_is_image_ready 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.174: [vfs7552] QUERY DATA READY entering state 1 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.174: Receiving 64 bytes 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.175: Got 6 bytes out of 64 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.175: [vfs7552] QUERY DATA READY completed successfully 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.175: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.175: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.175: [vfs7552] QUERY DATA READY entering state 0 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.175: Sending vfs7552_is_image_ready 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.175: [vfs7552] QUERY DATA READY entering state 1 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.175: Receiving 64 bytes 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.176: Got 6 bytes out of 64 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.176: [vfs7552] QUERY DATA READY completed successfully 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.176: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.176: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.176: [vfs7552] QUERY DATA READY entering state 0 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.176: Sending vfs7552_is_image_ready 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.176: [vfs7552] QUERY DATA READY entering state 1 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.176: Receiving 64 bytes 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.177: Got 6 bytes out of 64 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.177: [vfs7552] QUERY DATA READY completed successfully 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.177: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.177: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.177: [vfs7552] QUERY DATA READY entering state 0 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.177: Sending vfs7552_is_image_ready 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.177: [vfs7552] QUERY DATA READY entering state 1 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.177: Receiving 64 bytes 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.178: Got 6 bytes out of 64 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.178: [vfs7552] QUERY DATA READY completed successfully 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.178: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.178: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.178: [vfs7552] QUERY DATA READY entering state 0 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.178: Sending vfs7552_is_image_ready 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.178: [vfs7552] QUERY DATA READY entering state 1 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.178: Receiving 64 bytes 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.179: Got 6 bytes out of 64 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.179: [vfs7552] QUERY DATA READY completed successfully 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.179: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.179: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.179: [vfs7552] QUERY DATA READY entering state 0 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.179: Sending vfs7552_is_image_ready 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.179: [vfs7552] QUERY DATA READY entering state 1 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.179: Receiving 64 bytes 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.180: Got 6 bytes out of 64 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.180: [vfs7552] QUERY DATA READY completed successfully 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.180: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.180: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.180: [vfs7552] QUERY DATA READY entering state 0 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.180: Sending vfs7552_is_image_ready 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.180: [vfs7552] QUERY DATA READY entering state 1 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.180: Receiving 64 bytes 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.181: Got 6 bytes out of 64 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.181: [vfs7552] QUERY DATA READY completed successfully 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.181: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.181: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.181: [vfs7552] QUERY DATA READY entering state 0 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.181: Sending vfs7552_is_image_ready 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.181: [vfs7552] QUERY DATA READY entering state 1 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.181: Receiving 64 bytes 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.182: Got 6 bytes out of 64 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.182: [vfs7552] QUERY DATA READY completed successfully 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.182: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.182: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.182: [vfs7552] QUERY DATA READY entering state 0 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.182: Sending vfs7552_is_image_ready 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.182: [vfs7552] QUERY DATA READY entering state 1 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.182: Receiving 64 bytes 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.183: Got 6 bytes out of 64 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.183: [vfs7552] QUERY DATA READY completed successfully 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.183: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.183: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.183: [vfs7552] QUERY DATA READY entering state 0 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.183: Sending vfs7552_is_image_ready 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.183: [vfs7552] QUERY DATA READY entering state 1 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.183: Receiving 64 bytes 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.184: Got 6 bytes out of 64 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.184: [vfs7552] QUERY DATA READY completed successfully 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.184: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.184: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.184: [vfs7552] QUERY DATA READY entering state 0 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.184: Sending vfs7552_is_image_ready 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.184: [vfs7552] QUERY DATA READY entering state 1 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.184: Receiving 64 bytes 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.185: Got 6 bytes out of 64 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.185: [vfs7552] QUERY DATA READY completed successfully 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.185: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.185: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.185: [vfs7552] QUERY DATA READY entering state 0 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.185: Sending vfs7552_is_image_ready 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.185: [vfs7552] QUERY DATA READY entering state 1 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.185: Receiving 64 bytes 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.186: Got 6 bytes out of 64 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.186: [vfs7552] QUERY DATA READY completed successfully 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.186: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.186: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.186: [vfs7552] QUERY DATA READY entering state 0 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.186: Sending vfs7552_is_image_ready 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.186: [vfs7552] QUERY DATA READY entering state 1 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.186: Receiving 64 bytes 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.187: Got 6 bytes out of 64 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.187: [vfs7552] QUERY DATA READY completed successfully 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.187: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.187: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.187: [vfs7552] QUERY DATA READY entering state 0 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.187: Sending vfs7552_is_image_ready 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.187: [vfs7552] QUERY DATA READY entering state 1 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.187: Receiving 64 bytes 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.188: Got 6 bytes out of 64 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.188: [vfs7552] QUERY DATA READY completed successfully 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.188: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.188: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.188: [vfs7552] QUERY DATA READY entering state 0 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.188: Sending vfs7552_is_image_ready 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.188: [vfs7552] QUERY DATA READY entering state 1 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.188: Receiving 64 bytes 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.189: Got 6 bytes out of 64 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.189: [vfs7552] QUERY DATA READY completed successfully 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.189: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.189: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.189: [vfs7552] QUERY DATA READY entering state 0 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.189: Sending vfs7552_is_image_ready 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.189: [vfs7552] QUERY DATA READY entering state 1 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.189: Receiving 64 bytes 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.190: Got 6 bytes out of 64 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.190: [vfs7552] QUERY DATA READY completed successfully 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.190: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.190: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.190: [vfs7552] QUERY DATA READY entering state 0 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.190: Sending vfs7552_is_image_ready 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.190: [vfs7552] QUERY DATA READY entering state 1 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.190: Receiving 64 bytes 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.191: Got 6 bytes out of 64 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.191: [vfs7552] QUERY DATA READY completed successfully 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.191: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.191: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.191: [vfs7552] QUERY DATA READY entering state 0 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.191: Sending vfs7552_is_image_ready 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.191: [vfs7552] QUERY DATA READY entering state 1 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.191: Receiving 64 bytes 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.192: Got 6 bytes out of 64 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.192: [vfs7552] QUERY DATA READY completed successfully 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.192: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.192: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.192: [vfs7552] QUERY DATA READY entering state 0 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.192: Sending vfs7552_is_image_ready 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.192: [vfs7552] QUERY DATA READY entering state 1 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.192: Receiving 64 bytes 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.193: Got 6 bytes out of 64 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.193: [vfs7552] QUERY DATA READY completed successfully 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.193: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.193: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.193: [vfs7552] QUERY DATA READY entering state 0 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.193: Sending vfs7552_is_image_ready 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.193: [vfs7552] QUERY DATA READY entering state 1 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.193: Receiving 64 bytes 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.194: Got 6 bytes out of 64 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.194: [vfs7552] QUERY DATA READY completed successfully 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.194: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.194: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.194: [vfs7552] QUERY DATA READY entering state 0 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.194: Sending vfs7552_is_image_ready 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.194: [vfs7552] QUERY DATA READY entering state 1 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.194: Receiving 64 bytes 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.195: Got 6 bytes out of 64 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.195: [vfs7552] QUERY DATA READY completed successfully 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.195: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.195: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.195: [vfs7552] QUERY DATA READY entering state 0 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.195: Sending vfs7552_is_image_ready 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.195: [vfs7552] QUERY DATA READY entering state 1 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.195: Receiving 64 bytes 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.196: Got 6 bytes out of 64 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.196: [vfs7552] QUERY DATA READY completed successfully 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.196: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.196: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.196: [vfs7552] QUERY DATA READY entering state 0 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.196: Sending vfs7552_is_image_ready 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.196: [vfs7552] QUERY DATA READY entering state 1 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.196: Receiving 64 bytes 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.197: Got 6 bytes out of 64 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.197: [vfs7552] QUERY DATA READY completed successfully 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.197: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.197: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.197: [vfs7552] QUERY DATA READY entering state 0 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.197: Sending vfs7552_is_image_ready 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.197: [vfs7552] QUERY DATA READY entering state 1 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.197: Receiving 64 bytes 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.198: Got 6 bytes out of 64 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.198: [vfs7552] QUERY DATA READY completed successfully 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.198: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.198: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.198: [vfs7552] QUERY DATA READY entering state 0 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.198: Sending vfs7552_is_image_ready 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.198: [vfs7552] QUERY DATA READY entering state 1 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.198: Receiving 64 bytes 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.199: Got 6 bytes out of 64 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.199: [vfs7552] QUERY DATA READY completed successfully 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.199: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.199: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.199: [vfs7552] QUERY DATA READY entering state 0 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.199: Sending vfs7552_is_image_ready 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.199: [vfs7552] QUERY DATA READY entering state 1 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.199: Receiving 64 bytes 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.200: Got 6 bytes out of 64 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.200: [vfs7552] QUERY DATA READY completed successfully 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.200: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.200: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.200: [vfs7552] QUERY DATA READY entering state 0 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.200: Sending vfs7552_is_image_ready 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.200: [vfs7552] QUERY DATA READY entering state 1 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.200: Receiving 64 bytes 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.201: Got 6 bytes out of 64 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.201: [vfs7552] QUERY DATA READY completed successfully 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.201: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.201: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.201: [vfs7552] QUERY DATA READY entering state 0 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.201: Sending vfs7552_is_image_ready 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.201: [vfs7552] QUERY DATA READY entering state 1 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.201: Receiving 64 bytes 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.202: Got 6 bytes out of 64 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.202: [vfs7552] QUERY DATA READY completed successfully 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.202: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.202: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.202: [vfs7552] QUERY DATA READY entering state 0 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.202: Sending vfs7552_is_image_ready 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.202: [vfs7552] QUERY DATA READY entering state 1 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.202: Receiving 64 bytes 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.203: Got 6 bytes out of 64 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.203: [vfs7552] QUERY DATA READY completed successfully 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.203: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.203: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.203: [vfs7552] QUERY DATA READY entering state 0 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.203: Sending vfs7552_is_image_ready 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.203: [vfs7552] QUERY DATA READY entering state 1 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.203: Receiving 64 bytes 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.204: Got 6 bytes out of 64 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.204: [vfs7552] QUERY DATA READY completed successfully 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.204: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.204: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.204: [vfs7552] QUERY DATA READY entering state 0 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.204: Sending vfs7552_is_image_ready 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.204: [vfs7552] QUERY DATA READY entering state 1 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.204: Receiving 64 bytes 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.205: Got 6 bytes out of 64 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.205: [vfs7552] QUERY DATA READY completed successfully 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.205: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.205: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.205: [vfs7552] QUERY DATA READY entering state 0 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.205: Sending vfs7552_is_image_ready 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.205: [vfs7552] QUERY DATA READY entering state 1 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.205: Receiving 64 bytes 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.205: Got 6 bytes out of 64 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.205: [vfs7552] QUERY DATA READY completed successfully 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.205: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.205: [vfs7552] CAPTURE_NUM_STATES entering state 2 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.205: [vfs7552] REQUEST CHUNK entering state 0 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.205: Sending vfs7552_read_image_chunk 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.206: [vfs7552] REQUEST CHUNK completed successfully 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.206: [vfs7552] CAPTURE_NUM_STATES entering state 3 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.206: [vfs7552] CAPTURE_NUM_STATES entering state 2 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.207: [vfs7552] REQUEST CHUNK entering state 0 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.207: Sending vfs7552_read_image_chunk 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.207: [vfs7552] REQUEST CHUNK completed successfully 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.207: [vfs7552] CAPTURE_NUM_STATES entering state 3 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.208: [vfs7552] CAPTURE_NUM_STATES entering state 2 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.208: [vfs7552] REQUEST CHUNK entering state 0 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.208: Sending vfs7552_read_image_chunk 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.208: [vfs7552] REQUEST CHUNK completed successfully 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.208: [vfs7552] CAPTURE_NUM_STATES entering state 3 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.209: [vfs7552] CAPTURE_NUM_STATES entering state 4 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.209: Cleaning image 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.209: variance_after = 2342 431s 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.209: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.209: [vfs7552] QUERY DATA READY entering state 0 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.209: Sending vfs7552_is_image_ready 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.209: [vfs7552] QUERY DATA READY entering state 1 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.209: Receiving 64 bytes 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.210: Got 6 bytes out of 64 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.210: [vfs7552] QUERY DATA READY completed successfully 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.210: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.210: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.210: [vfs7552] QUERY DATA READY entering state 0 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.210: Sending vfs7552_is_image_ready 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.210: [vfs7552] QUERY DATA READY entering state 1 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.210: Receiving 64 bytes 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.211: Got 6 bytes out of 64 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.211: [vfs7552] QUERY DATA READY completed successfully 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.211: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.211: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.211: [vfs7552] QUERY DATA READY entering state 0 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.211: Sending vfs7552_is_image_ready 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.211: [vfs7552] QUERY DATA READY entering state 1 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.211: Receiving 64 bytes 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.211: Got 6 bytes out of 64 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.212: [vfs7552] QUERY DATA READY completed successfully 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.212: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.212: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.212: [vfs7552] QUERY DATA READY entering state 0 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.212: Sending vfs7552_is_image_ready 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.212: [vfs7552] QUERY DATA READY entering state 1 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.212: Receiving 64 bytes 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.212: Got 6 bytes out of 64 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.213: [vfs7552] QUERY DATA READY completed successfully 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.213: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.213: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.213: [vfs7552] QUERY DATA READY entering state 0 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.213: Sending vfs7552_is_image_ready 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.213: [vfs7552] QUERY DATA READY entering state 1 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.213: Receiving 64 bytes 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.213: Got 6 bytes out of 64 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.214: [vfs7552] QUERY DATA READY completed successfully 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.214: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.214: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.214: [vfs7552] QUERY DATA READY entering state 0 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.214: Sending vfs7552_is_image_ready 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.214: [vfs7552] QUERY DATA READY entering state 1 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.214: Receiving 64 bytes 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.215: Got 6 bytes out of 64 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.215: [vfs7552] QUERY DATA READY completed successfully 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.215: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.215: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.215: [vfs7552] QUERY DATA READY entering state 0 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.215: Sending vfs7552_is_image_ready 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.215: [vfs7552] QUERY DATA READY entering state 1 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.215: Receiving 64 bytes 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.216: Got 6 bytes out of 64 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.216: [vfs7552] QUERY DATA READY completed successfully 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.216: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.216: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.216: [vfs7552] QUERY DATA READY entering state 0 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.216: Sending vfs7552_is_image_ready 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.216: [vfs7552] QUERY DATA READY entering state 1 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.216: Receiving 64 bytes 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.217: Got 6 bytes out of 64 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.217: [vfs7552] QUERY DATA READY completed successfully 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.217: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.217: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.217: [vfs7552] QUERY DATA READY entering state 0 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.217: Sending vfs7552_is_image_ready 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.217: [vfs7552] QUERY DATA READY entering state 1 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.217: Receiving 64 bytes 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.218: Got 6 bytes out of 64 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.218: [vfs7552] QUERY DATA READY completed successfully 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.218: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.218: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.218: [vfs7552] QUERY DATA READY entering state 0 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.218: Sending vfs7552_is_image_ready 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.218: [vfs7552] QUERY DATA READY entering state 1 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.218: Receiving 64 bytes 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.219: Got 6 bytes out of 64 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.219: [vfs7552] QUERY DATA READY completed successfully 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.219: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.219: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.219: [vfs7552] QUERY DATA READY entering state 0 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.219: Sending vfs7552_is_image_ready 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.219: [vfs7552] QUERY DATA READY entering state 1 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.219: Receiving 64 bytes 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.220: Got 6 bytes out of 64 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.220: [vfs7552] QUERY DATA READY completed successfully 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.220: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.220: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.220: [vfs7552] QUERY DATA READY entering state 0 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.220: Sending vfs7552_is_image_ready 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.220: [vfs7552] QUERY DATA READY entering state 1 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.220: Receiving 64 bytes 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.221: Got 6 bytes out of 64 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.221: [vfs7552] QUERY DATA READY completed successfully 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.221: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.221: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.221: [vfs7552] QUERY DATA READY entering state 0 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.221: Sending vfs7552_is_image_ready 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.221: [vfs7552] QUERY DATA READY entering state 1 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.221: Receiving 64 bytes 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.222: Got 6 bytes out of 64 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.222: [vfs7552] QUERY DATA READY completed successfully 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.222: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.222: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.222: [vfs7552] QUERY DATA READY entering state 0 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.222: Sending vfs7552_is_image_ready 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.222: [vfs7552] QUERY DATA READY entering state 1 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.222: Receiving 64 bytes 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.223: Got 6 bytes out of 64 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.223: [vfs7552] QUERY DATA READY completed successfully 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.223: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.223: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.223: [vfs7552] QUERY DATA READY entering state 0 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.223: Sending vfs7552_is_image_ready 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.223: [vfs7552] QUERY DATA READY entering state 1 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.223: Receiving 64 bytes 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.224: Got 6 bytes out of 64 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.224: [vfs7552] QUERY DATA READY completed successfully 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.224: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.224: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.224: [vfs7552] QUERY DATA READY entering state 0 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.224: Sending vfs7552_is_image_ready 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.224: [vfs7552] QUERY DATA READY entering state 1 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.224: Receiving 64 bytes 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.225: Got 6 bytes out of 64 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.225: [vfs7552] QUERY DATA READY completed successfully 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.225: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.225: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.225: [vfs7552] QUERY DATA READY entering state 0 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.225: Sending vfs7552_is_image_ready 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.225: [vfs7552] QUERY DATA READY entering state 1 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.225: Receiving 64 bytes 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.226: Got 6 bytes out of 64 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.226: [vfs7552] QUERY DATA READY completed successfully 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.226: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.226: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.226: [vfs7552] QUERY DATA READY entering state 0 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.226: Sending vfs7552_is_image_ready 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.226: [vfs7552] QUERY DATA READY entering state 1 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.226: Receiving 64 bytes 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.227: Got 6 bytes out of 64 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.227: [vfs7552] QUERY DATA READY completed successfully 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.227: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.227: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.227: [vfs7552] QUERY DATA READY entering state 0 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.227: Sending vfs7552_is_image_ready 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.227: [vfs7552] QUERY DATA READY entering state 1 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.227: Receiving 64 bytes 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.228: Got 6 bytes out of 64 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.228: [vfs7552] QUERY DATA READY completed successfully 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.228: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.228: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.228: [vfs7552] QUERY DATA READY entering state 0 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.228: Sending vfs7552_is_image_ready 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.228: [vfs7552] QUERY DATA READY entering state 1 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.228: Receiving 64 bytes 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.229: Got 6 bytes out of 64 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.229: [vfs7552] QUERY DATA READY completed successfully 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.229: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.229: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.229: [vfs7552] QUERY DATA READY entering state 0 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.229: Sending vfs7552_is_image_ready 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.229: [vfs7552] QUERY DATA READY entering state 1 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.229: Receiving 64 bytes 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.230: Got 6 bytes out of 64 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.230: [vfs7552] QUERY DATA READY completed successfully 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.230: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.230: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.230: [vfs7552] QUERY DATA READY entering state 0 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.230: Sending vfs7552_is_image_ready 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.230: [vfs7552] QUERY DATA READY entering state 1 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.230: Receiving 64 bytes 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.231: Got 6 bytes out of 64 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.231: [vfs7552] QUERY DATA READY completed successfully 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.231: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.231: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.231: [vfs7552] QUERY DATA READY entering state 0 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.231: Sending vfs7552_is_image_ready 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.231: [vfs7552] QUERY DATA READY entering state 1 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.231: Receiving 64 bytes 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.232: Got 6 bytes out of 64 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.232: [vfs7552] QUERY DATA READY completed successfully 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.232: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.232: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.232: [vfs7552] QUERY DATA READY entering state 0 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.232: Sending vfs7552_is_image_ready 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.232: [vfs7552] QUERY DATA READY entering state 1 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.232: Receiving 64 bytes 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.233: Got 6 bytes out of 64 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.233: [vfs7552] QUERY DATA READY completed successfully 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.233: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.233: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.233: [vfs7552] QUERY DATA READY entering state 0 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.233: Sending vfs7552_is_image_ready 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.233: [vfs7552] QUERY DATA READY entering state 1 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.233: Receiving 64 bytes 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.234: Got 6 bytes out of 64 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.234: [vfs7552] QUERY DATA READY completed successfully 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.234: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.234: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.234: [vfs7552] QUERY DATA READY entering state 0 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.234: Sending vfs7552_is_image_ready 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.234: [vfs7552] QUERY DATA READY entering state 1 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.234: Receiving 64 bytes 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.235: Got 6 bytes out of 64 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.235: [vfs7552] QUERY DATA READY completed successfully 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.235: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.235: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.235: [vfs7552] QUERY DATA READY entering state 0 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.235: Sending vfs7552_is_image_ready 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.235: [vfs7552] QUERY DATA READY entering state 1 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.235: Receiving 64 bytes 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.236: Got 6 bytes out of 64 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.236: [vfs7552] QUERY DATA READY completed successfully 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.236: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.236: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.236: [vfs7552] QUERY DATA READY entering state 0 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.236: Sending vfs7552_is_image_ready 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.236: [vfs7552] QUERY DATA READY entering state 1 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.236: Receiving 64 bytes 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.237: Got 6 bytes out of 64 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.237: [vfs7552] QUERY DATA READY completed successfully 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.237: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.237: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.237: [vfs7552] QUERY DATA READY entering state 0 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.237: Sending vfs7552_is_image_ready 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.237: [vfs7552] QUERY DATA READY entering state 1 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.237: Receiving 64 bytes 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.238: Got 6 bytes out of 64 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.238: [vfs7552] QUERY DATA READY completed successfully 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.238: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.238: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.238: [vfs7552] QUERY DATA READY entering state 0 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.238: Sending vfs7552_is_image_ready 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.238: [vfs7552] QUERY DATA READY entering state 1 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.238: Receiving 64 bytes 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.239: Got 6 bytes out of 64 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.239: [vfs7552] QUERY DATA READY completed successfully 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.239: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.239: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.239: [vfs7552] QUERY DATA READY entering state 0 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.239: Sending vfs7552_is_image_ready 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.239: [vfs7552] QUERY DATA READY entering state 1 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.239: Receiving 64 bytes 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.239: Got 6 bytes out of 64 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.240: [vfs7552] QUERY DATA READY completed successfully 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.240: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.240: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.240: [vfs7552] QUERY DATA READY entering state 0 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.240: Sending vfs7552_is_image_ready 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.240: [vfs7552] QUERY DATA READY entering state 1 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.240: Receiving 64 bytes 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.240: Got 6 bytes out of 64 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.240: [vfs7552] QUERY DATA READY completed successfully 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.240: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.240: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.240: [vfs7552] QUERY DATA READY entering state 0 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.240: Sending vfs7552_is_image_ready 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.241: [vfs7552] QUERY DATA READY entering state 1 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.241: Receiving 64 bytes 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.241: Got 6 bytes out of 64 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.241: [vfs7552] QUERY DATA READY completed successfully 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.241: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.241: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.241: [vfs7552] QUERY DATA READY entering state 0 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.241: Sending vfs7552_is_image_ready 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.242: [vfs7552] QUERY DATA READY entering state 1 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.242: Receiving 64 bytes 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.242: Got 6 bytes out of 64 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.242: [vfs7552] QUERY DATA READY completed successfully 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.242: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.242: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.242: [vfs7552] QUERY DATA READY entering state 0 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.242: Sending vfs7552_is_image_ready 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.243: [vfs7552] QUERY DATA READY entering state 1 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.243: Receiving 64 bytes 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.243: Got 6 bytes out of 64 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.243: [vfs7552] QUERY DATA READY completed successfully 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.243: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.243: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.243: [vfs7552] QUERY DATA READY entering state 0 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.243: Sending vfs7552_is_image_ready 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.244: [vfs7552] QUERY DATA READY entering state 1 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.244: Receiving 64 bytes 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.244: Got 6 bytes out of 64 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.244: [vfs7552] QUERY DATA READY completed successfully 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.244: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.244: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.244: [vfs7552] QUERY DATA READY entering state 0 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.244: Sending vfs7552_is_image_ready 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.245: [vfs7552] QUERY DATA READY entering state 1 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.245: Receiving 64 bytes 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.245: Got 6 bytes out of 64 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.245: [vfs7552] QUERY DATA READY completed successfully 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.245: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.245: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.245: [vfs7552] QUERY DATA READY entering state 0 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.245: Sending vfs7552_is_image_ready 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.246: [vfs7552] QUERY DATA READY entering state 1 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.246: Receiving 64 bytes 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.246: Got 6 bytes out of 64 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.246: [vfs7552] QUERY DATA READY completed successfully 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.246: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.246: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.246: [vfs7552] QUERY DATA READY entering state 0 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.247: Sending vfs7552_is_image_ready 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.247: [vfs7552] QUERY DATA READY entering state 1 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.247: Receiving 64 bytes 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.247: Got 6 bytes out of 64 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.247: [vfs7552] QUERY DATA READY completed successfully 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.247: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.247: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.247: [vfs7552] QUERY DATA READY entering state 0 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.247: Sending vfs7552_is_image_ready 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.248: [vfs7552] QUERY DATA READY entering state 1 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.248: Receiving 64 bytes 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.248: Got 6 bytes out of 64 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.248: [vfs7552] QUERY DATA READY completed successfully 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.248: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.249: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.249: [vfs7552] QUERY DATA READY entering state 0 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.249: Sending vfs7552_is_image_ready 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.249: [vfs7552] QUERY DATA READY entering state 1 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.249: Receiving 64 bytes 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.249: Got 6 bytes out of 64 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.249: [vfs7552] QUERY DATA READY completed successfully 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.249: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.249: [vfs7552] CAPTURE_NUM_STATES entering state 2 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.249: [vfs7552] REQUEST CHUNK entering state 0 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.249: Sending vfs7552_read_image_chunk 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.250: [vfs7552] REQUEST CHUNK completed successfully 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.250: [vfs7552] CAPTURE_NUM_STATES entering state 3 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.251: [vfs7552] CAPTURE_NUM_STATES entering state 2 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.251: [vfs7552] REQUEST CHUNK entering state 0 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.251: Sending vfs7552_read_image_chunk 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.251: [vfs7552] REQUEST CHUNK completed successfully 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.251: [vfs7552] CAPTURE_NUM_STATES entering state 3 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.252: [vfs7552] CAPTURE_NUM_STATES entering state 2 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.252: [vfs7552] REQUEST CHUNK entering state 0 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.252: Sending vfs7552_read_image_chunk 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.252: [vfs7552] REQUEST CHUNK completed successfully 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.252: [vfs7552] CAPTURE_NUM_STATES entering state 3 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.253: [vfs7552] CAPTURE_NUM_STATES entering state 4 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.253: Cleaning image 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.253: variance_after = 16 431s 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.253: [vfs7552] CAPTURE_NUM_STATES completed successfully 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.253: [vfs7552] DEACTIVATE_NUM_STATES entering state 0 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.263: [vfs7552] DEACTIVATE_NUM_STATES entering state 1 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.263: [vfs7552] STOP CAPTURE entering state 0 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.263: Sending vfs7552_cmd_04 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.263: [vfs7552] STOP CAPTURE entering state 1 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.263: Receiving 64 bytes 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.264: [vfs7552] STOP CAPTURE entering state 2 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.264: Sending vfs7552_cmd_52 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.264: [vfs7552] STOP CAPTURE entering state 3 431s (process:2292): libfprint-vfs7552-DEBUG: 00:54:40.264: Receiving 64 bytes 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.265: [vfs7552] STOP CAPTURE completed successfully 431s (process:2292): libfprint-SSM-DEBUG: 00:54:40.265: [vfs7552] DEACTIVATE_NUM_STATES completed successfully 431s (process:2292): libfprint-device-DEBUG: 00:54:40.265: Device reported finger status change: FP_FINGER_STATUS_NONE 431s (process:2292): libfprint-image_device-DEBUG: 00:54:40.265: Image device reported finger status: off 431s (process:2292): libfprint-image_device-DEBUG: 00:54:40.265: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 431s (process:2292): libfprint-image_device-DEBUG: 00:54:40.265: Deactivating image device 431s (process:2292): libfprint-image_device-DEBUG: 00:54:40.265: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_DEACTIVATING 431s (process:2292): libfprint-image_device-DEBUG: 00:54:40.265: Image device deactivation completed 431s (process:2292): libfprint-image_device-DEBUG: 00:54:40.265: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE 431s (process:2292): libfprint-device-DEBUG: 00:54:40.265: Device reported capture completion 431s (process:2292): libfprint-device-DEBUG: 00:54:40.265: Completing action FPI_DEVICE_ACTION_CAPTURE in idle! 431s (process:2292): libfprint-device-DEBUG: 00:54:40.265: Updated temperature model after 2.32 seconds, ratio 0.27 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 431s (process:2292): libfprint-image_device-DEBUG: 00:54:40.266: Image device close completed 431s (process:2292): libfprint-device-DEBUG: 00:54:40.266: Device reported close completion 431s (process:2292): libfprint-device-DEBUG: 00:54:40.266: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 431s (process:2292): libfprint-device-DEBUG: 00:54:40.266: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 431s ** (umockdev-run:2288): DEBUG: 00:54:40.412: umockdev.vala:154: Removing test bed /tmp/umockdev.NJ5F22 431s (umockdev-run:2288): GLib-DEBUG: 00:54:40.419: unsetenv() is not thread-safe and should not be used after threads are created 431s Comparing PNGs /tmp/libfprint-umockdev-test-9jrhz3lv/capture.png and /usr/share/installed-tests/libfprint-2/vfs7552/capture.png 431s PASS: libfprint-2/driver-vfs7552.test 431s Running test: libfprint-2/driver-aes2501.test 431s ** (umockdev-run:2301): DEBUG: 00:54:40.502: umockdev.vala:127: Created udev test bed /tmp/umockdev.0MW812 431s ** (umockdev-run:2301): DEBUG: 00:54:40.503: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0/usb1/1-10 431s ** (umockdev-run:2301): DEBUG: 00:54:40.505: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0/usb1/1-10 (subsystem usb) 431s ** (umockdev-run:2301): DEBUG: 00:54:40.511: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.0MW812/dev/bus/usb/001/044 431s ** (umockdev-run:2301): DEBUG: 00:54:40.511: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0/usb1 431s ** (umockdev-run:2301): DEBUG: 00:54:40.513: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0/usb1 (subsystem usb) 431s ** (umockdev-run:2301): DEBUG: 00:54:40.519: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.0MW812/dev/bus/usb/001/001 431s ** (umockdev-run:2301): DEBUG: 00:54:40.519: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0 431s ** (umockdev-run:2301): DEBUG: 00:54:40.519: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0 (subsystem pci) 431s (process:2305): libfprint-context-DEBUG: 00:54:40.640: Initializing FpContext (libfprint version 1.94.8+tod1) 431s (process:2305): libfprint-tod-DEBUG: 00:54:40.640: Impossible to load the shared drivers dir Error opening directory “/usr/lib/arm-linux-gnueabihf/libfprint-2/tod-1”: No such file or directory 431s (process:2305): libfprint-context-DEBUG: 00:54:40.643: No driver found for USB device 1D6B:0002 431s (process:2305): libfprint-device-DEBUG: 00:54:40.643: Device reported probe completion 431s (process:2305): libfprint-device-DEBUG: 00:54:40.643: Completing action FPI_DEVICE_ACTION_PROBE in idle! 431s (process:2305): libfprint-device-DEBUG: 00:54:40.643: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 431s (process:2305): libfprint-image_device-DEBUG: 00:54:40.645: Image device open completed 431s (process:2305): libfprint-device-DEBUG: 00:54:40.645: Device reported open completion 431s (process:2305): libfprint-device-DEBUG: 00:54:40.645: Completing action FPI_DEVICE_ACTION_OPEN in idle! 431s (process:2305): libfprint-device-DEBUG: 00:54:40.645: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 431s (process:2305): libfprint-device-DEBUG: 00:54:40.646: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 431s (process:2305): libfprint-image_device-DEBUG: 00:54:40.646: Activating image device 431s (process:2305): libfprint-image_device-DEBUG: 00:54:40.646: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING 431s (process:2305): libfprint-SSM-DEBUG: 00:54:40.646: [aes2501] ACTIVATE_NUM_STATES entering state 0 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.646: write 38 regs 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.648: all registers written 431s (process:2305): libfprint-SSM-DEBUG: 00:54:40.648: [aes2501] ACTIVATE_NUM_STATES entering state 1 431s (process:2305): libfprint-aes2501-DEBUG: 00:54:40.648: read data 1 431s (process:2305): libfprint-SSM-DEBUG: 00:54:40.648: [aes2501] ACTIVATE_NUM_STATES entering state 2 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.648: write 7 regs 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.649: all registers written 431s (process:2305): libfprint-SSM-DEBUG: 00:54:40.649: [aes2501] ACTIVATE_NUM_STATES entering state 3 431s (process:2305): libfprint-aes2501-DEBUG: 00:54:40.649: 7399848710496: ../libfprint/drivers/aes2501.c:140 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.649: write 1 regs 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.650: all registers written 431s (process:2305): libfprint-aes2501-DEBUG: 00:54:40.650: reg 0xaf = 20 431s (process:2305): libfprint-SSM-DEBUG: 00:54:40.650: [aes2501] ACTIVATE_NUM_STATES entering state 5 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.650: write 7 regs 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.651: all registers written 431s (process:2305): libfprint-SSM-DEBUG: 00:54:40.651: [aes2501] ACTIVATE_NUM_STATES entering state 6 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.651: write 16 regs 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.651: all registers written 431s (process:2305): libfprint-SSM-DEBUG: 00:54:40.651: [aes2501] ACTIVATE_NUM_STATES completed successfully 431s (process:2305): libfprint-image_device-DEBUG: 00:54:40.651: Image device activation completed 431s (process:2305): libfprint-image_device-DEBUG: 00:54:40.651: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE 431s (process:2305): libfprint-image_device-DEBUG: 00:54:40.652: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 431s (process:2305): libfprint-device-DEBUG: 00:54:40.652: Device reported finger status change: FP_FINGER_STATUS_NEEDED 431s (process:2305): libfprint-aes2501-DEBUG: 00:54:40.652: 7399848712962: ../libfprint/drivers/aes2501.c:310 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.652: write 23 regs 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.653: all registers written 431s (process:2305): libfprint-aes2501-DEBUG: 00:54:40.654: 7399848715165: ../libfprint/drivers/aes2501.c:310 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.654: write 23 regs 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.655: all registers written 431s (process:2305): libfprint-aes2501-DEBUG: 00:54:40.656: 7399848717560: ../libfprint/drivers/aes2501.c:310 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.656: write 23 regs 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.658: all registers written 431s (process:2305): libfprint-aes2501-DEBUG: 00:54:40.659: 7399848720047: ../libfprint/drivers/aes2501.c:310 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.659: write 23 regs 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.660: all registers written 431s (process:2305): libfprint-aes2501-DEBUG: 00:54:40.661: 7399848722296: ../libfprint/drivers/aes2501.c:310 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.661: write 23 regs 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.663: all registers written 431s (process:2305): libfprint-aes2501-DEBUG: 00:54:40.663: 7399848724631: ../libfprint/drivers/aes2501.c:310 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.663: write 23 regs 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.665: all registers written 431s (process:2305): libfprint-aes2501-DEBUG: 00:54:40.666: 7399848727378: ../libfprint/drivers/aes2501.c:310 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.666: write 23 regs 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.668: all registers written 431s (process:2305): libfprint-aes2501-DEBUG: 00:54:40.668: 7399848729692: ../libfprint/drivers/aes2501.c:310 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.668: write 23 regs 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.670: all registers written 431s (process:2305): libfprint-aes2501-DEBUG: 00:54:40.671: 7399848732056: ../libfprint/drivers/aes2501.c:310 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.671: write 23 regs 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.672: all registers written 431s (process:2305): libfprint-aes2501-DEBUG: 00:54:40.673: 7399848734434: ../libfprint/drivers/aes2501.c:310 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.673: write 23 regs 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.675: all registers written 431s (process:2305): libfprint-aes2501-DEBUG: 00:54:40.675: 7399848736852: ../libfprint/drivers/aes2501.c:310 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.675: write 23 regs 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.677: all registers written 431s (process:2305): libfprint-aes2501-DEBUG: 00:54:40.678: 7399848739271: ../libfprint/drivers/aes2501.c:310 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.678: write 23 regs 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.679: all registers written 431s (process:2305): libfprint-aes2501-DEBUG: 00:54:40.680: 7399848741483: ../libfprint/drivers/aes2501.c:310 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.680: write 23 regs 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.682: all registers written 431s (process:2305): libfprint-aes2501-DEBUG: 00:54:40.682: 7399848743536: ../libfprint/drivers/aes2501.c:310 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.682: write 23 regs 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.684: all registers written 431s (process:2305): libfprint-aes2501-DEBUG: 00:54:40.684: 7399848745611: ../libfprint/drivers/aes2501.c:310 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.684: write 23 regs 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.686: all registers written 431s (process:2305): libfprint-aes2501-DEBUG: 00:54:40.686: 7399848747731: ../libfprint/drivers/aes2501.c:310 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.686: write 23 regs 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.688: all registers written 431s (process:2305): libfprint-aes2501-DEBUG: 00:54:40.688: 7399848749728: ../libfprint/drivers/aes2501.c:310 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.688: write 23 regs 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.690: all registers written 431s (process:2305): libfprint-aes2501-DEBUG: 00:54:40.690: 7399848751763: ../libfprint/drivers/aes2501.c:310 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.690: write 23 regs 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.692: all registers written 431s (process:2305): libfprint-aes2501-DEBUG: 00:54:40.692: 7399848753712: ../libfprint/drivers/aes2501.c:310 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.692: write 23 regs 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.694: all registers written 431s (process:2305): libfprint-aes2501-DEBUG: 00:54:40.694: 7399848755696: ../libfprint/drivers/aes2501.c:310 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.694: write 23 regs 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.696: all registers written 431s (process:2305): libfprint-aes2501-DEBUG: 00:54:40.696: 7399848757650: ../libfprint/drivers/aes2501.c:310 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.696: write 23 regs 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.698: all registers written 431s (process:2305): libfprint-aes2501-DEBUG: 00:54:40.698: 7399848759697: ../libfprint/drivers/aes2501.c:310 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.698: write 23 regs 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.700: all registers written 431s (process:2305): libfprint-aes2501-DEBUG: 00:54:40.700: 7399848761720: ../libfprint/drivers/aes2501.c:310 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.700: write 23 regs 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.702: all registers written 431s (process:2305): libfprint-aes2501-DEBUG: 00:54:40.702: 7399848763845: ../libfprint/drivers/aes2501.c:310 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.702: write 23 regs 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.704: all registers written 431s (process:2305): libfprint-aes2501-DEBUG: 00:54:40.705: 7399848766061: ../libfprint/drivers/aes2501.c:310 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.705: write 23 regs 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.706: all registers written 431s (process:2305): libfprint-aes2501-DEBUG: 00:54:40.707: 7399848768292: ../libfprint/drivers/aes2501.c:310 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.707: write 23 regs 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.708: all registers written 431s (process:2305): libfprint-aes2501-DEBUG: 00:54:40.709: 7399848770375: ../libfprint/drivers/aes2501.c:310 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.709: write 23 regs 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.711: all registers written 431s (process:2305): libfprint-aes2501-DEBUG: 00:54:40.711: 7399848772480: ../libfprint/drivers/aes2501.c:310 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.711: write 23 regs 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.713: all registers written 431s (process:2305): libfprint-aes2501-DEBUG: 00:54:40.713: 7399848774598: ../libfprint/drivers/aes2501.c:310 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.713: write 23 regs 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.715: all registers written 431s (process:2305): libfprint-aes2501-DEBUG: 00:54:40.715: 7399848776721: ../libfprint/drivers/aes2501.c:310 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.715: write 23 regs 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.717: all registers written 431s (process:2305): libfprint-aes2501-DEBUG: 00:54:40.717: 7399848778748: ../libfprint/drivers/aes2501.c:310 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.717: write 23 regs 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.719: all registers written 431s (process:2305): libfprint-aes2501-DEBUG: 00:54:40.720: 7399848780967: ../libfprint/drivers/aes2501.c:310 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.720: write 23 regs 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.721: all registers written 431s (process:2305): libfprint-aes2501-DEBUG: 00:54:40.722: 7399848783038: ../libfprint/drivers/aes2501.c:310 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.722: write 23 regs 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.723: all registers written 431s (process:2305): libfprint-aes2501-DEBUG: 00:54:40.724: 7399848785079: ../libfprint/drivers/aes2501.c:310 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.724: write 23 regs 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.725: all registers written 431s (process:2305): libfprint-aes2501-DEBUG: 00:54:40.726: 7399848787116: ../libfprint/drivers/aes2501.c:310 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.726: write 23 regs 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.727: all registers written 431s (process:2305): libfprint-aes2501-DEBUG: 00:54:40.728: 7399848789221: ../libfprint/drivers/aes2501.c:310 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.728: write 23 regs 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.729: all registers written 431s (process:2305): libfprint-aes2501-DEBUG: 00:54:40.730: 7399848791261: ../libfprint/drivers/aes2501.c:310 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.730: write 23 regs 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.732: all registers written 431s (process:2305): libfprint-aes2501-DEBUG: 00:54:40.732: 7399848793662: ../libfprint/drivers/aes2501.c:310 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.732: write 23 regs 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.734: all registers written 431s (process:2305): libfprint-aes2501-DEBUG: 00:54:40.734: 7399848795708: ../libfprint/drivers/aes2501.c:310 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.734: write 23 regs 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.736: all registers written 431s (process:2305): libfprint-aes2501-DEBUG: 00:54:40.737: 7399848797939: ../libfprint/drivers/aes2501.c:310 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.737: write 23 regs 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.738: all registers written 431s (process:2305): libfprint-aes2501-DEBUG: 00:54:40.739: 7399848800898: ../libfprint/drivers/aes2501.c:310 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.740: write 23 regs 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.742: all registers written 431s (process:2305): libfprint-aes2501-DEBUG: 00:54:40.743: 7399848804185: ../libfprint/drivers/aes2501.c:310 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.743: write 23 regs 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.744: all registers written 431s (process:2305): libfprint-aes2501-DEBUG: 00:54:40.745: 7399848806314: ../libfprint/drivers/aes2501.c:310 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.745: write 23 regs 431s (process:2305): libfprint-device-DEBUG: 00:54:40.745: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.746: all registers written 431s (process:2305): libfprint-aes2501-DEBUG: 00:54:40.747: 7399848808396: ../libfprint/drivers/aes2501.c:310 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.747: write 23 regs 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.748: all registers written 431s (process:2305): libfprint-aes2501-DEBUG: 00:54:40.749: 7399848810224: ../libfprint/drivers/aes2501.c:310 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.749: write 23 regs 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.750: all registers written 431s (process:2305): libfprint-aes2501-DEBUG: 00:54:40.751: 7399848811933: ../libfprint/drivers/aes2501.c:310 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.751: write 23 regs 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.752: all registers written 431s (process:2305): libfprint-aes2501-DEBUG: 00:54:40.752: 7399848813794: ../libfprint/drivers/aes2501.c:310 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.752: write 23 regs 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.754: all registers written 431s (process:2305): libfprint-aes2501-DEBUG: 00:54:40.754: 7399848815668: ../libfprint/drivers/aes2501.c:310 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.754: write 23 regs 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.756: all registers written 431s (process:2305): libfprint-aes2501-DEBUG: 00:54:40.756: 7399848817468: ../libfprint/drivers/aes2501.c:310 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.756: write 23 regs 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.757: all registers written 431s (process:2305): libfprint-aes2501-DEBUG: 00:54:40.758: 7399848819278: ../libfprint/drivers/aes2501.c:310 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.758: write 23 regs 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.759: all registers written 431s (process:2305): libfprint-aes2501-DEBUG: 00:54:40.760: 7399848821034: ../libfprint/drivers/aes2501.c:310 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.760: write 23 regs 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.761: all registers written 431s (process:2305): libfprint-aes2501-DEBUG: 00:54:40.761: 7399848822884: ../libfprint/drivers/aes2501.c:310 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.761: write 23 regs 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.763: all registers written 431s (process:2305): libfprint-aes2501-DEBUG: 00:54:40.764: 7399848825009: ../libfprint/drivers/aes2501.c:310 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.764: write 23 regs 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.765: all registers written 431s (process:2305): libfprint-aes2501-DEBUG: 00:54:40.766: 7399848826935: ../libfprint/drivers/aes2501.c:310 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.766: write 23 regs 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.767: all registers written 431s (process:2305): libfprint-aes2501-DEBUG: 00:54:40.767: 7399848828741: ../libfprint/drivers/aes2501.c:310 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.767: write 23 regs 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.769: all registers written 431s (process:2305): libfprint-aes2501-DEBUG: 00:54:40.769: 7399848830554: ../libfprint/drivers/aes2501.c:310 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.769: write 23 regs 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.771: all registers written 431s (process:2305): libfprint-aes2501-DEBUG: 00:54:40.771: 7399848832404: ../libfprint/drivers/aes2501.c:310 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.771: write 23 regs 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.772: all registers written 431s (process:2305): libfprint-aes2501-DEBUG: 00:54:40.773: 7399848834228: ../libfprint/drivers/aes2501.c:310 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.773: write 23 regs 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.774: all registers written 431s (process:2305): libfprint-aes2501-DEBUG: 00:54:40.775: 7399848836067: ../libfprint/drivers/aes2501.c:310 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.775: write 23 regs 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.776: all registers written 431s (process:2305): libfprint-aes2501-DEBUG: 00:54:40.776: 7399848837894: ../libfprint/drivers/aes2501.c:310 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.776: write 23 regs 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.778: all registers written 431s (process:2305): libfprint-aes2501-DEBUG: 00:54:40.778: 7399848839781: ../libfprint/drivers/aes2501.c:310 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.778: write 23 regs 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.780: all registers written 431s (process:2305): libfprint-aes2501-DEBUG: 00:54:40.781: 7399848842076: ../libfprint/drivers/aes2501.c:310 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.781: write 23 regs 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.782: all registers written 431s (process:2305): libfprint-aes2501-DEBUG: 00:54:40.783: 7399848843932: ../libfprint/drivers/aes2501.c:310 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.783: write 23 regs 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.784: all registers written 431s (process:2305): libfprint-aes2501-DEBUG: 00:54:40.785: 7399848846052: ../libfprint/drivers/aes2501.c:310 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.785: write 23 regs 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.786: all registers written 431s (process:2305): libfprint-aes2501-DEBUG: 00:54:40.787: 7399848848024: ../libfprint/drivers/aes2501.c:310 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.787: write 23 regs 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.788: all registers written 431s (process:2305): libfprint-aes2501-DEBUG: 00:54:40.788: 7399848849866: ../libfprint/drivers/aes2501.c:310 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.788: write 23 regs 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.790: all registers written 431s (process:2305): libfprint-aes2501-DEBUG: 00:54:40.790: 7399848851675: ../libfprint/drivers/aes2501.c:310 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.790: write 23 regs 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.792: all registers written 431s (process:2305): libfprint-aes2501-DEBUG: 00:54:40.792: 7399848853474: ../libfprint/drivers/aes2501.c:310 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.792: write 23 regs 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.793: all registers written 431s (process:2305): libfprint-aes2501-DEBUG: 00:54:40.794: 7399848855313: ../libfprint/drivers/aes2501.c:310 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.794: write 23 regs 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.795: all registers written 431s (process:2305): libfprint-aes2501-DEBUG: 00:54:40.796: 7399848857304: ../libfprint/drivers/aes2501.c:310 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.796: write 23 regs 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.797: all registers written 431s (process:2305): libfprint-aes2501-DEBUG: 00:54:40.798: 7399848859079: ../libfprint/drivers/aes2501.c:310 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.798: write 23 regs 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.799: all registers written 431s (process:2305): libfprint-aes2501-DEBUG: 00:54:40.799: 7399848860906: ../libfprint/drivers/aes2501.c:310 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.799: write 23 regs 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.801: all registers written 431s (process:2305): libfprint-aes2501-DEBUG: 00:54:40.801: 7399848862711: ../libfprint/drivers/aes2501.c:310 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.801: write 23 regs 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.803: all registers written 431s (process:2305): libfprint-aes2501-DEBUG: 00:54:40.803: 7399848864475: ../libfprint/drivers/aes2501.c:310 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.803: write 23 regs 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.804: all registers written 431s (process:2305): libfprint-aes2501-DEBUG: 00:54:40.805: 7399848866349: ../libfprint/drivers/aes2501.c:310 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.805: write 23 regs 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.806: all registers written 431s (process:2305): libfprint-aes2501-DEBUG: 00:54:40.807: 7399848868212: ../libfprint/drivers/aes2501.c:310 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.807: write 23 regs 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.808: all registers written 431s (process:2305): libfprint-aes2501-DEBUG: 00:54:40.809: 7399848870089: ../libfprint/drivers/aes2501.c:310 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.809: write 23 regs 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.810: all registers written 431s (process:2305): libfprint-aes2501-DEBUG: 00:54:40.810: 7399848871881: ../libfprint/drivers/aes2501.c:310 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.810: write 23 regs 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.812: all registers written 431s (process:2305): libfprint-aes2501-DEBUG: 00:54:40.812: 7399848873741: ../libfprint/drivers/aes2501.c:310 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.812: write 23 regs 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.814: all registers written 431s (process:2305): libfprint-aes2501-DEBUG: 00:54:40.814: 7399848875742: ../libfprint/drivers/aes2501.c:310 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.814: write 23 regs 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.816: all registers written 431s (process:2305): libfprint-aes2501-DEBUG: 00:54:40.817: 7399848878223: ../libfprint/drivers/aes2501.c:310 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.817: write 23 regs 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.818: all registers written 431s (process:2305): libfprint-aes2501-DEBUG: 00:54:40.819: 7399848880062: ../libfprint/drivers/aes2501.c:310 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.819: write 23 regs 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.820: all registers written 431s (process:2305): libfprint-aes2501-DEBUG: 00:54:40.820: 7399848881912: ../libfprint/drivers/aes2501.c:310 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.821: write 23 regs 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.822: all registers written 431s (process:2305): libfprint-aes2501-DEBUG: 00:54:40.822: 7399848883753: ../libfprint/drivers/aes2501.c:310 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.822: write 23 regs 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.824: all registers written 431s (process:2305): libfprint-aes2501-DEBUG: 00:54:40.824: 7399848885573: ../libfprint/drivers/aes2501.c:310 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.824: write 23 regs 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.826: all registers written 431s (process:2305): libfprint-aes2501-DEBUG: 00:54:40.826: 7399848887400: ../libfprint/drivers/aes2501.c:310 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.826: write 23 regs 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.827: all registers written 431s (process:2305): libfprint-aes2501-DEBUG: 00:54:40.828: 7399848889266: ../libfprint/drivers/aes2501.c:310 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.828: write 23 regs 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.829: all registers written 431s (process:2305): libfprint-aes2501-DEBUG: 00:54:40.830: 7399848891263: ../libfprint/drivers/aes2501.c:310 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.830: write 23 regs 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.831: all registers written 431s (process:2305): libfprint-aes2501-DEBUG: 00:54:40.832: 7399848893139: ../libfprint/drivers/aes2501.c:310 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.832: write 23 regs 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.833: all registers written 431s (process:2305): libfprint-aes2501-DEBUG: 00:54:40.834: 7399848894923: ../libfprint/drivers/aes2501.c:310 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.834: write 23 regs 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.835: all registers written 431s (process:2305): libfprint-aes2501-DEBUG: 00:54:40.835: 7399848896748: ../libfprint/drivers/aes2501.c:310 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.835: write 23 regs 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.837: all registers written 431s (process:2305): libfprint-aes2501-DEBUG: 00:54:40.837: 7399848898518: ../libfprint/drivers/aes2501.c:310 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.837: write 23 regs 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.838: all registers written 431s (process:2305): libfprint-aes2501-DEBUG: 00:54:40.839: 7399848900334: ../libfprint/drivers/aes2501.c:310 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.839: write 23 regs 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.840: all registers written 431s (process:2305): libfprint-aes2501-DEBUG: 00:54:40.841: 7399848902130: ../libfprint/drivers/aes2501.c:310 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.841: write 23 regs 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.842: all registers written 431s (process:2305): libfprint-aes2501-DEBUG: 00:54:40.843: 7399848904028: ../libfprint/drivers/aes2501.c:310 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.843: write 23 regs 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.844: all registers written 431s (process:2305): libfprint-aes2501-DEBUG: 00:54:40.844: 7399848905860: ../libfprint/drivers/aes2501.c:310 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.844: write 23 regs 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.846: all registers written 431s (process:2305): libfprint-aes2501-DEBUG: 00:54:40.846: 7399848907743: ../libfprint/drivers/aes2501.c:310 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.846: write 23 regs 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.848: all registers written 431s (process:2305): libfprint-aes2501-DEBUG: 00:54:40.848: 7399848909486: ../libfprint/drivers/aes2501.c:310 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.848: write 23 regs 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.849: all registers written 431s (process:2305): libfprint-aes2501-DEBUG: 00:54:40.850: 7399848911375: ../libfprint/drivers/aes2501.c:310 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.850: write 23 regs 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.851: all registers written 431s (process:2305): libfprint-aes2501-DEBUG: 00:54:40.852: 7399848913188: ../libfprint/drivers/aes2501.c:310 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.852: write 23 regs 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.853: all registers written 431s (process:2305): libfprint-aes2501-DEBUG: 00:54:40.854: 7399848915059: ../libfprint/drivers/aes2501.c:310 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.854: write 23 regs 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.855: all registers written 431s (process:2305): libfprint-aes2501-DEBUG: 00:54:40.855: 7399848916895: ../libfprint/drivers/aes2501.c:310 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.855: write 23 regs 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.857: all registers written 431s (process:2305): libfprint-aes2501-DEBUG: 00:54:40.857: 7399848918740: ../libfprint/drivers/aes2501.c:310 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.857: write 23 regs 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.859: all registers written 431s (process:2305): libfprint-aes2501-DEBUG: 00:54:40.859: 7399848920500: ../libfprint/drivers/aes2501.c:310 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.859: write 23 regs 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.860: all registers written 431s (process:2305): libfprint-aes2501-DEBUG: 00:54:40.861: 7399848922357: ../libfprint/drivers/aes2501.c:310 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.861: write 23 regs 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.863: all registers written 431s (process:2305): libfprint-aes2501-DEBUG: 00:54:40.863: 7399848924530: ../libfprint/drivers/aes2501.c:310 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.863: write 23 regs 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.864: all registers written 431s (process:2305): libfprint-aes2501-DEBUG: 00:54:40.865: 7399848926368: ../libfprint/drivers/aes2501.c:310 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.865: write 23 regs 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.866: all registers written 431s (process:2305): libfprint-aes2501-DEBUG: 00:54:40.867: 7399848928243: ../libfprint/drivers/aes2501.c:310 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.867: write 23 regs 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.868: all registers written 431s (process:2305): libfprint-aes2501-DEBUG: 00:54:40.869: 7399848930110: ../libfprint/drivers/aes2501.c:310 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.869: write 23 regs 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.870: all registers written 431s (process:2305): libfprint-aes2501-DEBUG: 00:54:40.871: 7399848931934: ../libfprint/drivers/aes2501.c:310 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.871: write 23 regs 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.872: all registers written 431s (process:2305): libfprint-aes2501-DEBUG: 00:54:40.872: 7399848933757: ../libfprint/drivers/aes2501.c:310 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.872: write 23 regs 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.874: all registers written 431s (process:2305): libfprint-aes2501-DEBUG: 00:54:40.874: 7399848935584: ../libfprint/drivers/aes2501.c:310 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.874: write 23 regs 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.875: all registers written 431s (process:2305): libfprint-aes2501-DEBUG: 00:54:40.876: 7399848937385: ../libfprint/drivers/aes2501.c:310 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.876: write 23 regs 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.877: all registers written 431s (process:2305): libfprint-aes2501-DEBUG: 00:54:40.878: 7399848939256: ../libfprint/drivers/aes2501.c:310 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.878: write 23 regs 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.879: all registers written 431s (process:2305): libfprint-aes2501-DEBUG: 00:54:40.880: 7399848941105: ../libfprint/drivers/aes2501.c:310 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.880: write 23 regs 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.881: all registers written 431s (process:2305): libfprint-aes2501-DEBUG: 00:54:40.881: 7399848942907: ../libfprint/drivers/aes2501.c:310 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.881: write 23 regs 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.883: all registers written 431s (process:2305): libfprint-aes2501-DEBUG: 00:54:40.883: 7399848944757: ../libfprint/drivers/aes2501.c:310 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.883: write 23 regs 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.885: all registers written 431s (process:2305): libfprint-aes2501-DEBUG: 00:54:40.885: 7399848946531: ../libfprint/drivers/aes2501.c:310 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.885: write 23 regs 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.887: all registers written 431s (process:2305): libfprint-aes2501-DEBUG: 00:54:40.887: 7399848948481: ../libfprint/drivers/aes2501.c:310 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.887: write 23 regs 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.888: all registers written 431s (process:2305): libfprint-aes2501-DEBUG: 00:54:40.889: 7399848950315: ../libfprint/drivers/aes2501.c:310 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.889: write 23 regs 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.890: all registers written 431s (process:2305): libfprint-aes2501-DEBUG: 00:54:40.891: 7399848952168: ../libfprint/drivers/aes2501.c:310 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.891: write 23 regs 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.892: all registers written 431s (process:2305): libfprint-aes2501-DEBUG: 00:54:40.893: 7399848953930: ../libfprint/drivers/aes2501.c:310 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.893: write 23 regs 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.894: all registers written 431s (process:2305): libfprint-aes2501-DEBUG: 00:54:40.894: 7399848955777: ../libfprint/drivers/aes2501.c:310 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.894: write 23 regs 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.896: all registers written 431s (process:2305): libfprint-aes2501-DEBUG: 00:54:40.896: 7399848957730: ../libfprint/drivers/aes2501.c:310 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.896: write 23 regs 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.898: all registers written 431s (process:2305): libfprint-aes2501-DEBUG: 00:54:40.898: 7399848959908: ../libfprint/drivers/aes2501.c:310 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.899: write 23 regs 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.900: all registers written 431s (process:2305): libfprint-aes2501-DEBUG: 00:54:40.900: 7399848961769: ../libfprint/drivers/aes2501.c:310 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.900: write 23 regs 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.902: all registers written 431s (process:2305): libfprint-aes2501-DEBUG: 00:54:40.902: 7399848963555: ../libfprint/drivers/aes2501.c:310 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.902: write 23 regs 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.903: all registers written 431s (process:2305): libfprint-aes2501-DEBUG: 00:54:40.904: 7399848965341: ../libfprint/drivers/aes2501.c:310 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.904: write 23 regs 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.905: all registers written 431s (process:2305): libfprint-aes2501-DEBUG: 00:54:40.906: 7399848967316: ../libfprint/drivers/aes2501.c:310 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.906: write 23 regs 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.907: all registers written 431s (process:2305): libfprint-aes2501-DEBUG: 00:54:40.908: 7399848969167: ../libfprint/drivers/aes2501.c:310 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.908: write 23 regs 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.909: all registers written 431s (process:2305): libfprint-aes2501-DEBUG: 00:54:40.910: 7399848971322: ../libfprint/drivers/aes2501.c:310 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.910: write 23 regs 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.911: all registers written 431s (process:2305): libfprint-aes2501-DEBUG: 00:54:40.912: 7399848973394: ../libfprint/drivers/aes2501.c:310 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.912: write 23 regs 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.913: all registers written 431s (process:2305): libfprint-aes2501-DEBUG: 00:54:40.914: 7399848975449: ../libfprint/drivers/aes2501.c:310 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.914: write 23 regs 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.916: all registers written 431s (process:2305): libfprint-aes2501-DEBUG: 00:54:40.916: 7399848977659: ../libfprint/drivers/aes2501.c:310 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.916: write 23 regs 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.918: all registers written 431s (process:2305): libfprint-aes2501-DEBUG: 00:54:40.918: 7399848979611: ../libfprint/drivers/aes2501.c:310 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.918: write 23 regs 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.920: all registers written 431s (process:2305): libfprint-aes2501-DEBUG: 00:54:40.920: 7399848981656: ../libfprint/drivers/aes2501.c:310 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.920: write 23 regs 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.922: all registers written 431s (process:2305): libfprint-aes2501-DEBUG: 00:54:40.922: 7399848983548: ../libfprint/drivers/aes2501.c:310 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.922: write 23 regs 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.924: all registers written 431s (process:2305): libfprint-aes2501-DEBUG: 00:54:40.924: 7399848985485: ../libfprint/drivers/aes2501.c:310 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.924: write 23 regs 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.926: all registers written 431s (process:2305): libfprint-aes2501-DEBUG: 00:54:40.926: 7399848987508: ../libfprint/drivers/aes2501.c:310 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.926: write 23 regs 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.928: all registers written 431s (process:2305): libfprint-aes2501-DEBUG: 00:54:40.928: 7399848989526: ../libfprint/drivers/aes2501.c:310 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.928: write 23 regs 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.929: all registers written 431s (process:2305): libfprint-aes2501-DEBUG: 00:54:40.930: 7399848991314: ../libfprint/drivers/aes2501.c:310 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.930: write 23 regs 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.931: all registers written 431s (process:2305): libfprint-aes2501-DEBUG: 00:54:40.932: 7399848993202: ../libfprint/drivers/aes2501.c:310 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.932: write 23 regs 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.933: all registers written 431s (process:2305): libfprint-aes2501-DEBUG: 00:54:40.934: 7399848995064: ../libfprint/drivers/aes2501.c:310 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.934: write 23 regs 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.935: all registers written 431s (process:2305): libfprint-aes2501-DEBUG: 00:54:40.936: 7399848996926: ../libfprint/drivers/aes2501.c:310 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.936: write 23 regs 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.937: all registers written 431s (process:2305): libfprint-aes2501-DEBUG: 00:54:40.938: 7399848998997: ../libfprint/drivers/aes2501.c:310 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.938: write 23 regs 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.939: all registers written 431s (process:2305): libfprint-aes2501-DEBUG: 00:54:40.939: 7399849000873: ../libfprint/drivers/aes2501.c:310 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.939: write 23 regs 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.941: all registers written 431s (process:2305): libfprint-aes2501-DEBUG: 00:54:40.942: 7399849003207: ../libfprint/drivers/aes2501.c:310 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.942: write 23 regs 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.943: all registers written 431s (process:2305): libfprint-aes2501-DEBUG: 00:54:40.944: 7399849005059: ../libfprint/drivers/aes2501.c:310 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.944: write 23 regs 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.945: all registers written 431s (process:2305): libfprint-aes2501-DEBUG: 00:54:40.946: 7399849006930: ../libfprint/drivers/aes2501.c:310 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.946: write 23 regs 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.947: all registers written 431s (process:2305): libfprint-aes2501-DEBUG: 00:54:40.947: 7399849008824: ../libfprint/drivers/aes2501.c:310 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.947: write 23 regs 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.949: all registers written 431s (process:2305): libfprint-aes2501-DEBUG: 00:54:40.949: 7399849010799: ../libfprint/drivers/aes2501.c:310 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.949: write 23 regs 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.951: all registers written 431s (process:2305): libfprint-aes2501-DEBUG: 00:54:40.951: 7399849012714: ../libfprint/drivers/aes2501.c:310 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.951: write 23 regs 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.953: all registers written 431s (process:2305): libfprint-aes2501-DEBUG: 00:54:40.953: 7399849014546: ../libfprint/drivers/aes2501.c:310 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.953: write 23 regs 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.954: all registers written 431s (process:2305): libfprint-aes2501-DEBUG: 00:54:40.955: 7399849016388: ../libfprint/drivers/aes2501.c:310 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.955: write 23 regs 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.956: all registers written 431s (process:2305): libfprint-aes2501-DEBUG: 00:54:40.957: 7399849018279: ../libfprint/drivers/aes2501.c:310 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.957: write 23 regs 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.958: all registers written 431s (process:2305): libfprint-aes2501-DEBUG: 00:54:40.959: 7399849020211: ../libfprint/drivers/aes2501.c:310 431s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.959: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.960: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:40.961: 7399849022057: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.961: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.962: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:40.963: 7399849023988: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.963: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.964: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:40.965: 7399849025982: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.965: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.966: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:40.967: 7399849027923: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.967: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.968: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:40.968: 7399849029842: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.968: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.970: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:40.970: 7399849031711: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.970: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.972: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:40.972: 7399849033621: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.972: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.974: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:40.974: 7399849035584: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.974: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.976: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:40.976: 7399849037499: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.976: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.977: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:40.978: 7399849039342: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.978: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.979: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:40.980: 7399849041449: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.980: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.981: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:40.982: 7399849043401: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.982: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.983: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:40.984: 7399849045334: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.984: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.986: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:40.987: 7399849048203: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.987: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.988: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:40.989: 7399849050064: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.989: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.990: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:40.990: 7399849051892: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.990: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.992: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:40.992: 7399849053740: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.992: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.994: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:40.994: 7399849055536: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.994: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.996: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:40.996: 7399849057446: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.996: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.997: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:40.998: 7399849059266: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.998: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:40.999: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.000: 7399849061090: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.000: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.001: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.001: 7399849062875: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.001: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.003: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.003: 7399849064695: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.003: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.005: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.005: 7399849066535: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.005: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.006: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.007: 7399849068332: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.007: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.008: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.009: 7399849070185: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.009: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.010: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.011: 7399849071954: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.011: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.012: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.012: 7399849073817: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.012: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.014: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.014: 7399849075699: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.014: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.016: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.016: 7399849077534: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.016: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.017: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.018: 7399849079336: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.018: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.019: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.020: 7399849081204: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.020: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.021: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.022: 7399849083021: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.022: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.023: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.023: 7399849084852: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.023: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.025: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.025: 7399849086689: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.025: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.027: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.027: 7399849088524: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.027: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.028: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.029: 7399849090316: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.029: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.030: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.031: 7399849092143: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.031: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.032: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.033: 7399849093964: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.033: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.034: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.034: 7399849095793: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.034: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.036: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.036: 7399849097648: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.036: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.038: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.038: 7399849099462: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.038: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.039: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.040: 7399849101271: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.040: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.041: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.042: 7399849103159: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.042: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.043: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.044: 7399849104951: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.044: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.045: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.045: 7399849106915: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.046: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.047: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.047: 7399849108775: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.047: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.049: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.049: 7399849110615: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.049: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.051: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.051: 7399849112431: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.051: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.052: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.053: 7399849114309: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.053: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.054: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.055: 7399849116169: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.055: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.056: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.057: 7399849117953: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.057: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.058: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.058: 7399849119837: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.058: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.060: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.060: 7399849121695: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.060: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.062: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.062: 7399849123486: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.062: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.063: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.064: 7399849125343: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.064: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.065: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.066: 7399849127355: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.066: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.067: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.068: 7399849129216: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.068: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.069: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.070: 7399849131061: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.070: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.071: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.071: 7399849132887: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.071: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.073: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.073: 7399849134666: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.073: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.075: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.075: 7399849136543: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.075: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.077: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.077: 7399849138467: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.077: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.078: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.079: 7399849140287: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.079: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.080: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.081: 7399849142168: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.081: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.082: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.083: 7399849143953: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.083: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.084: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.084: 7399849145784: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.084: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.086: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.086: 7399849147604: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.086: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.087: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.088: 7399849149376: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.088: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.089: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.090: 7399849151219: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.090: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.091: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.092: 7399849153048: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.092: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.093: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.093: 7399849154887: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.093: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.095: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.095: 7399849156729: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.095: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.097: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.097: 7399849158515: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.097: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.098: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.099: 7399849160403: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.099: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.100: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.101: 7399849162221: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.101: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.102: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.103: 7399849164070: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.103: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.104: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.104: 7399849165863: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.104: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.106: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.106: 7399849167740: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.106: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.108: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.108: 7399849169548: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.108: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.110: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.110: 7399849171444: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.110: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.111: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.112: 7399849173347: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.112: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.113: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.114: 7399849175232: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.114: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.115: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.116: 7399849177224: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.116: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.117: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.118: 7399849179207: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.118: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.119: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.120: 7399849181263: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.120: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.121: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.122: 7399849183173: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.122: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.123: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.124: 7399849185141: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.124: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.125: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.126: 7399849187292: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.126: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.127: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.128: 7399849189232: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.128: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.129: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.130: 7399849191212: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.130: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.131: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.132: 7399849193225: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.132: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.133: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.134: 7399849195193: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.134: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.135: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.136: 7399849197201: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.136: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.137: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.138: 7399849199216: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.138: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.139: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.140: 7399849201192: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.140: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.141: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.142: 7399849203287: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.142: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.143: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.144: 7399849205223: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.144: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.145: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.146: 7399849207402: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.146: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.148: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.148: 7399849209445: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.148: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.150: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.150: 7399849211447: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.150: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.151: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.152: 7399849213460: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.152: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.153: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.154: 7399849215413: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.154: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.155: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.156: 7399849217387: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.156: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.158: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.158: 7399849219468: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.158: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.159: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.160: 7399849221399: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.160: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.162: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.162: 7399849223483: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.162: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.164: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.164: 7399849225487: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.164: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.165: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.166: 7399849227335: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.166: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.167: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.168: 7399849229352: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.168: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.169: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.170: 7399849231284: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.170: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.171: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.172: 7399849233190: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.172: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.173: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.174: 7399849235168: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.174: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.175: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.176: 7399849237134: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.176: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.177: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.178: 7399849239045: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.178: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.179: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.180: 7399849241039: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.180: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.181: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.182: 7399849242921: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.182: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.183: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.183: 7399849244911: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.184: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.185: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.185: 7399849246815: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.185: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.187: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.187: 7399849248674: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.187: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.189: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.189: 7399849250559: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.189: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.191: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.191: 7399849252477: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.191: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.193: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.193: 7399849254433: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.193: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.194: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.195: 7399849256364: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.195: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.196: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.197: 7399849258263: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.197: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.198: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.199: 7399849260248: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.199: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.200: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.201: 7399849262218: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.201: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.202: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.203: 7399849264174: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.203: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.204: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.205: 7399849266012: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.205: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.208: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.209: 7399849270437: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.209: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.211: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.211: 7399849272695: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.211: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.213: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.214: 7399849275384: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.214: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.216: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.216: 7399849277512: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.216: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.218: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.218: 7399849279718: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.218: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.220: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.220: 7399849281725: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.220: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.222: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.223: 7399849283968: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.223: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.224: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.224: 7399849285814: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.224: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.226: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.226: 7399849287681: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.226: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.228: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.229: 7399849290270: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.229: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.231: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.231: 7399849292690: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.231: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.233: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.233: 7399849294548: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.233: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.235: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.235: 7399849296429: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.235: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.236: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.237: 7399849298467: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.237: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.238: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.239: 7399849300340: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.239: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.240: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.241: 7399849302214: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.241: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.242: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.243: 7399849304108: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.243: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.244: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.245: 7399849305966: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.245: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.246: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.247: 7399849307926: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.247: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.248: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.248: 7399849309813: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.248: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.250: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.250: 7399849311637: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.250: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.252: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.252: 7399849313527: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.252: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.254: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.255: 7399849316132: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.255: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.256: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.257: 7399849318390: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.257: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.258: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.259: 7399849320316: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.259: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.260: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.261: 7399849322305: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.261: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.262: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.263: 7399849324267: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.263: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.264: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.265: 7399849326223: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.265: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.266: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.267: 7399849328214: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.267: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.268: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.269: 7399849330220: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.269: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.271: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.271: 7399849332477: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.271: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.272: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.273: 7399849334489: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.273: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.275: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.275: 7399849336504: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.275: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.277: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.277: 7399849338434: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.277: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.278: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.279: 7399849340392: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.279: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.280: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.281: 7399849342300: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.281: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.282: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.283: 7399849344273: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.283: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.284: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.285: 7399849346299: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.285: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.286: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.287: 7399849348278: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.287: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.288: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.289: 7399849350232: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.289: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.290: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.291: 7399849352146: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.291: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.292: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.293: 7399849354082: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.293: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.294: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.295: 7399849355978: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.295: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.296: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.297: 7399849358261: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.297: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.298: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.299: 7399849360432: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.299: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.301: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.301: 7399849362586: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.301: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.303: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.303: 7399849364846: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.303: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.305: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.306: 7399849367034: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.306: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.307: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.308: 7399849369210: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.308: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.309: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.310: 7399849371333: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.310: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.311: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.312: 7399849373484: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.312: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.314: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.314: 7399849375674: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.314: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.316: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.316: 7399849377760: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.316: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.318: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.318: 7399849379809: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.318: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.320: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.321: 7399849382057: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.321: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.322: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.323: 7399849384046: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.323: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.324: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.325: 7399849386308: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.325: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.327: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.327: 7399849388496: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.327: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.329: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.329: 7399849390583: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.329: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.331: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.331: 7399849392709: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.331: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.333: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.333: 7399849394875: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.333: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.335: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.336: 7399849397031: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.336: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.337: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.338: 7399849399249: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.338: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.339: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.340: 7399849401483: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.340: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.342: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.342: 7399849403636: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.342: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.344: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.344: 7399849405810: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.344: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.346: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.347: 7399849407951: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.347: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.348: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.349: 7399849410065: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.349: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.350: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.351: 7399849412241: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.351: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.352: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.353: 7399849414353: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.353: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.355: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.355: 7399849416490: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.355: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.357: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.357: 7399849418557: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.357: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.359: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.359: 7399849420644: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.359: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.361: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.361: 7399849422777: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.361: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.363: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.363: 7399849424892: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.363: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.365: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.366: 7399849427070: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.366: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.367: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.368: 7399849429232: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.368: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.369: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.370: 7399849431364: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.370: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.372: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.372: 7399849433483: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.372: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.374: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.374: 7399849435705: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.374: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.376: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.376: 7399849437857: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.376: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.378: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.379: 7399849440037: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.379: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.380: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.381: 7399849442140: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.381: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.382: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.383: 7399849444237: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.383: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.384: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.385: 7399849446418: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.385: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.387: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.387: 7399849448616: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.387: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.389: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.389: 7399849450773: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.389: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.391: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.391: 7399849452884: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.391: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.393: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.394: 7399849454991: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.394: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.395: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.396: 7399849457162: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.396: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.397: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.398: 7399849459300: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.398: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.399: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.400: 7399849461457: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.400: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.402: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.402: 7399849463724: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.402: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.404: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.404: 7399849465916: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.405: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.406: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.407: 7399849468091: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.407: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.408: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.409: 7399849470187: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.409: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.410: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.411: 7399849472477: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.411: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.413: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.413: 7399849474711: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.413: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.415: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.416: 7399849477015: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.416: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.417: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.418: 7399849479427: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.418: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.420: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.420: 7399849481687: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.420: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.422: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.423: 7399849483946: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.423: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.424: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.425: 7399849486166: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.425: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.426: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.427: 7399849488380: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.427: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.429: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.429: 7399849490639: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.429: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.431: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.431: 7399849492837: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.431: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.433: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.433: 7399849494799: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.433: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.435: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.435: 7399849496800: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.435: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.437: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.437: 7399849498814: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.437: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.439: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.440: 7399849500985: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.440: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.441: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.442: 7399849503018: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.442: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.443: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.444: 7399849505031: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.444: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.445: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.446: 7399849507033: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.446: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.447: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.448: 7399849509014: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.448: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.449: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.450: 7399849510997: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.450: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.451: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.452: 7399849512970: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.452: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.453: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.454: 7399849514926: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.454: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.455: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.455: 7399849516851: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.455: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.457: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.457: 7399849518799: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.457: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.459: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.459: 7399849520767: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.459: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.461: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.461: 7399849522853: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.461: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.463: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.463: 7399849524830: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.463: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.465: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.465: 7399849526771: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.465: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.467: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.467: 7399849528788: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.467: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.469: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.469: 7399849530766: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.469: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.471: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.472: 7399849533131: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.472: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.473: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.474: 7399849535151: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.474: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.475: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.476: 7399849537089: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.476: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.477: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.478: 7399849539087: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.478: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.479: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.480: 7399849541035: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.480: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.481: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.482: 7399849543033: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.482: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.483: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.484: 7399849544932: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.484: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.485: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.486: 7399849547182: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.486: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.487: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.488: 7399849549160: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.488: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.489: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.490: 7399849551092: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.490: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.491: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.492: 7399849553037: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.492: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.493: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.494: 7399849555038: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.494: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.495: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.496: 7399849556961: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.496: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.497: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.497: 7399849558857: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.497: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.499: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.499: 7399849560835: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.499: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.501: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.501: 7399849562778: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.501: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.503: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.503: 7399849564829: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.503: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.505: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.505: 7399849566830: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.505: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.507: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.508: 7399849569295: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.508: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.509: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.510: 7399849571228: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.510: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.511: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.512: 7399849573126: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.512: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.513: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.514: 7399849575047: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.514: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.515: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.516: 7399849577273: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.516: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.517: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.518: 7399849579264: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.518: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.519: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.520: 7399849581223: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.520: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.521: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.522: 7399849583175: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.522: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.524: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.524: 7399849585884: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.524: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.526: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.527: 7399849587922: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.527: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.528: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.528: 7399849589810: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.528: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.530: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.530: 7399849591792: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.530: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.532: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.532: 7399849593789: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.532: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.534: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.534: 7399849595760: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.534: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.536: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.536: 7399849597716: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.536: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.538: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.538: 7399849599685: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.538: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.540: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.540: 7399849601583: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.540: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.542: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.542: 7399849603621: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.542: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.544: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.544: 7399849605540: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.544: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.546: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.546: 7399849607491: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.546: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.548: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.548: 7399849609450: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.548: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.550: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.551: 7399849612164: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.551: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.552: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.553: 7399849614235: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.553: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.554: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.555: 7399849616323: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.555: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.557: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.557: 7399849618635: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.557: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.559: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.559: 7399849620694: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.559: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.561: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.561: 7399849622622: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.561: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.563: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.563: 7399849624615: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.563: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.565: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.565: 7399849626616: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.565: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.567: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.567: 7399849628607: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.567: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.569: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.569: 7399849630672: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.569: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.571: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.571: 7399849632601: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.571: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.573: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.573: 7399849634491: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.573: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.574: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.575: 7399849636409: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.575: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.576: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.577: 7399849638408: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.577: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.578: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.579: 7399849640412: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.579: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.580: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.581: 7399849642373: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.581: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.582: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.583: 7399849644283: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.583: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.584: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.585: 7399849646212: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.585: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.586: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.587: 7399849648119: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.587: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.588: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.589: 7399849649966: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.589: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.590: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.590: 7399849651882: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.590: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.592: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.592: 7399849653792: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.592: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.594: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.594: 7399849655766: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.594: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.596: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.596: 7399849657689: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.596: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.598: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.598: 7399849659704: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.598: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.600: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.600: 7399849661688: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.600: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.602: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.602: 7399849663704: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.602: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.604: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.604: 7399849665605: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.604: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.606: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.606: 7399849667623: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.606: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.608: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.608: 7399849669520: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.608: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.610: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.610: 7399849671523: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.610: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.612: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.612: 7399849673769: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.612: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.614: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.614: 7399849675702: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.614: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.616: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.616: 7399849677671: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.616: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.618: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.618: 7399849679782: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.618: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.620: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.620: 7399849681727: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.620: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.622: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.622: 7399849683671: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.622: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.624: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.625: 7399849686026: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.625: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.626: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.627: 7399849687975: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.627: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.628: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.629: 7399849690029: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.629: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.630: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.630: 7399849691916: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.631: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.632: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.633: 7399849693921: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.633: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.634: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.634: 7399849695851: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.634: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.636: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.636: 7399849697831: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.636: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.638: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.638: 7399849699789: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.638: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.640: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.640: 7399849701693: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.640: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.642: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.642: 7399849703672: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.642: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.644: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.644: 7399849705546: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.644: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.646: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.646: 7399849707513: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.646: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.648: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.648: 7399849709437: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.648: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.649: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.650: 7399849711408: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.650: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.651: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.652: 7399849713336: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.652: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.653: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.654: 7399849715296: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.654: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.655: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.656: 7399849717232: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.656: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.657: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.658: 7399849719229: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.658: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.659: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.660: 7399849721229: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.660: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.661: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.662: 7399849723181: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.662: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.663: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.664: 7399849725162: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.664: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.665: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.666: 7399849727123: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.666: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.667: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.668: 7399849728980: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.668: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.669: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.669: 7399849730877: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.669: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.671: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.671: 7399849732813: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.671: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.673: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.673: 7399849734793: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.673: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.675: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.675: 7399849736783: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.675: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.677: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.677: 7399849738754: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.677: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.679: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.679: 7399849740610: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.679: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.681: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.681: 7399849742554: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.681: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.683: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.683: 7399849744479: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.683: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.685: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.685: 7399849746523: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.685: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.687: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.687: 7399849748493: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.687: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.689: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.689: 7399849750496: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.689: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.691: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.691: 7399849752611: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.691: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.693: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.693: 7399849754533: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.693: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.695: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.695: 7399849756513: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.695: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.696: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.697: 7399849758408: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.697: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.698: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.699: 7399849760455: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.699: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.700: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.701: 7399849762411: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.701: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.704: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.704: 7399849765529: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.704: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.706: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.707: 7399849767933: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.707: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.708: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.709: 7399849770331: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.709: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.710: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.711: 7399849772350: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.711: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.712: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.713: 7399849774318: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.713: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.715: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.715: 7399849776754: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.715: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.717: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.717: 7399849778673: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.717: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.719: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.719: 7399849780608: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.719: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.721: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.721: 7399849782634: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.721: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.723: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.723: 7399849784638: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.723: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.725: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.725: 7399849786569: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.725: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.727: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.727: 7399849788480: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.727: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.728: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.729: 7399849790436: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.729: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.730: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.731: 7399849792444: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.731: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.732: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.733: 7399849794401: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.733: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.734: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.735: 7399849796335: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.735: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.736: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.737: 7399849798317: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.737: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.738: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.739: 7399849800396: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.739: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.741: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.741: 7399849802475: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.741: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.743: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.743: 7399849804468: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.743: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.744: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.745: 7399849806425: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.745: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.746: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.747: 7399849808384: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.747: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.748: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.749: 7399849810343: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.749: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.750: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.751: 7399849812368: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.751: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.752: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.753: 7399849814483: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.753: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.754: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.755: 7399849816369: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.755: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.756: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.757: 7399849818320: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.757: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.759: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.760: 7399849820984: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.760: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.761: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.762: 7399849823096: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.762: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.763: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.764: 7399849824996: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.764: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.765: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.765: 7399849826913: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.766: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.767: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.767: 7399849828809: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.767: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.769: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.769: 7399849830793: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.769: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.771: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.772: 7399849833282: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.772: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.773: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.774: 7399849835325: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.774: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.775: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.776: 7399849837403: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.776: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.777: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.778: 7399849839410: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.778: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.779: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.780: 7399849841436: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.780: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.781: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.782: 7399849843351: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.782: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.783: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.784: 7399849845321: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.784: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.785: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.786: 7399849847294: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.786: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.787: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.788: 7399849849207: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.788: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.789: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.790: 7399849851163: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.790: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.791: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.792: 7399849853029: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.792: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.793: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.794: 7399849854972: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.794: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.795: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.795: 7399849856887: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.795: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.797: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.797: 7399849858875: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.797: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.799: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.799: 7399849860738: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.799: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.801: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.801: 7399849862651: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.801: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.803: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.803: 7399849864557: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.803: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.805: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.805: 7399849866508: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.805: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.807: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.807: 7399849868488: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.807: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.808: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.809: 7399849870488: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.809: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.810: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.811: 7399849872422: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.811: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.812: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.813: 7399849874337: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.813: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.814: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.815: 7399849876339: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.815: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.816: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.817: 7399849878227: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.817: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.818: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.819: 7399849880150: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.819: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.820: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.821: 7399849882060: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.821: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.822: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.823: 7399849884047: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.823: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.824: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.824: 7399849885912: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.825: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.826: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.826: 7399849887900: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.827: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.828: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.828: 7399849889827: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.828: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.830: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.830: 7399849891746: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.830: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.832: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.832: 7399849893727: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.832: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.834: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.834: 7399849895645: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.834: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.836: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.836: 7399849897570: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.836: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.838: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.838: 7399849899552: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.838: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.840: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.840: 7399849901469: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.840: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.841: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.842: 7399849903419: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.842: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.844: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.844: 7399849905538: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.844: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.846: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.846: 7399849907445: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.846: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.847: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.848: 7399849909344: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.848: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.849: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.850: 7399849911321: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.850: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.851: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.852: 7399849913219: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.852: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.853: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.854: 7399849915202: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.854: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.855: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.856: 7399849917183: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.856: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.857: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.858: 7399849919090: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.858: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.859: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.860: 7399849920961: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.860: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.861: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.862: 7399849922926: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.862: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.863: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.864: 7399849925757: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.864: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.867: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.868: 7399849929360: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.868: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.873: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.874: 7399849934949: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.874: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.876: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.876: 7399849937783: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.876: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.878: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.879: 7399849940385: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.879: write 23 regs 432s Executing: libfprint-2/driver-aes2501.test 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.881: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.881: 7399849942900: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.882: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.884: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.887: 7399849948035: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.887: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.889: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.890: 7399849951675: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.890: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.892: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.893: 7399849954183: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.893: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.897: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.897: 7399849958786: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.897: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.900: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.900: 7399849961765: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.900: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.902: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.903: 7399849964223: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.903: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.904: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.905: 7399849966387: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.905: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.907: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.908: 7399849969109: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.908: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.909: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.910: 7399849971200: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.910: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.911: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.912: 7399849973196: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.912: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.913: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.914: 7399849975322: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.914: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.916: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.916: 7399849977515: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.916: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.918: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.918: 7399849979522: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.918: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.920: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.920: 7399849981543: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.920: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.922: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.922: 7399849983503: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.922: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.924: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.924: 7399849985612: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.924: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.926: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.927: 7399849988276: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.927: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.928: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.929: 7399849990327: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.929: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.930: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.931: 7399849992298: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.931: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.932: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.933: 7399849994432: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.933: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.935: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.935: 7399849996549: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.935: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.937: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.937: 7399849998542: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.937: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.939: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.939: 7399850000605: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.939: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.941: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.941: 7399850002515: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.941: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.943: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.943: 7399850004675: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.943: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.945: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.945: 7399850006646: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.945: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.947: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.947: 7399850008797: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.947: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.949: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.949: 7399850010917: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.950: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.951: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.952: 7399850013382: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.952: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.954: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.954: 7399850015474: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.954: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.956: all registers written 432s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.956: 7399850017598: ../libfprint/drivers/aes2501.c:310 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.956: write 23 regs 432s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.958: all registers written 433s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.958: 7399850019649: ../libfprint/drivers/aes2501.c:310 433s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.958: write 23 regs 433s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.960: all registers written 433s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.960: 7399850021707: ../libfprint/drivers/aes2501.c:310 433s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.960: write 23 regs 433s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.962: all registers written 433s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.962: 7399850023735: ../libfprint/drivers/aes2501.c:310 433s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.962: write 23 regs 433s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.964: all registers written 433s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.964: 7399850025882: ../libfprint/drivers/aes2501.c:310 433s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.964: write 23 regs 433s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.966: all registers written 433s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.967: 7399850028111: ../libfprint/drivers/aes2501.c:310 433s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.967: write 23 regs 433s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.968: all registers written 433s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.969: 7399850030216: ../libfprint/drivers/aes2501.c:310 433s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.969: write 23 regs 433s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.970: all registers written 433s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.971: 7399850032318: ../libfprint/drivers/aes2501.c:310 433s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.971: write 23 regs 433s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.973: all registers written 433s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.973: 7399850034593: ../libfprint/drivers/aes2501.c:310 433s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.973: write 23 regs 433s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.975: all registers written 433s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.975: 7399850036661: ../libfprint/drivers/aes2501.c:310 433s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.975: write 23 regs 433s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.977: all registers written 433s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.977: 7399850038784: ../libfprint/drivers/aes2501.c:310 433s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.977: write 23 regs 433s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.979: all registers written 433s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.980: 7399850041227: ../libfprint/drivers/aes2501.c:310 433s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.980: write 23 regs 433s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.981: all registers written 433s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.982: 7399850043395: ../libfprint/drivers/aes2501.c:310 433s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.982: write 23 regs 433s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.984: all registers written 433s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.984: 7399850045636: ../libfprint/drivers/aes2501.c:310 433s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.984: write 23 regs 433s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.986: all registers written 433s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.987: 7399850047965: ../libfprint/drivers/aes2501.c:310 433s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.987: write 23 regs 433s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.988: all registers written 433s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.989: 7399850050217: ../libfprint/drivers/aes2501.c:310 433s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.989: write 23 regs 433s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.991: all registers written 433s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.991: 7399850052572: ../libfprint/drivers/aes2501.c:310 433s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.991: write 23 regs 433s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.993: all registers written 433s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.994: 7399850054917: ../libfprint/drivers/aes2501.c:310 433s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.994: write 23 regs 433s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.995: all registers written 433s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.996: 7399850057055: ../libfprint/drivers/aes2501.c:310 433s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.996: write 23 regs 433s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.997: all registers written 433s (process:2305): libfprint-aes2501-DEBUG: 00:54:41.998: 7399850059508: ../libfprint/drivers/aes2501.c:310 433s (process:2305): libfprint-aeslib-DEBUG: 00:54:41.998: write 23 regs 433s (process:2305): libfprint-aeslib-DEBUG: 00:54:42.000: all registers written 433s (process:2305): libfprint-aes2501-DEBUG: 00:54:42.000: 7399850061607: ../libfprint/drivers/aes2501.c:310 433s (process:2305): libfprint-aeslib-DEBUG: 00:54:42.000: write 23 regs 433s (process:2305): libfprint-aeslib-DEBUG: 00:54:42.002: all registers written 433s (process:2305): libfprint-aes2501-DEBUG: 00:54:42.003: 7399850063944: ../libfprint/drivers/aes2501.c:310 433s (process:2305): libfprint-aeslib-DEBUG: 00:54:42.003: write 23 regs 433s (process:2305): libfprint-aeslib-DEBUG: 00:54:42.004: all registers written 433s (process:2305): libfprint-aes2501-DEBUG: 00:54:42.005: 7399850066088: ../libfprint/drivers/aes2501.c:310 433s (process:2305): libfprint-aeslib-DEBUG: 00:54:42.005: write 23 regs 433s (process:2305): libfprint-aeslib-DEBUG: 00:54:42.006: all registers written 433s (process:2305): libfprint-aes2501-DEBUG: 00:54:42.007: 7399850068290: ../libfprint/drivers/aes2501.c:310 433s (process:2305): libfprint-aeslib-DEBUG: 00:54:42.007: write 23 regs 433s (process:2305): libfprint-aeslib-DEBUG: 00:54:42.009: all registers written 433s (process:2305): libfprint-aes2501-DEBUG: 00:54:42.009: 7399850070622: ../libfprint/drivers/aes2501.c:310 433s (process:2305): libfprint-aeslib-DEBUG: 00:54:42.009: write 23 regs 433s (process:2305): libfprint-aeslib-DEBUG: 00:54:42.011: all registers written 433s (process:2305): libfprint-aes2501-DEBUG: 00:54:42.011: 7399850072868: ../libfprint/drivers/aes2501.c:310 433s (process:2305): libfprint-aeslib-DEBUG: 00:54:42.011: write 23 regs 433s (process:2305): libfprint-aeslib-DEBUG: 00:54:42.013: all registers written 433s (process:2305): libfprint-aes2501-DEBUG: 00:54:42.014: 7399850075116: ../libfprint/drivers/aes2501.c:310 433s (process:2305): libfprint-aeslib-DEBUG: 00:54:42.014: write 23 regs 433s (process:2305): libfprint-aeslib-DEBUG: 00:54:42.015: all registers written 433s (process:2305): libfprint-aes2501-DEBUG: 00:54:42.016: 7399850077271: ../libfprint/drivers/aes2501.c:310 433s (process:2305): libfprint-aeslib-DEBUG: 00:54:42.016: write 23 regs 433s (process:2305): libfprint-aeslib-DEBUG: 00:54:42.017: all registers written 433s (process:2305): libfprint-aes2501-DEBUG: 00:54:42.018: 7399850079502: ../libfprint/drivers/aes2501.c:310 433s (process:2305): libfprint-aeslib-DEBUG: 00:54:42.018: write 23 regs 433s (process:2305): libfprint-aeslib-DEBUG: 00:54:42.020: all registers written 433s (process:2305): libfprint-aes2501-DEBUG: 00:54:42.020: 7399850081597: ../libfprint/drivers/aes2501.c:310 433s (process:2305): libfprint-aeslib-DEBUG: 00:54:42.020: write 23 regs 433s (process:2305): libfprint-aeslib-DEBUG: 00:54:42.022: all registers written 433s (process:2305): libfprint-aes2501-DEBUG: 00:54:42.022: 7399850083776: ../libfprint/drivers/aes2501.c:310 433s (process:2305): libfprint-aeslib-DEBUG: 00:54:42.022: write 23 regs 433s (process:2305): libfprint-aeslib-DEBUG: 00:54:42.024: all registers written 433s (process:2305): libfprint-aes2501-DEBUG: 00:54:42.024: 7399850085888: ../libfprint/drivers/aes2501.c:310 433s (process:2305): libfprint-aeslib-DEBUG: 00:54:42.024: write 23 regs 433s (process:2305): libfprint-aeslib-DEBUG: 00:54:42.026: all registers written 433s (process:2305): libfprint-aes2501-DEBUG: 00:54:42.027: 7399850087993: ../libfprint/drivers/aes2501.c:310 433s (process:2305): libfprint-aeslib-DEBUG: 00:54:42.027: write 23 regs 433s (process:2305): libfprint-aeslib-DEBUG: 00:54:42.028: all registers written 433s (process:2305): libfprint-aes2501-DEBUG: 00:54:42.029: 7399850090301: ../libfprint/drivers/aes2501.c:310 433s (process:2305): libfprint-aeslib-DEBUG: 00:54:42.029: write 23 regs 433s (process:2305): libfprint-aeslib-DEBUG: 00:54:42.030: all registers written 433s (process:2305): libfprint-aes2501-DEBUG: 00:54:42.031: 7399850092349: ../libfprint/drivers/aes2501.c:310 433s (process:2305): libfprint-aeslib-DEBUG: 00:54:42.031: write 23 regs 433s (process:2305): libfprint-aeslib-DEBUG: 00:54:42.033: all registers written 433s (process:2305): libfprint-aes2501-DEBUG: 00:54:42.033: 7399850094562: ../libfprint/drivers/aes2501.c:310 433s (process:2305): libfprint-aeslib-DEBUG: 00:54:42.033: write 23 regs 433s (process:2305): libfprint-aeslib-DEBUG: 00:54:42.035: all registers written 433s (process:2305): libfprint-aes2501-DEBUG: 00:54:42.035: 7399850096705: ../libfprint/drivers/aes2501.c:310 433s (process:2305): libfprint-aeslib-DEBUG: 00:54:42.035: write 23 regs 433s (process:2305): libfprint-aeslib-DEBUG: 00:54:42.037: all registers written 433s (process:2305): libfprint-aes2501-DEBUG: 00:54:42.038: 7399850098991: ../libfprint/drivers/aes2501.c:310 433s (process:2305): libfprint-aeslib-DEBUG: 00:54:42.038: write 23 regs 433s (process:2305): libfprint-aeslib-DEBUG: 00:54:42.039: all registers written 433s (process:2305): libfprint-aes2501-DEBUG: 00:54:42.040: 7399850101136: ../libfprint/drivers/aes2501.c:310 433s (process:2305): libfprint-aeslib-DEBUG: 00:54:42.040: write 23 regs 433s (process:2305): libfprint-aeslib-DEBUG: 00:54:42.041: all registers written 433s (process:2305): libfprint-aes2501-DEBUG: 00:54:42.042: 7399850103386: ../libfprint/drivers/aes2501.c:310 433s (process:2305): libfprint-aeslib-DEBUG: 00:54:42.042: write 23 regs 433s (process:2305): libfprint-aeslib-DEBUG: 00:54:42.044: all registers written 433s (process:2305): libfprint-aes2501-DEBUG: 00:54:42.044: 7399850105542: ../libfprint/drivers/aes2501.c:310 433s (process:2305): libfprint-aeslib-DEBUG: 00:54:42.044: write 23 regs 433s (process:2305): libfprint-aeslib-DEBUG: 00:54:42.046: all registers written 433s (process:2305): libfprint-aes2501-DEBUG: 00:54:42.046: 7399850107807: ../libfprint/drivers/aes2501.c:310 433s (process:2305): libfprint-aeslib-DEBUG: 00:54:42.046: write 23 regs 433s (process:2305): libfprint-aeslib-DEBUG: 00:54:42.048: all registers written 433s (process:2305): libfprint-aes2501-DEBUG: 00:54:42.049: 7399850109962: ../libfprint/drivers/aes2501.c:310 433s (process:2305): libfprint-aeslib-DEBUG: 00:54:42.049: write 23 regs 433s (process:2305): libfprint-aeslib-DEBUG: 00:54:42.050: all registers written 433s (process:2305): libfprint-aes2501-DEBUG: 00:54:42.051: 7399850112050: ../libfprint/drivers/aes2501.c:310 433s (process:2305): libfprint-aeslib-DEBUG: 00:54:42.051: write 23 regs 433s (process:2305): libfprint-aeslib-DEBUG: 00:54:42.052: all registers written 433s (process:2305): libfprint-aes2501-DEBUG: 00:54:42.053: 7399850114316: ../libfprint/drivers/aes2501.c:310 433s (process:2305): libfprint-aeslib-DEBUG: 00:54:42.053: write 23 regs 433s (process:2305): libfprint-aeslib-DEBUG: 00:54:42.054: all registers written 433s (process:2305): libfprint-aes2501-DEBUG: 00:54:42.055: 7399850116393: ../libfprint/drivers/aes2501.c:310 433s (process:2305): libfprint-aeslib-DEBUG: 00:54:42.055: write 23 regs 433s (process:2305): libfprint-aeslib-DEBUG: 00:54:42.057: all registers written 433s (process:2305): libfprint-aes2501-DEBUG: 00:54:42.057: 7399850118496: ../libfprint/drivers/aes2501.c:310 433s (process:2305): libfprint-aeslib-DEBUG: 00:54:42.057: write 23 regs 433s (process:2305): libfprint-aeslib-DEBUG: 00:54:42.059: all registers written 433s (process:2305): libfprint-aes2501-DEBUG: 00:54:42.059: 7399850120857: ../libfprint/drivers/aes2501.c:310 433s (process:2305): libfprint-aeslib-DEBUG: 00:54:42.059: write 23 regs 433s (process:2305): libfprint-aeslib-DEBUG: 00:54:42.061: all registers written 433s (process:2305): libfprint-aes2501-DEBUG: 00:54:42.062: 7399850122985: ../libfprint/drivers/aes2501.c:310 433s (process:2305): libfprint-aeslib-DEBUG: 00:54:42.062: write 23 regs 433s (process:2305): libfprint-aeslib-DEBUG: 00:54:42.063: all registers written 433s (process:2305): libfprint-aes2501-DEBUG: 00:54:42.064: 7399850125289: ../libfprint/drivers/aes2501.c:310 433s (process:2305): libfprint-aeslib-DEBUG: 00:54:42.064: write 23 regs 433s (process:2305): libfprint-aeslib-DEBUG: 00:54:42.065: all registers written 433s (process:2305): libfprint-aes2501-DEBUG: 00:54:42.066: 7399850127419: ../libfprint/drivers/aes2501.c:310 433s (process:2305): libfprint-aeslib-DEBUG: 00:54:42.066: write 23 regs 433s (process:2305): libfprint-aeslib-DEBUG: 00:54:42.068: all registers written 433s (process:2305): libfprint-aes2501-DEBUG: 00:54:42.068: 7399850129607: ../libfprint/drivers/aes2501.c:310 433s (process:2305): libfprint-aeslib-DEBUG: 00:54:42.068: write 23 regs 433s (process:2305): libfprint-aeslib-DEBUG: 00:54:42.070: all registers written 433s (process:2305): libfprint-aes2501-DEBUG: 00:54:42.070: 7399850131797: ../libfprint/drivers/aes2501.c:310 433s (process:2305): libfprint-aeslib-DEBUG: 00:54:42.070: write 23 regs 433s (process:2305): libfprint-aeslib-DEBUG: 00:54:42.072: all registers written 433s (process:2305): libfprint-aes2501-DEBUG: 00:54:42.073: 7399850133990: ../libfprint/drivers/aes2501.c:310 433s (process:2305): libfprint-aeslib-DEBUG: 00:54:42.073: write 23 regs 433s (process:2305): libfprint-aeslib-DEBUG: 00:54:42.074: all registers written 433s (process:2305): libfprint-aes2501-DEBUG: 00:54:42.075: 7399850136218: ../libfprint/drivers/aes2501.c:310 433s (process:2305): libfprint-aeslib-DEBUG: 00:54:42.075: write 23 regs 433s (process:2305): libfprint-aeslib-DEBUG: 00:54:42.076: all registers written 433s (process:2305): libfprint-aes2501-DEBUG: 00:54:42.077: 7399850138295: ../libfprint/drivers/aes2501.c:310 433s (process:2305): libfprint-aeslib-DEBUG: 00:54:42.077: write 23 regs 433s (process:2305): libfprint-aeslib-DEBUG: 00:54:42.079: all registers written 433s (process:2305): libfprint-aes2501-DEBUG: 00:54:42.079: 7399850140611: ../libfprint/drivers/aes2501.c:310 433s (process:2305): libfprint-aeslib-DEBUG: 00:54:42.079: write 23 regs 433s (process:2305): libfprint-aeslib-DEBUG: 00:54:42.081: all registers written 433s (process:2305): libfprint-aes2501-DEBUG: 00:54:42.081: 7399850142621: ../libfprint/drivers/aes2501.c:310 433s (process:2305): libfprint-aeslib-DEBUG: 00:54:42.081: write 23 regs 433s (process:2305): libfprint-aeslib-DEBUG: 00:54:42.083: all registers written 433s (process:2305): libfprint-aes2501-DEBUG: 00:54:42.083: 7399850144620: ../libfprint/drivers/aes2501.c:310 433s (process:2305): libfprint-aeslib-DEBUG: 00:54:42.083: write 23 regs 433s (process:2305): libfprint-aeslib-DEBUG: 00:54:42.085: all registers written 433s (process:2305): libfprint-aes2501-DEBUG: 00:54:42.085: 7399850146661: ../libfprint/drivers/aes2501.c:310 433s (process:2305): libfprint-aeslib-DEBUG: 00:54:42.085: write 23 regs 433s (process:2305): libfprint-aeslib-DEBUG: 00:54:42.087: all registers written 433s (process:2305): libfprint-aes2501-DEBUG: 00:54:42.087: 7399850148688: ../libfprint/drivers/aes2501.c:310 433s (process:2305): libfprint-aeslib-DEBUG: 00:54:42.087: write 23 regs 433s (process:2305): libfprint-aeslib-DEBUG: 00:54:42.089: all registers written 433s (process:2305): libfprint-aes2501-DEBUG: 00:54:42.089: 7399850150744: ../libfprint/drivers/aes2501.c:310 433s (process:2305): libfprint-aeslib-DEBUG: 00:54:42.089: write 23 regs 433s (process:2305): libfprint-aeslib-DEBUG: 00:54:42.091: all registers written 433s (process:2305): libfprint-aes2501-DEBUG: 00:54:42.091: 7399850152808: ../libfprint/drivers/aes2501.c:310 433s (process:2305): libfprint-aeslib-DEBUG: 00:54:42.091: write 23 regs 433s (process:2305): libfprint-aeslib-DEBUG: 00:54:42.093: all registers written 433s (process:2305): libfprint-aes2501-DEBUG: 00:54:42.093: 7399850154912: ../libfprint/drivers/aes2501.c:310 433s (process:2305): libfprint-aeslib-DEBUG: 00:54:42.094: write 23 regs 433s (process:2305): libfprint-aeslib-DEBUG: 00:54:42.095: all registers written 433s (process:2305): libfprint-device-DEBUG: 00:54:42.096: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 433s (process:2305): libfprint-image_device-DEBUG: 00:54:42.096: Image device reported finger status: on 433s (process:2305): libfprint-image_device-DEBUG: 00:54:42.096: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 433s (process:2305): libfprint-aes2501-DEBUG: 00:54:42.096: 7399850157321: ../libfprint/drivers/aes2501.c:581 433s (process:2305): libfprint-SSM-DEBUG: 00:54:42.096: [aes2501] CAPTURE_NUM_STATES entering state 0 433s (process:2305): libfprint-aeslib-DEBUG: 00:54:42.096: write 26 regs 433s (process:2305): libfprint-aeslib-DEBUG: 00:54:42.098: all registers written 433s (process:2305): libfprint-SSM-DEBUG: 00:54:42.098: [aes2501] CAPTURE_NUM_STATES entering state 1 433s (process:2305): libfprint-SSM-DEBUG: 00:54:42.098: [aes2501] CAPTURE_NUM_STATES entering state 2 433s (process:2305): libfprint-aeslib-DEBUG: 00:54:42.098: write 7 regs 433s (process:2305): libfprint-aeslib-DEBUG: 00:54:42.099: all registers written 433s (process:2305): libfprint-SSM-DEBUG: 00:54:42.099: [aes2501] CAPTURE_NUM_STATES entering state 3 433s (process:2305): libfprint-SSM-DEBUG: 00:54:42.100: [aes2501] CAPTURE_NUM_STATES entering state 4 433s (process:2305): libfprint-aeslib-DEBUG: 00:54:42.100: write 7 regs 433s (process:2305): libfprint-aeslib-DEBUG: 00:54:42.100: all registers written 433s (process:2305): libfprint-SSM-DEBUG: 00:54:42.100: [aes2501] CAPTURE_NUM_STATES entering state 5 433s (process:2305): libfprint-aes2501-DEBUG: 00:54:42.101: sum=5 433s (process:2305): libfprint-aes2501-DEBUG: 00:54:42.101: ADREFHI is 50 433s (process:2305): libfprint-SSM-DEBUG: 00:54:42.101: [aes2501] CAPTURE_NUM_STATES entering state 4 433s (process:2305): libfprint-aeslib-DEBUG: 00:54:42.101: write 7 regs 433s (process:2305): libfprint-aeslib-DEBUG: 00:54:42.101: all registers written 433s (process:2305): libfprint-SSM-DEBUG: 00:54:42.101: [aes2501] CAPTURE_NUM_STATES entering state 5 433s (process:2305): libfprint-aes2501-DEBUG: 00:54:42.102: sum=8 433s (process:2305): libfprint-aes2501-DEBUG: 00:54:42.102: ADREFHI is 48 433s (process:2305): libfprint-SSM-DEBUG: 00:54:42.102: [aes2501] CAPTURE_NUM_STATES entering state 4 433s (process:2305): libfprint-aeslib-DEBUG: 00:54:42.102: write 7 regs 433s (process:2305): libfprint-aeslib-DEBUG: 00:54:42.102: all registers written 433s (process:2305): libfprint-SSM-DEBUG: 00:54:42.102: [aes2501] CAPTURE_NUM_STATES entering state 5 433s (process:2305): libfprint-aes2501-DEBUG: 00:54:42.103: sum=19 433s (process:2305): libfprint-aes2501-DEBUG: 00:54:42.103: ADREFHI is 40 433s (process:2305): libfprint-SSM-DEBUG: 00:54:42.103: [aes2501] CAPTURE_NUM_STATES entering state 4 433s (process:2305): libfprint-aeslib-DEBUG: 00:54:42.103: write 7 regs 433s (process:2305): libfprint-aeslib-DEBUG: 00:54:42.103: all registers written 433s (process:2305): libfprint-SSM-DEBUG: 00:54:42.103: [aes2501] CAPTURE_NUM_STATES entering state 5 433s (process:2305): libfprint-aes2501-DEBUG: 00:54:42.104: sum=60 433s (process:2305): libfprint-aes2501-DEBUG: 00:54:42.104: ADREFHI is 38 433s (process:2305): libfprint-SSM-DEBUG: 00:54:42.104: [aes2501] CAPTURE_NUM_STATES entering state 4 433s (process:2305): libfprint-aeslib-DEBUG: 00:54:42.104: write 7 regs 433s (process:2305): libfprint-aeslib-DEBUG: 00:54:42.105: all registers written 433s (process:2305): libfprint-SSM-DEBUG: 00:54:42.105: [aes2501] CAPTURE_NUM_STATES entering state 5 433s (process:2305): libfprint-aes2501-DEBUG: 00:54:42.105: sum=123 433s (process:2305): libfprint-aes2501-DEBUG: 00:54:42.105: ADREFHI is 30 433s (process:2305): libfprint-SSM-DEBUG: 00:54:42.105: [aes2501] CAPTURE_NUM_STATES entering state 4 433s (process:2305): libfprint-aeslib-DEBUG: 00:54:42.105: write 7 regs 433s (process:2305): libfprint-aeslib-DEBUG: 00:54:42.106: all registers written 433s (process:2305): libfprint-SSM-DEBUG: 00:54:42.106: [aes2501] CAPTURE_NUM_STATES entering state 5 433s (process:2305): libfprint-aes2501-DEBUG: 00:54:42.106: sum=226 433s (process:2305): libfprint-aes2501-DEBUG: 00:54:42.106: ADREFHI is 28 433s (process:2305): libfprint-SSM-DEBUG: 00:54:42.106: [aes2501] CAPTURE_NUM_STATES entering state 4 433s (process:2305): libfprint-aeslib-DEBUG: 00:54:42.106: write 7 regs 433s (process:2305): libfprint-aeslib-DEBUG: 00:54:42.107: all registers written 433s (process:2305): libfprint-SSM-DEBUG: 00:54:42.107: [aes2501] CAPTURE_NUM_STATES entering state 5 433s (process:2305): libfprint-aes2501-DEBUG: 00:54:42.108: sum=461 433s (process:2305): libfprint-aes2501-DEBUG: 00:54:42.108: ADREFHI is 28 433s (process:2305): libfprint-SSM-DEBUG: 00:54:42.108: [aes2501] CAPTURE_NUM_STATES entering state 4 433s (process:2305): libfprint-aeslib-DEBUG: 00:54:42.108: write 7 regs 433s (process:2305): libfprint-aeslib-DEBUG: 00:54:42.108: all registers written 433s (process:2305): libfprint-SSM-DEBUG: 00:54:42.108: [aes2501] CAPTURE_NUM_STATES entering state 5 433s (process:2305): libfprint-aes2501-DEBUG: 00:54:42.109: sum=466 433s (process:2305): libfprint-aes2501-DEBUG: 00:54:42.109: ADREFHI is 28 433s (process:2305): libfprint-SSM-DEBUG: 00:54:42.109: [aes2501] CAPTURE_NUM_STATES entering state 4 433s (process:2305): libfprint-aeslib-DEBUG: 00:54:42.109: write 7 regs 433s (process:2305): libfprint-aeslib-DEBUG: 00:54:42.109: all registers written 433s (process:2305): libfprint-SSM-DEBUG: 00:54:42.109: [aes2501] CAPTURE_NUM_STATES entering state 5 433s (process:2305): libfprint-aes2501-DEBUG: 00:54:42.110: sum=465 433s (process:2305): libfprint-aes2501-DEBUG: 00:54:42.110: ADREFHI is 28 433s (process:2305): libfprint-SSM-DEBUG: 00:54:42.110: [aes2501] CAPTURE_NUM_STATES entering state 4 433s (process:2305): libfprint-aeslib-DEBUG: 00:54:42.110: write 7 regs 433s (process:2305): libfprint-aeslib-DEBUG: 00:54:42.110: all registers written 433s (process:2305): libfprint-SSM-DEBUG: 00:54:42.110: [aes2501] CAPTURE_NUM_STATES entering state 5 433s (process:2305): libfprint-aes2501-DEBUG: 00:54:42.111: sum=620 433s (process:2305): libfprint-aes2501-DEBUG: 00:54:42.111: ADREFHI is 28 433s (process:2305): libfprint-SSM-DEBUG: 00:54:42.111: [aes2501] CAPTURE_NUM_STATES entering state 4 433s (process:2305): libfprint-aeslib-DEBUG: 00:54:42.111: write 7 regs 433s (process:2305): libfprint-aeslib-DEBUG: 00:54:42.111: all registers written 433s (process:2305): libfprint-SSM-DEBUG: 00:54:42.112: [aes2501] CAPTURE_NUM_STATES entering state 5 433s (process:2305): libfprint-aes2501-DEBUG: 00:54:42.112: sum=629 433s (process:2305): libfprint-aes2501-DEBUG: 00:54:42.112: ADREFHI is 28 433s (process:2305): libfprint-SSM-DEBUG: 00:54:42.112: [aes2501] CAPTURE_NUM_STATES entering state 4 433s (process:2305): libfprint-aeslib-DEBUG: 00:54:42.112: write 7 regs 433s (process:2305): libfprint-aeslib-DEBUG: 00:54:42.113: all registers written 433s (process:2305): libfprint-SSM-DEBUG: 00:54:42.113: [aes2501] CAPTURE_NUM_STATES entering state 5 433s (process:2305): libfprint-aes2501-DEBUG: 00:54:42.113: sum=615 433s (process:2305): libfprint-aes2501-DEBUG: 00:54:42.113: ADREFHI is 28 433s (process:2305): libfprint-SSM-DEBUG: 00:54:42.113: [aes2501] CAPTURE_NUM_STATES entering state 4 433s (process:2305): libfprint-aeslib-DEBUG: 00:54:42.113: write 7 regs 433s (process:2305): libfprint-aeslib-DEBUG: 00:54:42.114: all registers written 433s (process:2305): libfprint-SSM-DEBUG: 00:54:42.114: [aes2501] CAPTURE_NUM_STATES entering state 5 433s (process:2305): libfprint-aes2501-DEBUG: 00:54:42.114: sum=585 433s (process:2305): libfprint-aes2501-DEBUG: 00:54:42.114: ADREFHI is 28 433s (process:2305): libfprint-SSM-DEBUG: 00:54:42.114: [aes2501] CAPTURE_NUM_STATES entering state 4 433s (process:2305): libfprint-aeslib-DEBUG: 00:54:42.114: write 7 regs 433s (process:2305): libfprint-aeslib-DEBUG: 00:54:42.115: all registers written 433s (process:2305): libfprint-SSM-DEBUG: 00:54:42.115: [aes2501] CAPTURE_NUM_STATES entering state 5 433s (process:2305): libfprint-aes2501-DEBUG: 00:54:42.116: sum=581 433s (process:2305): libfprint-aes2501-DEBUG: 00:54:42.116: ADREFHI is 28 433s (process:2305): libfprint-SSM-DEBUG: 00:54:42.116: [aes2501] CAPTURE_NUM_STATES entering state 4 433s (process:2305): libfprint-aeslib-DEBUG: 00:54:42.116: write 7 regs 433s (process:2305): libfprint-aeslib-DEBUG: 00:54:42.117: all registers written 433s (process:2305): libfprint-SSM-DEBUG: 00:54:42.117: [aes2501] CAPTURE_NUM_STATES entering state 5 433s (process:2305): libfprint-aes2501-DEBUG: 00:54:42.117: sum=418 433s (process:2305): libfprint-aes2501-DEBUG: 00:54:42.117: ADREFHI is 28 433s (process:2305): libfprint-SSM-DEBUG: 00:54:42.117: [aes2501] CAPTURE_NUM_STATES entering state 4 433s (process:2305): libfprint-aeslib-DEBUG: 00:54:42.117: write 7 regs 433s (process:2305): libfprint-aeslib-DEBUG: 00:54:42.118: all registers written 433s (process:2305): libfprint-SSM-DEBUG: 00:54:42.118: [aes2501] CAPTURE_NUM_STATES entering state 5 433s (process:2305): libfprint-aes2501-DEBUG: 00:54:42.119: sum=406 433s (process:2305): libfprint-aes2501-DEBUG: 00:54:42.119: ADREFHI is 28 433s (process:2305): libfprint-SSM-DEBUG: 00:54:42.119: [aes2501] CAPTURE_NUM_STATES entering state 4 433s (process:2305): libfprint-aeslib-DEBUG: 00:54:42.119: write 7 regs 433s (process:2305): libfprint-aeslib-DEBUG: 00:54:42.119: all registers written 433s (process:2305): libfprint-SSM-DEBUG: 00:54:42.119: [aes2501] CAPTURE_NUM_STATES entering state 5 433s (process:2305): libfprint-aes2501-DEBUG: 00:54:42.120: sum=389 433s (process:2305): libfprint-aes2501-DEBUG: 00:54:42.120: ADREFHI is 28 433s (process:2305): libfprint-SSM-DEBUG: 00:54:42.120: [aes2501] CAPTURE_NUM_STATES entering state 4 433s (process:2305): libfprint-aeslib-DEBUG: 00:54:42.120: write 7 regs 433s (process:2305): libfprint-aeslib-DEBUG: 00:54:42.121: all registers written 433s (process:2305): libfprint-SSM-DEBUG: 00:54:42.121: [aes2501] CAPTURE_NUM_STATES entering state 5 433s (process:2305): libfprint-aes2501-DEBUG: 00:54:42.121: sum=388 433s (process:2305): libfprint-aes2501-DEBUG: 00:54:42.122: ADREFHI is 28 433s (process:2305): libfprint-SSM-DEBUG: 00:54:42.122: [aes2501] CAPTURE_NUM_STATES entering state 4 433s (process:2305): libfprint-aeslib-DEBUG: 00:54:42.122: write 7 regs 433s (process:2305): libfprint-aeslib-DEBUG: 00:54:42.122: all registers written 433s (process:2305): libfprint-SSM-DEBUG: 00:54:42.122: [aes2501] CAPTURE_NUM_STATES entering state 5 433s (process:2305): libfprint-aes2501-DEBUG: 00:54:42.123: sum=393 433s (process:2305): libfprint-aes2501-DEBUG: 00:54:42.123: ADREFHI is 28 433s (process:2305): libfprint-SSM-DEBUG: 00:54:42.123: [aes2501] CAPTURE_NUM_STATES entering state 4 433s (process:2305): libfprint-aeslib-DEBUG: 00:54:42.123: write 7 regs 433s (process:2305): libfprint-aeslib-DEBUG: 00:54:42.124: all registers written 433s (process:2305): libfprint-SSM-DEBUG: 00:54:42.124: [aes2501] CAPTURE_NUM_STATES entering state 5 433s (process:2305): libfprint-aes2501-DEBUG: 00:54:42.124: sum=389 433s (process:2305): libfprint-aes2501-DEBUG: 00:54:42.124: ADREFHI is 28 433s (process:2305): libfprint-SSM-DEBUG: 00:54:42.124: [aes2501] CAPTURE_NUM_STATES entering state 4 433s (process:2305): libfprint-aeslib-DEBUG: 00:54:42.124: write 7 regs 433s (process:2305): libfprint-aeslib-DEBUG: 00:54:42.125: all registers written 433s (process:2305): libfprint-SSM-DEBUG: 00:54:42.125: [aes2501] CAPTURE_NUM_STATES entering state 5 433s (process:2305): libfprint-aes2501-DEBUG: 00:54:42.126: sum=379 433s (process:2305): libfprint-aes2501-DEBUG: 00:54:42.126: ADREFHI is 28 433s (process:2305): libfprint-SSM-DEBUG: 00:54:42.126: [aes2501] CAPTURE_NUM_STATES entering state 4 433s (process:2305): libfprint-aeslib-DEBUG: 00:54:42.126: write 7 regs 433s (process:2305): libfprint-aeslib-DEBUG: 00:54:42.126: all registers written 433s (process:2305): libfprint-SSM-DEBUG: 00:54:42.127: [aes2501] CAPTURE_NUM_STATES entering state 5 433s (process:2305): libfprint-aes2501-DEBUG: 00:54:42.127: sum=361 433s (process:2305): libfprint-aes2501-DEBUG: 00:54:42.127: ADREFHI is 28 433s (process:2305): libfprint-SSM-DEBUG: 00:54:42.127: [aes2501] CAPTURE_NUM_STATES entering state 4 433s (process:2305): libfprint-aeslib-DEBUG: 00:54:42.127: write 7 regs 433s (process:2305): libfprint-aeslib-DEBUG: 00:54:42.128: all registers written 433s (process:2305): libfprint-SSM-DEBUG: 00:54:42.128: [aes2501] CAPTURE_NUM_STATES entering state 5 433s (process:2305): libfprint-aes2501-DEBUG: 00:54:42.129: sum=356 433s (process:2305): libfprint-aes2501-DEBUG: 00:54:42.129: ADREFHI is 28 433s (process:2305): libfprint-SSM-DEBUG: 00:54:42.129: [aes2501] CAPTURE_NUM_STATES entering state 4 433s (process:2305): libfprint-aeslib-DEBUG: 00:54:42.129: write 7 regs 433s (process:2305): libfprint-aeslib-DEBUG: 00:54:42.129: all registers written 433s (process:2305): libfprint-SSM-DEBUG: 00:54:42.129: [aes2501] CAPTURE_NUM_STATES entering state 5 433s (process:2305): libfprint-aes2501-DEBUG: 00:54:42.130: sum=193 433s (process:2305): libfprint-aes2501-DEBUG: 00:54:42.130: ADREFHI is 28 433s (process:2305): libfprint-SSM-DEBUG: 00:54:42.130: [aes2501] CAPTURE_NUM_STATES entering state 4 433s (process:2305): libfprint-aeslib-DEBUG: 00:54:42.130: write 7 regs 433s (process:2305): libfprint-aeslib-DEBUG: 00:54:42.131: all registers written 433s (process:2305): libfprint-SSM-DEBUG: 00:54:42.131: [aes2501] CAPTURE_NUM_STATES entering state 5 433s (process:2305): libfprint-aes2501-DEBUG: 00:54:42.131: sum=178 433s (process:2305): libfprint-aes2501-DEBUG: 00:54:42.131: ADREFHI is 28 433s (process:2305): libfprint-SSM-DEBUG: 00:54:42.131: [aes2501] CAPTURE_NUM_STATES entering state 4 433s (process:2305): libfprint-aeslib-DEBUG: 00:54:42.131: write 7 regs 433s (process:2305): libfprint-aeslib-DEBUG: 00:54:42.132: all registers written 433s (process:2305): libfprint-SSM-DEBUG: 00:54:42.132: [aes2501] CAPTURE_NUM_STATES entering state 5 433s (process:2305): libfprint-aes2501-DEBUG: 00:54:42.133: sum=164 433s (process:2305): libfprint-aes2501-DEBUG: 00:54:42.133: ADREFHI is 28 433s (process:2305): libfprint-SSM-DEBUG: 00:54:42.133: [aes2501] CAPTURE_NUM_STATES entering state 4 433s (process:2305): libfprint-aeslib-DEBUG: 00:54:42.133: write 7 regs 433s (process:2305): libfprint-aeslib-DEBUG: 00:54:42.133: all registers written 433s (process:2305): libfprint-SSM-DEBUG: 00:54:42.133: [aes2501] CAPTURE_NUM_STATES entering state 5 433s (process:2305): libfprint-aes2501-DEBUG: 00:54:42.134: sum=157 433s (process:2305): libfprint-aes2501-DEBUG: 00:54:42.134: ADREFHI is 28 433s (process:2305): libfprint-SSM-DEBUG: 00:54:42.134: [aes2501] CAPTURE_NUM_STATES entering state 4 433s (process:2305): libfprint-aeslib-DEBUG: 00:54:42.134: write 7 regs 433s (process:2305): libfprint-aeslib-DEBUG: 00:54:42.135: all registers written 433s (process:2305): libfprint-SSM-DEBUG: 00:54:42.135: [aes2501] CAPTURE_NUM_STATES entering state 5 433s (process:2305): libfprint-aes2501-DEBUG: 00:54:42.135: sum=152 433s (process:2305): libfprint-aes2501-DEBUG: 00:54:42.135: ADREFHI is 28 433s (process:2305): libfprint-SSM-DEBUG: 00:54:42.135: [aes2501] CAPTURE_NUM_STATES entering state 4 433s (process:2305): libfprint-aeslib-DEBUG: 00:54:42.135: write 7 regs 433s (process:2305): libfprint-aeslib-DEBUG: 00:54:42.136: all registers written 433s (process:2305): libfprint-SSM-DEBUG: 00:54:42.136: [aes2501] CAPTURE_NUM_STATES entering state 5 433s (process:2305): libfprint-aes2501-DEBUG: 00:54:42.137: sum=154 433s (process:2305): libfprint-aes2501-DEBUG: 00:54:42.137: ADREFHI is 28 433s (process:2305): libfprint-SSM-DEBUG: 00:54:42.137: [aes2501] CAPTURE_NUM_STATES entering state 4 433s (process:2305): libfprint-aeslib-DEBUG: 00:54:42.137: write 7 regs 433s (process:2305): libfprint-aeslib-DEBUG: 00:54:42.137: all registers written 433s (process:2305): libfprint-SSM-DEBUG: 00:54:42.137: [aes2501] CAPTURE_NUM_STATES entering state 5 433s (process:2305): libfprint-aes2501-DEBUG: 00:54:42.138: sum=157 433s (process:2305): libfprint-aes2501-DEBUG: 00:54:42.138: ADREFHI is 28 433s (process:2305): libfprint-SSM-DEBUG: 00:54:42.138: [aes2501] CAPTURE_NUM_STATES entering state 4 433s (process:2305): libfprint-aeslib-DEBUG: 00:54:42.138: write 7 regs 433s (process:2305): libfprint-aeslib-DEBUG: 00:54:42.139: all registers written 433s (process:2305): libfprint-SSM-DEBUG: 00:54:42.139: [aes2501] CAPTURE_NUM_STATES entering state 5 433s (process:2305): libfprint-aes2501-DEBUG: 00:54:42.139: sum=161 433s (process:2305): libfprint-aes2501-DEBUG: 00:54:42.139: ADREFHI is 28 433s (process:2305): libfprint-SSM-DEBUG: 00:54:42.139: [aes2501] CAPTURE_NUM_STATES entering state 4 433s (process:2305): libfprint-aeslib-DEBUG: 00:54:42.139: write 7 regs 433s (process:2305): libfprint-aeslib-DEBUG: 00:54:42.140: all registers written 433s (process:2305): libfprint-SSM-DEBUG: 00:54:42.140: [aes2501] CAPTURE_NUM_STATES entering state 5 433s (process:2305): libfprint-aes2501-DEBUG: 00:54:42.141: sum=161 433s (process:2305): libfprint-aes2501-DEBUG: 00:54:42.141: ADREFHI is 28 433s (process:2305): libfprint-SSM-DEBUG: 00:54:42.141: [aes2501] CAPTURE_NUM_STATES entering state 4 433s (process:2305): libfprint-aeslib-DEBUG: 00:54:42.141: write 7 regs 433s (process:2305): libfprint-aeslib-DEBUG: 00:54:42.141: all registers written 433s (process:2305): libfprint-SSM-DEBUG: 00:54:42.141: [aes2501] CAPTURE_NUM_STATES entering state 5 433s (process:2305): libfprint-aes2501-DEBUG: 00:54:42.142: sum=161 433s (process:2305): libfprint-aes2501-DEBUG: 00:54:42.142: ADREFHI is 28 433s (process:2305): libfprint-SSM-DEBUG: 00:54:42.142: [aes2501] CAPTURE_NUM_STATES entering state 4 433s (process:2305): libfprint-aeslib-DEBUG: 00:54:42.142: write 7 regs 433s (process:2305): libfprint-aeslib-DEBUG: 00:54:42.143: all registers written 433s (process:2305): libfprint-SSM-DEBUG: 00:54:42.143: [aes2501] CAPTURE_NUM_STATES entering state 5 433s (process:2305): libfprint-aes2501-DEBUG: 00:54:42.143: sum=162 433s (process:2305): libfprint-aes2501-DEBUG: 00:54:42.143: ADREFHI is 28 433s (process:2305): libfprint-SSM-DEBUG: 00:54:42.143: [aes2501] CAPTURE_NUM_STATES entering state 4 433s (process:2305): libfprint-aeslib-DEBUG: 00:54:42.143: write 7 regs 433s (process:2305): libfprint-aeslib-DEBUG: 00:54:42.144: all registers written 433s (process:2305): libfprint-SSM-DEBUG: 00:54:42.144: [aes2501] CAPTURE_NUM_STATES entering state 5 433s (process:2305): libfprint-aes2501-DEBUG: 00:54:42.145: sum=166 433s (process:2305): libfprint-aes2501-DEBUG: 00:54:42.145: ADREFHI is 28 433s (process:2305): libfprint-SSM-DEBUG: 00:54:42.145: [aes2501] CAPTURE_NUM_STATES entering state 4 433s (process:2305): libfprint-aeslib-DEBUG: 00:54:42.145: write 7 regs 433s (process:2305): libfprint-aeslib-DEBUG: 00:54:42.145: all registers written 433s (process:2305): libfprint-SSM-DEBUG: 00:54:42.145: [aes2501] CAPTURE_NUM_STATES entering state 5 433s (process:2305): libfprint-aes2501-DEBUG: 00:54:42.146: sum=143 433s (process:2305): libfprint-aes2501-DEBUG: 00:54:42.146: ADREFHI is 28 433s (process:2305): libfprint-SSM-DEBUG: 00:54:42.146: [aes2501] CAPTURE_NUM_STATES entering state 4 433s (process:2305): libfprint-aeslib-DEBUG: 00:54:42.146: write 7 regs 433s (process:2305): libfprint-aeslib-DEBUG: 00:54:42.147: all registers written 433s (process:2305): libfprint-SSM-DEBUG: 00:54:42.147: [aes2501] CAPTURE_NUM_STATES entering state 5 433s (process:2305): libfprint-aes2501-DEBUG: 00:54:42.147: sum=106 433s (process:2305): libfprint-aes2501-DEBUG: 00:54:42.148: ADREFHI is 28 433s (process:2305): libfprint-SSM-DEBUG: 00:54:42.148: [aes2501] CAPTURE_NUM_STATES entering state 4 433s (process:2305): libfprint-aeslib-DEBUG: 00:54:42.148: write 7 regs 433s (process:2305): libfprint-aeslib-DEBUG: 00:54:42.148: all registers written 433s (process:2305): libfprint-SSM-DEBUG: 00:54:42.148: [aes2501] CAPTURE_NUM_STATES entering state 5 433s (process:2305): libfprint-aes2501-DEBUG: 00:54:42.149: sum=74 433s (process:2305): libfprint-aes2501-DEBUG: 00:54:42.149: ADREFHI is 28 433s (process:2305): libfprint-SSM-DEBUG: 00:54:42.149: [aes2501] CAPTURE_NUM_STATES entering state 4 433s (process:2305): libfprint-aeslib-DEBUG: 00:54:42.149: write 7 regs 433s (process:2305): libfprint-aeslib-DEBUG: 00:54:42.149: all registers written 433s (process:2305): libfprint-SSM-DEBUG: 00:54:42.149: [aes2501] CAPTURE_NUM_STATES entering state 5 433s (process:2305): libfprint-aes2501-DEBUG: 00:54:42.150: sum=51 433s (process:2305): libfprint-aes2501-DEBUG: 00:54:42.150: ADREFHI is 28 433s (process:2305): libfprint-SSM-DEBUG: 00:54:42.150: [aes2501] CAPTURE_NUM_STATES entering state 4 433s (process:2305): libfprint-aeslib-DEBUG: 00:54:42.151: write 7 regs 433s (process:2305): libfprint-aeslib-DEBUG: 00:54:42.151: all registers written 433s (process:2305): libfprint-SSM-DEBUG: 00:54:42.151: [aes2501] CAPTURE_NUM_STATES entering state 5 433s (process:2305): libfprint-aes2501-DEBUG: 00:54:42.152: sum=40 433s (process:2305): libfprint-aes2501-DEBUG: 00:54:42.152: ADREFHI is 28 433s (process:2305): libfprint-SSM-DEBUG: 00:54:42.152: [aes2501] CAPTURE_NUM_STATES entering state 4 433s (process:2305): libfprint-aeslib-DEBUG: 00:54:42.152: write 7 regs 433s (process:2305): libfprint-aeslib-DEBUG: 00:54:42.153: all registers written 433s (process:2305): libfprint-SSM-DEBUG: 00:54:42.153: [aes2501] CAPTURE_NUM_STATES entering state 5 433s (process:2305): libfprint-aes2501-DEBUG: 00:54:42.154: sum=39 433s (process:2305): libfprint-aes2501-DEBUG: 00:54:42.154: ADREFHI is 28 433s (process:2305): libfprint-SSM-DEBUG: 00:54:42.154: [aes2501] CAPTURE_NUM_STATES entering state 4 433s (process:2305): libfprint-aeslib-DEBUG: 00:54:42.154: write 7 regs 433s (process:2305): libfprint-aeslib-DEBUG: 00:54:42.154: all registers written 433s (process:2305): libfprint-SSM-DEBUG: 00:54:42.154: [aes2501] CAPTURE_NUM_STATES entering state 5 433s (process:2305): libfprint-aes2501-DEBUG: 00:54:42.155: sum=19 433s (process:2305): libfprint-aes2501-DEBUG: 00:54:42.155: ADREFHI is 28 433s (process:2305): libfprint-SSM-DEBUG: 00:54:42.155: [aes2501] CAPTURE_NUM_STATES entering state 4 433s (process:2305): libfprint-aeslib-DEBUG: 00:54:42.155: write 7 regs 433s (process:2305): libfprint-aeslib-DEBUG: 00:54:42.156: all registers written 433s (process:2305): libfprint-SSM-DEBUG: 00:54:42.156: [aes2501] CAPTURE_NUM_STATES entering state 5 433s (process:2305): libfprint-aes2501-DEBUG: 00:54:42.157: sum=13 433s (process:2305): libfprint-aes2501-DEBUG: 00:54:42.157: ADREFHI is 28 433s (process:2305): libfprint-SSM-DEBUG: 00:54:42.157: [aes2501] CAPTURE_NUM_STATES entering state 4 433s (process:2305): libfprint-aeslib-DEBUG: 00:54:42.157: write 7 regs 433s (process:2305): libfprint-aeslib-DEBUG: 00:54:42.157: all registers written 433s (process:2305): libfprint-SSM-DEBUG: 00:54:42.157: [aes2501] CAPTURE_NUM_STATES entering state 5 433s (process:2305): libfprint-aes2501-DEBUG: 00:54:42.158: sum=5 433s (process:2305): libfprint-aes2501-DEBUG: 00:54:42.158: ADREFHI is 28 433s (process:2305): libfprint-SSM-DEBUG: 00:54:42.158: [aes2501] CAPTURE_NUM_STATES entering state 4 433s (process:2305): libfprint-aeslib-DEBUG: 00:54:42.158: write 7 regs 433s (process:2305): libfprint-aeslib-DEBUG: 00:54:42.159: all registers written 433s (process:2305): libfprint-SSM-DEBUG: 00:54:42.159: [aes2501] CAPTURE_NUM_STATES entering state 5 433s (process:2305): libfprint-aes2501-DEBUG: 00:54:42.160: sum=2 433s (process:2305): libfprint-aes2501-DEBUG: 00:54:42.160: ADREFHI is 28 433s (process:2305): libfprint-SSM-DEBUG: 00:54:42.160: [aes2501] CAPTURE_NUM_STATES entering state 4 433s (process:2305): libfprint-aeslib-DEBUG: 00:54:42.160: write 7 regs 433s (process:2305): libfprint-aeslib-DEBUG: 00:54:42.160: all registers written 433s (process:2305): libfprint-SSM-DEBUG: 00:54:42.160: [aes2501] CAPTURE_NUM_STATES entering state 5 433s (process:2305): libfprint-aes2501-DEBUG: 00:54:42.161: sum=0 433s (process:2305): libfprint-aes2501-DEBUG: 00:54:42.161: ADREFHI is 28 433s (process:2305): libfprint-SSM-DEBUG: 00:54:42.161: [aes2501] CAPTURE_NUM_STATES entering state 4 433s (process:2305): libfprint-aeslib-DEBUG: 00:54:42.161: write 7 regs 433s (process:2305): libfprint-aeslib-DEBUG: 00:54:42.162: all registers written 433s (process:2305): libfprint-SSM-DEBUG: 00:54:42.162: [aes2501] CAPTURE_NUM_STATES entering state 5 433s (process:2305): libfprint-aes2501-DEBUG: 00:54:42.162: sum=0 433s (process:2305): libfprint-aes2501-DEBUG: 00:54:42.163: ADREFHI is 28 433s (process:2305): libfprint-SSM-DEBUG: 00:54:42.163: [aes2501] CAPTURE_NUM_STATES entering state 4 433s (process:2305): libfprint-aeslib-DEBUG: 00:54:42.163: write 7 regs 433s (process:2305): libfprint-aeslib-DEBUG: 00:54:42.163: all registers written 433s (process:2305): libfprint-SSM-DEBUG: 00:54:42.163: [aes2501] CAPTURE_NUM_STATES entering state 5 433s (process:2305): libfprint-aes2501-DEBUG: 00:54:42.164: sum=0 433s (process:2305): libfprint-aes2501-DEBUG: 00:54:42.164: ADREFHI is 28 433s (process:2305): libfprint-assembling-DEBUG: 00:54:42.271: calc delta completed in 0.106434 secs 433s (process:2305): libfprint-assembling-DEBUG: 00:54:42.376: calc delta completed in 0.105365 secs 433s (process:2305): libfprint-assembling-DEBUG: 00:54:42.376: errors: 53228 rev: 72653 433s (process:2305): libfprint-assembling-DEBUG: 00:54:42.481: calc delta completed in 0.104907 secs 433s (process:2305): libfprint-assembling-DEBUG: 00:54:42.481: height is 102 433s (process:2305): libfprint-image_device-DEBUG: 00:54:42.482: Image device captured an image 433s (process:2305): libfprint-image_device-DEBUG: 00:54:42.484: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 433s (process:2305): libfprint-device-DEBUG: 00:54:42.485: Device reported finger status change: FP_FINGER_STATUS_PRESENT 433s (process:2305): libfprint-device-DEBUG: 00:54:42.485: Device reported finger status change: FP_FINGER_STATUS_NONE 433s (process:2305): libfprint-image_device-DEBUG: 00:54:42.485: Image device reported finger status: off 433s (process:2305): libfprint-image_device-DEBUG: 00:54:42.485: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 433s (process:2305): libfprint-image_device-DEBUG: 00:54:42.485: Deactivating image device 433s (process:2305): libfprint-image_device-DEBUG: 00:54:42.485: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_DEACTIVATING 433s (process:2305): libfprint-SSM-DEBUG: 00:54:42.485: [aes2501] CAPTURE_NUM_STATES completed successfully 433s (process:2305): libfprint-aes2501-DEBUG: 00:54:42.485: 7399850546056: ../libfprint/drivers/aes2501.c:547 433s (process:2305): libfprint-aes2501-DEBUG: 00:54:42.485: 7399850546065: ../libfprint/drivers/aes2501.c:820 433s (process:2305): libfprint-image_device-DEBUG: 00:54:42.485: Image device deactivation completed 433s (process:2305): libfprint-image_device-DEBUG: 00:54:42.485: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE 433s (process:2305): libfprint-image-DEBUG: 00:54:42.490: Minutiae scan completed in 0.005217 secs 433s (process:2305): libfprint-device-DEBUG: 00:54:42.490: Device reported capture completion 433s (process:2305): libfprint-device-DEBUG: 00:54:42.490: Completing action FPI_DEVICE_ACTION_CAPTURE in idle! 433s (process:2305): libfprint-device-DEBUG: 00:54:42.490: Updated temperature model after 1.74 seconds, ratio 0.27 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 433s (process:2305): libfprint-image_device-DEBUG: 00:54:42.491: Image device close completed 433s (process:2305): libfprint-device-DEBUG: 00:54:42.491: Device reported close completion 433s (process:2305): libfprint-device-DEBUG: 00:54:42.491: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 433s (process:2305): libfprint-device-DEBUG: 00:54:42.491: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 433s ** (umockdev-run:2301): DEBUG: 00:54:42.616: umockdev.vala:154: Removing test bed /tmp/umockdev.0MW812 433s (umockdev-run:2301): GLib-DEBUG: 00:54:42.626: unsetenv() is not thread-safe and should not be used after threads are created 433s Comparing PNGs /tmp/libfprint-umockdev-test-fclhivkd/capture.png and /usr/share/installed-tests/libfprint-2/aes2501/capture.png 433s PASS: libfprint-2/driver-aes2501.test 433s SUMMARY: total=36; passed=36; skipped=0; failed=0; user=24.8s; system=12.7s; maxrss=35352 434s autopkgtest [00:54:43]: test installed-tests: -----------------------] 438s autopkgtest [00:54:47]: test installed-tests: - - - - - - - - - - results - - - - - - - - - - 438s installed-tests PASS 442s autopkgtest [00:54:51]: @@@@@@@@@@@@@@@@@@@@ summary 442s installed-tests PASS